NFL Stat Oddity: Week 14

~ Scott

Week 14 in the NFL was a lot to take in. Or a little if you were caught watching either of the two games that were scoreless at halftime. Seriously, we go 4 years without a scoreless first half and get two in one afternoon? That second one almost went the distance to 0-0 in regulation but thank God for Nick Mullens (said no one ever).

The Cowboys blew out the Eagles, who lost back-to-back games against their main NFC contenders by 20 points. Sounds pretty 2022 Vikings to me.

The Bills won another game in Kansas City after an egregious offside penalty on the offense wiped out one of the coolest, game-winning type of plays you’ll ever see. But that doesn’t mean it wasn’t a dumb penalty, Kansas City.

Did offense feel worse than usual this weekend? We still have a MNF doubleheader that does not look good, but there has yet to be a quarterback to post a 75.0 QBR this week. Most weeks have multiple players in the 80s and 90s. The highest was Matthew Stafford (73.4) in a loss in Baltimore. This is so unusual that it hasn’t happened in any week of the regular season since 2006, the first season we have QBR data for. Maybe Tua or Jordan Love puts an end to that tonight, but Monday night shenanigans, the MetLife playing surface, eh, we’ll see.

There were 7 games with a comeback opportunity this week, though for the second time this season, no team came back to win from 10 points down. The Steelers and Chiefs almost did that, but again, we’re seeing arguably the darkest patches of the Mike Tomlin and Andy Reid eras in Pittsburgh and Kansas City. Losing back-to-back home games to 2-10 teams is brutal (and historic), and the Chiefs are on a 2-4 slide and just lost wire-to-wire in back-to-back games for the first time with Mahomes at quarterback.

This season in NFL Stat Oddity:

Bills at Chiefs: Toney, Toney, You Gotta Go

Another week, another Kansas City loss where the Chiefs gave up two early touchdowns, lost the turnover battle, a receiver royally screwed up a lead-changing play, and Patrick Mahomes’ last gasp on 4th-and-long fell incomplete.

Then there’s the latest officiating controversy.

But I don’t think it was that controversial. The irony of it was Kadarius Toney scored the touchdown and it would have been his most memorable play had the schmuck not lined up offsides.

Offensive offsides, who even does that? But before that ending, it was another game where the Chiefs played disappointing, mistake-filled football. They let the Bills dominate early with passes to their running back (James Cook) while Mahomes seemingly can’t throw a screen to CEH without disaster happening like an opening-drive interception in Buffalo territory.

Rashee Rice provided the obligatory fumble late in the third quarter when the Chiefs were driving in a 17-14 game. They did tie the game in the fourth quarter, but a quick 3-and-out with a chance to take the lead wasn’t good, then Josh Allen continued to show why he’s been so successful in Arrowhead with a go-ahead drive for a field goal.

The only problem with that was a total mismanagement of the clock, and you would think Buffalo more than any team would be observant of the clock against the Chiefs. They are 13 seconds away from going 4-0 in this building since 2021. The Bills had a chance to set up the field goal as the final play, but Allen threw 3 low-percentage balls to receivers that all fell incomplete and stopped the clock with the Chiefs keeping 2 timeouts. It made no sense. Even the last throw before the 2-minute warning was barely caught for a 1 yard to run clock.

So, Mahomes had a full 1:54 in a 20-17 game, which is an eternity for him to get a go-ahead touchdown, let alone a field goal. But four plays into a good looking drive, it happened. Mahomes found Travis Kelce over the middle and he somehow had the stones to lateral the ball across the field to Toney, who went the final 24 yards for what should have been a huge go-ahead touchdown and possibly the game-winning score to end Buffalo’s season.

It will go down as an all-time great play that never counted. It was aesthetically pleasing, in a big moment, risky as hell, and a huge reward. But it’s all for naught cause the biggest clown on the roster was lined up offsides.

Is that going to be called 100% of the time on the offense? No, I don’t think so. Is it ever called on the offense? Apparently 11 times this year, so less than once a week. I understand the argument that it was inconsequential to the play, but I also think the strong reaction from the Chiefs, namely Mahomes and Andy Reid, is way overblown. Just don’t line up offsides and it’s not a penalty. How hard is that? Does a veteran really need a warning for this late in the fourth quarter? I could see if he was repeatedly doing it in the game, then the officials should inform him of that. But there’s just no excuse to line up in the wrong spot on a play where the clock wasn’t even running.

Like the other Kansas City drives this year, they fell apart after the big play was not made. Think of the Toney drop against Detroit that could have easily set up a game-winning field goal, the MVS dropped touchdown against the Eagles, the no-call for DPI on MVS against the Packers last week, and now this offsides wiping out a touchdown.

It’s like the Chiefs get so frustrated from these plays that they forget to finish the drive. Namely, the offensive line forgets as the protection turning to dog shit has a lot to do with these drives fizzing out a couple plays later. Mahomes had to throw away passes under pressure, and just like that, it was 4th-and-15. Here we go again.

Mahomes’ arm was hit just as he threw the ball and it came out funny with no chance of ever being caught. Another game over after Mahomes threw incomplete on a 4th-and-10+. That’s happened in all 5 losses this year. It happened in exactly one Kansas City game in 2018-22 and that was Super Bowl 55 with a lopsided score.

The Chiefs are 8-5 and barely hanging onto the No. 3 seed right now. It is looking likely that they will have to play a road playoff game this year. I guess it is possible for the Chiefs to win out (12-5), then hope Miami loses multiple games to Cowboys/Ravens/Bills to finish with a No. 2 seed or better. Then they’d have to hope No. 1 (Baltimore) chokes in the divisional round, which isn’t impossible of course. But it’s not looking good. At this point, the Chiefs might get shut down by New England and lose to Bailey Zappe next week. Jake Browning with the Bengals is a possibility too.

Mahomes’ strong reaction to the ending was weird to me. It almost felt like he was letting out years of frustration with calls like this, maybe even going back to the Dee Ford offsides in the 2018 AFC Championship Game loss, another rare offsides call that had nothing to do with the play at hand. Hard to think of any team in between 2018-23 with bigger offsides penalties than the Chiefs with these two. Then with the way last week’s game ended in Green Bay, it’s just been a frustrating season for Kansas City and I think he chose to take it out on the refs instead of strangling Toney, who really needs to be cut. He provides no value and has almost single-handedly cost them games against the Lions and Bills this year.

But not knocking out the Bills (7-6) when you had a chance could prove fatal. Imagine if this propels Buffalo to make the playoffs and this ends up being a 7/2 or 6/3 wild card matchup. That would not be good for the Chiefs, who struggle with Buffalo as much as any opponent.

But we’ll see how things go from here and if Buffalo can build from this with a tough remaining schedule. The Chiefs only have 4 games left to improve, but it feels like both sides of the ball are declining right now.

Trading away Tyreek Hill and trading for Kadarius Toney is epic team mismanagement. That’s almost as bad as getting Trent Richardson for Andrew Luck in Indy when he literally needed any other good player besides a running back.

This is the first time since 2017 where the Chiefs failed to have a lead in back-to-back games. Those were the ugly losses to the Giants (12-9 in overtime) and Buffalo (16-10). Do you know what that slide led to? Andy Reid gave up play-calling duties to offensive coordinator Matt Nagy, who is the OC now in 2023.

Might need a new plan here, because this isn’t working. I made this prediction before Week 7 when the Chiefs were 5-1, and it was tongue-in-cheek at the time. But my goodness, this is where the Chiefs are seemingly every week now. A game-winning play is botched, the offensive line falls apart, and there’s Mahomes throwing a miracle ball on 4th-and-long to end the game.

This is who Kansas City is in 2023 and I don’t see it changing this time. And that is why the frustration is boiling over on the field now.

Eagles at Cowboys: Another NFC Stomping

The big NFC round robin is complete now, and the 49ers come out looking like the best team after stomping the Cowboys (42-10) and Eagles (42-19) this year. The Cowboys and Eagles split their matchups with Philadelphia winning 28-23 at home and then Dallas returning the favor with this 20-point win.

So, only 1-of-4 games ended up being a competitive 60-minute game. But this is what I was saying about the Eagles the last few weeks. They rely on winning close games this year while the 49ers and Eagles blow teams out. They are your classic “win big, lose close” teams, and they just blew the Eagles out by 20 points in back-to-back weeks.

The crazy thing with this game is that the Eagles never even scored a touchdown on offense. Their only touchdown was Jalen Carter returning a fumble of Dak Prescott 42 yards for a score in the third quarter, the last time this looked like it might be a game.

Prescott said as much after the game that he didn’t have his best night, and he certainly didn’t. The Cowboys left plenty of points on the field, and we did at least see how awesome their new kicker is as Brandon Aubrey improved to 30-for-30 on the season at field goals with makes from 60, 59, 50, and 45 yards, making it look easy in the process. Yes, this has “misses first time all year in a crucial playoff moment” written all over it, but he was money in this game, becoming the first kicker to make from 59 and 60 in the same game.

But Prescott did not hurt his MVP case. In fact, he’s the outright leader now after he threw for 271 yards and 2 touchdowns, notching a 12th-striaght home game with at least 27 points scored (third-longest streak in NFL history).

Dallas was in control and moving the ball well from the opening drive. The Eagles were too sloppy with the ball. Jalen Hurts, who didn’t even pass for 200 yards again, lost a fumble on his team’s opening drive. A.J. Brown had a nice game, but he also fumbled on the team’s opening drive of the second half at midfield, down 24-6.

Down 27-13 late in the third quarter, Hurts threw for 3 yards on 3rd-and-11, then a 1-yard completion to DeVonta Smith on 4th-and-8. Those are failed completions. Finally, any chance of an improbable 17-point comeback was snuffed out when Smith fumbled a completion in the red zone with 6:38 left. Game over. The Eagles’ top 3 skill players all lost fumbles in this one.

But as I said last week, the 49ers and Cowboys could have beat the Eagles by 50 points each in these games, and there’s still a good chance Philadelphia gets the No. 1 seed, the bye week, and gets to host the rematch with these teams, who are now all 10-3. The Eagles don’t play any good teams the rest of the way. The Cowboys have to go to Buffalo and Miami the next two weeks, tough road games against contenders. The 49ers have to host the Ravens on Christmas, a tough game.

But we can save talk about future games for down the road. It’s just an eyesore on Dallas’ resume to lose that game to Arizona as a 13-point favorite, because that could be the one that costs them a No. 1 seed. Strong performance here by the Cowboys, and maybe the back-to-back beatings puts some doubt in the Philadelphia locker room.

But chances are the Cowboys (and 49ers) will have to do it again to Philly in January.

Rams at Ravens: Unexpected Hero in Unexpected Overtime Classic

Lamar Jackson is now 19-1 against the NFC in his career, but this may have been the toughest win to earn yet. I really did not see this coming as the Rams were a 7.5-point road underdog, and we’ve seen the Ravens destroy some NFC teams at home this year like the Lions (38-6) and Seahawks (37-3). My thought on Lamar against the NFC is that those teams just aren’t familiar with playing him yet and it takes some experience as he is such a unique talent.

But the Rams scored on 4-of-5 drives to start the game, had no turnovers on the road, and Matthew Stafford showed up for this one. Both quarterbacks had 3 touchdown passes and Stafford was only 6 yards away from matching Lamar with a 300-yard passing game. Jackson also rushed for 70 yards.

It was a tight, enjoyable back-and-forth game with plenty of points – exactly the kind of experience we almost never get in 2023. The Rams took a lead on a safety at one point when a bad snap was kicked out of bounds by Jackson to avoid a touchdown going on the board. But the defense made a stop, and Jackson put Justin Tucker in range for a 33-yard field goal to regain the lead with 11:17 to play in a 23-22 game.

A couple drives later, Stafford threw a touchdown, but the Rams failed on the 2-point conversion, leading 28-23 with 4:41 left. Not many comeback drives in situations like this in Lamar’s career, but he pulled this one off just when it looked like things were falling apart at the end with a 3rd-and-17. Zay Flowers was left open for a 21-yard touchdown with 1:16 left, and the Ravens made the crucial 2-point conversion this time to take a 31-28 lead.

Stafford has plenty of experience doing this, and a big play to Cooper Kupp moved the ball to the Baltimore 22. But the Rams were not able to get any more than 4 yards from there, so they settled for a game-tying field goal and overtime.

The Ravens went 3-and-out in overtime, which we don’t penalize enough for the team that goes first on offense, because now all the Rams had to do was get a field goal to win. But the Rams also went 3-and-out, and Sean McVay let an inexcusable delay of game penalty happen on the drive to make it 3rd-and-9. You get timeouts in overtime; you should use them there to avoid that mess.

The Rams punted, and while you usually don’t expect much on these plays anymore, the Ravens made them pay with Tylan Wallace returning the punt 76 yards for a touchdown. It almost had a Steve Young vs. Vikings quality to it with Wallace stumbling after 3 broken tackles, but he housed it for only the 4th game-winning punt return touchdown in overtime history:

And that is the shocking way the Ravens moved to 10-3 and the Rams dropped to 6-7. A much better game than you could have expected from this one. This is the second non-offensive game-winning score of the year. The first was T.J. Watt’s fumble return touchdown from Deshaun Watson in Week 2 in Browns-Steelers.

Vikings at Raiders: Almost 0-0

I thought 6-0 last week in New England in decent weather was bad, but 3-0 indoors in Vegas?

At some point, I stopped being mad at the lack of scoring and was rooting for history to be made with a scoreless overtime tie, which has never happened in NFL history. It may have happened without a quarterback change by the Vikings, which led to the game-winning drive as Nick Mullens finally strung together some completions after Joshua Dobbs could not.

We were really close on this one:

  • The last scoreless tie in the NFL was in 1943 between the Giants and Lions before overtime existed.
  • Vikings-Raiders is only the 11th game since 1940 with no more than 3 combined points.
  • It is the NFL’s first 3-0 game since the 2007 Steelers beat Miami in the game where the punt stuck in the ground. Pittsburgh’s score came with 17 seconds left, so this game was the longest an NFL game had gone scoreless since this one in 2007.
  • Almost 30 years to the date, the Jets and Redskins played a 3-0 game on 12/11/1993 with the Jets scoring in the first quarter. That makes Vikings-Raiders and Dolphins-Steelers the only games with fewer than 6 combined points in the salary cap era.

So, we didn’t get the record, but we can say this is the 2nd-longest game to last scoreless since 1978.

Given the shitshow the Vikings put on against the Bears their last timeout, Kevin O’Connell has to explain why things are broken right now, and Dobbs may be out of the starting lineup next week now that a division title is within reach.

Justin Jefferson returned from his hamstring injury in this game, but he unfortunately didn’t last long after taking a nasty shot to the back. But the Vikings still have weapons. Certainly enough to do better than 9 punts on 11 possessions. The game only had 1 missed field goal (by Minnesota) and the Raiders turned it over 3 times in the second half, including a big fumble in the red zone by Hunter Renfrow, and Aidan O’Connell was immediately intercepted after Greg Joseph’s 36-yard field goal provided the only points at the 2-minute warning.

I’m not sure Mullens is the answer going forward, but it doesn’t look like Dobbs is. I’m also not sure you can hire an interim coach who loses a home game indoors 3-0 like Antonio Pierce just did.

And oh joy, both teams will be in island games this week with the Raiders playing the Chargers on Thursday night and the Vikings on Saturday against the Bengals.

Seahawks at 49ers: Drew Locked Up Some Millions

Not much was expected from this game with Drew Lock starting for an injured Geno Smith. The spread moved above 14 points, but I did like Seattle to cover that as divisional rematches can be weird.

This one was a little weird as Lock played a competent game and the Seahawks were within striking distance. But the 49ers averaged 9.9 yards per play on their way to 527 yards as the studs were not being stopped on this day. Christian McCaffrey kicked it off with a 72-yard run on the first snap, though he was taken out for a breather and never scored a touchdown despite having odds in the -350 range to do so this week. Ouch.

Deebo Samuel had another huge game with 149 yards and a touchdown. Brandon Aiyuk (126 yards) was also over 100 yards, and George Kittle caught a 44-yard touchdown, because of course he did. Where was that on Thanksgiving when I needed 40 yards from him to win $2,500?

But anyways, it was the Kittle touchdown two snaps into the final quarter that shifted everything as Seattle was only down 21-16 before that score. Lock was then intercepted twice, and the 49ers ran out the clock for another win that all but wraps up this NFC West race.

But Lock probably made himself a few million in the process as a competent start against what looks like the best team in the league could keep him around for years to come in a league starved for quarterbacks.

Yet it is Mr. Irrelevant who continues to break football minds as he had another big game with 368 yards on just 27 attempts. It wasn’t the big YAC plays this week like last week in Philadelphia too as Purdy dropped some balls right in the basket in big moments. He’s legitimately very good in running this offense, and while a lot of quarterbacks may be in his shoes, you look around at the 0-0 scores on Sunday and the other offenses that struggled to find the end zone at all like the Eagles, and you have to say Purdy is a remarkable story.

Lions at Bears: No 12-Point Comeback This Time

I think you have to be worried if you’re a Detroit fan that this thing is about to spiral out of control. No, they still haven’t lost back-to-back games yet this year, but losing out and losing the division title to Minnesota is now a real possibility.

The Lions needed the miracle comeback of the season to erase a 12-point deficit against the Bears at home just a few weeks ago. This performance was even worse in Chicago as the Bears did what they did on offense again, but the Lions had no strong finish this time. In fact, things only got worse with the Lions going scoreless on their 7 possessions in the second half, including a fumble, two failed 4th downs, and an interception on their last 4 drives.

It was an aborted snap by Detroit late in the third quarter that led to a short field for the Bears, who turned it into a touchdown and 25-13 lead. Fittingly, it was another 12-point comeback opportunity, but Jared Goff just didn’t have it in the elements this day. The running game was solid with David Montgomery and Jahmyr Gibbs both going over 60 yards, but when it came time for a 4th-and-1 conversion, Gibbs was stuffed in the backfield for a 4-yard loss.

The Lions were taking their time on the ensuing drive in a 28-13 game, and Goff eventually threw incomplete on 4th-and-17 with 5:16 left. More pressure on him on the next drive led to an interception on 4th-and-24 with 2:31 left to seal it.

Detroit played much better in the first matchup when turnovers put them in a hole. This time, the Bears more or less controlled play from the opening kickoff, something we have rarely ever seen in the Matt Eberflus era.

The Lions have now allowed at least 26 points in all 5 games since the bye week. Without a home win against Denver next week, this is going to get very dicey with games against the Vikings and a trip to Dallas left.

Colts at Bengals: Nice System in Cincinnati…

I hope Jake Browning’s thumb is good because this is getting really interesting in Cincinnati. For the second start in a row, Browning completed at least 75% of his passes with at least 275 yards in a win against another playoff contender in the AFC.

He didn’t take any sacks against the Colts, and his only real mistake was a pick-six that was a receiver error as he handed the ball to the defender on a silver platter. That also proved to be Indy’s final score of the game as the offense only mustered one touchdown drive in a 34-14 loss. It was only the second time all year the Colts failed to score 20 points in a game under Shane Steichen.

They picked a bad time for it with the Bengals in that wild card mix. But Browning clearly won this battle of backups, and Gardner Minshew may have even stayed in the game despite a possible concussion early in the game. The Colts failed to score on their final 5 possessions.

The Colts (7-6) might be in real trouble when you consider how games with the Steelers, their next opponent, usually go. Not only do you have to contend with Minshew’s mistakes, but the running game has essentially gone nowhere in 4-of-5 games.

The Bengals (7-6) are not finished as they have stumbled onto something to work with at the quarterback position in Browning.

Jaguars at Browns: Lawrence Returns But So Has Joe Flacco

Trevor Lawrence has still never missed a start due to injury in his NFL career, but sometimes you wonder if it’s not for the best if a player takes a week to rest. Lawrence barely averaged 5.0 yards per attempt as he threw 50 passes, including 3 interceptions, a 31-27 loss in Cleveland that felt like a 5-hour game.

Cleveland led wire-to-wire with Joe Flacco stepping up to throw for 311 yards and 3 touchdowns, simultaneously making you want to praise Kevin Stefanski for finding quality play in another quarterback not named Deshaun Watson while also questioning just how good that Jake Browning performance was on Monday night if the Jags are playing defense like this. Seriously, David Njoku was left wide open several times for big plays in this one.

But the Jaguars continued to struggle running the ball effectively, and the turnovers were hard to overcome. The game went on so long in part because Cleveland also turned it over 3 times. Each team had 16 possessions (kneeldowns excluded).

The big turning point was the second play of the 4th quarter when Lawrence was picked on a deep ball on 3rd-and-1 in a 21-14 game. I guess the Jaguars can’t even trust Travis Etienne to get a yard when they needed it most. Flacco used that short 48-yard field for another touchdown drive. But the Jaguars kept scoring and applying pressure, even coming up short on a 4th-and-3 with 3:30 left. By the time Jacksonville scored with 1:33 left, there was only time for an onside kick in a 31-27 final. They didn’t recover and the game was over.

Fortunately for the Jaguars (8-5), the Colts and Texans lost too. But the Browns are gaining confidence at 8-5 and just may have a quarterback answer in Flacco if you can believe it in 2023.

Buccaneers at Falcons: Baker Mayfield Brings NFC South Race to a Standstill

The Bucs were 1-15 when allowing 20 points under Todd Bowles since 2022, but make that 2-15 and give Baker Mayfield just as many wins doing it as Tom Brady had last year. The Buccaneers (6-7) are currently leading the NFC South as the Falcons and Saints are also 6-7 for the league’s worst division around.

But Baker did pull out a little Brady in this one as the Falcons were generally the better team, but Younghoe Koo missed two field goals he usually makes, and the Tampa defense was opportunistic in intercepting a screen pass and getting a safety to lead 19-10.

But the Falcons rallied to take a late 25-22 lead. Mayfield’s accuracy and decision making looked woeful on the ensuing drive as he looked like he was playing for a touchdown with under 30 seconds left instead of calmly taking the easy plays in a 3-point game with enough time left. But he finally got on track with a huge 3rd-and-10 conversion to Chris Godwin for 32 yards, then two plays later, he found Cade Otton for an 11-yard touchdown with 31 seconds left to take a 29-25 lead.

The Falcons did a solid job using their 2 timeouts to get into range for the win at the Tampa Bay 31 with 4 seconds left. But that last throw absolutely had to be in the end zone on the final play, and for some reason, Desmond Ridder threw short, completing a pass to Drake London for 28 yards to the 3-yard line to end the game. Didn’t understand that decision at all as Ridder had time to throw a little deeper to the end zone.

The Falcons and Bucs have split with each team winning on the road this year. Who is the best team out of Saints, Buccaneers, and Falcons? Damn if I know. The winner of the division should just be a sacrificial lamb to the NFC East runner-up.

Broncos at Chargers: Did We Just Lose Justin Herbert?

That would be something if this turned out to be the final game of the Brandon Staley-Justin Herbert era for the Chargers. Herbert left with a fractured index finger on his throwing hand, which is obviously not good.

It was already shaping up to be a rough start for Herbert, who had a pick at the line that led to a 3-yard touchdown run by Javonte Williams, his first score on the ground in 2 whole years.

Almost fittingly, Herbert was injured on a 4th-and-2 attempt in the second quarter as Staley bypassed a 47-yard field goal. Easton Stick, a 5th-round pick by the team way back in 2019, replaced him for the rest of the game. That was a tough assignment as the Chargers finished 1-for-6 on 4th down thanks to going 0-for-12 on 3rd down.

The Chargers (5-8) are toast, and the Broncos (7-6) are only a game behind the Chiefs (8-5) in the AFC West if you can believe that.

Texans at Jets: The Most Unexpected 300-Yard Passing Game

What a strange game. It always felt like a trap for the Texans, but who could have imagined 11 straight punts and a knee to go to halftime scoreless, then for Zach Wilson to throw for 301 yards in a 24-6 win?

The weather wasn’t as windy as some expected, so it wasn’t the issue. Not when Wilson was able to pass for 301 yards and multiple touchdowns in his first start in weeks. C.J. Stroud, the rookie who entered Week 14 leading the league in passing yards, only passed for 91 yards before he left the game injured in the fourth quarter.

But this was a case of not having your top two wide receivers and tight end while facing a tough pass defense on the road. The Texans already lost Tank Dell for the year, tight end Dalton Schutlz was still out, and Nico Collins left the game early with an injury. Stroud had his hands full and the Texans just did not deliver this afternoon.

But Wilson had his way with the defense as he completed 27-of-36 passes with Garrett Wilson going over 100 yards, and Randall Cobb even caught a touchdown.

Amusingly, the Jets tacked on 3 field goals in the fourth quarter on drives that all lost yardage as they were set up in Houston territory after 4th down stops by the defense. But the damage was done before that point.

Panthers at Saints: The NFC South Is Really This Bad

The passing offense was absolutely grotesque well into the second half of this game:

Derek Carr ended up finishing with 119 yards on 18 completions, taking him out of record territory, but it was still a putrid showing against the NFL’s only 1-win team. Bryce Young also struggled mightily again as he is regressing instead of showing improvement in his rookie season.

The Saints were almost going to win this one with 7 points on offense and the other 7 from a blocked punt return touchdown. But the defense stopped Carolina on a 4th-and-1 in a 14-6 game, then Carr hit a 44-yard completion that was more yardage than he had in the first 50 minutes combined. That drive was finished with a 7-yard touchdown to Chris Olave, then Jimmy Graham later caught a touchdown to blow it open 28-6.

We can talk about the Saints’ struggles on offense, but the Panthers are beyond putrid. There was already that Week 4 game against Minnesota where the Panthers scored 6 points (two field goals) despite holding the ball for 38:29. They came close to that again in this one with 34:50 in time of possession but only a pair of field goals to show for it.

Not only is Young failing to flash signs of improvement, but he’s f’n boring to watch too. Things are a real mess in Carolina right now and it is unlikely a good coach is going to want to take this job in 2024.

Next week: Are we really going to start the week with Easton Stick and Aidan O’Connell? A Saturday triple-header with no must-see games? It has to be Dallas at Buffalo to carry Sunday, because even SNF (Ravens-Jaguars) has lost some luster with the Jaguars on a losing streak. They flexed KC-NE out of MNF for Eagles-Seahawks, but I thought that was a mistake even before this KC losing streak. I much rather see if the Chiefs can avoid losing to Bailey Zappe than to watch another game with fading Seattle (and Philly for that matter) right now.

Unknown's avatar

Published by Scott