Sep 18, 2026 1:41 PM

Abandoned passing lanes and rigid play-calling stifled a late-game surge, as Petzing’s stubborn insistence on an ineffective ground attack neutralized the offense and gifted Buffalo a narrow victory.

When game tape is reviewed from the Detroit Lion's last night's heart-wrenching loss to Buffalo, the primary culprit won't be a lack of physical effort or talent. It will be the baffling, rigid sequence of second-half play calling orchestrating from offensive coordinator Drew Petzing.

In a high-stakes setting where adapt-or-die is the golden rule of play calling, Petzing stubbornly refused to ride the momentum of what was working, instead forcing a grounded offense straight into a brick wall.

The Air Attack Was Cooking

From the opening kickoff, it was abundantly clear how to exploit Buffalo's defensive front. When Petzing dialed up passing concepts, the offense looked fluid, explosive, and completely unstoppable. The intermediate routes were slicing up zone coverage, high-low reads were holding safety assistance, and the rhythm of the quick-release passing game neutralized Buffalo’s front-seven pass rush.

Every single time the ball was put into the air late in the game, positive yards followed. Drive extensions, key first downs, and field position flips were routinely secured off the back of the passing game. The aerial scheme was actively solving every problem Buffalo presented.

Yet, as the fourth quarter ticked away and the margin for error dropped to zero, Petzing appeared intent on proving an ideological point rather than winning a football game.

The Ground Game Was Dead on Arrival

To call the late-game rushing attack ineffective would be an underestimation; it was a momentum killer. Buffalo's defensive line adjusted mid-game, stacking the box, penetrating the interior, and blowing up running lanes before the back could even make an initial cut.

On repeated late-game drives, Petzing predictably called early-down interior runs that resulted in brutal, self-inflicted damage:

*1st and 10: Stuffed for a 1-yard gain.

*2nd and 9: Tackled behind the line of scrimmage for a 2-yard loss.

*3rd and 11: Forced into a predictable, high-pressure passing situation against a pinning-their-ears-back pass rush.

By repeatedly running the ball into loaded boxes, Petzing did Buffalo's defensive coordinator a massive favor. He consistently put the offense behind the chains, killing potential rhythm, burning crucial clock time, and handing the defensive coordinator easy third-and-long blitzing scripts.

A Failure to Adjust When it Mattered Most

The most frustrating element of Petzing's sequence wasn't just that the runs failed; it was the outright refusal to pivot. Football at the highest level requires an operational pivot when a primary game plan gets compromised. When the defense makes it impossible to run, a coordinator must use the short passing game, quick slants, screens, and speed-outs, as an extension of the run game to stretch the field horizontally.

Instead, Petzing fell into the classic play-calling trap of clinging to "balance" for the sake of balance. Throwing the ball wasn't just an alternative option; it was the only functional mechanism keeping the offense alive. Passing was creating space, moving the chains, and putting pressure back on Buffalo. Running was halting drives before they even started.

By treating a failed run game like a security blanket late in the fourth quarter, Petzing effectively snatched defeat from the jaws of victory.

Moving Forward

A loss for Detroit like last night’s stings because it was entirely preventable. The players executed when given plays that matched the flow of the game. If Petzing wants to steer this offense to its full potential, he needs to trust what the game dictates, throw out the rigid call sheet when it isn't working, and put the ball in the hands of the passing game when it's the only machine generating heat.

Comments
anonymous profile image
Powered by RoundtableBuilt on infrastructure designed for real-time media. Learn more at RTB.io.© Roundtable 2026. By using this site you agree to the Terms of Use and Privacy Policy