Ball don’t lie: 3 worst calls from Week 5 of the NFL

1. Chase Claypool got robbed of a fifth touchdown

Yeah, you read that correctly. Claypool’s Week 5 could’ve been even better. The Steelers needed all four of Claypool’s touchdowns to survive the Philadelphia Eagles’ upset attempt this week. Pittsburgh’s rookie is just another example of Mike Tomlin and Kevin Colbert’s ridiculous ability to select high-caliber wide receivers each April. The Notre Dame product caught what he thought at the time was his fourth touchdown, but it was called back thanks to an incredibly weak OPI.

I’m all for seeing pass interference go the other way from time to time, especially given how weak officiating crews have become at allowing contact in the secondary. The rulebook is already suspect as to what’s pass interference, and what isn’t. The officials have no idea how to follow it, and despite blowing a literal playoff game because of that, they’re as awful as ever at interpreting those rules. Even when given a tool to overrule bad calls, they refused to do so. I have no words.

So, when defensive backs see a play like Claypool’s go the other way for once, they must be laughing it up. That’s what it feels like, rookie. That still doesn’t make it fair.

Recap: Yes, this week’s bad calls were a little Steelers-centric, but Claypool’s was easily among the worst of the season so far. The Giants lost what might’ve been their best (and only) chance at a win this year. And officials still have no idea what roughing the passer is. There are plenty of takeaways here, but overall it’s better than last week by a bit. A solid C, enjoy passing college.