BlindFaith
Well-Known Member
- Messages
- 5,115
- Reaction score
- 2,624
smh
I debated this till my fingers bleed back then. Not about to do it again. The rules are what they are and were applied correctly to Dez and to Ertz. The real issue, at least to me, is the underlying objective of how and why the rule is what it is. The language of the rule is just as much to blame as is some gaps in the rule itself. But by understanding the intent, you can see why they've added and modified the language.
So, instead of beating a dead horse, how about proposing how to clarify what a catch is? Let's give it a try...
First, the intent of the language "establish himself as a runner" is not clearly written. The intent is to ensure that the receiver has the ability and/or time to protect themselves. They've tried to convey this with different examples. "Be upright long enough", "make a football move", "have time to make a football move", etc. The act in of itself does not require actually being a runner or even running at all.
Example: WR catches a ball, both feet down, possess it. And he just stands there, makes no move. This is where the "time" element comes in. If he has the time to protect himself and secure the ball, then it's a catch. But let's say that instead of just standing there he gets drilled simultaneously? Now he doesn't have the "time" to protect himself. So no catch, even though he still secured the ball with both feet down. Now you could remove the time element, but now it goes from no catch to fumble.
Now onto "going to the ground". So if a receiver catches a ball but is in the act of going to the ground he has to maintain possession of the ball through contacting the ground. What this means is if the player, with or without contacting another player, ends up on the ground during the act of catching the ball, BEFORE having the ability to protect themselves. Or as the rule is currently written, to establish themselves as a "runner". Back to intent.
Example: WR dives to catch a ball. In mid air he catches the ball, then while still falling his knee and elbow hits the ground and it jars the ball out. The player did not have a chance to protect himself. Now you could remove the "become a runner" or "make a football move" and call that a catch and fumble. But do we want to open that up to the potential risk of having more fumbles?
What muddies the water even more are how athletic these guys are. Some catches where any average person would go to the ground immediately, these guys are able to somewhat regain their balance and get a few steps in before they actually do hit the ground. But do we remove the protection from them just because they take a few steps or shift the ball from one hand to another. If while doing all of this, still ultimately on their way to the ground, somehow they loose control of the ball. Do we call that a fumble just because they briefly controlled the ball and had two feet down? That's one of the aspects the NFL has and is struggling with when trying define this particular part of the rule. Weighing protecting the receiver from unforced fumbles vs making it a catch.
So what to do to fix it? Rewrite the rules to allow for more of the controversial non catches to be catches at the peril of also introducing a much greater chance for fumbles? Or leave things exactly as is with minor corrections to the language in the rule and simply tell receivers that they have to hang on to the ball if they are going to the ground while in the act of catching the ball?
I would love to hear the proposals for any rule change. But remember, it can't just be in the context of the Dez catch or any one specific example. It has to be in the context of how the rule change would impact every type of catch.
I debated this till my fingers bleed back then. Not about to do it again. The rules are what they are and were applied correctly to Dez and to Ertz. The real issue, at least to me, is the underlying objective of how and why the rule is what it is. The language of the rule is just as much to blame as is some gaps in the rule itself. But by understanding the intent, you can see why they've added and modified the language.
So, instead of beating a dead horse, how about proposing how to clarify what a catch is? Let's give it a try...
First, the intent of the language "establish himself as a runner" is not clearly written. The intent is to ensure that the receiver has the ability and/or time to protect themselves. They've tried to convey this with different examples. "Be upright long enough", "make a football move", "have time to make a football move", etc. The act in of itself does not require actually being a runner or even running at all.
Example: WR catches a ball, both feet down, possess it. And he just stands there, makes no move. This is where the "time" element comes in. If he has the time to protect himself and secure the ball, then it's a catch. But let's say that instead of just standing there he gets drilled simultaneously? Now he doesn't have the "time" to protect himself. So no catch, even though he still secured the ball with both feet down. Now you could remove the time element, but now it goes from no catch to fumble.
Now onto "going to the ground". So if a receiver catches a ball but is in the act of going to the ground he has to maintain possession of the ball through contacting the ground. What this means is if the player, with or without contacting another player, ends up on the ground during the act of catching the ball, BEFORE having the ability to protect themselves. Or as the rule is currently written, to establish themselves as a "runner". Back to intent.
Example: WR dives to catch a ball. In mid air he catches the ball, then while still falling his knee and elbow hits the ground and it jars the ball out. The player did not have a chance to protect himself. Now you could remove the "become a runner" or "make a football move" and call that a catch and fumble. But do we want to open that up to the potential risk of having more fumbles?
What muddies the water even more are how athletic these guys are. Some catches where any average person would go to the ground immediately, these guys are able to somewhat regain their balance and get a few steps in before they actually do hit the ground. But do we remove the protection from them just because they take a few steps or shift the ball from one hand to another. If while doing all of this, still ultimately on their way to the ground, somehow they loose control of the ball. Do we call that a fumble just because they briefly controlled the ball and had two feet down? That's one of the aspects the NFL has and is struggling with when trying define this particular part of the rule. Weighing protecting the receiver from unforced fumbles vs making it a catch.
So what to do to fix it? Rewrite the rules to allow for more of the controversial non catches to be catches at the peril of also introducing a much greater chance for fumbles? Or leave things exactly as is with minor corrections to the language in the rule and simply tell receivers that they have to hang on to the ball if they are going to the ground while in the act of catching the ball?
I would love to hear the proposals for any rule change. But remember, it can't just be in the context of the Dez catch or any one specific example. It has to be in the context of how the rule change would impact every type of catch.