Ball don’t lie: The 3 worst calls from NFL refs during Super Bowl 57
By Mark Powell
Super Bowl worst calls from NFL refs: What exactly is a catch?
The NFL’s definition of a catch is confusing to any fan. Really, it’s a case by case basis. We just wish there was a little more consistency in the matter.
Super Bowl 57 had several examples of catch vs. no-catch rulings, and while they weren’t necessarily wrong in the moment, they are worth pointing out due to the lack of clarity.
Arrowhead Addict described the play:
"“On the Eagles’ opening drive of the second half, quarterback Jalen Hurts found running back Miles Sanders for a short pass, but Chiefs defensive back L’Jarius Sneed was more than ready for it and it was an instant hit for a three-yard loss. Even more importantly, the ball was knocked loose and Bolton picked it up and sauntered into the end zone. For a brief moment, it looked as if Bolton would have his second touchdown of the night—an incredibly heroic performance from a second-year linebacker—but officials quickly went to work to see if it was the right call or not.”"
https://twitter.com/ClutchPointsApp/status/1624953030826409985
It’s important to note that the play was called a fumble and defensive touchdown on the field. After a long review, the ruling on the field was overturned.