Great news: the NFL is still trying to determine what is and what isn’t a catch. They have taken what is seemingly one of the easiest things ever to determine and made it one of the most confusing and controversial: but the shield will not let it go, damit. They’re going to keep changing and refining the rule until we all know damn well what a catch is.
And I think they finally, finally got it right: now, it’s a catch if “a player has the ball long enough to become a runner when, after his second foot is on the ground, he is capable of avoiding or warding off impending contact of an opponent, tucking the ball away, turning up field or taking additional steps.”
Yeah, because that clears it all up: it’s a catch if the receiver is capable of warding off some dude trying to knock the crap out of him, while tucking the ball away, whatever the hell that entails and then taking additional steps, two or five or ten, or who knows, because it doesn’t say.
Again, the league has taken the simplest thing ever and made it the most confusing.
I’m going to do this one more time and one more time only. And then never again. I will tell you how you know what’s a catch and what’s not in the NFL. Ready. Try to follow along. A catch is a catch. That’s what a catch is.
It’s that simple. If a player catches the ball, it’s a catch. If the player drops the ball, it is not a catch.
Stop clouding the issue and wasting my time with whether or not the player made a football move…or established himself as a runner. Or perform an act common to the game: I’m going to perform an act for the good of all mankind: and tell you what a catch is. A catch is a catch. If he catches it. It’s a catch.
Put that in red ink in the rule book. Now you’re done. And so I am. Stop wasting our time.
This post brought to you by Jim Rome.