2024 NFL Stat Oddity: Conference Championship Games

~ Scott

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.

Unknown's avatar

Published by Scott

Leave a comment