Once again I was ready to proclaim Week 14 as one of the worst I ever covered in my history with the NFL. That’s not hyperbole; that’s research on the closeness of games. Through the 1 p.m. slate, about the closest finish we had all week was the Thursday night game between the Steelers and Vikings, a game where Pittsburgh trailed 29-0 in the third quarter before an impressive attempt at a historic rally came up short. You know it’s bad when one of the six comeback attempts this week was Houston, down 19-13, against Seattle in a game that ended 33-13.
This shit was rotten, and the three games between teams with non-losing records were among the biggest offenders. The Chiefs led the no-show Raiders 35-0 in the first half, the Browns were up 24-3 on the Ravens, and the Cowboys took a 27-8 lead into the fourth quarter in Washington. Two of those games fabricated drama late thanks to the Cowboys and Browns nearly shitting their pants, but there were never any lead changes there.
The 4 p.m. slate always looked better on paper this week, but it was not helping matters with the Chargers and Broncos jumping all over the Giants and Lions in routs. Once again, the two games between non-losing teams were most disappointing. Instead of close, high-scoring affairs, the 49ers led Cincinnati 20-6 late and the Buccaneers got up 27-10 on Buffalo in the fourth quarter. Then a Bears-Packers game to cap off the day? Give me a break. Rams-Cardinals better be an instant classic on Monday night to salvage this.
Then some funny things happened. The Bills and Bengals found their offenses, forced overtime, and both still lost to the only game-winning drives of the week. Then the Bears-Packers game went off the rails in the second quarter with the teams combining for 45 points on a lot of long touchdowns. It was really the most exciting quarter I’ve ever seen in a Bears-Packers game.
So, it ended up not being an all-time stinker of a week (unless you are stuck watching the Jaguars, then they’re all epic stinkers).
This season in Stat Oddity:
- Week 13
- No Week 12 (personal week)
- Week 11
- Week 10
- Week 9
- Week 8
- Week 7
- Week 6
- Week 5
- Week 4
- Week 3
- Week 2
- Week 1
Bills at Buccaneers: Interfering with My Plans
If there was an AFC-NFC matchup on the schedule this year that you would have circled as a Super Bowl preview, this was the choice for months. Sure, some would pick Packers-Chiefs, but even if you didn’t know Aaron Rodgers would miss it with COVID, you should still know better than to trust Green Bay to get back to a Super Bowl before the LOAT.
But the Bills looked far from Super coming into this one. They haven’t been able to stack wins since their season peaked with a Week 5 win in Kansas City. NBC’s Cris Collinsworth was ready to give Josh Allen the MVP that night just because the Chiefs couldn’t cover anything deep and couldn’t stop the ball from being tipped for interceptions.
You know who watched Buffalo fail to capitalize on multiple tipped balls in this one? Tom Brady. You know which defense didn’t give up a completion longer than 25 yards? Tampa Bay. But while the usually stout run defense watched Allen unconventionally do it his way for 109 rushing yards, it looked like the Bills putting 100% of the offense on Allen was a total bust.
Buffalo became the first NFL offense since at least 1991 to not give a single carry to a running back in the first half. The first non-quarterback run of the game was in the third quarter, and even that was a fake punt that failed miserably to convert. But despite getting two straight possessions inside Buffalo territory, Tampa Bay came away scoreless. That’s unusual.
Yet with Tampa Bay up 27-10 with 11:20 to play, this felt like it was finished. That’s when Allen quickly drove the Bills 75 yards for a touchdown, watched Brady go three-and-out with two incompletions, drove for another touchdown on a shorter field, and again the defense stopped Brady cold in the four-minute offense of a 27-24 game.
It was like watching Peyton Manning lead the 2009 or 2010 Colts against Brady’s Patriots those years, two attempts at 17-point comebacks in the fourth quarter with vastly different outcomes. Allen landed somewhere between game-winning touchdown and game-ending interception in this one.
The Bills, still winless (0-5) in close games this year, had a great drive going into the red zone, but Allen’s pass to Stefon Diggs in the end zone on third down did not draw a flag despite plenty of contact. I did not hate the no-call, but I’ve seen less get flagged. That led to a field goal and overtime.
While the Bills were red hot on offense, they immediately cooled with a disappointing three-and-out. A great punt pinned Tampa Bay at the 6, and a very close run by Leonard Fournette to convert a third-and-1 helped the Bucs avoid their own three-and-out. Imagine that. Then Brady got his bogus DPI penalty for 19 yards on a throw to Mike Evans, which again speaks to how inconsistently one of the most crucial penalties in the game is applied.
If that’s DPI, then why wasn’t it DPI on the Diggs play? The Bills could have easily won in regulation. When you give a receiver with Evans’ size and talent to a quarterback known to draw more DPI flags (a record number last year) seemingly out of reputation, it’s a nightmare for defenses. Alas, this was shockingly just the second DPI flag drawn by Evans this season. He led all wideouts with nine drawn DPI flags in 2020, not including two big phantom calls before halftime of the Super Bowl when it was still a game.
The Bills did not pass their first actual test without corner Tre’Davious White, though they did hold Brady to 6.78 yards per pass attempt on his first 45 throws. However, Throw 46 was fatal. On a third down near midfield, the game was decided once Brady found Breshad Perriman and he had a clear 58-yard path to the end zone to end this one. Tampa Bay is going 14-3 with this schedule, and this team may not lose another game this season unless someone really steps up. Maybe it’s Arizona or Green Bay or the hottest AFC team, but it probably isn’t Buffalo.
But if there somehow is a rematch in February, then maybe the Bills can take some notes and pride from this near comeback. Like how the Bucs turned things around from Week 12 on the Chiefs last year, or how the 2007 Giants gained confidence from the 16-0 game against the Patriots for that year’s Super Bowl upset.
49ers at Bengals: Look Who Can’t Close Again
The headline looks like I’m going to attack Kyle Shanahan again, but we know the 49ers got a big overtime win in Cincinnati. I’m going to attack Shanahan anyway, but the focus is on Zac Taylor, who is now 2-17 when his Bengals have a 4QC opportunity.
Worse, Taylor’s 4QC record is 1-8 with Joe Burrow as his quarterback. Compare this to the 49ers. Shanahan is a poor 9-21 (.300) at 4QC opportunities, but that record improves to a stellar 8-7 (.533) with Jimmy Garoppolo at quarterback, leaving him at 1-14 with the other quarterbacks.
Fairly small samples, but still about as night and day as it gets. This looks bad for Burrow, who only has a comeback win against the Jaguars, but he was not the big problem in this game. In fact, it could have easily ended in regulation after Burrow tied the game if Robbie Gould hit a 47-yard field goal as time expired for the 49ers. No overtime comeback necessary.
Of course, the 49ers got there after only scoring 20 points on their first 11 drives despite the return of Deebo Samuel. That even included an 8-yard field goal drive and a 31-yard touchdown drive set up by two muffed punts by the Bengals.
While George Kittle (13 catches for 151 yards and a touchdown) was a beast again, this Samuel thing fascinates me. He got eight carries for 37 yards and a touchdown, but Samuel received just one pass target, which he caught for a 22-yard gain. And while Deebo produced a 27-yard touchdown run, his other seven carries produced 10 yards and one first down. That’s kind of lousy production when you’re going to sacrifice his skills as a wideout for that type of rushing.
I thought the 49ers figured something out in their upset of the Rams when Deebo had five catches for 97 yards and a touchdown to go with five runs for 36 yards and a touchdown. Maybe this dual-threat thing is just a reaction to the injuries at running back and getting your most talented player the ball in space, but Samuel is a damn fine wide receiver too. In the last three games, he has three catches for 49 yards. That’s not an average; that’s his TOTAL for three games. In the first nine games this season, Samuel was AVERAGING six catches for 108.8 yards per game. They need to find a better balance of using him on some runs and still utilizing his skill as a No. 1 wide receiver.
This game nearly slipped away with the 49ers not being able to finish more scoring drives. The Bengals finally came to life in the fourth quarter with two touchdowns to Ja’Marr Chase after he dropped one earlier in the game. But after getting the ball first in overtime, the Bengals curled up a bit after two explosive passes and ran the ball twice. Nick Bosa logged a key sack of Burrow on third down and the 49ers held the Bengals to a field goal to extend the game. You’d like to see Burrow finish the game off, which he’s failed to do multiple times this year now against teams like the Bears and Packers.
Garoppolo drove the 49ers 75 yards with no real pressure of the clock and four downs to use. They only came up on a third down once and Kittle converted it with ease. Brandon Aiyuk showed some nifty moves on the game-winning touchdown, just doing enough to break the plane to end the game.
It is fitting for both teams to be 7-6 as they are above average but maddeningly inconsistent. I thought the Bengals would perform better after the Baltimore loss presented a big opportunity in the division race, but the 49ers led most of the game and nearly won in regulation.
It’s also crazy to me that the over (48.5 points) hit on the nose after getting the necessary and very precise combination of a 14-point Cincinnati comeback, a missed game-winning field goal in regulation, a go-ahead field goal to start overtime, and a game-winning touchdown to get to 49 points. Almost like it was fixed.
But when it comes to these Bengals and close games, count on disappointment.
Bears at Packers: 45-30? These Two?
These teams met in prime time for the 16th season in a row, but it may have actually been the best first half they ever played. If you told me Chicago scored 27 points in the first half and it didn’t involve multiple turnovers and return touchdowns a la “We let them off the hook!” I wouldn’t have believed it. The Bears are the first team since the 2020 Packers (in Indy) to score at least 27 points before halftime and lose the game.
In fact, since 1940 the Bears were 51-0 when scoring at least 27 points in the first half. Make that 51-1 now.
I also wouldn’t believe Jakeem Grant turning into Tyreek Hill. I knew he was a fine returner for Miami, but his impact in this game was ridiculous. I still can’t believe how horrific the special teams were for Green Bay, and that doesn’t even include the plays late in the game they caught huge breaks on, like a muffed punt getting wiped out by a player running out of bounds penalty, or a stupid NFL rule that says you cannot advance a muffed onside kick for a touchdown. You absolutely should be able to do that. The way the play happened tonight proves the rule should be changed for onside kicks. Make them a little more fun.
The Bears knocked Aaron Rodgers around in the first quarter, but once his pass protection settled in, he shredded them for 341 yards and four touchdowns. Yes, he still owns the Bears.
Justin Fields mixed some good (big plays and 74 rushing yards) with bad (they were mostly YAC and his pick-six). The Packers dominated the third quarter, 17-0, to prevent the fourth from having any real drama (outside of the spread).
But as far as a Packers-Bears game in prime time, this was passable. Who knows, it could even be the last time Rodgers is involved in one…
Raiders at Chiefs: That First Play Knockout…
I’m really starting to believe it’s impossible to fumble for a touchdown on the first play of scrimmage and not get completely blown out. The Raiders did this in Kansas City with a fumble by Josh Jacobs on a run. That’s less egregious than the high snap over Ben Roethlisberger’s head that led to a Cleveland touchdown in the wild card round last January, or the same thing that happened to Peyton Manning’s Broncos in Super Bowl 48 (for a Seattle safety that time).
The Raiders didn’t show up for this one. They turned the ball over five times, including four lost fumbles. Patrick Mahomes with an elite defense is terrifying, and that’s especially true when he is shredding the Las Vegas defense this season. The big plays returned for the Chiefs’ offense, and they nearly had the first shut out with a 35-point lead at halftime in the NFL since the 2015 Dolphins were up 41-0 on Houston.
The Chiefs get a big test with the Chargers (in LA) on a short week this Thursday. A true first-place battle for the division. But while the Ravens and Bills finally beat the Chiefs triumphantly early in the season, this team is playing much differently now. The defense has been incredible and the offense is not except for the Raiders games. Can’t wait to see that one on Thursday. Meanwhile, the Bills and Ravens are falling apart at the moment. The Chargers are doing well, but the Chiefs have a shot to maintain control of the division and maybe the conference once again.
I’ve been saying it for a couple of weeks, but it really is looking like a season where Patriots-Chiefs is the AFC Championship Game and the winner faces Tampa Bay in the Super Bowl. That sounds absolutely awful, but if no one else is going to step up in this era…
Ravens at Browns: Not This 15-Point Deficit Thing Again…
I really don’t feel like talking about this at 4 AM again, but there were a lot of games this week where a team was down 15 points in the fourth quarter, scored a touchdown, and had a decision to make with a 9-point deficit.
- PIT/MIN: Steelers tried for two with 12:11 left, failed, got behind by 16, cut that in half, and eventually lost 36-28.
- CAR/ATL: Panthers kicked extra point at 3:11, kicked off deep with four clock stoppages, but left Kyle Pitts wide open on a third-and-14 and couldn’t get the ball back in a 29-21 loss.
- BAL/CLE: Ravens tried for two with 8:56 left, failed, scored a touchdown on their second drive with 1:17 left, recovered a miracle onside kick, and went four-and-out after a horrific ALEX throw on fourth down by backup Tyler Huntley, who performed better off the bench than Lamar Jackson (ankle) played in a win against Cleveland two weeks ago. The Browns won 24-22 this time as the Ravens (+2.5) got a miracle cover but still lost.
I was lukewarm with Pittsburgh’s decision, because I think Troy Aikman actually made the proper point that kicking and making it an 8-point game (one possession) would keep the pressure on a Minnesota team that has choked away games all year long. When you run a terrible two-point play and don’t get it like Pittsburgh did and trail by nine, that would take a lot of air out of my sail and let the Vikings relax a little. I think we saw that with the long touchdown the Steelers gave up falling behind 16, but after a Kirk Cousins pick, the Steelers had a chance at the end of the game still. But the main reason I didn’t hate Mike Tomlin’s call is that it was so early in the quarter that they had plenty of time to answer from a two-score deficit.
I thought Matt Rhule absolutely made the right call to kick, but he initially wanted to go for it and was only turned away by a false start that pushed the ball back 5 yards. Again, why effectively decide the game at 3:11? Extend the game, kick the extra point, make it a one-possession game, and put the pressure on an Atlanta team that folds as much as anyone. The Falcons even started with a holding penalty and 1st-and-20, but the Carolina defense collapsed and couldn’t get the ball back. But just keep extending the game.
Then we have this Baltimore one, which wasn’t as early in the game as Pittsburgh, but not as late as Carolina. I’m supposed to believe John Harbaugh is a genius because his failed 2PC with the backup QB led to a Cleveland 3-and-out, Baltimore 3-and-out, Cleveland 3-and-out, 90-yard Baltimore touchdown drive, and miracle onside kick recovery with 1:15 left? Really?
How about you let the best kicker ever make that extra point to go to 24-16, then when you get that touchdown later, you have your shot at the game-tying two-point conversion you fucked up a week ago? And guess what? If you blow it again, you can still onside kick and recover your miracle kick and go win on a field goal.
The “go for two early” crowd continue to make two bad assumptions and ignore that their decision is more likely to lead to needing to recover one, if not two onside kicks. It ignores that the difference in the likelihood of a seven and eight-point comeback is not more significant than the difference between seven and nine-point comebacks.
The first bad assumption is that “having more information” actually makes offenses play differently in these situations. They flat out don’t do that in the NFL. A team down 9-11 points is not going to run a super-fast no-huddle offense with so many minutes left in the quarter. They’re going to run things similar to a team down 4-8 points with an eye on the touchdown first. Were the Ravens in hurry-up mode down 15 with 11:30 left, knowing the information that they may need three scoring drives the rest of the way? No, they dicked around with a 2-yard run, a loss of 3 yards on a pass to the back that took up 40 seconds, and they were fortunate to convert a 4th-and-11 at their own 30 that should have effectively ended the game early if Cleveland got the stop.
It was only with 5:26 left, and the Ravens down two possessions thanks to the failed 2PC, that Baltimore got into a more conventional hurry-up offense.
The second bad assumption is that teams down 8 points are trying to score a touchdown as late as possible, leaving themselves little time if the tying 2PC fails. Again, this is wrong. Most offenses take touchdowns as they come. Many even try to force plays way too early that would leave too much time for the opponent to answer. Do I need to remind Baltimore fans of Joe Flacco’s interception down 35-31 in the 2014 playoffs in New England? What was that going to accomplish other than leaving Brady enough time to win the game in regulation?
In a perfect world you can score a touchdown at the exact time you want, but it doesn’t work that way in reality most of the time. Look at the Davante Adams touchdown before halftime for Green Bay. They left enough time for the Bears to add another field goal. It happens. That’s just the NFL.
So there is no reason to assume that the Ravens would have scored significantly later than the 1:17 that they scored their touchdown with. There’s also no reason not to think had they been down 24-22 and failed on a game-tying 2PC, they could still try the onside kick and recover like they did. It does not take long to set up a field goal, and Justin Tucker’s range is as good as anyone. Alas, the Ravens had a weak final drive and lost the game.
But acting like the failed 2PC call early is WHY the Ravens would have won rather than an inexplicable onside kick recovery is the type of silliness that makes me rant about this every single time. Why couldn’t they possibly get the same onside kick recovery and GW FG had they gone for two only when they had to?
Hopefully Lamar isn’t out long, because there are still some battles to be had with this Baltimore team even as it continues to struggle.
Cowboys at Washington: What the Dak?
Did you know Dak Prescott (45.9) is ranked 23rd in QBR this season, one spot ahead of Ben Roethlisberger (43.4)? Yet I don’t see much criticism of the 28-year-old quarterback who should be in his prime on a loaded offense like I do of the 39-year-old quarterback on his way to retirement. While Roethlisberger has gotten better over the last eight games, Prescott’s season seems to be going the other direction after a hot start.
But even going back to opening night in Tampa Bay when he sailed a pass for CeeDee Lamb for an interception, something just seems to be off with this offense too often for my liking. Even two months ago, I was not feeling the Dak for MVP love at all.
While the team’s best running back these days (Tony Pollard) was out, the Cowboys still gave Dak Tyron Smith at left tackle, his top three wideouts, and Ezekiel Elliott. The Cowboys scored one offensive touchdown on a 41-yard field set up by an outstanding interception by Randy Gregory, who should be a lock for NFC Defensive Player of the Week.
It was also Gregory who forced a crucial strip-sack of Washington backup quarterback Kyle Allen after the Cowboys nearly blew a 27-8 lead in the fourth quarter thanks to a Prescott pick-six with 4:13 left. But Gregory closed the door on that comeback at 27-20, and Dak finally ran for a game-clinching first down to end it.
I never thought the Dallas defense would jump ahead of the offense like this, but that seems to be where we’re at this season. With only one non-division game left on the schedule, we’ll see just how much of a contender Dallas can be in the playoffs when the Cowboys host Arizona in Week 17.
Hurry-Up Finish
Some quick thoughts as I race to complete more tasks before getting to sleep.
Giants at Chargers: Herbert, FTW
I may have to formally share my Justin Herbert MVP thoughts this week, but for now, here’s a brilliant deep throw for a touchdown to escape pressure and convert a third-and-long.
The ball traveled 63.8 yards in the air according to Next Gen Stats, second-longest completion of 2021. Herbert has hit 10 passes of 55-plus air yards since 2020 to lead the league. The kid is special, and in this game, he became just the 16th unique QB in NFL history to throw 30 touchdowns in consecutive seasons and the first to do it in his first two professional seasons.
Saints at Jets: Gambling Is Dumb (NFL Exhibit 18,194)
I made one Same Game Parlay on this silly game, and it hit because Taysom Hill decided to keep running for a 44-yard touchdown on 3rd-and-12 while leading 23-9 with just over a minute left. He could have gone down at any time after getting the first down, but he kept going, allowing his 60+ rushing yards prop to hit.
Gambling is dumb and winning doesn’t make you feel smart. But it still feels a hell of a lot better than losing.
Jaguars at Titans: Before You Make That 1998 Peyton Manning Comparison…
I promise I am going to make that piece about why bad rookie quarterback seasons should not be compared to Peyton Manning’s 1998 rookie campaign, which set a record for interceptions (28) but also smashed a lot of other rookie records at the time. By the seventh game, Manning started to figure things out and the Colts were an above-average offense. He showed real improvement while someone like Trevor Lawrence seems to be doing no such thing under the terrible coaching of Urban “Dead Man Walking” Meyer.
Lawrence threw four interceptions of varying degrees of egregiousness in Jacksonville’s 20-0 loss against the Titans. It was the fifth game this season where Lawrence led the Jaguars to fewer than 11 points, something that happened twice in Manning’s 16-game rookie season and five times in his first 72 starts. That Lawrence total does not include a sixth game against Denver where only a kick return touchdown got the Jaguars to 13 points as the offense managed one touchdown in a 23-13 loss.
Again, hold out hope that this is 2016-17 Jared Goff all over again, but the Jaguars better find one hell of a coach to get that kind of improvement in 2022. Adding some talent would help too. Lawrence was using Tavon Austin and Carlos Hyde on crucial downs today. In 2021. Christ.
Next week: The very rare, front-loaded week. I’m hoping Chiefs-Chargers (TNF) and Colts-Patriots (Saturday Night Football) deliver enough that I can forgive the shitfests to come on SNF (Saints-Bucs) and MNF (Bears-Vikings).
Captain Comeback: NFL Analysis by Scott Kacsmar 
8 thoughts on “NFL Stat Oddity: Week 14”