The first quarter of Monday Night Football couldn't have started any better for the Tampa Bay Buccaneers.
In a difficult matchup between two heavyweights, the Bucs hosted the Baltimore Ravens who are home to a pair of potential MVP candidates in quarterback Lamar Jackson and running back Derrick Henry. But, Tampa Bay has one of their own in quarterback Baker Mayfield.
Speaking of Mayfield, he and the offense marched right down the field after winning the coin toss. Mayfield hit wide receiver Mike Evans for his 100th career touchdown, and things were absolutely rolling.
As if it couldn't get any better to begin with, the Bucs defense went on to sack Jackson twice on the Ravens' first drive and forced Baltimore to punt.
On Tampa Bay's second possession, Mayfield and the offense marched down the field yet again and, for a moment, it appeared as though the Bucs were about to go up 14-0. Mayfield hit wide receiver Chris Godwin for a touchdown but, before Godwin and his teammates could start celebrating, a penalty flag was thrown.
The refs called a holding penalty on left tackle Tristan Wirfs, who hadn't been flagged for holding since Week 16 of 2022. So, the fact that there was a holding call on Wirfs was a bit of a shock to us all; either Wirfs is actually human, or the refs made a big mistake.
More Bucs news:
As it turns out, based on the video evidence you can see here, this was a flat-out horrendous call. Forget "controversial" or "polarizing," if you will. This wasn't a good call, whatsoever. Maybe, just maybe, it could have gone either way. But, based on the reactions, it was far from a concrete call by the officials.
Just take the following reactions, for example. These are a few of many similar sentiments offered across social media in regards to the Wirfs penalty.
Fans and media react on social media to the phantom Tristan Wirfs holding call
That absolutely wasn’t holding on Wirfs
— trey wingo (@wingoz) October 22, 2024
Even Mr. Trey Wingo agrees. It wasn't holding.
HOW THE HELL WAS THAT A HOLD ON WIRFS!!!!!! It really should be 14-0 but what do I know
— Aaron Bledsoe (@shadowpirate27) October 22, 2024
Aaron is saying what every Bucs fan was thinking.
That is a phantom call on Wirfs right there. Cost the Bucs 4 points. Rough. Officiating strikes again
— Jon Ledyard (@LedyardNFLDraft) October 22, 2024
The best way to put it, honestly ... a "phantom" call, indeed.
That wasn't a hold on Tristian Wirfs. Refs painting the narrative, gotta keep their darling's happy
— SeanG (@poundempanthers) October 22, 2024
That's one way to put it ... not sure on the narrative, but it was indeed painted.
That’s not a hold on Wirfs
— Duke Manyweather (@BigDuke50) October 22, 2024
No, no it is not.
That’s a bad holding call
— Jarrett Bailey (@JBaileyNFL) October 22, 2024
Yes, yes it is.
Refs saved us because that was not a hold by Tristan Wirfs. It was just great offensive lineman play. #RavensFlock #WeAreTheKrewe
— Maher 🇵🇸 (@pabloikonyero) October 22, 2024
So, even a Ravens fan admits it! That settles it, once and for all. It was not holding on Wirfs, period.