From the moment the league office overturned two key fourth-quarter rulings in the Week 14 Steelers-Ravens game, the countdown started for Sunday morning. What would NFL officiating messenger Walt Anderson say, or not say, on NFL Network about the Aaron Rodgers “catch” and the Isaiah Likely “non-catch”?
And, more importantly, would Anderson be given enough time in the four-hour show to address all of the controversial calls from the game, including the unnecessary roughness penalty on a field-goal attempt that the league privately told the Ravens was a mistake?
As to the last question, the answer was no. Despite the importance of the issue to the actual and perceived integrity of the game, Anderson spoke for fewer than two minutes of the 240-minute show, addressing only one of the three very controversial calls from Pittsburgh at Baltimore.
Here’s what he said about the decision to reject the real-time ruling from the on-field officials that Likely had completed the catch process, for what would (should) have been a go-ahead touchdown with 2:47 to play.
“There’s three elements that have to be satisfied,” Anderson said, “Control of the football. And then two steps or a body part. And so he gets control, he takes two steps. What are we now looking for? And the rule is very specific. After those first two, you’ve got to have that third element. And the most common element for receivers that are running is a third step with control of the ball. As you can see here, before that third step gets down, the defender is able to punch the ball out. That’s why the pass is incomplete.”
If we’re only focusing on a third foot as the way to satisfy the third element, Anderson isn’t wrong. The problem is that, as we explained at the time, the replay process has focused on three feet down to the exclusion of the other ways to perform an act common to the game: “extend[ing] the ball forward, . . . tuck[ing] the ball away and turn[ing] upfield, or avoid[ing] or ward[ing] off an opponent.”
Anderson did not address, and was not asked to address, whether Likely had extended the ball forward or warded off an opponent. To overturn the ruling of a touchdown, the replay process requires (as the rules are written) clear and obvious evidence that Likely had done neither of those things.
“We can keep arguing about this for a long time,” Steve Mariucci said after Anderson explained the Likely ruling. “What is a football move?”
And then there was no discussion whatsoever about the other side to the argument. No mention of whether Likely had, or hadn’t, made a football move/act common to the game. More importantly (and more on that in a second), there was no reference to whether Likely had possession of the ball long enough to do so.
Anderson also made no effort to reconcile the replay ruling on the Aaron Rodgers “catch” with the Likely ruling, probably because Anderson and the rest of the league office know that the decisions cannot be reconciled. If Rodgers caught the ball, then Likely did, too.
Anderson instead addressed a play from Thursday night’s Falcons-Buccaneers game. The catch and fumble by Falcons running back Bijan Robinson.
“These plays are very, very similar, except for that third element,” Anderson said. “And so what you can see here is Bijan Robinson gets control of the ball, he gets two steps, and then what he’s able to do, because that left is one, the right is two, the left foot comes down again. That’s the third step, and then he loses the ball. So he’s completed all three elements of the catch process. That’s why this is a catch and in this case a fumble. Had Likely got that third step down while he maintained control of the ball because he was in the end zone, it would have been a touchdown because by rule then the ball would be dead in the end zone.”
Again, they’re focusing only on the third foot and ignoring the rest of the rule, both as to performing an act common to the game and having the time to do so.
Consider this, and watch the Robinson play at full speed, not in slow-motion. If Robinson had possession of the ball long enough to perform an act common to the game (by rule, take a third step among other things), didn’t Likely have possession of the ball long enough to perform an act common to the game?
Even if we ignore the fact that Likely was extending the ball and/or warding off an opponent (and it’s not clear and obvious he wasn’t), Likely had it long enough to, for instance, “tuck the ball away and turn upfield.” But Likely had no reason to do that, because: (1) he was in the end zone; and (2) he was trying to keep the ball away from a defender who was literally attached to his back and trying to knock out the ball.
Here’s the bottom line. Whoever is making the decisions about replay review in the league office (and many throughout the league don’t know who that is at any given moment) has decided to hinge the catch decision on getting three feet down, and to disregard the rest of the rule as it relates to performing an act common to the game, or having enough time to do so.
That’s the inescapable message, both from last week’s ruling and Anderson’s Sunday morning explanation of it. The league office has gone rogue as to the catch rule (and the replay standard), ignoring language that was adopted by a 75-percent supermajority vote of ownership.
At this point, the only way to fix the problem will be for the owners to take control of the situation, if necessary reminding the employees of the league office who writes the checks — and who cashes them.
