We all know it’s lame for sports fans to complain about refs. Generally speaking, calls go both ways. And if you’re in a position to have a single call make or break you, you haven’t done enough to win the game.
And yet…
The overturned Ravens touchdown on Sunday’s game against the Steelers was a particularly brutal act of referee malfeasance. Even if you never complain about refs, we’ll make an exception and allow you to in this case. Had the refs not reversed that call, the Ravens would have won the game, simple as that.
To recap: With the Ravens down 27 to 22, and with all the momentum on their side, Lamar Jackson threw a 13-yard pass to tight-end Isaiah Likely who caught it, took three steps, and then dropped the ball. Boom. Ravens touchdown. 29-27 Ravens, with 2:47 left to play and our defense on fire.
There was such pandemonium in the stadium that people didn’t even hear—or comprehend—when referee Alex Moore overturned the call. (It didn’t help that his mic was broken due to “technical difficulties,” the NFL said.)
He said no touchdown, because the receiver needed to take a third step and make a “football move”—aka one of the most subjective terms in football.
As many pointed out on social media, why does a player need to make a “football move” when he’s already in the end zone?
Announcers Tony Romo and Jim Nantz were flabbergasted. So were many folks on X. Let it all out, Baltimore!
And to the Steelers fans who admit that we were robbed (not that they’re complaining), mad respect for the solidarity.
The overturn of Likely TD is one of the worst calls in NFL history. — Jason Whitlock (@WhitlockJason) December 7, 2025
THAT WAS A TD CATCH BY LIKELY. HAD IT! RAVENS SHOULD'VE WON THAT GAME. — Skip Bayless (@RealSkipBayless) December 7, 2025
Watched and played a lot of football and that’s just not right. No way — Jameis Winston (@Jaboowins) December 7, 2025
This was ruled a Steelers touchdown Week 4.
Today this catch from Likely for the Ravens was not ruled a touchdown, spot the difference. https://t.co/vygk2nkkJz pic.twitter.com/HFk4OAzVvA — Rate the Refs (@Rate_the_Refs) December 7, 2025
Steelers bias aside,
This was a touchdown 😭😭😭
Sorry Ravens fans we just got good refs pic.twitter.com/g4c4h90cPV — PickensBurgh 🫡 (@PickensBurgh) December 7, 2025
Tony Romo: "To me, that seemed like a touchdown."
Jim Nantz: "I agree, Tony. Looked like a touchdown to me." 🏈🦓🎙️ #NFL pic.twitter.com/ADKPo5lT6z — Awful Announcing (@awfulannouncing) December 7, 2025
Stop. He’s in the end zone already! A football move as defined by this list is unnecessary at that point. This was an officiating failure. https://t.co/mWunY7VLct — Benjamin Watson (@BenjaminSWatson) December 7, 2025
Why do you have to make a football move in the end zone. Where is he moving? For more yards?!?!
Catch + 2 feet should be a TD. https://t.co/CKrEysxRyV — Hayden Winks (@HaydenWinks) December 7, 2025
just received an NFL officiating memo about this call.
They're saying that even though the receiver completed all the necessary elements for a catch, replay officials "thought it looked kinda weird" and noted that "it just felt wrong idk" and overruled based on those reasons https://t.co/Oc1P5siyLF — Rodger Sherman (@rodger) December 7, 2025
I’ve watched this 50 times and still don’t get how this isn’t a TD. Ravens end up not scoring — one of the worst calls I’ve ever seen. Complete officiating malpractice. pic.twitter.com/IdSxUtd4jk — William Herman (@_williamherman) December 7, 2025
How was this not a catch for the Ravens??
Baltimore just got SCREWED by the refs 🤦♂️pic.twitter.com/vrlNEAlasZ — Dov Kleiman (@NFL_DovKleiman) December 7, 2025
