The NFL's Catch Conundrum: Still a Mystery?
It's a question that has haunted football fans, coaches, and commentators for years: What exactly constitutes a catch in the NFL? This debate has resurfaced with a vengeance, once again leaving fans scratching their heads after a controversial play in the recent playoff game between the Buffalo Bills and the Denver Broncos, where the Broncos won 33-30.
In overtime, Josh Allen's pass to Brandin Cooks was wrestled away by Ja’Quan McMillian, leading to a turnover. The officials ruled that McMillian secured the ball before Cooks was down. This decision, which effectively ended the Bills' playoff hopes, sparked immediate controversy.
Referee Carl Cheffers explained that Cooks lost possession as he hit the ground, and the defender completed the catch. Bills coach Sean McDermott, unable to challenge the call due to overtime rules, could only seek an explanation. He expressed frustration over the perceived rushed review process, highlighting that similar plays in regular-season games often receive more in-depth scrutiny.
But here's where it gets controversial... McDermott's frustration wasn't just about the loss; it was about the swiftness of the decision-making process during such a crucial moment in the game. He felt that the pivotal play deserved more thorough review.
Retired cornerback Richard Sherman, a three-time All-Pro, weighed in on social media, stating that such contested catches are almost always ruled in favor of the receiver. ESPN analyst Dan Orlovsky echoed this sentiment, calling the ruling an interception in a playoff game a season-ending decision.
Similar plays have had different outcomes in the past, adding to the confusion. For instance, a play in a Ravens-Steelers game saw a batted ball end up in Aaron Rodgers' hands, only to be stripped by Teddye Buchanan, initially resulting in an interception. However, the call was overturned because Rodgers had control before going to the ground. Conversely, in a Week 12 game, Cobie Durant of the Rams ripped the ball from Buccaneers tight end Cade Otton as he was going down, resulting in an interception and touchdown, even though Otton appeared to have a knee down.
And this is the part most people miss... This isn't the first time a catch definition has caused a playoff uproar. Remember the Dez Bryant non-catch in the 2015 divisional-round game? That play led to rule clarifications and eventually a 2018 overhaul, removing the "survive the ground" element from the definition.
So, what is a catch, according to the rule book?
Here's the official definition:
A forward pass is complete (by the offense) or intercepted (by the defense) if a player, inbounds:
- Secures control of the ball in their hands or arms before the ball touches the ground.
- Touches the ground inbounds with both feet or any body part other than their hands.
- After fulfilling the above, clearly performs an act common to the game (e.g., extend the ball forward, take an additional step, tuck the ball away and turn upfield, or avoid or ward off an opponent), or maintains control long enough to do so.
Important Notes:
- Movement of the ball doesn't automatically mean loss of control.
- If a player satisfies the first two conditions but loses control while contacting the ground, it's an incomplete pass.
The rule book also covers simultaneous catches:
- If two eligible players catch a pass at the same time and both retain it, the offense gets the ball.
- It's not a simultaneous catch if one player gains control first.
- If the ball is fumbled after simultaneous touching, all offensive players become eligible to catch it.
The Bottom Line:
Defining a catch can be complex, often difficult to discern in real-time and even on replay.
What do you think? Did the officials get the call right in the Bills-Broncos game? Do you think the NFL's catch rule is clear enough, or does it still need more work? Share your thoughts in the comments!
