Denzel Ward on Corey Davis’ 66-yard TD: It wasn’t my coverage, but I’ll take the blame


The Jets scored two touchdowns in the final 1:22 to beat the Browns. It left the Browns to try to figure out what went wrong.

There is plenty of blame to go around, including giving up a 66-yard touchdown in the final two minutes. It seems inexcusable that Corey Davis, even with his speed, would get so far behind the defense for an easy score with 1:22 remaining.

It completed a two-play, 75-yard touchdown drive that used up only 33 seconds, and the Jets then recovered the onside kick.

Browns cornerback Denzel Ward has taken the most heat for the play, but he said Monday it wasn’t his responsibility.

“It wasn’t my coverage,” Ward said, via Mary Kay Cabot of the Cleveland Plain Dealer. “But I’ll take the blame for it.”

Davis ran by Ward with safety Grant Delpit behind Ward, but it’s unclear exactly who was supposed to do what. Ward said he was “playing the flat” in the Cover 2, and he had coverage on tight end Tyler Conklin.

But Ward added that “it’s easy to fix.”

Delpit said the Browns had two possible coverages on the play and mentioned a “communication error” several times.

“I’m not going to play the blame game with my teammates,” Delpit said.

Ward responded to criticism on Twitter on Monday morning, writing, “I was only targeted one time yesterday. A lot of fake news out there. People don’t know what they don’t know.”

The only thing anyone knows for sure is Davis scored an easy touchdown in the final two minutes as part of collapse for the ages by the Browns. There is plenty of blame to go around.

12 responses to “Denzel Ward on Corey Davis’ 66-yard TD: It wasn’t my coverage, but I’ll take the blame

  1. Seems like the guy that gets burned badly always thinks it was someone else’s coverage. Jalen Ramsey starts yelling at a teammate every time he gets burned.

  2. Starting out by saying it wasn’t your coverage is the opposite of taking the blame.

    Also, shout out to Amari Cooper on the hands team for failing to secure the onside kick. Who had the coverage on the game losing touchdown?

  3. When up by 2 TDs with under 2 minutes remaining the idea is to take away the big play and allow a short play that east up the clock, especially if it’s in bounds.
    Letting speedy WRs run deep while uncovered is the opposite of what you want to do.

    While Flacco isn’t a good QB anymore he can still throw it fairly deep.
    So I don’t understand how it happened.

  4. This never should have come down to the defense saving the day anyways. Love Chubb, but if he don’t score that 3rd td, we run the clock out and win. Having said that,That was clearly Delpit’s coverage and he blew it. We gotta clean that stuff up quickly.

  5. Poopy Mcpoopface says:
    September 20, 2022 at 5:54 am

    While Flacco isn’t a good QB anymore he can still throw it fairly deep.
    So I don’t understand how it happened.


    Teams shouldn’t sleep on Flacco the guy can still play at a NFL level. He may not be the guy he used to be but he isn’t chopped liver. Surprising, yes. Unbelievable, not so much.

  6. Honestly, it’s completely the Coaching staff’s fault. After getting burned by a similar play in the last minutes of the prior week, they should have gone to Man-to-Man defense. The “prevent” and/or zone defense that they always go in at the end of every game is exactly what is “preventing” them from winning. They need to play the same shutdown defense style that has worked for them the previous 3 quarters instead of this “give up the short pass” garbage that they go into for every 4th quarter. These players are not yet smart enough to play zone defense. They have no clue what their assignments are in zone defense. Trust your D-Line to put pressure and trust your DB’s to cover their man. Plain and simple.

  7. It should have been both his and the safety’s coverage. they should have been in prevent. should have had at least 4 DBs covering deep. The jets didn’t have any timeouts. So to me, this is on the D-coordinator. and he can get his pink slip anytime now.

Leave a Reply

You must be logged in to leave a comment. Not a member? Register now!

This site uses Akismet to reduce spam. Learn how your comment data is processed.