Ball Don’t Lie: 3 worst calls from Week 1 in the NFL

Year after year, there's always one loser in football: The referees. Here are the absolute worst calls from Week 1.

Philadelphia Eagles v New England Patriots
Philadelphia Eagles v New England Patriots / Kevin Sabitus/GettyImages
facebooktwitterreddit
Prev
3 of 3
Next
Jawaan Taylor, Chiefs
Jawaan Taylor, Kansas City Chiefs / David Eulitt/GettyImages

Week 1 NFL Worst Calls: DO YOU HAVE EYES, SIR? Jawaan Taylor's blatant false starts and other pre-snap penalties

Kansas City Chiefs right tackle Jawaan Taylor got away with everything save for murder on Thursday night. In the Chiefs' season-opening loss to the Lions, Taylor got called out by Chiefs haters and Twitters users alike for his blatant miscues all game.

From the start of the game, fans noticed that Taylor was often lined up too far into the backfield and should have gotten flagged for an illegal formation. Once or twice, Taylor was spotted holding Lions' Aidan Hutchinson. And still other times, the ex-Jaguars tackle was moving his right leg when he shouldn't have and starting his pass-blocking set too early, two pre-snap fouls that Taylor also wasn't called for.

Finally, after nearly 60 minutes of play, the referees decided to call a false start on Taylor, but by then, the damage had been done. The uncalled fouls had racked up, and the world had already decided this season was scripted for another Chiefs' Super Bowl win.

One needs only to look back to February of this year to remember the controversial James Bradberry holding call that gave the Chiefs a fresh set of downs late in the fourth in their Super Bowl victory over the Eagles.

Not penalizing those obvious false starts by Jawaan Taylor gives the NFL officiating crew a bad rep in Week 1. Not like they had a good one in the first place.

One reason every NFL team can win the Super Bowl. light. Next. SL: One reason every NFL team can win the Super Bowl