Tag Archives: Kansas City Chiefs

Running Teams BeGone

The longer the Raven defense held Buffalo close, the more imminent their victory seemed. 

Throughout the first half, Baltimore’s top-ranked running attack seemed one fingernail away from cracking the big run that would break the game open.  They finished the half with 77 rushing yards, averaging 4.3 per running attempt.  But no touchdowns, as the first half ended in a 3-3 tie.

Now, in the second half, Baltimore seemed poised to break through.  Beginning at their own 25-yard line, Baltimore would drive to the Buffalo 9-yard line in 14 grinding plays – 7 runs (for 31 yards) and 7 passes (5 of 6 completed for 39 yards and a 4-yard sack).

Now there were only 58 seconds left in the quarter.  Baltimore, facing third-and-goal, was one play away from tying this game up.  Quarterback Lamar Jackson followed tight end Mark Andrews with his eyes as Mark settled into a void in Buffalo’s zone defense about three-yards deep into the end zone.  Jackson’s subsequent throw would result in his only touchdown pass of the game.

Unfortunately for him, it wouldn’t be to Andrews – or any other Raven player.

Running Teams Begone

The Divisional Round in the AFC found two of football’s top three running games still in the hunt for the title.  The Ravens – playing in Buffalo on Saturday night – had averaged an astonishing 191.9 rushing yards a game through the regular season.  Their 555 rushing attempts, and their 5.5 yards per rush were also easily the best marks in football.  Their 24 rushing touchdowns ranked third.

Sunday would see the defending champs in Kansas City host the surprising Cleveland Browns.  Now 12-5 after holding off Pittsburgh in the WildCard Round, Cleveland carried the third most potent running attack – averaging 148.4 yards per game.  They ranked fourth in attempts (495) and fifth in both yards per rush (4.8) and rushing touchdowns (21).  Both played their final games of the season over the weekend, with both teams scoring fewer than 20 points.  Baltimore fell to Buffalo, 17-3 (gamebook) (summary), while the Chiefs took down the Browns 22-17 (gamebook) (summary).  Each journey to that result, though, was quite different.

Ravens Done In By an Old Weakness

As I speculated about this game last week, I pointed out that Baltimore wasn’t a long drive team.  They were a big-play running team, every bit as dependent on the big play as Tampa Bay.  Against Buffalo, Baltimore racked up 150 rushing yards – but none of their individual runs struck for more than 19 yards.

As this team still struggles to throw the ball with much effectiveness against the better teams, the more Buffalo forced them to put drives together, the more opportunity it presented for them to take advantage of the inefficiencies in the Baltimore passing attack – an incompletion, a holding penalty, a sack – an interception.

In the pivotal moment of this game, it was that interception that told the tale.

Aware that Jackson had locked onto Andrews, cornerback Taron Johnson dropped his zone a little deeper and edged toward the middle.  His interception and subsequent 101-yard return broke the Ravens’ back, sending them home for the offseason, and sending the Bills into Kansas City with a trip to the Super Bowl on the line.

Lamar’s final passing line of 14 for 24 for 162 yards and the interception pans out to a 61.5 passer rating.  The rating system isn’t perfect, but that number fairly accurately describes Lamar’s afternoon.  Jackson also found himself sacked three times, as Buffalo decided to pressure him.  As opposed to Tennessee in the WildCard round – who sent extra rushers after Jackson just 4 times in the game – Buffalo blitzed him 13 times (a full 43.3% of his drop-backs).

This is still an effective approach as it forces Jackson to recognize protections and hot routes and forces him to speed up his process.  Last Saturday, it was one final lapse in the passing that ended Baltimore’s season.

Valiant in Defeat

The loss is all the more bitter in light of another marvelous performance by Wink Martindale’s defense.  One week after muffling Derrick Henry and Tennessee’s running attack (the Titans were second in the NFL, by the way, at 168.1 rushing yards per game), the Raven defense – with a bit of an assist from the gusting winds – mostly dismantled Josh Allen and his third-ranked passing game.

Josh threw only one touchdown pass of his own, was limited to 206 yards and an 86.1 rating.  During the season, Allen ranked fourth in passer rating at 107.2.  He averaged just 8.96 yards per completion Saturday night, as Baltimore mostly inhaled his deep passing game.  Josh completed just 1 of his 6 passes of more than 20 yards.

Football’s finest receiver (as far as yards and catches go) was still unstoppable.  Stefon Diggs finished with 106 yards on 8 catches.  But Baltimore shut out two of Buffalo’s more important secondary receivers.  Cole Beasley and Gabriel Davis had no catches on a combined 6 targets – Davis drawing especially close coverage.  On the average throw in his direction, Gabriel had a defender 0.8 yards away.

The second-ranked offense by yards, Buffalo managed just 220 yards against Baltimore, scoring just ten points on offense (remember, the other 7 came courtesy of the Bills’ defense).  It was a superior performance, more than worthy of sending the Ravens into the Conference Championship Game.

That will have to be comfort enough for Raven fans between now and next September.

Not the Same Old Browns, But Still . . .

The story in Arrowhead was quite different.  Armed with a potent running attack against a team that has shown some weakness in stopping the run, Cleveland decided not to deploy it.  Straggling into the locker room at the half, the Browns had run the ball just 6 times for 18 yards.  Not coincidentally, Kansas City (which had run the ball 12 times for 60 yards) held a 17:43-12:17 time of possession advantage and a 19-3 lead.  Former Chief Kareem Hunt, who had rushed for 841 yards and caught 38 passes for Cleveland this year, had no touches in the half.

The Browns forged their way back into the contest in the second half, on the strength mostly, of that running game.

Neglected for thirty minutes, Cleveland punched through the KC defense to the tune of 94 second-half rushing yards at a clip of 5.9 yards per carry.  Had they started the game that way, the story might have been different.  As it was, Cleveland began the second half in catch-up mode, and the passing game wasn’t up to the challenge.

Against the 94 rushing yards, Baker Mayfield threw for only 70 yards in the second half – averaging just 3.5 yards per attempted pass and 5.83 yards per completed pass – some of that influenced by a KC game-plan that blitzed Baker on 52.6% of his drop-backs.

As Cleveland’s season ends, and as KC prepares to meet Buffalo, it’s fair to remember how far the Browns have come this year.  Just 6-10 last year, Cleveland is only three years removed from the team that was 0-16 in 2017.  Whether or not they have actually turned a corner is a question that will have to wait for next year.  They still lost both games to Baltimore this year, and the first game to Pittsburgh.  That they beat the Steelers in the season’s final game is more attributable to Pittsburgh resting its starters.  Their conquest of the Steelers in the WildCard round still feels more like a Pittsburgh meltdown than anything that Cleveland did – remember, that game began with the snap sailing over Ben Roethlisberger’s head and things went south from there.

Still, this Cleveland team nearly came all the way back against Kansas City after trailing by 16 points.  But for a heart-breaking fumble through the end zone that eliminated a golden first half scoring opportunity, Cleveland might well be preparing for Buffalo.  This Cleveland franchise will be one to keep an eye on next year.

Of Huntley and Henne

Adding to the intrigue of the Divisional Round games – and possibly to the Championship Game – both Baltimore and Kansas City finished the game (and not by choice) with their backup quarterbacks on the field as both of the league’s last two MVP quarterbacks went out of the game with concussions.

In Buffalo, on the drive that followed the pick six, Jackson had a second-down snap sail over his head.  Lamar chased it down and managed to heave it out of bounds before he was tumbled by Tremaine Edmunds and Trent Murphy.  He landed on his back in the end zone – bouncing his head off the turf.  It was his last play of the season.

Into the breach came Tyler Huntley – a rookie out of Utah who had thrown 5 passes during the regular season.  Tyler was Baltimore’s third back-up quarterback of the year after various difficulties befell Robert Griffin III and Trace McSorley

Tyler wasn’t terrible.  He completed 6 of 13 for 60 yards and ran for another 32.  On Baltimore’s last possession of the season, Tyler drove the team to the Buffalo ten-yard line, where his fourth-down-pass was deflected away by Edmunds.

Honestly, at that point, the absence of Jackson wasn’t much of an issue.  Lamar has never brought a team back from a 14-point deficit, and it’s most unlikely that this would have been the night.  In this game, Jackson’s absence was mostly a footnote.  That wasn’t the case in Kansas City.

Henne-thing’s Possible

About half-way through the third quarter, KC quarterback Patrick Mahomes tried to skirt right end to convert a third-and-one.  He couldn’t get around Mack Wilson, and then struggled to get up after the hit.

And suddenly, the season rested on the shoulders of back-up Chad Henne.

From the hoopla that surrounded the event, one would think that no back-up quarterback in NFL history had ever made a play in a game.  In truth, Chad’s situation wasn’t nearly as dire as the 35-3 deficit that Frank Reich inherited against Houston all those years ago.  Still, there were plays that needed to be made, and Chad made them.

He entered a 19-10 game (KC in front), facing a fourth-and-one.  He would finish this drive and have two more of his own in the fourth quarter.  In this drive, he was on his 48-yard line, still needing quite a few yards to get into field goal range.  This is a drive I will get back to.

On his subsequent possession, Chad threw an interception into the end zone to open the door a crack.  The Chief defense quieted the uprising, forcing a punt that gave the ball back to Henne with 4:09 left in someone’s season – Kansas City clinging to a 22-17 lead.

Here, Chad’s job was to run out the clock.  More than anything else, KC didn’t want to give the ball back to the Browns.  It was during this drive that the legend of Chad Henne was born.

On third-and-four with 3:21 left, Chad completed a five-yard pass to Darrel Williams (whose contributions to this game would equal those of Henne).  Then, on the final play before the two-minute warning, Chad suffered a sack at the hands of Myles Garrett.

Now, it was third-and-fourteen with KC still pretty deep in their own territory (their own 35).  Without a huge play here, Cleveland would be getting the ball back with around a minute left to do something with.  With his receivers covered and the pocket collapsing, Chad Henne pulled the ball down and darted up the left sideline.  As he approached the first-down marker – and with M.J. Stewart closing in – Chad hurled himself, head-first, toward that precious first-down line.

As he slid across that line, the KC sideline (and the fans in the stadium) erupted.  The moment was so galvanizing that it didn’t even matter that the officials marked the ball just short – bringing up fourth-and-inches.  At that point, it only served to add one more memory for Chad – a five-yard, fourth-down completion to Tyreek Hill in the right flat that put a bow on things.

That Final Field Goal

The Chad Henne moment was – without a doubt – the most romantic moment of this round.  He could be even more important in the Championship Game, depending on how things develop with Mahomes – who is in concussion protocol.

But, I keep coming back to that moment when Chad first came into the game – with a fairly critical first down to get.

Talking to the press after the game, coach Andy Reid made a point of the fact that the loss of Mahomes didn’t weaken the knees of his football team at all.  That was evidenced on the fourth-and-one play, when Williams burst around left end for 12 yards to earn the first down with authority.  He shot around the right end for 16 more on the next play (dragging Browns as he went), to pull the ball down to the Cleveland 24.

Four plays later, Harrison Butker kicked the 33-yard field goal that gave them an important buffer.

Williams – who finished with 78 rushing yards and 16 more on pass receptions – spent much of the season – like Henne – deep on the depth chart.  His opportunity in this game came because of the injury to number-one back Clyde Edwards-Helaire.  During the season, he had only 39 carries.

Sung and Unsung

Kansas City has now won 23 of Patrick Mahomes’ last 24 starts.  So much of the attention during this run has gone to the marquee names – Mahomes, Tyreek Hill, Travis Kelce, Chris Jones, etc.  And justifiably so.  These are franchise talents that have combined to vault this team into the elite circles of the NFL.

But just as critical are the contributions of many other players you don’t hear much about.  Demarcus Robinson, Daniel Sorensen, Tanoh Kpassagnon – and now Darrel Williams and Chad Henne.  These guys aren’t the most awe-inspiring talents to dot an NFL roster.  But what they are is play-makers.  I don’t think it’s unfair to say that Kansas City’s roster is deeper in guts than it is in raw talent, but the fact is that the deeper you grind into the playoffs the more important the guts of a team becomes.

There are now four teams left in the tournament.  With most of them, I’m not at all sure how they will respond to the critical moments that will decide these last three games.  But I know how Kansas City will respond.  Someone on this roster will make a play.  It might be a small play to keep a drive going, or pulling a receiver down a yard short of the first-down marker.  It might be a play that the media won’t remember after the game.

But when the money is on the table, you can be sure that someone on this roster – starter or reserve – will make a play.  Buffalo’s challenge is actually greater than It appears on paper.

But, if Patrick can’t go . . .

The NFL Profiles as a Touchdown Pass League

Four teams are left standing – in many ways, very disparate in their approaches to winning.  It’s an interesting blend of strengths and weaknesses that will make, no doubt, for a lively finish.

These four teams do, though, have one commonality that binds them together.  Their quarterbacks get the ball into the end zone.

Looking at the last four quarterbacks standing, we have Aaron Rodgers In Green Bay.  His 48 touchdown passes led the league.  He will be matched this weekend against Tampa Bay’s Tom Brady, who’s 40 touchdown passes ranked him second (tied with Seattle’s Russell Wilson).  The AFC Championship Game will pit Number 4 (KC’s Pat Mahomes – assuming he’s available) against Number 5 (Josh Allen of Buffalo).  Mahomes threw 38 in the regular season, and Allen tossed 37.

Whatever else you do in the NFL – whether you run and stop the run, throw high-percentage, low interception passes, or spend your games dialing up shot plays – the indispensable accessory your team must have if it’s going to make a deep playoff run is that quarterback who gets you into the end zone.

It’s the NFL’s gold standard in the early years of the new decade.

A Time to Refrain from Sliding

There were 57 seconds left in the first half – a 6-6 tie between the Los Angeles Rams and the Seattle Seahawks.  The Rams, out of time outs, faced a third-and-eight on their own 27-yard line.

Abandoning the pocket, Ram quarterback Jared Goff was scrambling towards the first-down that would keep the drive going.  But as he approached the sticks, and linebacker Bobby Wagner closed in, Jared slid to a stop one yard before the marker, setting up a Ram punt.

In the broadcast booth, ex-Dallas quarterback Troy Aikman reviewed the play, and watching Jared slide short, he pointed out that “there’s a time to slide and a time to go for it.”

For some time, now, I have been trying to put my finger on exactly what it was about Jared that was preventing me from truly believing in him.  That play – and the comment by Aikman – helped clarify the thing for me.

The particular play, of course, mattered little.  Even if he had ducked his head and plowed through for the first down, the Rams were still in their own territory with 40-some seconds and no time outs – an unlikely scenario for more scoring.  But of great significance is the revelation that emerged from the moment.

Put into the language of the Proverbs, there is a time to slide, and a time to refrain from sliding.  Jared didn’t slide due to any lack of toughness.  Later in the game, Goff would break his thumb against a helmet, would pop the thumb “back in,” and continue playing.  He slid because he didn’t realize that it was a time to refrain from sliding.

Coach Sean McVay’s system is called “quarterback friendly.”  What that means is that the system defines things very clearly for the quarterback in most situations.  The system features a lot of boots and roll-outs that give Jared a lot of one-key options (if the safety comes in, throw it over his head; if he stays back, throw underneath him).  Usually the game plan features a lot of play action (on average, the Rams run play action about 50% more often than the average offense).  This pulls linebackers in toward the line, widening the gap between the levels of the defense.

(On Sunday afternoon, for some reason, LA got away from its play-action identity, calling it only 9 times.)

When Goff can roll out of his break and see what he is looking for in the secondary, he can be very decisive and very effective.

It also helps that the Rams’ concept is heavy on short passes to receivers with room to add yardage after the catch.  At the beginning of the week, Jared was running football’s fourth shortest passing game – his average completion was to a receiver just 4.8 yards from scrimmage.  But that receiver would then add an average of 6 more yards after the catch (the second highest after-the-catch average in the league).

Jared’s problems come when things don’t go quite according to plan – as happened on this particular scramble.  Jared was caught in-between at the decisive moment.  Go for it? Slide?

When the moment comes too quickly for him, Jared goes with a reaction – a reflex really.  There’s the defender – time to slide.

It was the exact process behind Goff’s worst moment in Los Angeles’ 20-9 loss to Seattle (gamebook) (summary).

The possession before, leading 6-3, the Rams began on their own 14 with 8:37 left before the half.  Ten plays later, LA had moved the ball 47 yards to the Seattle 29, while nursing 5:06 off the clock.

On first-and-ten, the Rams ran play-action.  But Goff was flushed from the pocket and came scrambling out to his right.  As he approached the line of scrimmage and the sideline at about the same time, it was decision time.  Run the ball?  Throw it away?  Try to find a receiver?

There was no time for him to ponder, so Jared reacted.  Downfield he caught a flash of receiver Robert Wood somewhere up the sideline.  He came to a nearly full stop just as he was about to reach the line, thought it over for the briefest of moments before trying to flip the ball up-field to Woods.

The ball fluttered away from the line, where Quandre Diggs closed on it and made the interception.

Defending the Rams

Throughout the game, Seattle was able – in a lot of ways – to speed things up for Jared, putting him in that in-between zone for much of the afternoon.

As their defense has been coming together coming down the stretch, Seattle has been able to generate a significant pass rush with just their down linemen.  Even though the Seahawks sent an extra rusher only 11 times, the pressure on Jared was steady throughout the game.  Goff ended up being sacked 3 times (all in the second half) and hit a total of 9 times – part of 18 pressures that kept pushing him into that in-between zone.

Additionally, they sat on Jared’s short routes, forcing him to look farther up the field.  His average completion in this game was to a receiver 6.75 yards from scrimmage (who then added only 3.00 additional yards after the catch).  It was not an offensive style that the Rams are comfortable in.

Seattle also took away the right sideline – the side that Jared rolls to when he’s in trouble.  Jared was just 5 of 13 (38.5%) when throwing to the right side of the field for 70 yards and that one interception.

It was a nuanced game-plan from an opponent that understands Jared’s strengths and weaknesses very well.

Is this fixable?  I’m not sure.  None of his issues have anything to do with what Jared knows or what he has or hasn’t been coached to do.  It’s that moment when his instincts take over that he gets into trouble.  And I’m not sure what to do about a quarterback’s instincts.

Missed Opportunities

The interception caused at least a three-point swing – if not a ten-point swing – as Seattle turned the mistake into a field goal (remember that the Rams were within field goal range at the time).  It was one of three Ram drives that lasted at least 5 minutes.  They scored a total of 3 points off of those drives.

On their first possession of the second half, LA drove 69 yards on 12 plays in a drive that lasted 7:17.  It brought them to first-and-goal from the 2.

From there they ran on four straight plays, being turned away each time.  Would one of those downs have been a good opportunity for a play-action pass?  Possibly.  But I find I can’t argue with a coach who wants to run the ball right at them in that situation.  It is axiomatic in football that if you can’t get one yard when you really need it (especially when you take four shots at it), that you don’t really deserve to win.

In the Rams’ case last Sunday afternoon, they couldn’t, and they didn’t.

Not How You Start

One of the game’s most instinctual quarterbacks played for the other team.  That would be Russell Wilson.  Long regarded as one of the better deep throwers in the game, Wilson missed that deep shot several times in the first half.  Harassed himself by the Ram front four, Wilson went into the locker at the half with that 6-6 tie, and little production to show for the first 30 minutes.  Wilson was 10-of-19 (52.6%) for only 84 yards.

On the first third-down of the second half, Russell rolled out and lofted a 45-yard beauty up the right sideline to David Moore.  It led to the game’s first touchdown, and sparked a second half in which Wilson completed 10 of 13 (76.9%) for 141 yards (10.85 yards per attempted pass).

The Seahawks look a lot better as they head into the playoffs than they did last year (and this win clinched the division title for them).  This year, their defense looks to be a strength (you couldn’t say that last year) and they have healthy running backs (remember last year that all of their running backs were injured).

And, of course, they have Russell Wilson.  Seattle looks like they will be a tough out.

A Time to Throw Long

In Week 11, the Pittsburgh Steelers went to 10-0 with a relatively easy 27-3 conquest of Jacksonville.  At that point, it looked like the AFC would be coming down to Pittsburgh and Kansas City.

Ten games into the season, the Steelers were scoring 29.8 points a game, never scoring fewer than 24 in any one game.  Defensively, they were allowing just 17.4 points per game.  Offensively, they were football’s fourth highest-scoring team, while the defense led all of football in fewest points allowed.  They also ranked fourth in total yardage given up (third against the pass).  The 71.8 passer rating against them was the lowest in football.  They also led all defenses in sacks (38) and sack rate (9.9%).

Utilizing a new quick-pass offensive style, 38-year-old quarterback Ben Roethlisberger was sustaining a 101.4 passer rating, while being sacked just 10 times (only 2.6% of his drop-backs).  Things couldn’t have gone much better for the Steelers to that point.

All of that changed with their Week 12 game against the Baltimore Ravens – this was the game that was postponed about three times and finally played with about half of the Ravens on the COVID list.  Pittsburgh squeaked to a 19-14 win, but things wouldn’t be the same thereafter.  The Steelers lost the next three games, scoring 17 points against Washington, 15 against Buffalo, and – shockingly – just 17 against Cincinnati.  (The defense served up a total of 76 points during that stretch, as well – over the four games just preceding, Pittsburgh had surrendered a total of 46 points).

During this offensive brown-out, Pittsburgh converted just 11 of 41 third downs, and their running game – never among the league’s best – completely disappeared.  Through ten games, they were averaging 102.2 rushing yards a game and 3.9 yards per carry (both figures below the league averages).  During the losing streak, they managed just 51.3 rushing yards a game and just 2.9 per carry.

As for Ben and the short passing game, teams had begun to sink their coverages securely around all the quick-opening underneath routes.  His completion percentage dropped from 67.1% to 57.8%, his per-pass average fell from 6.67 yards to 5.17 yards, his yards per completion went from 9.9 to 8.9, and his touchdown percentage fell from 6.3 to 3.9.  Meanwhile his interception percentage rose from 1.3 to 3.1.  During the losing streak, Roethlisberger’s touchdown-to-interception ratio was a struggling 5-4, and his passer rating sat at 71.8 – exactly what Pittsburgh’s defense had held opposing passers to over those first ten games.  Add in a case of the drops that his receivers suffered through (and during one three-game stretch Ben had 14 of his passes dropped) and you have a picture of an offense in a bit of a crisis.

Clearly, it was time to change things up.  Defenses would now have to be loosened up, or they would smother the life out of the Steelers.

With the division title there for the taking, Pittsburgh welcomed the 10-4 Indianapolis Colts into Heinz Field for a critical Week 16 matchup rife with playoff implications.  Certainly, the message of the past few weeks had registered.  It was time to throw the ball long.

But for thirty horrific minutes against the Colts, things just snowballed.  Roethlisberger completed only 11 of 20 through that first half for but 98 yards.  The rushing attack accounted for just 4 yards on seven rushes – none of them gaining more than 2 yards.

Indianapolis trotted off the field at the half having outgained the Steelers 217-93, and their 21-7 halftime lead was only marred by a short-field touchdown allowed.  Pittsburgh’s defense had briefly risen to the moment, striping the ball away from Indianapolis quarterback Philip Rivers in the early moments of the second quarter.  The recovery was advanced to the Indy 3-yard line – about as far as the Steeler offense could sustain a drive.

In the aftermath of Pittsburgh’s surprising 28-24 comeback victory (gamebook) (summary), the questions posed to Ben and to head coach Mike Tomlin wondered why they waited till the second half to throw the ball up the field.  The answer, of course, was that they didn’t.  The deep strike had been a part of the game plan from the beginning, but throughout the first two quarters they just couldn’t connect with the big play.

One, in particular, worth remembering came with 14 seconds left in the half.  Diontae Johnson flew up the right sideline, and Ben let it go for him.  But Johnson veered his route back toward the middle, while Roethlisberger’s throw continued up the sideline.  In the locker room at the half, the two got together and compared notes on the play.

Say this for the Steelers and Tomlin their coach.  Through all of this, there was no panic.  They knew that they just needed to hit on one of those plays to dispel the dark clouds and get a little momentum going.

And so it was, with 3:23 left in the third quarter and the Steelers now down 24-7, that Johnson flew up that same right sideline and Roethlisberger lofted that same pass.  This time, however, Johnson’s route hugged that sideline.  He finally caught up with the pass at about the point he was crossing the goal line.  In the signature moment of the comeback, Diontae laid out for the throw.  Responsible for 13 drops this season, this time Johnson reeled in the big one, and the rally was on.

During the rousing second half, Ben completed 23 of his last 29 passes (79.3%) for 244 yards and 3 touchdowns.  He completed 3 passes of more than 20 yards up-field.  In addition to the 39-yard strike to Johnson, Ben completed a 34-yarder to Chase Claypool and the rally capping 25-yard touchdown toss to JuJu Smith-Schuster.  That throw – with 7:38 left in the contest – gave Pittsburgh it’s only lead of the afternoon – the only one they would need.  The one that produced the 28-24 final.

Ben entered the contest running the NFL’s third-shortest passing game.  His average completion was only 4.5 yards from the line of scrimmage.  On Sunday, his average completion was 6.09 yards from scrimmage – which is about the league average.  The quick pass was still very much a part of the offense – in fact, 84% of Ben’s throws (including all three touchdown passes) were out of his hand in less than 2.5 seconds.  Coming into the game, only 75% of his throws were out of his hand that quickly.

The difference on Sunday was how well the passing game did when Ben did hold the ball for more than 2.5 seconds.  Through the first 14 games of the season, Ben’s passer rating when he held the ball was a disappointing 63.5.  Last Sunday, he was 6-for-7 for 88 yards when taking more than 2.5 seconds.

Going Forward

It was certainly a relief for the Steeler organization to break through a little bit like this.  It’s probably premature, though, to assume that their struggles are over.  The pass offense in general will profit from this slight change in emphasis.  There is nothing like hitting a few deep throws to get the defense to back off and open up some underneath routes.  The running game, though, is still a mess.  Pittsburgh came out of the Colt contest with all of 20 rushing yards and a 1.4 yard average per carry.  Colt running back Jonathan Taylor had almost that many on one carry (he broke off an 18-yard run in their first possession of the second half).

Until they fix their running game, I don’t believe in the Steelers’ ability to run the table in the playoffs.  As opposed to last year, very few of the teams likely to make the playoffs are run-dependent teams.  But almost all of them – especially the ones that are most likely to bring home the hardware – have a legitimate running game that they can turn to whenever they need to.  Pittsburgh does not.  At some point during the playoffs that is almost certainly going to bring them down.

The Disappearance of the Colt Running Game

After running the ball 20 times in the first half, Indianapolis ran just 8 times in the second.  After controlling the clock for 18:17 of the first half, they held the ball for just 14:11 thereafter, adding fuel to the Pittsburgh comeback.

In the post-game, questions were asked about the disappearance of the running attack.  Coach Frank Reich informed the press that they had more runs called, but they checked out of them when the Steelers showed certain pressures.  Elaborating on the situation, Rivers offered that the Colts had called running plays from formations with three wide-receivers on the field.  The intent was that Pittsburgh would remove a linebacker in favor of a defensive back and open up some running space.  But according to Philip, Pittsburgh stayed with their base personnel, and Indy chose not to run against that front seven without significant numbers of big people on the field to block them.

They weren’t asked why they didn’t run more large-package formations (two or three tight ends, for example) and try to keep the running game going.

A Time to Refrain from Throwing Long

Matt Ryan’s season has been opposite – in many ways – from Ben Roethlisberger’s season.  Record, of course, is an obvious point of comparison.  Pittsburgh took the field against Indy carrying an 11-3 record.  As Ryan’s Atlanta Falcons took the field in Kansas City to play the reigning world champions, they sported a 4-10 record.

But more than record separates these two veteran quarterbacks – the very styles of their passing attacks are strikingly different.  Where Roethlisberger has spent almost the entire season throwing short, quick passes, Ryan’s attack has been one of football’s most up-field attacks.  Going into last Sunday’s contest against the Chiefs, Matt was second in the league in air yards per pass thrown.  His average target was 8.8 yards from scrimmage.  He led the entire NFL in air yards per completed pass, with his average completion occurring 7.5 yards from scrimmage.

Some of this is certainly game-situation related.  The Falcons have been behind a lot this year.  But mostly this is an organization that believes that if you have a quarterback with a strong arm and top-shelf receivers like Julio Jones (who missed this game), Calvin Ridley and Russell Gage, then your offense should be doing more than dumping screen passes to running backs.

And so Ryan has taken his shots up the field.  Targeted 68 times, Jones has been an average of 11.2 yards from scrimmage for every pass thrown in his direction.  Ridley’s average is 15.1 yards away for each of his 131 targets.  Another receiver (who also didn’t play last Sunday) Olamide Zaccheaus has been targeted 32 times this year at an average distance of 13.8 yards upfield.

Against Kansas City, you could make the argument that this mind-set should continue, the assumption being that with the Chief scoring machine on the other sideline, your own offense should be all about the points – as many as possible as quickly as possible.

The problem was that the game’s biggest statistical mismatch was Patrick Mahomes and the Kansas City passing attack (ranked first in the NFL) against the Falcon passing defense (ranked second to last).  The Chiefs ranked above average to well above average in every significant passing statistic – including passer rating, where Mahomes ranked third at 110.6.  The Falcon defense ranked below average to well below average in every significant passing statistic – including passer rating, where their 103.2 ranked fifth-worst.  These numbers suggest that for the Falcons – or anyone, really – to try to bomb it out with the Chiefs – trying to match them touchdown pass for touchdown pass – is mostly like bringing a butter knife to a gun fight.

So, Atlanta tried a different approach.  While coaches Raheem Morris and Jeff Ulbrich fashioned a daring defensive game plan that worked better than it had any right to, offensive coordinator Dirk Koetter played complimentary football.  The offensive objective was to control the clock, keep Mahomes and his receivers on the sideline – hopefully at the end of the day denying them a possession on two.  So Atlanta ran the ball as much as they legitimately could (which turned out to be 23 rushes).

And they went to the short passing game.

In contrast to the offense run most of the season, Matt and the Falcons went all Ben Roethlisberger on the Chiefs.  Of Matt’s 35 passes, only 3 were at targets more than 20 yards from scrimmage.  With two of his top wide-receivers on the shelf, Matt dropped the ball off liberally to his tight ends and running backs.  Eighteen of his passes went to that grouping.  Ridley still provided the occasional long threat (he was an average of 15.0 yards downfield on his 9 targets), but Gage became another check-down option.  Targeted 5 times, Russell finished with 4 catches for 23 yards – his average depth of target being just 1.4 yards.

For the game, Matt’s average target was 6.51 yards from scrimmage – still higher than average, but more than two yards shorter than normal.  To this point of the season, the Falcons were averaging only 4.0 yards after the catch.  Against KC they averaged 5.56.  In fact, in the final analysis, Ryan’s 300-yard passing game broke exactly evenly between yards in the air (150) and yards after the catch (also 150).

The results were as much as Atlanta could have hoped for.  Matt completed 10 of 12 (83.3%) in the first half for 129 yards (10.75 per attempted pass).  For the game, he completed 77.1% of his passes (27 of 35), tossed a couple of touchdowns, and finished with a 121.1 passer rating against a very good pass defense.

This in spite of the fact that he was blitzed almost half of the time (19 of his 39 drop-backs), was sacked 4 times and hit 12 times on the day.  The Falcons finished with only 14 points, but did so while controlling the clock (33:12) and limiting KC’s possessions (they had 10 instead of the normal 12 or 13).

It was a very gritty offensive performance that gave this team a legitimate shot at the upset.

A Time to Blitz

Two, of course, can play at the blitzing game, and Atlanta returned the favor by coming after Mahomes.  They came after him with an extra rusher 39.1% of the time (18 blitzes in 46 drop-backs) and played aggressive man-coverage behind.  Much of the success of the plan – and it did succeed – came, I think, from the surprise factor.  It was probably the last thing that KC expected.

Few teams challenge the athleticism of the KC receivers.  And few teams come after Mahomes.  Over the course of the season coming into that game, Patrick was seeing blitzes only 20.2% of the time – mostly because he is one of football’s best at picking apart teams that blitz him.

In the postgame, Patrick owned that he missed checking into some protections and didn’t find the hot routes that he usually does.  As much as anything else, I believe that had to do with the surprise of the Atlanta game plan.  Patrick was rarely hit or hurried as the line did its usual excellent job of picking up the blitz.  Mahomes wasn’t sacked.  But his timing was visibly effected.

Patrick ended his afternoon with a pedestrian 79.5 passer rating – his lowest of the season.  His final line showed him below the NFL average in all of the passing categories, except yards per completion.  As you might expect against a defense that featured a heavy dose of blitz, there were some big plays hit, and Patrick did pick up 278 yards on his 24 completions (11.58 per).

All things considered, though, on both sides of the ball the Falcons delivered a surprising effort against arguably football’s best team.  It was almost enough to secure them the victory.

In Their Grasp

The game deciding sequence began with just 2:07 left in the contest.  Trailing 14-10, the Chiefs faced first-and-ten on the Atlanta 25.  Mahomes went for it all, lofting a pass for Tyreek Hill in the middle of the end zone down the right sideline.

Just in front of him, a leaping AJ Terrell, in a breath-taking show of athleticism, soared above Hill’s head and latched onto the ball at its highest point, pulling down the interception that would almost certainly end Kansas City’s long winning streak.  Except that as he landed in the end zone, the impact jarred the ball out of his grasp.

You knew what would happen then.

On the very next play, Damarcus Robinson shook free of Kendall Sheffield (who had no safety help) to gather in the 25-yard pass that put the Chiefs back in front 17-14.

Atlanta still had 1:55 of clock left and two time outs.  And true to their plucky nature, back came the Falcons.  Ryan completed three quick passes to bring Atlanta to the KC 28 yard line with a minute left.  Later, an offsides penalty put the Falcons on the Chief 21-yard line, first-and-five, 27 seconds left – Atlanta still with two timeouts.

Three incomplete passes later, now with 14 seconds left, Atlanta brought out Pro-Bowl kicker Younghoe Koo – riding a streak of 27 consecutive field goals – to give them a tie and send the game into overtime.

And, of course, he missed – the kick fluttering wide to the right.  And with that, Kansas City’s amazing streak continues (gamebook) (summary).  The Chiefs have now won 10 in a row, 14 of 15 for the season, and 23 of their last 24.

For all of that, though, there is a strong sense that this is a Kansas City team that’s winning on guile, guts and a fair amount of luck.  Of their ten straight wins, the last seven have all been one-score games (and four of those have been decided by a field goal).  This list includes excellent teams like New Orleans and Tampa Bay, but also includes several that you would think should be more easily subdued – Carolina, Denver and, of course, Atlanta.  They are now winning games that they probably should lose.

That’s all well and good, but I have this unshakeable feeling that a tough-luck loss is coming for them.  I absolutely concur that this is football’s best team, but even the best team loses from time to time.  At this point, that loss could well interrupt their playoff run.  If that loss comes.

Once More Into the Breach

Meanwhile, the nightmare season for the Falcons now has only one more game to go.  After yet another galling loss to a team on its way to the playoffs, Atlanta now gets a second helping of Tom Brady and the Buccaneers.  I am not even going to attempt to recap all the woulda-shoulda-couldas of the Falcons’ season – the number of late leads lost, the number of near victories – at this point its water under the bridge.

I will say this, though.  This last game against Tampa Bay, I believe, has become very important for this franchise – perhaps even more than it is to the Bucs.  After everything they’ve been through, getting one more shot at Brady, one more chance to prove themselves against a playoff team – one last chance before the season ends to close out a team – all of these things will be enormous for this franchise.

The Proverb says that to everything there is a season.  For the Falcons, though, that season will have to be next season.

These Old Guys Don’t Go Down Easy

Tom Brady and Drew Brees have been doing this for a long time.

They are a combined 84 years old, with Brees turning 42 during the playoffs.  They have combined for 41 seasons (counting this one) and 581 starts at the most critical position in their sport.  They have thrown a combined 21,023 passes, completing 13,831 of them (65.8%) for 158,303 yards and 1,141 touchdowns.

They went back and forth for a while this season for the all-time lead in touchdown passes.  With Brees missing the last four weeks with some broken ribs, Tom has earned himself a little separation from Drew.  Brady’s lead in all-time touchdown passes currently sites at 573-568.

These, by the way, are just regular season numbers.  The playoffs are worthy of a chapter of their own.

And then, last Sunday, both of these all-time greats trailed at one point in their games by a combined 31-0.  The games, of course, didn’t end that way.

Brees and His Near Comback

The decision to activate and then start Brees was made rather late in the week.  Up until Wednesday, or so, everyone was expecting another Taysom Hill start.  After missing four weeks, Drew was going to be a little rusty, anyway (and, perhaps, limited reps in practice might have amplified that).  Under the best of circumstances, Kansas City is a difficult team to line up against.

While the offense gets all the ink, Kansas City’s defense has been much more than on-lookers – especially the pass defense.  They might, in fact, be the best defense in the NFL that nobody talks about.  The Chiefs entered the game allowing completions on only 62.4% of the passes thrown against them – football’s third-best figure.  Moreover, they came into the game having made 15 interceptions, and restricting opposing passers to just an 84.2 rating.  This was the fourth best defensive rating in the NFL.

It would be unfair to attribute New Orleans’ slow start completely to rust on Brees’ part.  The Chief defense played very well.  But whatever the balance between rust and tight defense, the game couldn’t have started much worse for Drew and the Saints.  He started off missing on his first 6 passes (including an interception), and New Orleans went three-and-out on its first four possessions (if you include the possession that ended with the interception – which was thrown on third down).

The interception led to a short field (setting up one touchdown), and KC put together an 11-play, 80-yard, 5 minute and 1 second drive for a second touchdown.  In the early moments of the second quarter the Chiefs were ahead 14-0 and looking like they would leave New Orleans in the dust.

Even when Brees did begin to complete some passes, what evolved was a very different New Orleans game plan than we are used to seeing.  Instead of the precision, sideline-to-sideline short passing game, Drew’s attack was decidedly vertical.  Six of his 33 passes (one of his 34 passes was a throw-away) travelled more than 20 air-yards from scrimmage, and 4 others were more than ten yards.  Of his 15 completions, 4 were more than 15 yards upfield.

Accounting for the Change

Drew began the week running the second shortest passing game in the NFL – his average target being just 5.4 yards from the line.  On Sunday, his average target was 8 yards beyond the line of scrimmage (the NFL average is 7.81).  Why the difference?  It could be a combination of several factors.

In his post-game press conference, Drew blamed himself for not taking check-downs, so some of it was due – perhaps – to rusty decision making.  I believe, though, that there was more to it.  Psychologically, when you fall behind 14-0 to a team as dangerous as Kansas City, there must be some anxiety to score quickly to get back into the game .  I also think – especially with Michael Thomas out of the lineup in order to heal for the playoffs – that there was some focus by Kansas City on the short routes, almost as though the Chiefs might dare Brees to beat them over the top.

Whatever the underlying causes, the results were quite uncharacteristic.  Drew finished with an uncharacteristically low completion percentage (44.1 on 15 of 34) and an uncharacteristically low passer rating (84.7).  On the other hand, he also finished with an uncharacteristically high 15.6 yards per completion.  He finished with a very characteristic 3 touchdown passes.

He needed, perhaps, one more possession to bring New Orleans all the way back.  As it was, they fell in a thriller to the Chiefs, 32-29 (gamebook) (summary).

Saints’ Defense Better than the Score Indicates

Kansas City’s final offensive tallies included the 32 points, 411 yards of offense and 34 first downs.  Not the kind of numbers to suggest that the defense played all that well.  In this case, the numbers are less than descriptive of how the game played out.  The New Orleans defense came into the game with significant credentials as well.  At the start of the week, they ranked second in overall defense, second against the run and fourth against the pass.

Cognizant that even they couldn’t deny everything to the KC offense, New Orleans chose to allow the run in an effort to mitigate the aerial light show that quarterback Patrick Mahomes usually conducts with his quiver of speedy receivers.  So Kansas City’s running numbers were gaudy – 179 yards on 41 attempts.  But the elite passing attack was controlled (to a great degree).

As you might expect, Mahomes entered the game ranked in the top five in almost every passing category – including passer rating, where his 112.3 ranked second in all of football.  In that context, Patrick’s 26 for 47, 254 yard performance seemed pedestrian, indeed.  He competed just 55.3% of his passes (13.1% lower than his season average), averaged just 5.4 yards per pass attempt (3.07 below his season average) and 9.77 yards per completion (2.63 below his average).  He recorded no completions of longer than 23 yards, which he managed just twice, for his only passing plays of twenty-or-more yards.

His 92.0 passer rating was 20.3 points below his season average, and he only managed that because – being Patrick Mahomes – he still managed to toss three touchdown passes without having one intercepted.

The prescriptions for containing both of these skilled passing attacks were virtually identical: Heavy pass rush pressure from the front four, and tight coverage in the secondary.  Neither team blitzed much at all.  Mahomes saw an extra rusher just 7 times, and the Chiefs sent extra men at Brees only 5 times.  But the pressure from the down linemen and the coverage were impressive by both sides. 

Patrick was sacked 4 times as part of being hit 11 times while having 8 passes batted away by a defender.  Drew took only one sack, but was also hit 7 times while having 9 passes defended.  Brees’ wide receivers and tight ends managed an average of just 1.99 yards of separation (according to Next Gen stats) – a number which speaks to the impact that losing Thomas has on the rest of the team.

In fact, if there was one number that most expressed the difference between these two teams last Sunday, it might be the third-down tallies.

With their running game keeping them in manageable third downs, Kansas City finished 9-for-18 in those opportunities.  With their running game mostly abandoned (and New Orleans ran the ball only 17 times) and Drew’s passes falling incomplete much of the time, the Saints spent the afternoon in a lot of third and longs.  They finished 1-for-11 on that down.

This led to Kansas City running 92 plays and controlling the ball for 41:14 of the game.  The Saints just couldn’t stay on the field.  Their longest possession of the afternoon lasted just 2:40, and they finished with 7 three-and-outs (again, including the interception possession).

Encouragement in Defeat

Of all the teams that have lost to Kansas City this year (and that has been almost all of them), I believe that New Orleans can be most encouraged by their near miss.  They were playing with a quarterback rusty from the IR, playing without their best pass receiver, falling behind early by two touchdowns, and playing all of the fourth quarter without their best defensive lineman (Cameron Jordan got himself ejected).  And, for all of that, fell just one possession short.

Given the chance for a re-match (which could only happen in the Super Bowl), New Orleans must be convinced that they can play with this team.  Whether they can overcome the Mahomes magic, though, is another question.

That is the question that ultimately bedevils the entire league.

Brady’s Day

Tom Brady’s afternoon in Atlanta could have hardly started worse.  The downtrodden Atlanta Falcons hit them with a perfect half.  They converted 6 of 10 third downs, committed no penalties, no turnovers and suffered no sacks.  They rolled up a 261-60 advantage in total yards, a 16-5 advantage in first downs and took a 17-0 lead into the locker room at the half.

As opposed to the defenses in the Saint-Chief game, the word of the day for both defenses in this game was blitz and blitz some more.  Both teams blitzed at almost exactly the same rate.  Atlanta came after Brady 43.8% of the time (21 of 48 drop-backs), and Tampa Bay responded by sending extra rushers after Matt Ryan 43.4% of the time (23 blitzes in 53 drop backs).

In the first half, the story was Brady under siege and Atlanta keeping the rush away from Ryan.  In the second half, some protection adjustments gave Tom more time in the pocket, and allowed him to fully exploit the coverage difficulties that the Falcons have suffered with the entire season.

In the second half alone, Brady completed 21 of 29 passes (72.4%) for 320 yards.  Think for a moment about throwing for 320 yards in one half.

Brady average 11.03 yards per pass attempt in that half, and 15.24 per pass completion.  He also tossed a couple of touchdown passes as he conjured a few memories (bitter for the Falcon fans, to be sure) of the Falcons’ Super Bowl loss to New England.  The Patriots (er, I mean Buccaneers) came all the way back for a 31-27 victory (gamebook) (summary).

Playoff Consequences

Two surprising Week 15 upsets juggled the playoff situations a bit.  The Rams’ loss to the Jets caused some minor movement in the NFC.  That loss by LA, gives Tampa Bay an open opportunity to claim the fifth seed, dropping the Rams to sixth.  The two teams currently hold identical 9-5 records, with the Rams holding the head-to-head tie breaker.

But Tampa Bay’s closing schedule is Detroit and Atlanta again (very winnable games), the Rams finish with Seattle and Arizona.  If the Bucs win out and LA stubs its toe just once, the two teams will switch positions.

More Upheaval in the AFC

The other big upset was Cincinnati eclipsing Pittsburgh.  In absorbing their third loss in a row, the onetime presumptive first seed In the conference will now likely fall to third.  Pittsburgh and Buffalo now hold identical 11-3 records, with the Bills holding the tie breaker by virtue of their win over the Steelers last week.

And, finally, the Cleveland Browns got that one win that they needed to put themselves in the playoff driver’s seat when they beat the Giants on Sunday night.  Cleveland is now 10-4, Baltimore is 9-5 and Miami is also 9-5.  The Ravens hold the tie-breaker with the Browns (season sweep), and close with an easy schedule (they finish with the Giants and Bengals.)  Cleveland would have to win both of their games to stay ahead of the Ravens.  This week they have the Jets (who will come in enthused off their victory) and they finish with Pittsburgh, so I still think it likely that Baltimore will finish ahead of Cleveland (they will get the fifth seed).

So the Cleveland win now makes the Dolphins vulnerable. The Dolphins are a game behind the Browns and finish on the road in Las Vegas and Buffalo.  Miami’s playoff fate may depend on whether Buffalo needs to win that final game or not – and from the looks of things right now, I will guess that they will need that game.

If Cleveland does, in fact, get in, they will probably claim the sixth seed.  They have an earlier victory over Indianapolis, so the Colts could very well finish 11-5 this season and be relegated to the seventh seed.

The Quarterback Kvetching Society

The old saying goes that the quarterback always gets too much credit when his team wins, and too much blame when it doesn’t.  My experience confirms this.  Even so, complaining about your quarterback is one of our basic constitutional rights that we sometimes take for granted.

2020 (different in a lot of ways from other years) is also distinct for the amount of criticism attached to “made” quarterbacks.  Throughout history, there have been some of these great field generals that have elevated themselves to the point where they are (usually) considered immune from the harping that lesser quarterbacks are subjected to.  Can you imagine any in the football universe openly caviling Johnny Unitas or Joe Montana?  Didn’t think so.

And yet, this year some resumed signal callers have been called out, publicly by their coaches as well as by the fandom in general.  The discussion of “what’s wrong with Tom Brady” has turned into a season-long polemic that has abated only slightly with Tampa Bay finally winning a game.  Brady, of course, is history’s most decorated quarterback – the numbers of Super Bowls, awards and records need not be recounted here.  In earlier posts (here is one) we’ve tried to take an objective look at the swirl of chatter around (arguably) the finest quarterback of this generation.

Of the up-comers, Jared Goff of the Rams – who led them to a Super Bowl a few years ago – has also taken some gentle flack from his head coach – and we looked as his efforts in an earlier post as well.

But of all these decorated quarterbacks, none has been under the constant assault that New England’s Cam Newton has been subjected to.  A former MVP, Newton – as you must surely recall – led the Carolina Panthers to the Super Bowl on the heels of a nearly undefeated season (they were 15-1) just 5 years ago.  When he signed on as Brady’s replacement, it was widely assumed that cam would lead that franchise back to glory.  Yes he is 31 now, and has had some injuries.  But Cam was Lamar Jackson before Lamar Jackson – and he still carried some of that Superman mystique that defined his earlier success in Carolina.

It hasn’t exactly been plug-and-play for Cam in Foxboro.  He was benched for Jarrett Stidham in the fourth quarter of last Thursday’s 24-3 loss to the Los Angeles Rams (gamebook) (summary).  Cam’s numbers were as sluggish as the entire Patriot offense looked during that effort.  Newton was 9 for 16 for 119 yards.  He threw 1 interception while throwing no touchdowns (obviously).  His passer rating of 53.9 was only his fourth worst of the season.  On the season, he is having 3.3% of his passes intercepted (which would tie his career high if it stays there) while only tossing touchdowns on 1.7% of his passes (he has never been below 3.7% in any full season of his career).

I can’t speak for the entire internet, but pretty much everywhere I’ve looked the word in the web is that he’s done.  In the press conference after the game, the press circled coach Bill Belichick like so many vultures demanding to know why he was still sticking with Newton (“What has he shown you to warrant your confidence?” and other such questions).  Obviously, the press covering the Patriots is tired of Cam and are already clamoring for Stidham.

By the way, Belichick’s press conferences – which have always been pained affairs – have taken on a distinctly funerary overtone these days, with Bill looking positively embalmed on Thursday night.

It is somewhat ironic that I am defending Newton – and I mostly will.  If you search the Cam Newton tags on my site, you will find some posts where I delve into the things that have prevented him from becoming the enduring star that he could (here is one, there are others).  But as with Brady and Goff, I believe that his critics are short-sighted, and that he has become the lightening rod for a lot of issues that New England’s offense is struggling with.

This is not to say that Cam is blameless.  His lack of discipline and hit-and-miss mechanics are still underpinning his inconsistencies.  Football reference (in the summary I linked to above) charged him with 4 “bad throws” – so one out of every four passes didn’t go where Cam would have intended.  Those would include his last two throws before being benched.  Damiere Byrd and James White both had a little separation, but the throws were off the mark.  Of course, New England was already down 24-3 at that point, so . . .

But Newton also averaged 13.22 yards per pass completion, and three of his nine completions accounted for at least 25 yards – with two of them moving the ball 30 or more yards downfield.  His 9 completions traveled an average of 9.7 yards in the air – the highest such average of any quarterback last week.  And this against a pass defense that came into the game ranked first in both fewest yards allowed per pass (6.05) and fewest yards per completion (9.7).

In all honesty, when you look at Cam on film, he doesn’t look all that different than he did in his glory days with the Panthers – he is still the same blend of sometimes dazzling talent and sometimes maddening disappointment.  The big difference in the Newton of today and the Newton of yesteryear is the support system around him.  Cam is, in fact, struggling with the same issues that made Tom Brady look old last year – lack of pass protection, and lack of playmakers to throw the ball to.

You may not be aware, but Brady led all of football in 2019 in throwing away passes – he unloaded 40 of them last year – 9 more than Aaron Rodgers’ 31.  The bulk of these involved Tom just getting the ball out of his hand to avoid taking a sack.  Newton is less committed to avoiding sacks, and so is throwing away fewer passes (only 8 so far).  He is, consequently, getting sacked more (on 7.1% of his drop backs, so far this year).  But he is operating under the same duress that Brady encountered last year.

In 22 drop backs against the Rams, Newton was sacked 4 times and knocked down 3 others as Los Angeles hit him 10 times and forced 2 scrambles.  He was hurried on a couple of other occasions.

And then, of course, there are the receivers.  Between injured reserve and COVID-19, Julian Edelman has missed the least 7 games.  Of the pass catchers that were available, only Byrd showed any consistent ability to gain separation.  Damiere averaged 3.7 yards of separation on the 8 passes thrown in his direction.  Cam’s other receiving options (Jakobi Meyers, N’Keal Harry and Devin Asiasi) combined averaged just 1.52 yards of separation.

Regardless of your expectation for Newton, this is not a formula for success.  Few quarterbacks could thrive in this circumstance.  Belichick is the last head coach you can imagine that will give in to the whinging of the press and the internet, so it’s doubtful that he will give the offense to Jarrett.  Bill – while certainly not content with Cam’s performance – realizes that his situation is challenging.  So Newton will keep getting his opportunity to work through these things.

It is doubtful that his treatment by the press will be equally fair.

The Rams Roll On

As to the Rams, their formula against the Patriots was an extension of the plan they ran against Arizona the Sunday before.  Lots of running and lots of short passes.

They finished with 36 rushing plays that accounted for 186 yards (5.2 per).  While the New England Cam (Newton) endured a frustrating night, Los Angeles’ Cam (Cam Akers) was having a breakthrough performance.  The Rams’ rookie running back slashed through the Patriot defense for 171 of those yards (on 29 carries).  Of those 171 yards, 112 came before contact, as the LA offensive line owned the contest.

And the passing continues to be exceedingly short.  Goff’s average target was only 4.6 yards away from the line of scrimmage (Week 14’s third shortest range passing attack).  Of the 24 passes he actually threw to a receiver (he threw one of his 25 passes away), 20 of them were less than ten yards from scrimmage.

Jared finished with just 137 passing yards for the night, but only threw 7 passes in the second half, as the Rams ran on 23 of 31 second half snaps.

And that is a formula for success.

Kansas City Also Rolls On

One place they aren’t kvetching over their quarterback play is Kansas City, where they Chiefs won again.  Once again, they spotted their opponent (this time the Miami Dolphins) a 10-0 lead, but had pulled back in front 14-10 by halftime, on their way to a 33-27 conquest (gamebook) (summary).  The Chiefs have now won 12 of 13 this season, and 21 of their last 22 (including playoffs).

But this time the quarterback play wasn’t as clean and pristine as usual.  Patrick Mahomes was sacked 3 times (one of them for a 30-yard loss, which I understand is a record) and tossed 3 interceptions in a 4-turnover day for Kansas City.

Forty-four games into his young career, this was only the second time that Mahomes had thrown 3 picks in a game.  The only other time was that epic showdown with the Rams in Week 11 of 2018.  Los Angeles won that one 54-51, and Patrick threw 6 touchdown passes to go along with his interceptions.

That was, in fact, the last regular-season game in which Patrick threw more than one interception (he did, you’ll recall, throw 2 in last year’s Super Bowl).  So that snapped his streak of 31 consecutive regular season games without throwing multiple interceptions.

Mahomes finished the game 24-of-34 for 393 yards and 2 touchdowns (a 91.9 rating) after a torrid second half in which he completed 11 of his final 15 passes for 221 yards.  That equates to 14.73 yards per attempted pass, and 20.09 yards per completion.

How to Beat the Chiefs

So here was the pattern – very reminiscent of their playoff journey.  They look bad early.  Sacks, fumbles (Mahomes also fumbled during the game, but KC recovered it), drops – interceptions.  Suddenly, its 10-0 bad guys (or, Dolphins, in this case).

Then one good thing happens for the Chiefs – one big play.  This time Tyreek Hill on a running play scooted 32 yards for a touchdown.  One big play, and the Chiefs exploded.

Counting that drive, the Chiefs scored touchdowns on three of four drives in not quite a quarter’s worth of playing time.  This first drive began with 10:14 left in the second quarter, and the fourth drive ended with 13:50 left in the third.  All together, the four drives required just 19 plays while accounting for 204 yards (10.7 yards per play).  They consumed a total of 7 minutes 11 seconds, and included – in addition to the big run by Hill – a 21-yard pass to Travis Kelce, a 26-yard pass up the sideline to running back Clyde Edwards-Helaire, and a picture perfect, 44-yard deep strike to Hill running behind the secondary.

Toss in a 67-yard punt return for a touchdown by Mecole Hardman after Miami’s next posession, and the dynamic Kansas City offense and special teams tossed up 28 points in 10:30 of football time. (The Dolphins, by the way, entered the game allowing the second fewest points in the NFL – not that that matters to Kansas City).

So, this suggests a strategy.

Don’t give up that first big play!

Knowing that this is football’s most momentum-phillic offense, don’t allow the play that swings the momentum to their side.  This is roughly equivalent to telling a pitcher that the way to stop the Dodger hitting attack is to simply not make any mistakes with any of his pitches – and, as pieces of advice go,  just as practical.

So seriously, how do you go about slowing this team?  Well, that’s the million-dollar question, isn’t it?  In this space, I will sometimes speculate about things I might try against various offenses if I were the defensive coordinator charged with concocting a game plan.

To date, I don’t have a comprehensive answer for the Chiefs.  I wouldn’t take the deep-zone approach designed to prevent the big play.  Kansas City is one of the few offenses that can consistently drive the field taking all the short and intermediate throws that you give them.  And, frankly, the teams that take that approach against them usually give up the big play, anyway.  I would opt for man coverage.

Ideally, you would like to double everybody.  In practice, that’s impossible.  But I would double-cover Hill, and I would literally mug Kelce at the line – even walking a defensive lineman out over him in an attempt to disrupt him.

But the basic approach would be pressure.  A vigorous, relentless pass rush will stop any passing attack.  Here, though, is the rub.  You have to get that pass rush from just your four down linemen.  If you blitz him, Mahomes will destroy you.

It is, to say the least, a conundrum.

Miami Trending Down

After a 1-3 start, the Dolphins suddenly caught fire.  They won five in a row, including splash wins against the 49ers, Rams and Cardinals.  In addition to the surprisingly stingy defense, Miami featured the franchise quarterback that they had drafted in the first round of the most recent draft (that would be Tua Tagovailoa) and a certain knack for finding a way to win games that they looked like they should have lost.  They also received outstanding special teams play.

Over the last month or so, gravity seems to have caught up with them a bit.  They have split their last 4 games, with their other loss coming against the Denver Broncos.  Through his first three starts, Tua posted a passer rating of 104.9, throwing 5 touchdowns against no interceptions.  In losing two of this last three, Tua’s rating has slipped to 88.3 as his completion percentage has dropped to 60.8%.

Sunday against KC, Tagovailoa was just 28-for-48 for 316 yards and 2 touchdowns to weigh against his first career interception – an 83.3 rating.  He was also sacked 4 times (the Broncos got him 6 times).

He was just 5-for-12 for 80 yards in the 10-to-20 yard range.

However it plays out in the end, this has been a welcome resurgence season for the Dolphins.  But, over the last few games and heading into a tough finishing stretch (Miami closes with New England, Las Vegas and Buffalo), their youth has been starting to show.

Turning a Corner in Tampa Bay?

There was 5:22 left in the second quarter as the Tampa Bay Buccaneers broke the huddle.  They were facing a first-and-ten on their own 34-yard line.  To that point, Tampa Bay had just been taking it – offensively and defensively – as they trailed the world champion Kansas City Chiefs by a 17-0 count.  The Chiefs had already scored 3 touchdowns.  The Tampa Bay offense had earned 3 first downs (they received a fourth on a penalty), and had 3 three-and-outs.

For a team eating a lot of frustration over not living up to their offensive potential – and on the heels of disastrous efforts against New Orleans and the Rams – this was another nightmare a-brewing.  To this point, quarterback Tom Brady was in the midst of another mediocre outing.  He had completed only 8 of this first 14 passes for just 51 yards (3.64 yards per pass).  His rating – at that moment – was a disappointing 64.9.

But at that moment, Brady’s old friend and fellow ex-Patriot Rob Gronkowski slipped in behind the Kansas City defense to pull in a 29-yard pass – and all of a sudden everything was better.  On the next play, Brady tossed a swing pass into the left flat for running back Ronald Jones.  Jones (who has dropped a few this season) caught this one and squirted up the sideline for the final 37 yards for the touchdown that brought Tampa Bay back into the game.  After picking up just 51 yards on his first 14 passes, Tom achieved 66 yards on the next two.

Beginning with the pass to Gronk, the Buc offense began to resemble the dangerous downfield attack that coach Bruce Arians envisioned when he invited Brady to leave New England for the warmer climes of southern(ish) Florida.  Brady finished his evening hitting on 19 of his last 27 passes for 294 yards (10.89 yards per attempted pass and 15.5 yards per pass completion).  He would add 3 touchdown passes into the mix.

Tampa Bay didn’t pull off the victory.  After falling into a 17-point hole, they spent the rest of the game in trail mode.  But they did pull close, bringing the final score to 27-24 (gamebook) (summary).

With three straight losses, Tampa Bay falls to 7-5.  A distressing situation for a team that had painted themselves as Super Bowl contenders – but the situation isn’t desperate.  The Bucs are still currently holding onto the sixth playoff spot in their conference, and the schedule will ease as the season winds down.  After their bye this week, they will draw Minnesota (5-6), Detroit (4-7) and Atlanta (4-7) twice.

But these will not be walk-over games.  The Vikings have not given up on making the playoffs and have been playing desperate football ever since their choppy beginning.  Atlanta is still a very dangerous team (ask the Raiders).  This makes these last four games – in one sense – the defining moments of the Buccaneers’ season.  In another sense, that moment has passed.  Losing any of their final four games will only invite continuing questions about the character of this team, while winning games they will be expected to win won’t add appreciably to their luster.

Even in the comeback against KC, all the flaws that have been present in Arians’ team continued to present themselves.  As with so many teams that are enamored with throwing the ball, there is little run commitment in Tampa Bay.  The Bucs ran the ball 6 times in the first half – one of those a Brady kneel-down, and just 7 times in the second half.  While the KC run defense has been better the last several weeks, this is still a team that entered the weekend allowing 133.5 rushing yards per game, and 4.6 yards per rush. 

That Tampa Bay didn’t even truly attempt to exploit this potential weakness is one thing.  That they couldn’t connect running the ball to controlling the clock and keeping the Kansas City offense – which was crucifying their defense – on the sideline is rather typical of Tampa Bay’s approach to football.

Is my defense having a tough time of it?  They seem to be.  Too bad.  We’re going to throw the ball.  They’ll have to figure it out.

The impact on the offense is what it usually turns out to be.  With no running game to respect, Kansas City blitzed shamelessly.  The Chiefs blitz fairly often anyway (36.6% of the time).  On Sunday, they ramped it up against the Bucs.  Brady saw 18 blitzes on his 42 drop-backs –an aggressive 42.9 percent of the time.  The result of a scheme that has the quarterback always looking to throw long, combined with an offensive line that has issues with protection and a defense that is dialing up blitz after blitz with no regard for the run is pretty predictable.

That quarterback is going to get hit.  He’s going to get hit hard, and he’s going to get hit a lot.  Again, this doesn’t seem to matter to the coaching staff.  When that quarterback throws interceptions – and Brady added two more to his ledger on Sunday – the fingers point to him.  On the first interception, the Chiefs had a free rusher bearing down on him.  He was hit squarely and fully in the ribs as he was throwing the second.

Again, that’s too bad.  But the Bucs are going to keep doing what they do, and Brady – or whatever other quarterback is standing back there absorbing the punishment – is just going to have to complete those passes, anyway.  That, apparently, is the job.

There were some hopeful signs coming from the Tampa Bay offense over the last 35 minutes of the game.  But the shortcomings are still there.  And their failure to win any of their last three games against other potential playoff teams will hang over this team until they get another such opportunity.

And Then There’s the Defense

As frustrating as the afternoon was for the Tampa Bay offense, the defense continued to be pushed around by high octane offenses – especially this season by the Saints and now the Chiefs.

Kansas City had an almost record-setting start to the game.  While Brady and the Tampa Bay offense were still in their funk, Kansas City’s Patrick Mahomes and his deep-threat receiver Tyreek Hill were lighting things up.

Mahomes threw for 359 yards and 2 touchdowns.  That was the first half.  Hill caught passes for 210 yards.  Again, that was the first half.  Like New Orleans, the Chiefs exploited the chink in Tampa Bay’s defensive armor – their inability to generate a consistent pass rush unless they blitz.  And so, Tampa Bay blitzes as aggressively as almost any team in football.  Coming into the game, they were tied for second in the NFL with Baltimore, blitzing on 41.9% of passing downs.

But against Kansas City, they couldn’t blitz as Mahomes and company are deadly when defenses send extra rushers.  In the 95 times that Patrick has been blitzed so far this year (according to football reference), he has completed 60 of 89 passes for 840 yards, 11 touchdowns and no interceptions.  His passer rating is higher on these throws (137.2) than when he is not blitzed (109.3).  He has also been sacked only 3 times and forced to scramble on 3 other occasions.

So Todd Bowles and his defense backed off.  On his 53 drop-backs, Patrick saw only 9 blitzes (17%), leaving the secondary behind to endure a very long afternoon.

In the short run, things will get easier – schedule-wise – for the Bucs.  But these are issues that will haunt them during the playoffs.  Barring a surprising reversal in the playoffs, it looks like Tampa Bay will end their season with at least as many questions as answers.

Time to Take the Raiders Seriously?

Six weeks ago – out of the blue – the Las Vegas Raiders beat the defending World Champion Kansas City Chiefs.  It was easy to dismiss at the time.

Kansas City (at the time) had won 13 in a row (counting playoffs), and nobody wins them all (KC has since won five more consecutive games since that loss – so they are now 18 of their last 19).

As for the Raiders, it was hard to think of them as true contenders.  They had just lost their previous two games – yielding 66 points in the process.  In fact, when you add in the 32 that Kansas City scored in the loss (it was a 40-32 Raider win), and the 45 points that Tampa Bay laid on them the next week, then you are looking at a Raider team that allowed 30 or more points five times in their first six games in a 3-3 start to the season.  Clearly that surprise win against the Chiefs was just “one of those games” and nothing to be overly impressed with.

But after being slapped around by Tampa Bay, Las Vegas went on a little three-game winning streak.  It wasn’t an overly impressive array of teams they beat (Cleveland, the Chargers and Denver) but it did inflate their record to 6-3 as they prepared for last Sunday Night’s rematch against Kansas City.

Surely the Chiefs – remembering their Week Five defeat – would show up with their A game and avenge their only loss in over a year in a big way.  Surely the defending champs would expose their hated division rival.

And so, when quarterback Derek Carr completed a 12-play, 75-yard drive with a one-yard bullet to Jason Witten in the near-right corner of the end zone to give Las Vegas a 31-28 lead with 1:43 left in the game, I started to do some re-assessment.

It is, perhaps, time to take the Raiders seriously.

Vegas didn’t win the game.  One hundred and three seconds with a time out is far too much time to leave Patrick Mahomes, who, as is his habit, drove Kansas City 75 yards in just 1:15, winning the game, 35-31, with a 22 yard toss to a wide open Travis Kelce with 28 ticks left (gamebook) (summary).  But even in defeat Jon Gruden’s Raiders made their statement.

This is still a team with shortcomings – especially on the defensive side.  And, in fact, I still don’t see them as a playoff team (an early-season loss to Buffalo will probably be the tie-breaking game that allows the Bills in and keeps the Raiders out).  But this team is clearly building itself to compete with football’s best team (arguably).  Even in defeat, Las Vegas pushed the KC defense to the edge.  They converted 6 of 9 third downs, and scored touchdowns on 4 of 5 red zone trips.

More impressively, they almost completely broke down the Chief pass defense – which had been one of the best in the NFL.  Entering the week, opposing passers were only earning 6.64 yards per attempted pass with an 11-9 touchdown to interception ratio.  While the NFL average passer rating sits at 94.5, KC opponents were only managing an 81.4 rating – football’s fourth lowest.

But for all of the gaudy statistics, Kansas City’s pass defense is sometimes held back by a mediocre pass rush.  Nineteen quarterback sacks in their first 9 games isn’t anything to get excited over.  It was a flaw that the Raiders took full advantage of.

Carr’s first two passes of the night went for 26 and 29 yards – the first against man coverage and the second against a zone.  Both times the Chiefs’ four-man rush applied insignificant pressure.  It set the tone for the night.  In general Derek was presented with a comfortably clean pocket.  He wasn’t sacked, was hurried only a few times, scrambled just twice and averaged 3.05 seconds in the pocket.  Last week, only two quarterbacks spent more time sitting in the pocket and surveying defenses.

The time and comfort allowed Carr and his receivers to exploit both the gaps in the Chief zone (especially with TE Darren Waller) and the difficulties that the KC cornerbacks (Charvarius Ward and Bashaud Breeland) have holding up in man coverage – especially with little pass rush pressure.

Waller (7 catches for 88 yards) and wideout Nelson Agholor (6 catches for 88 yards) were the primary beneficiaries.  Agholor was the one who spent most of the evening lining up against Breeland.

The Chiefs did mix in some blitzes – and managed to get occasional pressure when they sent extra rushers.  But even that tactic mostly failed as the extra pressure couldn’t compensate for a compromised secondary.  Carr’s first touchdown pass, for example – a 17-yarder to Agholor – came when Kansas City sent six rushers after Derek.  But the blitz was picked up.  Waller ran a vertical of his own from the left slot that he turned toward the middle of the field – drawing Tyrann Mathieu with him.  This left Breeland all alone against Agholor, who simply sprinted past him and gathered in the throw in the back corner of the end zone.

Sometimes the blitz was self-defeating.  With the Raiders facing a second-and-nine on their own 33 with 2 minutes left in the first half, the Chiefs sent five rushers, and with Josh Jacobs whiffing on blitzing linebacker Ben Niemann, Neimann came free enough to flush Carr from the pocket.

As Derek pulled the ball down and started to sprint up the middle, Mathieu dropped his coverage on Waller (who was running a crossing pattern, right-to-left across the field) and turned to make a play on the scrambling quarterback.  The problem was that Tyrann a) dropped his coverage before Carr had reached the line of scrimmage, and b) was directly in front of Derek when he stopped running and turned toward the line.  Waller kept running. Carr noted this and tossed him the ball when he was wide open up the left sideline.  That play gained 18 yards.

More than a few times, KC sent six rushers and tried to play zone behind it with just five defenders.  That almost never worked out, as Derek dumped short passes into the voids in coverage, allowing his receivers more yards after the catch than they normally get.  Carr finished the contest with more of his passing yards after the catch (155) than air yards before the catch (120).

The game plan was as well executed as it was well conceived.  Sometimes Carr doesn’t get the recognition due him for the accuracy of his passes.  Derek was 23 for 31 in the game.  Two of those were throw aways, and of his 6 other incompletions, 3 were drops.  So Carr was catchably accurate on 26 of his 29 throws.

Of course, a clean pocket has a lot to do with that.

This is a weakness of the Chiefs that hasn’t really hurt them so far this year.  The league’s top scoring offense frequently takes the anxiety out of playing defense – for Kansas City.  The Chiefs have allowed an opposing passer a rating of 100 points or better only three times this year – and two of those were the Raiders (126.5 in Week Five and 119.7 last Sunday).

In the end it was too much Mahomes.  Patrick rebounded from a mediocre first half (an 82.4 rating) to shoot out the lights I the second half.  He completed 20 of his last 24 passes (83.3%) for 203 yards and that game-winning touchdown pass with less than half a minute to go.  His second half rating was 115.8.

Gruden and the Raiders still have some work to do.  But they have clearly given notice.

Some Good KC Defensive Notes

While the pass defense got pushed around more than usual, the KC run defense seems to be turning the corner.  In their Week Five loss, Las Vegas bludgeoned them on the ground to the tune of 144 yards on 35 carries – including 2 rushing touchdowns.  Kansas City, in fact, was scorched for more than 100 rushing yards in all of its first five games, and six times in the first seven. At that point, they were serving up 149.9 rushing yards per game and 4.9 yards per carry.

But beginning with the game against the Jets in Week Eight, the run defense has tightened up considerably.  The last three opponents (Jets, Panthers and Raiders) have averaged only 95.3 rushing yards per game, and just 3.8 yards a carry.

The Jets, of course, are not among football’s top running teams, but the Panthers rank fifteenth and the Raiders rank seventh in rushing, entering the game averaging 139.2 yards per game.

But on Sunday evening – while the passing game was having its way – the Kansas City defense muffled the Raiders best attempts to establish a running attack.  Las Vegas finished the game with just 89 ground yards on 26 attempts (3.4 yards per).

One of the pillars of this defensive resurgence is interior lineman Derrick Nnadi.  The Raiders found it nearly impossible to get under him with their double-teams.

The game was still a 7-7 contest with 4:01 left in the first.  The Raiders faced first-and-ten on their own 40.  They called a run designed to burst off right guard, but there was no movement on the line as Nnadi withstood Brandon Parker and Gabe Jackson to deny the play.

Now, with 8:41 left in the second quarter, Las Vegas was again in a first-and-ten, this time on the Kansas City 32 yard line.  Game was tied again at 14.  Now Derrick was absorbing blocks from the other side of the line from both Rodney Hudson and Denzelle Good.  That allowed Willie Gay to flow cleanly from the second level to fill the intended hole off left guard. Running back Devontae Booker tried to cut the run to the left sideline, but was corralled by Tanoh Kpassagnon – who had defeated the attempted block of Witten.

And so it went.

Derrick’s biggest play of the evening, though, was a stop he made on first-and-goal from the 1-yard line.  There was 2:10 left in the game, and KC was clinging at this point to a 28-24 lead.  Nnadi imploded the entire middle of the line, blowing right under Hudson (who had his arm wrapped around his neck, by the way).  Jacobs was supposed to leap over the pile for the score, but by the time the pile reached him, it was too far to leap.

Two plays later, Las Vegas scored anyway on the touchdown pass to Witten.  Typical, as it turned out.  For most of the contest, the passing attack came to the rescue of the running game.

It’s encouraging progress.  But the Chiefs are still going to need more pass rush from their front four – maybe by as early as this week when they face Tampa Bay.

Losing their Balance, But Not the Game

The kick, of course, never really had a chance.

With 2 seconds left in Carolina’s contest against the Kansas City Chiefs, placekicker Joey Slye lined up a 67-yard field goal.  If successful, the kick would bring the ten point underdog Panthers an improbable 34-33 victory over the reigning world champions.

As a rookie in 2019, Slye had made 8 of 11 over 50 yards, but none longer than 55.  So far this season, including an attempted 51-yarder that had hit the left upright earlier in the game, Joey was 0-for-3 over 50 yards.  That, of course, was just chatter.  A field goal of 67 yards had never been achieved – and it wouldn’t be on this night.  Joey’s kick was way off to the right.  It was never close.

And the defending champions escaped again, 33-31 (gamebook) (summary).  That the game was as close as it was was due in part because of the desperate play of the Panthers, trying to stem their then-three-game losing streak and stay relevant in the playoff race; in part because of the return of running back Christian McCaffrey; and, significantly, in part because the Chiefs strayed from their game plan – again.

For his entire career, head coach Andy Reid has had an uncomfortable relationship with the running game.  It cost him profoundly in Philadelphia.  The 2004 season – the first time Andy went to the Super Bowl – is a ready example.

The Eagles were 13-3 that season and their offense featured Pro Bowlers Donovan McNabb (the quarterback), Terrell Owens (the featured wide out) and running back Brian Westbrook.  In the 15 games that he started, McNabb threw the ball 469 times.  As a team, the Eagles attempted 547 passes (the ninth most in the NFL).  Owens caught 77 passes for 1200 yards and 14 touchdowns (and he missed a couple of games with an injury).  But Westbrook finished with only 812 rushing yards, getting just 13.6 carries per game.  He had almost as many receiving yards (703) as he did rushing yards.

When they ran the ball, Philadelphia averaged 4.4 yards a rush – the tenth best total in football.  They just didn’t do it.  They finished thirty-first in rushing attempts and twenty-fourth in rushing yards.

They had moments where they loved the running game.  They had four separate regular season games in which they ran for more than 140 yards, and then dominated Atlanta in the Championship Game with 156 rushing yards on 33 attempts.

But that run commitment was gone by the time they reached the Super Bowl.  In their 24-21 loss to New England they ran just 17 times for 45 yards as McNabb tried, unsuccessfully, to pass them to a victory.  Donovan threw the ball 51 times in that game, throwing 3 interceptions and finishing with a 75.4 rating.

Something in Andy Reid chafes when a running play gains only a yard or two.  Usually, the running game works early or it’s set aside.

During last year’s Super Bowl run, Reid seemed to embrace the running game as never before.  One could almost argue that it was the difference in the Super Bowl.  After running for 118 and 112 yards against Houston and Tennessee, the Chiefs added 129 rushing yards on 29 carries against San Francisco, on a day when the 49ers were making life difficult for Mahomes.

When Kansas City expended their first-round draft choice on running back Clyde Edwards-Helaire, the football world wondered if this meant the re-birth of the running game in Kansas City.  It did.  For about three games.

In victories over Houston, the Chargers and Baltimore, Kansas City ran an average of 29 times a game for an average of 141 rushing yards.  The balance also lifted the passing game, with Patrick throwing for 9 touchdowns in those games and holding a 114.3 rating.  With the exception of a surprising 245 yard rushing day against Buffalo in Week Six, Kansas City has mostly gotten away from the running attack.  In their Week Five loss to the Raiders, they ran just 20 times for 80 yards while attempting 46 passes.

Against Carolina, Kansas City ran on their first two offensive plays.  It’s very likely that the game plan against the Panthers would have been run-heavy.  Through their first eight games, Carolina had been fairly tough against the pass.  They came in allowing just 6.64 yard per pass attempt (fifth in the league) including just 9.6 yards per completed pass – the NFL’s lowest figure.  They had also allowed just 9 touchdown passes.

But run defense had been as enduring issue.  Seven of their first eight opponents had run for at least 117 yards against them, and they were yielding 124.9 rushing yards per game – at 4.7 yards per rush attempt.  The 12 rushing touchdowns they had allowed already in 2020 ranked them thirtieth in that department.  By any measure, Carolina presented themselves as an inviting target for Kansas City’s running attack.

But, the Panthers had scored a touchdown on their opening drive, and the first two running plays had netted just 2 yards, so that was enough of that.  Mahomes threw on 8 of the next 9 plays, leading the Chiefs to a field goal.

Once the Panthers answered that field goal with another touchdown, there was obviously no time to fool around with the running game.  Mahomes led them to another field goal with a six-play drive that was all passing.  This was part of a sequence of ten straight passing plays for Kansas City until Edwards-Helaire would pick up a first down with a 7-yard run on second-and-three with a little more than 6 minutes left in the half.  It was the fourth and final Kansas City run of the half – a half which ended with them trailing 17-13.

Getting the ball first in the third quarter, KC ran on two of their first three plays (possibly having reminded themselves of the game plan?).  Those runs garnered 4 yards each.  Not enough.  That drive ended with four consecutive pass plays.

The next time they possessed the ball, they scored on a 59-yard, 5-play touchdown drive.  The drive was 4 passes and a gadget running play (Tyreek Hill sprinted around left end on the jet sweep for 8 yards).

Once they finally got the lead back (20-17) their next offensive play was a run – for no gain.  And so it was back to the pass.  And so it went.

With 1:52 left in the game, Kansas City took over on the Carolina 42 after a failed onside kick attempt.  The Chiefs were clinging to their 33-31 lead, and Carolina still had all of their time outs.  Surely, you would think, the Chiefs would take the air out of the ball here and try to at least burn through the Panther time outs.  And they did.  For one play.

On a day when the Chiefs ran only 11 times (and one of those a Mahomes scramble), and never called back-to-back running plays after the first two plays of the game, Kansas City ran once, for no yards, and turned back to the pass.

It worked out about the same, in this instance.  Mahomes was sacked, causing the Panthers to call their second time out, and then a short completion brought the third before KC punted away.

By game’s end, the Panthers had controlled the ball for 38:01, finally possessing the ball on their own 9 with 1:26 left, needing only a field goal to win.

The Chiefs are one of the few teams that can get away with this.  Even with no run game for support, and an exhausted defense that surrendered more yards and points than usual (the Chiefs were yet another team that lost the yardage war but won the game last Sunday), Patrick Mahomes and that passing game was still equal to the moment.  Patrick finished 30 of 45 for 372 yards and 4 touchdowns without an interception – a 121.7 rating.

For most teams, this is not a formula for success.  The Rams (another team that sometimes forgets that they are a running team first) have lost a few games this year when they have lost their balance.  On Sunday night, Tampa Bay set an All-Time record when they ran the ball only 5 times all game (one of those a kneel-down).  They got their lunch handed to them.

But Kansas City can do this and get away with it.  Sometimes.

Still, it’s a tendency to keep an eye on.

Derrick Brown

While never thoroughly challenged, the few time that KC did run the ball, the Panther’s run defense did respond well.  KC’s 11 runs included a scramble and the jet sweep from Hill.  Of the nine (yes, there were only nine) actual running attempts by running backs, the Chiefs gained just 22 yards.  Six of the nine runs managed less than four yards.

In the middle of what action there was, was Carolina’s first-round draft choice, defensive lineman Derrick Brown.  He was mostly unmovable – especially holding his ground well against Kansas City’s attempted double-teams.  The principle beneficiary here was linebacker Shaq Thompson, who had to deal with little traffic from offensive linemen and had ample opportunity to fill the holes as they opened.

Whether Carolina could have sustained this over the course of the game is something that we can’t know.  The Chiefs made no real effort to wear them down.  But to the extent that he was challenged, Carolina’s first-round draft choice acquitted himself well.

Bills Surprised by KC Running Attack

My question, after digesting the film, is was this the plan from the beginning?  Or was it the mist?

Last Monday night, the game that should have been the Thursday night game between Kansas City and Buffalo was finally contested.  The game-time temperature was a nippy 51 degrees and the cardboard patrons were treated to a fine mist.  This would develop into a light but fairly steady rain as the game progressed.  But I think the teams had more trouble with the mist.

With the game’s first possession, Buffalo and their quarterback Josh Allen threw the ball three times – all incomplete as the slippery football seemed to sail on Josh.

On the succeeding possession, Kansas City’s All-Everything quarterback Patrick Mahomes also threw three times.  He completed one for a short 8-yard gain, while having the other two slide off target.  But they also ran the ball 5 times during that drive (counting a scramble from Mahomes).  The running plays gained 25 yards and 2 first downs.

They finished the first quarter with 56 rushing yards on only 6 attempts, but that didn’t convince them quite yet.

Then, on the first play of their first possession of the second quarter, Mahomes fumbled the snap.  He recovered the slippery ball, and completed two passes to turn a second-and-11 into a first down.  It was at this point – apparently – that coach Andy Reid must have observed to himself that the running game had worked pretty well.  Maybe, until the conditions soften a bit, it would be a good idea to string together a few running plays.

And so they did.  In a very un-Andy like sequence, the Chiefs ran on six consecutive downs.  They gained at least 5 yards on each run, and totaled 46 yards on the six plays. That brought them to Buffalo’s 10-yard line, where 2 passes later KC was in the end zone for the second time and possessors of a 13-10 lead (after the extra-point sailed wide right).

Thereafter, the Chiefs didn’t exactly take the ball out of Patrick’s hands.  He still threw his passes – and threw them very well.  But from that point on, the running game became focal point of the attack.  By halftime Kansas City had authored 15 runs – amassing 117 yards.  Entering the contest, KC was averaging 119.4 rushing yards per game.

But they were only getting started.  The second half would see the sometimes pass-happy Chiefs add 31 more running plays for an additional 128 bruising yards.  By the time Mahomes took the game’s final kneel-down, the Kansas City Chiefs had drubbed the Buffalo defense into abject submission.  They finished with 245 rushing yards on 46 soul sucking carries as they outfought the Bills 26-17 (gamebook) (summary).

The center piece of the onslaught, of course, was rookie running back Clyde Edwards-Helaire.  He accounted for 161 of the yards (on 26 carries) – averaging 6.2 yards a carry.  It was the second 100-yard game of his short career, and vaulted him to second in the NFL in rush yards so far for 2020.

Make no mistake about it, Edwards-Helaire is a gifted runner.  He spun out of a few tackles and put a nifty juke on Buffalo safety Jordan Poyer to turn what would have been about a 15-yard run into a game-high 31 yard burst.  Clyde ran very well.

But the stars that night were the members of the offensive line – a surprising occurrence, considering their condition.

When KC opened the season against Houston in mid-September, the offensive line starters were Eric Fisher (LT), Kelechi Osemele (LG), Austin Reiter (C), Andrew Wylie (RG) and Mitchell Schwartz (RT).  When Schwartz went down with a back injury on the last play of that first series, he became the third member of that starting five to require a replacement.  Mike Remmers – already in the lineup replacing Osemele at left guard – slid over to take Schwartz’ tackle spot, leaving left guard to an unknown second year player with just 8 career snaps with the offense.  This was, of course, 2019’s seventh-round draft pick, Nick Allegretti.  The third new face on the line belonged to center Daniel Kilgore.  He would be making his first start as a Chief, but had started 56 over the previous 8 years with San Francisco and Miami.  He had been a fifth-round pick of the 49ers back in 2011.

All things considered, it seemed an unlikely enough group to dominate a game, but they absolutely did.  For the 46 running plays, Kansas City backs averaged 3.0 yards before contact – the NFL average is 2.4. While they all played well, the standouts were the two newest guys, Allegretti and especially Kilgore.

It was these two – along with Wylie – who formed a kind of moving shield during Edwards-Helaire’s 31-yard run, as they swept Buffalo’s Quinton Jefferson and rising superstar Tremaine Edmunds before them.  Later, with 13:31 left in the game and the Chiefs facing a first-and-10 on their own 47, Kilgore and Allegretti fired out on a double-team block on Ed Oliver (who has seen enough of those two to last him a while now).  The run was designed to go up the middle, but Buffalo’s Edmunds had anticipated the hole and was moving to fill it even as Nick and Daniel were opening it up.

Seeing what was developing, Kilgore left Oliver to Allegretti and slid quickly over to knock Tremaine out of the way.  Allegretti finished up the block on Oliver – pancaking him to the turf.  The run was only 5 yards, but was an apt example of how these replacement linemen played as though they had been doing this together for a decade.

It was like this the whole game.  Kansas City’s mostly unheralded offensive line beat Buffalo to a pulp.  Certainly an encouraging note for the Chiefs, who should at least get Reiter back next week with Schwartz listed as questionable.

Issue for Buffalo

For the Bills, the aftermath might be a little more unsettling.  Last year’s club finished tenth in the league against the run – giving just 103.1 yards per game (although that season featured a similar meltdown when they allowed 218 rush yards in a 31-13 loss to Philadelphia).  This year’s team took the field against the Chiefs allowing a not-so-bad average of 108.6 rush yards per game – and that after allowing 139 to the Titans the week before.  Run defense has not been thought to be a special problem in Buffalo.

But my enduring memory from this game is how small the Bills front seven looked on the field against the Chiefs.  Oliver, Jefferson, Justin Zimmer and Vernon Butler (who is listed at 330) were easily handled – and frequently manhandled – by KC’s makeshift line.  The defensive ends – especially Jerry Hughes and A.J. Epenesa are pass rushers who put up little resistance to the running game. Darryl Johnson and Mario Addison aren’t notably better.

Of the two linebackers that played Monday night, Edmunds seems to have the physicality necessary, but is still fooled too often.  On several plays, influenced by KC’s misdirection, Tremaine found himself shooting into the wrong hole.  Meanwhile, the other linebacker, A.J. Klein seemed, frankly, to be targeted by the Chiefs.  After the first quarter or so it seems that they ran exclusively to his side of the formation, where all of the aforementioned offensive linemen took turns pushing him out of the way.

None of the secondary – especially Cameron Lewis (who plays the hybrid linebacker position) or Poyer (who – as the strong safety – often plays down in the box) showed any particular vigor in tackling.

This might turn into an Achilles Heel for this team.  It will be interesting to see if any of their future opponents challenge this aspect of their defense.

Of course, it could also be that they were just taken by surprise.  I mean, hey, if I had told you before the game that KC would run 46 times and throw just 26 times, you would have asked me to take a drug test, right?

In the end, you have to feel a little sorry for the Bills – and a little concerned for the rest of the defenses in the NFL.  Here they went and constructed a game plan that they hoped would limit the big passing plays only to watch the Chiefs run the ball right down their throats.

Slowing the Chiefs

In their three wins in last year’s playoffs, all three of their opponents held the high-scoring Kansas City offense down – for a while.  By the final whistle, though, the talented Chiefs’ offense had prevailed, scoring 51, 35 and 31 points – the last two games against two of the NFL’s best defenses.

During the 2019 regular season, though, the NFL’s fifth-most prolific scoring team was held below 30 points in 9 of their 16 games, proving that slowing down the Kansas City offense is possible.

Thus far in 2020, KC ranks eighth in scoring, and has been denied 30 points twice in the first four games.  Two games in particular have showcased the NFL’s very best efforts to restrict the irresistible force that is the Kansas City offense.  In Week Two, the Chiefs trailed 17-9 against the Chargers after three quarters before coming back to claim a 23-20 overtime win (summary).  Then, last Monday they were scuffling to a 6-3 lead over New England with less than a minute left in the third quarter before eventually pulling away for a 26-10 win (gamebook) (summary).

The two approaches differed greatly, but they represent the two best proven remedies for a quarterback with no weaknesses in his game.  You have to beat the rest of his team.

Pressure from LA

What the Charger defense does best is come after the passer.  They have yet to harvest many sacks (only 6 in four games), but they are tied for fourth in the league in QB pressures with 45.  With defensive linemen Joey Bosa and Jerry Tillery leading the way, KC quarterback Patrick Mahomes saw some form of direct harassment on 23 of his 47 passing attempts.  This doesn’t count the times he was forced out of the pocket.

It remains one of the age old truisms of football.  No quarterback can beat you when he’s flat on his back.  The trickiest aspect of this approach is that the pressure has to come from no more than four rushers.  The Chargers are blessed with dynamic linemen that can disrupt almost any passing attack.  But you have to do it with four.  Once you start blitzing Patrick, you are inviting disaster.

The Chargers might well have won that contest.  But, while the defense was dampening down the Chief’s firepower, the offense didn’t take full advantage of their opportunities.  After scoring 14 points in the first half, their first three drives of the second half all took them into Kansas City territory.  They managed just 2 field goals and had a pass intercepted on the KC five yard line.  The last field goal came after LA had a first-and-goal from the 4.

What happened, then, was that they let the Chiefs hang around long enough that one big play (the 54-yard touchdown strike to Tyreek Hill with Mahomes scrambling out of the pocket) turned the momentum of the game.

Patriots Played Coverage

New England’s defense doesn’t feature the pass rush ability of the Chargers.  But, the Patriots have (arguably) football deepest and most highly skilled secondary – led by cornerback deluxe Stephon Gilmore.  In their matchup with the Chiefs, New England frequently rushed only three and dropped eight into coverage, almost evenly mixing man coverages and zones.

This is also a very workable strategy when executed well.  It doesn’t matter how great the quarterback is if he doesn’t have open receivers to throw to.  Unusual in Kansas City during the Mahomes era, last Monday you saw Patrick standing in the pocket holding the ball.  And holding.  And holding while waiting for someone to uncover.

In 35 drop-backs. Patrick dealt with imminent pressure just 9 times – although he was forced to scramble on 5 occasions.  Such pressure as New England managed usually was not early pressure, but came after Mahomes had surveyed the field awhile.  While he completed 19 of 29 throws (65.5%), most of his completions were contested, and two of his incompletions were very nearly intercepted.

Save for Tyrann Mathieu’s fourth-quarter interception return for a touchdown, Kansas City would have finished the evening with an almost unheard of 19 points.

As with the Chargers, the Patriots were able to do this because they are the best in the NFL (or nearly the best) in what they do – coverage.  They have an aspect of their defense that is strong enough and consistent enough to interfere with the regular workings of Andy Reid’s offense.

And they didn’t blitz.

In between these two victories, Kansas City had a relatively easy time beating Baltimore 34-20.  The Ravens also boast an elite secondary, but their pass rush is a function of a variety of cunning blitzes.  Patrick and his offense feasted on the Baltimore blitzing.  They carried a 27-10 lead into the half, and never looked back.  Mahomes finished the night 31 of 42 for 385 yards and 4 touchdowns.

Even if you are one of football’s best blitzing teams, this is not the offense to try that with.

Also, like the Chargers, the Patriots failed to take advantage of the long stretch of the game that the defense held the Chiefs close.  New England, of course, was absent its starting quarterback.  (Apparently Superman is vulnerable to the COVID virus.  I must have missed that episode.)  Their offensive struggles were somewhat understandable.

Even so, this is another plank in the formula for slowing down (and, eventually, beating) KC – which now reads:

First, either through pressure or coverage, beat the players around Mahomes.

Second, blitz rarely if at all.

Third, don’t miss on scoring opportunities.  You will not beat this team 13-10.

And, oh yes, a final point.  During all of this you have to stop their running game as well.  Andy has taken quite a shine to his first-round draft pick – a running back out of LSU named Clyde Edwards-Helaire.  Clyde has put up 304 ground yards through the first four games.  If you over play the pass, Clyde and the Chiefs will punish you on the ground.

The good news in all of this is that, yes, the Chiefs can certainly be slowed.  But it clearly isn’t easy.

Just One Thing – Analyzing Super Bowl LIV

Sunday, December 29 in Kansas City, Missouri was cloudy, quite chilly, and memorably beautiful.  It was Week 17 of the 2019 NFL season – the final regular weekend of football’s one hundredth season.

Earlier in the week, Chiefs’ coach Andy Reid had decided to play his regulars and try to win the game.  There were reasons to consider the other path – resting his regulars before the playoffs began.  The Chiefs had long since locked up their division and were comfortably positioned to host a playoff game on WildCard Weekend.  They did have a chance to claim the second seed and a first round bye – but for that to happen the almost unthinkable would have to occur.  The woeful Miami Dolphins would have to go into Foxboro at the end of December and beat the defending champion Patriots.

An improbable enough scenario that Reid could be forgiven if he chose the path of safety.  As the fourth quarters of both games played out on that memorable Sunday afternoon, and it began to be apparent that both parts of this improbable scenario were playing out, an almost surreal euphoria settled over the denizens of Arrowhead Stadium.  A promising postseason had suddenly become much more promising.

Getting a first round bye is a huge factor in gaining the Super Bowl.  It is inexpressibly sweeter when that bye is won at the expense of a bitter rival – the much-detested New England Patriots.  The final day of the recently concluded regular season was one of the sweetest days to be a Chiefs fan in about a half century.

Two Sunday’s later, all of the hope and euphoria lie crumbled on the Arrowhead Stadium floor.

Thanks to Tennessee’s upset of Baltimore the night before, the road to the Super Bowl now led through Kansas City – a fact that made the transpirings that Sunday afternoon all the more bitter.

Playing as though they had forgotten every fundamental of football, the Chiefs were quickly buried in an avalanche of mistakes.  Dropped passes, blown coverages, blocked punts, muffed punts, pre-snap penalties – the Chiefs committed all of the above.  The beneficiaries of all this ineptitude were the visiting Houston Texans, who gratefully lapped up every gift they were presented.

Five minutes into the second quarter, Houston kicker Ka’imi Fairbairn added the field goal that increased the Texans’ lead to 24-0.  The silence in the stands was palpable.  In the long history of playoff disappointments endured by the Kansas City fandom, this one just might have been the most heart breaking.  So good for so much of the season, and now with the road to the Super Bowl paved before them, and to blow it all in the very first quarter – it was a bitter result indeed.

And then, one thing went right for the Chiefs.  Just one thing.

On the ensuing kickoff, Mecole Hardman returned the kick 58 yards to the Texan 42.  And that was all it took.

Just like that, the Kansas City Chiefs remembered that they were not the mistake-prone, bumbling offense that they had shown themselves to be for the first 20 minutes of this contest.  They remembered that they were one of football’s most potent offenses.  Two plays later, they were in the end zone (Damien Williams taking the touchdown pass off his hip), and the reverse route was on.

Beginning with that touchdown, the Chiefs would go on to score on eight straight possessions – earning touchdowns on the first seven of those possessions.  Down at one point 24-0, Kansas City would advance to the Championship Game on the strength of a 51-31 thrashing of the Texans.

For twenty minutes, Houston had played as nearly perfect a game as they could have hoped for.  Had they held onto that lead, they would then have inherited home field for the Championship Round.  But they made one mistake on special teams and let the genie out of the bottle.

But the Kansas City story was just beginning to be written.

The next week they again overcame a deficit (this time just 10 points) on their way to the 35-24 conquest of Tennessee that advanced them to the Super Bowl for the first time in a half century.

Once there, though, they found their mercurial offense virtually silenced – in particular, by the defensive line of the San Francisco 49ers.  Over the 60 brutal minutes of Super Bowl LIV, Patrick Mahomes spent most of the evening running for his life. 

They played San Francisco to a 10-all tie through the first thirty minutes, but as the third quarter dissolved into the fourth quarter the relentless pressure began to get to Mahomes.  In the late third quarter and into the early fourth – even when he did have time to throw – Patrick’s accuracy began to suffer.

With 5:36 left in the third quarter, trailing 13-10 and facing a third-and-12, Mahomes couldn’t get enough loft on his throw over the deep middle, tossing the ball right into the waiting arms of San Fran’s Fred Warner.

San Francisco turned that interception into the touchdown that put them ahead 20-10.

With 1:10 left in the third, Sammy Watkins was breaking into an open window in the middle of the 49er zone, but Patrick skipped the throw in.

Early in the fourth quarter – still trailing by 10 – Mahomes drove KC to a third-and-six at the San Fran 23 yard line.  With still 12:05 left in the game, this drive represented their best chance (and maybe last best chance) to claw themselves back into the game.

Running out of the slot to the left, Tyreek Hill darted quickly into the open middle against nickel-corner K’Waun Williams.  With a good throw, it’s first-and-ten on the 15.  But, playing very fast at this point, Mahomes slung the ball well behind Hill.  Tyreek reached back to try to make a play on it, but only succeeded in deflecting the pass into the air, where Tarvarius Moore made the interception.

The next time the Chiefs got the ball, there were fewer than nine minutes left in the game.  With a first-and-ten on their own 29, Mahomes completed this pass to Hill, but the gain could have been much more than the 9 yards they got.  With room in front of Tyreek, Patrick threw the ball short – almost into the dirt in front of Hill’s feet, with Tyreek making an excellent diving catch.

A run from Williams picked up the first, and initiated the most telling sequence of Super Bowl LIV.

On first down, a false start from Laurent Duvernay-Tardif set KC back five yards to the KC 35.  Now with a first-and-fifteen, Hill settled into an opening in the zone in front of cornerback Emmanuel Moseley.  Charging hard, Moseley arrived at the same time as the football, successfully breaking up the pass.

Now it was second-and-fifteen.  Hill, lining up on the right side, threatened the 49er zone with a strong vertical stem, pushing Richard Sherman and Jaquiski Tartt deeper and deeper.  When Tyreek put his foot in the turf and turned looking for the ball, he was on the San Fran 43-yard line with no defender within six yards of him.  Calling the game on FOX, Troy Aikman offered that this should have been Patrick’s easiest completion of the evening.  Instead, Mahomes (throwing with Solomon Thomas’ hand in his face) delivered well short again.  Hill came back for the pass and made a strong enough play on it that he was originally credited with a 16-yard reception that was easily overturned on review.

So, here was the Kansas City season.  Fourth quarter.  Just 7:13 left.  Trailing by ten points.  Facing a third-and-fifteen from deep in their own territory against the NFL’s third-most feared pass rush (rated on percentage of sacks).

To this point in the biggest game of his young career, the electric Pat Mahomes was clearly struggling.  He had completed just 4 of his last 11, and for the game to that point he was 19 of 32 (just 59.38%) for 181 yards (averaging just 5.66 yards per pass attempt, and just 9.53 per completion).  Only 8 of his 19 completions had earned first downs, and he had thrown no touchdown passes to offset his two interceptions.  His passer rating to that point of the game was a humbling 49.09 to go along with 3 sacks San Francisco had already rung up against him.

Things could scarcely have looked much worse at this point.

And then, one thing went right for the Chiefs.  Just one thing.

On third-and-fifteen, Mahomes lifted his eyes to find Hill all alone deep up the left sideline.  In spite of pressure from lineman DeForest Buckner (who was hitting Patrick as he was releasing the ball), Mahomes arched a strike into Hill’s waiting arms for a game-changing 44-yard gain.

And just like that, the Chiefs remembered again that they were one of football’s most prolific offenses.  Beginning with that completion, Patrick would complete 7 of his next 9 for 105 yards and 2 touchdowns.  Much like in the Houston game, KC went on to score touchdowns on their next three drives, flipping a 10-point deficit into an 11-point win, 31-20 (gamebook) (summary).

As with Houston, the San Francisco defense had played an exceptional game for 53 minutes.  But against Kansas City (who with the victory became the first team ever to come from 10 or more points behind to win three straight playoff games) any mistake could prove fatal.

In the almost three weeks since the official end of the season, this has been the lingering memory of this season’s playoffs.  In three post-season contests the Chiefs faced three quality defenses that each presented solid game plans that – for a time – were very well executed.  In all three games, at some point, the Kansas City juggernaut was on its heels and very vulnerable.

But if you were going to beat Kansas City this post-season, you needed to play mistake-free from opening kickoff to final gun.  It was a no-room-for-error tightrope that all these teams had to walk. At any point in the proceedings just one crucial play can flip the momentum.

And once the scoring starts, the Chiefs don’t need a lot of time to do big damage.  Against Houston, four of the seven touchdown drives took 2:03 of clock time or less.  Their three fourth-quarter touchdowns against San Francisco took 2:40, 2:26 and 0:13.

Super Bowl LIV Notebook:

Interceptions have always been something of a rarity in the Super Bowl – to a, perhaps, surprising degree.  When Jimmy Garoppolo’s desperation fourth quarter pass was intercepted, it marked the first time in Super Bowl history that both quarterbacks threw at least two interceptions.

For Patrick Mahomes, his 4.8% interception rate (2 interceptions in 42 tosses) was the highest for a winning quarterback in a Super Bowl since Pittsburgh won Super Bowl XL (40) 21-10 over Seattle in spite of 2 interceptions from Ben Roethlisberger in just 21 passes (a 9.5% rate).

Garoppolo’s 2 interceptions came in 31 passes – a 6.5% rate. That is the highest rate for any Super Bowl quarterback since Rex Grossman had 7.1% of his passes intercepted in Super Bowl XLI – Chicago’s 29-17 loss to Indianapolis.  Rex threw 28 passes that day – 2 of them to Colts.

Garoppolo’s 219 passing yards were also the fewest by a Super Bowl losing quarterback since Grossman’s 165 yards against Indy.

The Chiefs finished with a surprising 129 rushing yards – a good chunk of those yards coming on Damien Williams’ clinching 38-yard touchdown burst.  As San Francisco ran for 141 yards, that made this the first Super Bowl since the before-referenced Pittsburgh-Seattle Super Bowl (number 40) in which both teams ran for at least 120 yards.  The Steelers ran for 181 that day, while the Seahawks pounded away for 137.

That run, by the way, pushed Williams to 104 for the game.  He becomes the first running back from a winning Super Bowl team to exceed 100 rushing yards since Dominic Rhodes piled up 113 rushing yards for the Colts against Chicago in Super Bowl XLI (41).

49er wide receiver Kendrick Bourne caught 2 passes on the evening for just 42 yards.  Those yards, though, made him San Francisco’s leading receiver in yardage for the game. You would have to go all the way back to Super Bowl XXXV (35) – Baltimore’s 34-7 demolition of the New York Giants – to find the last time that the losing Super Bowl team didn’t manage one receiver with at least 60 yards.  Ike Hilliard led the battered Giant receiving corps that day with 30 yards on 3 catches.

The Undercard

So much of the focus of Super Bowl LIV went to the matchup of the irresistible force (the KC offense) vs the immovable object (the SF defense), that the matchup between the 49er offense (second highest in scoring and fourth in yards) against the much-improved Chief defense became mostly overlooked.

Looking ahead, though, the significance of the 49er appearance in Super Bowl LIV cannot be overstated.  For the last couple of seasons, we have noted the rise of the Neanderthal offense in the NFL – a Neanderthal offense is one that seeks to run the ball more than it passes.  Unimaginable a few seasons ago, there are now several teams who identify as primarily running teams.  And now one of them – San Francisco – has advanced as far as the Super Bowl.

In their games leading up to the Super Bowl. The 49ers were at their Neanderthal best.  During the regular season, their 498 rushing attempts and their 144.1 yards per game were both the second best totals in the NFL.  They ran the ball 47 times in the Divisional Round against Minnesota, rolling up 186 yards.  Quarterback Jimmy Garoppolo threw only 19 passes in that game.

Against the Packers in the Championship Game, they rolled up 285 rushing yards on 42 carries, while asking Garoppolo to throw just 8 times.

While logic would suggest that a similar approach – if effective – would go a long way towards keeping the KC offense on the sideline, apparently a run-heavy approach was never in the game plan.

On first down, of course, San Francisco employed a very Neanderthal approach.  The 49ers ran the ball 16 times on first down – 14 of those on first-and-ten.  This they did to excellent effect, rolling up 119 yards on those carries (8.5 yards per).

Off of that first-down running game, Garoppolo ran a devastatingly effective passing attack.  Throwing 12 times on first-and-ten, Jimmy completed 10 of those passes (83.33%) for 96 yards and a touchdown – a 127.78 rating.  As you might expect, the play-action pass was a featured part of the passing attack.  For the game, Jimmy was 12 for 15 (80.00%) on play-action for 123 yards (8.20 per attempt).  His lone touchdown pass came off of play-action, giving him a 123.06 rating for the game.

When he ran play-action on first-and-ten, he was 7-for-7 for 73 yards.  But all that changed on second down.

Against the Packers, San Fran ran the ball 12 times on second down for 101 yards (8.4 per), scoring 3 of their 4 rushing touchdowns on that down.  Against KC, they barely made the attempt.

On 16 second down plays, the 49ers ran just 4 times (for 12 yards).  They asked Jimmy to throw the ball 12 times on that down, with minimal results (6 completions for 66 yards).  Both of Garoppolo’s interceptions fell on second down – leaving him a rating of 27.08 on that down.

For all of that, though, Kansas City didn’t force many third-and-long situations.  San Francisco faced third down only 8 times all evening (converting 3)

Timely Defense

The game was, in fact, rather characteristic of how the Kansas City defense played down the stretch and into the playoffs.  They forced only one three-and-out, and throughout the contest they always seemed on the verge of yielding points.  San Francisco managed at least one first down in each of their first 7 possessions.  Two of those possessions consumed more than five minutes of clock time, and four of the seven ended in Chief territory – yielding two touchdowns, two field goals, one punt, one interception and a possession that ended with the end of the first half.

In many ways, the San Francisco offense clicked along according to plan – with one glaring exception.  San Fran had three consecutive possessions in the second half during which they held a lead.  They got the ball with 5:23 left in the third holding a 13-10 lead; their next possession came with 11:57 left in the fourth with a 20-10 lead; and shortly thereafter, still leading 20-17 with 6:13 left in the game they had another possession.

These possessions should have constituted the Neanderthal moment.  This is the game situation you strive for if you are that running team.  This was the time that San Fran needed to impose its will and take firm control of the game.  In those three drives, the 49ers ran 14 plays – 6 of them running plays that earned just 18 yards.  As they had done against Tennessee, the gritty Kansas City defense just did not allow the running game to take over.  They were disciplined in forcing Garoppolo to win the game with his arm.

And that would prove to be challenge enough.

All About the Pressure

As surprising as San Francisco’s decision to de-emphasize its running game was, Kansas City’s defensive response was equally puzzling.  Throughout the regular season, the Chiefs were a moderate blitzing team, adding extra rushers about 30% of the time.  Against a similar offense in Tennessee in the Championship Game, KC blitzed on just 9 of 34 passing attempts.

But against San Francisco they decided the answer would be the blitz.  And so they came.  They blitzed on San Fran’s first two passing plays (giving completions on both plays), and 10 times on the 49ers first 13 passes – including the last six in a row.

For the game, the Chiefs ended up blitzing 20 of Jimmy’s 33 drop backs (a surprising 60.6%).  And for 3 quarters the results couldn’t have been worse.

The 49ers’ offense is especially challenging to blitz.  The strength of their play-action attack was very effective in removing the pressure of the added rushers.  Typically, the line would react as though running a stretch play, with Garoppolo faking the hand-off and then rolling in the opposite direction of his line and – almost always – away from any trouble.  The first 14 times that the Chiefs blitzed, Garoppolo completed 12 of 14 for 131 yards and his touchdown pass to Kyle Juszczyk.

And then, as Kansas City began mounting its comeback, San Francisco stopped doing those things.  They still responded to the KC blitz with play-action, but it was a less-convincing “hint” of play-action with the line in pass blocking mode.  As the fourth quarter arrived, Jimmy stopped rolling out of the pocket and waited there for the pressure to arrive.  All of a sudden, instead of dictating to the Kansas City blitz, the 49ers stood still and let the KC defense dictate to them with a collection of delayed blitzes and overload blitzes that had Garoppolo throwing under heavy pressure for most of the last quarter.

After completing his first pass of the fourth quarter, Garoppolo’s numbers for the game read 18 for 21 (85.71%) for 195 yards (an average of 9.29 per attempted pass) with 1 touchdown and 1 interception – a rating of 101.39.  From that point on, Jimmy was only 2 for 10 for 24 yards and another interception – a 0.00 rating only because the rating system doesn’t allow for negative ratings.

When given a relatively clean pocket, Jimmy was 17 for 22 for 186 yards.  Under significant pressure – which didn’t happen on any consistent basis until that fourth quarter – Garoppolo was just 3 for 9 for 33 yards, an interception and a sack.  The last 6 times that KC blitzed, Garoppolo was 0-for-5 with the sack by Frank Clark on fourth-and-ten that pretty much closed things out.

Here again the KC defense continued their meme of rising to the occasion as they continued to play their best at the game’s most crucial moments.  But the deeper story is more complex than that.  Throughout the game, San Francisco ran plays and did things that worked.  And then they stopped doing them.

Receiver Deebo Samuel carried the ball on three rushing plays, gaining 32, 7, and 14 yards on those carries.  The last of those came on the third play of their first drive of the second half.  San Francisco never went back to it again.

Both coaching staffs have done an admirable job all season.  Under the pressure of the Super Bowl, though, I think out-thinking yourself becomes a very real danger.  San Francisco’s Kyle Shanahan may have done that.

Andy Reid, I think, was guilty of that as well.

Unexpected is Not Always Best

After the 49ers toppled the Packers to earn the right to play in Super Bowl LIV, I made this observation about their defense:

As teams began to understand the San Francisco defense, they realized that what made them special was the defensive line – especially Nick Bosa, Arik Armstead and DeForest Buckner.  Beginning with their Week Nine, 28-25 win over Arizona, the league began constructing game plans that would minimize the impact of the defensive line, and force the linebackers and defensive back to beat them. 

Opponents began to run the ball with more commitment, and when they threw the ball they kept more blockers in the backfield to block.  Or, noting that the 49ers run a predominantly zone defense, they resorted to shorter, quicker passes and a more ball-control concept.  (Here is the full post.)

Noting that the 49er defensive line was the only part of the San Francisco defense that could cause real havoc with the Chief offense, I expected Reid and the offense to do some of those things against San Fran.  At the very least, I expected they would provide some help for their tackles (an occasional tight end, perhaps a chip from a running back).

But largely none of that happened.  The Chiefs did throw a couple of quick passes, but never really exploited the short openings in the zone.  Extra protection for Mahomes almost never happened.  Kansas City did run the ball with more than expected frequency and with good commitment, but not often enough to impact the pass rush.  And most surprisingly, they left their offensive tackles on an island against the San Francisco ends virtually the entire game – even though it was obvious before their first quarter was concluded that these were mismatches.

If asked to name the most dominant player of Super Bowl LIV, I would nominate San Francisco defensive end Nick Bosa.  But he should have been.  The opposing coach practically invited him to be.

Against the Packers two weeks before, Bosa and fellow disruptive end Arik Armstead were frequently left alone against Packer tackles David Bakhtiari and Bryan Bulaga.  But Bakhtiari and Bulaga are two of the top tackles in football, and they gave as good as they got against the 49er ends.

Kansas City’s tackle tandem of Eric Fisher and Mitchell Schwartz don’t rank with the pair in Green Bay.  They are a rather middling pair of tackles.  But Andy Reid’s game plan treated them as though they were as elite as the ends he would be asking them to block.  Even after it became apparent that they were in over their heads, Reid made no move to alleviate the situation.

Schwartz fared a bit better against Armstead – who sometimes moved inside to rush where the Chiefs could get a double-team on him.  But left tackle Fisher spent the game at Bosa’s mercy.  And Nicky almost took Kansas City’s crown away from them.

Coming mostly from Bosa, 25 of Mahomes’ 50 dropbacks came under heavy pressure.  I define this as pressure that either forces the quarterback to run for his life, or that has him being hit as he throws the ball (or within a step of being hit), or pressure that forces the quarterback to make another decision with the football (like throwing it away).  Patrick was just 7 of 17 with an interception and a 61.40 passer rating under this kind of pressure – to go with 4 sacks and 4 scrambles.  It was this consistent heat that held the explosive Kansas City offense to just 10 points up until the halfway point of the season’s last quarter.

Even after the Chiefs began their comeback, the pressure continued.  Five of Patrick’s last 10 passes – including the 44-yarder to Hill and the go ahead toss to Williams – came under this level of intense pressure.  At the end of the day, it came down to Mahomes making important throws under great duress.  That he was able to deliver a Super Bowl victory in a game where his line never, ever gained control of the line of scrimmage is just another indicator of how special Patrick is.

And how consistently exploitable the 49ers were in the secondary.  As I had previously noted, the 49er defense is elite at the defensive line level, but notably less spectacular after that.  If there was one player whose mistakes might be most responsible for San Francisco’s defeat, that player might be cornerback Emmanuel Moseley.

Moseley’s Miscues

San Francisco’s only poor moment in the Divisional win over Minnesota was the 41-yard touchdown pass thrown from Kirk Cousins to Stefon Diggs – a deep pass poorly played by then-starting cornerback K’Waun Williams.  That play led to Williams being shifted to nickel corner and prompted San Francisco to elevate Moseley’s to the right corner spot opposite Richard Sherman.

On Super Bowl Sunday, that decision came back to haunt them.

Throughout, Emmanuel was very solid in man coverage.  The problem, though, is that San Francisco is a predominate zone defense – they were in zone 54.8% of the time in Super Bowl LIV – and in zone, Moseley fights an almost irresistible urge to wander – a tendency that expressed itself in a few of the game’s most critical moments.

With 14:08 left in the first half, the Chiefs – already leading 7-3 – had a first-and-ten on their own 44 after an interception.  Tyreek Hill lined up opposite Moseley and started up-field on what seemed to be a vertical route.  But after about 15 yards, Tyreek began to bend his route toward the middle, and Emmanuel drifted with him.  That allowed Sammy Watkins to settle into the vacated area, where he pulled down a 28-yard pass.  That play set KC up inside the 49er 30-yard line, and led to the field goal that accounted for their last scoring of the first half.

It was also Kansas City’s only play of 20 or more yards in the entire first half – an erratic effort that saw them head into the locker room only 1-for-6 on third down, and having gained only 155 total yards.

San Fran dodged one on the first play of the fourth quarter.  It was Watkins this time who started wide but curled toward the middle of the field – taking Moseley with him.  This left Hill all alone up the sideline against safety Jimmie Ward (who thought he only had the short zone to that side).  It was the pass rush – this time from Dee Ford – that saved the day, not allowing Mahomes enough time to wait for Hill to clear and ultimately forcing an errant throw.

They weren’t so lucky about eight minutes later.  On third-and-fifteen, and the season trickling through Kansas City’s fingers, Moseley once again abandoned his deep responsibilities to follow Watkins over the middle – making possible the momentum-changing 44-yard toss to Hill, who had the entire sideline opened to him.

For the game, when throwing to his left (Moseley’s side) Mahomes was 9 for 12 (75%) for 133 yards (11.08 yards per attempt and 14.78 per completion) – a 110.76 passer rating.  It will be something for the 49ers to chew on over the offseason.

A Tale of Two Tight Ends

One of the intriguing pregame storylines were the two tight ends, each of whom led his respective team in both receptions and receiving yards. 

In his third season out of Iowa, San Francisco’s George Kittle earned his second consecutive Pro Bowl berth on the strength of an 85-catch, 1053-yard season – his second consecutive year with over 80 catches and more than one thousand yards.

With the emphasis on the run in the 49ers’ first two playoff games, George had fewer opportunities than usual, catching 3 passes against the Vikings for 16 yards.  He had just one catch against Green Bay for 19 yards.

On the other side of the field was Kansas City’s Travis Kelce.  In his seventh season out of Cincinnati, Kelce was named to his fifth consecutive Pro Bowl.  He followed up his 103 catches in 2018 with 97 more during the regular season, and completed his fourth consecutive thousand yard season – with his 1229 yards in 2019 ranking him fourth among all receivers in football.

Travis was one of the heroes of the comeback against Houston.  He caught 10 passes for 134 yards and 3 touchdowns in that game.  He was held to 3 catches for 30 yards against Tennessee.

Interestingly, in that game, Travis saw almost exclusive coverage from defensive backs, as the Titans decided to defend more against his speed than his size.

This coverage concept followed both tight ends into their Super Bowl showdown.  Kittle saw a lot of safety Daniel Sorensen – and drew more frequent double coverage than Hill.  As for Kelce, almost every time he lined up as the lone receiver to either side he drew the attention of the cornerback on that side.  When he lined up to the offensive right side (Richard Sherman’s side), he would be subjected to a very physical press coverage.  Even if San Francisco would resort to zone coverage afterward, Sherman would still jam him at the line to disrupt his route.

This additional attention was very effective for both defenses, as neither end was particularly prominent in the passing game.  Kelce finished with 6 catches for 43 yards, and Kittle caught 4 for 36 yards.  During the regular season, Kittle had caught 27 passes on third down – 18 for first downs.  In the Super Bowl, George had no third down catches, and was targeted just once on that down.  Kelce didn’t even have a third down pass thrown his way.

The difference, though, was the offenses around them.  The extra coverage on Kittle didn’t seem to compromise Kansas City’s overall pass defense.  On the other hand, while the 49ers were extra-concerned with Kelce, Tyreek Hill was targeted 16 times, catching 9 of them for 105 yards.

On the Toughness of the Chiefs

After they pushed their way past Tennessee, I made note of the unexpected toughness of the flashy Kansas City offense.  That toughness was again on display in Super Bowl LIV.  We saw it from Mahomes, who took several big hits and bounced back up every time.

On the last Sunday of the NFL’s one-hundredth season, that toughness found its best expression in the Kansas City running game and emerging running back Damien Williams.

In his second season in Kansas City after four uninspiring seasons in Miami, Williams began the season as the “other” back behind LeSean McCoy.  After rushing for just 256 yards in all of 2018, Damien began 2019 in quiet fashion.  Six games into the season, Williams had just 48 carries for 100 yards even – 2.1 yards per rush.  Then, in a Week 7 win against Minnesota, Damien scorched the Viking defense for 125 yards on just 12 carries.

From that point forward – with the exception of three late season games missed with an injury – Williams began to surpass McCoy on the depth chart.  LeSean wasn’t even listed as active for the Super Bowl.

Williams averaged 6.3 yards a carry over his last 5 regular season games, and ended the season just ahead of McCoy, 498 yards to 465.

During Super Bowl LIV, Kansas City ran the ball 10 times with less than four yards to gain for a first down – once on first-and-one; five times on second-and-one, once on third-and-two, once on third-and-one, and twice on fourth-and-one.  They converted 9 of the 10, with Williams going 7-for-7 in those chances.

One of the memorable plays from the game was the colorful spin-o-rama play.  This was one of the fourth-and-one plays called for with 1:57 left in the first quarter.

The Chiefs lined up with two wide receivers (Watkins and Demarcus Robinson) joining Williams in the backfield.  Just before the snap, all four members of the offensive backfield executed a 360-degree turn.  It was a flashy move that served a sneaky purpose as it now aligned Williams directly behind the center, where he took a direct snap.

Damien would pick up the first down, but it wouldn’t be easy.  While he was still a yard in the backfield, Sheldon Day overpowered Fisher, grabbing Damien around his knees. As Day’s hands slid down to Williams’ ankles, it seemed certain that Damien would go down – possibly before gaining the first down.

But somehow he pulled his feet out of the snare, and, executing a second spin move on the same play, he twirled out of the grasp of Emmanuel Moseley. Then – with the goal line in sight – Damien lowered his shoulder and plowed through Jaquiski Tartt’s attempted tackle.  He was ultimately pulled down inches short of the goal line, having made the first down with plenty to spare.

Perhaps no single play encapsulates the 2019 Kansas City Chiefs better.  Underneath the eye-candy – unpinning the flash-and-dash – was an unexpected core toughness.  The physical toughness to convert short-yardage runs against an elite defensive line, combined with the mental and emotional toughness to overcome large deficits in three straight playoff games to bring home a championship.

And as for Williams, the man who scored the first touchdown in their comeback win against Houston ended up scoring the last two touchdowns of the season.  He heads into the offseason as, possibly, the least celebrated 100-yard rusher (he finished with 104) in Super Bowl history.

For Kansas City it may work out better that way.  Better, perhaps, that you remember the glitter and pay less attention to the grit.