Allen landed somewhere between game-winning touchdown and game-ending interception in this one. It was like watching Peyton Manning lead the 2009 or 2010 Colts against Brady’s Patriots those years, two attempts at 17-point comebacks in the fourth quarter with vastly different outcomes. That’s when Allen quickly drove the Bills 75 yards for a touchdown, watched Brady go three-and-out with two incompletions, drove for another touchdown on a shorter field, and again the defense stopped Brady cold in the four-minute offense of a 27-24 game. Yet with Tampa Bay up 27-10 with 11:20 to play, this felt like it was finished. But despite getting two straight possessions inside Buffalo territory, Tampa Bay came away scoreless. The first non-quarterback run of the game was in the third quarter, and even that was a fake punt that failed miserably to convert. But while the usually stout run defense watched Allen unconventionally do it his way for 109 rushing yards, it looked like the Bills putting 100% of the offense on Allen was a total bust.īuffalo became the first NFL offense since at least 1991 to not give a single carry to a running back in the first half. You know which defense didn’t give up a completion longer than 25 yards? Tampa Bay. You know who watched Buffalo fail to capitalize on multiple tipped balls in this one? Tom Brady. NBC’s Cris Collinsworth was ready to give Josh Allen the MVP that night just because the Chiefs couldn’t cover anything deep and couldn’t stop the ball from being tipped for interceptions. They haven’t been able to stack wins since their season peaked with a Week 5 win in Kansas City.

Sure, some would pick Packers-Chiefs, but even if you didn’t know Aaron Rodgers would miss it with COVID, you should still know better than to trust Green Bay to get back to a Super Bowl before the LOAT.īut the Bills looked far from Super coming into this one. If there was an AFC-NFC matchup on the schedule this year that you would have circled as a Super Bowl preview, this was the choice for months. So, it ended up not being an all-time stinker of a week (unless you are stuck watching the Jaguars, then they’re all epic stinkers).īills at Buccaneers: Interfering with My Plans It was really the most exciting quarter I’ve ever seen in a Bears-Packers game. Then the Bears-Packers game went off the rails in the second quarter with the teams combining for 45 points on a lot of long touchdowns.

The Bills and Bengals found their offenses, forced overtime, and both still lost to the only game-winning drives of the week. Rams-Cardinals better be an instant classic on Monday night to salvage this.

Then a Bears-Packers game to cap off the day? Give me a break. Instead of close, high-scoring affairs, the 49ers led Cincinnati 20-6 late and the Buccaneers got up 27-10 on Buffalo in the fourth quarter. Once again, the two games between non-losing teams were most disappointing. slate always looked better on paper this week, but it was not helping matters with the Chargers and Broncos jumping all over the Giants and Lions in routs. Two of those games fabricated drama late thanks to the Cowboys and Browns nearly shitting their pants, but there were never any lead changes there. The Chiefs led the no-show Raiders 35-0 in the first half, the Browns were up 24-3 on the Ravens, and the Cowboys took a 27-8 lead into the fourth quarter in Washington. This shit was rotten, and the three games between teams with non-losing records were among the biggest offenders. You know it’s bad when one of the six comeback attempts this week was Houston, down 19-13, against Seattle in a game that ended 33-13. slate, about the closest finish we had all week was the Thursday night game between the Steelers and Vikings, a game where Pittsburgh trailed 29-0 in the third quarter before an impressive attempt at a historic rally came up short. That’s not hyperbole that’s research on the closeness of games. Once again I was ready to proclaim Week 14 as one of the worst I ever covered in my history with the NFL.

Week 14 ben roethlisberger stats