Skip to main content

The 3 controversial Packers penalties that sparked another stunning collapse

An inexcusable loss. But, some controversial penalties helped out the Vikings.
ByScott Rogust
Green Bay Packers v Minnesota Vikings
Green Bay Packers v Minnesota Vikings | Todd Rosenberg/GettyImages

There are no excuses, really, for this kind of loss. The Green Bay Packers ended last season by losing to a hated division rival after a late-game collapse. In the first game of the 2026 season, the Packers accomplished the same thing. Promise for two and a half quarters, only to watch a sure-fire win turn to dust.

The Packers held a 22-10 lead in the third quarter against the rival Minnesota Vikings, who saw starting quarterback Kyler Murray leave due to a concussion and be replaced by Carson Wentz. Even though the Packers looked like they could coast to a win, they completely collapsed, surrendering 29 unanswered points.

There's no excusing how the Packers lost. But on the one drive in which the Vikings took the lead for good, there was plenty of controversy. By that, we mean controversial penalties called against the Packers.

One penalty-riddled drive sunk the Packers' chances of winning

1. Illegal contact to wipe out a drive-ending sack

11:03 remaining, Vikings 3rd-and-11 at their 34-yard line

The Packers, up 22-17, could have effectively ended the Vikings' comeback chances at the start of the fourth quarter. On third-and-11, Edgerrin Cooper and Devonte Wyatt both sacked Wentz to seemingly end the drive.

However, safety Javon Bullard was called for an illegal contact penalty, giving the Vikings a fresh set of downs. But that wasn't the truly controversial penalty.

2. Roughing the passer penalty that ruins another third-down stop

9:12 remaining, Vikings 3rd-and-3 at their 46-yard line

On 3rd-and-3, Wentz threw an incomplete pass to tight end T.J. Hockenson. However, Wentz was hit by rookie defensive tackle Chris McClellan, who was flagged for roughing the passer. But when looking at the replays, McClellan let up on his hit.

The referees said McClellan drove Wentz into the ground. Even commentator and former NFL pass rusher J.J. Watt didn't agree with the call.

3. Defensive holding that took an interception off the board

6:49 remaining, Vikings 3rd-and-5 at the Packers' 6-yard line

If you thought the penalties were done there, the referees decided they had one more in them. On yet another third down for the Vikings, the Packers again stopped Wentz, this time with an interception by safety Evan Williams.

Yet, the interception didn't count, as fellow safety Xavier McKinney was called for defensive holding. That then gave the Vikings yet another first down. It was another controversial call.

Three penalties resulted in a fresh set of downs for the Vikings. The drive ended with a 3-yard rushing touchdown from Aaron Jones. One successful two-point conversion later on a pass from Wentz to Justin Jefferson, the Vikings took a 25-22 lead.

Packers inexcusably contributed to collapse with awful late-game play

For the Packers, while that drive was egregious, they still had plenty of time to bounce back and retake the lead. Instead, they choked. Notably, quarterback Jordan Love and the offensive line completely fell apart.

On the following drive, Love fumbled the football, which was recovered by Vikings linebacker Andrew Van Winkel. The Vikings were set up on the Packers' own 1-yard line, and they immediately scored on a rushing touchdown by Jordan Mason.

As if things couldn't look any bleaker for the Packers, Love's throw to Christian Watson was picked off by cornerback James Pierre. Six plays later, Wentz connected with Jefferson on a 9-yard touchdown pass to give the Vikings a 39-22 lead.

This game will be the ultimate "watch the tape, and then burn it" moment for the Packers. Hopefully, the Packers can learn from this game, play cleaner football, ensure the referees don't become too much of a factor in the final decision, and not falter when the pressure begins mounting.

This was not how the Packers fanbase hoped the 2026 season would start. A true disaster.

Add us as a preferred source on Google

Loading recommendations... Please wait while we load personalized content recommendations