Ball don’t lie: 3 worst calls from Week 9 in the NFL
By Mark Powell
1. The Marcus Peters interception that wasn’t
I have no idea what a catch is. You have no idea what a catch is. NFL officials have no idea what a catch is. As long as we enter this conversation with that amount of understanding, all is well.
Marcus Peters made a hell of a play against the Indianapolis Colts on Sunday, getting in the way of a Philip Rivers deep ball and making what — at the time — appeared to be an interception. Upon further review, though, Peters did not control the ball all the way to ground. So, it’s an easy call, right? Right?
https://twitter.com/MySportsUpdate/status/1325528758368030720
Nope. Peters evidently made a football move while falling and was gifted the interception, even after review. I’d have sincere criticism for such a decision if I understood whatsoever what the NFL is going for here. No one understands the catch rule. There is zero consistency in key decisions made by the officiating crew. Peters quite literally dropped the interception. It’s Colts ball, yet the NFL even doubled down on its initial controversial claim.
I’m not mad, I’m just disappointed.
Recap: Week 9’s list was top-heavy. The Peters so-called interception and Watson’s touchdown post-delay of game were so egregious that they could’ve formed a list of their own. The Cowboys-Steelers game was filled with questionable, yet defensible decisions. So, in the end, we’ll go with a C. Enjoy passing college.