2024 NFL Stat Oddity: Divisional Round

After a lackluster wild card round, the NFL’s divisional round delivered with the Chiefs inching closer to the three-peat, the Commanders pulling off an all-time upset in Detroit, a quality snow game in Philadelphia, and the most Baltimore ending possible in Buffalo.

I couldn’t personally get a parlay to hit, but at least my tight ends parlay (+539) on 365Scores was correct, and I had some other good picks like Travis Kelce having another 70-yard game in the postseason, Amon-Ra St. Brown going over 90 yards, and Terry McLaurin scoring a touchdown.

At least I was right that Ravens-Bills would not be a great quarterback duel, and it would come down to those things like fumble recoveries and avoiding big drops, which the Ravens of course failed to do again.

I’ll try to limit officiating talk here because I’d prefer to do something more in depth on that later this week. Plus, it’s just really annoying to harp on that for every game when we know the officiating is bad. None of these games were directly decided by the refs.

Save that kind of referee talk for Championship Sunday from the 2018 season (IYKYK)

This season in NFL Stat Oddity:

Ravens at Bills: Baltimore Blunders Strike Again

I’ll be curious to watch the season finale of Hard Knocks this week and see how John Harbaugh reacts to the latest playoff loss for his Ravens. This one was different, and yet at the same time, it was very much on brand for Baltimore throughout his tenure. I’m not sure any other recent franchise has a long list of blunders like this in close playoff losses:

Some of those games weren’t that close (2009 Colts, 2019 Titans), but many were, and many of these plays can probably be visualized in your head by their brief mention if you’ve followed the NFL closely for years.

I’ve pounded the table for the “Same Old Steelers, let’s fire Mike Tomlin” crusade for years now in Pittsburgh, which also loses playoff games in excruciatingly similar ways year after year. But while Harbaugh can say the same of his team, I simply don’t see it the same way that he’s got to go if they’re ever going to change.

At some point, the play is out of the coach’s hands, and players have to make the plays. Catch the ball, protect the ball, make the kick. Hold onto the fucking ball, as Lamar Jackson pointed out after the game, probably the most frustrating loss of his career after he had his best season in 2024.

I can already see the legacy talks for Lamar won’t be kind after this game even though it was clearly his best performance in a playoff loss. If he does indeed have a third MVP win this year, good luck ever getting nominated for a fourth. People are not going to take his regular seasons seriously until he puts together a great playoff run.

Maybe that’s fair too. But what’s not fair is to lump this 27-25 loss in Buffalo in with the past Baltimore playoff losses for Lamar.

Remember that stat about how he had his game with the fewest points that season in the playoffs all four times he’s gone? He broke that streak by putting up 25 in this game (lowest game was 16 points in Pittsburgh). Unfortunately, the Ravens were 13-0 when they scored 28+ this year and 0-6 when they didn’t. They needed 28+ again to win this game too and came up a little short.

But this game was still different. Usually, Jackson loses a low-scoring game and wire-to-wire in the playoffs. This time, he led an opening touchdown drive, making some big plays on third downs and making it look easy. But Buffalo was able to answer with its own opening drive touchdown to tie it at 7.

Jackson’s next pass was intercepted on either a poor read or a ball that just got away from him. Uh-oh, here comes the narrative. He can’t handle the playoffs and this was the coldest game of his career. But the Bills punted from there, so it didn’t really harm things.

The next drive was the significant one with the Ravens driving into Buffalo territory in a 7-7 game. It always hurts when you compound mistakes in the playoffs, and the Ravens did that here. Mark Andrews dropped a pass that should have set up a 2nd-and-short, then a bad snap was high to Jackson, he tried to make too much happen on the play instead of settling for a sack and third-and-long, and he fumbled it. The Bills returned it to the Baltimore 24 and set themselves up for another one of those short touchdown drives with Josh Allen scoring from 1 yard out to go up 14-7.

Just like that, Lamar had two quick turnovers, something he hadn’t done all regular season, and the playoff choke narrative was writing itself nicely. But there was a drop and bad snap that directly preceded that mistake. He wasn’t alone there.

We used to show grace to people who made up for their mistakes, but that seems to have gone out the window in today’s society. If you look at how Jackson finished the game from there, he played great and did his job. Throw in an opening-drive touchdown, and it’s really those two plays with the turnovers that were his biggest flaws on the night.

In the past, Lamar would have just crumbled from there. This time, he made plays and strung together drives, but they still didn’t all result in touchdowns because the running game had some letdowns. I’m not sure why they didn’t pound Henry more when they had 1st-and-goal at the 2. They were stuffed, then tried throwing twice before settling for a field goal and 14-10 deficit.

Buffalo used most of the final 3:43 in the half to score a touchdown, but the drive was not without controversy. On a 3rd-and-5, Allen threw incomplete for rookie Keon Coleman, who drew a defensive pass interference flag against former Bill Tre’Davious White. The call was bullshit. That’s either OPI or preferably no flag at all since they were both engaged with each other. Just a terrible call that led to the Bills scoring another 4-yard touchdown run by Allen to take a 21-10 lead into the half.

https://twitter.com/GeneSteratore/status/1881143728703979919

Again, this is the spot where you expect Lamar to crumble, but it did not happen this time. It helped that the Bills punted twice in the third quarter after a couple of ineffective drives. Frankly, I have no idea what the plan was for Buffalo’s passing game. They ran a chickenshit, dink-and-dunk style passing game where Allen got the ball out the fastest he has all season, but it only kind of worked because the running game was solid with America getting a chance to see how impressive this line and trio of backs has been.

But it took Allen a long time to even break 100 passing yards, and he only finished the game with 127 passing yards and 20 rushing yards on a quiet night.

Once Henry broke through with a touchdown run on his best drive of the night by far (he finished with 84 rushing yards), the Ravens went for two. I always say they’re terrible at these, and they didn’t prove me wrong as they love throwing on them. Jackson’s pass was incomplete and the Ravens still trailed 21-19. I didn’t think it was too early to go for it there.

The Bills settled for a 51-yard field goal to make it 24-19. This was looking a lot like their playoff game in this round last year against the Chiefs with Allen mixing a good running game and the dink and dunk to have a fourth-quarter lead at home. But Jackson had his shot to go up 27-24, the same score the Chiefs won that game by last year.

It was going well until Andrews decided to try getting YAC at midfield, only for him to have the ball punched out on a huge fumble. Just the second lost fumble of his career too. He usually doesn’t try to move like that in the open field, and it was a big turning point.

The Bills turned that into points but not before a huge decision on 4th-and-2 at the Baltimore 2 with 3:31 left:

  • Do you try to go for the touchdown and 31-19 lead, putting it basically out of reach with a 2-touchdown lead and the Ravens down to one timeout?
  • Do you go for the short field goal and take a 27-19 lead, feeling comfortable that the Ravens will blow another 2PC?
  • Do you risk not getting it, and leaving yourself open to the Ravens driving for the go-ahead touchdown?

In the end, I think Sean McDermott made the right call of a field goal just because of how sure I am about Baltimore screwing up those 2PC plays. With Henry on the sideline, without Zay Flowers all game, Jackson faced his legacy drive.

I thought he did a good job with it, and maybe scoring so quickly (1:33 left) was an issue as Buffalo would have plenty of time to go get the winning score. But you’re going to take the score when it’s open, and Jackson found Isaiah Likely for the 24-yard touchdown.

But what do they do on the 2-point conversion? They’re now 2-for-9 on these in the fourth quarter when trailing with Lamar at quarterback. I even have a tweet from 2021 talking about how they go to Mark Andrews way too much in these situations and don’t connect.

Sure enough, it happened again. I even screamed “Andrews!” at the TV as I saw he was open on the right side, and the pass was thrown to him again. I thought the pass was good enough and should have been caught by a Pro Bowler, but he just flat out dropped it, solidifying his spot as the biggest choker at his position as he still hasn’t scored a touchdown in the postseason. Couldn’t even catch this game-tying play right in his hands.

That was it. The Bills recovered the onside kick and ran out the clock for a 27-25 win. The Ravens couldn’t overcome their minus-3 turnover margin on the road even though the tie was right there. Like Buffalo last year against Kansas City, it may have just ended in a 30-27 loss to a last second field goal, but you never know.

And you’ll never know when you make mistakes like that drop. Andrews should definitely get the brunt of the blame with his late-game mistakes. There’s just no margin for error left when you do that so late in the game to kill multiple drives.

The Bills had a 34-yard pass play on their third snap from scrimmage, then never had a play gain more than 17 yards the rest of the night. They sat back and pounced on Baltimore’s mistakes, getting the fortunate fumble and great field position from Lamar’s fumble on a bad snap, getting the bogus DPI call before halftime for an additional 4 points, and adding the insurance field goal after Andrews’ fumble that they forced with the punch-out. That was enough for the win this time.

The Ravens were kind of built to self-destruct at some point, but it’s still stunning to see that Jackson and Andrews would make these mistakes again in the biggest game of the year. It was Jackson early and Andrews late.

But the other stat that caught my attention, and maybe this is the way to bring it full circle and lay some responsibility on Harbaugh, is the lack of takeaways by the Ravens’ defense in the postseason.

Remember last year when Baltimore had the defensive triple crown? No. 1 in points allowed, sacks, and takeaways? Well, that great defense didn’t force a single takeaway in either playoff game against the Texans or Chiefs. That doesn’t mean they didn’t play well enough to win both games, but they didn’t get the takeaways that make it easier to do so like Buffalo’s been getting all year. The Bills are somehow now +16 in fumble recoveries and +27 in turnover margin this year – absurd numbers. They just set the modern NFL record with 21 straight games without losing the turnover battle.

Meanwhile, the Ravens have tied the NFL record by going four straight playoff games without a takeaway. Their last came in the 2022 AFC wild card in Cincinnati, the game started by Tyler Huntley for an injured Lamar, who hasn’t seen a takeaway in a playoff game since 2020 in Tennessee. That’s five straight playoff starts for Lamar where his defense didn’t get a turnover, which would be the longest streak in NFL history.

It’s still the ultimate team game. Baltimore’s lack of playoff success in the Jackson era has never been about only him, but he has been the central figure as the quarterback who has played well below his standards in those games.

But this game was something different. He had his mistakes, but so do many quarterbacks in big playoff games, including everyone from Joe Montana to Tom Brady to Patrick Mahomes. I don’t remember when perfection was ever the requirement to win these games.

But when your star tight end turns into whatever you want to call Andrews’ performance, and your defense doesn’t get any takeaways or create a real swing of momentum, then you’re left with coming up short like this.

I can understand why Jackson sounded extra frustrated in the post-game, and even if he was truly talking about his own turnovers, I can forgive him if he had Andrews first in mind after everything that happened this season from Likely’s toe on opening night to Kyle Hamilton’s dropped interception in Cleveland to Justin Tucker’s awful game against the Eagles to now this loss in Buffalo.

At least we know damn well that the Ravens would have choked on the 2PC in Kansas City if they went for it opening night. I said it then. But if I knew in 2021 that they were throwing too many passes in general and way too many to Andrews in these clutch 2PC moments, why don’t they know that in 2025?

Jackson is making progress in the playoffs with three pretty solid games in his last four tries. His QBR (85.8) was higher in this game than Allen’s (71.1), and yes, he even beat him in the precious EPA stat.

But is Andrews making progress in big games? No. Is the defense coming up with the kind of clutch takeaways that drove teams like the Commanders, Eagles, and Bills to wins this weekend? Nope.

At least the Ravens didn’t panic after going down 21-10 this time, but their progress in the playoffs is slow moving. Bad enough to change coaches? I’m not sure. I just know someone is always screwing up in Baltimore save for 2012, and even that year was saved by Rahim Moore taking the worst angle possible on the touchdown to Jacoby Jones (RIP) in Denver.

Had that gone like every other Baltimore postseason, I don’t think I’d be talking about Harbaugh coaching this team right now. He’d have been let go many years ago.

But the Ravens have just completed one of the most dominant 7-year runs (2018-24) in NFL history without a single Super Bowl appearance to show for it. Even the 1979 Rams got there with Vince Ferragamo at quarterback. The closest thing to Baltimore might be Buffalo if that team loses next week too. Otherwise, it’s probably the 1999-2005 Colts as the closest comparison.

That team won the Super Bowl in 2006 after people wrote them off when they followed a 9-0 start with a 3-4 finish. They still had their albatross receiver (Marvin Harrison) weighing the offense down in the postseason, but they still produced enough points and the defense finally started producing turnovers.

Maybe Baltimore can do that in 2025, but it’s tough to keep coming back after finishing short like this. The competition isn’t going away either. It’s the same demons to slay, but Baltimore might have to look in house and fix some of their own demons first. Whether that means moving forward with Likely as TE1, a different coach, or trying to become more of a pass-first offense, they need to shake things up.

And no matter what you do, hold onto the fucking ball.

Commanders at Lions: Shock and Awe

I believed in Jayden Daniels enough to cover the spread and give Detroit a battle, but I sure as hell didn’t expect a 45-31 win to end Detroit’s dream season. He had that kind of “road virtuoso” performance that is so rare in the playoffs for a considerable underdog, and he did it as a rookie – granted, the best rookie QB to ever do it.

But for as shocking as the game was, it kind of made sense too. I just wrote the other day that Detroit’s fatal flaws are Jared Goff going goofy with turnovers and the defense having too many injuries to survive a playoff run against these non-Sam Darnold-led offenses.

Sure enough, both things did them in. Goff turned it over three times in the first half, then one more for good measure at the end with the game basically out of reach. The Lions also did themselves no favors when they threw a pick on a trick play in a 38-28 game in the fourth quarter with Jameson Williams making a bonehead throw. Maybe burn that one, Ben Johnson.

But I think the clear turning point was in the second quarter. You have this fun offensive game going on. Terry McLaurin just took a pass 58 yards to the end zone for a 17-14 lead. You think Detroit is going to answer, then bang, Goff throws a bad pick-six, he gets absolutely destroyed by a cheap shot to the face on the return. That should have been a penalty to negate the touchdown and make Washington earn it on offense. Instead, they get nothing in their favor and Goff leaves the game momentarily.

That’s what started the Lions chasing a 10-point deficit the rest of the night. You like to think you can get one score before halftime, but Goff threw another pick. Then when you think you have some answers in the fourth quarter, you leave 12 men on the field defensively on a 4th-and-2, and the Commanders convert one that way in embarrassing fashion for Dan Campbell’s staff.

Then the Williams pick disaster happened, and just like that, it’s 45-28 with half a quarter to go and your season is essentially over. You can’t make up that turnover deficit against such a hot offense that played mistake free football. Daniels diagnosed the blitz so well, he didn’t take any sacks, no turnovers, and they were 3-of-4 on fourth down (not including the 12 men penalty).

It’s crazy to think the Lions were closer to winning last year’s Super Bowl than this one. I made sure not to blame Goff or Campbell’s decision making for last year’s blown lead in San Francisco in the title game. That was more about the Josh Reynold drops, the Gibbs fumble, and the deflected pass to Aiyuk that could have been picked. But this time around? Yeah, Goff shit the bed and that defense just didn’t have any answers for Daniels and company outside of a poorly run sneak by Marcus Mariota on the opening drive.

Just spectacular stuff from Washington, the only road team to win this postseason. They have one more tough task left, but why shouldn’t the best rookie quarterback ever become the first to start a Super Bowl? That’d be a hell of a story.

It also puts to shame these teams who talk about multi-year rebuilding plans and act like you need so many years to get competitive. This team won 4 games last year, hired a retread in Dan Quinn, a retread OC in Kliff Kingsbury, signed cast-off veterans like Zach Ertz and Austin Ekeler, and it’s all working because they found the right quarterback in Daniels. How can you not be impressed?

As for Detroit, it looks quite possible 2023 was their window to get it done. Beat the 49ers, and they would have had their shot at upsetting the Chiefs without great weapons on KC’s side that year and a head-to-head win to start that season in Arrowhead. The Lions aren’t going to fall off in 2025 most likely, but you wonder if they lose Johnson, what happens to the offensive creativity, and is Goff someone you can trust to go the distance in the playoffs? The defense should be healthier, but I question even if they had Aidan Hutchinson if they still have enough stars to be a championship unit on that side of the ball.

But I genuinely feel bad for Detroit fans because I thought this was going to be their year. Their aggressive calls on fourth down could have been quite the show against the Chiefs in the Super Bowl if the No. 1 seeds met. Now, maybe Washington can be that team with a true gamer and demon at quarterback in Daniels.

Rams at Eagles: Saquon the Snow Angel

My expectations for this game were low since I didn’t think the Rams had the offense to keep up if the Eagles were going to throw it more, and I expected another big game from Saquon Barkley.

But it turned out to be a good game in the snow thanks to the Rams showing Monday night wasn’t a fluke as they sacked Jalen Hurts seven times, including a couple of drives where they knocked him out of field goal range. They also recorded a safety on a sack where Hurts seemed to have no interest in trying to avoid it just minutes after a bad looking play on his knee on another sack. Maybe he needed some more time but his movement wasn’t great the rest of the game.

That kept the Rams alive, and so did a couple of missed extra points from Jake Elliott. But it’s really a miracle the Rams were 13 yards away from winning this game in the closing seconds when you consider their two lost fumbles in the second half, then giving up three touchdown runs of 40-plus yards in the game. Saquon again gashed them twice for 60+ yard scores, including what should have been the clincher from 78 yards out with 4:36 left.

But that missed extra point made it interesting at 28-15. Matthew Stafford finally started hitting some passes in succession in the no huddle, the Rams managed the clock well to get the first touchdown, and the defense stood tall on the three-and-out after sacking Hurts on an ill-advised second-down pass call.

Stafford had 2:23 left to drive 82 yards for the win, which would have been such a shocker after Barkley’s long run. The drive was going pretty well, but then the Rams had a huge false start, then picked the worst time to let Jalen Carter to crash in for a sack that brought up 4th-and-11. Stafford’s pass really wasn’t even close to Puka Nacua on the sideline and the game was over.

The Eagles had 184 rushing yards on their three big touchdown runs, and just 65 net passing yards to go with it because of the sacks. I thought A.J. Brown would step up after last week’s game, or that DeVonta Smith would be a big factor after he missed the Week 12 game. But they had 6 catches for 35 yards combined in this game.

Throw in Hurts sounding like he was high on pain medication at the end of the game and uncertain about next week, and it’s not the greatest look for next Sunday against the Commanders, who are rolling with confidence right now.

Don’t go penciling that Chiefs-Eagles rematch in by any means. It probably should happen just based on the general strength of these teams and home-field advantage, but they rarely make it look easy.

They still win though. But that was a solid effort from the Rams in weather they’re not used to playing games in.

Texans at Chiefs: When You’re Rusty and Still Win Wire-to-Wire

The Chiefs have broken the brains of so many people that I’m not sure what they’ll do if this team manages to win two more games this season. Even in a game where the Chiefs came out a bit rusty after 24 days since Christmas, they still never trailed, they found ways to make Travis Kelce look like his vintage self, and they put away the Texans with eight sacks and blocked another 35-yard field goal for good measure to the naysayers.

Were the Texans outplaying them early despite the scoreboard? Yeah, I said as much, and if you ignore dreadful special teams. But that all changed halfway through the second quarter. After Hollywood Brown dropped a perfect deep ball, Travis Kelce was left wide open over the middle where he actually made a YAC play for the longest playoff catch of his career (49 yards). The Chiefs finished that drive for a touchdown and led 13-3.

Even after that moment, the Chiefs still outscored the Texans 10-9 before intentionally taking a safety in the final seconds. The game never really felt in doubt, but that won’t stop ESPN from acting like it was a travesty the Texans lost another divisional round game. From Troy Aikman having a fit in the booth about the penalties to graphics like this after the game, they’re really trying to sell it hard that a team who lost wire-to-wire was the better team and something unnatural must have caused this loss:

Yeah, it’s called the Texans played poorly, and the Chiefs took advantage of it.

On Sunday, the NFL supported both the roughing the passer call and late hit on Mahomes’ late slide. Don’t say the NFL never admits to errors, because I have a list of such times they did coming up this week. You may not like the dynamics of those calls with the late slide an issue, but they said any time you go to the head and neck area, it’s likely going to get a call that wouldn’t be changed even if replay assist looked at it.

Also, I can’t believe people are going to pretend like the Chiefs couldn’t overcome a 2nd-and-6, which would have been the situation after the Mahomes scramble without the 15-yard flag. Did the refs give up that touchdown on 3rd-and-goal from the 11 too? A perfect pass to Kelce while falling down to make it 20-12 in the fourth quarter.

Did the officials cause C.J. Stroud to go 1-of-8 in success rate while trailing 20-12 in the fourth quarter? He did that. The Chiefs tackled him cleanly on the opening drive that made him limp, and while he still had some good scrambles in this game, by the end of it he couldn’t move well, Steve Spagnuolo smelled blood in the water, and they racked up four of their eight sacks on one drive.

Then there’s the piss-poor special teams. You could see it on the opening snap when the Chiefs had a 63-yard return, fumbled it, but Houston failed to recover. Then the idiot (Kris Boyd) who forced the fumble threw his helmet off for a 15-yard flag, then had the nerve to go shove his position coach on the sideline.

If that wasn’t enough, the kicker Fairbairn missed an extra point, badly missed a 55-yard field goal they probably shouldn’t have attempted in the cold, and had his 35-yard kick blocked just so the Chiefs can show Denver was no fluke. That’s a 10-point swing on special teams alone, and with the Chiefs getting some good field position on several drives, that helped build up a yardage disparity.

But the other disingenuous part of that 49-0 graphic is the “outgained by 100 yards” stat of it. The Chiefs were outgained by 124 yards (336-212), but they lost 27 yards intentionally on the last drive with a couple of kneeldowns and an intentional safety. Otherwise, they wouldn’t have been outgained by 100 yards and the stat wouldn’t exist. The safety might not have been 100% necessary but the strategy was to avoid a blocked punt return touchdown, the most harmful outcome that could have happened to the Chiefs at that stage of the game.

But I’m really annoyed about hearing about officials when the Texans played this poorly. Both defenders were clearly headhunting too on the play where Mahomes gave himself up and they could have just tagged him down. They took each other out on a head-to-head hit anyway, the same team that knocked out Trevor Lawrence with a nasty concussion this season. Maybe your team just has a target on its back from these plays, Houston.

I don’t see how the ref made DeMeco Ryans delay a decision to go for a fourth-and-10, fail to call timeout, then lose a bunch of yards on a sack. Houston played poorly. Even their 82-yard touchdown drive had to gain 101 yards of offense because they kept shooting themselves in the foot with penalties. It was that inefficient of a performance in turning yards into points.

There are things I’d like to see the Chiefs do better. You’re probably not beating Buffalo with 23 points or 0 catches from Hollywood and DeAndre Hopkins. The designed plays to Worthy felt too gimmicky and not the best use of his emerging talent. The lack of go for the kill shots in Houston territory were alarming from Andy Reid, who seems to get off by keeping the game within one score.

But the Texans did not even come close to deserving to win this game. The Chiefs took advantage of their mistakes and that’s why they’re moving on to host another AFC Championship Game, their seventh appearance in a row.

Next week: Huge rematches on Championship Sunday and so much history at stake. You’re God damn right I want the rookie QB vs. the three-peat in the Super Bowl, but that could be the least likely outcome we get from this final four. The Chiefs will have to overcome their last loss with starters against Buffalo, and the Eagles have to overcome their only loss in their last 15 games against the Commanders. That’s good stuff.

NFL 2024 Divisional Round Predictions: The “Oh Fvck, It’s Finally Here” Edition

It’s been a pretty long week building up to my favorite NFL week of the year. After a lackluster Wild Card Weekend, I’m ready for some real drama and memorable moments that I think this round, short of a classic Super Bowl, provides the best.

Do we get it? That’s hard to say. I think these four games have a lot of potential for volatility to them.

  • Are the Chiefs rusty as hell with this 24-day window since playing the Steelers, or do they look sharp and easily get past a Houston team that flopped 34-10 in this spot a year ago after one decent half in Baltimore?
  • Does Jayden Daniels only grow his legend in Detroit in a close game, or is this payback for 1991 NFC-CG (41-10 win by Washington) and another rookie QB gets routed on the road in the playoffs by a +222 scoring differential juggernaut? I do like that it’s indoors given this week is cold as fvck and that’s probably going to hamper the other games.
  • Do Saquon Barkley and Derrick Henry just run wild over the Rams and Bills again, or will Jalen Hurts and Lamar Jackson actually need to throw the ball for more than 150 yards this week? And can Jackson do it in the cold without his best wide receiver (Zay Flowers)?

All I know is home teams were 5-1 last week. The team who won the previous game was 3-1 in rematches. Only one losing team scored more than 14 points. Washington was the team that broke through for all three stats. Let’s see what happens this time around.

This Week’s Articles

NFL Divisional Round Predictions

At least we’ll get my main rooting interest this weekend out of the way first.

Texans at Chiefs (-8.5)

The Chiefs win a playoff game by more than one possession? Surely you jest. But I am nervous about this one, just because it’d be a devastating blow to see the three-peat end with this opponent in the divisional round. Losing next week to either team is whatever. It’s logical. This would even be logical if the Texans had Stefon Diggs and Tank Dell, but instead they’re limping in with only Nico Collins and JAGS while hoping the defense gets a bunch of takeaways. Let’s not forget how bad Houston looked in the first half last week, which says a lot about how bad the Chargers were.

But it’s the rust thing too. 24 days off for starters is historic. I think people are reading this as a criticism of Patrick Mahomes too, but it’s not even about that. I trust him more than anyone on the Chiefs to show up. But what if it is a slow start on both sides of the ball, and you see the Chiefs get into trouble the way they did against Houston in the 2019 AFC-D when they fell behind 24-0? That’s dropped passes, a blown coverage TD on defense, a special teams mistake, etc. — All things this team is clearly capable of doing in 2024 too.

What they’re not capable of doing in 2024 anymore is coming back from a 24-0 deficit in the blink of an eye. They’ve been too methodical on offense and don’t have the big runs and YAC plays to get it done like that anymore. The Chiefs are also riding a record-tying streak of 7 games without a turnover, so that could snap in this game but they better just hope it’s not multiple turnovers or that they lose the battle there by multiple turnovers. Defense can contribute too.

But yeah, I could see someone like Jaylen Watson taking a misstep or missing an assignment in his first game since October. He has the best excuse to be rusty for the Chiefs in this game.

The Chiefs losing this game would plague hell on my mentions this weekend. But for the people talking about point differential, let’s not forget the Texans are 372 points scored, 372 points allowed this season. That’s not an impressive team. C.J. Stroud has yet to win a playoff game where his defense/ST allowed more than a net 3 points.

I think the Chiefs are playing with fire in a way that isn’t really their fault because of scheduling, getting the No. 1 seed, and injuries to key players. But working in a new LT (Humphries or Tuney) and WRs (Hollywood) this late in the year against a good pass rush isn’t the greatest. Of course, Week 16 happened too, and that’s why I’m not that concerned.

Just survive the first half and the Chiefs should be fine. But no, I’m not picking them to cover. This is the Kansas City special. They don’t cover but they still win.

Final: Chiefs 24, Texans 17

Commanders at Lions (-9.5)

Pretty cool to see the only two teams in NFL history to have 3 games in a season with 0 punts/turnovers face each other in the playoffs. I hope it is a 4th-down fever dream from both sides with dazzling plays and second guessing all night — a game so weird that David Lynch is looking down and nodding in approval.

I like those stats that the Lions have failed to win by 10 points in 8-of-9 games where they allowed 20 points and also in games where they turn it over once. I think Washington can achieve both of those things in this game, especially the scoring since they’ve had at least 18 in every game.

But it’s tough for a rookie to win games like this, and Daniels already exceeded expectations last week. Still, I’m going with the same score I had last week, the same score the Commanders lost in Baltimore this year.

Final: Lions 30, Commanders 23

Rams at Eagles (-6.5)

Yeah, you’re not going to convince me this probably won’t be the worst game this weekend. I just don’t care for watching the Eagles most of the time, and that GB game last week is a pretty solid example for why. I wish they showed a little more care in throwing the ball, but maybe this game will get it from them.

But I expect Saquon Barkley to do well without the 70-yard touchdown runs this time. You just can’t stop that line from dominating right now. Then you have an LA team on the road that hasn’t topped 20 offensive points in any of Stafford’s last 4 starts. He’s become so dependent on Puka Nacua. They haven’t scored much on the Eagles the last two years. I have very low hopes for the Rams in this one, but I do think McVay is a better coach than Sirianni, and that defense has been playing very well in the last month. You never know.

Final: Eagles 23, Rams 14

Ravens at Bills (+1.5)

I see we’re already doing that thing where “Lamar should win as the favorite” in a game where the spread has gone from Buffalo -1 to Ravens -1.5, which is still tiny as these teams are so close this year they even have the same scoring differential (+157).

More than Half of my 6,000-word AFC preview was spent on this game, so I’ve said a lot about it already.. But my main takeaway has been this:

I said it before the season that the Ravens bomb in the playoffs because they try to be the offense they aren’t with throwing the ball and leaning on Lamar to do everything. They can’t do that in this game, especially with Zay Flowers out. I think if the Ravens play bully ball and stick with the run and 2-TE formations and Lamar does very well as a dual-threat, then the Ravens have a very good chance of winning this game. Their D has been the best at limiting points in the second half of the season and they already held Buffalo to a season-low 10 points.

But do I trust the Ravens to do that if they fall behind 7 or 10 points? Will they just panic again and abandon Henry and lead Lamar into trouble in what could be the coldest game of his career? This guy is dressed like Ralphie in A Christmas Story in Houston weather. He’s going to be freezing in Buffalo.

If the game was in Baltimore, I don’t think I’d be questioning it as much. But I’m more in the camp that I need to see this team do something differently in a game like this before I believe fully in them to pull it off. So yeah, I’m probably in that mindset that if the Ravens win this game, they’ll beat the Chiefs next week as I said after Week 1 they’ll feel good for the rematch. And if it’s Houston, then hell yeah they’re going to the Super Bowl. Both of these teams will feel SB bound if that first game Saturday goes Houston’s way.

But that’s the thing. I don’t think this game is going to live up to the hype because of the weather and the fact that QB duels rarely pan out in the playoffs. It’s the defense. It’s the better OL/running game. It’s turnovers, which Buffalo better watch out for cause they are long overdue for some fumbles going against them. It’s rarely the QBs, and the four Jackson-Allen games to date haven’t been QB masterclasses at all.

Do the Ravens still win ugly games? Because they might have to here. Haven’t won a game without scoring 28 points this year, but it could happen here if the defense shows up against Allen. I don’t see the Ravens scoring 28 at all. The under 51.5 is one of my favorite picks this week, and if you’re betting on the Ravens to lose, you should probably consider under 16.5 alternate points (think it’s like +500) to keep in line with the “Lamar scores his season low in the playoffs” stat.

But I think it is a coin flip game. The Ravens are more battle tested. They kicked Buffalo’s ass already. They’re better built for this weather right now. But they just have to show us that they can adapt in a playoff game and handle the pressure on the road.

Also, I hope I’m wrong about this game. I hope it is a QB classic, but I just don’t see it living up to 2021 Allen-Mahomes in the divisional round. But the funny thing about that game is the legacy would be even greater if the Chiefs won the Super Bowl that year. They didn’t even get there, losing to the Bengals the following week.

And that’s my other point about this game. For the winner, don’t get too cocky. All this hype about the MVP and this game, it doesn’t mean a damn thing if your team just goes into Kansas City next week and loses again, putting that team one game away from a three-peat, the closest anyone’s ever been.

This is not the end, but it is for one of these teams.

Final: Bills 24, Ravens 20

NFL Stat Oddity: 2023 Divisional Round

Block out the first game of the weekend, and the NFL playoffs were back with points, lead changes, game-winning drives, game-ending interceptions, and questionable coaching decisions and flags from the officials. All the real drama this postseason was lacking last week.

Also, I’d love to see one of the charting sites confirm if this postseason has had more dropped interceptions than actual interceptions, because it sure feels like it has. The fact that Jordan Love and Baker Mayfield were the only quarterbacks to have a pick in their stat line this weekend is crazy, and even half of the pair they each threw was a deflection off their own receiver.

We also were reminded that kickers are people too, and like people, it sucks when they are too far right or far left. The Packers and Bills got a dose of that in their latest January exits.

But the streak of 27 quarters this postseason without a lead change ended Saturday night in San Francisco in a big way, and the games continued being competitive through Sunday too. It sets up a Championship Sunday where the No. 1 seeds (Ravens-49ers) will host the No. 3 seeds (Chiefs-Lions), and I know damn well which rematch I’d rather see in Super Bowl 58.

(Hint: It’s how this season started.)

But before we get to that, let’s go over the four games from this weekend.

This season in NFL Stat Oddity:

Chiefs at Bills: History Did Repeat Itself (But It Was Buffalo Wide Right)

I spent the week comparing this game to the 2006 AFC Championship Game, which was played 17 years ago to the date on Sunday when the Colts came back from a 21-3 deficit to win 38-34 and slay that New England dragon in the playoffs so they could win a Super Bowl.

Well, history did repeat itself in Buffalo, but it looked more like Super Bowl 25 with the Bills playing the role of the ball-control Giants before ultimately revealing themselves to be who we thought they were: Buffalo, the wide right team. The drought continues for another year.

The Chiefs coughed up their worst Obligatory Fumble yet, and even that wasn’t enough for Buffalo to take this game. I am not going to force any more old narratives on this game and will just go over the facts of what happened. But I badly wanted to write early in the fourth quarter that the Kansas City offense was having its best game of the season, and the defense was trying to waste it with its worst.

That was definitely happening into the fourth quarter. Even though Buffalo never had a play gain more than 18 yards, the combination of effective short throws and a strong ground game (sometimes aided by Josh Allen) was producing points and draining clock at alarming rates for the Chiefs. The Bills had 24 points and were averaging 60 yards per drive on their first 5 possessions.

In the 3 divisional round games since 2020, the Bills only gave Allen a grand total of 33 carries for 107 yards in non-quarterback rushing support. In this game alone, he had 27 carries for 110 yards.

Usually, shrinking the game is a good strategy against the Chiefs, because you want to maximize their mistakes like the dropped passes, fumbles, and penalties. Those hurt more if the Chiefs are only getting like 8 drives in the game, which is basically what they had in this one if you ignore the kneeldown to get to halftime after a penalty.

But the Chiefs didn’t hurt themselves that badly in this game. Sure, Justin Watson could have made a better play on a third-down pass on the opening drive that led to a field goal. Mahomes missed a couple of throws in the end zone, settling for a second field goal. But after those couple of misses, the Chiefs were all business with 3 touchdowns.

Patrick Mahomes looked great in his first road playoff game as I expected he would. Travis Kelce ended his 7-game drought without a touchdown by scoring twice. Isiah Pacheco chipped in 97 yards. Even MVS looked competent with catches of 32 and 30 yards. In fact, the Chiefs had 8 plays that gained 20 yards, a huge edge over Buffalo (0) that allowed the Chiefs to score 27 points despite barely possessing the ball. The Bills held the ball for 37:03. This is already the third time in his career that Mahomes has led the Chiefs to at least 27 points in a playoff game despite not having the ball for at least 25 minutes. No other quarterback has done that more than once.

This game was an offensive gem for both teams until the Chiefs scored the go-ahead touchdown (Pacheco 4-yard run) with 14:20 left to take a 27-24 lead. Shortly after that, this one went off the rails.

To Kansas City’s credit, Steve Spagnuolo’s defense has been great at adjusting in the second half all year. They needed until the fourth quarter to get on track here as Buffalo’s only third-quarter drive was a 15-play, 75-yard touchdown march that took up 8:25. That’s always the concern when you have a team using clock and scoring touchdowns to limit Mahomes’ opportunities.

But after Allen had another designed run for 8 yards, the defense made their mark with a run stop that got James Cook 3 yards behind the line. Allen’s pass on 3rd-and-5 for Stefon Diggs was batted down at the line and it was a 3-and-out.

But instead of punting, the Bills ran a fake to Damar Hamlin of all people, and he only gained 2 yards, giving the Chiefs the ball at the Buffalo 32. Supposedly they caught the Chiefs with 10 players on the field and gave it a shot, but I hate that call. It’s just too risky in that spot.

Pacheco immediately ripped off a 29-yard run to the 3 and it looked like that fake punt was going to be the dagger and put the Bills down 10 points. But I had my most prescient moment of the weekend when I warned Saturday night that the Chiefs could try something excessively stupid with Mecole Hardman in this game:

Hardman already got a carry earlier in the game and fumbled in the red zone, which the Chiefs were lucky to recover. Sure enough, they gave him the ball again on a trick play and he fumbled it through the end zone, reaching too hard for a touchdown he’d never get. One of the worst rules in football was correctly applied after a Buffalo challenge, and the Chiefs coughed up their worst Obligatory Fumble of the season.

Just couldn’t help yourself, could you, Andy? No Kadarius Toney (inactive), but you had to make sure Hardman made his mark on this one. I thought that would doom the Chiefs, but again, the run defense made the difference by stopping Cook for a 4-yard loss. Allen threw a deep ball on 3rd-and-12 and Trent Sherfield, playing more for an inactive Gabe Davis, was unable to come down with it. He had a chance.

The Chiefs also had a chance with solid field position (own 43) to put this one away, and they even got a controversial defensive pass interference penalty to convert a third down when it looked like the contact was made before the ball was released. Thankfully, no one is going to care about that one as the Chiefs punted 3 plays later.

The Bills took over with 8:23 left and tried to slow-walk this one down the field. The drive was long, but it was almost constant short throws by Allen. By stuffing Cook for -7 yards on the last two series, I think the Chiefs spooked the Bills out of not running anymore. Right or wrong, the Bills put the ball in Allen’s hands on 10 straight plays on this drive.

It wasn’t going all that great. Allen fumbled on a 3rd-and-10 run and it was a miracle the Chiefs didn’t recover before the Bills did. Looking more and more like fumble bounce fortune was going to end the Chiefs’ season and repeat bid.

Allen converted a 4th-and-3. Cook eventually received 2 carries on the drive, but they went for no gain and 1 yard. I said this drive was full of short throws, but it started with a deep ball for Diggs, who did a horrible job of locating it.

Diggs had a season-low 24 yards on 11 targets against the Chiefs in Week 14. This time, he caught 3-of-8 targets for 21 yards, fumbling on the first snap of the game (Bills batted it out of bounds for a penalty), and making that egregious effort. His decline in the second half of a season where he only turned 30 needs to be studied, because this was significant.

Allen no doubt had love for the short throws in this one, but maybe he was doing it too much. According to Next Gen Stats, Allen’s 16 completions behind the line of scrimmage were tied for the most in any game since 2018.

Having said that, maybe he could have used a few more at the end of this drive? When these teams met in the divisional round 2 years ago, there were 31 points scored after the 2-minute warning. The game reached that point again, so what would we see this time?

Well, I think Allen tried to recreate one of his touchdowns to Davis from that game. The receiver (Shakir) was open in the end zone but they didn’t come close to connecting on a bit of a wasted snap that quickly brought up 3rd-and-9. On that one, I really don’t know what the plan was from Allen, but that too was incomplete and thrown away. There were no sacks in the game by either defense.

You had to go with kicker Tyler Bass from 44 yards out at that point. If you play this game long enough, no kicker is perfect in these situations. But Bass has not established himself yet as someone who you would call reliable in the clutch. After this miss, now you wonder if his career is going to tank like many before him have seen happen after they miss a legacy-defining field goal in the playoffs.

With 1:43 left, Bass’ kick was wide right, the worst fate you can have as a Buffalo kicker as it immediately recalls what Scott Norwood did at the end of Super Bowl 25, which is sadly still going to be the closest the Bills ever were to winning a Super Bowl.

The Chiefs just had to hand it to Pacheco twice for a first down, and that was the ball game. The Chiefs held on for a 27-24 win as no points were scored in the final 14:20 after such a stellar start for both offenses. Mahomes’ road playoff debut was a huge success.

The fake punt didn’t really ruin Buffalo’s game thanks to the Hardman fumble cancelling it out, but would things have gone better without that? Then again, the punter was injured and not doing well all night. Maybe the Bills are just cursed this time of year, and something will always go wrong, and it seems like special teams are often at the forefront of that (Norwood, Music City Miracle, not kicking short to burn time in the 13 seconds game, etc.).

Once is an accident, twice is a coincidence, but three times is a pattern. The Bills can beat the Chiefs by 35 points in the regular season next year and I cannot in good faith pick them to win the next playoff matchup.

I’m out on Buffalo if Mahomes and the Chiefs are involved.

Packers at 49ers: Did Love Text a Dick Pic or Incriminating Welfare Scam Question Before His Favreian Interception?

The future may be bright for the Packers again with Jordan Love at quarterback. But if Saturday night is any indication of things to come, the future may resemble a lot of the past three decades as well.

Jordan Love paid homage to Aaron Rodgers and Brett Favre in the same night by throwing a disastrous game-ending interception and losing to the 49ers in the NFC divisional round. The Packers are now 0-5 in the playoffs since 2012 against the 49ers, including an 0-3 record for coach Matt LaFleur.

Oh, what could have been this time. Like last week, the Packers won the coin toss and rightfully chose to receive. Take it to that front-running team early. But this time the Packers were stopped in the red zone and held to a field goal, which would become a theme of the night.

Brock Purdy had an interception dropped right off the bat and in between his completions to Deebo Samuel, who left with an injury after what looked like could have been a huge night for him.

But the Packers messed up the early second quarter drive when they tried to quickly run a quarterback sneak and Love was ruled short. I hate when teams rush the sneak. The best thing about the play is you can usually convert even when the defense knows it’s coming. Take your time, dig in, and get push. The Packers didn’t get enough push and that was a bad turnover on downs. I never saw any real convincing angle to show Love got it for sure to overturn the call.

George Kittle struck with a touchdown on Purdy’s best throw of the half, then the 49ers later had a 48-yard field goal blocked to end the half with a 7-6 lead. I honestly wasn’t sure which team should have felt better about that half. Both left chances on the field for more points and the Deebo injury was big.

The third quarter was some of the best action this postseason. Bo Melton caught a 19-yard touchdown, which was answered by a 39-yard touchdown run from Christian McCaffrey. After 27 straight quarters without a lead change this postseason, we finally had them pouring in. The Packers even had special teams revenge in mind for their horrific performance in the 2021 divisional round loss. They returned a kickoff 73 yards after CMC’s score, but they nearly lost it on a fumble. That set up a 20-yard touchdown drive, and Love threw to Aaron Jones for the 2-point conversion. Speaking of Jones, the Packers had been a bit of an outlier this postseason as the only real road team who was winning games and running the ball well. Jones had 108 yards on a tough run defense, though 53 of that did come on one play.

But it was enough to take a 21-14 lead into the fourth quarter. Could it have been better? Sure. Love threw behind his tight end and the pass was tipped for an interception, only his second pick in the second half of the season. That set the 49ers up at midfield as the final quarter approached.

But isn’t a 7-point lead usually enough to beat Kyle Shanahan’s 49ers? Yes and no. The stat they showed during the game was that Shanahan is 0-30 when entering the fourth quarter and trailing by 5+ points. He’s now 1-30. But that isn’t the same as saying Shanahan has never won a game when trailing by 5+ in the 4th quarter. In fact, the 49ers were down 24-17 late when they came back to force overtime against the 2021 Rams in Week 18. That win is how they made the playoffs that year.

In those playoffs, they were infamously down 10-3 in the fourth against the No. 1 seeded Packers in the divisional round when they blocked a punt for a game-tying touchdown with 4:41 left before winning 13-10 on a last-second field goal.

That means of the 3 times Shanahan has won a game when trailing by 7 points in the fourth quarter, 2-of-3 were in the playoffs against LaFleur and the Packers. Ouch.

Shanahan’s 0-for stat, which did not apply here and is still active, is that he is 0-38 when the 49ers trail by at least 8 points in the fourth quarter. We’ll see if that one comes up the rest of this season.

The season is continuing after a big finish from the team. Rookie kicker Jake Moody had that big game-deciding miss in Cleveland this year, but he looked good on a 52-yard kick on the first snap of the fourth quarter to make it 21-17.

The 49ers got the ball back and reached the Green Bay 40, but the drive stalled once Purdy tried throwing deep on 3rd-and-10 for Ray-Ray McCloud. That seemed like an insane decision, but that’s what happens when Deebo is out, and Brandon Aiyuk was oddly quiet.

Jones broke his 53-yard run, and that looked like it might be a dagger. But the Packers stalled again, and rookie kicker Anders Carlson was about to join the infamous list of kickers who choked in the playoffs. He’s had his struggles this year, missing 5 extra points, and this was going to be a 41-yard attempt, which shouldn’t have been so bad. I was worried about Moody for the 49ers, but Carlson should have been the one on my radar instead. Sure enough, he pulled the kick wide left with 6:18 left.

It wasn’t nearly as bad as what Gary Anderson did for the 1998 Vikings to ruin his perfect season and fail to give his team a late 10-point lead. But it would have been a big kick for Carlson’s team to go up 24-17 with overtime a possibility in the worst-case scenario. But now he left the door open for the 49ers to take the lead and break the hearts of Packers’ fans again.

I thought Purdy had an underwhelming game and his accuracy was spotty all night. But when it came to the drive of the game, he was money this time. He was 6-of-7 passing with a drop by Kittle. He found Aiyuk for a key 3rd-and-5 pickup. He scrambled for a good 9-yard gain in the red zone. On the next play, McCaffrey took the handoff for an easy 6-yard touchdown run, his second of the game. It almost looked like the Packers let  him score, and given the situation (3rd-and-1, 1:11 left), maybe that was the right call.

But I hated the idea of Carlson’s next kick being one that would determine if Green Bay still had a season left. He probably wanted no part of that kick either, but first the offense had to get him out there.

I attacked Favre and Rodgers for years for their performances in these spots. Favre was in the situation a ton, so he had a lot of game-winning drives, but boy did he have a lot more awful turnovers. Rodgers got better at this in the second half of his career, but he was still prone to taking sacks and not being aggressive enough.

We are still of course learning about Love but yikes, what an impression he left in the biggest moment of his career so far. He had 67 seconds and 3 timeouts, so that is plenty of time to get a field goal even if you had to get that sucker within 35 yards for this kicker to make it.

It looked a little like pulling teeth to get that initial first down, but sometimes that is the hardest one to get. But after using the first timeout with 52 seconds left, I never imagined Love would make such a reckless, awful throw on 1st-and-10. I don’t know what he thought was going to happen, but Dre Greenlaw was there for another pick. Instead of going down and ending the game, Greenlaw was relentless in trying to return the ball. Did he tell his cash-strapped friends to bet $$$$$ on 49ers -9.5 or something? Jesus Christ, get down, man.

The 49ers had separate drives with a 53-yard run and a 38-yard completion and scored no points on either drive. They had a 41-yard field goal to take a 7-point lead and missed it. They were maybe 30 yards away from another game-tying field goal attempt and threw a horrific pick that only would have looked more like Favre if Love was wearing Crocs and texting how to defraud the Mississippi Welfare Fund.

It was a classic Green Bay playoff loss, and it’s good to know the new era is going to share a lot in common with the past two. Better find a Reggie White or Charles Woodson again. Someone who will put down Purdy or hold onto his interception in the big moment.

But hats off to the 49ers too. This was the kind of game I questioned if they could win since they had no game-winning drives all season and rarely were tested this way. They showed they can overcome a slow start and some adversity like the Deebo injury. It should serve them well the rest of the postseason.

Buccaneers at Lions: The Baker-Goff Sunday Matinee We Deserved

Given the lack of history between these teams, I didn’t know what to write to fill up their game preview, so I spent about 1,100 words on showing some appreciation for Jared Goff and Baker Mayfield. They’re both No. 1 picks who have been accused of being play-action merchants and products of Sean McVay and Kevin Stefanski, but both have now won playoff games with different teams, and not anyone can end long playoff droughts for the f’n Cleveland Browns and Detroit Lions.

So, this may not have been your typical divisional round matchup, but the quarterbacks and teams put on a good show in a competitive 31-23 game that got increasingly higher scoring as the talent took over.

Early on, the defenses were making it tough to earn anything. Mayfield had a pass deflected off Mike Evans’ hands that was intercepted on a third-and-long, and the Bucs should have picked off Jared Goff in the end zone on that drive, but he got away with it (drop by Jamel Dean) and the Lions got a field goal out of it.

But that was what made it a good game as the defenses were playing well and making the offenses really earn every first down and point. The Bucs had the upper hand in running the ball early, which was surprising given they were the 32nd-ranked run game again this year, but neither team ran the ball well at all in Week 6. Eventually, the Lions did figure things out and Jahmyr Gibbs popped a 31-yard touchdown run to start the fourth quarter that broke a 17-17 tie and was in effect the game-winning touchdown. Gibbs finished with 74 rushing yards, and tight end Sam LaPorta had 9 catches for 65 yards, so it was another successful outing for the rookie class of the Lions.

Tampa hit the upright on a 50-yard field goal late in the first half, but it did rebound by getting the ball back and Mayfield threw a touchdown to Cade Otton, another young tight end who played well and tied the game at 10 at halftime.

I thought Mayfield played quite well, but there were some troubling mistakes that you’re not sure if it was his fault for missing something pre-snap or if it was a coaching mistake. But there is no reason for Aidan Hutchinson to come in unblocked off the edge on multiple occasions, including a 3rd-and-4 sack to start the third quarter that knocked the Bucs out of field goal range. Hell, the kicker (Chase McLaughlin) probably would have missed again anyway. But that was a mistake that happened a few times in this game.

Speaking of mistakes, I thought the Lions were hosed on a chop block to wipe out a 25-yard gain on 3rd-and-10 deep in their own in the third quarter. It looked like David Montgomery went to block the defender before his lineman did, so that call was pretty weak to me. But the Lions ended up getting the ball back and scored a go-ahead touchdown on a 4th-and-1 run by Craig Reynolds after some passes were unsuccessful by Goff. Just pound it in, Detroit.

But I have my complaints with Dan Campbell too as I felt he was asleep at the wheel when he didn’t challenge if Baker was down on a sack before he threw a ball away to almost end the quarter. It looked like his calf was down and that would have made it a lot tougher on the Bucs to convert. Instead, they threw a screen on 3rd-and-10 and Rachaad White scored a 12-yard touchdown on a great call to tie the game.

Gibbs was absolutely dominant on the game-winning drive with 57 of the 75 yards. The Bucs went 3-and-out, and it looked like the Lions put it away with an 89-yard touchdown drive where Amon-Ra St. Brown was the star this time. He converted a 3rd-and-15 with a strong YAC effort to just get over the line, then finished the drive with a 9-yard touchdown to make it 31-17 with 6:22 left.

St. Brown had his ninth straight game with at least 6 catches and 70 yards. Only Marvin Harrison (2001-02 Colts) and Travis Kelce (2020-21 Chiefs) have done that for 9 straight games in their careers.

But Mayfield kept the game alive and led a great drive with a 4th-and-14 conversion to Evans, who also caught a 16-yard touchdown with 4:37 left to make it 31-23. The Bucs went for 2, and Evans is usually excellent at acting and embellishing to draw DPI flags, but he didn’t do it well here and there was no call despite the defensive back not playing the ball that well. The Bucs still trailed 31-23.

This decision always gets defended as the “analytics play” and NBC’s Cris Collinsworth went through the explanation of it again. I get it. I don’t mind it. I probably would have gone for it too in this game with the way it was going.

But I just hate the way people hammer on this like it’s some amazing cheat code to win games or that it’s always the right, obvious call.

Because it’s not.

I ranted about this on Twitter already, but first, we have to stop pretending that all teams down 14 in the fourth quarter are trying to win in regulation when we know most of them are thinking of tying the game. Todd Bowles does not strike me as the kind of coach who would go for the go-ahead 2 if his team scored its second touchdown with 2:00 or 1:05 left in the game either. He’d think he was playing for overtime.

Also, this is the playoffs and the rules have changed for overtime where both teams are guaranteed possession now. So, would overtime really be that bad of an outcome now when it can no longer end after a touchdown drive like in the past?

The only other thing I’ll say is it never seems to be acknowledged just how aggressive you can make the other team when you do this. Don’t you think Detroit might approach the following drive a little differently if it was up 6 points instead of 7 or 8 points? If you’re up 8, you can be a little safer with that cushion. Same way a team approaches things differently if it was down 1 point instead of in a tied game. If you do this move and get it right on the first touchdown, you’re giving the opponent two chances to be more aggressive. Detroit is more aggressive than most to begin with, but encouraging the Lions to be extra aggressive isn’t the smartest move in my view.

  • Since 2021, 48 NFL teams have scored a touchdown in the fourth quarter while down exactly 14 points with a point after decision to make.
  • 34 teams kicked the extra point, and those teams were 8-25-1 (.250) in the game.
  • 14 teams went for the 2-point conversion, 9-of-14 (64.3%) were successful, and they were 2-12 (.143) in the game.
  • The average extra point kick came with 8:48 left to play.
  • The average 2-point conversion came with 5:47 left to play, so there is a time element to consider as this strategy should be attempted with less time left in the game.

If you ask me, 2-12 when your only wins are the most improbable comeback of the 2023 season (Tennessee in Miami) and a game where the Saints choked on a field goal in Green Bay after having nearly 3:00 to set it up are not a ringing endorsement here. Tua had almost 2 full minutes in that Miami loss too just to get the No. 1 offense in position for a winning field goal. Again, you can’t control the clock like you think you can.

Anyways, it ended up being a bit moot. The Lions almost were too good on offense as they started the drive with 3 consecutive first downs: 15-yard pass, 11-yard run, and a penalty that wiped out a sack. But the Lions didn’t gain another first down and the Bucs got the ball back with 1:59 and 1 timeout left at their own 10 in a 31-23 game.

Baker has done this before, but the Lions aren’t the Raiders in a low-stakes Thursday night game. Just two plays into the drive, he forced a pass over the middle and Derrick Barnes made the pick of his life to send the Lions to the NFC Championship Game. Fron 1 playoff win during 1958-2022 to 2 playoff wins in January 2024. Crazy stuff.

Speaking of crazy, the Bucs still had their final timeout left after the pick. The Lions did them a favor by taking a knee quickly on second down, so after Goff took a knee on third down with 37 seconds left to bring up fourth down, why in the hell would Bowles not call his last timeout with over 30 seconds left?

The ball was at the Tampa 31. It would have been a 49-yard field goal attempt for a so-so kicker. He could have missed or it could have even been blocked, giving Tampa the ball back with over 25 seconds in a one-possession game. To just let the game end was insane, and the NBC broadcast didn’t even acknowledge this happened.

Asked after the game, Bowles tried saying they’d have 12 seconds after the field goal. Not a chance. They likely have over 30 seconds left, which even in an 11-point game would still be a chance even if it’d require one of the craziest comebacks ever. But even if it was 12 seconds, you don’t just give up on the game like that. If this weekend showed anything, you don’t trust a kicker from 49 yards away to make the kick.

The better team, better coach, and better quarterback won in the end. Now let’s see what the Lions have left for a road trip as a big underdog. Watching them win as a home favorite in back-to-back weeks in the playoffs was cool, but they have a much tougher test coming up in San Francisco.

Texans at Ravens: They Had Me the First Half, I’m Not Gonna Lie

Ending with the game that started the weekend, Houston’s 34-10 loss in Baltimore was a sobering reminder of just how hard it is for a rookie quarterback to succeed in the NFL’s postseason against a great defense, especially on the road.

Sure, C.J. Stroud did well at home against Cleveland last week, but the Browns did not travel well defensively this year. Baltimore has been legitimate all year on defense, and it made some history in this game by being able to hold the Texans to just 3 offensive points. The only Houston touchdown was a punt return.

The Texans set a record for worst margin of defeat (24 points) in NFL history for a team that had no turnovers and no sacks in a game.

In fact, the Texans are the first NFL team since 1940 (regular season or postseason) to lose by more than 10 points in a game where they had no offensive touchdowns, no sacks, and no turnovers.

This is a near-impossible combo of stats to pull off in a game, and the Texans only had one missed field goal and one failed fourth down too. The list of teams to have no sacks and no turnovers and only score 10 points (or fewer) is small at just 24 teams in the Super Bowl era. One of those teams was the 2023 Chargers in their 6-0 win over the Patriots this year.

You would have figured Stroud threw a pick parade or took a handful of sacks like he had in Week 1 when these teams played. But it was nothing like that. Just stopped them cold time and time again. Sure, they dropped a pick in this game, but they didn’t even need a turnover to keep them out of the end zone. They shut down the running game completely as Devin Singletary had 9 carries for 22 yards.

But for a half, the Texans were hanging in there with Baltimore. I don’t believe this is a case of Baltimore’s past playoff failures getting in their heads. I think it was more like “we blew off Week 18, we had a bye week, and we’re not as sharp as we need to be” for about a half.

But DeMeco Ryans went against his script and was very aggressive with blitzes, and it is hard to deny it worked for a half. On six drives, they forced the Ravens into a 3-and-out 4 times, gave up a 53-yard field goal to start the game, and only allowed one 76-yard touchdown drive. Lamar Jackson was sacked 3 times in a half that saw him net just 23 passing yards. His damage was on the ground where he had 50 yards.

If the Texans didn’t miss a 47-yard field goal with 32 seconds left in the half, they likely go to the locker room with a 13-10 lead. Not bad for a team with an offense that couldn’t find the end zone, and one that racked up 8 penalties for 50 yards as pre-snap penalties killed the Texans early in this game. That’s a good sign of an inexperienced team that was struggling to communicate on the road.

But the second half was a runaway by the Ravens, who put together 3 straight touchdown drives while the Texans floundered. Just like that, it was 31-10 with 5:00 left and the rest of the game was a formality.

The first drive of the half for each team set the tone for the rest of the game. The Ravens adjusted to Houston’s blitzing, and after Jackson avoided a red-zone interception that was dropped, he took off on a 15-yard quarterback draw for a touchdown. While Stroud had a few impressive throws in the first half, Houston played too scared with him on early downs with ineffective runs and short throws. A screen pass lost 5 yards and short-circuited Houston’s drive in Baltimore territory. They punted and never threatened the rest of the game.

Isaiah Likely caught a 15-yard touchdown, then Jackson ran for another 8-yard score, giving him 2 by air, 2 by ground to tie a playoff record. It was the first time the Ravens scored more than 20 points in a playoff game under him.

The future is bright for Houston, but that team just wasn’t ready to win a game like this.

The Baltimore offense from the second half will need a similar performance against the Chiefs, who look prepared this postseason for these big games. Both teams will provide each other’s biggest challenge this season.

Next week: I think we are getting the best possible championship game matchups this season could produce. Cowboys and Eagles imploded, and we already saw the 49ers crush them. Give Detroit as an underdog a shot. You know they’ll at least be aggressive.

As for the AFC, is there any team in the league that you’d trust more to knock off the No. 1 defense on the road than the Chiefs? If the Ravens want this to go down as a historic defense and team, they must take out Mahomes and the champs. It’s a perfect storyline as this was supposed to be the new AFC rivalry years ago, then Buffalo and Cincinnati substituted instead since the Ravens couldn’t win in the postseason or keep their QB healthy through December. Now we get to see it with the Super Bowl on the line.

Can’t wait for that one and it’s on first.

NFL 2023 Divisional Round Predictions

It’s finally here. My favorite weekend of the NFL year.

But I recall being very disappointed with last year’s divisional round.

  • Patrick Mahomes had the high-ankle sprain against Jacksonville, which took some shine off that game.
  • The Giants didn’t even show up in Philadelphia.
  • The Bengals jumped all over Buffalo in another game that was over (competitively) very fast.
  • Then the Cowboys and 49ers played a decent game that ended 19-12.

It was a major dud compared to two seasons ago (2021 season) when we had the single best divisional round ever.

  • The Bengals survived 9 sacks in Tennessee to upset the No. 1 seed.
  • The 49ers shocked the Packers in Green Bay thanks to special teams.
  • The Rams looked like they sent Tom Brady into retirement in Tampa.
  • The Bills and Chiefs scored 31 points after the 2-minute warning in a 42-36 overtime classic.

We’ll see what we get this time, and two of the games are rematches from 2 years ago. Oddly enough, we almost had 3 rematches if the Rams would have pulled off the only close finish in the wild card round, but they lost 24-23.

That’s one of the things I’m looking at this week. We’ve had 22 straight quarters without a lead change this postseason. We already have 5 wire-to-wire wins (recent record is 8 in 2020) with 7 games to go this postseason. We have the No. 1 seeds nearly favored by 10 points, and even the Lions are a 6.5-point home favorite. But I think there is potential for more drama this weekend.

In 16 of the last 18 seasons, at least one home team lost in the divisional round (exceptions: 2015 and 2018).

This Week’s Articles

NFL Divisional Round Predictions

Let’s start with my chart of stuff I’m betting on this week, which includes most of the picks from the links above.

Yes, I put both BUF and KC in the ML picks because I will certainly be making bets for each scenario. I think it’s as big of a coin flip game as any this weekend. If you want my official pick you just have to scroll a couple centimeters cause I’m giving the final score picks right here.

Texans at Ravens (-9.5)

I certainly don’t think the Ravens have accomplished enough in the playoffs to trust them to take care of business here. But I have my concerns with Houston being down receivers and having an inconsistent defense. The “rookie quarterback on the road against No. 1 defense” is also obviously a huge hurdle to overcome, even if C.J. Stroud is a special case. I think Houston’s best hope is an early turnover or mistake from the Ravens (tipped pick or failed 4th down) and to get up on the scoreboard and let that pressure mount on the top seed. Houston’s lack of turnovers is a real positive in this matchup, because you can’t feed the Ravens short fields and make this easier for them.

Nothing this weekend would really shock me. None of these upsets would be on the level of the 2010 Jets in New England a month after 45-3 happened. This wouldn’t even be the worst loss by a Baltimore team as a No. 1 seed. In fact, that 2019 upset by the Titans is what makes this less of a surprise if it happens. But I think the Ravens have their best scoring playoff game under Lamar and get the win (but not the cover) over an impressive Stroud who will be the overwhelming favorite to repeat in the AFC South next year and be a top MVP candidate.

Final: Ravens 27, Texans 19

Packers at 49ers (-9.5)

Remember when the Packers were the front-running team that you just had to punch in the face early and take control of the game? The 49ers used to do that to them all the time in big games. In a way, that’s still possible in this matchup as Jordan Love is going to face a tougher challenge than he did a week ago in Dallas. But that game was good prep work for this one as the Cowboys and 49ers were both historical teams this year at winning games by big margins and rarely having to play from behind. That’s why I love the idea of Green Bay taking the ball first if they can like they did last week and getting off to that good start and making Brock Purdy play from behind.

But I think with an extra week to prepare and a better coaching staff, the 49ers are going to have a plan and have too much talent for the Packers to overcome this year. But just like with Baltimore, who also rested starters in Week 18 and had a bye week, watch out if there’s that early sign of rust and a mistake that the Packers can capitalize on. Remember, the Ravens and 49ers barely won any close games this year, so if you can challenge them early and make them uncomfortable, all the pressure is on them to win these games. That’s why I have some hope we could see at least one close finish, if not an upset out of these Saturday games.

Final: 49ers 30, Packers 23

Buccaneers at Lions (-6.5)

I don’t take much away from the 20-6 game these teams played in Week 6. The Detroit defense has gotten worse, the Tampa offense has gotten better. I think both teams score at least 20 and we get a nice little aerial show out of Goff and Mayfield. I like Evans and St. Brown to both score. But I like that Goff has a history of stepping up against Bowles’ blitz and carrying the offense in those games. The spread would probably be a little lower if I set the line for this game, but it should be a nice appetizer before Sunday’s main event. I’m just going to trust the Lions at home to get the job done again. A game similar to last week but with more balanced scoring over the two halves.

Final: Lions 30, Buccaneers 24

Chiefs at Bills (-2.5)

I think the top AFC preview, Upset Alert, and Scott’s Seven Pick linked above did my talking for me in great detail about this game already. My preseason pick was the Chiefs settling for the #3 seed because they lost to the #2 seed Bills in December. Then I had the Bills beating #7 Pittsburgh in the wild card, then I had them beating the #3 Chiefs in the divisional round to set up an AFC title game in Baltimore against the #1 seed next week.

Why change the pick now when we’re so close to that all happening? Having said that, I still think you see an upset this weekend, and this is still the game most likely to produce it. The closer we get to kickoff, the more I like the Chiefs’ chances as I think Buffalo’s injuries are relevant not just on defense, but they don’t have Gabe Davis to take some attention away down the field and free up Stefon Diggs, who had his worst game of the season in Arrowhead.

I also think the road game thing is overblown for Mahomes, who has been fantastic on the road in his career and will likely relish this challenge this week. He’s also 7-3 SU and 8-1-1 as an underdog in his career. Yeah, I’m already repeating things I wrote several times this week, so I would highly recommend reading those links above for my full thoughts on this game.

I just think the defenses play well enough to keep the score down (no 42-36 this time), and it’ll come down to who makes the big mistake or the big stop at the end. Just like it has the last 3 times these teams have met. And in the end, I’ve been saying all year how the Chiefs’ mistakes (the league-leading drops, the annoying penalties on the OL and one huge one on Kadarius Toney, the obligatory fumble, etc.) are going to kill them come playoff time when they’re on the road trying to keep up with another top quarterback and they have this WR room holding them back.

So, I stuck with the gut.

Final: Bills 24, Chiefs 21

Enjoy the last big slate (4 windows) of the 2023 season.

NFL Stat Oddity: 2022 Divisional Round

For as incredible as the divisional round was last season with road teams going 3-1 and every game decided on the final play, the 2022 slate was one of the worst in history.

  • Zero lead changes in the second half.
  • Three wire-to-wire wins.
  • Three home favorites won by 7+ points.
  • One game-winning drive that was settled on the first snap of the fourth quarter in a tied game, leading to the only pathetic 4QC attempt of the weekend.
  • A 7-point win marred by a major quarterback injury.
  • Three of the losing teams failed to score more than 12 points, which has not happened in the divisional round since the 2002 season.

I would rank it as the third-worst divisional round since 1970 behind only 1992 and 2000.

In 1992, you had three wins by 21+ points, and the closest game was a forgettable one in San Francisco with the 49ers beating Washington 20-13. Washington (13) scored as many points as the other three losers that weekend combined that’s how bad it was.

2000’s highlight game was that horseshit outcome in Tennessee when the top-seeded Titans choked 24-10 to the Ravens, losing on a blocked field goal return touchdown and Eddie George tipping a pick-six to Ray Lewis.

In the end, 2022 is just copying the same final four as 2021, giving us Bengals-Chiefs in Arrowhead, and the 49ers on the road against the latest NFC flash in the pan who everyone will say can win for years to come when this might legitimately be their best and final shot at a ring.

Does it play out the same way as last year? We’ll see next week, but for now, let’s try to quickly put a bow on this dud of a weekend. I can remember staying up super late last year in finishing the recap of 42-36 and the other games, still riding a sense of awe from my favorite weekend of the NFL year.

But this was not much fun this year, and I guess scoring streaks don’t mean what they used to when the teams in question have a history of coming up short this time of year.

This season in Stat Oddity:

Cowboys at 49ers: Mr. Self Destruct on Repeat All Summer

One team did this:

The other did this:

Pretty obvious which team won, and which team lost again even if you didn’t see the game.

There are other plays I could point to, like two classic 2022 Dallas interceptions thrown by Dak Prescott, or how the defense failed to hang onto multiple Brock Purdy pick opportunities. Tight end Dalton Schultz also made some boneheaded plays at the end of the game as he is no George Kittle, that’s for sure.

But the Cowboys’ destructive ways finally caught up to them even if the 49ers certainly didn’t play their A game. Kicker Brett Maher had another extra point miss, but it was blocked this time. Still, it looked like he was going to miss it if it wasn’t blocked.

That second Prescott interception in the red zone just before halftime was a killer. Instead of Dallas scoring, the 49ers turned that into a field goal and 9-6 lead as both defenses did a lot of good things. The 49ers also caught a break when Tony Pollard suffered a game-ending injury in the first half right before the last pick.

The only points of the third quarter went to Dallas on a 25-yard field goal – we found a distance Maher can still hit from – after the 49ers fumbled a punt return, so that wasn’t really earned by the offense.

Before what became the game-winning drive, the Cowboys had a chance to go for a fourth-and-5 at the San Francisco 40. They took a delay of game penalty and punted. Very conservative decision by Mike McCarthy there that proved costly.

On the second play of the drive, Kittle made that ridiculously athletic catch from above for a 30-yard gain into Dallas territory. Kittle had both 49ers’ 30-yard plays in this game, but that was the big one. Purdy’s only other positive gain on the drive was an 8-yard gain on a little throw to Christian McCaffrey.

The drive could have stalled on a third-down sack, but the Cowboys were penalized for defensive holding, giving the 49ers a new set of downs. McCaffrey walked in for a 2-yard touchdown run on the first play of the fourth quarter to take a 16-9 lead.

The Cowboys ended up settling for a 43-yard field goal after a blown blocking assignment on first down blew up the drive with a 4-yard loss. Maher actually made the kick normally and it was 16-12.

Dan Quinn’s defense did a good job in the game against a team that was scoring well over 30 points per game with Purdy, but you can complain about these back-to-back scoring drives that were both long and impactful in the second half. The 49ers put together another one, taking 7:59 off the clock and adding a field goal, leaving Prescott with 2:59 left to try tying the game at 19 or taking the lead on a two-point conversion.

This was plenty of time, but similar to last year when the Cowboys had a stinker of a drive in a 23-17 game in the wild card round, they quickly folded here too, going three-and-out. Prescott was sacked and the Cowboys had to hurry the punt team to save the two-minute warning.

Remember last year’s craptacular ending with the infamous quarterback draw with no timeouts left? It took some bad game management by the 49ers to get Dallas that opportunity, and something similar would happen here as well. The 49ers came out throwing with 2:05 left, which was perfectly fine given the upcoming clock stoppage for the two-minute warning. But the short throw was carried so well by Kittle for 11 YAC that it was almost a meaningless first down as the clock stopped with Dallas still holding all three timeouts.

I’m not saying it would be easy for Kittle to give up on a play, but a gain of 9 yards would have really been the best thing possible there to burn clock. Two plays later, Elijah Mitchell did something much worse. He got to the outside and ran for a 13-yard gain to get a first down that could have burned most of the clock, but he ran out of bounds instead of sliding down once he got the first.

There would be no third first down gained on the drive. The 49ers punted and the Cowboys were left in the unenviable position of having to drive 94 yards in 45 seconds for a touchdown with no timeouts.

But at least it was a chance thanks to the Mitchell mistake. Prescott nearly pissed it away with a sack for a safety, but Arik Armstead seemed to pull up on the hit, which Prescott absorbed and threw the ball away from.

Schultz caught a couple short ones, though he didn’t get out of bounds properly on one, which led to the clock rolling. Then he casually didn’t drag his second foot down on another play with 6 seconds left, costing the Cowboys 15 yards and an outside shot at a Hail Mary from 61 yards out.

All you could really do was a lateral-filled play at this point, 76 yards away from the end zone. The Cowboys were lining up Ezekiel Elliott at center in a unique formation, so you at least expected something unique they clearly worked on. But after the 49ers took a timeout, the play was ran, Elliott was pancaked, and Dak threw a short pass to a receiver who was immediately tackled for an 8-yard gain. Didn’t even get a lateral off.

What the hell was the point of that?

Oddly enough, you can say the same about every overhyped Dallas Cowboys season since 1996, because once again they are eliminated short of the NFC Championship Game. We will now see a fifth rookie quarterback start a Conference Championship Game since the Cowboys were last in it. Purdy joins Mark Sanchez (2009 Jets) and Joe Flacco (2008 Ravens) as the only three rookies to win multiple playoff games in NFL history.

But Purdy is going to have to be better in Philadelphia next week than he was here against Dallas if he wants to become the first rookie quarterback to start a Super Bowl.

As for the Cowboys, I’m not on the fire McCarthy and trade Dak bandwagon, but I do think there is a serious limitation on how far you can expect this team to go this time of year with them leading the way. I just struggle to see the better alternatives in 2023, because last I checked, McCarthy’s one Super Bowl win is still a year fresher than Sean Payton’s.

This league is hard, and yet the 49ers are going to their sixth NFC title game in the last 12 years with two head coaches and four different starting quarterbacks.

Bengals at Bills: Buffalo’s Emotional Season Meets Flat Finale

I am not very keen on calling this a big upset. I thought the opening 4.5-point spread for the Bills was too high, and I thought the 5.5 and 6-point spreads for the weekend were even more ridiculous. I was consistent from Week 17 to this week in choosing Buffalo to win by a field goal (27-24) in a close game like how every Cincinnati playoff game is close the last two years.

But this was shockingly one sided, and not in any way that made any sense going into this matchup:

  • For all the talk about Buffalo’s turnovers this year, the game’s only turnover was a meaningless Josh Allen interception with 1:02 left to play and the Bills down 27-10.
  • The game’s only turnover on downs, often a hidden turnover in the stat sheet, was halfway through the fourth quarter, and again, Buffalo was already down 27-10.
  • The Bills had just eight offensive drives for the game, and two of them were with a 27-10 deficit in the fourth quarter.
  • The Bengals were down three starting offensive linemen coming in, yet it was the Bills who looked like the team facing that dilemma.
  • While each quarterback was sacked once, Joe Burrow was rarely pressured while Allen was frequently pressured.
  • In the regular season, Buffalo was No. 7 in rushing yards and No. 2 in yards per carry. Cincinnati was No. 29 in both categories.
  • But the Bengals rushed for 172 yards on 5.1 yards per carry in their second-biggest rushing game of the year, and the Bills had 63 yards on 3.3 yards per carry, their fewest rushing yards in a game since 32 yards in the 2020 AFC divisional round vs. Baltimore.
  • Buffalo averaged 28.4 points per game in the regular season, ranked No. 2 in the league, but the 10 points were the fewest scored since last year’s 14-10 loss vs. Patriots in extreme wind.
  • The Bengals scored a touchdown on the opening drive and led wire-to-wire in the snow, once considered to be a home-field advantage for the Bills.

While there was more than an inch of snow as the weather people incorrectly predicted this week, remember when the Bills had a home-field advantage in the elements? That seems to be gone with this offense. The defense also looked incredibly soft and unable to put together a pass rush to take advantage of Cincinnati’s line, which played far better than Buffalo’s.

The Bills are the first top-five scoring offense to be held to 10 points in a home playoff loss since the 2005 Giants lost 23-0 to the Panthers in the NFC wild card.

That was Eli Manning’s first playoff start under Tom Coughlin. The Bills are supposed to be an experienced playoff team, and they were the Super Bowl favorites for most of this year.

The 2002 Eagles also lost 27-10 at home to the 2002 Buccaneers, an all-time elite defense. That’s one of the closest examples to this game, but at least those teams had some history. This was the first Burrow vs. Allen matchup, and they are scheduled to meet next regular season in Cincinnati. If this is how the Bills are going to handle one of their main rivals in the AFC, then the long wait for a Super Bowl may have just gotten a little longer.

This was really bad for the Bills, who looked incapable of forcing the Bengals into a negative play on their first two drives as Cincy quickly led 14-0. In between, Allen was pressured on a third down, missed Stefon Diggs on a deep ball, and the offense went three-and-out.

Long drives defined the second quarter with the Bills finally getting on the board with an Allen touchdown run, but the Bengals nearly matched it on their own lengthy drive. A Ja’Marr Chase touchdown was overturned after replay showed him losing control of the ball out of bounds. Had he caught that in the middle of the field, it would have stood as a completion. But we still have difficult rules in place for touchdowns, and I’m not sure how I feel about that philosophically. Should touchdowns be held to a higher standard, or should the final yard be no different from the rest? Either way, I think they got the call right this time, and that cost the Bengals an extra 4 points.

But the Bills could not capitalize on that break. Allen threw three straight incompletions from the Cincinnati 41 and the Bills punted on their final drive of the half. The Bills started the third quarter with another long drive that consumed half the quarter, but they again stalled in the red zone and had to settle for a field goal and 17-10 lead.

That sequence really did the Bills in. They had to do better than 3 points on two drives that took up so much time. There was no sense of what the game plan was for the Bills outside of hoping Allen would throw some lasers and run through some people. He led the team in rushing with 26 yards as the two backs who were so good late in the year had 11 carries for 37 yards. Seven receivers had multiple catches, but Stefon Diggs (4-of-10 for 35 yards) and Gabe Davis (2-of-4 for 34 yards) were quiet.

Meanwhile, the Bengals converted a huge third-and-10 after the Bills lost all sight of tight end Hayden Hurst. That led to another touchdown, a 1-yard run by Joe Mixon to make it 24-10.

The Bills quickly went three-and-out and punted on a fourth-and-2 from their own 20. They’d never see the ball again without facing a three-score deficit.

Incredibly, this was the deficit for Buffalo at the start of its eight drives:

  • -7 (three-and-out)
  • -14 (three-and-out)
  • -14 (touchdown)
  • -10 (punt)
  • -10 (field goal)
  • -14 (three-and-out)
  • -17 (turnover on downs)
  • -17 (interception)

The Bills trailed by double digits on their final seven drives. In the first 17 games this season, the Bills had five drives where they trailed by double digits, and they were all in the Baltimore game where they came back from 20-3 down to win.

There would be no comeback this time. Only a massive letdown, the biggest one yet for Buffalo in this era. The Bengals drove for a field goal early in the fourth quarter to take a 27-10 lead. The Bills had a chance to kick a late field goal in a three-score game, but what good would that really do with half a quarter left against a team you cannot stop? Maybe you can get away with kicking there against the Texans, but it made sense to go for it. Allen did not find anyone open, and his desperation pass fell incomplete.

Game all but over there. The Bengals burned five more minutes and Allen added the irrelevant pick after the Bills were thoroughly dominated without any turnovers.

It was such a flat ending to one emotional rollercoaster of a season. You have to admit, the America’s Game for this team would have been quite the watch if they won it all.

  • Opening night destruction of the defending champion Rams
  • Melting down in Miami before coming back from 20-3 to beat the Ravens
  • Allen’s monster passing day vs. Steelers in Kenny Pickett’s first start, a 38-3 rout
  • The game-winning drive in Week 6’s showdown in Kansas City
  • Allen’s elbow injury at the end of the Jets game
  • The insane fumble and everything else that happened in the Minnesota overtime loss
  • The Cleveland game getting moved to Detroit after six feet of snow hit Buffalo
  • Von Miller’s torn ACL on Thanksgiving and Allen’s frozen rope to Diggs for the game-winning drive
  • The game-winning drive in the snow against Miami on a Saturday night
  • The Damar Hamlin cardiac arrest that stunned the sports world in Cincinnati, the first game cancelled for non-labor reasons since 1935
  • Nyheim Hines returning the opening kickoff for a touchdown in the next game against New England; one of two returns for him that day in eliminating the Patriots
  • A wild 34-31 win over the Dolphins in the wild card

With the break of getting this game in Buffalo instead of a neutral field, and the ankle injury to Patrick Mahomes on Saturday, this just seemed like a team of destiny this year with one hell of a championship story to tell.

Now, tale as old as time, it’s just a 57th-straight Buffalo season that will end without winning the Super Bowl. In some ways, this ending is much worse than the 13 seconds in Kansas City last year. At least that team had some fight. This team looked like a soft dome team not ready for the weather, which is an insane thing to say about a Buffalo team, but that’s where they are now.

I prefaced this season talking about The Five-Year Rule for both the Bills and Ravens. No team has ever won its first championship by starting the same quarterback for the same head coach for more than five seasons.

In picking Buffalo to win the Super Bowl, I had them beating Baltimore and Lamar Jackson in the AFC Championship Game next week. Now, the Bengals eliminated both and it’ll either be another Kansas City or Cincinnati Super Bowl.

The five-year window has closed on the pairings of Sean McDermott/Allen and John Harbaugh/Jackson. It’s not looking good for their futures together. Getting into battles with Mahomes and the Chiefs is one thing, but now that you’ve let Cincinnati officially move past you in the AFC too, it may take significant changes for these teams to get over the hump.

But with no one in the AFC seemingly able to stop this Cincinnati team, their confidence is at an all-time high. Even if you’re a trash corner like Eli Apple, it is hard not to be this cocky after a 27-10 win in Buffalo.

Who dey think gonna beat them Bengals? Might have to be an NFC team with a great pass rush again. At the very least, I’m happy to see there will not be a neutral-field conference championship game. I think that would be a terrible move for the league to try in the future.

Jaguars at Chiefs: Quick, Break the Henne Emergency Glass

We’ll see if Patrick Mahomes can make it 3-for-3 in appearing in the Super Bowl after narrowly avoiding a season-ending injury. He did it in 2019 when he dislocated his kneecap in Denver and only missed two full games. He did it in 2020 when he tweaked a nerve during the third quarter of the divisional round against Cleveland, leaving the game as Chad Henne was able to come off the bench and direct a 22-17 win before Mahomes returned for the AFC Championship Game a week later.

But this is not a good time for Mahomes to suffer a high-ankle sprain with the Bengals coming to town next week. We’ve already seen the Chiefs go 0-3 with a healthy Mahomes against that team. Now his athleticism will no doubt be compromised, and that could be a big problem as this game on Saturday showed.

It’s a shame too because Mahomes came out firing with his A+ game against Jacksonville. That opening 83-yard touchdown drive was perfection as the Jacksonville defense had the right approach many times, but he continued to find different throwing angles and showed off the full extent of his abilities.

After Jacksonville matched the touchdown set up by a long kick return for a short field, it looked like we might get a legit shootout. But on the second Kansas City possession, the ankle injury happened to Mahomes:

Clearly hobbled, Mahomes stayed in the game, but I thought it was negligent to put him back in the game a la Robert Griffin II a decade ago. Then to call a stretch run play on the first snap since the injury? Even dumber. Mahomes completed his first two passes with the injury, but they were both short, and his last throw was an ugly one, leading to a field goal.

Thankfully, the team did take him out and he went to the locker room for an x-ray and treatment. It was a tough spot for Chad Henne to enter the game at his own 2-yard line, but he is a veteran who has been in the offense for years. He may not have did anything individually spectacular on the drive, but he did exactly what you could ask of a veteran backup: make smart plays and protect the ball. Henne almost had a pick on an early throw, but it was clearly tipped at the line and you could see he had the right decision. Would have been a bad luck pick, but the drive continued, and Isiah Pacheco helped out with a 39-yard run to eat up nearly half the field.

But Henne had a 4-of-7 success rate on the drive, converted a pair of third downs, and he finished it off with a 1-yard touchdown pass to Travis Kelce, who looked unstoppable in Saturday’s role of eating up the Jaguars on option routes and just sitting in the open area underneath. He’d finished with 14 catches for 98 yards and two touchdowns.

Imagine Henne leading a 98-yard touchdown drive in a playoff game before Mahomes. Besides taking a knee to take the game to half with the Chiefs up 17-10, that one 98-yard touchdown drive was all Henne had to do in this game, but what a great job from the backup quarterback.

Mahomes returned for the second half after what had to be one hell of a drug cocktail. I did not think we’d see him again with that shot of him on the sideline cheering Henne’s drive on, and with the Chiefs leading. But with the Jaguars only down a score and some likely begging to play from the league’s MVP, Mahomes was back in there.

That first drive did not look good, and the second would fail too after a third-and-1 run came up short with the direct snap to Noah Gray. But the Jaguars were failing to threaten on offense with far too many screens and passes behind the line of scrimmage from Trevor Lawrence.

Mahomes hit Gray for a 27-yard gain, his only 20-yard completion of the game. That set up a field goal and 20-10 lead going into the fourth, but the Jaguars finally put together a drive again and scored a touchdown to make it 20-17 with 11:49 left.

Could the Jags really come back from a double-digit deficit in the fourth quarter of back-to-back playoff games? But Mahomes would do his best work since the opening drive and complete four passes for 48 yards, including a clutch 6-yard touchdown to Marquez Valdes-Scantling. He’s the best quarterback at turning a one-score lead into a two-score lead in the fourth quarter, and that drive just grows the legend.

But could the defense close out the last seven minutes? Lawrence finally started using his legs and had a great 12-yard run on a third-and-10 to set up first-and-goal in a hurry. But while Jamal Agnew had some great returns to help his team out, he cost them with a big fumble with 5:29 left. Just lost the ball at the 3-yard line.

But the Chiefs did go three-and-out after the second run failure on third-and-1 of the game. Figures, Mahomes puts up 20 points on eight drives with one leg on the last seven, and it’s still two third-and-1 run stops that did the most damage to this offense.

However, any hope for Jacksonville was quickly lost after Lawrence panicked under pressure and threw up an interception to rookie Jaylen Watson, the seventh-round pick who shined in Week 2 with the huge pick-six against the Chargers.

The Chiefs burned the clock to 1:04 left, then Jacksonville could only get a field goal before failing on an onside kick to end it at 27-20. The Jaguars (+9.5) still covered, moving head coach Doug Pederson to 7-0 ATS and 5-2 SU as a playoff underdog, which are fantastic records. But even with the Mahomes injury, the Jaguars were unable to capitalize on offense early, and the two big turnovers late did them in.

I would be careful about penciling in the Jaguars for many more of these games going forward. Look what was once said about Andrew Luck and the Colts or Deshaun Watson and the Texans. Those franchise basically imploded after losing to the Chiefs in the divisional round in 2018 and 2019. But it was a successful season for the Jaguars, and they look to be moving in the right direction.

But frankly, playing AFC South teams like this in the second round is how the Chiefs have become just the third team after the 1973-77 Raiders and 2011-18 Patriots to play in at least five straight Conference Championship Games.

Even Brady and the Patriots weren’t doing this in the 2000s AFC when the conference was deeper. They started doing it in 2011 when they drew some of the weakest teams to ever advance in the tournament such as the 2011 Broncos (Tebow), 2013 Colts (who came back from 38-10 vs. Reid’s Chiefs), 2016 Texans (beat Connor Cook), and 2017 Titans (who came back from 21-3 vs. Reid’s Chiefs). Throw in Reid and Pederson losing in New England with the 2015 Chiefs, and you can say the Chiefs had a lot to do with New England’s streak still being the record.

So, here we go again with the Chiefs hosting the AFC Championship Game for the fifth year in a row. Not looking forward to Mahomes’ ankle talk all week, but it is the huge story in the AFC.

But Saturday’s win is a data point for “he could beat that team with one leg tied behind his back.”

Giants at Eagles: Giant Ass Kicking

It has been some time since we’ve seen this kind of early knockout and ass kicking in the playoffs. There was no letdown on Philadelphia’s part after the bye week. The Eagles led 28-0 at halftime and won 38-7 to complete the three-game sweep of the rival Giants, who were just no match for the top seed this year.

The 2019 Packers were down 27-0 at halftime against the 49ers in the NFC Championship Game before losing 37-20, so at least they had a little fight after the break. The last time a team was getting shutout at half by 28-plus points in a playoff game was when the 2015 Panthers went up 31-0 on the Seahawks in the divisional round. Seattle got it to 31-24 late but could not recover an onside kick.

But this is just the sixth time in playoff history where a team was shutout by 28-plus points at halftime.

Never good to be in the company of the 73-0 game for the loser. The Giants were just never in this one. They gave up a 40-yard bomb on the second play of the game, Dallas Goedert made an incredible one-handed catch to get a 16-yard touchdown, and once Daniel Jones took a bad sack on a fourth-and-8 in response, it was already a dangerous time for the Giants.

The Eagles took the short field for another 52-yard touchdown drive, and then Jones made his worst throw of the night for a pick by James Bradberry. Boston Scott later pounded in his 11th touchdown against the Giants, and the Giant Killer is now 9-for-9 at scoring touchdowns in games against the Giants. Did he grow up a Patriots fan or something? He was born in Louisiana and went to school there. I’m not sure why he shits all over the Giants every time, but he did it again in the playoffs to secure his legacy against them.

Throw in the obligatory Hurts touchdown run before halftime and it was 28-0. Between the early Scott score and Hurts easily running that one in, the Eagles looked like they were toying with the Giants.

Things did not go much better in the second half. One 39-yard run by Saquon Barkley helped the Giants to their only touchdown drive in the game to make it 28-7. But the moment worthy of criticism came on their next possession, which extended into the fourth quarter.

Facing a fourth-and-6 at their own 42, the Giants punted with 13:12 left. You’re down three touchdowns, you’re almost certainly going to lose barring a miracle. Why are you punting, Brian Daboll? If you go for it, you might convert and keep this improbable rally going. If you don’t get it, there’s still some value here in that the drive should not consume much time with the Eagles on the edges of field-goal range. You could even push them back a little and force a punt.

But the Giants punted, and the Eagles burned almost eight minutes on a run-heavy drive before kicking a field goal to make it 31-7 with 5:16 left. So much good punting did there. But the Giants had a terrible run defense this year, and it was exposed in this game and especially on that drive when Kenneth Gainwell ripped off 12 yards with a great effort on a third-and-12.

But even if they didn’t add the three points on that drive, it took up way too much time. On their next drive, Jones started getting into sack trouble against the defense that had 70 sacks this year. Still, he made a fourth-and-16 conversion look so casual with a 17-yard completion, his longest completion of the game to a non-running back. Gee, maybe that fourth-and-6 earlier would have been worth the try?

The drive eventually stalled and was turned over on downs. The Eagles padded the score with Gainwell taking off for a 35-yard touchdown run on a third-and-9 that he didn’t need with 1:51 left. The Eagles finished with 268 rushing yards and Hurts only needed to throw for 154 in his first playoff win. Jones then completed a few hospital balls to his receivers, because I guess 38-7 in the last two minutes is the right time to start getting aggressive as a passer. Then it was finally over.

I think the frustrating thing about the Giants is that they never seemed to have any plan for the game. Maybe it was blown up by the quick 14-0 hole, and maybe they were shell shocked by the fourth-down sack and the interception. But I have no idea if they wanted to establish Saquon, make use of Jones’ legs, try to use the slot receivers to stay away from the outside corners, or just chuck it deep and hope for pass interference.

They did none of those things. Barkley had 8 carries for 22 yards when you set aside his 39-yard burst in a 28-0 hole. Jones lost more yards on five sacks (26) than he had on six runs (24 yards). Richie James had 10 targets compared to 17 for the rest of the team, and he was the only receiver with more than 21 receiving yards. The game only had six penalties for 30 yards between the two teams, and it was free of controversy because the Giants were knocked out almost immediately.

It is unusual to see a Giants playoff run that doesn’t end one-or-done or in the Super Bowl like 12 of their last 14 trips have.

This game had the biggest talent disparity this weekend and the results backed that up. Now we’ll see if the Eagles can win against a legitimate elite team for the first time in the Hurts era.

NFL 2022 Divisional Round Predictions

My favorite weekend of the NFL year is here. This historically has been the toughest week for road teams to win, because you used to have a pair of teams in each conference coming off a first-round bye. So when those upsets did happen, they are instantly memorable, and they almost can hurt worse than getting blown out in the Super Bowl does.

But with only one bye per conference now, maybe things aren’t what they used to be. Last season, the road teams were 13 seconds away from going 4-0 with each win by 3 points. The Bills screwed that up, but it led to a change in playoff overtime rules, and it was the best second round of all time. Hard to top that this weekend.

I think the schedule is amusing this weekend as you have both No. 1 seeds playing both longshots on Saturday. Not much is expected of the Jaguars and Giants, but you never known. Crazier things have happened in both franchise’s histories. The Jaguars winning would be akin to the 1996 team upsetting Denver in the divisional round. We know all about the Giants shocking the 2007 Cowboys (top seed) and 2011 Packers (15-1 team) in this round.

Then you get the two marquee matchups on Sunday. We finally get to see Bills vs. Bengals, and Cowboys-49ers is a classic NFC playoff matchup and a rematch from last year’s wild card round.

If I had to pick a Super Bowl matchup today, I’d probably still go Bills vs. 49ers.

But a team that turns the ball over that much and a team with a rookie quarterback are hard to trust this time of year. That’s just part of what makes this weekend so interesting.

If you are holding out hope for a Super Bowl rematch of Bills vs. Cowboys, here is an interesting stat I came across in research for this week. The Cowboys recently had a 9-game streak snapped of scoring at least 27 points. The Bills also did it earlier this year, though most of the games were carried over from 2021.

But such a streak has only lasted nine games 14 times in NFL history. If you look at the previous 12 cases before the Bills and Cowboys, all 12 of those teams advanced to at least a conference championship game in one of the seasons the streak took place. All but the 2018 Chiefs reached the Super Bowl or league championship game, and five of them won a ring.

Regardless of this table, I think Bills vs. Cowboys is very realistic if both can win this weekend.

Some articles I did this week:

NFL Divisional Round Predictions

After going over these games so many times this week, I am beyond ready to get this weekend going. Here are my final score predictions for each game:

Jacksonville Jaguars at Kansas City Chiefs (-9.5 at Bovada)

The Chiefs should win, but you have to be impressed with Doug Pederson starting his career 6-0 ATS as a playoff underdog. Even better is the 5-1 SU record. The Chiefs are not your typical 14-win team by any means. They join the 2001 Rams as the only 14-win teams with a minus-3 turnover differential. They’re also 32nd in touchdown passes allowed and 31st in red zone touchdown percentage on defense. But these kind of stats would mean more against a Cincinnati or Buffalo team that has had their number since last year.

I don’t think the Jaguars are ready for this yet, but I do think they have learned how to battle back and will make a game of it, even if it means dialing up trick plays or doing a surprise onside kick. Anything to steal a possession. I also have my eye on kicker Harrison Butker this postseason. Everyone is worried about Brett Maher in Dallas, but Butker could be a weak link for the Chiefs.

Also, can we get back to Travis Kelce scoring touchdowns and Jerick McKinnon not catching one every single week?

Final: Chiefs 30, Jaguars 23

New York Giants at Philadelphia Eagles (-7.5 at Bovada)

I think between the NFC preview and upset articles linked above, I laid out a good case for why the Eagles peaked too early and have some strong warning signs for a No. 1 seed that loses the first playoff game at home. We’re still waiting for a signature win in the Jalen Hurts era, and while this will count, it’ll be interesting to see what happens next week no matter who wins the other game.

But I can’t go as far as to pick the Giants to win outright, because I do think the crap quality of the Vikings and Colts defense has played a big factor in the offensive success in recent weeks. The Eagles had 70 sacks this year and can defend these receivers with their healthy corners. A.J. Brown usually shows up for big games. Boston Scott is the Giant Killer as he is a ridiculous 8-for-8 at scoring touchdowns in games against them.

If the Giants had one of their better defensive units like 2016, I could totally buy this upset. But I don’t see it happening this week, but once again, I think it’s going to be close and the Giants are going to push them and leave them with little momentum going into next week.

Final: Eagles 24, Giants 17

Cincinnati Bengals vs. Buffalo Bills (-5.5)

In Week 17, I was on board with the Bills winning 27-24, and I see no reason to change my pick. I think the spread is a little high here, I think the Bengals have a right to be pissed this isn’t played on a neutral field as they were denied the chance to finish a game they led 7-3 and were driving for more that could have given them the No. 2 seed over Buffalo, and I think the Bills miss Von Miller in this matchup.

Imagine a talent like Von in this game against the team with three injured linemen. But I don’t think it’s going to be a Chiefs-Bucs Super Bowl type day for the Bengals. They’ll adjust and they’ll just have to compensate for sacks/pressures by getting turnovers from a Buffalo team that has 30 giveaways in 17 games, one of the worst teams this year at protecting the ball.

But I expect both quarterbacks to play well, and I am sticking to my preseason pick and Week 17 pick of Buffalo.

Final: Bills 27, Bengals 24

Dallas Cowboys vs. San Francisco 49ers (-3.5)

You see the Dallas upset link above, and the other upset article picks this game too, so not much surprise where I’m going with this one.

I wrote the Cowboys off for months, and some of it was just doing my part to reverse jinx Brady and the Buccaneers. Some of it was legitimate belief though that this team is too self destructive to win a playoff game. Now here I am backing the Cowboys on the road against a team that’s won 11 in a row with the top defense.

But I also think there’s a real paper tiger element to the 49ers’ season, and I can’t just ignore that they had the weakest schedule, went 0-1 against the only elite team they played, and Dallas is 3-1 against the other 12+ win teams this year. The Cowboys have an elite offense and defense with the most takeaways. The 49ers are 0-4 with multiple giveaways and 14-0 when they don’t do that this year. Pretty cut and dry.

If the Cowboys can make Brady look like he’s 50, then they need to make Brock Purdy look like the last pick in the draft and pick off some of these bad throws he got away with last week. And for Dak Prescott, it might be now or never. Go get this one.

And really, the 49ers almost blew a 23-7 fourth-quarter lead last year to Dallas in the wild card round. A game with Kyle Shanahan, Mike McCarthy, and Dan Quinn should have plenty of shenanigans going down. Hell, it’d be the story of the week if Brett Maher wins it on a long field goal. But I’d have multiple two-point conversion plays prepared for this one just in case.

I just wouldn’t have any QB draw in the god damn playbook this time.

Final: Cowboys 26, 49ers 23

Yes, I went against the grain and picked the underdog to cover in all four games. That hasn’t happened in the divisional round since the 2006 season, or that weekend where the Chargers intercepted Tom Brady on fourth down and fumbled the ball back to him. But it has happened before, and after a competitive regular season, mostly competitive wild card round, why not expect more of the same this weekend?

The only real gaps between these teams is that the Jaguars and Giants stick out like sore thumbs. But when it comes to the other six, you are likely just looking at who is going to make the big mistake, and who is going to make the play that lives in infamy for the highlight reels. It is going to take two or three coin-flip wins to get this championship. No one is good enough to run away with it anymore.

Enjoy the games.

NFL Stat Oddity: Divisional Round

The last five rounds of the NFL playoffs had been historically low on drama, so you might say regression hit hard with the best divisional round weekend in history. All four games were decided by a walk-off score, a grand total of 15 points separating the teams, and three road underdogs won.

We were 13 seconds away from the first perfect road sweep in the divisional round. It was however the first time ever that both No. 1 seeds (Titans and Packers) lost on the same day. We could even have watched the last games in the Hall of Fame careers of Aaron Rodgers and Tom Brady. That expected NFC Championship Game rematch between the two? Forget about it. We’re getting 49ers-Rams III.

Cincinnati’s halftime lead in Tennessee before winning 19-16 made it a 26-0 run for the team leading at halftime in the playoffs. But the 49ers-Packers ended that historic streak. A blocked punt return touchdown by the 49ers also helped lead to the first fourth-quarter lead change in the playoffs since Super Bowl LIV. We tied the all-time streak at 20 playoff games (set in 1935-50) without a fourth-quarter lead change, but that is thankfully over.

But even if last-second field goals in tied games were still not enough drama for you, the Bills and Chiefs made sure we got all the lead changes you could imagine. Try four after the two-minute warning alone, or one too many if you’re a Buffalo fan.  

We start with one of the absolute best playoff games ever played.

This season in Stat Oddity:

Bills at Chiefs: The Greatest Divisional Round Game Ever

If the Chiefs go on to win the Super Bowl, we’ll be talking about this one on our deathbeds. Rarely does a heavyweight matchup like this one deliver, but this game blew away all expectations.

There were 31 points scored AFTER the two-minute warning. If that’s not the NFL record, then I don’t know what is. The 2013 Vikings-Ravens scored 36 points in the final 2:04, but only 28 came after the two-minute warning.

Even if it wasn’t a significant playoff game with an incredible ending, this was one of the best-played games ever. It is the first game in NFL history where both teams scored 30 points, had no turnovers, and combined for fewer than five penalties. You want clean, efficient play with two incredibly athletic quarterbacks? This was the game to watch.

Josh Allen led the Bills to five touchdowns on nine drives. You could say he’s slipping after going 7-for-7 a week ago, but he was great in this game. Patrick Mahomes led the Chiefs to five touchdowns, three field goals, one missed field goal, and two punts on their 11 drives.

You know you’re dealing with an incredible game when the biggest complaint is the overtime system not letting the other team answer on offense. No officiating controversy. No bogus play to decide it. Just one score after another.

Right from the start you could see this game was going to be special with the teams exchanging touchdowns in a fast-moving first quarter. Mahomes had the toe injury last postseason, so we did not see him run as effectively as he did in the previous postseason. He does seem to have some Colin Kaepernick in him where he “lets it all hang out” in these playoff games. In this game, Mahomes had 49 yards rushing on the first drive alone, scored a touchdown, and finished with a career-high 69 rushing yards to lead the Chiefs.

I said in my preview that the Bills had the No. 1 scoring defense and the Chiefs were No. 1 since Week 6, but both used weak schedules to boost those stats. Against top offenses, they were not reliable this year. Sure enough, the two offenses that were so efficient a week ago had their way with these defenses this night. But for anyone thinking a 42-36 shootout had no defense, that would gloss over all the incredible plays Allen and Mahomes made to avoid sacks. Each took two sacks, but the number would have been so much higher with lesser quarterbacks. Mahomes especially had better pocket movement and sack avoidance in this game than I’ve ever seen from him. Buffalo had to be sick at how often he got away, but tackling was an issue on other plays too, including a 25-yard touchdown run by Mecole Hardman that looked like it would gain a couple yards at best.

Before the 31-point bonanza at the end, this looked like a game where the Chiefs were going to be kicking themselves for a bad kicking night by Harrison Butker (missed a field goal before halftime and an extra point) and a terrible red-zone call in the fourth quarter. Up 23-21, the Chiefs had a chance to go up two scores, but decided to run an option play with Blake Bell pitching to Jerick McKinnon on third-and-1 for a 3-yard loss. WTF was that? Did they not learn from the Wildcat disaster a week ago? Don’t take the ball out of Mahomes’ hands. That’s way too cute on a pivotal play.

Down 26-21, the stage was set for Allen. I predicted he would lead the first game-winning drive with a touchdown for the Bills (0-5 at them in 2021) in this game. I didn’t think he’d almost use the final nine minutes to do it, but the Chiefs could not stop his runs as he had 68 yards on 11 carries. None were bigger than his 6-yard scramble on a fourth-and-4 with 2:48 left. It looked like the Chiefs had him dead to rights on the play, but he escaped a la Steve McNair and picked it up.

After a bad completion to Devin Singletary lost 7 yards when Allen should have thrown the ball at his feet, the Bills faced a 4th-and-13. Allen found Gabriel Davis wide open for 27 yards in the end zone. Davis was the target on Allen’s 75-yard rocket in the third quarter as well. Stefon Diggs had a shockingly quiet night (three catches for 7 yards), but he came through on the receiving end of a two-point conversion after Allen extended the play.

Down 29-26, you knew Mahomes would answer, but could you trust Butker on this night? Didn’t have to. The connection to Tyreek Hill struck playoff gold again over the middle and Hill turned on the jets for a 64-yard touchdown. But did he leave too much time? The Bills had 1:02 and all three timeouts, an eternity in this game. Davis continued to deliver and was the open target again on a 19-yard touchdown, his fourth of the game, a playoff record. The Chiefs were badly missing safety Tyrann Mathieu, who left early with a concussion.

The Butker misses and the cutesy play call were almost forgotten at this point, but I knew I’d be talking about them in recapping this loss for the Chiefs. It’d be the fourth blown fourth-quarter lead for the defense this year. But as long as you have 13 seconds, your timeouts, and Mahomes, you still have a chance in a 36-33 game.

This was going to be tough, but the Bills could not have played it any worse on three straight plays. First, why a touchback? Kick it short and make them burn a few seconds. Every second is crucial. Then the defense was way too soft as the Chiefs picked up 19 yards to Hill in five seconds before using the first timeout. Still difficult, but not impossible. Then the back-breaker: Kelce left way too open for a 25-yard gain right down the seam. Timeout at three seconds and Butker came on to deliver from 49 yards out. Overtime. That’s 44 yards in 10 seconds. That can’t happen.

There have been some miraculous touchdown drives in less time thanks to a Hail Mary or lateral-filled play. But I have the Chiefs as the only offense since 1981 to drive 40-plus yards for a field goal in the last 15 seconds to tie or win a game.

You hate to see it come down to a coin flip, but if ever there was a game where that was inevitable, it was this one. The Chiefs, like they did in Los Angeles against the Chargers in my regular season Game of the Year 2021, won the coin toss and took the ball right down the field for a touchdown. Mahomes threw a perfect ball to Kelce for an 8-yard touchdown to end it.

Since 2011, the team receiving first in overtime in the playoffs is 10-1 and seven games ended on a first-drive touchdown. Only the 2018 Saints lost to the Rams in a game any rational person would tell you had no business going to overtime. But this tells me the system is not working, and for years I have said we need a system that doesn’t have to be as corny as college, but it has to be better for the postseason than this. It’s a damn shame we didn’t get to see Allen answer after his second go-ahead touchdown pass to Davis after the two-minute warning. The Chiefs ended up with 11 drives to nine for the Bills in this game.

I guess the Bills just needed to be closer to perfect like they were a week ago, but at the same time, don’t blow it with 13 seconds or you leave yourself open to exactly this type of ending. But what a game these teams put on. Allen has earned a lot of respect from me with his playoff run, and really going back to that near-comeback attempt in Tampa Bay and his great game in New England. He is a legitimate stud, but Mahomes is still just better.

The best.

Is it the greatest divisional round game ever? Yes, and I don’t answer that as a prisoner of the moment. I hyped this game up as having massive potential for only being a second-round matchup. If I was going full wrestling writer here and creating a system to judge the best games, I would look at things like relevancy/importance, past history/rivalry, roster talent, quarterback performance, game script/drama/lead changes, highlight plays/visual imprints it left, and how it ended.

This one is going to score higher than anything using such criteria. It was a rematch of last year’s AFC Championship Game, so there was history and relevance. Both teams have major Super Bowl aspirations again, and after the three upsets preceding it, this arguably was this year’s Super Bowl. Then after the way the quarterbacks performed, the Gabriel Davis record-setting performance, the 31 points scored after the two-minute warning, the 13-second game-tying drive, a game with no turnovers and four penalties, a walk-off touchdown to a Hall of Fame tight end in overtime – the whole thing was just incredible football.

In the divisional round, you have a lot of games famous for one play or drive in particular:

  • The Immaculate Reception
  • The Sea of Hands
  • Ghost to the Post
  • Red-Right 88
  • Danny White to Drew Pearson in Atlanta (1980)
  • John Elway’s bomb against the 1991 Oilers.
  • The Tuck Rule (two plays, counting Adam Vinatieri’s field goal).
  • Fourth-and-26.
  • Brady having his fourth-down interception fumbled back to him in San Diego (2006).
  • San Diego backup QB Billy Volek’s game-winning drive in Indy (2007).
  • Antonio Brown’s coming out party on third-and-19 against the 2010 Ravens.
  • Alex Smith to Vernon Davis against the 2011 Saints.
  • Joe Flacco to Jacoby Jones via Rahim Moore in Denver (2012).
  • Dez Caught It (2014)
  • Aaron Rodgers to Jeff Janis twice, but Larry Fitzgerald in OT (2015)
  • Rodgers to Jared Cook in Dallas (2016)
  • The Minneapolis Miracle to Stefon Diggs (2017)

A lot of great moments, and some were even great games before that moment. But I would still put this game ahead of them all, as well as any other overtime game like 1971 Chiefs-Dolphins (longest game but forgettable), 2003 Panthers-Rams (Steve Smith in double overtime), or a 2002 Steelers-Titans shootout involving Tommy Maddox (and kicker/actor Joe Nedney).

When you get to the cream of the crop in the divisional round, I think you’re talking about 2005 Steelers at Colts. It was the first time a No. 6 seed beat the No. 1 seed, and it was one of the most dramatic fourth quarters in playoff history with the Colts trying to rally from a 21-3 deficit. Jerome Bettis’ fumble, Nick Harper’s recovery, and Ben Roethlisberger’s tackle set up a crushing missed field goal by Mike Vanderjagt, creating a montage of “he missed it” quips from Bettis, Bill Cowher, Tony Dungy, and Peyton Manning. The Steelers went on to win the Super Bowl that year. Harper being stabbed by his wife the night before the game just adds to the lore. But it loses points for not having any lead changes and coming down to that liquored-up kicker you knew would choke.

The other game that will usually come up in the best divisional round game talk is The Epic in Miami: 1981 Chargers at Dolphins. The favored Chargers led 24-0 before the Dolphins, led by backup QB Don Strock off the bench, rallied the team to a 24-24 tie. The teams exchanged touchdowns before the Dolphins even took a 38-31 lead, which was answered by Dan Fouts and his high-powered offense to tie the game at 38. Strock had his interception fumbled back to him, but Miami’s 43-yard field goal was tipped by tight end Kellen Winslow to end regulation. The Chargers could have ended things immediately, but missed a 27-yard field goal to start overtime. Oof. Several more drives took place, including Miami’s 34-yard field goal being blocked. The Chargers finally won 41-38 on a 29-yard field goal.

Great game (I’ve seen a full replay), certainly an epic, but I’m not putting any game that involves Don f’n Strock throwing for 403 yards off the bench and a bunch of failed field goals as the No. 1 game over what we just saw on Sunday.

So, there you have it. This was the best of the best. I can only hope we see these teams meet in the playoffs more. This was already the fourth Mahomes-Allen game in the last two seasons. John Elway and Dan Marino met three times in 16 seasons despite being drafted into the same conference in the same year. This could be the NFL’s next great rivalry with a signature game to boot already.

Of course, now it’s the Bengals’ turn to take on the Chiefs in Kansas City. The Chiefs do not have to make up that 27-3 loss in Tennessee. They get to stay home and make up that 34-31 loss in Cincinnati. Let’s just say I won’t be voting against Mahomes again any time soon.

Not even 13 seconds is good enough to put him away. But props to Buffalo for closing the gap from last season. Just have to make one more stride to get over the hump next year.

Rams at Buccaneers: Did Tom Brady’s Luck Finally Run Out?

If I was writing the script for Tom Brady’s final NFL game, it might look quite similar to what happened on Sunday. You know I would have him lose as a home favorite in an early round of the playoffs. You know I would have him commit multiple turnovers. But I would write in all sorts of absurd Brady Bullshit (Trademark 2003) to leave no doubt that he was the luckiest player to ever lace them up in this sport. The LOAT. The first unsportsmanlike conduct penalty of his career was a nice twist I didn’t see coming, but he kind of made himself a target for that this week.

But even after getting a mind-numbing number of breaks to go his way, he would still lose in the end. And that’s exactly what happened against the Rams, though my script would have been better for my blood pressure.

But there will not be a repeat champion, extending the longest drought without one in NFL history. As for Brady retiring? I’ll believe it when I see a Week 1 without him. I don’t think we’re lucky enough to be done with him, but the days have to be numbered.

I also have to do a bit of an apology to Matthew Stafford. I’ve been hard on him about the 8-68 record against winning teams, though I wanted that to go viral to motivate him this season. You also should know by now that my game predictions for Brady are reverse jinxes, which is why you see me pick his team to win every time. You have to read between the lines. When I say things like “The Rams have a lot of the right elements to deal with Tampa Bay,” but then you see me bring up Brady’s luck, that’s a pretty good sign I actually believe the Rams should win this game. They’re the better team.

While I was absolutely right that turnovers would be the story of this game, none of them were Stafford’s fault as I feared. Stafford was money on the road, saw the field very well, and made the biggest throws of the game to Cooper Kupp. He passed for 366 yards despite Cam Akers (24 carries for 48 yards) only averaging 2.0 yards per carry and wasting a lot of first downs.

Stafford was 0-53 in his career when his team allowed more than 24 points against a team with a winning record. Make that 1-53 after the biggest win of his career.

But my lord did the Rams make this tougher than it needed to be. You could see early on that the Rams, who had already won two in a row over Brady’s Bucs, were a tough matchup for this team. Neither team had their best tackle (Andrew Whitworth for Rams, Tristan Wirfs for Bucs), but the Rams’ superior pass-rushing talent took over while Stafford was better at delivering throws from different angles.

Brady was off early, missing his first four throws as the Rams built a 10-0 lead. Stafford found Kupp inexplicably open for a 70-yard touchdown on third-and-20 to take a 17-3 lead. The Buccaneers missed a 48-yard field goal on the drive where Brady was penalized for cursing at a ref, though it should be pointed out they eventually had a first down four yards beyond where that penalty was marked off. The drive just stalled out as was often the case for the Bucs, who finished 3-of-14 on third down, even worse than their bad week against the Eagles on third down. The Buccaneers were all-around sloppy in this game, kicking off out of bounds multiple times, and drawing multiple 15-yard flags.

LOAT MOMENT #1: But with the Rams up 20-3 at the two-minute warning, that’s when the LOAT kicked into gear, or perhaps when Brady sacrificed a newborn’s soul for one last pact with the devil. Brady just threw up a pass for Gronk that was intercepted and returned to the Tampa Bay 31 with 1:53 left. Now if someone like Peyton Manning, Drew Brees, or Aaron Rodgers throws that pick in a big game, they’re falling behind 27-3 at the half. Maybe 24-3 at best. But what makes Brady the LOAT is he wills his defense to force Cam Akers to fumble at the 1-yard line after the ball just started coming out prior to Akers’ head being down on the ground.

What a break. As you might expect, the last team to lead a playoff game by 14+ points and lose a fumble before losing the game was Atlanta in Super Bowl 51. That was the big Hightower strip-sack of Matt Ryan with the Falcons up 28-12 on third-and-1. When Al Michaels and Cris Collinsworth remind you that if anyone can lead this comeback, it’s Brady, they’re burying the lede that he isn’t even on the god damn field when these crucial plays are happening. But if Jimmy Garoppolo can lead a 17-point second-half comeback against these Rams in Week 18, Brady could too.

The Rams seemed to overcome this one. They used a sequence of a great punt, three-and-out on defense, and a big punt return to set up a 28-yard touchdown drive. Stafford’s QB sneak looked better this week and the Rams were in the end zone again. Brady had to settle for a field goal, and it was 27-6 late in the third quarter. Again, this is Super Bowl LI territory. Just make one more good drive and you win the game, which is exactly what Atlanta failed to do despite so many chances. After Tampa’s second kickoff out of bounds, things were looking good at the 40. However…

LOAT MOMENT #2: The reliable Kupp fumbled a short completion and Brady was at the 30. Here we go again.

According to Stathead, the Rams are the only team in the playoffs since at least 1994 to lose two fumbles from scrimmage in a game while leading by at least 14 points.

Four plays later on a fourth-and-9, there’s Brady suddenly with a wall of pass protection and a big cushion on Scotty Miller, who caught the ball for 16 yards. Again, learn from Atlanta. One good play ends the game. Three plays later, Leonard Fournette was in the end zone and it was 27-13 going into the fourth quarter.

The Rams used a whopping 31 seconds to go three-and-out. But just when you thought you knew where this one was headed, Von Miller said enough of this bullshit. He got to Brady for a strip sack and the Rams had the ball back at the Tampa 25. At worst, they’d kick a field goal and take a three-score lead again. Well, about that…

LOAT MOMENT #3: Stafford was not expecting the snap from center and the ball went over his head for a third fumble. The strip-sack actually helped Brady gain 25 yards in field position.

When I just told you the Rams are the only playoff team to fumble two times when leading by at least 14 points, you know damn well that means they’re the only team to do it three times since at least 1994. As far as regular-season games, you have to go back to 2002 Bills vs. Bengals to find the last team to cough it up three times with a 14+ point lead. But at least two of those Buffalo turnovers were in the final four minutes of the game with a 27-9 lead.

Surprisingly, Brady did not turn this one into points despite starting at the Los Angeles 45. He took a big sack from Leonard Floyd to bring up a fourth-and-14. Brady threw incomplete for Mike Evans, but Eric Weddle was there for a late hit that was unnecessary. That’s a 15-yard penalty, but the interesting part is that it’s a dead ball foul assessed after the change of possession as the hit came a split second after the ball hit the ground. Maybe something to look at for a rule change, but a rare case of things going against Brady. Though, let’s be real. A bad throw bailed out by a late hit would have just been LOAT MOMENT #4. Speaking of which…

LOAT MOMENT #4: Just when you think the Rams are going to put it out of reach at 17 points, kicker Matt Gay comes up short on a 47-yard field goal with 6:31.

Now a 47-yard field goal is not a lock, but who in the NFL comes up SHORT on a kick from that distance in a game played in Florida? Absurd effort from the kicker there to keep the Bucs alive. But again, Brady couldn’t respond. He didn’t see a wide-open Miller on a fourth-and-9 and threw incomplete with 4:26 left. The Bucs had to use their three timeouts to get a three-and-out and get the ball back with 3:56 left.

All the Los Angeles defense has to do is not give up a touchdown before the two-minute warning. Ideally, you stop them cold. But if you give up a touchdown after the 2MW, then it’s just a matter of recovering the onside kick to end it. Of course, Tampa probably recovers that with the way this one was going, but whatever. Just play defense.

LOAT MOOh wait, let’s give him one here. Knowing this clock situation, Brady took his shot deep and finally hit a good pass in the game, finding Evans in coverage with Jalen Ramsey for a 55-yard touchdown with 3:20 left. The Bucs trailed 27-20.

One first down can win the game with the Bucs out of timeouts. McVay shrunk in this situation against the 49ers in Week 18. He couldn’t do it again, could he? Passing on second-and-7 to end it certainly was an option, but they stuck with Akers. He looked to have a hole, but oh shit.

LOAT MOMENT #5: Akers fumbles at the LA 30 with 2:25 left. Brady is 30 yards away from the tie, his ninth playoff touchdown drive starting in opponent territory since 2020. This is only the third time during Brady’s NFL career that a player fumbled in the final 3:00 of a playoff game with a one-score lead. The other two involved the Steelers: they forced Cincinnati’s Jeremy Hill to fumble in 2015 and Jerome Bettis lost his infamous one in Indy in 2005 before Ben Roethlisberger tackled Nick Harper.

Now the only question was if “no risk it, no biscuit” Bruce Arians would go for two if the Bucs get a touchdown. The Brady sneak on fourth-and-1 may have made that more likely, but with everyone expecting it, the Bucs went with a run to Fournette, who broke a tackle in the backfield and ran for a 9-yard touchdown with 42 seconds left. I think the extra point to tie the game at 27 was the right call with that much time left.

It’s probably a good thing I didn’t tweet about a pick-six coming next, but it sure felt like the Rams were going to blow this one. They’ve already coughed up four fumbles and you couldn’t trust the kicker. The ensuing drive got off to a rough start too with Stafford taking a sack. But that final timeout by McVay at 35 seconds bought the team time to compose itself before making some plays. Stafford found Kupp for 20 yards, then against the blitz-happiest defense in the league, Stafford went back to the most targeted receiver against the blitz in the NFL this season. Kupp ran right down the middle of the field and the ball was perfect for a 44-yard gain. The spike operation was smoothly done, and Gay was able to make the kick from 30 yards out to win the game.

I would have preferred a more humorous ending for Brady to lose, but this works for me. A signature game-winning drive for Stafford and a memorable throw to Kupp, the best wideout this year.

It seems crazy that the Rams still have to beat another nemesis next week to get to the Super Bowl, because this was some real slay the dragon shit in Tampa. They overcame four fumbles in the LOAT’s house, blew a 24-point lead, and still found a way to win. The Rams are the first team since the merger to have zero interceptions and lose four fumbles in a playoff game.

It took 13 years, but Stafford has a signature win. This Tampa team’s success last year was a model for what the Rams are doing this season. Now they are just two more wins away from getting it done, but neither game expects to be easy.

As for Tampa Bay, I’ll just let Antonio Brown have the final words:

49ers at Packers: Aaron Rodgers To Go Through with Super Bowl Boycott After All

Wait, was that it? Did we really just see the end of Aaron Rodgers’ run in Green Bay with a 13-10 home loss to the 49ers in the divisional round? He’s the first quarterback in NFL history to lose four playoff games to the same opponent, but none have been more shocking or disappointing than this one.

In fact, I think it’s the worst loss of Rodgers’ career.

The Packers were swept out of the playoffs by the 2012 49ers, 2013 49ers, 2014 Seahawks, 2015 Cardinals, 2016 Falcons, 2019 49ers, and 2020 Buccaneers. That means they were 0-2 against all those teams, opponents that were usually just better and they never found an answer for. This is the first time Green Bay didn’t get swept out of the playoffs since they lost 37-20 to the 2011 Giants in the divisional round. That was another team, like the 2021 49ers in Week 3, where they escaped with a road win on a last-second field goal. But come playoff time, they shit the bed. At least in 2011, the Packers could blame a slow start on resting Rodgers after the 15th game and having the bye. Those Giants also completed a second historic Super Bowl run that year, and I do not believe these 49ers are those Giants reincarnated. These 49ers needed a 17-point comeback in LA to make the tournament before holding on for dear life in Dallas last week.

Sure, the 2011, 2014, and 2020 Packers all looked more prepared to win a championship than this year’s version, a team that had key players injured on both sides, relied too much on Davante Adams, ranked 21st in points per drive allowed, and had a hard time putting teams away comfortably. Those three MVP seasons by Rodgers were better versions of him than what we saw this year, which will still likely net him a fourth MVP as it’s a regular-season award and the votes have been cast.

But what I’m most stunned by is the 13-10 final. Prior to Saturday night, Rodgers was 41-0 in starts he finished where the Packers allowed fewer than 14 points. The only loss by actual record in that situation was a 7-3 game he left early (concussion) against the 2010 Lions. But he was undefeated in games he finished. Keyword: was. You could also say Rodgers was 55-1 in games where the Packers allowed under 16 points with the only loss being the Fail Mary in Seattle (2012).

Make that 55-2.

Incredibly, the slow-starting Packers opened this game with a nice 69-yard touchdown drive to take a 7-0 lead. The defense, which was excellent, forced a three-and-out, collecting the first of four third-down sacks on the night. You couldn’t ask for a better start. But Marcedes Lewis fumbled in San Francisco territory on the second drive, and the Packers gained more than one first down on one of their last eight drives.

You don’t deserve to win when you only score 10 points. I inadvertently jinxed Rodgers big time when I pointed out he had by far the longest streak in playoff history (20 games) of leading his team to 20 points. But he only got halfway there this time, and it’s only the second playoff game where he did not throw a touchdown pass.

But this offensive dud has another major storyline. It was one I could see coming weeks ago.

The Packers had the worst special teams (in a variety of ways) this season, and while it was not a strength for the 49ers this season, sure enough it was a huge part of this upset loss. As predicted, here is that bullet-point list of special teams woes. I’m not even going to bother listing a few short punts and kickoffs that gave the 49ers good field position. We’ll just stick with the big ones.

  • Mason Crosby’s 39-yard field goal was blocked to end the first half, wasting a 75-yard catch by Aaron Jones and keeping the score at 7-0.
  • Deebo Samuel, who had another great game, returned the opening kickoff of the second half 45 yards to give the 49ers the ball at the 50. The drive ended with a field goal.
  • One for playoff lore: up 10-3 with 4:50 left, Green Bay’s punt was blocked deep in their own end, the ball took forever and a day to land on the ground, and the 49ers were there for the 6-yard touchdown return to tie the game.
  • San Francisco kicker Robbie Gould nailed a 45-yard field goal at the buzzer to win the game, 13-10.

That was a brutal special teams performance, but there is some solace in watching your weakness end your season. It hurts more when your strength lets you down, and that happened here too with the offense. Last season against the Buccaneers, it was the historically-great red zone offense that let down a couple times, including that famed sequence late that led to a field goal when the Packers were down eight points.

But this year? Things were all around sour after the opening drive. Lewis’ fumble was just a bad play by him, but it also speaks to the lack of a tight end after losing Robert Tonyan. The new running attack was stalled out when A.J. Dillon, who scored the touchdown, left with injury. Dillon and Jones combined for just 66 yards on 19 carries. Jones had 129 receiving yards to lead the team, but 75 of those yards were on that blown coverage before halftime. Rodgers only passed for 55 yards in the second half. A whopping 18 of his 20 completions went to Adams and Jones as only four Packers caught a ball.

Rodgers took five sacks against a defense that could barely touch him in Week 3. Nick Bosa was indeed a beast this time around. He probably dedicated the performance to Kyle Rittenhouse. The offensive line has not been as strong this year, and left tackle David Bakhtiari was not able to go again, but Rodgers took some really costly sacks in this one, a usual hallmark of a disappointing Green Bay loss.

The defense was not a scapegoat this time though. Garoppolo flirted with multiple picks, forced an awful one in the end zone on first down despite George Kittle being wide open, and his internal clock seemed to be frozen on this snowy, freezing night. But the 49ers also seemed to adjust better to the conditions than the Packers, which was weird. It was the 49ers hurting themselves more with drops, including a wide-open one by Kittle that would have been a big play. The 49ers hung in there, got the huge break on the blocked punt, and just waited for their chance as the Packers could not move the ball.

When Garoppolo just has to complete two quick passes for 26 yards to get a game-winning drive going, that’s going to be ideal for the 49ers. When you can just hand the ball to Samuel three times to get a first down that puts you in field-goal range, including a 9-yard run on third-and-7 where almost any other quarterback would have to make a huge throw, that’s stealing for the 49ers.

And they stole this victory away from Green Bay to end its season in one of the most painful ways possible. Rodgers was numb after the loss and that’s easy to understand. He has opened himself up to more criticism than ever before this season with the way he’s handled himself on podcasts and media interviews. I’m not going to pile on here. I’m just glad we don’t have to entertain the idea of him letting Brady get to a second Super Bowl in the NFC before he does. After this loss, I don’t think he will ever get back to the big game.

Matt LaFleur’s 2019-21 Packers are the first team in NFL history to win at least 13 games in three straight regular seasons. But they are also going to go down as the only team to win 39 games in a three-year span and not reach the Super Bowl.

Is this the end of an era of Hall of Fame quarterback play in Green Bay from 1992 through 2021? I don’t know what it’s like to watch an NFL where the Packers don’t have Favre or Rodgers. I got a little taste of it in 2013 and 2017 when he had his collarbone injuries, and yeah, the Packers weren’t relevant those weeks.

We’ll see what the future holds, but it’s crazy to think the 49ers are one win away from sending Jimmy Garoppolo to more Super Bowls than the Packers reached with Rodgers.

Bengals at Titans: Ryan Tannehill’s Interception Sudoku

I usually do not boil a playoff game down to one quarterback choking, but Ryan Tannehill choked this one away for the Titans, who fell to 0-3 in Tennessee in home playoff games as the No. 1 seed. They never scored more than 16 points in any of those games either. This comes on the heels of a 20-13 wild card loss to the Ravens last year in which Tannehill also had a late interception.

This time, Tannehill threw an interception on his first pass of the game, his first pass of the second half, and his last pass of the game. It’s like filling in an interception sudoku. He would have tried to add one in overtime if the game ever got there, and the fact that it didn’t is the most egregious part of this all.

Well, there’s also this fact: teams who score under 20 points and take nine sacks are 2-126-2 (.023) since 1960. The 1990 Seahawks had the first win against the Chiefs after Dave Krieg escaped Derrick Thomas’ final sack attempt. Now the Bengals have the first playoff win after Joe Burrow, who led the league in sacks taken this year (51), took nine sacks and still got the low-scoring road win. Tennessee’s pass rush was impressive at overwhelming the Bengals throughout the game, but it went to waste from an offensive performance that would make Jeff Fisher nod with approval.

The Titans waited basically all season to get their offense healthy for this playoff run. A.J. Brown was awesome with 142 yards and a one-handed touchdown catch. Julio Jones looked good with six grabs for 62 yards. Derrick Henry had screws in his foot, didn’t look quite ready for his 20-carry workload, but he scored a touchdown and had a few vintage runs. The Titans probably should have given D’Onta Foreman more touches as he had four carries for 66 yards, including a 45-yard run for the offense’s biggest play of the game.

But even after getting all his guys back, Tannehill did not go to them on the crucial play of the game. On a third-and-5 at his own 40 with 28 seconds left, Tannehill decided to force a pass at midfield to Nick Westbrook-Ikhine. The result was a tipped interception, which set up the Bengals for their game-winning field goal with no time left after Burrow found Ja’Marr Chase for 19 yards. Evan McPherson has been an outstanding rookie kicker and he drilled a 52-yard field goal to win this game.

The last thing Tannehill could do was turn the ball over in bad field position. If he wanted to throw a bomb to Brown or Jones that was picked 40 yards downfield, that probably would get the game to overtime too. But with overtime in his back pocket, Tannehill got greedy and didn’t even pick a good option.

That was a killer, but so was the tipped pick after Foreman’s 45-yard run got the ball into the red zone. Mike Hilton made an incredible play on the ball, so it wasn’t all Tannehill’s fault, but he was not sharp in the game. The offensive line also did not get any push on a couple of key Henry runs, including a fourth-and-1 in a tied game with 7:16 left. Mike Vrabel is willing to chop his dick off for a Super Bowl ring, but he can’t get behind a quarterback sneak? Is he afraid he’ll have to actually go through with the castration if the Titans get a Super Bowl on his watch?

Watching Tannehill in the last three postseasons, where he averages 150.8 passing yards per game, I’m not sure Vrabel has to worry about any Super Bowl in the near future.

One thing blowing back on Vrabel from this game was his decision to go for a two-point conversion with the game tied at 6-6. It was early in the game (second quarter), the extra point puts Tennessee up 7-6, but I liked it just because there was a penalty that put the ball at the 1. I liked the call to give the ball to Henry, but he came up inches short and the game remained tied.

Would we have a 9-7 game at halftime if the Titans go for one? Probably. Would the Bengals go for two on their touchdown to start the third quarter to make it 17-7 instead of 16-7? Probably not. Do the Titans take a 17-16 lead late third quarter if they had gone for one? Good chance. But would Burrow still take a brutal sack that knocks the Bengals out of field goal range in the fourth quarter if he was down 17-16 instead of tied 16-16? Maybe, maybe not. The whole fourth quarter could play out much differently from there, so I’m not going to put the loss all on that one decision. There were more missed opportunities than that in the game. The Titans had three plays of 40-plus yards and turned those drives into just nine points.

It was the second year in a row that the Titans had an offensive letdown at home for a one-and-done postseason. Turn the ball over enough and you can lose to anyone in this league. If it’s true against the Texans in Week 11, it’s for sure true in the playoffs against Cincinnati.

After watching the Bills-Chiefs game on Sunday night, it’s still hard to believe the Titans beat both of those teams the way they did this year. It’s also hard to believe they could have done it again next week, or next year for that matter.

If Tannehill could learn anything from Burrow in this game, it may be that eating the ball is sometimes the smartest option. Don’t throw the game away.

Next week: Can we actually get a third Bengals-49ers Super Bowl? It’s the worst option available and would require two road upsets, but we’ll see. Personally, I want a rematch of 54-51 between the Rams and Chiefs. It’s the best matchup and provides the best storylines. Even 49ers-Chiefs isn’t so bad since it would be a rematch of Super Bowl LIV.

NFL 2021 AFC Divisional Round Preview

Despite only one team getting a first-round bye now, the divisional weekend is still prime for some of the richest drama in NFL history. I just recapped some of the most dramatic games in divisional round history that tested 14 eventual Super Bowl champions.

Of course, the bigger story in that link is that we have gone 19 straight playoff games without a fourth-quarter lead change, one shy of tying the record from 1935-50.

Maybe we’ll get something memorable this weekend, but this has been a difficult round for the road teams to win. Since 2011, home teams are 31-9 (.775) in the divisional round. But most years have that one upset and 2016 was the last time there were two road winners (Packers in Dallas and Steelers in Kansas City).

The Titans stunned the hell out of the top-seeded Ravens in 2019, and the Buccaneers avoided a three-game sweep by the Saints last year, propelling them to a Super Bowl win.

The NFC previews will be posted on Friday. Let’s start with a new matchup in the AFC and a crucial rematch of last year’s AFC Championship Game.

Bengals at Titans (-3.5)

See my early preview for this game at BMR.

The Bengals finally ended their long playoff drought last week with a 26-19 win over the Raiders. The young offense, led by Joe Burrow and Ja’Marr Chase, did not crack in the first playoff game for this new era of Cincinnati football, but the Raiders were one of the worst playoff teams in history.

Now the Bengals must try to shake an 0-7 road playoff record against the top-seeded Titans. And no, the Titans are not the worst No. 1 seed in history. I refuse to even call them the worst Tennessee team to be the No. 1 seed in the AFC. That 2008 team with Jeff Fisher and Kerry Collins was such fool’s gold at 10-0 before stumbling down the stretch.

These Titans have much better skill players when healthy, Mike Vrabel has been an awesome coach when playing the role of an underdog, and this team can win high-scoring games and close games. They are also battled tested, winning more games (eight) in one season against teams with a winning record than any team in NFL history and having the best win percentage (8-3, .727) in such games (min. nine games).

Now, are those records a little misleading? Yes, the 17th game helped 8-8 teams Tennessee beat like the Saints and Dolphins finish with a winning record at 9-8. But the Titans still boast more quality wins than any team this year, already hammering the Chiefs and beating the Bills in a shootout. Now the Titans just have to beat an inexperienced Cincinnati team and only one of those AFC powerhouses to get to a Super Bowl. Yeah, the Titans lost to the Jets, but so did the Bengals.

Derrick Henry expects to be back for his first game since Week 8, but I think the Titans have shown they can win some big games without him or with him being ineffective. The health of A.J. Brown may be more important to the offense than any other non-quarterback. Tennessee is 10-1 when Brown plays at least 60% of the snaps in a game and 2-4 when he does not. He needs to have a big game. Brown scored Tennessee’s only touchdown in a disappointing 20-13 home playoff loss to the Ravens last year. This team seems to perform better when the chips are stacked against them.

Three of the four biggest receiving games against the Bengals this year were done by top-tier tight ends, but Davante Adams also had 206 yards and a touchdown in Cincinnati. Julio Jones being back should also help the passing game. It’s been so rare this season for the Titans to have Brown, Jones, and Henry on the field together. The wideouts being out had a lot to do with that overtime loss to the Jets early this season, and the significant injuries that hit the Titans in losses to the Steelers, Patriots, and Texans had to contribute to Tennessee turning the ball over 13 times in those three games. This offense usually protects the ball well. The Bengals are not great at taking the ball away.

I think the week of rest is big for the Titans to get as healthy as possible for this matchup. I was surprised to see how close the Titans and Bengals are defensively this season, but I’d still give the Titans an edge there. No quarterbacks have been sacked more than Burrow (51) and Ryan Tannehill (47) this year. The Bengals have the better quarterback right now as Tannehill did not have his best season with the injuries around him, and Tannehill has been pedestrian in his four playoff starts. But I think unlike the Raiders, who called 58 passes and ran Josh Jacobs 13 times despite success on the ground, the Titans are going to stay balanced and stick to their usual game plan. The Titans are also better on third down and in the red zone. The Bengals struggled in the red zone against a historically bad red zone defense last week. That area has been money for the Titans under Tannehill, and they were fifth this year in touchdown rate (63.9%).

This isn’t Jeff Fisher and Kerry Collins trying to win a 13-10 game. I’m sticking with my gut and the NFL history that says a pass-happy team with a young offensive core is prime for a letdown on the road in the playoffs against a physical team, especially when it’s that team’s first postseason. Maybe Henry is rusty and fumbles early or is completely ineffective like he was last year against the Ravens, and the Bengals ride their top pass connection to an early lead. We’ve seen it before. But I’m going to trust the better coach and the team that’s been better this year and should be healthy at the right time to win this one.

We can talk next week about why the Titans won’t get to the Super Bowl, but I like them on Saturday. Just hang onto the victory cigar for later, Joe.

Final: Titans 28, Bengals 20

Bills at Chiefs (-1.5)

It is not unheard of to consider a game early in the playoffs to be “the real Super Bowl” if you will. When the NFC won every Super Bowl from 1984 through 1996, the NFC Championship Game was often thought of as the real Super Bowl those years, especially when it was Dallas vs. San Francisco in 1992-94. The 2006 AFC Championship Game between the Patriots and Colts was thought to be the real Super Bowl that year because of the entity known as Rex Grossman waiting for the winner in Miami.

But wow, I cannot remember a divisional round game being thought of as the Super Bowl, especially between two teams that are not the No. 1 seed. Maybe I’m tripping and this is too high praise, but I think these teams are the real deal in the AFC and this is an epic rematch of last year’s AFC Championship Game. The Chiefs were the AFC favorites going into the season, and the Bills took over that spot when they won 38-20 in Kansas City in Week 5. They had some bad losses since, but Buffalo just had the most perfect offensive game imaginable in crazy conditions against the Patriots, scoring a touchdown on all seven possessions. In fact, this is the first playoff game in NFL history between two quarterbacks who threw five touchdown passes the previous week. Patrick Mahomes threw his five touchdowns in a span of 11:31 against the Steelers.

This could be the next great rivalry in the NFL. This will already be the fourth meeting between Mahomes and Josh Allen in the last two years. John Elway and Dan Marino were in the same conference for 16 seasons and only met three times with two of those coming in Elway’s final season (1998). The Chiefs sent Buffalo home last year to end an eight-game winning streak. The Bills got some revenge this year by handing Mahomes the worst home loss of his career (18 points). His other home losses have been by no more than eight points. The spread has already moved a point towards Buffalo since opening at Chiefs -2.5.

I’m going to break this preview up into the two main questions I have about this matchup.

Question 1: Can the Chiefs turn around the 38-20 defeat from Week 5, and was it really that lopsided?

Results can vary wildly from week to week in the NFL, but on wild card weekend, all five rematches were won by the team who won the previous matchup, including these Bills and Chiefs. Buffalo scored the most points anyone has against New England since 1990. The Chiefs pounded the Steelers for the second time in a month, sending Ben Roethlisberger into retirement.

Both offenses should cool down a little from that historic territory, but there should be more pressure on Kansas City to adjust from that 38-20 walloping the Bills put on them in Week 5. It is hard to beat a great team twice in the same season, but for teams that have already done it, on the road no less, it actually is easier than average in the rematch.

Since 2002, road teams attempting a sweep in the playoffs are now 13-13. The Bills and Rams just reversed their home losses last week by beating the Patriots and Cardinals. The Rams in particular turned a 17-point home loss into a 23-point win on Monday night, but obviously the Cardinals were on life support down the stretch and already lost a home game to their division rival Rams. Likewise, the Patriots flopped down the stretch this year, including two games (without the bad wind) where they couldn’t get the Bills to punt. This is Mahomes in Kansas City, so a bit different.

However, consider these numbers. Since 2002, teams that win the regular-season matchup by at least 18 points are 25-9 (.735) in the playoff rematch. When those teams are the underdog in the playoffs, a rare situation, they are still 5-1 in the playoffs. The only loss was the 2004 Broncos vs. Colts, but that whole example is misleading since Indy rested starters in Week 17 before blowing the Broncos out at home in the playoffs.

But let me rant on my own stat for a brief moment here. This is something I really need to start focusing on more in the offseason. I just gave you a stat on a sample size of 34 games based on games where a team won by at least 18 points. Yes, the Bills beat the Chiefs by 18 points, but an 18-point win is a lot closer to an 11-point win than it is a 31-point win like seven of the games in that sample were. So, why am I looking at a group of “comparable games” when my game is at the lowest end of that qualifier? I’d be better off looking at games decided by 11-to-25 points, or a 7-point window around 18 points. In that case, 23-17 (.575) is the record since 2002, not nearly as one-sided as 25-9 (.735). Just something to think about with stats like that.

It is fair to say the Chiefs were embarrassed by Buffalo in Week 5 as the Bills learned a few things from their 2020 losses. The “don’t blitz Mahomes” thing that got so popular this year? The Bills were actually the first defense to do that, blitzing zero times in the 2020 game on Monday Night Football. The Chiefs just had a great running attack that night and Mahomes made an incredible conversion on third-and-12 to Byron Pringle to put the game away. But it was the lowest-scoring game between these two at 26-17.

In Week 5, Mahomes threw a season-high 54 passes but was only blitzed twice. He was not even pressured that often – 14.3% tied for second-lowest game this season – but did not handle the different looks well. Mahomes scrambled seven times that night, twice more than any other game, as he was not comfortable in the pocket. The Bills, who were destroyed by short throws and YAC from the Chiefs in the AFC Championship Game, also tackled very well in Week 5, holding Mahomes to 4.2 YAC/completion, his second-lowest game of 2021.

On the other side of the ball, the Bills struggled to get any big plays going in their two losses to the 2020 Chiefs. That sure changed in Week 5. Allen had pass completions of 61, 53 (TD), 41, and 35 (TD) yards as he completed 15-of-26 passes for 315 yards without a sack or turnover. Despite his reputation for a big arm, Week 5 remains the only game of Allen’s NFL career where he threw multiple touchdown passes of 25-plus yards. Mahomes has 11 such games in his career.

As it turns out, throwing the deep ball with safety Daniel Sorensen in coverage is quite profitable. Sorensen allowed the two longest completions for 114 yards that night. For the season, he allows 12.1 yards per target in coverage, but the Chiefs have been wise to limit his snaps since that night. Sorensen went from playing 98% of snaps in Weeks 1-5 to 47% of snaps in Weeks 6-17.

Allen also rushed for a team-high 59 yards and a touchdown. Mahomes led the Chiefs with 61 rushing yards but that is not as ideal for Kansas City as it is Buffalo. Jerick McKinnon just had the game of his life for the Chiefs with 142 yards from scrimmage against Pittsburgh, but the Steelers were horrible against running backs this year. With the Kansas City backfield being so inconsistent this year, look for the Bills to contain whichever back gets the majority of touches this time.

There’s this idea that Mahomes has had to adjust with the way defenses are playing the Chiefs, copying that Super Bowl blueprint of minimal blitzes and two-deep safeties. There is definitely truth to this. Mahomes has six games this season with an aDOT under 6.5 yards and all six of those games are since Week 11. His lowest game of the season (5.0 yards) was against the Steelers on Sunday as the Chiefs had big YAC plays.

So, while there is truth to it, let’s not overblow it out of proportion. The Chiefs have had success with long drives in past years. They weren’t all 60-yard bombs to Hill for scores. In fact, Mahomes just threw the longest touchdown pass of his career to Kelce (48 yards) on Sunday night. Mahomes did still attack the Steelers (Week 16) and Bengals (Week 17) deep late in the season with success. I just think it’s important for Kansas City to get Hill and Kelce involved this week. They’ve had some really quiet games down the stretch here, and while the lesser players have stepped up, I’m not sure the Chiefs can continuously score without their stars doing big things.

More than anything, the Chiefs are simply going to have to protect the ball better this time after losing the turnover battle 4-0 in Week 5. Sure, there was a tipped ball off Tyreek Hill’s hands that went to the Bills for a pick-six to make it 31-13 in the third quarter. But guess what? Hill has tipped multiple picks for interceptions this year as Mahomes has had numerous picks come off tipped balls. There was also that red-zone pick by Buffalo, a very good defense at forcing takeaways, on a tipped ball that cost the Chiefs more points that night. Again, guess what? The Chiefs have had multiple tipped picks in scoring territory this year, including against the Giants on MNF and last Sunday against the Steelers.

Mistakes just happen at bad times for this offense, and it’s been that way for much of the season. I’m not sure we can just magically count on them to not do it this week against one of the best defenses they’ll see. On the other hand, one thing they could control is to not give up the obligatory Chiefs fumble by not calling a fvcking Wildcat play when you have Mahomes at QB. The Chiefs called a wildcat play against Pittsburgh, and it blew up for a touchdown return by T.J. Watt. So, let’s scratch that one from the playbook this week, but you’re on your own fortune for tipped picks.

I guess what I’m getting at is if you keep Sorensen off the field and don’t give up as many big plays, and you avoid the tipped pick-six, that could cut 14 points off that 18-point deficit. I think this game should be a lot closer this time, and that could be a bad thing for the Bills, who are 0-5 at 4QC/GWD opportunities this season. Buffalo’s 1-5 record in close games was the worst in the NFL this season.

This was not an issue for Allen’s first three seasons, and his fourth quarter stats look great this year (71.1% complete, 10 TD, 0 INT, 7.6 YPA, 117.7 PR). But they are simply not finishing the drives in crunch time. You saw the red-zone failures in the windy game against New England, a 14-10 loss. He was erratic against the Steelers in Week 1. He was stopped short on the sneak in Tennessee. He choked badly against Jacksonville in a 9-6 stunner. Mahomes is 43-1 when the Chiefs allow fewer than 27 points. The Bills cannot expect to be in position to win a low-scoring game this week.

But in my view, that effort to come back from 17 points down in the fourth quarter in Tampa Bay was big for this team. While they did not win the game in overtime, they tied it up and had a chance in regulation had the referees called defensive pass interference the way they called it for Tampa in overtime (go figure; #LOAT). If I’m a Chiefs fan and Allen has the ball late to win the game, I am nervous as hell. After not blowing a fourth-quarter lead in 2020, the Chiefs have done it three times this year (Ravens, Chargers, Bengals), and that doesn’t even include the epic comeback in Los Angeles when the Chiefs had to win in overtime. Those losses are the reason why this team wasn’t resting as the No. 1 seed and opening with a softer opponent like the Bengals.

Question 2: Do we trust Buffalo’s No. 1 scoring defense for the whole season or Kansas City’s No. 1 scoring defense since Week 6?

This is an interesting matchup as the Bills have the No. 1 scoring defense and were the only team to allow fewer than 300 points this season. But after a horrible start to the season where the Chiefs allowed at least 29 points in all five games, Kansas City turned things around under veteran defensive coordinator Steve Spagnuolo. Since Week 6, the Chiefs have the No. 1 scoring defense, allowing 24 fewer points than No. 5 Buffalo in that time. The Bengals (34) were the only team to hit 29 points on the Chiefs since Week 6.

Do we trust the season stats or the more recent stats? I’m not sure anyone has ever posted a definitive study of this, or if anything on it would even be conclusive enough as the league is just goofy like that. For example, when I look at the fewest points allowed by a team in Games 6-16 since 2011, the top of the list is the 2011 Steelers. You know, the defense that let Tim Tebow complete 10 passes for 316 yards in a 29-23 wild card loss. Right behind them are the 2014 Seahawks, famous for blowing a 10-point fourth-quarter lead in the Super Bowl, and the 2015 Chiefs, who lost 27-20 in New England.

With defense, it’s all about how you play that day, and who you play usually plays a huge role in that. Sure, we can say the Bills padded their defensive stats by playing rookie Davis Mills in the rain, a 40-0 shutout where he threw for 87 yards and four picks. We can see that Mahomes (272) and Brady (363) were the only quarterbacks to pass for more than 260 yards on Buffalo this year, and Brady (105.6) was the only one to have a passer rating higher than 86.7. That looks daunting for Mahomes, but it’s less daunting when you see this starting QB list for Buffalo:

  • Three cast members of The Walking Dead (2021 Big Ben, Matt Ryan, Cam Newton)
  • Six rookies in a terrible rookie year (Trevor Lawrence, Zach Wilson, Davis Mills, Mac Jones 3x)
  • Two hopeful employees in 2022 (Taylor Heinicke, Trevor Siemian)
  • One bus driver (Carson Wentz)
  • One create-a-player with a generic name (Mike White)

That leaves Brady and his aforementioned big game that still needed overtime and one blown coverage, Mahomes and the game we went over, and Ryan Tannehill got a huge game from Derrick Henry on an effective night where the Titans scored 34 points in a win.

In other words, I’m not sure the Chiefs need to be that scared of this defense, especially without corner Tre’Davious White (ACL) to take on Hill. In Week 5, Mahomes was just 5-of-11 for 36 yards when targeting White in coverage. He’s gone now.

On the other hand, the Bills can look at this Kansas City defensive improvement and point to the schedule as well. Like getting Daniel Jones and the Giants on any week. Getting the Cowboys when they were in a funk and Amari Cooper had COVID and CeeDee Lamb left at halftime with a concussion. Two games against zombie Big Ben with a foot in the door for retirement. Two games against Derek Carr, who has spent eight years teasing the Raiders he’s a franchise quarterback. One big game against Green Bay where Aaron Rodgers was out with COVID, forcing Jordan Love to make his first start. It didn’t go well. Teddy and Drew Lock? Please, and they actually let Lock run wild in that rematch. A huge fumble by Melvin Gordon won that game for the Chiefs.

But what happened when the improved Chiefs faced the Chargers in a first-place showdown in Week 15 and a red-hot Joe Burrow with the No. 1 seed in contention in Week 16? The defense did not perform well. Mahomes and the offense had to rally in Los Angeles, hope for some Chargering, and got the ball first in overtime to end it 34-28. Despite leading by double-digits multiple times in Cincinnati, the Chiefs gave up 34 points and the game-winning drive to end it after committing multiple penalties again. The defense even allowed a third-and-27 conversion for 30 yards to Ja’Marr Chase.

So, the over/under is 54 points and you can see why with the way these offenses are capable of lighting it up, and neither defense is exactly reliable against what would be considered a good offense this year.

The Chiefs are undeniably playing better defense than they did to start the season when they were arguably the worst in the league. But is this a championship-caliber defense like 2019 was? After seeing the games in Week 15-16, I say no. But they’ll have a great opportunity to prove it on Sunday, as will Buffalo’s top-ranked scoring defense. I said last year that if the Bills could combine their 2020 offense with their 2019 defense, they would win the Super Bowl. The 2021 Bills, Jacksonville loss be damned, are trying to be that team.

The Prediction

In the preseason, I picked the Chiefs to get back to the Super Bowl. But it’s really hard to get back to a third in a row, especially coming off such a brutal 31-9 loss. We’ve already seen the Chiefs lose this year to the Ravens, Chargers, Bills, Titans, and Bengals. They are 0-3 against the remaining playoff field in the AFC. I think this is the week where having the bad-bounce turnovers and giving up too many plays to good offenses combine to hurt the Chiefs and send the Bills to the next round and a step closer to that elusive Super Bowl win.

My detailed prediction: I see the Chiefs leading 27-24 late as KC and under bettors are sweating bullets. Allen finally puts his gaudy fourth-quarter stats to use this year and leads the first game-winning drive of the season for a touchdown in the final minute.

Is it the ending I want? No, but if the early game on Sunday goes my way, I can watch this one in peace and be satisfied with anything that happens.

Final: Bills 31, Chiefs 27

NFL Stat Oddity: 2020 Divisional Round

The divisional round is no longer going to be my favorite week of the NFL year if the games are going to start looking like this every season. You know it was a rough slate when Jared Goff kept up his end of the bargain to make that game in Green Bay the best played from the quarterback position this weekend.

Lamar Jackson and Patrick Mahomes, the last two MVP winners, will not be having their first postseason meeting in the AFC Championship Game next week. Both quarterbacks left their games in the third quarter after suffering a concussion. If Jackson’s didn’t occur on a freak play after a bad snap and while he was already down 17-3, this weekend might have caused a referendum on the usage of quarterbacks in the running game. For decades, the argument was that you cannot run college-style plays or the speed-option at the professional level without getting your quarterback killed.

Well, Andy Reid almost got his quarterback killed, nearly killing his team’s wonderful season in the process. Mahomes is reportedly doing okay, but of course they are going to say that, so who knows what will happen next week. The Chiefs were fortunate to survive the Browns by a 22-17 final. Still, it has to make you think about when your quarterback should get the greenlight to run and when he should stick to passing and only running out of necessity.

Maybe Jackson-Mahomes wouldn’t have been a great title game anyway. You know, these big-time quarterback matchups rarely play out as great performances by both players. Just look at the combined 85-year-olds in New Orleans on Sunday, which is where we must start for I am willed by Him to do so.

Previous weeks in Stat Oddity:

Buccaneers at Saints: The Swansong for Drew Brees You Hate to See

It took a record 10 games, but this postseason finally had a second-half lead change and a game-winning drive in the fourth quarter. If I told you it was a Tom Brady-led team beating a Drew Brees-led team, you probably wouldn’t be surprised by that part.

However, I am sad to say this was not the result of Brees’ defense blowing a late lead in explicable fashion, or wasting one of his go-ahead drives again, or any obscene officiating error in the final minutes. I can’t even blame Taysom Hill for a failed gadget play, because he was inactive with an injury.

No, this game fell largely on Drew Brees, who had his worst ever playoff game by far with three interceptions and just 134 passing yards on 34 attempts (3.94 YPA). It will likely be the final game of his stellar career too as he is expected to retire even though nothing is official yet.

Based on how he looked in this one, it is time. Watching Brees unable to get any mustard on the ball any time the Buccaneers got close to him was sad. The Saints’ only 20-yard play in this game was a brilliant gadget design with Jameis Winston throwing a 56-yard touchdown to a very wide open Tre’Quan Smith, who caught both of the Saints touchdowns in the game. Alvin Kamara never scored, and Michael Thomas never caught a pass on four targets.

While Brees had a horrible game, the fact is Tom Brady wasn’t much better. In fact, this first (and last) playoff meeting between Brady and Brees looked a lot like the first playoff match between a young Brady and Peyton Manning in the 2003 AFC Championship Game. The Patriots won that game 24-14 after Manning was intercepted four times by the No. 1 defense in the snow. But the part that always gets lost in that one is how Brady also played terrible, trying to match all four of Manning’s interceptions with his own bad throws, but the Colts could not take advantage of more than one of them. I posted a video of this over eight years ago.

I could do the same thing for this game as Brady left three opportunities out there for Saints defenders to make interceptions, something they did five times against Carolina in Week 17, but zero times in the playoffs. Brady threw five interceptions against the Saints in the regular season, but again, the defense was empty in the big games here in January.

One of the missed picks was when the defensive back did not drag his second foot in bounds to secure the pass, which is noticeably different from the Buccaneers when Brady’s teammate made sure to get his footwork right on one of Brees’ three interceptions.

In classic Brady fashion, he saved the worst for the fourth quarter to cap off a game-winning drive. Marshon Lattimore jumped Scotty Miller on a third down and nearly picked Brady off with a diving attempt. Even infamous QB apologist Troy Aikman had to note how he got lucky there. The Buccaneers instead kicked a 36-yard field goal to take a 23-20 lead. Brees was intercepted five plays later on what may have been a miscommunication with Kamara down the field.

For the third time, Tampa Bay had great field position and turned it into a touchdown to make it 30-20 with 4:57 left. If Brees had one more miracle in him, and this would have been a huge one, he had to score quickly on a day where the big plays just weren’t happening for him. Four plays into the drive, his third interception came on a pass deflected off Jared Cook. So you had one that looked woeful and late, one that looked like miscommunication, and one that was just a bad luck deflection.

And that might be the final pass of Brees’ career.

There is plenty of valid criticism to aim at Brees for this performance. The 3.94 YPA is his second-lowest in a game with the Saints (he was at 3.87 against the 2013 Seahawks on MNF). The fact that Winston had to come in to throw the deep ball on the gadget is a bad look for him too.

However, this idea that one quarterback outplayed the other because he was more “clutch” or is a better “winner” is the same type of horseshit that was shoveled after the 2003 AFC Championship Game with Manning and Brady.

This game was about two old quarterbacks playing like shit against good defenses, but only the Tampa Bay defense made big plays to get turnovers. The Saints couldn’t get one despite three offerings.

The other annoying part is that the biggest play of the game was a Jared Cook fumble in the third quarter, another play that has nothing to do with either of these quarterbacks.

The Saints were leading 20-13 in the third quarter and looked to be driving again with Brees converting on a third down into Tampa territory, but Cook had the ball knocked out. Instead of taking a two-score lead, the Saints were at their own 40 and couldn’t keep the Buccaneers out of the end zone from tying the game.

That was the killer turnover in the second half, but the first three turnovers for the Saints set up Tampa Bay in incredible field position. The Buccaneers only had to move 63 total yards on their three touchdown drives (3, 40, and 20 yards). On the eight drives that did not start in Saints territory, the Bucs had no touchdowns.

I had to look it up, and sure enough, this puts the game in rare territory for field position. The average touchdown drive in the playoffs is about 65 yards. This is only the fourth playoff game since 2001 where a team had three touchdown drives that started inside the opponent 40. Three of the four games involve Tom Brady, though not quite like you might think.

2014 AFC Championship Game, New England vs. Indianapolis: It’s the Deflategate game. The Patriots had touchdown drives of 26, 13, and 40 yards, but at least they had other long drives too in a 45-7 win.

2005 AFC Championship Game, Pittsburgh at Denver: The Steelers had touchdown drives of 39, 38, and 17 yards. They did have an 80-yard touchdown drive in the second quarter too in a 34-17 win.

2005 AFC Divisional, Denver vs. New England: How did Denver get to that Pittsburgh game? They beat Brady and the Patriots the week before. They did it with touchdown drives of 40, 1, and 15 yards. They had no other touchdown drives, meaning the 2005 Broncos and the 2020 Buccaneers are the only offenses in the last 20 postseasons to have three touchdown drives start inside the 40 and nothing longer. The kicker is the only reason this isn’t Tampa Bay alone is Denver’s 1-yard touchdown drive that was the result of a Brady interception returned by Champ Bailey that Ben Watson miraculously tracked down and saved from being a pick-six. If not for that Brady error that looked similar to what Lamar Jackson did on Saturday night, Brady would be the only quarterback of his era to have a playoff game where he needed so many short fields to score his touchdowns. I wish I could make this stuff up.

It is hard for me to see the Bucs winning this one without those turnovers producing such amazing field position. Brady was not able to pass for 200 yards on this defense. The loaded receiving corps of Mike Evans, Chris Godwin, Rob Gronkowski, and Antonio Brown combined for 61 yards. That’s it. It was Tyler Johnson who had the big catch of the day, stretching out for a 15-yard gain on 3rd-and-11 on what became the game-winning drive instead of a three-and-out. Scotty Miller then chipped in the only 20-yard catch of the game by coming down with a 29-yard gain.

What a disappointing game, but it should have been expected. When do you really see these big QB battles play out as being shootouts or with both players playing at a high level? Brees and Manning once delivered a pretty good Super Bowl, but more often than not, these games are one-sided (think Dan Marino or John Elway against Joe Montana in the Super Bowl) or the quarterback play isn’t even that good and the game is decided by other factors. Hell, just look at these three Brees-Brady games this year. They both sucked in the first and third games, and Brady was horrific in the second while Brees played very well in the 38-3 rout.

But this is the only Saints-Bucs game people will remember from 2020, and that is the unfortunate part for Brees, especially if it proves to be his swansong. Now it’s up to the Packers to see if they can reverse the 38-10 outcome the way Tampa Bay recovered from 38-3 in this game.

But remember, for all the hype to come with Brady vs. Rodgers, it’s unlikely to be a game where both quarterbacks play great. It didn’t happen in 38-10. It didn’t happen when they met in 2018. If we’re lucky, it will look like the 2014 game, which Rodgers and the Packers won 26-21.

Browns at Chiefs: Andy Reid Kills Season Before Bringing It Back to Life

For the second year in a row, the Chiefs’ Super Bowl hopes hinge on the health of Patrick Mahomes. Last year it was a dislocated kneecap in Week 7 that only ended up costing him 11 quarters. This year, if he misses even one game it could very well mean the season is over for the Chiefs. When I warned that “one mistake could end the season” for this Chiefs team with all their nail-biting finishes, I certainly never thought it would mean a concussion that left Mahomes, who was already grimacing through a toe injury from the first half, visibly shaken and out of sorts.

This was a tough game to watch, but it was nice seeing the Chiefs operating on offense as if it hadn’t been three weeks since the starters last played. Mahomes led two 75-yard touchdown drives to start things, but the touchdown pass to Travis Kelce is where the toe injury happened, leading to his first trip to the blue medical tent. You could see it start to affect his planting and throwing on the next drive, which ended in a field goal. The Chiefs tacked on another field goal to end the half, scoring 19 points on four first-half possessions just like No. 1 seed Green Bay did on Saturday.

The Browns could have started this game with the ball and try to take a 7-0 lead before Mahomes took the field for the first time in three weeks, but they deferred to the second half. I hated that decision, and sure enough, it didn’t help them out. Baker Mayfield threw an interception three plays into the third quarter and this looked like a rout was on. However, the Chiefs didn’t get a first down and Harrison Butker missed a 33-yard field goal after already missing an extra point terribly to start the game. Those four points could have been huge too. The quarter basically reset, and the Browns were able to find the end zone without fumbling through it like Rashard Higgins did late in the second quarter. One of the dumbest rules in the game got Cleveland in a big way, but at least Browns 2.0 fans have a new version of “The Fumble” to call their own.

Still, the Chiefs led 19-10. That’s when the outlook changed as Mahomes kept the ball on an option run and was hit awkwardly. He struggled to get up and had to be helped off the field. This looked like an obvious concussion and you just figured his day was over, but hopefully not his season.

First, I have to say this was a horrible call to make in this game. Mahomes clearly was not 100% after the toe injury. Why would you have him run an option play on a 3rd-and-1 at the Kansas City 48 in a 19-10 game in the third quarter? Mahomes scored a little touchdown to open the game on a similar play, but I can live with that. It was to score. This was, at best, going to get a first down at midfield, and he didn’t even convert it. The Chiefs have to be smarter than this, and it’s a joke that they would be content with this call when they are afraid to use Mahomes on a quarterback sneak, the most effective short-yardage weapon in the game, because Mahomes was injured on one in 2019.

Well, he’s injured again, and it will be questionable if he’s cleared and able to play well next week in the AFC Championship Game. Again, save the designed runs for the big spots like icing the game at the end, converting a fourth down, or scoring a touchdown. The risk there was not worth it.

This game only had 15 possessions, which makes the 22-17 final look misleading as to how well the offenses played. Cleveland had an 18-play touchdown drive after the Mahomes injury to pull within five. Enter Chad Henne, the veteran who has really nothing to show on his lengthy resume in the NFL, but hopefully this will be the one bright spot. It started well with big completions to Hill and Kelce, but then Henne got greedy on a first-and-25 and air-mailed an easy interception in the end zone. Really? He’s just going to lob that one up there on first down close to field goal range? Isn’t the whole point of a backup quarterback to take care of the ball? But it would show that Reid was not afraid to take some chances with Henne in the game.

Now the Chiefs had to get a stop on defense with 8:00 left. This is a spot where I said they weren’t tested much at all this season because of how successful Mahomes was at leading the offense with a one-score lead. If Mahomes was in the game, the Chiefs would probably add a field goal or touchdown to that 22-17 lead and feel safer about closing things out. But Henne threw the pick and it was clenched ass time.

Frankly, the Browns sucked here, and I’m not even talking about Jarvis Landry setting a WR playoff record for the fewest receiving yards (20) on at least 7 catches. Kareem Hunt looked like the livelier, fresher back than Nick Chubb did. I would have gone to Hunt on this drive, but the Browns were still infatuated with short Chubb runs and trying to get him involved in the passing game, which isn’t a strength of his. Maybe the screen last week in Pittsburgh (40-yard TD) proved to be fool’s gold for Cleveland as Chubb had 4 yards on five targets in this game. On a 3rd-and-11, Mayfield checked down to Hunt for 2 yards to set up 4th-and-9 at the Cleveland 32 with just over four minutes left.

Head coach Kevin Stefanski was really in no man’s land with this decision. It is a hard conversion and Baker was not playing that well. If you don’t get it, the Chiefs are probably able to add a field goal, which would keep it a one-possession game at 25-17. Maybe they get two first downs and run out the clock. A horrible challenge by Stefanski earlier in the quarter on a clear catch by Hill cost the team a timeout, which came back to hurt as you’d expect.

I feel with Henne in the game, you think you can get the three-and-out stop and get the ball back with plenty of time to go win the game. So I would support the decision to punt. The Chiefs stayed aggressive though with Henne twice dropping back on second-down plays, which is almost unheard of in the four-minute offense in this league. He converted one third down, but faced a third-and-14 after taking a big sack by Myles Garrett.

It felt like Mayfield would get one last chance to win the game. It seemed like the Chiefs needed to just run this one and punt the ball back with about 70 seconds left. But Reid called a pass and Henne pulled out a 13-yard scramble that came up just short of the conversion. I did not know he had wheels like that at 35. The 2013 season was the last time Henne had a 14-yard run.

This set up a 4th-and-1 at the Kansas City 48. I thought punting was the right call, because in a 22-17 game, if you go for it and don’t get it, you’re really putting the screws to yourself for a potential game-losing touchdown drive the other way. In a 25-17 game I’d go for it, maybe even in a 24-17 game I’d go for it, but not in that 4-to-6 point danger zone.

It looked like the Chiefs were just going to try to draw the Browns offsides, but to the shock of everyone, they snapped the ball with 5 on the play clock and Henne threw a quick pass to Hill for the game-sealing first down.

That took some balls.

Balls we really haven’t seen before. I cannot find a play, regular season or playoffs, since 1994 where an offense threw a pass on fourth down in their own territory in the final 80 seconds with a 1-8 point lead that wouldn’t have been the final snap of the game. Sometimes you’ll see a team do this on fourth down just to run out the clock instead of punting. Drew Lock did this for Denver this year against Miami and actually ended up completing the pass to Tim Patrick for 61 yards.

So good on Chad Henne. Let his NFL career be remembered by this moment instead of him being probably the last player who will ever have three seasons with more interceptions than touchdowns (min. 400 attempts).

We sure do not want to see him start next week against Buffalo with the Super Bowl on the line. If worst comes to worst, then Reid will just have to cook up his greatest recipe yet to outscore the Bills.

Just leave the runs to Henne’s discretion.  

Ravens at Bills: 17-3, But Of Course

“Instant classic,” he said. “These franchises finally have exciting quarterbacks,” he said.

Leave it to the Ravens and Bills to tease us with recent 500-point seasons, hot winning streaks leading up to this matchup, and then to shit the bed on Saturday night and give us a jittery 17-3 game with one offensive touchdown. It is the fourth-lowest scoring playoff game in the 32-game era.

It was sitting in a tie with the lowest scoring playoff game since 2002, a 10-3 loss by Sean McDermott’s 2017 Bills to Jacksonville, until Lamar Jackson threw a pass that, fairly or not, will define where he is as a big-time quarterback in this league.

Down 10-3, Jackson was leading his best drive of the night when he saw the field poorly and forced a pass on third and goal from the 9 that was intercepted and returned 101 yards for a touchdown by Taron Johnson, tying the longest pick-six in playoff history.

Oddly enough, it’s the first time a quarterback has thrown a pick-six in the third quarter of a playoff game while trailing by 1-7 points since Dan Marino did it against the 1997 Patriots. That game also ended 17-3.

That was going to force Jackson into the biggest comeback attempt of his career, but it all ended two snaps later when another piss-poor snap by center Patrick Mekari had to be gathered by Jackson to save points for his team. Jackson hit his head after throwing the ball away best he could (still a grounding penalty), which caused the concussion and knocked him out of the game. The Ravens couldn’t score anything with backup Tyler Huntley.

Look, it was a weird game. There was no snow, but there was some wind, though it seemed to bother the kickers more than anyone with both missing a pair of kicks in the 41–46 yard range. You know it’s not your night when Justin Tucker misses two field goals under 50 yards for the first time in his career. There were at least three terrible snaps by Mekari that hurt the Ravens. What is it with these AFC North centers this postseason? Jackson had one brilliant scramble drill where he found J.K. Dobbins with a pass on third down, but Dobbins dropped it as he’s not used to catching the ball in this offense. That ended drive No. 2 on the night, but let’s just say I had my doubts that the Ravens would have made it the last 75 yards to score a touchdown.

The wind didn’t seem to bother the Bills from giving Josh Allen the ball 25 times as opposed to one handoff in the first half. The Bills are the first team in NFL history to not register a rushing attempt in the first quarter of a playoff game. The Bills ended up finishing with 9 carries for 29 yards. Frankly, I don’t think this extreme pass-happy approach worked that well and would not advise it for their game in Kansas City. One thing is clear though: Stefon Diggs is a beast. He had 106 yards and the game’s only offensive touchdown after the Ravens left a clear mismatch in numbers (3 vs. 2) on a screen that was too easy for Diggs.

Baltimore’s sloppy night was a big disappointment for John Harbaugh’s team, but the attention is going to go on Jackson and the offense, and I would say rightfully so as we are now seeing a clear pattern here with this team.

Jackson has started six games where the Ravens trailed by at least 14 points (0-6 record). Half of them are the three playoff losses and two more are his last two games against the Chiefs. How does this team ever expect to get to another Super Bowl if they can’t score points in the playoffs and keep up with Mahomes, Allen, and anyone else on the rise in the AFC?

Is this style of offense still capable of delivering in the playoffs? Baltimore started this game with three nice runs for 32 yards, looking like business as usual for this offense. But the Bills tightened things up and the run was not as effective as usual, especially for Jackson who had 34 yards on nine runs.

When will the Ravens try to throw the ball more like a normal offense in today’s game? In the second quarter, Jackson had just made his best throw of the night, picking up 21 yards on a 3rd-and-18 to Marquise Brown. Two plays later, he kept the ball on a zone-read and had to eat it in the backfield for a 4-yard loss. It totally blew up the drive and the Ravens had to punt. I love his scrambles and think there are spots to take advantage of the designed runs, but a first down after you’ve finally hit a big throw is not the place for that.

After the game, slot receiver Willie Snead had some interesting comments about Jackson’s career progress, hoping this will be a wake-up call:

While Snead may have called Jackson an elite passer first, he’s clearly not a believer of that yet and thinks it’s on Jackson the most to improve there. He’s right too. The idea that you can just acquire a wide receiver and he’s going to automatically fix your ability to throw with accuracy and read the defense and make good throws to other receivers is nonsensical. Diggs was great for Buffalo this year. He still had barely more than a quarter of the targets. Allen had to make a lot of leaps in his third year and he did. Jackson seemingly has not when it comes to being a passer.

Once is an accident, twice is a coincidence, three times is a pattern.

This is the third year in a row where Jackson has led the Ravens to their season low in points in the playoffs.  This is considering only games he started. It is now 17 points against the Chargers in 2018, 12 points against the Titans in 2019, and three points in this game. Even if Tucker made his field goals and Jackson wasn’t concussed, what’s the most realistic total for them to score here? Seventeen maybe? That’s usually not going to be good enough.

Meanwhile, Jackson has led the Ravens to 20+ points in 37 of his 41 career starts. Three times he has failed to do it in the playoffs, and the only regular season game was the 23-17 loss in New England in heavy rain this year.

So part of the reason this fact exists is because Jackson sets such a high bar in the regular season. If he had a regular season dud where they scored nine points, then it would be easier for him to not set the season low in the playoffs. Still, this is a higher-scoring era and 2020 was the highest-scoring season in NFL history.

What really gets on my nerves is that Peyton Manning is now the go-to comparison for a quarterback who is struggling to win playoff games like Jackson (now 1-3) is. This is because Manning started 0-3, but if you know anything about those first two games especially, you know that he didn’t play poorly. He actually had leads while Jackson never led (not even 3-0 in the first quarter) in his three playoff losses. Jackson also has seven turnovers in four playoff games. Manning had two turnovers in his first five playoff games, and they came against the 2002 Jets when his team trailed 34-0 and 41-0 in the fourth quarter.

Manning’s early losses also weren’t season-lows in scoring for the Colts like these games have been for Jackson, and he never in his career had a season-low in scoring in back-to-back postseasons.

In fact, here’s how often some recent top quarterbacks (plus one elite name) have fared at having their season-low scoring game in the playoffs. You’ll see that Jackson’s three-for-three is a huge eyesore. It’s as many times as Manning, Rodgers, and Roethlisberger combined.

  • Lamar Jackson: three times in three postseasons (2018, 2019, 2020)
  • Joe Flacco: once in six postseasons (2009)
  • Tom Brady: five times in 18 postseasons (2005, 2007, 2011-T, 2012, 2019-T)
  • Peyton Manning: three times in 15 postseasons (2002, 2004, 2013)
  • Aaron Rodgers: zero times in 11 postseasons
  • Ben Roethlisberger: zero times in 11 postseasons
  • Drew Brees: once in 10 postseasons (2020)
  • Russell Wilson: once in eight postseasons (2015; still won game 10-9)

This has happened once to Cam Newton (Super Bowl 50) and Deshaun Watson (2018) and twice for Andrew Luck (2012-T, 2014-T) as well. However, it only happened once to Andy Dalton (2013-T) in his four postseasons despite the 0-4 record.

Until Jackson shows us otherwise, he is closer to Andy Dalton in the playoffs than he is Peyton Manning (or Joe Flacco for that matter.)

Rams at Packers: No. 1 Nothing

When I previewed this game, I wanted to stress that No. 1 defenses are known for doing great in the playoffs because of their success in Super Bowls (6-1) against No. 1 offenses. However, if a team made the Super Bowl, that means they already delivered in the postseason a couple times, probably because the defense was great, and probably because the offense didn’t screw them over.

No one wants to point out that the No. 1 defense was only 3-5 (now 3-6) against the No. 1 offense in earlier playoff rounds such as this game on Saturday in Green Bay. The expectations were that the Packers would score too much, and the Jared Goff-led Rams couldn’t possibly keep up.

Well, that did happen. It wasn’t 44-3 like the 1993 Giants/49ers matchup, but the Packers won 32-18 in a game that never felt overly close despite the Rams having a fourth-quarter comeback opportunity at one point.

However, I am more disappointed with the Rams No. 1 defense than I am the No. 22 offense (or No. 25 on a per-drive basis). Sure, the offense only chipped in 18 points, making it six straight games to end the season for Sean McVay’s unit not scoring more than 23 points. Green Bay was very successful in coming up with four sacks in a game that had no turnovers.

But where was this great Los Angeles defense that led the league in so many categories when the Packers scored 25 points on their first five drives? The Packers had 29 seconds before halftime after the Rams cut into the 16-10 lead with a touchdown. You would think they could get to the half with that respectable margin, but the Packers quickly hit big plays to get into scoring range. Aaron Rodgers forced back-to-back throws in the end zone that should have been intercepted, but the Rams failed to come away with either of them, the first more egregious than the second. That led to a field goal and suddenly 19-10 felt like that offensive touchdown didn’t even happen.

Then to top it off, Aaron Jones breaks off a 60-yard run to start the third quarter, leading to another touchdown and a 25-10 deficit.

You’ll hear about Aaron Donald’s rib injury and that he was limited, but this goes well beyond Donald, who was ineffective when he played and even hurt his team with a 15-yard penalty in the first half that wiped out a 3rd-and-7 situation.

The 2020 Rams defense allowed season highs in:

  • Yards – 484 (only game over 400)
  • Rushing yards – 188 (only game over 140)
  • Passing yards – 296 (only game over 275)
  • First downs – 28

Is this what happens when over half of your schedule was the NFC East, an injured Kyler Murray, the Jets (still lost to them), Broken Cam Newton, and getting Seattle three times during its second-half offensive slump? The Rams even drew Tom Brady and the Buccaneers during the stretch where he couldn’t hit a deep ball to save his life.

That’s why I wrote in my preview that Buffalo was the only comparable top offense to Green Bay that the Rams faced this season. What happened that day? They allowed 35 points and were shredded by Josh Allen. What happened this time? Rodgers put up 32 points on nine drives and the final drive was just running out the last five minutes on the clock.

If the 2020 Rams wanted to be a legendary No. 1 defense, they would have showed up in these games against Buffalo and Green Bay instead of making those offenses look better than their average output.

Maybe things would have been a hair different if Donald was 100%, but the Rams had little pressure and no sacks of Rodgers. More glaring was the way the run defense failed in the worst way this season. Green Bay’s success in that department arguably put the game away. After the Rams had the ball with a 25-18 deficit in the fourth quarter and punted because of another sack on Goff, the defense needed to get a second straight stop to have any hope. But on a second-and-6, Rodgers used play-action to set up one of the few deep pass attempts of the game. He hit it to an open Allen Lazard for a 58-yard touchdown. Green Bay led 32-18 with 6:52 left and the game was essentially over there. Goff took his final sack on a fourth down and the Packers ran out the clock.

Any time the Rams looked to have made some traction in this game, they would take a step back, like a false start penalty when they were going to go for a fourth down, having to then settle for a field goal. Another inexcusable spot was McVay calling a timeout on 3rd-and-16 in the fourth quarter instead of just taking the delay of game and saving the timeout. Worse, Goff threw a short pass that had no hope of converting and only ran more time as the Rams punted. Five plays later, Rodgers hit the dagger to Lazard.

I am not sure anyone in these playoffs could beat the Packers without scoring 30-plus points, but I like to think these other defenses would give it a better effort than the Rams’ “No. 1 defense” did on Saturday.

As for the Rams going forward, it could be tough to get back to this point. Goff is limited obviously, though I think he played better than expected in this one. The offense only had eight drives and wasted too many of them and he could have had better protection. At least Cam Akers seems to be the solution at running back, and it would be nice if Cooper Kupp (injured again) could stay healthy for a playoff run. He didn’t in 2018 either.  

Now the Packers get to prove that 38-10 in Tampa Bay was the outlier of the season. I have to preview this game twice this week so there’s no point in talking about it now, but let’s just say the stars seem to be aligning for the worst postseason I could imagine.

I guess that’s what I get for enjoying last year’s so much.

NFL 2020 Divisional Round: Buccaneers at Saints

The New Orleans Saints hope to extend Drew Brees’ career at least another week by completing the season sweep of the Tampa Bay Buccaneers.

For previews of Saturday’s games, click here.

For Browns-Chiefs, click here.

Buccaneers at Saints (-3)

Let’s get the 3-0 sweep part out of the way first with New Orleans looking to put the cherry on top of their 34-23 win in Week 1 and 38-3 win in Week 9 over Tampa Bay this season.

Going for the 3-0 Sweep

Yes, it is hard to beat a playoff team three times in one season. Beating a playoff team once is usually harder than average, and then to do it three times to a team that has to come from your division, who knows you so well, is certainly a tough task.

But the only time we ever talk about this is when a team has already won the first two games. By the playoffs, the brooms are already two-thirds of the way out.

Since the merger, a team has gone for the three-game sweep 21 times and is 14-7 at pulling it off. The sweep happens two-thirds of the time. It just so happens that the 2017 Saints are the last team to pull it off against Carolina, winning the NFC wild card game 31-26.

That was a good playoff win for the 2017 Saints when you consider that the home team is 1-5 in the last six playoff games between division rivals regardless of how the regular season series went. As we just saw with the Steelers-Browns in Week 17 and the wild card round, these rematches can look dramatically different, so the Saints cannot take too much faith in Week 9’s 38-3 obliteration of Tampa Bay.

Some other facts from this table:

  • The 2020 Saints outscored Tampa Bay by 46 points so far, the largest scoring differential for all 22 series.
  • The three teams with the largest scoring differential before the Saints went 0-3 in the playoffs: 1989 Oilers vs. Steelers (+34), 1994 Vikings vs. Bears (+34), and 1998 Cowboys vs. Cardinals (+35).
  • Those same three teams all happened to have the largest Game 1 margin of victory, winning Game 1 by 27+ points, only winning Game 2 by 6-7 points, and then 0-3 in the playoffs.
  • It would appear dominating the earliest matchup in the season has less relevancy for the playoffs.
  • The three teams who won Game 2 by 17+ points were 3-0 in the playoffs with a double-digit win each time (1999 TEN-JAX, 2000 NYG-PHI, 2009 DAL-PHI).
  • New Orleans’ 38-3 win in Game 2 over Tampa Bay is the largest margin of victory in any of the 65 games in the chart.
  • The only three teams before the 2020 Saints to win both games by double digits were 2-1 in the playoffs with wins for 2000 Giants-Eagles and 2017 Saints-Panthers and a loss for the 2007 Cowboys-Giants.
  • The 2-0 team is 7-5 in the wild card round, 3-1 in the divisional round, and 4-1 in the conference championship.

Basically, the only example that really compares to what Tampa Bay is trying to do here is the 2007 Cowboys-Giants. That’s the only one where a team lost both games by double digits before winning on the road in the playoffs. That’s also the only one where the 0-2 road team won after the wild card round. When the 1983 Seahawks lost to the Raiders in the AFC Championship Game, that game was played in Los Angeles because the Raiders (12-4) were a better team than Seattle (9-7), which just happened to get the best of them in the regular season before upsetting a rookie Dan Marino as well in the divisional round that year.

New Orleans having a home letdown in the playoffs wouldn’t be a new story, but the Saints are better than the Buccaneers.

Or are they?

So Which Team Is Better?

Thanks a lot, COVID-19, for this weird season. The Steelers were the last unbeaten at 11-0 and led the league in scoring differential for a while until falling off hard. Baltimore finished No. 1 in scoring differential despite only going 11-5 and No. 7 in DVOA (but No. 3 in SRS at Pro Football Reference). The Chiefs had the best record locked up with 14 wins before resting starters and getting their ass pointlessly kicked by the Chargers, so they finished 6th in DVOA, 6th in SRS, and not even in the top five for points scored. Green Bay scored the most points but finished No. 5 in SRS and No. 3 in DVOA. Buffalo is basically the Josh Allen cautious wave meme here, just chilling in the crowd.

Yet the place where DVOA and SRS seem to agree this season is that the Saints are No. 1 and the Buccaneers are No. 2, and the margin between the two isn’t that great despite the scoreboard difference in their first two meetings this season.

Frankly, I don’t know what to make of these numbers. I wish I had a better explanation for what the advanced stats sees in the Saints and Bucs this year. I think the Chiefs and Packers are more reliable to score points and win games this season. I think the Ravens are scarier to play than the Bucs or Saints. I think the 13-3 Bills, who have one loss on a Hail Mary and another to the Chiefs, have played better football than those teams as well this year.

Here are some things I do know the Saints and Buccaneers share in common this season:

  • Both lost to the Chiefs by three points after trailing by 14+ points.
  • Both had a 17-point comeback win in October over the Chargers, who hand those out as freely as mints on hotel pillows.
  • Both swept the Falcons and Panthers, who couldn’t win a close game to save their lives.
  • Both helped put the Vikings out of their misery in December. Alvin Kamara scored six touchdowns and it felt like Dan Bailey missed six kicks when he played Tampa Bay.
  • Both got to play in arguably the two biggest COVID farces of 2020: Saints beat Denver 31-3 after the Broncos were told the day before the game that none of their quarterbacks were eligible to play. They had to start a practice squad wide receiver at quarterback and completed one pass. The Buccaneers destroyed a Detroit team 47-7 in Week 16 after much of the coaching staff was out for COVID on short notice. It got so bad that Blaine Gabbert came in the third quarter and still threw two touchdowns on his first six throws.
  • Tampa Bay also sort of won in Denver without facing a quarterback when the Broncos played Jeff Driskel and Brett Rypien in Week 3.
  • Both beat a cupcake in the NFC wild card after the Buccaneers drew the 7-9 Washington No Names with MAGA Heinicke pulling out a 300-yard game on them, and the Saints jogged through a 21-9 win over Mitchell Trubisky and the 8-8 Bears.

Where did the Buccaneers and Saints differ this year?

  • New Orleans lost in the Raiders’ first game in Las Vegas while the Buccaneers pulled away late in a 45-20 win.
  • The Saints beat the Bears in overtime while Tampa Bay lost to Nick Foles in October.
  • Tampa Bay destroyed Green Bay’s No. 1 offense in a 38-10 victory while the Saints lost 37-30 at home following some Taysom Hill Hijinks.

And isn’t that always the difference this year when we talk about Tampa Bay? It’s that 38-10 Green Bay game, Tampa Bay’s only win against a team with a winning record. Otherwise, they are 0-4 against the Saints, Chiefs, and Rams, and even lost to the 8-8 Bears. The once 0-13 Jets still have more wins (two) against winning teams this year than the Buccaneers (one).

That is why Tampa Bay feels like such a paper tiger to me this year. They fatten their stats, especially on offense, in recent weeks against the Falcons (twice) and Lions, and then they draw a Jack Del Rio defense in the playoffs. Tom Brady has destroyed Del Rio his whole career and last week was more of the same with Washington leaving receivers wide open and getting minimal pressure.

So is Tampa now peaking, or is it just heavily related to the opponents? When they last played legitimate playoff teams in the Rams and Chiefs, they lost 27-24 at home in both games, outgained and outplayed.

For a team with some gaudy stats, the Buccaneers have had a lot of rough patches this season, rarely able to put in a complete game effort until recent weeks. In fact, the Buccaneers have five games this season where they trailed by at least 17 points, something Brady rarely experienced in New England.

They were able to come back and beat the Falcons and Chargers, because of course they were. That’s what those teams do. But Tampa didn’t beat the Chiefs or Saints in the other three games. Tampa Bay has trailed by 17+ in more games this season than the Packers, Chiefs, Bills, and Ravens combined as those teams have one game each. The Saints have two, and the Rams and Browns have three each.

This got me curious. How many games would you expect a legitimate Super Bowl team to fall behind by at least 17 points during a season? So I dug out the answer back to 1994, the start of the salary cap and two-point conversion era. As it turns out, Tampa Bay would be the highest.

The Super Bowl winner averages 1.4 such games a season and the Super Bowl loser averages 2.0 games a season.

No Super Bowl teams since the 2009 Colts and Saints have had more than two three-score deficits in the regular season. Even that’s misleading as both teams rested their starters in Week 17 to tally a third. The 2012 49ers actually had two in a row in the playoffs, but came back to beat the Falcons (duh) before losing to the Ravens in the Super Bowl. The 1994 Chargers, 1998 Falcons, 2000 Giants, 2002 Raiders, 2010 Steelers, and 2013 Broncos also had their last one of the season in the Super Bowl loss.

The only Super Bowl winner with a legitimate three games of trailing by 17+ is the 2007 Giants, which might not surprise you. The 2011 Giants played high-scoring, close games, but the 2007 Giants got their ass kicked a few times. Funny how this is the second time we’re bringing them up as the hopeful comparison for a Brady team since his 2007 Patriots are responsible for those Giants’ spot in lore.

The 2006 Colts, 2016 Patriots, and 2019 Chiefs are the only teams to win a Super Bowl after trailing by 15+ points in the playoffs. That is true for all time and not just since 1994. You know which games…

Green Bay may very well be the next challenge for the winner of this game, but for this week, it comes back to the crowning achievement of New Orleans’ season to this point: sweeping Tampa Bay.

Third Time the Charm?

If anything, the Saints should be expected to pull off this sweep, and FiveThirtyEight actually has them at 71% to win with an Elo point spread of -6 instead of the game’s -3 spread.

Yet why do I have this terrible feeling that Brees will have to go out having one postseason (2009) in his career with multiple wins?

Oh yeah, it’s the playoffs, and the rationing of luck among Tom Brady and every other great quarterback of this generation feels like this:

I bitch about Brady getting multiple chances to lead one late scoring drive to win a game. Now he’s getting a third chance to beat the Saints one time, and it may come in the way that I have dreaded since the 2018 season.

Sean Payton, here’s your opportunity to hand Brady a playoff win after going to Taysom Hill with the game on the line. Please don’t use it.

Jokes aside, thirteen months ago, I wrote about the lack of luck Brees has had in his career, especially in comparison to Brady. I pointed out how just five plays in his career that had nothing to do with him could have drastically altered things to the point where he might be 5-0 in Super Bowls, with a few wins over Brady himself, and going for a sixth ring this year.

Instead, Brees is 9-8 in the playoffs, meeting Brady there for the first time, and it’s probably his last game ever if he loses it. Even with a win on Sunday, there will always be some disappointment there.

So what can change from the first two meetings? I watched them both live and the Saints were absolutely the better team. I was behind the argument that Week 1 wasn’t that telling with Brady making his Tampa Bay debut after no real offseason or preseason. Brees and the offense actually weren’t that great at all in that matchup either. He struggled to move the ball too, but Brady threw a pick-six and struggled after the opening drive.

Flash forward to Week 9. The Saints were grinding out close wins against so-so teams. The Buccaneers were a few weeks removed from 38-10. They just activated Antonio Brown, because god knows you have to give the GOAT four different 1,300-yard receivers to make this offense shine. I picked the Buccaneers to win that rematch, and I couldn’t have been any more wrong.

That 38-3 game was the most one-sided domination I watched this season. It was about as perfect a game as you can have on offense and defense. Brady wasn’t able to complete passes, he started throwing interceptions, the Saints were getting anything they wanted on offense. Only some mistakes by Jared Cook kept that from being 45-0 at halftime. Tampa had to kick a cheap field goal late to avoid the shutout. The Buccaneers set an NFL record with only five rushing attempts. It was incredible.

But now, what changes this week?

Brees had his rib injury start in the Tampa Bay game. He missed four games, but he’s about to make his fifth start in a row. He had that really rough start against the Chiefs before finding his way back later in the game. In the last three weeks, he’s pretty much back to where he was, leading an effective offense again that is finally healthy with Alvin Kamara, Michael Thomas, and Emmanuel Sanders ready to play. The funny thing is with all those guys together, the Saints went to Deonte Harris for seven catches and 83 yards against the Bears on Sunday. Was that a way to not show their hand to Tampa Bay about what they might do with their normal offense in a third matchup this week? It was interesting and Harris looked good after doing almost nothing this season.

The Saints can score on this defense, but we know Todd Bowles loves to blitz. Brees faced his highest blitz count in the two Tampa games this year. He was sacked once in each game and hasn’t had a pressure rate above 23% in any game this season according to Pro Football Reference.

For Brady and the Bucs, can the Saints get to him again? They sacked him three times in both games and had a season-high 36.6% pressure rate in the 38-3 game. The Buccaneers usually protect well but have not done so against the Saints yet. Brady has also thrown five of his 12 interceptions this season against New Orleans.

While the argument of Week 1 rust didn’t work out for Tampa Bay last time, could the argument of Antonio Brown’s progress work this time? His first game was 38-3 and clearly it took some time for them to figure this offense out. Brown took Scotty Miller’s snaps after Miller started the season so well with making deep catches. Brown didn’t seem to click until he caught a touchdown bomb to beat the Falcons (of course) in Week 15. He has now scored in four straight games and looks more like the receiver we’re familiar with.

Brown’s impact could be huge if Mike Evans has his usual disappearing act in the Superdome. Evans has four games in his career with fewer than 10 receiving yards. Three of them are in New Orleans, including 2 yards in Week 1. He also had a 1-of-6 game with 13 yards in 2017. When you stack that many bad games against an opponent, it can’t just be a coincidence. This looks good for corner Marshon Lattimore, but he can only guard one guy. The Buccaneers still have Brown, Chris Godwin, Gronk, Miller, and even Cameron Brate reminded us he’s still there with 80 yards against Washington last week.

This offense just has too many weapons, and if they would ever play to their full potential, this team could go the distance. But they have to get over their biggest hump so far this year. Does Brees finally have a defense to rally around him and prevent his retirement before another ring? The Saints did not allow a 300-yard passer this season and are one of three defenses in 2020 (Rams and Steelers) to allow fewer than 275 net passing yards in all 17 games. That hasn’t been done since the 2006 Colts did not allow 250 net passing yards in a record all 20 of their games on their way to a Super Bowl win. Even though you can run on that team, which you usually can’t on these Saints, I am a bit shocked I only discovered this stat on January 15, 2021.

Nostalgia aside…

I hate to say it, but part of me expects Payton to do something really stupid in this game that gives Tampa Bay the edge. Don’t forget Bruce Arians is 32-26-1 (.551) in 4QC/GWD opportunities, so he’s had his own magic beans produce good luck over the years. Only Mike Vrabel (14-10) has a better record among active coaches.

If not Payton, could it be the refs again with the Saints in the playoffs? It blows my mind that the NFL tried one season of making pass interference reviewable, ditched it, but left nothing in place to prevent the same egregious, game-deciding call happen again at the end of a playoff game like that no-call in the 2018 NFC Championship Game. You don’t want to make PI challengeable? Fine. But at least make it subject to review by the replay system in the final two minutes of the game so we don’t see the same damn mistake again.

Not to make Saints fans more scared, but your defense now leads the league with 19 pass interference penalties this season. Tampa Bay set a record this year by being the beneficiary of 24 DPI flags. Do you see where this is going?

Do you believe my final score is legit or just another reverse jinx? I guess we’ll have to find out Sunday evening. Maybe even sooner, because if the Rams upset the Packers on Saturday, then you know which lucky bastard is going to the Super Bowl again. Bet accordingly.

Final: Buccaneers 28, Saints 24