Tag: Andy Reid

2025 NFL Stat Oddity: Week 14

~ Scott ~ Leave a comment

I said Sunday could prove to be a franchise-altering day in the AFC, and I think the results speak for themselves.

  • The Colts (8-5) have likely gone from 7-1 and the No. 1 seed to out of the playoffs after losing to the Jaguars again and losing Daniel Jones to a torn Achilles.
  • The Bengals (4-9) blew a snow game in Buffalo that should absolutely give the team the green light to fire Zac Taylor and his entire staff after Joe Burrow and company will miss the playoffs for a third-straight season.
  • The Ravens (6-7) lost at home to the Steelers (7-6), and while the AFC North is hardly decided, Baltimore still has to play the Patriots and Packers (teams competing for No. 1 seeds), and teams they just lost to at home (Bengals and Steelers on the road). If there was ever a season to force John Harbaugh out of town…
  • The Chiefs (6-7) couldn’t finish another close game against a good team and are on life support for the playoffs, needing to win out and for the Colts and Chargers to lose multiple games (actually not that unrealistic). But with how this year has gone, they’d be foolish not to make some major changes for 2026 as their AFC West reign is over and so may be their playoff streak.

I just wrote earlier this week how we’re trying to make sense of the new contenders this year and the unprecedented decline of so many contenders at once.  However, saying teams like the Bengals, Ravens, and Chiefs (Steelers too) need to make big changes for 2026 is not an overreaction to one off year. There have been things festering for multiple years there, and with the teams in dire situations going into Week 15, maybe they’ll finally realize something has to change.

As for the rest of Week 14, a lot of the games were duds as we’ve only had six comeback opportunities. In fact, the only double-digit comeback win of the last two weeks was the Bills over Bengals today, and the only fourth-quarter lead change on Sunday was Joe Burrowing throwing that pick-six in Buffalo.

This season in NFL Stat Oddity:

Texans at Chiefs: Game of the Day

You have to give the 2025 Chiefs credit. If this was their last stand for the playoffs, and that’ll look increasingly likely if the Chargers win on Monday night, then they gave the home crowd all the greatest hits to their season:

  • An embarrassing pass rush when they didn’t blitz, leaving numerous receivers wide open on third-and-longs.
  • No takeaways on defense again.
  • Harrison Butker had about the loudest doink ever on a missed 42-yard field goal.
  • Limited touches for Brashard Smith (a 7-yard run) and Tyquan Thornton (19 yards but also had a touchdown bomb knocked away in the end zone) despite showing solid play.
  • Remember when the first pass of the season was Travis Kelce running into Xavier Worthy in Brazil? The first pass here saw backup left tackle Wanya Morris suffer a game-ending injury, leaving the offensive line without three starters and placing a third-string left tackle (UDFA rookie) in his NFL debut against the No. 1 defense.
  • Mahomes led the team in rushing with 59 yards (they’re 0-4 this year when that happens).
  • Season on the line, a pass from Mahomes went right off of Kelce’s hands for an interception (third time this year).

But there were a couple wrinkles in this performance that made it stand out as the worst loss of them all this season for the Chiefs: Aggression inconsistency and dropped passes.

The Chiefs, even going back to last year, have made a habit of playing games with limited possessions, usually getting 8-9 drives a week, the lowest total in the NFL. This makes it harder on the offense as every mistake gets magnified, but they made it work better last year with clutch plays to close out one-score games. The exact kind of plays they keep failing on this year.

But this game was different. The Chiefs had a season-high 13 possessions as each team had the ball 13 times. That’s because there were a lot of three-and-out drives and quick stops. It wasn’t a game with limited possessions, so the Chiefs could stand to make some mistakes here as the defense played well even after losing top corner Trent McDuffie early.

That’s why Andy Reid’s fourth-down decision making didn’t make any sense. He let the Dallas game beat him twice, because he was criticized in that one for a fourth-down punt in a shootout with Dallas. But this wasn’t a shootout. It was a grind with C.J. Stroud playing ice cold in the second half.

Reid let the offense go for a 4th-and-1 that led to a 2-yard Kareem Hunt touchdown in the third quarter. They needed the touchdown, so that was fine. But two drives later, why settle for the 36-yard field goal on 4th-and-2 at the 18 to tie the game with 1:50 left in the third? Why not be consistent and go for it again with your offense starting to move it well and the defense playing so well? You were getting possessions.

Then the real head-scratcher: 4th-and-1 at your own 31 in a 10-10 game with 10:22 left. The Texans just punted on a 4th-and-1 at their own 35, because they knew what kind of game this was. Why didn’t Reid understand it? Instead, he let the offense go for it, and Mahomes’ pass to Rashee Rice was defended tightly by Stingley, and I couldn’t tell if it was another defensed-dropped or what. But it was a turnover on downs either way.

Now a struggling Houston offense was set up 31 yards away from the end zone, and that gave the Texans new life to get a go-ahead touchdown, which they did. That decision largely killed the Chiefs in this game.

Then in getting the ball back in a 17-10 game, Reid basically did it again, going for a 4th-and-4 at his own 41 where failure almost likely leads to a 10-point deficit with under 5:00 left. Game over against this defense. And once again, Mahomes’ pass to Rice was flat out dropped.

Surprisingly, Houston went three-and-out after that one, giving Mahomes another chance from 92 yards away and 3:44 left. After a short drop by Kelce on first down, Mahomes threw a pass that should have been a first down to him that went off his hands and right to the defense for the third pick of the night. The second one to start the fourth quarter was an arm punt on third down out of FG range and out of 4-down territory, but this one hurt and it’s something Kelce has done three times this year to Mahomes – none bigger than here.

That one was the dagger as the Texans used up most of the clock to add a field goal for a 20-10 lead with 0:30 left. From there, it was just two stat-padding completions to avoid Mahomes finishing a full game with under 150 passing yards for the first time in his career. It was the first time he threw for 3 interceptions and no touchdowns.

But look what it took to get there. Three linemen out, the backup LT going out on play 1, the No. 1 defense on the other side, and a career-high 8 or 9 drops depending how you want to count some of those plays. Those drops combined with some really poor fourth-down decision making by Reid were actually far more damaging to the game than the backup offensive line was. This wasn’t Super Bowl 55 or Super Bowl 59 all over again with constant pass rush.

This was receivers not getting open against good coverage, then when they did, not completing plays as Mahomes has never had this many drops in one game. Just a ridiculous effort in the biggest game of the year for this team.

If this was Kelce’s last playoff-contention type of game in his NFL career, he finishes it with more drops (2) than catches (1) for the first time in his career. I’d say Mahomes might be a little happy on the downlow if Kelce chooses to retire and marry the most famous woman in the world. But then when you tell me Rice, who dropped a big third-and-8 in Dallas last week in a similar clutch situation, is supposed to be his next top target, I think the Chiefs are in some long-term trouble if they don’t sort this out.

On a cold night with both teams feeling the playoff pressure, the Texans stepped up and the Chiefs did not.

Fight or flight. The 2018-24 Chiefs had it in them to get it done in these games. The 2025 Chiefs simply do not, and the shame of it all is people will look at a game like this and still blame it all on the quarterback.

As for the Texans, they have hands down the best defense in the league this season. They were also very good in 2024, so we know this isn’t a fluke. They’ve been to the playoffs the last two years, got to the divisional round both times, and if they keep playing like this, they just might be able to win out until the Super Bowl in this weakened AFC. They might be the closest team we’ve seen to the 2015 Broncos from a decade ago, and yes, Davis Mills did his Brock Osweiler-level job of saving the season with some big wins over the Jags and Bills.

From 0-3 to 8-5, DeMeco Ryans and company deserve a lot of credit for this turnaround. As for Reid and the Chiefs, they aren’t mathematically eliminated, but it sure looks dire even if collapses by the Chargers (see schedule) and Colts (Jones/schedule) are not improbable at all.

What’s improbable is thinking the 2025 Chiefs can ever get through four straight wins without screwing up a game. They haven’t done it all year, and I no longer expect them to.

It’s a lost season.

Steelers at Ravens: The Rivalry Continues, Same As It Ever Was

This may be a selfish reason to want the continued employment of Mike Tomlin and John Harbaugh for these teams, but would the Steelers vs. Ravens rivalry be the same without them? Like, imagine these teams go in the opposite direction and hire some dorks trying to cosplay as Kyle Shanahan and Sean McVay. It just wouldn’t be the same and what makes this such a great rivalry filled with hard-fought, close games.

You can always throw out the records and spreads when these teams play. Did it matter that both played like shit at home in big losses last week where they turned it over and the quarterbacks were brutal? Nope, you ended up with a 27-22 thriller between two multi-time MVPs at quarterback in their first ever meeting.

Aaron Rodgers turned 42 this week but he looked as good as he has all season. He hit a deep ball to DK Metcalf on his first pass after going an entire month without a pass completed over 20 yards down the field. I want to say he had four in this game alone. He also scored his first rushing touchdown in over four years on a third-down scramble. His movement looked much better this week as if he got a Lazarus Pit to celebrate his 42nd birthday.

Then again, the Baltimore defense has been known to help quarterbacks perk up as Rodgers passed for a season-high 284 yards while taking no sacks. He also had no running game as the Steelers finished with 15 carries for 34 yards for him. Meanwhile, the Ravens rushed for 217 yards in the loss, producing this hilarious statistic about losing a game with a huge rushing margin:

That’s Steelers vs. Ravens in the 2020s for you. More accurately, that’s the Lamar Jackson era as to this day you still have to question Jackson’s arm and ability in games like this, another big one with first place in the AFC North on the line and the Ravens having a tougher remaining schedule.

Jackson won his last two starts against the Steelers in 2024, but his rest of career numbers and moments have been poor to say the least. In this game, he didn’t break 100 passing yards until the fourth quarter as the Ravens were leaning on the ground game with Derrick Henry and Keaton Mitchell also broke a 55-yard run.

There were some bright moments for Jackson in the fourth quarter, but the Ravens never put it together for a touchdown drive while the Steelers floundered on offense late. There was a go-ahead touchdown to Isaiah Likely that was ruled a drop after Joey Porter Jr. helped knock the ball out before Likely got a third foot down or did a football move. That was a tough call without great clarity from the NFL on what a catch is in 2025.

That drive ended in no points, because after the Likely mistake on first down, the Steelers stopped Henry twice, then Mark Andrews possibly got in the way of a Jackson pass on fourth down intended for DeAndre Hopkins in the back of the end zone with 2:22 left.

But given one more chance with 1:56 left and 74 yards to go, Jackson led a very poor two-minute drill, taking 69 seconds just to move the ball 8 yards. Reaching the Pittsburgh 30 with 9 seconds left, any shot at a Hail Mary was denied when Alex Highsmith sacked Jackson to end the game and give the Steelers a 7-6 record and first place.

The Ravens have struggled to play complementary football all season, and Sunday was no different. Pittsburgh finally won a big game this year without relying on a ton of turnovers on defense. Rodgers was excellent for three quarters, and if Likely wasn’t in a funk with the end zone, it may have been wasted again by the defense.

But the Steelers have been getting the best of this rivalry, especially when the games are at their closest. That’s also why I had full confidence in Pittsburgh still finishing with a winning record, because I knew they’d never get swept by Baltimore, especially not this Baltimore team.

Now we’ll see if they can build on this win and take advantage of a home game with Miami next week. Maybe even get a break with the Bengals possibly sweeping Baltimore on Sunday to create more separation.

But the sportsbooks have finally come around to making the Steelers the favorites (-160 at FanDuel) to win the AFC North over Baltimore (+170) and Cincinnati (+1300). There’s a reason almost every 1-5 team fails to come all the way back to make the playoffs.

The Ravens are just too mistake prone this year. Similar to the Chiefs in that regard, another team in the AFC they can’t seem to beat when they have to.

Bears at Packers: Ben Johnson Was Right Again

Ever since the Bears hired coach Ben Johnson, he has done an incredible job of saying the right things time and time again. He just probably wishes he wasn’t right when he said last week that the 9-3 Bears are winning in spite of their passing game with Caleb Williams.

On Sunday in Green Bay with the No. 1 seed on the line and the lead in the NFC North, Johnson was very prescient as Williams struggled mightily early on while Jordan Love had some key passes down the field for big plays (including third downs) that paced the Packers to numerous leads in a game they never trailed.

But Williams did make some of his best plays late, and even tied the game in the fourth quarter before the Packers marched for a game-winning touchdown. I predicted a 27-20 win by Green Bay, and they were up 28-21 late with Williams driving for what could have been his sixth comeback in the final 2:00 this year as you had to think Johnson probably goes for 2 on the road the way he is from the Dan Campbell school of thought.

But after the run got stuffed on 3rd-and-1, Williams blew a good play call with a bad throw on fourth down and it was intercepted in the end zone to end the game. Just like that, the Bears (9-4) fell from the No. 1 to the No. 7 seed.

These teams will meet again in 12 days, but Williams is going to need to be a lot more efficient if the Bears are going to get a split here.

Bengals at Bills: Mr. Perfect Until He Has to Be

I can say this about most quarterbacks, but Joe Burrow is actually more likeable than his annoying fans make him out to be. Watching him on those shows like Quarterback S2 or Hard Knocks In-Season with the AFC North, you can see he’s a football junkie, a Batman fan, and just wants to win games. This league is also in need of a pocket passer who can still frequently throw for 300 yards and multiple touchdowns without being a play-action merchant.

But where things get annoying with Burrow is the nonstop nicknames and the way the media has shoved him into conversations he doesn’t belong, or pretended that he’s a clutch player. I saw the “Joe Brrr” notification from the NFL app before Sunday’s snow game in Buffalo, and it was just earlier this week where I again pointed out that Burrow and his top wide receiver duo simply don’t win games in the clutch or shootouts despite being the most expensive trio in NFL history.

Burrow also has just one comeback win in the final 8:00 of a game in his career, and Sunday was no different. My other issues with Burrow stem from him being a sack merchant, often getting into trouble by looking for the big play. It should go against his nature as a perfectionist, which I think gets him into trouble in games where things don’t go well. He’ll let it snowball and not recover from a big mistake.

It all happened again on Sunday when Burrow went from playing a really fine game in Buffalo in the snow with four touchdowns on the first six drives. It was like he picked right up where he left off with his success against the Bills in 2022-23.

But one fateful pass from the Buffalo 33 with 5:35 left, leading 28-25, changed everything for the Bengals. Burrow tried to throw a quick pass, did a weird shot-put delivery on it, and Christian Benford was there for the 63-yard pick-six to put the Bills ahead 32-28.

Is Burrow so sick of me pointing out he has one comeback win in the last 8:00 that he tried to create a situation for himself to succeed? Then on the very next play, he got picked again on a battled ball at the line. The Bills took over at the Cincinnati 29, and of course Josh Allen, who got Dalton Kincaid back at a good time, was going to take advantage of the No. 32 defense on a short field by throwing another touchdown on fourth down.

Burrow answered quickly with his fourth touchdown pass to cut it to 39-34 with 2:13 left. That drive is another example of why stats that ignore the scoreboard show Burrow doing well in this situation when it was the two drives before this that mattered more when he had the picks.

But even after his defense sacked Allen to bring up 3rd-and-15, they gave up another 17-yard scramble to Allen, who also took off for a 40-yard touchdown earlier with inexplicably no defender in sight of his path to the end zone.

This was a very winnable game for the Bengals on the road to keep their season alive, but Burrow picked the worst time to make his worst play of the year. He crumbled instead of finishing the game, and given his history, it’s not that surprising.

He’s just not proven to be a closer yet, and this will be his third-straight missed postseason.

I still contend this is the worst Buffalo team since 2019, but if this is an AFC where they don’t have to worry about the Chiefs at all, don’t have to worry about going to Baltimore, and don’t have to worry about these Bengals, then Allen has no excuses left to not get to a Super Bowl.

Letting Drake Maye, Bo Nix, Trevor Lawrence, or C.J. Stroud get there before Allen does would be disastrous to his legacy.

Colts at Jaguars: Indiana Is Cursed in 2025

I was all in on the Jaguars to win this one despite being a 1.5-point home underdog. But you have to see Daniel Jones tear his Achilles on a different leg than the one he had the fractured fibula with. I’m not a doctor, so I can’t comment if that may have led to this the way Tyrese Haliburton’s calf injury led to his Achilles in the NBA Finals, but it’s just been that kind of cursed year for Indiana sports teams. Caitlin Clark also had a season-ending groin injury in a year her Fever had a shot in the playoffs.

The Colts would have had a shot in this AFC if they were healthy, but between Jones going down and Sauce Gardner getting injured shortly after they traded for him, it’s been a brutal stretch for the Colts. From 7-1 to 8-5 and little hope with that tough schedule left.

Worse, they don’t even have a healthy (even if temporarily healthy) Anthony Richardson to go to and see if he can give them anything for the playoff run. They might have to snag Joe Flacco away from the Bengals somehow.

But give credit to the Jaguars. They scored a lot of points on short fields set up by the defense like they’ve been doing this year. I actually think they can get to 12-5 given the schedule, which includes another game with battered Indy.

Crazy how you can go from 7-1 and averaging over 3.0 points per drive to potentially finishing with a losing record and an offense that’s barely top 10, if that, when you consider the Colts have to play the Seahawks, 49ers, Jaguars, and Texans.

Saints at Buccaneers: Tyler Shough Can Move Like That?

With all due respect to Taysom Hill, I don’t think your services are needed anymore in New Orleans. If Tyler Shough can move like that on his two rushing touchdowns in Tampa Bay, then there’s no reason he can’t keep the ball on some of those snaps they give to Hill.

Shough’s second touchdown run also completed the first game-winning drive of his NFL career as the Saints (+8.5) completed the 24-17 upset on the road despite the Bucs having more healthy weapons for Baker Mayfield, who struggled in this one.

But I would still argue Tampa Bay pissed this one away more than the Saints won it. Tampa Bay finished 2-of-7 on fourth down, so when you get 11 drives and end five of them on fourth down (plus one pick), that’s really brutal offense, and it’s not like these were 4th-and-desperate situations late in the game.

I don’t know if Todd Bowles wanted a bow with his points to take them, or if he thought this was the right strategy as these were the five fourth-down failures:

  • 1Q, tied 7-7, 4th-and-1 at NO 45: Bucky Irving lost 7 yards on a run.
  • 2Q, up 10-7, 4th-and-1 at NO 49: Tucker stuffed for no gain on a run.
  • 2Q, up 10-7, 4th-and-15 at NO 47: Mayfield incomplete pass (I guess they weren’t confident in the 65-yard field goal in the conditions)
  • 4Q, tied 17-17, 4th-and-2 at NO 46: Mayfield incomplete pass to Godwin (Saints drove for game-winning touchdown from there).
  • 4Q, down 24-20, 4th-and-4 at TB 26: Mayfield 3-yard pass to Cade Otton for a turnover on downs to end game.

The last one is obvious, the one before halftime makes sense given the field position, I guess. But those three short ones at midfield, out of field goal range, and not in a bad situation on the scoreboard? Might have been able to argue they should punt there and put the rookie QB on a long field.

The Buccaneers and Panthers are both 7-6 with two matchups to come. This thing is far from over in the NFC South if the Bucs are going to keep playing with their food like this.

Commanders at Vikings: For Who, For What?

I’ll never understand what the Commanders were doing with Jayden Daniels in 2025. He had a few injuries as a rookie, but his elbow injury this year was not necessary as it happened after Dan Quinn kept him in a blowout against Seattle far too long.

Then given this team was 3-9 and hadn’t won since Week 5, what’s the point of even playing him again this year? He returned Sunday, he was rusty against a complex defense, and he re-injured his elbow on an interception return play. Now they’ll probably sit him for the rest of the year, but he should have been on the bench in the Seattle blowout and this elbow stuff never should have happened.

You have to protect your best asset. I’m not sure Quinn makes it to 2026 as the defense didn’t get any better despite that being the side they needed to fix desperately. Now the offense is messed up as well.

Seahawks at Falcons: Road Warriors Strike Again

This was actually a 6-6 game at halftime before the Seahawks blew it open in the third quarter with Rashid Shaheed scoring his first Seattle touchdown on a 100-yard kickoff return, then a Bijan Robinson fumble led to the first of two JSN touchdown catches as the rout was on.

The Seahawks (10-3) have been strong on the road all year, and now they get to face the Colts without Daniel Jones before their huge Thursday night rematch with the Rams in Week 16 when they’ll have a chance to take the NFC West lead.

Broncos at Raiders: The Worst Beat of the Year

Given how horrible the Broncos were on offense in the 10-7 win against this team last month, you have to give them credit here. Granted, 7 of the 24 points were a punt return touchdown, but they only had 7 possessions in this game and they gained 81, 41, 47, 91, and 90 yards on the five drives that weren’t limited by the clock and situation at the end of each half. They were sustaining drives with ease.

Some bettors just wish they would have gained 4 more yards on their last snap, because that left enough time for the Raiders, who trailed 24-14 with as little as 0:05 left, get into field goal range after an absurd penalty for trying to stay on top of a receiver who was down extended the game one more down. Then Pete Carroll decided to kick the 46-yard field goal, it was good with 0:00 left, and the Raiders (+7.5) covered the spread in a ridiculous 24-17 final.

I’ve had a pretty good spread week (8-5 ATS), but that was definitely the worst beat of the season on one of these.

Rams at Cardinals: Someone’s Winning in Fantasy on These Cardinal Blowouts

You just know there’s someone out there winning their fantasy league or taking down DFS contests (they still run those, right?) by stacking Jacoby Brissett and Michael Wilson (11/142/2 on Sunday). All that sweet volume and very little real-life NFL value because they either get blown out like they did here to the Rams (45-17), or they come up short in the fourth quarter of a one-score loss.

But this one was the blowout as the Rams led 45-10 at one point. Big bounce-back effort after last week’s loss in Carolina.

Titans at Browns: Shedeur Gets Some Stats, Cam Ward Gets the Win

This Toilet Bowl between the Titans (1-11) and Browns (3-9) actually proved to be far more interesting and nuanced than most Week 14 games. I can’t believe I’m about to write as many words on a Week 14 game between these teams as I am.

It was in theory a matchup of what were supposed to be the top two quarterbacks in the 2025 draft before Shedeur Sanders fell to the fifth round. I knew he’d try to shine in this one against the worst team in football, and to some extent, he did. Sanders finished with 364 passing yards, 3 touchdown passes, 1 touchdown run, 1 interception, and he led a comeback attempt in the final 5:00 that came up a hideous 2-point conversion try short of tying the game.

Meanwhile, Cam Ward only completed 14-of-28 passes for 117 yards, 2 touchdowns, and one pick against that tough Cleveland defense. But Myles Garrett, much like last week against the 49ers, got the lone sack for the defense.

It was also another game where the rest of the team sold out the defense with poor field position as the Titans had touchdown drives of 53, 38, and 8 yards as well as a 6-yard field goal drive without a first down gained.

But late in the game with the Titans up 31-17 thanks to those short fields (and a big day for Tony Pollard with 161 yards and two scores), we saw the shortcomings of the new down 14 strategy that I was just questioning last week. What happens if a team misses both conversions and is still down 2 late? That’s what happened to Cleveland in large part because they called a weird trick play for the final one instead of letting Sanders do something more conventional.

Let’s just note that Cleveland scored that second touchdown with 1:03 left. That left plenty of time to recover an onside kick and win the field goal as I said teams will do in the NFL as  you can’t really time out when you get a touchdown. Then had the Browns made the first 2PC, if you score with 1:03 left, look at how much time that leaves the Titans to go get a game-winning field goal with the new kickoff rules and the improved range for kickers with the new k-balls. The same is true if they had only tied the game at 31.

So again, I understand why teams do the down 14 thing. I just don’t think it’s all that advantageous because of what it does to the game state. For one, I don’t like the prospects of having to convert a do-or-die 2PC at any point in the game, so I’d rather avoid that. Then if you get the first one and you’re down 6, that should trigger the opponent to try better to add to the lead or run out the clock than if they had the cushion of a 7-8 point lead. Then there’s the end-game scenario of taking a 1-point lead quite possibly with plenty of time for the other team to use 4-down football to set up a game-winning field goal.

Yeah, I’m just never going to be a big fan of that, and games like this make it look even less attractive to me. Going to overtime has never actually been less scary than it is now with the new rules there. There’s no real sudden death unless you majorly fuck up like a pick-six or safety on the first drive.

Alas, this was the Toilet Bowl, so it didn’t really matter what these teams did. Just a game with far more points – I believe the total closed at a season-low 33.0 – and intrigue than it ever deserved to have for Week 14.

Also, it’s going to make the Shedeur cult even crazier because he’s delivering the big plays they said he would in the NFL. Just don’t let them hear that some have been filled with YAC, or that he’s only done it against the two worst NFL teams this season (Vegas and Titans) and lost 26-8 to a San Francisco team that was missing its two best defenders.

Cults don’t like pesky facts like that.

Dolphins at Jets: The Streaks Continue

He didn’t have to do much in this one, but Tua Tagovailoa is now 7-0 as a starter against the Jets after the Dolphins quickly opened up a 21-0 lead and held on for the 34-10 win. The Jets were stuck playing UDFA rookie Brady Cook from Missouri after a Tyrod Taylor injury.

With the loss, the Jets (3-10) have been eliminated from the playoffs for the 15th season in a row, the longest active drought in the four major American sports leagues.

Next week: The Week 15 schedule is decent even if the island games are not. The Bucs need to pick things up at home against Atlanta on Thursday night. We’ll see a Baltimore-Cincy rematch from Thanksgiving that’s lost some luster with both losing Sunday. Chargers-Chiefs could be similar if the Chargers lose on Monday night. Bills-Patriots is the big one, and we’ll see if NE can win the AFC East or if Buffalo can try to repeat its 2021 success by coming back to beat them and eventually destroying them in the wild card.

Green Bay vs. Denver is decent for a non-conference game between possible No. 1 seeds. Lions at Rams might be more fun to watch for three quarters though. Colts should get rocked in Seattle. I’ll be writing this early while we’re stuck with Cowboys vs. Vikings on SNF. Steelers usually win at home on MNF, and Miami usually loses on the road under McDaniel to .500+ teams, but we’ll see how that one goes to end the week now that the Steelers will get props this week instead of being in that underdog role.

2024 NFL Stat Oddity: Super Bowl LIX

~ Scott ~ Leave a comment

Fool me twice, shame on me.

While I undoubtedly picked the Kansas City Chiefs to win Super Bowl LIX, I said clear as day in my final preview “But I think the No. 1 issue to watch for the Chiefs is the offensive line.”

I also made this foreboding note:

But you never want to feel too confident about a Super Bowl, because I think the last time I did that, Tampa Bay beat the Chiefs 31-9. Sure, there was the LOAT factor, but I misjudged the OL shuffle the Chiefs did that night.

I won’t make that mistake a third time going forward. The Chiefs have lost the benefit of doubt again, because this was a pathetic performance in every way on a night where they could have made important history. They built the three-peat up for 52 weeks and it came crashing down in about 1.5 quarters. You could even just take what I tweeted after the first quarter ended and it summed up the rest of the game too:

https://twitter.com/ScottKacsmar/status/1888745031625851109

Couldn’t block them. Couldn’t get to Jalen Hurts without blitzing, and even then, the game’s MVP did what he wanted with his arm and legs as he improved to 10-0 this season when passing for over 200 yards.

But make no mistakes about it. The Chiefs lost this game in the trenches, and that area is the driving force behind these three Philadelphia Super Bowl teams since 2017. They’ve built great offensive lines, they replaced Jason Kelce and Fletcher Cox without losing a step on either side of the ball, and they just outworked and outsmarted the Chiefs for four quarters (or 3.5 before some garbage time) in a way we haven’t seen any team do.

Blowouts in Super Bowls used to be common, then it became an outlier in the 21st century. But it’s not a good look that the Chiefs are on the losing end of two of the four Super Bowl blowouts in the last 24 years as this game was most comparable to the 2013 Broncos against the Seahawks.

Defense wins championships. Football games are decided in the trenches. Overhyped quarterback matchups tend to disappoint.

That all applies again as that’s the way I started my Super Bowl 55 recap after the Chiefs lost 31-9 to the Buccaneers. Same shit, different year. Who knew the 2024 Chiefs would become a carbon copy of the 2020 Chiefs?

https://twitter.com/ScottKacsmar/status/1888823897044210169

That’s eerie. Mahomes was 25-1 in his previous 26 starts going into Super Bowl LV with a chance to repeat. He was 22-1 in his last 23 starts going into Sunday night with a chance to three-peat. The Chiefs were playing offensive linemen out of position in both games and were blown out by 18-to-22 points with Mahomes running for his life.

You can’t say there wasn’t precedent for this happening to Kansas City. But it’s hard to believe the Chiefs played the 2024 Eagles far worse than the Deshaun Watson-led Browns, the Jaguars despite trailing 22-0, and the Bryce Young-led Panthers did. Hell, they played them worse than anybody, because even Cooper Rush was only down 7-6 and 14-7 after the two-minute warning for Dallas in two games.

Also, can we put the Chiefs’ referee conspiracy bullshit to bed? After the first call of the night went Kansas City’s way, almost everything else was pro-Eagles, so enough about the NFL rigging things for one team. The whole thing was an overreaction by the collective fanbases whining about the Chiefs winning close games that a ton of people watched. No one cares about officiating in blowouts or calls that go against the Chiefs when that doesn’t fit the narrative. Let’s hope that bullshit quiets down in 2025, but you know how people are.

Anyways, the nicest thing about a Super Bowl rout is I don’t need to stay up until 8 AM recapping it. There’s only so much you can say about one team kicking another team’s ass on the biggest stage.

This season in NFL Stat Oddity:

The First Quarter Tea Leaves

We’ll see how long I get through the game in sequential order before I start going off on tangents about how bad the Chiefs played. But you could see in the first quarter that this was shaping up to be a bad night for Kansas City.

Let’s start with the lone thing the Chiefs did well. On the first play from scrimmage, Saquon Barkley had a nice run where he looked hard to tackle, yet it only produced a 4-yard gain. That would be one consistent theme for the night. The Chiefs actually shut Barkley down cold as a runner, holding him to 57 yards on 25 carries (2.3 YPC) with a long of 10 yards.

According to Next Gen Stats, Barkley’s minus-48 rushing yards over expected was the lowest game of his career. Great. You sold out to stop the run, and what did that really get you? It reminds me of the Super Bowl 48 blowout where the Broncos only did one thing very well, and that was run defense. The Broncos held Seattle’s Marshawn Lynch to 39 yards on 15 carries. They just did everything else poorly and lost 43-8.

The Eagles ended up punting on their opening drive after a 4th-and-2 conversion to A.J. Brown for 32 yards was negated by an offensive pass interference penalty for Brown pushing off. I didn’t like the call for OPI, but he clearly did push the defender’s face before making the catch, so something was worth a flag there to negate that pay. But you already opened a can of worms with the officiating conspiracy on the first drive.

However, that would be short-lived. The Chiefs gained 11 yards on their first play with a quick pass to JuJu Smith-Schuster, but the Chiefs wouldn’t gain another first down until the first minute of the third quarter if you can believe that.

On a 2nd-and-9, Mahomes threw what looked to be a fine pass to Travis Kelce for a first-down gain, but the tight end dropped it. That brought up 3rd-and-9, and the pursuit of Mahomes was on in the first big test of the game, and he held the ball for a long time before nearly throwing a pick, a sign of things to come.

The officiating battle evened out quickly when the Eagles’ second drive was extended by a weak call for a late hit by Trent McDuffie on a high throw to Dallas Goedert, who didn’t even need to break 30 yards for the Eagles to have a big night. That could have led to a punt or maybe the Eagles go for it, but they ended up beating the blitz with a 27-yard throw to Jahan Dotson down to the 1 where Hurts carried it in for the Tush Push touchdown.

I think that was the only Tush Push of the night too, and he showed up Josh Allen how to run his play against the Chiefs. With the Eagles up 7-0, the Chiefs went three-and-out with edge pressure by Nolan Smith getting to Mahomes to affect a throw to Hollywood Brown, who came running back to the quarterback and may have even given up the first down had he caught the ball. I thought if Brown sat in the zone he’d be an easy target for a first, but the play didn’t work out and again it was quick edge pressure.

The Super Bowl 48 comp. intensifies.

The Chiefs added to their legacy of being the worst team at lining up properly on crucial downs as Charles Omenihu was lined up offsides (Dee Ford special) on a 3rd-and-4 play where they sacked Hurts out of field goal range. Alas, that play didn’t count, and the drive continued, ending a pretty bad first quarter for the Chiefs.

The Second Quarter Faceplant

The defense had its best moment of the night when Steve Spagnuolo’s blitz on 3rd-and-10 worked as Hurts made a poor decision on a deep ball that was intercepted, making sure the Chiefs wouldn’t go four games without a takeaway for the first time in franchise history. They also wouldn’t join those 2013 Broncos as the only Super Bowl participant to go an entire postseason without a takeaway.

But they had the 2013 Broncos’ back in other ways. The only thing bad about the pick of Hurts is it was caught at the Kansas City 2, so the offense was 98 yards away from the end zone, meaning the Eagles were still more likely to get the game’s next score.

Sure enough, the Chiefs went three-and-out after Mahomes’ pass on 3rd-and-3 was low and away from Kelce on a throw they usually connect with. I don’t call that a drop and that’s more on Mahomes. The Eagles ended up getting good field position (own 43) and did indeed get the game’s next score with a 48-yard field goal by Jake Elliott, who redeemed himself with a fine night.

The Chiefs were down 10-0 for the fifth Super Bowl in a row, but we’ve seen them crawl out of holes like this before. Things were looking poor, but to this point, it was only a few pressures on third downs and Mahomes trying to compensate with a quick throw on the third drive. They can get things moving, right?

Nope. The fourth possession moved this one into blowout territory.

On first down, I’m not sure what the Chiefs were trying to do with a play-action pass, but the Eagles blew it up immediately with Josh Sweat going right past Kelce (whiffed) and getting the first sack of the night. On 2nd-and-14, Mahomes has Xavier Worthy near the right sideline for a gain of 5-6 yards if he wants it, but he’d need to take it immediately. Instead, he tried to climb the pocket and was sacked again by a pair of Eagles despite the Chiefs having 7 blockers against 4 rushers.

https://twitter.com/ScottKacsmar/status/1888873409846616449

Then on 3rd-and-16, the gamebreaker, Mahomes threw his worst interception since…ever? At least since the play he accidentally injured Rashee Rice on in Week 4. I don’t know if he just never saw Cooper DeJean jumping the route, but the worst thing about this is it wasn’t even high reward enough. On 3rd-and-16, I’d much rather see him throw a 40-yard bomb and if it gets picked, then that’s the definition of an arm punt – not the fixed CBS version they use for Josh Allen.

https://twitter.com/LordSnowXRP/status/1888834469131608537

All the hype for Saquon Barkley’s birthday and not enough for Cooper DeJean turning 22 and turning in his first NFL interception for a huge 38-yard touchdown and 17-0 lead. It was the first time all year the Chiefs’ starters trailed by more than 11 points. It’s the first time Mahomes trailed by 17 points since a 2022 game against the Raiders that they came back to win 30-29 on a Monday night.

But this was going to be a daunting task. To this point, the Chiefs had 12 passes and 1 run (that gained 2 yards). Somewhere, Donovan McNabb is saying, “See, it’s not easy to win like that, is it?” in reference to Andy Reid’s career-long criticism of not running the ball in big games. Where were the screens and moving pockets to get away from that pressure?

The Chiefs then picked a curious time to call consecutive runs for the first time all night, down 17-0, and all it did was lead to 3rd-and-9. Mahomes tried to make something happen, but after running into the waiting arms of left guard Mike Caliendo (The Weakest Link), he took his third sack in his last four dropbacks.

https://twitter.com/ScottKacsmar/status/1888878242330775557

The left side of the line was the problematic side, and at that point, I would have made the switch. I tweeted this during the game at this time too. Put Joe Thuney back at left guard where he belongs, and bring in veteran left tackle D.J. Humphries, who was active, to play tackle like he knows how to do.

This Thuney-Caliendo thing was cute for the last month, but the Eagles are embarrassing you without even sending heat. But the change never came. On defense, the Eagles got lucky when they avoided a 3rd-and-26 situation after a horribly soft penalty call on the Chiefs for a late hit.

https://twitter.com/Rate_the_Refs/status/1888754342053978506

We can say that didn’t end up mattering since the Eagles punted 36 seconds later, but it did likely change field position. The Chiefs took over at their own 6 with 1:49 and two timeouts left. If they could get a field goal, they’d get the ball first in the third quarter, so getting back into a 17-10 game actually wasn’t out of the realm of possibility if they could get something going in a hurry-up situation.

But any shot at a competitive game ended when Josh Sweat pushed Thuney right into Mahomes as he was throwing the ball on the first play of the drive, and Zack Baun made this diving interception to set the Eagles up at the Kansas City 14. Two plays later, A.J. Brown walked into the end zone on a touchdown catch to make it 24-0. Game over.

https://twitter.com/ShaneHaffNFL/status/1888756766151749843
Mahomes’ second interception in the second quarter.

Now we absolutely had the Super Bowl 48 comparison. A quick edge pressure is sometimes all it takes, and this is why I think Sweat (2.5 sacks) had a real argument for Super Bowl MVP as he won’t get credit for a sack there, but that pressure of pushing Thuney into Mahomes created that big interception.

And again, the Chiefs deserve what they got for sticking with their best guard at tackle instead of trying to work in a real tackle with plenty of experience. In a span of 5 dropbacks in the second quarter, Mahomes took three sacks and threw two picks and there’s your ballgame.

Any shot for a score before halftime basically ended with a holding penalty on first down to negate a good scramble by Mahomes, something that he should have been doing earlier too. Actually, I take that back. They had the 3rd-and-11 on this last drive converted, but DeAndre Hopkins decided to do this with his big opportunity in a Super Bowl:

https://twitter.com/NFL_DF/status/1888758885403546070

The Chiefs had 23 yards of offense and 1 first down on 7 drives in the first half. They usually surpass those numbers by the first or second drive of a game.

The Second Half Just Delays the Inevitable

If you thought the Chiefs had any answers for a competitive second half, you’d be wrong. No offensive line changes. Even with trying to chip with a running back, the Chiefs continued giving up sacks to 4-man rushes. Back-to-back sacks led to a 3rd-and-17 for Mahomes where he was only able to scramble for half of it before the Chiefs punted.

Hurts made a few key scrambles, Barkley made his most impactful play on a bobbled 22-yard catch, but the Eagles were held to a field goal. Still, it was 27-0 and that drive consumed 6:42, which is exactly what you want if you’re the Eagles.

Like I said, Andy Reid had no answers before or during the game. After a Jawaan Taylor holding penalty (redundant) wiped out a first-down scramble by Mahomes, you knew the Chiefs were cooked when they’re trying to run for 1 yard with Kareem Hunt on 2nd-and-14. Mahomes ended up leading the team with 25 rushing yards as his backs had 7 carries for 24 yards.

Going for it on 4th-and-4, I thought Mahomes made his 2nd-biggest mistake of the night when he didn’t see Justin Watson open over the  middle and seemed to predetermined a throw to the right to Hopkins, which wasn’t close. The Chefs turned it over on downs, and the Eagles went for the kill shot immediately with a 46-yard touchdown strike to DeVonta Smith, which probably clinched the MVP for Hurts since you can’t give it to the whole defense.

Just like that, Mahomes was down 34-0 for the first time in his career. The team’s previous biggest deficit with him was 27-0 in a 27-3 loss in Tennessee in 2021.

At 34-0, we knew it was all over. Mahomes and Worthy (the only Kansas City player who showed up) connected a couple of times to quickly lead a 90-yard touchdown drive so there wouldn’t be a shutout. But the Eagles had another time-consuming field goal drive (5:43) to make it 37-6, then with just under 10:00 left, Mahomes was sacked for a career-high sixth time and fumbled. The officials didn’t even bother flagging the hit to Mahomes’ face on the play, and no one cared because it was a blowout and the missed call didn’t help the Chiefs.

https://twitter.com/TSN_Sports/status/1888781212736483455

By taking a sixth sack, that ends Mahomes’ streak of 132 games to start his career without taking more than 5 sacks in any game. Only Peyton Manning (293), Dan Marino (260), and Joe Flacco (180) had longer streaks to begin their careers.

The Eagles won the turnover battle 3-1 and finished the postseason +12 in turnover margin, including an absurd +7 in fumbles.

They added a field goal after the Mahomes fumble to get to 40 points, and then Mahomes threw two touchdowns to Hopkins and Worthy down the stretch to get some garbage-time stats for the 40-22 final with Kenny Pickett (oh, for fuck’s sake) kneeling it out for the Philadelphia win.

With the way people are reacting to those late touchdowns, it just proves I was right that Mahomes would get killed for “garbage-time stat padding” in Super Bowl 55 had he thrown a late touchdown to make it 31-16 and get a touchdown on the board instead of throwing his second interception in a 31-9 game that was long decided. Can’t win either way with the cult out there.

The Chiefs gained 11 yards on their first play of the night and didn’t have a longer gain until 2:33 remained in the third quarter with Worthy making a pair of 50-yard catches in this game.

For the reputation Andy Reid has as a great coach following bye weeks, he is 1-2 after a bye against Nick Sirianni, who I struggle to give credit to as it feels like he goes as his coordinators go.

Defensive coordinator Vic Fangio won his first Super Bowl and his first game against Mahomes, who he was 0-8 against. But Fangio had the right idea all night. He didn’t blitz once and still generated 16 pressures and 6 sacks. Reportedly that’s just the fourth time since 2018 that a defense didn’t blitz in a game, and I believe one of those games was Buffalo in 2020 against the Chiefs.

The Eagles played Cover 4 at the third-highest rate (59.5%) of any game since 2018.

https://twitter.com/NextGenStats/status/1888791032118030640

I don’t think that becomes the new “blueprint” to beat the Chiefs, because not everyone can get pressure like this just by rushing four. Compare how the Eagles looked and how the Bills looked two weeks ago, and it’s like night and day.

But Kansas City’s offense has had major struggles in what I would say is four of their five Super Bowls against these NFC teams. They found a way to come back and finish strong in three of those games for rings, but they’re always playing an elite unit, and they just never seem to struggle this much in big games when they play those AFC rivals like the Ravens and Bills.

It’s definitely an interesting dynamic, but it’s why you can’t give this team the benefit of the doubt anymore. Nineteen of the last 21 Super Bowls had been within one score in the fourth quarter, but this is now the second time the Chiefs lost by three scores, and this one wasn’t even that close if we’re just keeping it real.

The Chiefs got their asses kicked, something only a handful of teams can say they’ve done to them over the last seven seasons. Hats off to the Eagles for coming back strong after last year’s collapse and getting their revenge for Super Bowl 57.

I know which game I enjoyed more of the two, but sometimes you need a good ass kicking to get your priorities right. I still have to write two articles tomorrow about where the Chiefs and Eagles go from here, so I’m not going to get into that here.

But it’s pretty clear the Chiefs need to find a real left tackle who can stick around for the next decade with Mahomes. Starting five Super Bowls with five different left tackles is a cool footnote but not ideal at all. It reminds me of Peyton Manning going to four Super Bowls with four different head coaches.

They’re the only two quarterbacks who can do these things, but it’s not likely going to lead to great results when you’re going up against more complete teams.

Conclusion: The GOAT Case Is Closed

Many are using this game to say the GOAT case is closed, and I have to say I agree with that. Obviously, I was never on board with it anyway.

I mean, Andy Reid is simply not the greatest coach of his era, let alone all time. Now his 3-3 Super Bowl record with his team getting dominated twice largely because he didn’t have a real plan for the offensive line is an eyesore.

Maybe it wouldn’t have mattered if they started D.J. Humphries or gave Donovan Smith a call in December – the Eagles played that well. But I can’t see someone like Bill Belichick ever watch his team get crushed in all phases like this with so much on the line.

Sure, the 2007 Patriots blew the perfect season to the Giants, but it was a 17-14 game they led late in. This was another rout for Reid, and that’s very disappointing. Almost like the Chiefs don’t do well in the role of a favorite and villain. Just showing up as the defending champs doesn’t mean you’re supposed to win. The Eagles kicked their ass.

But yeah, people are going to use this game against Mahomes, and I get it. He’ll need some big Super Bowl moments in the future to offset the sting of these losses. It would be a really tough look if he never made it back as Brady is the only quarterback to start more than five Super Bowls. But I’d also be utterly shocked if Mahomes doesn’t get back.

And I still believe his best and most complete rosters can be in his future. The success he’s already created after starting for seven seasons is historically unmatched.

How quickly people forget Brady was 3-2 in Super Bowls, and a yard away from going 3-3 in Year 15 before Malcolm Butler happened. I don’t expect Mahomes to do what Brady did in his 40s, and I think this was his only good shot at the three-peat, and it hurts to not make that happen.

But no one knows where things go from here. Mahomes is only going into Year 9 and he’s already 3-2 in Super Bowls. He has time on his side, and the dynasty isn’t over until someone actually dethrones them with their own 3+ ring run. But they are going to have to play better when they get this far again. This was unacceptable, and it’s not about any one person.

The Chiefs will take a breather and start the process all over again for the 2025 season. I’ll do the same, and I have to admit I’ve been looking forward to the offseason and a little more down time as this has been a year from hell. The three-peat was actually a great source of escapism for me and something to follow along with throughout this season.

Going back to last April:

  • I’ve lost one of my oldest friends to suicide after an online mob used cancel culture against him much like one tried to do to me, so that made it hit even harder.
  • My neighbor was murdered (along with her friend) in her house by her own son after weeks of shooting incidents and threats from him that the police knew and did nothing about.
  • I lost my only uncle to cancer in December.
  • Just this week, my mom’s best friend and someone I always imagined would be there for me was found dead in her apartment from a very sudden illness.
  • I don’t expect my two oldest cats to see 2026 (maybe not even the spring) as they’re both struggling with their health.

There’s something else I never got closure from that happened in 2023, but I’ve probably overshared enough as is.

I just feel like I’m stuck in a Charlie Kaufman screenplay, and my world keeps getting smaller, darker, and has been surrounded by death for the last year. Throw in Trump and President Elon trying to destroy the country right in front of our eyes on a daily basis, and I don’t see much reason for optimism or hope about the future.

But I got a 15th season in me, and who knows, maybe there’s a Malcolm Butler out there who will save it in the end. I’ll have some offseason projects, basketball coverage, and will be catching up on movies.

This might even be the week for me to watch Emilia Perez, because it’d only be the second-shittiest thing I’ve watched this week after last night’s game.

Until next time, enjoy your loved ones while you still can.

2024 NFL Stat Oddity: Conference Championship Games

~ Scott ~ Leave a comment

I said Sunday was going to be a history-making day in the NFL and it absolutely was. We’re already seeing history in the Super Bowl as Chiefs vs. Eagles will be the first ever AFC vs. NFC matchup to happen in four consecutive seasons (2021-24) thanks to two Super Bowl matchups.

But how about the other history we were tracking?

  • The Chiefs are the first team to reach the Super Bowl after repeating, replacing the 1990 49ers as the closest to ever complete a Super Bowl three-peat.
  • After an early fumble, the Chiefs’ record streak of games without a turnover was snapped at eight.
  • The Chiefs have won 17 straight one-score games now (NFL record).
  • Even though the Bills started the game with two near interceptions and fumbled the ball four times, they finished with no giveaways, meaning they had just 8 turnovers in a 20-game season (NFL record for any season and any 20-game span).
  • The Bills now hold the NFL record for 22 straight games without losing the turnover battle. They were previously tied with the 1950s Rams at 21 games.
  • The Five-Year Rule lives on as Sean McDermott and Josh Allen will not be winning a Super Bowl in Year 7 together, and now Allen will have to try matching Peyton Manning as the only Super Bowl-winning quarterback who needed more than five postseasons to reach a Super Bowl.
  • Jayden Daniels did not become the first rookie quarterback to reach the Super Bowl, but the 2024 Commanders are the only team to ever score at least 18 points in 20 consecutive games in one season.

I would have loved a Daniels vs. Mahomes Super Bowl, but all things considered, Chiefs vs. Eagles is the best possible matchup this season could have produced in Super Bowl LIX. You get the three-peat against the team the title reign started against two years ago in Super Bowl LVII. These have been the best teams in their respective conference over the last three years, and there’s the added twist of Saquon Barkley, who will have his 28th birthday on Super Bowl Sunday.

I’m pleased with the outcome, but I sure as hell wanted a better game early in Philly. At least we got a classic in Kansas City again.

This season in NFL Stat Oddity:

Bills at Chiefs: Four Falls of Buffalo Gets a Sequel

It has to be frustrating to have a great team and still come up short because there’s always someone that is a little better. This happened to the Buffalo Bills when they lost four straight Super Bowls in 1990-93 with the NFC teams easily getting the best of them in the last three games before the salary cap was implemented in 1994.

They did a documentary on those losses called Four Falls of Buffalo for 30 for 30. But we might actually need a sequel as Buffalo’s 0-4 mark in the playoffs against the Kansas City Chiefs is arguably more infuriating since the games were usually closer than those Super Bowl losses. Sure, they haven’t been Super Bowls, but Buffalo damn well may have gone the distance in 2020, 2021, 2023, and 2024 had it not been for Patrick Mahomes and the Chiefs.

How do you top a team that’s won 17 straight one-score games? How do you overcome a quarterback who is 17-3 in the playoffs and always seems to shred your defense no matter how well you do in the regular season? Remember, the Bills have won four years in a row in the regular season against the Chiefs, including multiple games in Arrowhead.

Yet, here we are again with the Bills coming up short in a 32-29 classic that again went down to the wire. I think I’ll jump around some different storylines instead of doing a sequential recap.

Chiefs Save Their Best for the Playoffs Again

The Chiefs hadn’t scored 21 points in any half all season, and yet they did it in this game. The Chiefs hadn’t scored more than 30 points in any of their last 28 games. They hadn’t topped 31 points in their last 36 games, and yet they scored 32 in this game on just nine drives, and they ran out the clock on that final possession.

It just seems like no matter what the Chiefs do against Buffalo in the regular season, they’re able to turn it on in the playoffs against Sean McDermott’s defense.

The versatility of this team is key. In Week 11 in Buffalo, Mahomes never ran the ball once. In this game, his mobility was apparent from the opening drive, and the Chiefs had great success with RPOs – save for one fumbled exchange between Mahomes and Pacheco that broke the team’s record streak without a giveaway – as Mahomes read the field well the whole game with quick decisions.

But his legs were key again with over 40 rushing yards, two touchdowns scored, and he made it look effortless. Kansas City was all in on Travis Kelce against Houston, but he only had 2 catches for 19 yards in this game, shades of what the Bills did to him in Week 11. Instead, Mahomes found JuJu for 60  yards on the offense’s two longest plays that were both quick decisions over the middle. Even Samaje Perine had the game’s fifth-longest gain (17 yards) to put the game away on third-and-long in the 4-minute offense.

The Chiefs just do whatever is necessary to win the style of game they find themselves in. The people who said this team couldn’t win a shootout with Buffalo this year were wrong again. The Chiefs tend to dictate how these games go. Not Buffalo.

Can’t Ever Have Enough Good Corners

Injuries will probably come up as an excuse again for why McDermott’s defense failed and made the Chiefs look greater than usual. They were without safety Taylor Rapp, but I don’t remember when he turned into Ed Reed incarnate.

Then there’s the case of corner Christian Benford. He was carted off with a concussion in last week’s game. You know what the NFL is like in the post-2022 Tua Tagovailoa concussion protocol era. If you see a player that bad off after a concussion on a Sunday, he shouldn’t be playing the next Sunday.

But the Bills somehow got him on the field for this game, and they may have jeopardized his chances to get back on one any time soon. He took a hit to the head (friendly fire) early in the game and had to be carted off again, even strapped down with the seatbelt in the cart. It was a scary sight and something that should get a third-party investigation into the handling of clearing him.

With Benford out early, the Bills were stuck playing Kaiir Elam for more snaps, and the Chiefs attacked him frequently as teams often do when this happens to a secondary.

But I’m not going to feel bad for Buffalo here, because it’s a lesson that you can never have enough good corners. Elam is not a street free agent they signed a week ago for depth either. They used a 2022 first-round pick on this guy just two picks after the Chiefs drafted Trent McDuffie. Advantage Chiefs. Elam hasn’t been good and he didn’t help this game when they needed him to come up big.

Xavier Worthy: My Bad

Speaking of Kansas City draft wins over Buffalo, I have to eat some crow on Xavier Worthy. While I still believe Ladd McConkey would have been more unstoppable in this offense, Worthy has developed into a solid player who is more than just a gimmicky speed and gadget player. He attacks the ball down the field now, and he showed his skills on a 26-yard grab in the second quarter to prevent an interception and he also scored a touchdown on a very fine night where the veterans (Kelce, Hopkins, Hollywood) didn’t do much.

Of course, people called the 26-yard catch a controversial call for the Chiefs. First, there was a holding penalty on the Bills, so it would have been a first down anyway. Second, I think they got the call right with the rule change years ago that the ball is allowed to touch the ground as long as you maintain control. I don’t see where Worthy ever lost control of it as he gained possession from the DB, and in that situation, the offense gets the catch. Legit call.

But let’s say they called it incomplete. Then the Chiefs still have a first down at the Buffalo 24 with under 3:00 left in the half. Who’s to say they still don’t score a touchdown on that drive with the way they were going up and down the field all night? They may have even scored it with less than 1:55 left like they did, and that would leave less time for the touchdown that the Bills got to make it 21-16 going into halftime.

That sequence was also amusing as the Bills took the extra point off the board to go for a 2-point conversion from the 1-yard line. I don’t mind the decision to go after the penalty. But the Chiefs plugged the gap on the left where they knew Allen was going to run, and they stopped the play.

Erratic Allen Not So Automatic on the Sneak

I don’t think the game does much of anything to change the legacy for Josh Allen. He came in winless against the Chiefs in the playoffs with some close calls, and he went out winless with another close call in a game he briefly had a fourth-quarter lead in.

There were enough good plays to say he battled and gave them a chance, and he didn’t make a huge mistake with the game on the line. But it was far from his best game against the Chiefs, and he started it poorly with two throws that could have been intercepted on the opening drive alone.

Allen also fumbled 3 times on the night, but somehow the Bills recovered all 5 fumbles in this game (4 of their own, one unforced error by the Chiefs on the RPO). They’ll finish the season +17 in fumbles, an absurd number that has to regress next year.

But I did get the sense early that Allen was nervous in the biggest game of his career. There was a three-and-out in the second quarter before the big Worthy catch where Allen threw a poor 2nd-and-10 pass to Curis Samuel, which was dropped as he had to reach down to get it. He should have caught it, but if Allen threw it in stride, that’s a huge gain. Big miss there.

But Allen’s bread and butter on the short-yardage run was gone in this game. In fact, he was stuffed 3 times on crucial sneak plays, the most in any game since 2016.

Remember, the Ravens stuffed him last week on a big third down when he considered pitching the ball back on the play. Buffalo fans assured me Allen was automatic in these spots, but this postseason paints a different story. Incredible job by the Chiefs on defense on those plays.

The big one came on 4th-and-1 at the Kansas City 41 with the Bills up 22-21 with 13:01 left to play. Allen tried to go left on the Tush Push, but the Chiefs stood him up and it was ruled short on the field. The ruling on the field stood after video review with a turnover on downs.

I think what happened here is the Chiefs were saved by Chris Jones obstructing the view of the ball by standing right down the camera line from the key angle. You might be able to reasonably conclude that Allen probably had the ball to the 40, but there’s no visual evidence that he had the ball break that line. You see Allen but not the ball on the most shared shot of this.

Tough break for the Bills, but they were terrible on those short-yardage runs all night. I’m also not sure if James Cook was injured or what, but he deserved more than 13 carries after looking good in the second half.

The Chiefs Are Closers

After taking over on the 4th-and-1 stop, the Chiefs were surgical on another touchdown drive to regain a 29-22 lead after converting their first 2-point conversion of the season if I heard correctly.

But the Chiefs had some defensive lapses in this one despite playing well at times. They let Mack Hollins beat them deep a few times, and that led to another touchdown on a 4th-down play where Samuel was left wide open in the end zone to tie the game at 29.

The Chiefs were marching right into a first-and-goal, and just when you thought we’d see a flurry of a finish like the 13 Second Game, the Bills sacked Mahomes immediately on a first-and-goal, causing a failure on that revamped left side of the line.

Was that finally going to catch up to the Chiefs? Then with Harrison Butker coming out for a 35-yard field goal with 3:37 left, I jokingly predicted the other day he’d miss a 35-yard field goal. That was in my head for sure at the time as I could see him missing and the Bills making on the other end with 0:00 left to win 32-29.

But Butker was perfect on the kick, right down the middle. While this would have been a great time for the Chiefs to force the first non-QB fumble of the season for Buffalo (or any turnover), they instead cranked up the heat on 4th-and-5. Spagnuolo brought a blitz and Allen did his best to throw up a pass for Dalton Kincaid. He absolutely had a shot at a diving catch that could have lived in playoff lore, but instead he couldn’t make this play:

There was still 1:54 left, and Pacheco ran out of bounds to stop the clock on a nice 2nd-down pass from the Chiefs for a first down. But it got to 3rd-and-9 at the Buffalo 35, which is no man’s land in this situation with 1:35 left. Do you risk an incompletion to stop the clock? Risk a sack to lose the FG opportunity? Do you even want to kick the FG and go up 6 with that much time left?

Tough call, but the Chiefs made the right call, and Mahomes found Samaje Perine for a 17-yard gain out in the flat to send the Chiefs right back to the Super Bowl for an unprecedented three-peat opportunity.

That whole drive I was waiting for a running back to fumble to recreate the 1990 Roger Craig fumble moment in San Francisco that led to New York’s upset win. With the way Buffalo’s fumble luck was in 2024, you never know. But the Chiefs didn’t stumble, and they again put a team away in a one-score game for the 17th time in a row.

Unbelievable stuff from a historic team that is one win away from the ultimate history. Season on the line, there’s no quarterback you want more than Mahomes.

Final Thoughts

We’ve reached the end of our show where I guess I’m supposed to jump into my Bill Maher-style monologue (less smarmy about it) where I pat myself on the back for being right about Buffalo still not having what it takes to get over the Kansas City hump in the AFC.

And you’re probably wondering how I could say that when I picked the Bills to win 27-24 the night before. Yeah, but if you look closely, I also spelled out “THREEPEAT” with the first letter of each paragraph.

I did a reverse jinx on Buffalo, something I’ve been doing for 18 years (ever since it worked for the 2006 AFC Championship Game) because I grew tired of picking the team I wanted to win and seeing them lose the game. So, I get to either enjoy a correct prediction or enjoy the actual outcome to games like this.

I also said this was a coin-flip game, and it basically was – tied  at 29 with 6:15 left. As usual, the Chiefs closed, and the Bills didn’t make the plays to win the game or force overtime.

Buffalo had a very good year, but I trust my eyes, and I trust my numbers. Earlier this week, I introduced some numbers on my Fraud Alert metric, which I’ll be sharing more of before the Super Bowl. It had the Bills as by far the No. 1 misleading team this year based on turnover margin, field position, and strength of schedule. The Chiefs were only 17th, producing one of the biggest mismatches in my Fraud Alert Rating (FAR) system since 2002.

Well, I can tell you now that the teams with the higher FAR in the 11 biggest mismatches since 2002 are now 2-9 in the playoff meetings. Even better, I can tell you that in the 21 playoff games since 2002 with a spread of 0-to-2 points, the team with the higher FAR is now 6-15 (.286). That’s right. The team with the higher fraud alert won just 28.6% of the playoff games with the tiniest spreads, and you better believe this applies to Super Bowl LIX too.

When Bills fans tried to pump up Josh Allen by telling me that Mack Hollins is his WR1 (he wasn’t but he was better than Amari Cooper and Keon Coleman on Sunday)), I laughed it off, thinking maybe that’s a bad thing if you’re relying on Mack Hollins to be a big producer in your offense. Maybe it’s a bad thing that Dalton Kincaid’s numbers regressed so badly in his second year, or that Cooper hasn’t really done much since the trade.

Maybe “beating both No. 1 seeds” isn’t all it’s cracked up to be when you’re only 2-3 against playoff teams in the regular season.

Maybe “scoring 30 in regulation” as they liked to bring up as a shot at the Chiefs doesn’t mean much if you can’t keep most good teams under 30 points. Maybe it doesn’t mean much if you’re scoring 30+ against the likes of the Titans, Jaguars, Jets, Colts, and Dolphins.

Maybe it’s not a good thing if your team doesn’t have a single fourth-quarter comeback win this season, nor is it a bad thing that the Chiefs now have six of them as Mahomes tied the single-season record with his eighth game-winning drive Sunday. Still think they’re the 2022 Vikings?

Your quarterback didn’t win MVP, your team didn’t get the top seed, and you didn’t beat the Chiefs again in the playoffs. Close but no cigar. Only Brady and Burrow have smoked that one for getting past the Chiefs in the playoffs.

I’ve said it would be statistically improbable for the likes of Allen and Lamar to never at least reach a Super Bowl. I stand by that. But at the same time, I don’t think it’s a stretch to say Allen and McDermott blew their best shot in 2021 because of 13 Seconds, and that should have been their Super Bowl year.

Instead, it’s set the AFC on this butterfly effect where we pretend the Bengals are the team to beat only to see them be irrelevant unless Lamar gets hurt, the Ravens always choke in the playoffs, and the Chiefs traded Tyreek Hill, built up the defense, and keep winning one-score playoff games because Mahomes gets big moments out of JuJu, MVS, and some rookies.

Allen had his moment in 13 Seconds by finding Gabe Davis again, but the Bills still found a way to lose, and they frankly haven’t topped that moment in the playoffs ever since.

But that’s why Mahomes and the Chiefs are in their own tier, and the Bills are just the best-looking, ringless bridesmaid in the AFC.

Commanders at Eagles: Double Nickel Boys Run Wild on Washington

I’ll start by saying it’s almost impossible to beat these Eagles if the good version of Jalen Hurts shows up. I saw the knee bend against the Rams last week, and I thought that’d actually be problematic this week. Silly me. Hurts looked mobile and was as good as he’s been in any game this season.

Then when you throw in his receivers getting early production, Saquon Barkley hitting another 60-yard homerun on the first snap, and the Commanders fumbling it three times again just like they did in Week 16 to screw over their rookie quarterback, you end up with a 55-23 smackdown, the most points ever scored in a Conference Championship Game by one team.

I thought Jayden Daniels could be the one rookie who would get to a Super Bowl by producing a different outcome. In a way, he did stand out as he played better than any other rookie has in a conference championship game where rookies are now 0-6 since 1970. I hope he has more deep playoff runs in his future, because it would be insane if the closest he ever came was this year in a game where his defense allowed 7 rushing touchdowns and his skill guys put the ball on the ground three times early.

Daniels didn’t turn it over until he was down 25 points with 5:00 left. But the other Washington turnovers were very costly. Dyami Brown coughed up a fumble trying to get centimeters more YAC, leading to a short field and 14-3 lead for the Eagles. The Commanders could have scored before halftime to make it 20-20 or at least 20-15, but a fumbled kickoff led to another touchdown and 27-15 deficit at the half.

The real killer was the final minute of the third quarter. Washington was down 34-23 and driving at midfield with a first down. Austin Ekeler became the third skill player to put the ball on the ground for Washington as the Eagles are really good at forcing those fumbles. That led to the absurd sequence to start the fourth quarter of six straight attempts to do the Tush Push from the 1-yard line finally resulted in a touchdown run for Hurts, who scored three times just like Barkley on the day.

But it was the announcement that the refs could award a touchdown to Philadelphia if the Commanders kept jumping over the line before the snap in their effort to go all Troy Polamalu and stop the Tush Push.

I mean, that’s probably not a bad rule to have in case of emergency, but the whole thing looked ridiculous and I have really come to despite the Tush Push. Just get rid of it already and go back to normal quarterback sneaks. Washington should have called the refs’ bluff too —  go figure, it was Ed Hochuli’s son – and made them award the Eagles a touchdown. I’d love to see that in the stat sheet and how that dynamic works.

But yeah, it was a rough outing for the Commanders in a 55-23 loss. I think the only way they win the game is if they were +4 in turnovers (or just +3 in fumbles lost). Even without the turnovers, they still never showed a real answer to stopping Philadelphia’s offense. Even Will Shipley came in for Saquon and ripped off a 57-yard run before scoring a touchdown.

The Eagles had 11 drives, scored 8 touchdowns, missed one early field goal, and punted twice in the third quarter. Yeah, it wasn’t just about the turnovers even if that definitely made things worse for Washington’s chances.

So, that one was a dud but still an incredible turnaround season for the Commanders. I’m sure Daniels will be a trendy MVP pick for 2025, and I may even drink some of the Kool-Aid if they make some free-agent splash signings to give him stronger weapons and build up that defense.

But the Eagles are still the class of the NFC East, and they really have been the best NFC team over the last three years despite having a caricature of a head coach. We’ll see if they can solve the Chiefs in two weeks.

Next two weeks: Two weeks of hyping up the final game of the season. I’ll have plenty of Super Bowl articles next week. This week, I’m continuing with Part 5 of my LOAT series, looking at the playoff luck for Tom Brady and Patrick Mahomes. I’m also going to do a bigger presentation on my Fraud Alert Rating metric. The Chiefs just have to win one more game for that to look as solid as possible.

NFL Stat Oddity: Super Bowl LVIII

~ Scott ~ 1 Comment

Super Bowl LVIII was in fact a race to 24 points, but I’m not sure anyone imagined we would be 3 seconds away from double overtime, making this the longest Super Bowl ever played by game time (74:57).

But the Kansas City Chiefs are all about making history. It has been that way since Patrick Mahomes took over as the full-time starter in 2018, and it is only fitting that this team is now officially an NFL dynasty with 3 Super Bowl wins in the last 5 seasons. The longest drought in NFL history without a repeat champion is over at 18 seasons (2005-22).

The Chiefs have done it a little differently each time, though the ending that links all three has been Mahomes rallying the team back from a 10-point deficit in the Super Bowl and being named MVP. He joins Bart Starr (1966-67) and Terry Bradshaw (1978-79) as the only players to win Super Bowl MVP in back-to-back years.

But 2023 was just a season-long epic performance from Steve Spagnuolo’s defense, fairly reliable special teams, and Mahomes’ receivers did not screw up the games in the postseason like they did in the regular season. Ending things with a touchdown pass to Mecole Hardman, one of those scrutinized targets, was just the cherry on top to another year where the Chiefs beat the odds to finish with a championship.

This was a wild Super Bowl. If you ask me:

  • First 42 minutes – a bottom 5 Super Bowl all time with a bunch of fumbles (indoors to boot) and drive-killing plays
  • Last 33 minutes – a top 5 Super Bowl all time with 7 straight scoring drives to end it (minus a kneeldown)

I’d like to try to get into bed by 8 AM, so let’s jump into the recap and put this season to rest after another historic Super Bowl.

This season in NFL Stat Oddity:

The First Quarter: Scoreless

The 49ers came out strong doing exactly the things I thought they needed to do to win this game. That meant quality runs by Christian McCaffrey and easy completions to help Brock Purdy’s nerves. They chewed up 46 yards in 4 snaps before an unexpected blunder when the Chiefs forced CMC to fumble at the Kansas City 27, and they were able to jump on top of it for a shocking turnover.

The Chiefs had that incredible streak going of 8 straight playoff games with an opening-drive score (6 TD, 2 FG), but that came to a screeching halt with a 3-and-out. It was almost doomed from the first snap when Isiah Pacheco was stuffed for a 3-yard loss. Little did we know the 1-yard screen to Travis Kelce would be his only catch of the first half.

While Kelce sorted himself out later, George Kittle never got going in a hugely disappointing game for the other star tight end in this matchup. Kittle had an 18-yard catch wiped out by a holding penalty on Trent Williams, who was also called for a false start before the play. When that sets up 2nd-and-27, you might as well forget it against this blitzing defense.

Penalties didn’t become a huge story on the night – thank God – with both teams getting flagged 6 times. The Chiefs actually had more penalty yardage than the 49ers (55-40), so we can put the conspiracy theories to rest on the Swifties getting the calls.

But right from the second drive you could see pass protection was going to be an issue for Mahomes. Left tackle Donovan Smith was beat cleanly for a sack by Chase Young, and the 49ers almost brought Mahomes down for another sack before he scrambled for 4 yards on 3rd-and-14 on another short drive.

While the quarter ended scoreless, the 49ers had a drive going and it was actually the secondary receivers who were making the big plays. Chris Conley (18 yards) and Ray Ray McCloud (19 yards) pulled in back-to-back plays that gained more yards than the Chiefs had in the entire first quarter (16 yards).

Things were looking like 4 years ago when the 49ers played very well on defense and the game swung on a crucial 3rd-and-15 in the fourth quarter. But so far, Purdy was holding up very well and Mahomes wasn’t able to get in a rhythm.

This was only the 10th scoreless first quarter in Super Bowl history. The previous 5 all involved the Patriots.

The Second Quarter: Strange

After Kansas City corner Trent McDuffie made a great play to prevent a long touchdown to Deebo Samuel, the 49ers decided to try a 55-yard field goal. I’ve been hammering on Jake Moody being problematic as a rookie kicker, but he made me eat crow in this game. He calmly hit a 55-yard field goal, which was a Super Bowl record (for the time being) to get the first points on the board.

I’ll bemoan the Chiefs and their short-yardage flaws later, but they were getting creative with Rashee Rice taking a handoff on a 3rd-and-1 to convert on the ground. He actually looked like he tried to pitch it forward on the play, which should have been a penalty in my book, but nothing was said or flagged. Instead, it goes down as a fumble in the play-by-play that the Chiefs recovered, a theme of the night as they would recover 6 of the 7 fumbles in this game.

After Rice’s odd play, Mahomes went deep and found Mecole Hardman for the longest play of the game at 52 yards, which was hilarious since he is usually so awful at tracking the ball in the air. But he made that play work and the Chiefs had life. However, Pacheco continued what turned out to be a bad game for him and he fumbled from the 9-yard line, making sure the obligatory fumble was alive and well for Kansas City.

This kicked off a series of strange events, including Kelce’s meltdown on the sideline where he approached coach Andy Reid and was visibly frustrated with not being on the field for the Pacheco fumble:

We know he’s an emotional player, but this was a bad look for Kelce. The Chiefs followed that play up with a horse collar tackle of Purdy, but the defense delivered with a third-down pressure that led to a sack of Purdy. The Chiefs lost out on points on the Pacheco fumble, but at least it was still 3-0.

But the pressure on Mahomes was becoming the story again in a Super Bowl. The next drive was torpedoed from the first snap when Mahomes was pressured, held onto the ball a bit too long, and he tried to throw the ball away in the vicinity of his receiver. The officials didn’t agree and flagged him for intentional grounding, bringing up a 2nd-and-20. That call was iffy. The drive ended with Mahomes scrambling again for a few yards to avoid a sack.

In the end, Mahomes ended up taking 3 sacks on the night, and it could have easily been double that or more. Keep in mind, the only game in Mahomes’ NFL career where he took 5 sacks was against the Cardinals in 2018. Their head coach was Steve Wilks, who is San Francisco’s defensive coordinator. Things were looking good for his unit so far in this one.

Unfortunately, the 49ers lost a very good linebacker in Dre Greenlaw prior to this drive when he injured his Achilles in a freak moment of celebration coming onto the field. I’ve never seen anything quite like this:

What an awful way for your season to end. But the Chiefs were starting to lose their composure with another 15-yard penalty going against L’Jarius Sneed on the ensuing drive. Two plays later, the 49ers dialed up a trick play with wide receiver Jauan Jennings making the long pass back to CMC, who was left alone for a 23-yard touchdown to take a 10-0 lead. Pretty play with a sweet camera angle like this:

Like clockwork, it’s a Chiefs’ Super Bowl with Patrick Mahomes and they’re down 10 points. It’s happened all four times now, but they obviously have the experience at winning these games.

After CEH was stuffed for no gain (predictable) and Hardman was flagged for a false start, Mahomes was facing a 3rd-and-9 at his 40 at the 2-minute warning. I saw this as the play of the game so far:

Mahomes had barely thrown the ball before this drive, but in the big moment, he bought himself time and found Justin Watson for 21 yards. Huge play as the 49ers were not able to manage the clock and really give themselves another shot to score before halftime. The Chiefs marched into the red zone, but their play calls were a bit odd with Rice getting another rush on 2nd-and-7. Mahomes took another sack on 3rd down and the Chiefs had to kick a 28-yard field goal, but at least it was points on the board.

The Chiefs could have done a lot worse than 10-3 at the half.

The Third Quarter: Turning Point

This game was always going to come down to the second half, and we had all those interesting stats to watch play out here:

  • The Chiefs allowed the fewest points after halftime
  • The 49ers scored the most points after halftime
  • The Chiefs scored the 3rd-fewest points after halftime
  • The 49ers allowed the 2nd-fewest points in the 4th quarter

With numbers like that and the way these teams have recently played, I thought maybe we’d see a role reversal and the 49ers would have to be the team trying to come back this time. But instead, it was business as usual with Mahomes trying to lead the Chiefs back.

Things got off to a horrendous start when on the first play of the half, Mahomes pitched back to Pacheco and he didn’t handle it and nearly caused a fumble, an unforced error. That made it 2nd-and-22, practically short-circuiting another KC drive on the first snap, something that happened a solid 3 or 4 times in this game. The pitch from Mahomes could have been better, but Pacheco was caught looking upfield early.

Two plays later, Mahomes made his only real mistake with an interception on a forced throw on 3rd-and-12. In the first half, his only 2 incompletions were the debatable grounding and a pass Justin Watson could have caught but didn’t. This was the first time Mahomes really put the ball in danger and missed.

But the 49ers did not make him pay for it from the Kansas City 44. They called 3 straight passes, had a false start in the mix, and Purdy ended up scrambling for 4 yards on 3rd-and-15 to end the drive with a punt. This is why many might say the 49ers lost this game in the third quarter when they failed to take advantage of moments like this and passed too much. There is some truth to that, but it’s also true that they needed more points to win, and CMC was getting stuffed pretty well ever since his fumble. Purdy looked like he was handling the moment fine, but the Chiefs did get creative and relentless with their 3rd-down blitz packages.

But this was turning into a really lousy Super Bowl at this point with the teams unable to move the ball. The Chiefs went 3-and-out again after Pacheco was stuffed on a 3rd-and-1, because they refuse to run the tush push or normal quarterback sneak.

Purdy tried to create something with a pass to Jennings, but he lost 8 yards and killed the drive for another 3-and-out.

At this point, Mahomes started to take matters into his own hands, or more accurately – his own legs. He scrambled for 4 yards to convert a 3rd-and-4, then he took off by design for 22 more yards. But the drive stalled and Harrison Butker made sure Moody’s record didn’t hold up for 2 full quarters as he nailed a 57-yard field goal to make it 10-6.

The kickers at least showed up to play.

This game really needed a spark as the teams went back to trading 3-and-out drives. I was thinking the Chiefs were now going to win 13-10, fueling the conspiracy theories about it being fixed – 13 is Taylor Swift’s lucky number – and taking away one of my favorite stats where Tom Brady is the only quarterback to win a Super Bowl scoring 13 points. Actually, he did it twice too if you consider the offense only scored 13 in Super Bowl 36 against the Rams.

But with just under 3 minutes left in the quarter, we had our turning point on a real fluke of a play.

The 49ers were trying to field the punt, it grazed the heel of a San Francisco player, and McCloud did not make a great effort to pick up the ball. The Chiefs got it instead and were only 16 yards away from the lead. Mahomes immediately found MVS wide open for a go-ahead touchdown and the game was on at 13-10.

After the Chiefs took their first lead of the game, this really woke everyone up and led to one of the greatest finishes in Super Bowl history.

The Fourth Quarter: Back and Forth

We know even a 3-point deficit to start the fourth quarter is usually a deathblow for a Kyle Shanahan team in San Francisco. But things have been different this postseason, and they were driving again behind Purdy this time.

But what a ballsy call Shanahan made that will largely be forgotten because of the loss. Facing a 4th-and-3 at the Kansas City 15 with 12:46 left, Shanahan had his offense go for it and bypassed the game-tying field goal. I have to say I probably would have kicked it given the low-scoring game and the fact it was 3 yards to go, and you weren’t even in goal-to-go. A lot of risk with that call, but Purdy found Kittle, and he made his only real positive contribution of the game as a receiver with a 4-yard conversion.

Two snaps later, Purdy found Jennings over the middle and he fought his way into the end zone for a 10-yard touchdown to regain the lead. Could it really be possible that Jennings would win Super Bowl MVP with his touchdown pass and touchdown catch? I really think it would have happened if the 49ers held on to win in regulation, but a lot of time remained (11:22).

Also not good was Kansas City blocking the extra point, keeping it a 16-13 game. We could argue this ended up benefitting the 49ers later as it made the Chiefs feel content with a field goal to tie the game on the next drive instead of having to go for a touchdown on 4th down. Mahomes was sacked again on 3rd-and-goal at the 3, making the field goal a no-brainer in a 16-13 game for the Chiefs.

All things considered, I’d still much prefer to be up 17-13 and make the Chiefs go for a touchdown as they have had some issues with the red zone at times this year. Also, you never know when a low snap will derail their drive as that was a problem in this game again, and it was nearly a disaster with just under 10 minutes left. Mahomes had to field the poor snap and throw the ball away, narrowly avoiding another turnover. Creed Humphrey is a 2-time Pro Bowl center, but someone needs to work on his shotgun snaps with him because this is past the point of ridiculous.

We were tied again with 5:46 left. It wouldn’t be easy, but the 49ers had a chance to work the clock and kick a game-winning field goal with no time left. The Chiefs were down to 2 timeouts after Reid wasted one early in the third quarter to set up a Pacheco run on 3rd-and-1 that failed. In fact, that sequence was nutty as he could have challenged a possible bad spot on a Kelce catch that brought up that 3rd-and-1, but instead he just wasted a timeout for nothing. It really could have haunted the Chiefs here as the 49ers came so close to making this the knockout drive and finally delivering a Super Bowl ring to Shanahan.

A pass to Kittle for no gain was not an ideal outcome, but the play took so long that the 49ers did not have to run another play until the 2-minute warning, which was huge. This basically put the game on a 3rd-and-5 at the Kansas City 35. If the 49ers could convert, they could run out most of the clock on the Chiefs and kick the winning field goal.

But Spags sent another blitz and Trent McDuffie was the hero with a pass defensed in Purdy’s face. According to Next Gen Stats, Kansas City’s blitzing led to 9 unblocked pressures, their most in any game this season, and none were bigger than that one by McDuffie.

Again, credit Moody for silencing the critics with a 53-yard field goal. He played a great game. The 49ers led 19-16 and it was like watching a reverse of the 1988’s season Super Bowl when Joe Montana broke the Cincinnati Bengals’ hearts for the 49ers in a 20-16 comeback win.

Mahomes was going to have his moment with 1:53 and 2 timeouts left, an eternity for him to drive 75 yards for the winning touchdown. He made getting into field goal range look easy, but things perked up for the touchdown when he found Kelce on a 3rd-and-7 for 22 yards, getting out of bounds at the San Francisco 11 with 10 seconds left.

Kelce had 1 yard at halftime and still finished the game with 93 yards, his 13th-striaght playoff game with at least 70 yards (next closest is 7 games).According to Next Gen Stats, Kelce reached a top speed of 19.68 miles per hour on that 22-yard gain, his fastest speed in the last 7 seasons. That’s a pretty good argument for “wanting it more” on the big stage with your super-famous girlfriend watching.

But there wasn’t a Hollywood ending with Kelce catching the winning touchdown in regulation. The Chiefs only really had one shot at it, and while Mahomes went to Kelce, the play wasn’t there and they had to kick the field goal. Butker did his job from 29 yards out and we were getting overtime as Purdy took a knee with 3 seconds left.

Overtime: Underthinking the New Rules?

I have been wanting to see an overtime playoff game ever since they changed the rules two seasons ago. The irony is they changed them because of the way the Chiefs beat Buffalo in that 42-36 game in the divisional round. The Chiefs tied it in 13 seconds, they won the coin toss, drove down the field for a walk-off touchdown and Josh Allen, in his finest moment, never saw the ball again.

We can’t keep letting that happen just as it should have changed after Super Bowl LI ended that way between the Falcons and Patriots, and then again two years later when these Chiefs lost that way to the Patriots in the 2018 AFC Championship Game.

So, the Chiefs have been on both sides of this, but now they were in uncharted territory with the new rules allowing for both teams to get a possession even if there’s a touchdown. Well, a safety on the opening drive ends it too as would a defensive return touchdown. It’s a little weird to talk about, but the heart of the rule change is definitely in the right spot and we should see more fair outcomes like this was.

But new rules should mean new strategies, and I’m not sure Shanahan and the 49ers thought this one through in overtime.

In college, the common strategy is to go on defense first because you’ll know what you need on offense. I have to think that translates a lot here in the NFL’s new overtime system too. I think you go first on defense so you know what you need, and you can get it by playing 4-down football with no time rush at all. That means 4 plays to get 10 yards the whole way, and it doesn’t matter if the clock expires and you’re still trailing. The game will just go to overtime No. 2.

At least that’s my understanding of it now. During the game, I was not sure about the clock situation, and I know I wasn’t alone in that.

But in getting back to the strategy, I just don’t think you can realistically give Mahomes the ball last. Even if you get a touchdown and lead by 7 points, they can march down, score the touchdown, and go for 2 and the win and you never see the ball again. That is allowed, so the argument of “you get the first crack at a second possession” doesn’t sit well with me when Mahomes is the opponent.

Plus, if you go first like San Francisco, you are rather limited by more conventional, 3-down football. You are more likely to kick a field goal if it’s available. That’s just the nature of the game.

I also don’t buy the “49ers needed to rest the defense” argument. The Chiefs did run 11 more plays in the second half, but the 49ers won time of possession for the game (38-36 minutes). You really couldn’t handle a 2-minute drill that involved 2 timeouts, which was followed by another couple minute break before overtime?

And there is no guarantee of rest. The 49ers were about to go 3-and-out in overtime if not for a weak holding penalty on McDuffie on a 3rd-and-13 incompletion. They would have been right back on that field and with the Chiefs only needing a field goal if not for that call.

Like I said, if the Chiefs go first, they are going to be a little more careful and conservative, not always using 4 downs and going for the kill with the touchdown. With the game Pacheco was having, let them run more conventional plays instead of putting the game in Mahomes’ hands. Then even if Mahomes drives for a touchdown, you know they’re kicking the extra point. You get it back, down 7, and you can go win it with 8 and take your time in the process.

I just think it was absolutely the wrong call by San Francisco to go on offense first against Mahomes. You might get away with that against Burrow or Lamar. Not this quarterback.

Sure enough, the 49ers did not finish the job. They reached the Kansas City 9 before McCaffrey was stuffed, then another pressure by Chris Jones forced Purdy to throw the ball away, bringing out the field goal team on 4th-and-4. If they were more aggressive or behind, they are going for that 4th-and-4. But given the situation, it is practically impossible to bypass that field goal, so you take it and pray the Chiefs screw up or you get the ball again.

By the way, the 49ers were 3-of-12 on 3rd down while the Chiefs were 9-for-19. That mattered a lot too.

With 7:22 left, Mahomes was 75 yards away from one of the biggest legacy drives in NFL history. He could join the exclusive club of 3 Super Bowl winners, and it is the first time in NFL history we’ve ever seen a trailing team with the ball in overtime of the Super Bowl.

But it almost ended in 4 snaps. Pacheco was stuffed on another 3rd-and-1 run, and that’s when I thought this team’s refusal to run the quarterback sneak was going to cost them a championship. They just will not do it with Mahomes because he dislocated his kneecap in a freak accident play in Denver in 2019. It’s chickenshit logic that reminds me of how my uncle won’t eat kielbasa (unless it’s Easter or Christmas) because he ate a piece of glass from a package of it decades ago. Apparently, they screen out all the glass for holidays.

On 4th-and-1, season on the line, the Chiefs did put the ball in Mahomes’ hands, but it was on a keeper and he ran for 8 yards to save the game. Then MVS tried to give up the repeat bid on the next snap. Instead of cutting his losses on a play, he kept running backwards and lost 3 yards to set up 2nd-and-13. At least he made up for it with a 7-yard gain, then Mahomes found Rice to settle things down for 13 yards on 3rd-and-6.

Another 3rd-and-1 came up, and it was another scramble by Mahomes for 19 yards into the red zone that started to make this ending feel predictable, or inevitable with Kansas City. Pacheco ran for 3 more yards, Kelce caught a short one and took it 7 yards as you could see he wanted the touchdown so bad.

But that made it 1st-and-goal at the 3, and the clock just continued to tick down. Honestly, I wasn’t sure if the game was about to end or go to another overtime at this point, because the idea of a clock expiring with a team still trailing and the game continuing just doesn’t compute for me in the NFL (or NBA).

I found out after the game the rule is that if the second team’s initial possession has not been completed yet, the game does extend to a second overtime. So that’s that.

But with the Chiefs playing it casually and the 49ers not calling a timeout, the ending was almost anticlimactic as Mahomes hit Hardman with one of those uncovered passes to the flat they beat the Eagles with a year ago. Enjoy the Korean call of it:

After berating the wide receivers since Week 1, we watched Mahomes complete 9-of-13 passes for 131 yards and 2 touchdowns in the Super Bowl to the trio of Mecole Hardman, MVS, and Justin Watson. Meanwhile, Purdy was 8-of-20 for 86 yards throwing to his stud trio of Deebo, Kittle, and Aiyuk. That was largely the ballgame as CMC did finish with 80 yards on the ground and 80 through the air. Jennings stepped up. The run defense stepped up against Pacheco. The pass rush was very strong early for the 49ers before Mahomes started finding rushing lanes to exploit.

There wasn’t a singular moment this time as much as in LIV when Mahomes finding Tyreek Hill on 3rd-and-15 was the difference maker. But the 49ers had a few chances to put this game away and just didn’t do it.

That Shanahan, always a bridesmaid. I think he should have kicked off in overtime. Instead, we watched Mahomes become the first quarterback in NFL history with multiple walk-off touchdown passes in the postseason. He was the last to do it under the old rules, and he’s the first to do it in the first game with the new rules.

That is some king shit. So is having three of the top 5 postseasons in QBR for a Super Bowl-winning quarterback since 2006:

With 333 passing yards, 66 rushing yards, and 2 touchdown passes, Mahomes won his third Super Bowl MVP award. He is the only player to win that award for 3 consecutive rings won. Even Joe Montana needed to reach a fourth after Jerry Rice won the MVP for his third ring. Tom Brady’s third ring saw Deion Branch win the Super Bowl MVP against the 2004 Eagles.

Montana, Brady, and Mahomes all won their third Super Bowl in a season where they beat the No. 1 scoring defense on the road in the Conference Championship round.

But the 2023 Chiefs are the first team to ever beat 4 teams in the same postseason that had a +100 scoring differential in the regular season. They did this despite not being one of those teams themselves as they were only +77.

But after trailing the Bengals 17-7 in Week 17, the offense hit a switch, and it reached a level it could win games at with this defense providing a stellar performance since Week 1. The Chiefs never gave up more than 27 points in any game this season, and they even held all but one opponent under 25 points. You’re not going to put this defense on a historic level with the 2000 Ravens, 2002 Buccaneers, or 2013 Seahawks, but they were legitimately great this year and helped the team overcome one of the toughest postseason paths anyone has taken to a Super Bowl win.

You can say this is a team that got hot at the right time and carried that all the way to a Super Bowl win. But unlike the 2011 Giants or 2012 Ravens, this team has staying power and can do it again. This is closer to the 1988 49ers shaking off a 10-6 regular season and winning the third Super Bowl in the Joe Montana era, and we know what kind of encore that team had in 1989.

Conclusion: Yes, It’s a Dynasty and Mahomes Is 1-of-1

It’s been 19 long years, but we can finally add another dynasty to the annals of NFL history. The Chiefs were the expected pick to replace the Patriots for this years ago, but they gave us pause on multiple occasions since winning that first Super Bowl right around the time the world was starting to face a global pandemic with COVID-19.

They lost 31-9 to the Buccaneers in Super Bowl LV. They blew a 21-3 lead to the Bengals a year later at home in the AFC Championship Game. Then I thought last year would be the crowning achievement of Patrick Mahomes’ career, winning that Super Bowl with an MVP season and top offense after losing Tyreek Hill, then navigating that playoff run on a high-ankle sprain.

But this season was almost more impressive in some ways. He didn’t play as well individually, but he hung in there through the rough losses, the league-leading wide receiver drops, the excessive penalties and fumbles, and he knew he could trust the defense this time. Then they got it done on the road in the playoffs twice after never having to leave Arrowhead in January before. They took down both No. 1 seeds. They came back from 10 points down in this game. He had nearly 400 yards of offense and was flawless in overtime.

I always ask what is Mahomes’ weakness? I don’t think in 114 starts he has shown one yet. You have a better chance if you can make him hold the ball and throw low-percentage passes down the field, but we’ve also seen him destroy some teams by extending the play. Even in this game, I think that 3rd-and-9 conversion to Watson at the 2-minute warning in the first half was a game-changing moment to keep the Chiefs alive.

In all of NFL history, we have not seen a quarterback play this well so consistently while still being able to win at such a high level as often as Mahomes has. Usually, dynasties were stacked on defense, or they could run the ball really well, or they just didn’t have to rely on the quarterback as much. But the Chiefs are an outlier because their quarterback might just be 1 of 1 in this game.

My interest in the NFL was starting to wane in the 2017 season. Maybe it was the 7-year itch or burnout of covering this stuff 52 weeks a year with no real breaks. Getting into gambling helped some that year, but Mahomes taking over for the Chiefs in 2018 and instantly turning this into a historic team that’s always setting some record has rejuvenated my interest more than anything.

I want to make sure Mahomes and the Chiefs are being covered properly for their place in history. So, when a big game like this one comes up, I put things into perspective for what a win or loss means for the team. When Mahomes is telling CBS in his pre-game taped interview that dynasty is the goal, and Jim Nantz starts off the 6:00 p.m. broadcast window with dynasty talk, it was the big story of the night. The Chiefs would hands down be a dynasty with a third championship in five seasons.

But if they had lost this game? Then you start having people looking differently at a team that’s only 2-2 in the Super Bowl, and at a quarterback who had 5 touchdowns and 5 interceptions in those Super Bowls before the blocked punt changed the dynamics of this game. Suddenly it’s “what if Purdy didn’t get injured in Philly last year; he might be 2-0 in the Super Bowl and have more rings than Mahomes.”

You nip that talk in the bud by performing and winning the game, which he did again. Does it take some luck too like a muffed punt off a teammate’s heel? Does it take a defense stopping a great offense repeatedly on third down, and a kicker you can rely on for a long field goal? Yeah, it takes some combo of that too, every time.

It wouldn’t be the ultimate team game without those things. But where I take issue is when people still try to belittle his accomplishments by poorly comparing and equating them to some of the only quarterbacks you can even still compare Mahomes to as a 2-time MVP and 3-time Super Bowl MVP.

They’ll say Mahomes doesn’t win without his defense this year. Yeah, as if Bart Starr, Terry Bradshaw, Joe Montana, Troy Aikman, and Tom Brady were winning shootouts all the time and didn’t almost exclusively have top 10 defenses when they won their rings. Meanwhile, Mahomes is the only quarterback to win a Super Bowl when his team allowed 25 points per game in the postseason, and he’s done it twice. That number was much lower this year (15.8), but he still can’t hold a candle to Montana, who won 3 rings in postseasons where the 49ers did not allow more points than the 35 the Eagles scored in last year’s Super Bowl.

They’ll say Mahomes threw a pick in this game. But will they note it was on 3rd-and-12 and the 49ers went 3-and-out from midfield with it? It’s not like he threw a pick-6 to Robert Alford to fall behind 21-0. Will they acknowledge their King of Kings from New England, even in his best Super Bowl moment against the 2003 Panthers, threw a terrible red-zone pick midway through the fourth quarter when he could have taken a 2-score lead? Or that his game-winning drive that day started at the 40-yard line in a tied game after John Kasay sailed the kickoff out of bounds? Not quite driving 75 yards for the touchdown while facing a deficit in overtime, is it?

Also, will they ever acknowledge Montana had 4 turnovers before The Catch happened in the 1981 NFC Championship Game? Still put up enough points and won the game with a clutch drive, didn’t he? That used to be enough for the old days, but you know they fear Mahomes when they have to treat him differently and start holding him to standards they never put the past greats through.

But he keeps finding ways to succeed, and he should be the new standard for quarterback play if we are being honest about things. Does that mean he’ll win a lot more rings going forward? That will depend on what the rest of the league does more than anything. But I never believed for a second that Mahomes needs to win 7 or 8 Super Bowls to be the GOAT.

He’s up to 3 before his 29th birthday. He has some wiggle room as the LOAT did not win his 4th until he was 37 years old. Mahomes can win next year for the first 3-peat in the Super Bowl era. If he can do that, then win a fifth down the road without Reid and Kelce, I don’t see how anyone can reasonably deny him, assuming he’s also not done winning MVP awards and setting the pace for the most yards and touchdown passes in NFL history.

Mahomes and the Chiefs are a historic team, and that keeps me interested in the future to see where this story grows and goes. This was my 13th season of coverage, and it was a challenging one. I was dealt a personal shock in August, just 3 days after one of my oldest cats died, that I still am not really over. I guess you can say I should have researched this girl I thought I knew for the last 6-7 years as well as I’ve researched Mahomes for his 7 seasons as an NFL quarterback. Be careful who you trust in this world. There aren’t many people who are genuinely looking out for your best interests.

Then it seems like I’ve been sick every day since December, which is why I’ve had so many short posts on here for prediction pieces on the weekend because I usually didn’t feel that great. Just a lot of sinus stuff with sneezing attacks, then I got the flu in January for a couple of weeks, and I’m still coughing at times from that.

Hopefully there isn’t another pandemic brewing since the Chiefs took down the 49ers in the Super Bowl again, just like when COVID started four years ago.

I’m not sure what my offseason plans include, but I expect to be back for another season of NFL coverage. It is a grind, though. I’d love to make use of the next 7 months to also make sure I’m taking care of my mental and physical health better, since that can go ignored during the grind of the season.

But the offseason always hits better when the Super Bowl outcome was to your liking. At least I got closure from something I love this year.

NFL Stat Oddity: Super Bowl LVII

~ Scott ~ Leave a comment

After a season filled with low-scoring island games, the 2022 NFL season finished with a very good 38-35 Super Bowl that may have been one fewer flag away from an instant top five classic. Either way, Super Bowl LVII made history as the first Super Bowl where both teams scored at least 35 points.

It also rewrote the standard again for what kind of teams we can expect to win a Super Bowl, and no surprise that is thanks to Patrick Mahomes, who went home with MVP honors after throwing three touchdowns and making very few mistakes.

  • It took 57 years, but Mahomes is the first quarterback to lead the league in passing yards and win the Super Bowl in the same season.
  • Mahomes is the first quarterback since Kurt Warner (1999 Rams) to win MVP, first-team All Pro, and Super Bowl MVP in the same season. MVPs were on an 0-9 Super Bowl run and first-team All-Pro quarterbacks were 0-8 before Mahomes’ win.
  • The Chiefs join the 2006 Colts and 2011 Giants as the only teams since 1989 (and likely ever) to win a Super Bowl with a defense ranked lower than 15th in points per drive allowed. The Chiefs were No. 21 this year and won this game despite allowing 35 points on 10 drives.
  • Mahomes won this Super Bowl with a cap hit of 17% this season – the previous high for a Super Bowl-winning quarterback was Steve Young (13.1%) on the 1994 49ers, the beginning of the cap era.
  • The 2022 Chiefs are just one of seven Super Bowl winners to have a minus-3 or worse turnover differential in the regular season. But they were plus-4 in the playoffs.
  • The 2022 Chiefs are the first defense to win a Super Bowl after allowing 30 touchdown passes in the regular season. They allowed 33, four more than any other defense this year.

But in winning 38-35, the Chiefs did it their way. Jalen Hurts is now 15-2 when he leads the Eagles to at least 27 points, and both losses are to Mahomes, a f’n unicorn who just solidified himself this weekend as a first-ballot Hall of Famer with two Super Bowl MVPs and two MVP awards in his first six seasons. The only other two quarterbacks to do that needed 11 (Tom Brady) or 12 (Joe Montana) seasons to achieve it.

For the fourth time in the last nine Super Bowls, we had a team come back to win after trailing by double digits in the second half. That happened zero times in the first 48 Super Bowls.

I’d call it your classic Chiefs comeback against the front-running Eagles, akin to Super Bowl LIV against the 49ers, but this game was actually quite different. But by and large, this was a Kansas City script with a couple plot twists along the way.

This season in Stat Oddity:

The Least Valuable Player: The Turf

Before we get into the recap, the worst part of the game was the field surface in Arizona. If they really spent so much time and money growing this grass, then it was a waste as players were slipping all night. It did not really affect the outcome, and ultimately the game still had 73 points, but it sure would have been nice to see a better playing surface for the biggest game of the year.

This stadium has hosted some great big games, and god knows the Cardinals aren’t using it much in January and February, so when they bring the Super Bowl back to Arizona, hopefully the field will be better than this.

The First Quarter: Early Fireworks

Right from the start this was looking like an explosive Super Bowl with both offenses scoring a touchdown with their go-to players getting it done with Jalen Hurts on the QB sneak and Travis Kelce on a well-designed 18-yard route.

But you did also see some big hits, which became common in this game too. There was a lot of quality play all around, but an offensive pass interference penalty short-circuited the Eagles’ second possession for the first punt of the night.

So much for Mahomes and Kelce not being healthy, because the duo hooked up for a quick 60 yards on two drives to start the game. Kelce had just 23 yards against the Eagles last year, but you could throw that result out the window in this one as he still found ways to get wide open early.

But the Eagles would do a better job after those first three catches, and they also did a good job of holding down most of the other receivers on the night. Just enough pressure on Mahomes nearly forced an interception on a third down, but the Chiefs settled for a 42-yard field goal instead of going for a fourth-and-3.

This was probably Andy Reid’s biggest mistake of the night as the Eagles have been the more aggressive team and probably would have gone for that fourth down. Harrison Butker hit the left upright with his kick as he can often do on lower-pressure plays, and there went a golden opportunity for Kansas City’s first lead as the game went into the second quarter tied 7-7.

The Second Quarter: Eagles Do Their Thing

Over four months ago I was pointing out how historic the 2022 Eagles were in the second quarter. But even when the team was 6-0, I thought it was odd how they dominated that one quarter so much while not being special in the other three.

At 8-0, the Eagles had scored 133 points in the second quarter, the most points any team has had in any quarter through eight games in NFL history. This is why the Eagles were the third team since the 1970 merger to not trail in its first eight games. But this was clearly not going to sustainable. Would it be fatal down the stretch in a tight game and when the Eagles faced a legitimate quarterback for a change?

By season’s end, the Eagles were +116 in the second quarter and just +17 in the other three quarters combined. I did not think that was a good formula for the Chiefs, who we know can come back with the best of them.

But the second quarter was both as good as it got for the Eagles and a costly one as one huge mistake would haunt them.

The Eagles started their favorite quarter with Hurts taking a chance deep to A.J. Brown, and what looked like it may lead to defensive pass interference actually just laid in perfectly to the receiver for a 45-yard touchdown bomb.

The Chiefs went three-and-out after JuJu Smith-Schuster was clearly interfered with on third-and-8, but there was no penalty for some reason. More on that later.

After Hurts converted a third-and-8 with a brilliant scramble move, he really looked like the ultimate dual threat who was having a great game in his first Super Bowl. But then came the moment where the Eagles may have blown this one. One thing the team really struggled with all night was running the ball with the trio of backs, who combined for just 17 carries for 45 yards. If you thought Miles Sanders sucked against the Chiefs last year with 7 carries for 13 yards, he only had 7 carries for 16 yards in this one.

But on a second-and-1, it was Kenneth Gainwell who was stopped short to bring up third-and-1. No worries, the team who has turned the quarterback sneak into an even bigger cheat code would pick it up with ease. But that doesn’t happen when you get penalized for a false start as the timing was off for the Eagles. Huge mistake. On third-and-medium, Hurts tried a quarterback draw, but he just lost the ball on an unforced error, and Nick Bolton was there for the 36-yard scoop and score to tie the game.

It is so hard to win a Super Bowl when your offense coughs up a turnover for a touchdown, and that is the third time this season the Eagles did that in a game they went on to lose. The other time they just had four turnovers against Dallas, but this ended up being the only turnover in the whole game.

I was curious to see how Hurts responded to that blunder, but he did a great job and used his legs well to convert a ballsy fourth-and-5 with a 28-yard run by slipping a tackle. He also got another fourth-down conversion by drawing the Chiefs offsides in the red zone. The drive fittingly ended with Hurts running in his second touchdown on a successful draw to take a 21-14 lead with 2:20 left.

This was the part of the game in Super Bowl LV where the Chiefs really blew it against Tampa Bay. They had to answer here but it was another bad drive with Mahomes scrambling on a third down and apparently aggravating his ankle injury. He looked to be grimacing in pain much worse than he did when he initially had the injury against Jacksonville, and it was much worse than the third quarter against the Bengals when he tweaked it.

Chad Henne was apparently warming up, and this just felt like the Eagles catching another break with an injured quarterback. The Chiefs had the ball for just 8:06 in the first half as the Eagles dominated with long drives while Kansas City really did not show a lot after that hot opening drive. That makes 16 points for the offense in the last six quarters of Super Bowl action.

Things were looking poor for the Chiefs after getting outscored 17-7 in the quarter, and it could have been much worse without Hurts’ unforced error. It also would be nice if DeVonta Smith can make a cleaner catch down the sideline after his 35-yard grab was overturned to incomplete after a lengthy review. I can understand why they overturned it, but I was still surprised that they thought the evidence was conclusive enough to overturn the call on the field of a 35-yard catch.

That was a big reversal as it led to only a field goal and 24-14 lead for the Eagles at halftime. Still, this was looking like a Philadelphia script with an injured Mahomes even if the pass rush in this game was minimized.

Rihanna > Beyonce, forever and always, but moving onto the second half.

The Third Quarter: Here Come the Chiefs

With a half-hour halftime and Mr. White in the house to inject Mahomes with some Crystal Blue Persuasion, the MVP was able to return to the game and still looked good. The run game was also looking good for the Chiefs again, and Mahomes even took a play himself 14 yards after it looked like the Eagles were surprised he could still move like that.

Two plays later, Isiah Pacheco was in the end zone for a touchdown, and we had a game again at 24-21.

On the ensuing drive, Bolton thought he had another fumble touchdown, but the refs got the call right of a bang-bang play and no catch, no fumble for Sanders and the Eagles. What ensued was another painfully long drive with some incredible completions from Hurts to Dallas Goedert, including a third-and-14 conversion that took forever to review, but they got the call right as it was a catch this time.

The quarterback sneak worked for another fourth-and-1 for the Eagles, and this 7:45 drive was threatening to put the Eagles back up 10, but the pass defense stepped up and made a stop. The Eagles had a couple fourth downs already converted, and I was surprised that Nick Sirianni did not go for a fourth-and-6 at the Kansas City 15, understanding how much more valuable a 10-point lead is instead of 6 vs. 3.

But the Eagles settled for the 33-yard field goal and a 27-21 lead despite taking half the quarter with that drive. You can say Sirianni coached a pretty good Super Bowl when his biggest mistake in three quarters was not going for a fourth-and-6.

But with the Chiefs driving towards midfield, you could see where this one was heading.

The Fourth Quarter: Chiefs Do It Again

This postseason has sucked ass for drama, but maybe we would get something good here as it was the 18th Super Bowl in the last 20 years to be within one score in the fourth quarter. This postseason’s only fourth-quarter lead change was Jaguars vs. Chargers, and that was on the final play of the game. We needed something more dramatic here, and we absolutely got it.

JuJu, who I loved back in Pittsburgh his first two years and not so much after, was huge on this drive as he had three straight catches to put the ball at the 9-yard line. Incredibly, Marquez Valdes-Scantling had one target and no catches in the game after being so good against the Bengals. Kadarius Toney also had no touches on offense, so the Chiefs were getting almost everything out of Kelce, JuJu, and the running game.

But on a third-and-3, the Eagles completely blew a coverage and Toney was left wide open, not unlike his first NFL touchdown with the Chiefs against Jacksonville earlier this season. Andy Reid did it again. The Chiefs made the extra point to go up 28-27 and – STOP THE COUNT – they had their first lead and a lead for the 101st time in the last 102 games.

It also meant the 2022 Chiefs are the first team to have a fourth-quarter lead in 20 games in one season. But would they hang onto it to join the 1984 49ers and 2013 Seahawks as the only teams to do it in at least 19 games and win the Super Bowl? That is exclusive company for sure.

With the Eagles unable to run, it was going to be on Hurts’ shoulders, and he does not have the track record yet in these situations. Sure enough, the Eagles went three-and-out and this thing was going all Kansas City’s way. Toney returned the ensuing punt, after a little mix-up at the beginning, for 65 yards, nearly housing it, which likely would have earned him the MVP honors for this game. But his impact was felt as it was the longest punt return in Super Bowl history.

Not bad for a Kansas City team that had its longest punt return of the season against the Bengals (by Skyy Moore) to set up their game-winning drive last game out. Now they more than doubled that with this one by Toney. Speaking of Moore, he finished off this drive with yet another blown coverage by the Eagles as he was left all alone for a 4-yard touchdown. Way too easy.

Should the Chiefs have gone for two at 9:22 left? I think it was a little early to get the full benefit of that one, but I fully understand the argument by doing it. Still, it was 35-27 and this is out of the Eagles’ comfort zone.

However, when the QB sneak has been unstoppable all night, and the slants to Brown are open all night, the Eagles quickly moved the ball. Smith got wide open for a 45-yard bomb that if thrown a little better, he would have walked in for a touchdown. But on the next play, Hurts set a Super Bowl record with his third rushing touchdown at the quarterback position, giving him a record 18 for the season. He even finished the drive off with the game-tying two-point conversion as the league may have to interfere with the rule book to stop the Eagles’ dominance in short yardage. No more push sneaks in the near future? We’ll see.

But we were all tied up at 35 with 5:15 left. With the leaked script (read: a funny meme that some take too seriously) calling for a 37-34 win by the Eagles, you may have had it in the back of your mind that maybe the Chiefs screw this up after three straight touchdowns and the Eagles do win this one on a last-second field goal for a 38-35 win. The internet would go ape shit over that.

But no, Mahomes really is just different. He found Kelce for another catch that allowed him to hit his over (81 yards) by two yards, which cost me $700 in parlay wins, but no sour grapes here. Kelce now has nine straight games in the playoffs with over 75 receiving yards, three more than anybody else. Pacheco was able to convert the ensuing third-and-1 for a 10-yard gain.

Then came a definitive play. Mahomes scrambled right down the middle of the field for a 26-yard gain, looking pretty spry in the process and putting the Chiefs in field goal range. The rest of this drive was going to be very interesting strategy as the Eagles had three clock stoppages left, and the Chiefs could not afford to give them the ball back in a 38-35 game with nearly two full minutes left. Not after how easy the Eagles scored on the last drive.

The Chiefs even screwed this up with conservative play. A screen to JuJu gained nothing and brought up third-and-8. Mahomes just kind of lobbed one towards the end zone for JuJu on third down, which would have saved the Eagles’ last timeout, but there came the flag. Defensive holding on James Bradberry. Automatic first down.

I get why they called it, but I have to agree with FOX’s Greg Olsen. That is a very soft call on a night where the refs were swallowing the whistle. Bradberry tugged on the jersey, but the throw was also way off from the receiver, and I don’t think it was restrictive enough to say it drastically altered the play for the Chiefs. They got bailed out of a bad sequence with that call, and now the game was going to have a shit ending because the Chiefs were just going to set up the field goal.

For all the talk about referee Carl Cheffers screwing the Chiefs over in the past, his crew called just 3 penalties for 14 yards on the Chiefs in this game. He had gone 12 straight games calling at least 92 yards worth of penalties on both teams in Kansas City games, and 12 straight where the Chiefs had over 47.5 penalty yards.

So this was a surprise, and worse, there were just three penalties in the game on post-snap action, and they were all on the Eagles. The other six penalties were all your pre-snap things like false start, delay of game, neutral zone infraction, and offsides.

The refs tried to stay out of the story this week, but they had a huge impact on how this game would end. The part that pisses me off the most is how can they justify not calling the DPI on the Eagles on a JuJu coverage play on third down in the second quarter, but then they call this ticky tack crap? This inconsistency is what drives people nuts.

The Eagles did the right thing by offering the touchdown to the Chiefs, but Jerick McKinnon was wise to go down in bounds short of the end zone. Mahomes ended up taking two knees for minus-7 yards, meaning the Chiefs had 165 rushing yards before that happened. That is another big running day against the Eagles, who had their biggest statistical weakness at stopping the run this year (24th in yards per carry allowed), and last year the Chiefs ran for 200 yards on them for just the second time in the Mahomes era. This was another outstanding running day when you consider the Chiefs only had eight drives to score their 31 points. The Chiefs only had the ball for 24:13 and still scored 38 points. The only other time that has happened in the playoffs was when Andrew Luck led a 38-10 comeback against Reid’s 2013 Chiefs in a 45-44 win despite having the ball for 22:27.

For the anticlimactic finish, Butker just had to not go Blair Walsh and make a 27-yard field goal. He did it, and the Chiefs led 38-35 with 8 seconds left.

The Eagles returned the squib kick 11 yards before Gainwell gave himself up. Six seconds were eventually put back on the clock after it went down to 4 seconds, but either the Eagles didn’t seem to realize that, or they just blew the situation. There was no way Hurts could throw a Hail Mary over 65 yards with his shoulder injury, so the call should have been a quick pass to the sideline to get closer, or you do the laterals. Instead, Hurts held the ball and just threw a duck well short of the end zone and to no one in particular to end the game.

Conclusion

The Chiefs did it. Lesser defense filled with rookies, QB taking up 17% of the cap, injured skill players – none of it mattered. They also won this as a team as Mahomes’ 182 passing yards are tied for his fifth fewest in a game. He got the big run support, he got the fumble return touchdown, and he got the longest punt return in Super Bowl history. Mahomes was the right call to win Super Bowl MVP for making very few mistakes all night and still leading the offense to 31 points on eight drives with a missed field goal, but he still won this with the kind of team support we usually don’t see behind an MVP in a big game like this.

For the Eagles, it is a letdown for sure. I can say Hurts has still never beat a good quarterback on a good team in the NFL, but this game raised my respect for him. The fumble was an unfortunate blunder, but those happen. Mahomes just did it against the Bengals two weeks ago. Hurts was leading the MVP race most of the night as his run game and defense severely let him down as the 70-sack defense proved to be a paper tiger in the end. They were rarely tested this year, and when they faced the Chiefs, they folded with no sacks, very little pressure, and those blown coverages in the red zone are inexcusable.

Incredibly, the Eagles (70) and Chiefs (55) led the NFL in sacks this year with 125 between them, yet the only two in this game were on scramble plays where Hurts twice ran out of bounds for a small loss. Not even legitimate sacks in my view.

Mahomes got the ball off in 2.69 seconds on average according to Next Gen Stats. He is now 47-4 when he gets the ball out in under 2.9 seconds, so this game was above average for his release time even if it wasn’t quite the 2.32 seconds from last year’s meeting.

To close a week where we celebrated LeBron James breaking the NBA’s all-time scoring record that lasted almost 40 years, we just witnessed another great achievement for Mahomes in winning a Super Bowl with this team. It is not quite up to the level of LeBron knocking off the 73-9 Warriors, but to overcome all the negative perceptions of this team being too inexperienced, too pass happy, too imbalanced, and too injured, this is a big deal. I agree with Mahomes that this win means even more than 2019 did for him.

There is a long offseason ahead to be talking about their chances at ending the repeat drought, and Philadelphia’s chances at getting right back to this game as the NFC is not the toughest path right now.

But I am going to let this one marinate, go up to bed in a good mood as it’s always an easier offseason when the Super Bowl goes the way you wanted it to, and this is the end of my 12th season covering the NFL. I would say I look forward to the break from football, but I am scheduled for multiple XFL and NBA pieces this week, so it looks like I will be keeping busy for the next six months until we do it all over again for the 2023 NFL season.

Unless the aliens get past our space lasers.

NFL Stat Oddity: Championship Sunday

~ Scott ~ 1 Comment

Two rematches. Two painfully familiar postseason outcomes for the teams on the losing side.

For the first time in 56 seasons of the Super Bowl era, we will have a Super Bowl without a team that seeded higher than fourth. The Rams and Bengals were both No. 4 seeds that spent very little time – if any in Cincinnati’s case – in the spotlight as the teams to beat this year.

But now they are all that’s left after erasing double-digit deficits in the second half. For Kyle Shanahan and Andy Reid, this is becoming old hat.

Of the five blown leads of 18-plus points in the NFL playoffs since 2013, Reid’s Chiefs have lost three of them and were the winning team in a fourth game against Houston (down 24-0 in 2019). The only other such game was of course Super Bowl LI, where as offensive coordinator of the Falcons, Shanahan infamously called doomed passes with a big lead in the fourth quarter. It has started a string of three postseasons where Shanahan’s teams have been bounced after leading by double digits in the fourth quarter and never scoring again.

This sets up a Super Bowl between two quarterbacks drafted No. 1 overall by the Lions and Bengals (11 years apart). It may be the last outcome I wanted to see out of the four possibilities, but if this is what the post-Tom Brady NFL is going to look like, I’m sure I will learn to love it.

This season in Stat Oddity:

Bengals at Chiefs: Whoops, They Did It Again

It was the best of halves, it was the worst of halves, it was the age of adjustment, it was the age of sloppiness, it was the season of defensive regression, it was the season of tipped giveaways, it was 13 seconds to restore hope, and it’s now another winter of despair for this failed attempt at a dynasty.

Even Charles Dickens knew he had to write different beginnings and endings to his books no matter how successful they were in the past. The Kansas City Chiefs continue to tease us with many wonderful things, but only one time (2019) did things end on a positive note.

If it wasn’t for Jet Chip Wasp on third-and-15 in Super Bowl LIV, we would be calling the Chiefs the biggest underachievers and disappointment in the NFL in the last decade.

They still might be even with that play.

As the favorite in the final four this year, the Chiefs just had to hold onto a 21-3 lead to become the fourth team to go to three straight Super Bowls. Instead, they became the fourth team in NFL playoff history to blow an 18-point lead at home and the first to do it in a championship game. In the process, the Bengals are the first team in NFL history to beat an opponent twice in the same season after trailing by double digits at halftime. The 18-point blown lead is the largest of the Patrick Mahomes era, and the Bengals own a tie for the second largest at 14 points in Week 17.

Why does this keep happening under Andy Reid? It’s his third playoff loss in nine seasons where the Chiefs led by at least 18 points. Since 2013, Reid has coached the Chiefs to a league-high nine different win streaks of at least five games, including an eight-game streak this season that again had people believing this was the team to beat.

But look at how things have gone for Kansas City under Reid:

  • 2013: 9-0 start built up by playing backup quarterbacks, but swept by Peyton Manning’s Broncos to lose division, and blew a 38-10 lead in the wild card round in Indianapolis.
  • 2014: thought to have ended the Patriots’ dynasty and also beat the Seahawks, the NFC’s Super Bowl team that year, but finished 9-7 and missed the playoffs.
  • 2015: took another suspicious 11-game winning streak into New England and took what felt like 11 minutes to score one late touchdown in a 27-20 loss in the divisional round.
  • 2016: came back to beat the Chargers, outdueled Drew Brees and Andrew Luck, scored 30 on Denver’s defense, beat MVP Matt Ryan on a pick-two, and still lost the first playoff game at home to six Pittsburgh field goals.
  • 2017: 5-0 start with a great win on opening night in New England but finished 10-6 and blew a 21-3 halftime lead at home to Marcus Mariota and the Titans in the Forward Progress Game in the wild card round.
  • 2018: Mahomes is the MVP, but lost 43-40 in New England, 54-51 to the Rams, and still ended up as the No. 1 seed thanks to a Miami miracle against the Patriots. But lost 37-31 in overtime at home to those Patriots after Dee Ford lined up offsides and negated a game-ending interception. Never touched the ball in overtime.
  • 2019: trailed by double digits in every playoff game before winning each game by double digits. Apparently, the right combo of opponents involves Bill O’Brien, Playoff Ryan Tannehill, and Playoff Jimmy Garoppolo. Still needed a 10-point fourth-quarter comeback to win the Super Bowl.
  • 2020: the hottest team in the league, but also a record winning streak of seven games by fewer than seven points. Kept it up in playoffs but lost offensive tackles for the Super Bowl and failed to score a touchdown in rematch with Tampa Bay. Dominated 31-9 by a play-action offense and two-high safety defense.
  • 2021: ugly 3-4 start before the defense turned things around thanks to the schedule. Offense started clicking again late in year, but defense regressed to early struggles. Very fortunate to win coin toss and march for a touchdown against the Chargers and Bills; the latter being 13 seconds away from knocking the Chiefs out in the divisional round. Fell apart after 21-3 lead on Sunday.

Like I said, this team teases us with wonderful things, then they shit the bed when it matters most. The one time they didn’t blow it, they were fortunate to be playing Kyle Shanahan, but scroll down for more on his chokejobs.

A team with Alex Smith at quarterback being exposed as fool’s gold is one thing, but expectations have been much higher with Mahomes the last four years. For 10-plus quarters this postseason, it wasn’t hard to see why. He was putting together a case for the best postseason run ever by a quarterback. Then he had arguably the worst half of his career.

It really was a tale of two halves similar to what happened in Week 17 when the Chiefs scored four straight touchdowns, led by 14 points, then were held to a field goal in the second half before losing by a field goal on the final snap. But the Bengals hit up the Chiefs with big YAC plays that day and controlled the clock at the end. Mahomes wasn’t inept in the second half like he was in this one. It was a different game with a similar outcome.

Mahomes was close to perfect in this first half. He hit 13 of his first 14 passes and the Chiefs scored three straight touchdowns to take a 21-3 lead. If you wanted the easy, short throws, he took them. The running game looked good with the backs fighting hard for extra yards. Tyreek Hill and Travis Kelce were heavily involved unlike they were in Week 17. It looked like an unstoppable offense while the Bengals looked unprepared for a big game.

But then a screen pass broke for the Bengals for a late 41-yard touchdown. The Chiefs were driving for another touchdown after getting a defensive pass interference flag, in a game where the refs really swallowed their whistles for both sides all day, that put the ball at the 1-yard line with 9 seconds left.

This is where the Chiefs basically lost the game. You get two quick throws into the end zone in that spot. The Chiefs should have had another timeout, but they wasted one early in the game before challenging a bad spot that should have been an easy first down for them. That didn’t help. But you have to know the clock situation and where the ball must go. One pass didn’t work, and it was risky to try another with five seconds. With the Chiefs getting the ball to start the third quarter, I would have been fine with a field goal and 24-10 lead.

Reid listened to Mahomes, and I’m not sure why everyone didn’t know the throw had to be quick and into the end zone. It was in the flat to Hill, and he danced around for no gain and the half ended. That pass never should have been thrown.

That failure really seemed to put the Chiefs in a funk. They were stopped on their first five drives in the second half, something you practically never see happen to this offense. They got away from the run. They got away from throwing to Kelce and Hill. Mahomes was not forcing deep throws, but his passes were just off and going to the wrong guys. A couple big sacks on third down in the fourth quarter also happened.

This was a mess of a half where the Bengals just hung in there with their game plan, even when it seemed nonsensical. Cincinnati continuously ran the ball on first down, setting up countless second-and-9 situations, which usually led to a short completion and tough third down situation. It made no sense why they did not attack more after throwing for more than 400 yards last time. Why not some play-action shots on first down? Ja’Marr Chase was held to 54 yards, a big drop of 212 yards from his 266-yard effort in Week 17. But Tee Higgins had 103 yards this time, even if his 44-yard grab, tied for the longest gain in the game, resulted in no points after the Bengals went right back to being conservative.

But after getting a field goal to make it 21-13, the Bengals got the first turnover in nearly six quarters of action between these teams this season. Mahomes tried to set up a short throw and threw it to a defensive lineman, who tipped it to himself for an interception at the Kansas City 27. The Bengals used that short field to drive for a game-tying touchdown (to Chase) and two-point conversion to end the third quarter.

You could see the tide turned when Joe Burrow threw an interception at midfield early in the fourth quarter, but the Chiefs went three-and-out with Mahomes taking his second third-down sack in two minutes.

Why did it look like Mahomes was constantly running around in the second half to no avail? The Bengals changed things up and kept dropping eight defenders into coverage. According to Next Gen Stats, they did it a season-high 35% of the time, increasing it from 24% of passes in the first half to 45% in the second half. It was very effective.

Like with Tampa Bay in the Super Bowl, this will be all the rage as the new blueprint to stop the Chiefs going into 2022. They’ll just have to figure it out because they did not have the answers on Sunday.

While Mahomes was taking fourth-quarter sacks, Burrow was very close to throwing consecutive interceptions. On a simple throw away, he for some reason threw a pass right to a diving defender, who dropped the ball. He would have been in bounds for the pick, stopping Cincinnati’s go-ahead drive after two plays. But Burrow took that gift and made perhaps his best play of the game with a 7-yard scramble for a first down on third-and-6. Three plays later, he was just as good with an 11-yard run to convert a third-and-7. We usually don’t see Burrow avoid sacks like that, but he only went down once in this game and had multiple good scrambles.

Rookie kicker Evan McPherson continued his perfect postseason with a clutch 52-yard field goal to take a 24-21 lead with 6:04 left. CBS’ Tony Romo kept talking about Burrow never getting the ball back, and I thought he was insane. Does he not see how this offense has been playing this half? Does he not realize the Bengals have three clock stoppages left?

And yet, it worked out to where Romo could have been right. But playing cute with the clock actually ended up costing the Chiefs in the end. Mahomes calmed down and found open receivers to move into field goal range quickly, but the Chiefs really made things hard after the two-minute warning. Mahomes was scrambling for his life and going out of bounds to stop the clock multiple times for meager gains. It was getting ridiculous like this:

Remember when Mahomes ran for 497 yards before passing/getting sacked in the Super Bowl? It was the highest game in the last five seasons, only topping Mahomes’ 495 yards in the 40-32 loss to Vegas. I would love to see if he broke 500 yards in this game.

But the Chiefs still had a first-and-goal at the Cincinnati 5 with 1:30 left in a 24-21 game. I can understand wanting to try a run and force the Bengals to call their last timeout. I don’t understand how anyone could advocate for letting the Chiefs score. You only do that if they’re able to kick a game-winning field goal with no time left. This wasn’t that.

But this is something that pisses me off about today’s NFL. Why should the offense be penalized for doing its job and scoring a touchdown? “They left too much time” is such a bullshit cop-out to let a defense off the hook for not doing its job. Don’t give up a touchdown. I don’t care if they have 20 seconds or 120 seconds left, don’t give up a touchdown. Do your job. The offense just did.

This is why I would have preferred to see the ball in Mahomes’ hands instead of a run for 1 yard by Jerick McKinnon. I want to maximize my touchdown probability, especially in a 3-point game against an offense that is struggling to score touchdowns now.

But on second down, Mahomes again ran around too much before taking a 5-yard sack. Not good. The clock was down to 39 seconds, but the ball was now at the 9 on third down. This would take an amazing throw like Mahomes had to open the game with a touchdown to Hill, but you have to be careful about forcing it and getting a tipped pick. We’ve seen it so many times with the Chiefs this season, including in the red zone.

So, Mahomes had to be smart. He wasn’t. He took too long again, Sam Hubbard sacked him again, and this time there was a fumble that the Chiefs were lucky to recover, or the season would be over. What a near disaster, and yes, this would be a season-ending turnover that the QB got away with for those keeping count. It made the field goal 17 yards harder, but Harrison Butker did his job and nailed it from 44 yards to force overtime. Good on the kickers this week.

After the Chiefs won the coin toss, you had to think the football gods aren’t going to let them do this three times since Week 15. Based on what I saw in the second half, I knew this wasn’t going to end well.

But it went worse than expected. For starters, why is he throwing to Demarcus Robinson twice in overtime after Robinson had one target with zero catches all day? Robinson wasn’t looking for the second-down throw and it nearly ended up in a pick-six by Eli Apple. A Hasselbeck, if you will. But for some #BallDontLie, the third-and-10 throw was deep for Hill, the pass was in the right location for his hands, but the defender made a great play too on the ball, and it was tipped to Von Bell for an interception. The Bengals were already at their own 45 and the ending felt inevitable at that point.

It is fitting that this team’s season would end after a big blown lead and tipped interception. It’s what plagued them during the 3-4 start. The Bengals came back from 14 down three times in Week 17 too. It was going to catch up with them eventually. The Chiefs were simply too sloppy this season to deserve to go back to the Super Bowl.

Joe Mixon had some strong runs to put the Bengals in chip-shot range. McPherson wasn’t going to miss a 31-yard field goal. He didn’t, and the Bengals are off to their third Super Bowl with a 27-24 win, the biggest road win in franchise history. Zach Taylor has as many playoff wins this year as Mike Tomlin (two) and John Harbaugh (one) have combined since 2016. You might actually be able to pick him out of a lineup of generic white men now.

Everyone knows Burrow and Chase now after this breakout season, but it really has been clutch kicking and clutch defense with incredibly timely and pivotal takeaways that have keyed this run to the Super Bowl for the Bengals.

This is the third game in a row where the Bengals have intercepted a quarterback in the final minute of the fourth quarter or overtime in a close game. This is something that has only happened 20 times in the playoffs since 2001, and the Bengals have done it three weeks in a row to Derek Carr (fourth-down pick at the goal line), Ryan Tannehill (third-down pick at midfield in a tied game), and now Mahomes in overtime to set up a game-winning drive.

The only other defenses to have two such plays in the same postseason are the 2007 Giants (Tony Romo and Brett Favre in back-to-back weeks) and 2010 Packers (Michael Vick in Philadelphia and Caleb Hanie two games later in Chicago).

Not even Tom Brady, the LOAT, has ever willed his defense to do this three times in his lengthy playoff career. Sure, he’s benefitted twice, including the most crucial interception in NFL history by Malcolm Butler, but you’d be hard pressed to find a team with big picks like this three weeks in a row.

Now the Bengals get their third chance to win their first Super Bowl. Maybe it’s the first of numerous chances for Burrow and company. Maybe it’s the best chance they ever see. Maybe it’s the start of the NFL’s next dynasty, and it happened on Kansas City’s field where the next dynasty was supposed to be.

We won’t know those things for some years, but as I hammered on this offseason, chances like Super Bowl 55 cannot be taken for granted. When you lose a game like that 31-9 instead of repeating, you never know if you’ll ever get back to the Super Bowl.

Ask Dan Marino and Don Shula.

Ask Brett Favre and Mike Holmgren.

Ask Kurt Warner and the Rams.

Ask Drew Brees and Sean Payton in New Orleans.

Ask the Steelers/Ben Roethlisberger and Packers/Aaron Rodgers after Super Bowl 45, which was 11 years ago.

Ask Russell Wilson and Pete Carroll in Seattle.

That little grace period in the AFC where Tom Brady had to move on from New England, Big Ben’s clock stopped ticking in Pittsburgh, Andrew Luck retired, Deshaun Watson ruined his career, Josh Allen had to improve dramatically, and Burrow was just a rookie? That time is over. The AFC has caught up to the Chiefs, and this is before we find out how high the ceiling is for Mac Jones and Trevor Lawrence, if Justin Herbert can get a defense in Los Angeles, and if Rodgers or Wilson want to join the conference.

You could be thrilled that the team is always competitive and will have a chance every year with Mahomes, and there is nothing wrong with that. But any dynasty talk? Kill that noise now. Scoffing at the thought of only winning two or three titles like you’re Jim Irsay? Have you seen the last nine seasons for the Chiefs? Did you ever watch a Kansas City playoff game from 1970-2010? Be happy with the one ring and hopeful there’s ever a second. The NFL is a con when it comes to making sure great quarterbacks walk away with Super Bowl titles.

We just watched a coach in his 23rd season get tripped up by two of his career bugaboos: managing the clock and neglecting the run even against a three-man rush. He lost to a coach who ran the ball 17 times on first-and-10 and roped-a-dope his way to a win. Like many of us, Reid has fallen in love with his superstar quarterback and expects him to be Superman at all times. Except the NFL playoffs are kryptonite to teams relying on the quarterback this much.

After halftime, the Chiefs got Clark Kent. Maybe on Earth-Two, Frank Clark gets a strip-sack on the most sacked QB in the NFL. But in our reality, the clips of Mahomes taking those sacks and throwing that pick in overtime are going to be played more than the brilliant ending last week against Buffalo.

Kick the field goal before halftime. Take the boring throwaway instead of the ridiculous sack. Not every situation requires a hero. Burrow just won two road playoff games by being pretty boring. Christ, he really might be the new Brady. Kansas City’s defense was not playing poorly enough to justify so much hero ball. Mahomes will learn this eventually, but he better hope it doesn’t happen after kickstarting a Cincinnati dynasty by playing one of the worst halves of his career.

I’ll end with an unmodified Dickens quote, because this must be what it feels like to love the Chiefs and not have them love you back.

I loved her against reason, against promise, against peace, against hope, against happiness, against all discouragement that could be.

49ers at Rams: Gut-Check Win for Stafford, McVay

Losing six games in a row to one rival is a big deal, but there is no better way to avenge it than with a playoff win that puts you in the Super Bowl. We had not really seen anything like it since the 2001-04 Colts lost all six games to the Patriots to kick off a rivalry between Peyton Manning and Tom Brady. The Colts finally won a game in 2005, followed it up with another road win in 2006, but didn’t truly slay the dragon until they came back from a 21-3 deficit in the 2006 AFC Championship Game and went on to win the Super Bowl.

49ers-Rams is less of a big deal than that, and the Rams have folded time after time to the 49ers in a variety of ways. But no matchup was bigger than this one, and the Rams did not have Matthew Stafford, Odell Beckham, and Von Miller for all six of those losses. Head coaches Sean McVay and Kyle Shanahan come from similar backgrounds with time spent in Tampa Bay with Jon Gruden and time together in Washington under Kyle’s famous dad. This game was to decide which one would be making their second Super Bowl appearance in the last four seasons.

The Rams had a clear advantage at quarterback with Matthew Stafford, but that did not pay enough dividends in the first two upsets by the 49ers this year. On Sunday, it looked bleak through three quarters with the 49ers leading 17-7 and the Rams having one of those classic “finesse team getting bullied by the physical team in the playoffs” type of performances. Jimmy Garoppolo even threw for 200 yards before the fourth quarter of a playoff game for the first time in his career. Little was going right for the Rams, which is why the comeback was such a gut-check and hallmark victory for McVay and Stafford.

It was ugly early. Stafford threw a red-zone pick on a tipped ball on a third down where the 49ers actually covered Cooper Kupp tightly like they should have been doing as much as possible. Make the other players beat you, and the Rams lost tight end Tyler Higbee to injury early in this one. Kupp was a monster on third down the rest of the game, catching 11-of-14 targets for 142 yards and two touchdowns (both on third down). If the MVP award included the playoffs, Kupp would run away with it this season.

Deebo Samuel also had a hell of a year and showed again his incredible strength on a 44-yard touchdown on a screen that was all him. Ben Skowronek dropped a 38-yard touchdown on his only target of the game. Following that, Matt Gay missed a 54-yard field goal for the Rams before the 49ers made their kick to take a 10-7 lead into the locker room, a half that certainly favors San Francisco’s style of play.

If you know me well, you know I’m not a big fan of the “genius” label that gets attached to McVay and Shanahan. I think both are good coaches, but they are far from flawless, and their game management leaves a lot to be desired. This second half was a perfect example of their shortcomings, and they should be glad they were coaching against each other. Someone had to win.

First, the Rams tried a pass on a third-and-1 at the San Francisco 43 in the middle of the third quarter. If you know you’re going for it, as you should there, just run the ball. Run it twice if you have to. Instead, Stafford threw a pass away after not liking what he saw, and the Rams tried to sneak him on fourth down. His sneaks, even when they worked, have looked awful this postseason. He also seemed to be banged up during this game. Sure enough, he was short again and it wasn’t even that close on replay. But McVay wasted a challenge and precious timeout on the play.

The 49ers seemed to deliver a huge blow with a 58-yard touchdown drive to take a 17-7 lead. Jauan Jennings fought for extra yards on a key third-and-10 to convert it. I guess everyone in San Francisco is just amazing with YAC.

Skowronek drop aside, Garoppolo was pretty much outplaying Stafford, or at least playing up to his level in the game. Stafford was going to have to have the biggest fourth-quarter comeback of his career against a good opponent. Remember, Stafford was just 4-35 (.103) at game-winning drive opportunities against teams with a winning record.

Stafford was 0-28 in his career when trailing by double-digits to start the fourth quarter against teams with winning records. That included an 0-4 record this season with the Rams. But the Rams were already at the San Francisco 20 to start the fourth quarter after a great play call to the backup tight end popped for 20 yards. McVay had to burn his second timeout with 20 seconds left in the quarter to call it on first down, but the play was a great one.

On a third-and-1, Stafford was in empty and threw an 11-yard touchdown to Kupp with 13:30 left. Again, how do you not double team the best receiver on the field? Odell Beckham had a very good 100-yard game, but I’d sooner take my chances with him beating me than leaving the most dominant receiver in the game in single coverage.

The 49ers could have stopped the bleeding, but once again, they failed to score any points with the lead under Shanahan. I’d be very worried that he is just never going to understand when to go aggressive vs. conservative. If you’re leading by 16 points in the fourth quarter, you can be conservative. If you’re only up three points and you’re the underdog, you need to take some chances. He has failed both situations in his career.

The 49ers may have botched their season when they faced a third-and-2 at the LA 45 and called a run for fullback Kyle Juszczyk with big, injured tackle Trent Williams in motion. It’s a cutesy play that did not work. McVay even thought the 49ers fumbled the ball, so he wasted his third challenge and was out of timeouts with 10 minutes to go. But the real sin here was giving the ball to maybe your sixth-best ball carrier in this offense? No disrespect to Juszczyk. He’s one of the finest in a dying breed of a position, but I’m giving the ball to Deebo or George Kittle or Brandon Aiyuk or Elijah Mitchell or maybe Jennings again.

The vaunted rushing attack for Shanahan’s offense? It produced 19 carries for 46 yards without a run longer than 9 yards. It looks like the Rams learned from the regular season and made an adjustment.

Still, the 49ers could have overcome the bad play with a fourth-and-2 conversion. But from early in the play clock, it was evident that they were just trying to draw the Rams offsides and never intended to snap the ball before taking a delay of game and punting. What a shame. The 49ers had as many delay of game penalties in the fourth quarter (two) as they had in the entire 2021 regular season, which is something they also did in the Dallas wild card win.

By the way, if there are two areas where the NFL should make use of modern technology and improve the game, it would be a light/sound system for delay of game and better spotting of the ball. It’s absurd how many times teams are getting away with snapping the ball after the clock hits zero, and the spots are sometimes so bad you wonder if the game is being fixed. If this led to more delay of game penalties, then so be it. It shouldn’t take 40 seconds to get a play ready.

Anyways, that punt was cowardly. Stafford must have let some of the LOAT rub off on him last week after nearly starting the next drive with a terrible interception, but Jaquiski Tartt dropped the deep ball pick with 9:47 left. Not a game ender, but it mattered. Stafford found Beckham for 29 yards on the next play, the Rams’ longest play of the night, and the drive ended with a game-tying field goal with 6:49 left.

Stafford was under siege by the 49ers in Week 18. Things didn’t feel that bad in this game, but apparently, they were. Next Gen Stats had it as his highest-pressure rate in a game for Stafford this season.

But this was a great chance for the 49ers to take advantage of McVay’s terrible clock management and drive into game-winning field goal range with no time left. But it was a brutal three-and-out with Garoppolo throwing three incompletions and the 49ers struggling to even beat the play clock multiple times. Stafford found Kupp for another big 25-yard gain on a third down, and only a sack at the two-minute warning stalled the drive to a field goal attempt. Gay was good from 30 yards out with 1:46 left.

Garoppolo certainly overcame longer odds in Week 18, needing a touchdown in similar time. Just a field goal would be fine here, but my did we get the worst of him in this offense with the season on the line. After a wild throw and a checkdown lost 3 yards, it was quickly third-and-13. With Aaron Donald in chase, Garoppolo tried to avoid a sack and just threw a pass up that was eventually tipped to the Rams for a game-ending interception with 1:09 left. Just nine more seconds and it’d be on the list I posted above.

Incredibly, or maybe sadly, this is still in the running for Garoppolo’s best playoff start out of his six. You could say his two best games were the two he lost. But after the way this one ended, it will begin the Trey Lance era in San Francisco. The 49ers invested way too much in him to not go that route next season. Garoppolo will have to catch on somewhere else as this should end the five-season run for him and Shanahan together in San Francisco. There will be more pressure on Shanahan to get things right with Lance, since he’s been given a pass for Garoppolo’s durability and limitations. If the 49ers are still blowing winnable big games with Lance, then we know the problem all along starts at the coach.

Now McVay is the one who looks to cap off this five-year journey with the Rams with a Super Bowl win as a favorite against the Bengals. He would join an impressive list of coaches who also took that five-year journey to their first ring: Mike Holmgren (1992-96 Packers), Tony Dungy (2002-06 Colts), Mike McCarthy (2006-10 Packers), and John Harbaugh (2008-12 Ravens). Holmgren is the only one on that list who won it with his best team, and while the Rams had better stats and record in 2018, this team is in better position to win in two weeks than that team was.

Sometimes that’s what matters most. Just keep making the playoffs and hope things fall into place for three or four weeks. The Rams took an aggressive approach to build this team and they are where they wanted to be. The quarterback who was 8-68 against teams with winning records can notch a seventh such win this season in two weeks. Maybe even make himself a case for a gold jacket one day as he can join John Elway as the only quarterbacks to win their first championship more than a dozen seasons into their careers.

This is what the Lions drafted Stafford to do. This is what we’ve been told McVay can do for a team. Now together, McVay and Stafford can finish this thing off in their home stadium in Year 1.

Next two weeks: Well, go figure. We get what I said days ago was the least attractive option of the four.

Watching the 49ers play on Sunday, maybe it’s the second or third-best outcome after all. All I know is the Rams better score more than three points this time. The Bengals better figure out how to get in the end zone more often. A third dud Super Bowl in four years would be a letdown.

NFL Stat Oddity: Super Bowl LV

~ Scott ~ 7 Comments

Defense wins championships. Football games are decided in the trenches. Overhyped quarterback matchups tend to disappoint.

The first two were reinforced by Super Bowl LV, and while that last one isn’t part of NFL lore, it should be after a 13-game postseason peaked right at the beginning with Philip Rivers (Colts) and Josh Allen (Bills) providing us the best-played game at the quarterback position. When Patrick Mahomes vs. Tom Brady turns out worse than Taylor Heinicke vs. Tom Brady, you know you are watching one defense rise to the occasion and do something special.

On Sunday night, the Tampa Bay Buccaneers dominated the lines of the Kansas City Chiefs in one of the most decisive Super Bowls in the salary cap era. The 31-9 final is easily the worst loss of Patrick Mahomes’ NFL career and the worst stat line and performance in 54 games. It is his only game without an offensive touchdown as the Chiefs could do no better than three field goals on 10 possessions.

Tom Brady threw for 201 yards, three touchdowns, and was named Super Bowl MVP, because of course he was. It would be too difficult to split it among the 11 defensive starters in a game where turnovers were not the decisive story for a change. This was a masterclass in coaching by Bruce Arians and his staff, an eyesore for Andy Reid and his, and the image that I think sums this game up best would be this one of Mahomes trying to make a throw on fourth down to no avail.

It was that kind of night. Maybe the most concerning part is that last year in the Super Bowl was almost the same night for the Chiefs, who will enter the 2021 season with a “prove it in the Super Bowl” demand from their harshest critics as the latest attempt at reaching a new dynasty hit a serious road bump in Tampa.

Story of the Game: Pressure vs. No Pressure

A year ago in Super Bowl LIV, it was looking like a great defense (49ers) was about to shut down another prolific offense. Patrick Mahomes was having the worst game of his NFL career halfway through the fourth quarter as the Chiefs trailed 20-10. Then “Wasp” happened on 3rd-and-15 and the rest is history.

There was no Wasp this time. Just the Chiefs repeatedly getting stung by the pass rush and coverage of the Tampa Bay defense, which was outstanding. Meanwhile, the Buccaneers found offense come easy after a slow start. Tampa Bay completely took the game over in a six-drive stretch where it scored four touchdowns, one field goal, and got stopped at the 1-yard line on fourth down on the only non-scoring drive.

It comes down to pressure. When Brady’s Patriots beat Mahomes’ Chiefs in the 2018 AFC Championship Game, I noted the large pressure difference in that game. Mahomes was pressured almost 45% of the time while Brady was just under 11% according to ESPN Stats & Info. I wish I had an awesome database of pressure differences for every game in recent years, but that doesn’t appear to be in my collection. I just know something in the neighborhood of 34% is huge.

Well, this time it was worse. According to ESPN Stats & Info again, Mahomes was pressured on 29-of-56 dropbacks (51.8%), the worst in Super Bowl history. Meanwhile, the Chiefs only got to Brady on 4-of-30 plays (13.3%), his lowest rate in 10 Super Bowls. We are talking a difference of 38.5% in pressure percentage points. That is massive.

We joke about Brady “willing his defense” to do this stuff, but look at these results. Mahomes has four games in his career where he was held to six or fewer points at halftime and two of them are his playoff losses to Brady. What a two-way legend.

Obviously, the Eric Fisher injury and offensive line issue was a major concern going into this game for the Chiefs. I called it the wild card to the matchup, but I thought if any offense was able to make it a footnote instead of the main story, it’s these Chiefs and Mahomes.

I was wrong, the line did become the main story, but it’s still only half of it. Eric Fisher himself isn’t going to cut off 20+ pressures. Maybe not even getting right tackle Mitchell Schwartz back could have prevented this. Sure, we probably need a new rule that Mike Remmers should never be allowed to start at tackle in the playoffs again, but the Chiefs’ other problem was the defense had no answers for making things hard on Tampa Bay.

The pressure disparity was mind blowing to watch. I said during the game that Brady was feasting on screens, play-action, and DPI, but little did I know how right I was until after the game.

Brady started 0-for-4 in success rate in this game. He then went on to have 15 successful dropbacks the rest of the game, including his first touchdown drive in the first quarter of a Super Bowl. Thirteen of those 15 plays involved play-action, screens/pick plays, or checkdowns over the middle to the running back. The only two plays that didn’t fit that was a quick out to Gronk on third down in the second quarter for 5 yards and the 1-yard touchdown pass to Antonio Brown on the same drive, a good throw into not the smallest window you’ll ever see.

There was no pressure on any of these plays as Brady had time and great windows to deliver easy throws for all of his yards. And yeah, this doesn’t even get into the penalties we’ll get into later. I’m not saying Blaine Gabbert wins this game 31-9 for the Buccaneers, but I don’t see a throw he couldn’t make here.

Throw in a more than solid rushing attack and the Buccaneers just got whatever they wanted for a six-drive stretch in this game. Meanwhile, the Chiefs were in trouble from the first series of the game. On their second snap, Mahomes narrowly avoided a sack by getting rid of the ball for an incompletion. On the first third down, he scrambled for a first down. Kansas City would only go 2-of-12 on third down the rest of the night.

It felt like the Chiefs were worried about the protection, wanted to use quick passes on early downs, but it just did not work and set the offense back in the down-and-distance.

  • Even the first pass of the game was a quick one to Byron Pringle, who was fortunate to get 3 yards on forward progress after the fast defense knocked him back.
  • Another quick first-quarter throw to Mecole Hardman, who did not look for the ball, was so off with the timing because of the edge pressure that it could have been a pick-six if the throw were worse.
  • After the first Gronkowski touchdown, Mahomes tried a quick throw to the back and Jason Pierre-Paul batted it down with ease.
  • Same drive, but the first play of the second quarter was a big 3rd-and-4. The Chiefs tried to set up a RB screen, but the pressure again got there too well and the pass was off for an incompletion.
  • After the Chiefs got a 14-yard gain to Hill from their own 1, Mahomes tried a slow-developing pass in the backfield to Hardman that he couldn’t handle, but it would have lost yards anyways.
  • At the two-minute warning, Mahomes checked down to Hill in the backfield for a loss of a yard as the receiver ran out of bounds and stopped the clock, another fatal mistake.
  • On the first drive of the third quarter, Mahomes was low on a quick pass to Hardman, who made the catch and then slipped for no gain. That set up 3rd-and-7, pressure forced another tough throw the Chiefs couldn’t complete, and they settled for a field goal. Six plays later they were down 28-9 halfway through the third quarter, completely changing the game and putting everything in miracle/hero territory.

I just highlighted seven early-down quick throws that failed to do anything for the Chiefs before it got to 28-9. This game got away from them quickly, trailing 28-9 after having the ball six times. The Chiefs also didn’t seem interested in giving the tackles any help in this one, according to Next Gen Stats.

Tyreek Hill finished with 73 yards, a decline of 196 yards from Week 12, and even those 73 yards were mostly gathered with the game out of reach.

So what did Bowles do differently? For any game of his over the last five years, he blitzed the least (9.6% of snaps) and played two-high safety (87% of snaps) the most to take away the big plays.

Frankly, this is some of the coolest stat shit I’ve ever read. A true tendency breaker in the biggest game of his career, and it worked to great success. More coaches need to do this instead of the usual “we do what we do” crap that passes as coaching in this league. You have two weeks to prepare, it’s a great opponent, do something different to attack their specific strengths and weaknesses.

However, I feel the Chiefs gave in to this approach with the quick throws I mentioned before. They were so worried about the protection for obvious reasons, but if you look at this game before it got out of reach, their best shots at making plays came when Mahomes let the ball rip.

On the opening drive’s 3rd-and-8, he had Hardman open deep, but the young, mistake prone receiver seemed more occupied with staring at the ball instead of going for it. On the second drive, Mahomes did a great job under pressure to get off a pass on 3rd-and-11, but it hit Hill in the face instead of a potential touchdown or at least first down. On the fourth drive, Mahomes again made a great play under pressure, but Kelce had a bad drop on 3rd-and-8 that would have extended the drive. Maybe they still punt, but it likely would have helped the field position that ended up being awful after a penalty wiped out a punt and the punter continued his lousy night with a shank. Tampa Bay started at the Kansas City 38 and scored a touchdown to go up 14-3. Then of course there was the play on fourth down that I led this recap with where Mahomes got that pass off in mid-flight, but that too hit Williams in the face instead of him coming down with the touchdown catch to give this game a little life early in the fourth quarter. It was the last real gasp and Mahomes’ dejected face at the end of that play said it all.

https://twitter.com/benbbaldwin/status/1358604116285603840

I say the Chiefs are their own worst enemy, and that may not have been true on this night. Tampa Bay’s defense was tough, but there were still plays to be had by the Chiefs that they failed to make. This is why I cannot buy the notion that Mahomes “choked” in this Super Bowl. Where are the drives that he specifically screwed up or the open throws he missed or big opportunities he didn’t take advantage of? He didn’t bring his A game, probably not his B game either, but he had three drive-killing drops on plays where he made incredible efforts to even give his guys a shot at making a play. We are used to seeing this offense make highlight-worthy plays, but they couldn’t buy one in this game.

Left: Mahomes with the throw. Right: the receivers without the catch.

There were also 11 plays where Mahomes avoided a sack that a lot of quarterbacks wouldn’t. These were still successful plays for the Tampa Bay defense, but all I’m saying is the three sacks don’t begin to tell the story with how much pressure Mahomes was under in this game.

ESPN’s Seth Walder shared from Next Gen Stats what may be my favorite stat from the whole game: Patrick Mahomes ran a total of 497 yards before his passes/sacks in this game, the highest total in any game in the last five seasons. He broke his own record as he ran 495 yards against the Raiders this year, his only other loss in the previous 26 games, another game where his pressure rate was significantly high against a non-blitzing defense.

Walder also said that the third-highest game was Mahomes against the Saints (441 yards), another game where the offensive line took a beating. Josh Allen had the fourth-highest game at 403 yards in the AFC Championship Game. So perhaps we have the blueprint to beat Mahomes: make him run a full Fran Tarkenton scramble drill clinic and hope his receivers don’t make any plays on those throws. I mean, it worked this night to perfection.

The degree of difficulty in this game for each quarterback could not be any different. That’s why the Buccaneers are champions, and the Chiefs did not repeat. Give credit to the coaches of Tampa for exploiting the weaknesses in the Chiefs and taking advantage of the Fisher injury. However, there was another factor at play here that I warned about.

The Refs: Welcome to My Shit List, Carl Cheffers

Walt Coleman, Ron Winter, Bill Vinovich. Let’s add Carl Cheffers to my shit list of worst refs because he just had to make his crew a big first-half headline in this game. The worst thing a ref could do in a Super Bowl is become part of the story, but this crew did that, and I warned in one of my previews that this could happen with the way Tampa Bay draws defensive pass interference (DPI) flags at historic rates and Cheffers loves to call that on the road team (or any team) at crazy rates this year.

Obviously, the Chiefs had a brutal penalty night, racking up 11 calls for 120 yards. Tampa Bay had six first downs via penalty, something only four other teams have had in the playoffs since 1999. Only the 2002 Titans (against Oakland) had seven first downs via penalty. No team in the Super Bowl since 1999 had more than four first downs via penalty until Tampa Bay. Most of the damage came in the first half for Kansas City.

There was a lot of undisciplined football by the Chiefs. Chris Jones had a stupid retaliation penalty that wiped out a 3rd-and-7 and gave Tampa an automatic first down. Hardman was offsides on a 40-yard field goal on 4th-and-5, which led to a new set of downs and a touchdown, a 4-point penalty. There was also that holding on a punt with a good tackle that led to a re-kick, which gave Tampa great field position at the KC 38.

You can live with that stuff. It is what it is. But the way these officials catered to the Tampa Bay receivers in the second quarter, especially Mike Evans, really does make you question if these games are on the level. First, there was the “defensive holding” call to negate a Chiefs interception on a drive that ended in a Tampa Bay touchdown to take a 14-3 lead.

Are you kidding me with this? Where’s the jersey grab? Where’s the penalty on Evans for pushing off to try creating separation? Green Bay’s receivers were visibly held two weeks ago and couldn’t buy these calls at home. Yet they call this to negate a pick.

Then you get into the last minute of the second quarter. Brady does one of his classic chuck-and-duck plays, just throwing one up for Evans, who sells some incidental contact by falling down on a bad ball and it gets a 34-yard flag for DPI, the longest “play” from scrimmage on the night. That call was bullshit as well. Two plays later, Brady sails a pass for Evans into the first row because he knows it wasn’t there and he didn’t have time to waste. There was a little contact in the end zone, but the pass was so clearly uncatchable. Defensive pass interference, put the ball at the 1-yard line. How do you completely ignore the uncatchable part here? That pass had a better chance of being caught by a cardboard cutout than a human being.

People who say 5 yards for illegal contact are wrong too. By the time the ball is released, there is no relevant contact that you don’t see on every play. It’s either PI or nothing. The fact that Tyrann Mathieu was also called for taunting after this drive despite Brady doing the same things to him is also telling of how biased the refs were in this half.

One of the network ex-officials also saw a disparity in how this half was called compared to normal games.

https://twitter.com/SNFRules/status/1358587524260761603

Maybe the Chiefs still bomb in the second half of a closer game, but those two touchdown drives in the second quarter looked tainted to me, and it’s worse because I was predicting this would happen in Tampa Bay’s favor with this referee.

So Cheffers will be on my shit list going forward. People think it’s funny when Brady tries to high-five an official like he did in the Saints game this postseason, but I think he does it because he really does expect them to have his back in these games.

This time they did.

The 10th Mahomes Loss: Where Does It Stack Up?

I have been posting charts about every Mahomes game, and here are the 10 losses updated for this game.

Where does Tampa Bay stack up? Obviously the > 28-points threshold was reached, and it probably didn’t have to be, but that’s always important. The Buccaneers did not dominate time of possession, but they still won it. They sure didn’t mind the Chiefs taking up over eight minutes on the two drives that ended with a turnover on downs, or the five-minute field goal drive late in the second quarter. The Buccaneers did not push the ball much offensively after going up 31-9, so they only finished with 340 yards, the second fewest in a win over the Chiefs.

The Chiefs obviously had one of their worst penalty games (11 for 120 yards) in the Mahomes era, and that was big in this one as I just went over.

The running game was helpful for the Buccaneers with Leonard Fournette (89 yards) and Ronald Jones (61 yards) combining for 150 yards and a touchdown. It may have even been two touchdowns if the Bucs used Fournette instead of Jones at the 1-yard line in the second quarter on the only great stop of the game for the Kansas City defense. The Chiefs weren’t horrible at running the ball as Clyde Edwards-Helaire was one of the few good players on the night, finishing with 64 yards on nine carries. It just wasn’t a favorable game script to run a lot, or maybe one could argue the Chiefs should have tried some more runs early to give the tackles a break in the pass protection area.

All I know is it’s not the game to laugh at them for taking a running back in the first round, but CEH was not the downfall here. If anything, the backs should have been more involved with chipping and protecting since they weren’t good at catching. Darrel Williams only came down with two catches for 10 yards on seven targets and Le’Veon Bell didn’t even play. Fournette pitched in four helpful catches for 46 yards, so there’s really no comparison in the production the Buccaneers got from their backs versus the Chiefs.

While the Chiefs had two turnovers (Mahomes picks), this was oddly a Super Bowl not determined by those plays. They didn’t come until midway through the third quarter with the Chiefs already in the unenviable position of trailing 28-9. Not to mention the first was a tipped deep ball thrown on 3rd-and-13.

The biggest shock is that the fourth quarter was just never close, the first time Mahomes has never been within one score in the fourth quarter in his career. The score was 31-9 at the 2:46 mark of the third quarter and it never changed again.

Worst Postseason, But I’ll Eat Crow on the COVID Season

The 2020 NFL season is completed. All 269 games were played, only a few were a farce because of COVID, and the Super Bowl was finished on time. I never thought that would happen, but they pushed through and got it done, so I’ll eat some crow on that.

Of course, I don’t think the postseason could have gone any worse than it did from both an entertainment standpoint and my own personal rooting interests. This was terrible after a season in which a lot of teams had good seasons and it seemed like we would get interesting games in the playoffs. Remember all the double-digit comebacks every week?

We couldn’t even get a single fourth-quarter lead change, the first time that’s happened since the 2005 season. At least that postseason gave us Steelers-Colts in the divisional round, which was one of the most dramatic fourth quarters in NFL history from the Colts’ comeback attempt to Jerome Bettis’ fumble, Nick Harper’s return and tackle by Ben Roethlisberger, and Mike Vanderjagt shanking the kick for overtime. I know people hate Super Bowl XL, but at least it was a better game than tonight. So I’ll take the 2005 postseason any day over this one.

The longest drought without a repeat champion in NFL history continues. If Tampa Bay ends it next year, I may have to start focusing more attention on the NBA or learn hockey analytics, because it’s hard for me to want to invest so much time in a league where one ancient quarterback continues to see his defense hold prolific offenses out of the end zone. Two of the last three Super Bowls have been downright awful representations of the product after regular seasons that were legitimately good.

In a league that is dying for new blood and new powers to emerge in a transition period, we’re left with a 43-year-old quarterback who probably is pumped full of blood from random men half his age.

I will say this, Brady did a hell of a job at picking his new team. He stayed out of the AFC, making it easier to get back to the Super Bowl since the NFC loves those flash in the pan teams where everything just clicks one year. If he goes to someone like Indy or Miami or the cursed Chargers, he’s likely getting put down early by the Ravens or Bills or Chiefs. Instead, he goes to the NFC where his main competition becomes the Saints and Packers. Guess who stops those teams short of the Super Bowl in the NFC? EVERYBODY THE LAST DECADE. Well, minus Dallas. So he gets to the final four with statistically the best defense left and a loaded receiving corps that even got to add Gronk and AB. You think the Colts are bringing in Gronk and AB? I doubt it. They scored the first three touchdowns in the Super Bowl too. So I do have to give him credit for picking the best team possible to make this happen.

Defense wins championships. Football games are decided in the trenches. Tom Brady’s luck is the greatest of all time. If he doesn’t have to change his game, then neither do I. But I will start doing video work this offseason in addition to being more active as a writer.

If you think a Super Bowl blowout is going to make me hibernate for seven months, then you don’t know me very well — not that that’s ever stopped randoms on the internet from trying. I’m over 11 months into my diet and feeling good about hitting important milestones this year. I’ll definitely write about that if it comes to pass as it would mean a lot to me if I could help even just one person out there. I look forward to getting a COVID vaccine and being able to see people I care about in person. This last year has been tough, and while a Chiefs win would have made this a more enjoyable offseason and put the league on a better timeline for the future, the fact is it’s just a football game. The outcome doesn’t change a thing that I planned to do tomorrow, this week, or the next.

When I started this blog in 2012, the very first post was titled “You Are Now About to Witness the Strength of Street Knowledge.” I’ll end the 2020 NFL season with another N.W.A. reference just for the haters out there:

You don’t like how I’m livin’? Well, fuck you!

Until next time…

Previous weeks in Stat Oddity:

NFL 2020 Divisional Round: Browns at Chiefs

~ Scott ~ 2 Comments

The Chiefs begin their run to end the longest drought in NFL history without a repeat champion. After a historic streak of close wins and the dreaded “playoff rest in Week 17 followed by a bye” combo, should the Chiefs be on upset alert against a hungry Cleveland team?

For previews of Saturday’s games, click here.

Browns at Chiefs (-10)

The last time we saw Patrick Mahomes, he was just getting by the Falcons in an uncharacteristic 17-14 victory. That was three weeks ago from this Sunday. The Chiefs have since rested starters in a 38-21 blowout against the Chargers to end their record 60-game streak of not losing by more than eight points, and then had a bye week.

Meanwhile, the last time we saw the Browns, they were embarrassing the Steelers with a 28-0 start in the first quarter before winning their first playoff game since the 1994 season. This week their head coach, Kevin Stefanski, is back from COVID-19 and so is Denzel Ward, their best corner.

Doesn’t this 10-point spread feel a bit off considering the Chiefs just set an NFL record with seven straight wins by fewer than seven points? No other team has ever had more than five straight. The Chiefs have not beaten anyone by more than six points since the lowly Jets in Week 8, which was before the election if you need help with how long ago that was. Cleveland’s only losses by more than 10 this year were early-season blowouts in Baltimore (38-6) and Pittsburgh (38-7), but clearly the Browns closed the gap on those teams later in the year.

Look, I get it.

The Chiefs’ spread is -10 and double-digit favorites in the playoffs are 60-13 SU (.822) and 43-29-1 ATS (.596) in the Super Bowl era. They are 50-7 (.877) at home. The Browns were outscored 37-20 in the final three quarters in Pittsburgh and took advantage of a total gift on the opening botched snap for a touchdown and got two more tipped ball interceptions.

Baker Mayfield probably isn’t going to have another game where he isn’t even pressured once, though that offensive line is very good.

With Tennessee eliminated, the Browns have the worst remaining defense in the playoffs, ranked 23rd in points per drive allowed and have already allowed 34+ points seven times (six on the road).

Oh yeah, Mahomes is 23-1 in his last 24 starts, Andy Reid is 25-5 after a bye week, and the Chiefs have yet to score fewer than 31 points in the playoffs with Mahomes at quarterback. They also set an NFL record this year by beating five teams with a winning record on the road.

By now, you just expect the Chiefs to find a way to outscore the opponent and come away with the win. They won so many tight games this year and it was usually thanks to the offense taking over in the final minutes with a one-score lead and either expanding to a two-score lead or running out the clock. The 2020 Chiefs may have had the best four-minute offense season in NFL history.

The Chiefs did not blow a fourth quarter lead this season, but the offense did so well in close games that the defense rarely had to defend a 4QC/GWD attempt. When the offense failed to close the game out against Carolina, the defense had to stop the Panthers from a game-winning field goal. Thankfully, Teddy Bridgewater was awful in those moments all year (0-9 record), and the Panthers used the 86 seconds they were given to only set up a 67-yard field goal that was missed.

That was the closest call for the Chiefs and the defense’s best effort to save a game. Mahomes left Derek Carr only 28 seconds in Las Vegas when he forced a game-ending interception. Mahomes left Denver’s Drew Lock only 64 seconds, needing a touchdown after the Chiefs added a field goal, when the defense intercepted him too. Matt Ryan drove the Falcons down the field for at least overtime, but Younghoe Koo missed a short field goal to end that one.

I feel that the Kansas City defense is most responsible for why this team has not pulled away with ease in any game in over two months. No matter how well the game begins, it just seems like every one of them comes down to Mahomes with the ball late and in a one-score game.

Throw in the potential for rust, the shaky offensive line of recent weeks, the running game not always reliable, and this defense not being tested enough, and I think it’s a potential recipe for disaster this postseason.

Then again, how could anyone start a Super Bowl run worse than the Chiefs last year when they fell behind 24-0 to the Texans in the AFC divisional round?

Once the Chiefs got past the self-inflicted wounds, they dominated Houston and won 51-31, a game that wasn’t even close in the fourth quarter.

I would be far more worried for the Chiefs if it were Baltimore instead of Cleveland. Mayfield will need to have an exceptional game. I pointed out the zero pressures the

Steelers got on Sunday, but they also had zero takeaways and the Browns had two 40-yard touchdown catches with at least 30 YAC on each. In the regular season, the Browns had one pass play, let alone any touchdowns, with 30+ YAC. Just one.

Unusual things can happen in this league, but the Browns have to come in prepared for this one like they were against the Steelers and their road win in Tennessee. It is going to take points for sure as the over/under is 57 points. In NFL playoff history in games with a total of at least 54 points, the over is 10-5 and the home team is 10-5 SU.

The 2020 Browns have already tied the NFL record for most games in a season (playoffs included) where both teams scored 30 points. The 2018 Chiefs are one of six teams on that list, but something in Cleveland’s favor is they are 5-1 in these games.

Maybe it will be 66-59 like a classic meeting in college between Mayfield and Mahomes, won by Baker’s Oklahoma team.

https://twitter.com/BakersDawgs/status/1349375811695075329

That game had 10 straight touchdown drives in the second half before Oklahoma finally got one more first down on the ground with Joe Mixon to end it and deny Mahomes one last chance with the ball.

Oddly enough, scoring a shitload of points and denying Mahomes the ball at the end has carried over to be the best way to beat him in the NFL too.

Mahomes is 42-9 as a starter in the NFL. He has led the Chiefs to at least 22 points in 49 of his 51 starts. Outside of that weird 19-13 loss to the Colts in 2019, he has only lost when the opponent has scored more than 28 points.

I compiled a couple of charts to show just how hard it is to beat Mahomes and the Chiefs and what type of benchmarks it usually takes to come out with the win.

Before I go into the details, this second chart shows the 24 games where teams scored at least 20 points on the Chiefs and still lost. You’ll notice a lot more red here to indicate that they didn’t achieve the benchmarks I’ve laid out.

Keep in mind we are making a series of comparisons between samples of nine games (Table 1) and 24 games (Table 2), but I cannot help the fact that Mahomes is only this far into his career and we already talk about him in such historical context. I also understand that lots of these things would be helpful in beating any team in the NFL, but it’s just more pronounced with the Chiefs in the Mahomes era.

I’ll go over each section of the charts and how the 2020 Browns fit into this.

Opp Rec (+PO)

You can see the opponent’s final record and the playoffs are included in parenthesis if they made it. Seven of Mahomes’ nine losses are to playoff teams. Only those pesky 2019 Colts had a losing record while the Raiders finished .500 this year thanks to choking away that Miami game. This isn’t really an indicator of anything, but just providing context to the games listed. This is common sense that it will usually take a playoff team to beat a team like the Chiefs.

Fortunately for Cleveland, the Browns are a 12-5 playoff team this year and not the 7-8-1 team they were in 2018 when they lost 37-21 to the Chiefs.

Opp Scored > 28?

Did the opponent score more than 28 points on the Chiefs? Clearly you must score at least 29 to get the job done. Derek Carr had the game of his career this year and put up 40 points in Mahomes’ only loss in the last 24 games. In Table 2, only seven of those 24 teams scored more than 28.

The Browns have scored at least 32 points in eight of 17 games this season, so they are more than capable.

Opp TOP > 35 MIN?

I usually don’t talk about time of possession much because it just ends up being a result of playing well on both sides of the ball rather than something you can strive for on purpose. However, keeping the ball away from a great quarterback should always be high on the priority list for a team.

The Chiefs actually lost time of possession in eight of the nine games in Table 1, but in terms of letting the team have the ball 35 minutes or more, that happened two-thirds of the time. It only happened three times in the other 24 games, all wins by the Chiefs. That difference can be made up at the end of the game when your offense is the one finishing things off instead of Mahomes.

The Browns finished fifth in TOP/drive this season, right behind the Chiefs. The Panthers were second and they gave the Chiefs fits as you can see in Table 2 in one of the closest games on that list that was nearly a loss.

KC 8+ PEN? and KC 60+ PEN YD?

The next two columns are looking at penalties on the Chiefs. There has never been convincing evidence that the number of penalties or penalty yardage has a significant correlation to team performance. Mostly you just want to avoid the real costly ones that take away touchdowns or extend drives for the opponent.

Kansas City is a perfect example of this as the two New England losses in 2018 were the only losses where they did not have at least eight penalties or 60 yards of penalties. However, what’s the most memorable penalty in Kansas City history? Dee Ford lining up offsides by a centimeter in the AFC Championship Game, wiping out a game-ending interception thrown by Tom Brady in the final minute. Bummer.

However, Chiefs fans this year know their penalties can be costly. In the Raiders loss, they had two touchdowns wiped out by holding and offensive pass interference. The wins over Tampa Bay and Denver were a lot closer late after bad penalties for the Chiefs into third-and-forever situations. The Chiefs could do a better job with penalties than they do.

In the 24 wins, the Chiefs only hit eight penalties 10 times and 60+ penalty yards nine times, so they were better in those games at keeping the flags down.

Opp Rush for > 170 yds?

I feel like this one was a little controversial when I was selling it before Super Bowl LIV, but the fact is you usually have to run the ball well on the Chiefs to beat them. Two-thirds of the losses again were when the opponent rushed for at least 170 yards, and the Rams in that 54-51 game were the only team that did it without rushing for at least 119 yards.

I know I raised the bar high there, but it was still hit six times in nine losses while in the 24 wins in Table 2, only seven teams crossed 170 yards. Mahomes needed a fourth-quarter comeback in three of those seven games.

For the teams that beat the Chiefs, it’s not like they were just piling up those rushing yards in the fourth quarter with the game out of reach. No game in the NFL has been out of reach for Mahomes yet. These teams used the run to help facilitate their scoring, sometimes they hit big runs (like the Titans win in 2019), and to keep Mahomes off the field.

Can a Cleveland team with five 190-yard rushing games this season run well on the Chiefs? I believe so. Nick Chubb is great, and we know Kareem Hunt is viewing this as a revenge game, even if he only has his damn self to blame for the Chiefs cutting him.

The Chiefs will need a big effort to contain Chubb and Hunt in this one. The good news is the Chiefs are 5-0 this season when they allow 150+ rushing yards, never allowing more than 20 points in those games. But they’re not playing the Broncos, Brian Hoyer, Justin Herbert in his first game, or the Ravens (Lamar struggles with KC) in this one.

The Chiefs rank 32nd in red zone touchdown rate allowed this year (76.6%). That is not encouraging against a Cleveland offense that was third (73.6%) in that category this year. That’s why I love Chubb and Hunt to both score touchdowns in my Same Game Parlays for this one.

The Browns won’t set any rushing records in this one, but a long Chubb run in the fourth quarter could be the difference in another Super Bowl ring and a one-and-done.

Opp Gained 450+ Yds?

Did the opponent gain at least 450 yards of offense? Again, just more common sense that you need a lot of points to beat the Chiefs, and that’s something that requires significant yards unless you have the Chicago Bears D/ST in one of their random playoff years.  

The Chiefs allowed 450+ yards in two-thirds of their losses. They did it in only four of the 24 wins listed.

The Browns were 3-1 this year when they hit 450 yards, only losing that 47-42 game to Baltimore.

KC TO?

How many turnovers did the Chiefs have? I often speak of the “obligatory Chiefs fumble” and you can see that was really born in 2019 when they lost a big fumble in those losses to the Colts, Texans, and Titans (returned for a touchdown in that one).

The Chiefs had a turnover in seven of their nine losses and multiple turnovers in four of the games. In the 24 wins, they only had four games with multiple turnovers and eight games without a turnover.

Half of Mahomes’ six interceptions this season came in Miami when he had two tipped balls and Xavien Howard made a one-handed catch. Maybe he got it out of his system that day. Week 16 against Atlanta was the only other time the Chiefs had multiple turnovers this year, though one of them was a horrible decision to call a trick play on fourth down that led to Sammy Watkins throwing the pick.

Like I said earlier, the Browns had some great fortune on three of their five takeaways against the Steelers after a season where they were mediocre at best at taking the ball away. Instead of getting a pick, Cleveland’s best bet may be Myles Garrett getting a strip sack this week. He is nursing a shoulder injury though, but that Chiefs offensive line has been shaky at best down the stretch.

Denied or Stopped PM Late?

These last two columns in the charts perhaps tell each game’s story the best. No matter how well the game started or what you did well, can you stop Mahomes late in the game? Can you flat out deny giving him the ball last or in the final minutes?

When the Chiefs have lost in Table 1, it’s usually more of a denial (the tan green cells) of Mahomes than a flat-out stop. Only the Rams in that 54-51 game stopped him cold by getting two picks late, and I use “cold” lightly as he did throw a go-ahead touchdown pass with 2:47 left.

The 2019 Texans and 2020 Raiders ran out the clock on him, denying him that final drive with the ball. The 2018 Patriots twice beat him on the final snap, scoring last after getting the coin flip and ball in overtime in the AFC Championship Game. Philip Rivers threw that game-winning two-point conversion with four seconds left in 2018, basically the last play there. The 2018 Seahawks and 2019 Colts extended to a two-score lead in the last 2:30. Mahomes answered with a score both times, but not enough time left and the onside kicks failed. Finally, the 2019 Titans left Mahomes only 17 seconds, but he still set up a 52-yard field goal that was blocked to end the game.

When I say Mahomes doesn’t lose, he just runs out of time, I have the facts on my side.

In the 24 wins, that’s when he has put teams away late if the game was still close (one score). One of the six games that wasn’t close was Cleveland in 2018. The Browns could do no better than a 13-point deficit a play into the fourth quarter, which Mahomes immediately answered with a field goal and a 37-21 final.

In the other 18 games, Mahomes led seven game-winning drives. Four times he extended the lead to two scores. Mahomes ran out the clock fully four times, and ran it down from over four minutes to just 23 seconds in Baltimore this year.

The only two teams to stop him were Denver (2019) and that Carolina game I’ve talked about already. He still threw two touchdowns in the fourth quarter against Carolina, but it was that late three-and-out that could have been costly if the Panthers were able to get a closer field goal attempt. Against Denver, Mahomes didn’t score in the quarter, but the Broncos’ offense was inept and by the time they got it last, only four seconds remained for a 4QC/GWD opportunity.

If you want to beat Mahomes, you can’t let him have the ball last. End things with your own four-minute offense. With Cleveland’s running game and Mayfield’s recent emphasis on running more, they could do that.

Conclusion

So there it is. To beat Mahomes and the Chiefs, you just have to score a lot of points, gain a lot of yards on the ground and overall, hope for some breaks in the turnovers and penalties departments, and even then you better deny him the ball at the end of the game.

Got all that, Cleveland? I hope it is an exciting shootout and not a rout, but I just do not see the Browns pulling it off unless the Chiefs have another very uncharacteristic performance.

If my final score looks familiar, it’s because I picked it on purpose.

Final: Chiefs 38, Browns 33

Close Encounters: Super Bowl LIV

~ Scott ~ 2 Comments

No matter if it was the NFL’s first season or its 100th, the stingy defense with the great pass rush takes down another prolific passer. The QB who walks into the building with 23 points is stuck on 10 in the biggest game of his career.

Because football…football never changes.

Record a Ron Perlman voice-over for that.

That Fallout reference was going to be my tweet tonight more than halfway through the fourth quarter of Super Bowl LIV. That was my gut feeling around the time when the 49ers led the Chiefs 20-10 and Kansas City faced a 3rd-and-15 at its own 35.

For the first time in 36 games, I actually doubted Patrick Mahomes.

SBLIV

Then with just one snap, everything changed and the Chiefs are Super Bowl champions and Mahomes even walked away with the MVP award. It was one of the more dramatic fourth-quarter finishes in Super Bowl history even if the game itself wasn’t an instant classic.

So here is my Super Bowl LIV recap, my first game recap in ~54 weeks in a new section I’m calling what I have long wanted to call these recaps: Close Encounters

Mahomes: From Worst Game to Best Comeback to Champ Forever

The best player in football is the reigning Super Bowl MVP. That feels great to say after what’s felt like many years where it hasn’t been the case, and I’m grateful we never have to bother with the question of “can Mahomes win the big one?”

However, this was not a walk in the park for Mahomes like the first two playoff games. In fact, until those final ~7 minutes, it looked like he was having the worst game of his career in the biggest game of his career. But if there’s anything I absolutely nailed in my 5,000-word preview for this game, it was the very last paragraph:

There are a lot of areas that favor the 49ers, and I think historically the 49ers are the type of team more likely to win this game than a team like the Chiefs. There are just more ways for the 49ers to win while practically every positive outcome for Kansas City involves Mahomes playing really well. Then again, Mahomes is 9-0 in his career when his passer rating is under 90.0 because he’s the best at doing what the coach who succeeded Reid and preceded Shanahan used to say: f***ing score points.

Final: Chiefs 31, 49ers 27 (MVP: Patrick Mahomes)

Yeah, just score some f***ing points by any means necessary, and Mahomes has done that better over 36 games than any quarterback ever has. You sack him four times and he still puts up 31, even if the final touchdown was a killshot from the ground attack. You keep his passer rating under 90.0 (it was 78.1 in this game) by getting a pair of picks and he’s still 10-0 in his career with the scoreboard looking full.

He doesn’t have a weakness, but let’s look at how things progressed tonight because Mahomes had to lead the most significant late-game comeback of his career to pull this one off.

Mahomes started the game with a couple erratic throws for a quick three-and-out before rebounding well enough. Nerves in a first Super Bowl make sense. The 15-play touchdown drive that took up half the first quarter was in line with some of the great drive engineering he’s done this postseason with short passes. Not taking advantage of Jimmy Garoppolo’s interception and settling for a field goal was disappointing, but the Chiefs led 10-3 early.

The first big mistake of the night, at least coaching wise, was with just over two minutes left in the half tied 10-10. The Chiefs should have played this better with the 49ers getting the ball to start the third quarter. They essentially ran a series of plays that negated Mahomes’ existence. They ran the ball for 2 yards to get to the two-minute warning, then tried a trick play with Mecole Hardman that was blown up in the backfield for a 6-yard loss. How many tricks like that do you need with Mahomes? On 3rd-and-14, the Chiefs just ran a screen that was not effective on the night and the team punted. That was a really bad ending to the half and that wasn’t Mahomes’ fault at all, but he also wasn’t wowing us either like usual, so the game went to the half tied at 10.

Then in the third quarter, Mahomes recovered a fumble forced by Nick Bosa to set up 3rd-and-12. Mahomes has fumbled six times in the playoffs (five games), but has been fortunate not to lose any of them. But on the very next snap, he threw a terrible pass that was intended for Tyreek Hill and intercepted for his first ever postseason giveaway. That led to a 20-10 San Francisco lead and suddenly Mahomes looked rattled by the pass rush, the deficit, and the magnitude of the situation. He wasn’t attacking deep, or improvising big plays, and the short passing game was pretty well bottled up.

I’ve mentioned in the preview how the Chiefs had so many third-down drops in this postseason to kill drives. I can’t call what Mahomes did early in the fourth quarter a drop since he was so off target again to Hill, but the pass was tipped for an interception while the Chiefs were driving at the San Francisco 23. After seeing Mahomes step up from a decent pocket and still come up short on a pass to Hill, I was really convinced this was going to be a big scar on his resume. The 49ers were quick to challenge and the replay system correctly took away the 16-yard completion that should have been an easy one for Mahomes.

And then the play of the game on 3rd-and-15 happened. What a time for Mahomes to complete his longest pass (57.1 air yards) of 2019:

Without that play you would have seen a punt and probably a San Francisco win. It’s only the second time since 1994 that a team converted on 3rd-and-14 or longer in the fourth quarter (last time: Tom Brady to Julian Edelman vs. 2014 Seahawks on 3rd-and-14). Mahomes had to take such a deep drop to fire that one deep and Hill was free enough to make the catch. Game on. Three plays later, I thought the defensive pass interference call on third down was a good one since the defender made contact without ever playing the ball. That put the ball at the 1 where Mahomes found Travis Kelce for an easy 1-yard touchdown with 6:13 left to make it 20-17.

I made this thread in November to show that Mahomes has been much better than his 3-7 record (now 4-7) at fourth-quarter comeback opportunities:

So with 5:10 left he had his chance and the Chiefs put the ball in his hands on seven straight plays. The deep throw for 38 yards to Sammy Watkins made it look like the Chiefs might score too quickly again, but it came down to a 3rd-and-goal at the 5 this time. Kelce cleared some room and Mahomes just had to throw a short toss to RB Damien Williams, who did enough to cross the plane for the go-ahead touchdown with 2:44 left. I’m not 100% sure he broke the plane with the ball before stepping out, but that was the ruling on the field and there wasn’t anything conclusive enough to say he didn’t score. The Chiefs led 24-20 and put it in the defense’s hands again to much success. Williams delivered the deathblow with a 38-yard touchdown run to give us a 31-20 final.

Mahomes was really the default MVP in this one. He finished as a passer with 26/42 for 286 yards, 2 TD, 2 INT. He rushed nine times for 29 yards and a touchdown, though he actually lost 15 yards on three kneeldowns when the Chiefs ran the clock late. So he was effective as a runner once again. I can understand people wanting Williams as MVP for the late touchdowns, though he didn’t really need to score the last one. He could have gone down after the first down at any point and the Chiefs would have ran the clock out and won 24-20. I swear I’m not just bringing this up because my #1 bet was Chiefs by exactly 4:

kc4

(My real bet was $20 to win $500, but this still hurts)

So it wasn’t the cleanest game for Mahomes, but he was money in crunch time. He led the team to 24 points on their first eight drives, or 3.0 Pts/Dr against the best defense in the NFC. That’s nothing to take lightly. Most quarterbacks would have imploded against that pass rush, but Mahomes stepped up on back-to-back touchdown drives.

But make no mistake about it — 3rd-and-15 changed everything in this one and that throw was vintage Mahomes, the first NFL player to ever win an MVP and Super Bowl MVP before he was 25 years old. Hats off to him for capping an incredible first two seasons.

The Chiefs Did What!?

Some stats are hard to believe, but this one takes the cake:

The Chiefs trailed by 10+ points in all three playoff games, but still won all three games by 11+ points.

If you know my work, you know I don’t like using the final score to judge the closeness of a game. Things are going to be especially misleading for this downright historic Kansas City playoff run. The Chiefs trailed 24-0 to Houston before winning 51-31 and never even trailing in the second half. The Chiefs trailed by 10 twice to Tennessee and won 35-24. The Chiefs trailed 20-10 in the fourth quarter before beating the 49ers 31-20.

It’s the first time a team has three double-digit comeback wins in the same postseason. Think about that for a second.

  • Winning three straight games after trailing by 10+ points would be a crazy NFL feat (the 2013 Patriots did this Weeks 12-14).
  • Winning three straight games by double digits AFTER trailing by double digits would be an insane feat.
  • Doing that as your Super Bowl run is inconceivable and I am using that word correctly.

The Chiefs are just the third team to win a Super Bowl after trailing by more than 14 points in the postseason, joining Peyton Manning’s 2006 Colts (18 points down vs. Patriots in AFC-CG) and Tom Brady’s 2016 Patriots (25 points down vs. Atlanta in SB LI). The Chiefs are now the fifth team to win a Super Bowl after trailing by double-digits in the fourth quarter during the playoffs:

The Chiefs are the second team in NFL playoff history to enter the fourth quarter down by double digits and win the game by double digits. The Eagles did it to New Orleans, 36-20, in 1992.

Kyle Shanahan and Jimmy G: The San Francisco Blame Game

When it comes to Super Bowl collapses and heartbreak, Kyle Shanahan and Dan Quinn probably know it better than anyone now. Shanahan and Quinn shared the 28-3 collapse in Atlanta, but Quinn also saw the 10-point lead disappear to the Patriots with the 2014 Seahawks. Now Shanahan sees a 10-point lead disappear to the Chiefs in this one, and this graphic is particularly hard to swallow:

I really don’t want to rehash 28-3 tonight, but let’s just say Shanahan didn’t finish the game as badly this time. If anything, he didn’t do enough in the first half and that hurt. A few too many screens and horizontal passes slowed down the 49ers, who were much better at using Deebo Samuel in motion and getting quick-hitting plays from the middle of the field instead of testing the Chiefs on the edges. In fact a couple of screens turned a promising opening drive into a field goal instead of a touchdown. Jimmy Garoppolo threw a bad pick under pressure early, but overall he wasn’t playing that poorly for Shanahan. The offense looked deadly in the second quarter after gaining a first down on five straight plays, including a touchdown to tie the game at 10.

But things fell apart a bit after the two-minute warning. I mentioned Reid’s shortcomings in that part of the game, but Shanahan did even worse with clock management. He had three timeouts but failed to use one to stop the clock after KC’s screen pass failed. So instead of saving about 100 seconds and two timeouts for Garoppolo, he saved three timeouts and 59 seconds. Then he remained conservative with two runs to set up a 3rd-and-5 with 20 seconds left. Garoppolo delivered a 20-yard completion, then seemed to follow it up with a great 42-yard bomb to George Kittle. However, that was wiped out for offensive pass interference. I thought it was a pretty soft call for a little hand fighting that is let go quite often in this league. That felt pretty cheap to me and cost the 49ers three points, but the bigger question is why the hell wouldn’t you try to save as much time as possible and shoot for a double score against Mahomes?

So that was bad for Shanahan, but he and Garoppolo came out strong from the half and took that 20-10 lead into the fourth quarter with 11:57 left. Look, you have to keep scoring when you play Mahomes. There weren’t any errors this time like calling a pass on 3rd-and-1 deep in your own end with a 16-point lead, or not just running the ball after a Julio Jones catch when you’re up 8. That didn’t happen here. The 49ers did call three pass plays on second down with a lead, but I can’t fault the calls there with the Chiefs obviously expecting the run. And let’s face it, the running game wasn’t that outstanding on the night as most of the best plays were unconventional tricks with Samuel.

Garoppolo also completed the first of those second-down passes, which proved to be the only first down the 49ers offense would get in the fourth with a lead. Pressure definitely had an impact on Garoppolo with not only the pick, but also a few batted balls. NextGenStats had Garoppolo as 0/7 passing with two picks while under pressure on the night. He was 20/24 otherwise for 219 yards. Ouch.

Garoppolo was off in the fourth quarter while the Chiefs were surging to that 24-20 lead. Still, you don’t mind the situation of having the ball with 2:39 left and 85 yards away from glory. In fact, it’s probably the situation quarterbacks dream about for years. Garoppolo has been pretty good at comebacks in limited opportunities, but he definitely will regret the 3rd-and-10 pass from the KC 49 with 1:40 left. Emmanuel Sanders got behind the defense, but Garoppolo overthrew him deep. On 4th-and-10, there wasn’t much of a chance and Garoppolo was dumped for a sack. Two plays later, Williams exploded for a touchdown and it was basically game over. Garoppolo’s second pick looks worse in the box score than anything else.

This game did not swing on many plays, so I really look at what each QB did on a third-and-long in the fourth quarter as being very decisive to this Super Bowl. Mahomes was able to deliver deep on his 3rd-and-15 to save the day, but Garoppolo was off the mark on his attempt despite an open receiver. So I really don’t want to jump on a “Shanahan can’t finish off a big one” or “Garoppolo will never win them a Super Bowl!” narrative when the margin is that small. Had the defense, the strength of the team for most of the year, did its job first on 3rd-and-15, we’re probably asking if Andy Reid will ever win a ring and wondering what the hell happened to Mahomes on the big stage.

Now an extra field goal on the board for the 49ers probably would have changed that drive, but again, that was a big blunder in the first half. I can’t crush Shanahan for how he called the game late, and I don’t think Garoppolo’s performance is one to crucify, but he just didn’t redeem himself in the way that Mahomes did.

The NFC has been a lot tougher to get back to this point too, so I’m not sure the 49ers are in an advantageous spot in 2020, especially given the strength of their division. Don’t discount the Cardinals getting really good in a year or two. We already know about Seattle and the Rams still have talent. So this is a tough blown opportunity for San Francisco.

Andy Reid: Hall of Famer… and Dynasty Starter?

Finally, we’ll end on a positive note as this win should wrap up a spot in Canton for Andy Reid. I’ve made my clock management jokes like everyone else, but he’s been arguably the best coach not named Bill Belichick this century. It wasn’t a perfect night for him, but good on the two fourth-down calls and now he has the ring to go along with the seventh-most wins and his winning percentage is over 61%. If we’re putting Bill Cowher in, then we’re absolutely putting Reid in, right?

In fact, Reid just shattered a Cowher record by winning his first Super Bowl in his 21st season, by far the longest wait a coach has had to earn his first championship. Cowher needed 14 years with the Steelers, which is still a record for one franchise, but Reid spent 14 years with the Eagles before winning in his seventh season with the Chiefs.

HC1stSBW

We know Mahomes has only been the starter for two seasons, but this highlights a five-year playoff run for the Chiefs that finally resulted in that coveted ring for Reid. It’s similar to other recent five-year runs to the top from the 2011-15 Broncos and 2008-12 Ravens. The 2002-06 Colts also needed a fifth-straight playoff trip to go the distance in the Tony Dungy-Peyton Manning era.

So does the dynasty talk already start tonight? We know this happens when a franchise QB wins one Super Bowl. We saw it in back-to-back years with Drew Brees (2009) and Aaron Rodgers (2010), but neither has even made it back to the Super Bowl. The last young franchise QB to win his first ring was Russell Wilson in 2013, and while the Seahawks made it back the next year, we know how that ended and they haven’t been past the divisional round since. We’re still in the longest drought in NFL history without a repeat champion (2003-04 Patriots).

The sky seems to be the limit for Mahomes and Reid together. We have seven months to talk about 2020 and repeating so let’s save it, but I am happy to see a new champion that is a joy to watch.

Whether it’s on this blog, another website, or maybe in a PDF you’ll order from me, I hope to bring a lot more analysis (and perhaps random musings) in 2020. Like Mahomes and scoring points, I’m a writer and I just need to write as often as I can while I can.

NFL Week 2 Predictions: The Good Life Edition

~ Scott ~ Leave a comment

I’m not going to say that Week 1 of the 2018 NFL season sucked, but when the first two full games I watched live were Falcons-Eagles and Steelers-Browns, it didn’t get off to the best start. The Week 2 schedule looks really good, but it didn’t take long for injuries to start having an impact. Some of the players missing in action this week include Devonta Freeman, Greg Olsen, David DeCastro, Olivier Vernon, and basically every long-time Seahawk not named Russell Wilson or Earl Thomas. We’re also waiting to see if Aaron Rodgers, Ben Roethlisberger, and Marcus Mariota are good to go this week at quarterback. We still must wait to see the 2018 debuts of Joey Bosa, Carson Wentz, Alshon Jeffery, and Jack Conklin.

Game of the Week: Vikings at Packers

I really hope Aaron Rodgers plays this one, because it is a huge game for playoff seeding despite it only being Week 2. The Vikings knocked Rodgers out early in the first matchup last year and didn’t have to see him for the second one. They shouldn’t get that advantage again this year. They also have Kirk Cousins now in what is arguably the second-biggest game of his NFL career when you think about it. His only playoff game was also against Green Bay and Rodgers, a 35-18 loss at home in the 2015 Wild Card.

Over the last three seasons in Washington, Cousins was 3-10 on the road against teams that finished the year with a winning record. You’d expect Green Bay to be that kind of opponent this year. However, that 3-10 mark includes wins last season in Seattle and LA (Rams). Cousins also should have had a signature win in Kansas City, but Josh Doctson dropped a game-winning touchdown in the end zone. He can function in these spots and his Minnesota debut last week was solid.

Mike Zimmer’s had some decent success against Rodgers in his career, and this should be the most talented roster he’s taken into a Green Bay game yet. As I pointed out in FOA 2018, Zimmer entered this season with the best record against the spread (44-23) among active head coaches. Last week, his defense forced Jimmy Garoppolo into the worst start (and first loss) of his young career, and covered the spread.

HCATS

We don’t know what the spread is yet for this one because of Rodgers’ health, but clearly he isn’t 100 percent. I think a lack of mobility can be troublesome against such a talented Minnesota defense, and the Vikings should have scoring opportunities on the other side of the ball. That’s why, regardless of Rodgers’ status, I like the Vikings to pull this one off on the road with a superior roster. I know I’m already going against my season predictions where I had these teams splitting the series with each home team winning, but I also didn’t anticipate another Rodgers injury situation so soon.

Chiefs at Steelers

Under Andy Reid, Kansas City has beaten just about every contender in the NFL over the last four years. That includes wins over six of the last eight Super Bowl teams: 2014 Seahawks, 2014 Patriots, 2015 Broncos, 2016 Falcons, 2017 Patriots, and 2017 Eagles. (They didn’t play against the 2015 Panthers or 2016 Patriots, but notched wins against those teams the following season.)

One team Kansas City has not beaten is Pittsburgh, or at least not the Steelers with Ben Roethlisberger at quarterback. They won a game at Arrowhead in 2015 when Landry Jones had to start. But Reid is 1-6 in his career against Roethlisberger going back to 2004 with the Eagles. That’s not even necessarily impressive for Ben, because he doesn’t play defense and the number that stands out in those seven games is 16. Reid’s teams never scored more than 16 points against the Steelers in those games.

That could really change on Sunday after the Chiefs come in hot behind new QB Patrick Mahomes after scoring 38 points in LA as underdogs. Mobile quarterbacks have been giving the Steelers fits as of late with Brett Hundley, DeShone Kizer (Week 17), Blake Bortles and Tyrod Taylor (he actually stunk passing, but still ran well) hanging pretty good scoring numbers on the defense. Now the Steelers could be without Joe Haden and Artie Burns in the secondary, which is bad news with Tyreek Hill and Sammy Watkins coming to town. This isn’t Mahomes’ first road start either so they can’t hang their hat on that advantage, though Heinz Field is a different beast from the Chargers’ small park. He looked pretty poised last week and this is one of the most talented offenses in the league. It just hasn’t clicked in the past against Pittsburgh, though James Harrison is no longer there to own Eric Fisher. T.J. Watt is coming off a huge multi-sack game, and the pass rush looked quite good in Cleveland albeit a very indecisive game from Taylor.

If Mahomes can avoid the turnovers on the road, then the Chiefs have a great shot to win this one. It’s a bad week for Roethlisberger to be questionable and missing practices with an elbow injury, because this defense looked really vulnerable for the Chiefs last week. Philip Rivers had huge numbers that would have been even better without so many drops. Roethlisberger should have success with his weapons at home where the Steelers obviously play much better. I think the conditions played a factor in several of the turnovers last week, a game that Pittsburgh almost certainly wins without the rain leveling the playing field.

It could be a really fun game, but I think the Steelers get a tight win at home to avoid an awful 0-1-1 start to what was supposed to be another season with Super Bowl aspirations.

Patriots at Jaguars

I wish this rematch of the AFC Championship Game was the Sunday night game instead of Giants-Cowboys, but you know we can’t let a September or October go by without getting that matchup at night. When you try to pick out one of the few games the Patriots are going to lose this season, you always start with road matchups against playoff-caliber teams. This should be one of those, though the Jaguars didn’t scream “playoff lock” to me coming into the season. The offense scored 13 points last week against the Giants.

Much of that has to do with Blake Bortles, who lost the two Allen’s (Robinson and Hurns) at WR, and Marqise Lee is out for the season with a torn ACL. I’m just not sure this team has enough firepower to keep up with the Patriots, who aren’t as loaded themselves right now, but still have the best TE in the game. For all the talk Jalen Ramsey did this offseason, I’d like to see him match up frequently with Gronk in this one. Walk the walk, if you will. That’s really the key to slowing them down right now without any Welker clones left (Julian Edelman is suspended for three more games).

It would take an excellent performance from the defense, which has the talent to pull it off, to keep the Patriots under 20 points (preferably under 17). I think that’s what the Jaguars must do to win this one, because I just don’t see Bortles putting up many points. NE played the Texans and Deshaun Watson well last week.

Alas, it doesn’t sound good for RB Leonard Fournette playing this week. I actually think that could help Jacksonville. Maybe they won’t lean so heavily on him, because in that playoff game, the Jaguars tried to run out the clock way too early and weren’t aggressive enough on early downs. Also, Corey Grant had three early catches for 59 yards in that game. Maybe this lets Jacksonville get more people involved and opens up the playbook instead of just trying to grind things out with Fournette.

NFL Week 2 Predictions

I started 10-5-1 for both ATS and SU last week, but fell victim (like many) to the Buccaneers’ shocking upset in New Orleans, the season’s first double-digit favorite to collapse. Starting next week I’ll post a fancier version of my results, but for now, here are my Week 2 picks with a Twitter update to come on my MIN-GB pick (likely going Vikings regardless of spread).

2018Wk2

My three favorite picks: NO -9.5, ATL -6, NYJ -3.