- - Richard Sherman, Shannon Sharpe, other NFL stars react to controversial Bills play: 'Can't believe this decided the game'

Chris Cwik January 19, 2026 at 2:13 AM

0

The Buffalo Bills have a bone to pick with the NFL. Following a controversial interception in overtime, Bills head coach Sean McDermott went on the offensive, calling out the ruling and the league following the Bills' 33-30 loss to the Denver Broncos in the divisional round of the playoffs.

Based on Sunday's reactions to the play, McDermott isn't the only one who believes the league got it wrong. A number of former NFL players and officials weighed in on the play, with many believing it should not have resulted in an interception.

The play in question occurred with 7:55 to play in overtime. With the Bills trying to drive down the field for a possible game-winning score, Josh Allen attempted to hit Brandin Cooks deep down the field on a 3rd and 11 pass.

Cooks appeared to catch the ball initially, but had it taken away by Broncos cornerback Ja'Quan McMillian as the pair went to the ground.

The play was ruled an interception fairly quickly, and the Broncos were given possession. The team then drove down the field and kicked a game-winning field goal, eliminating the Bills.

Former NFL cornerback — and current Amazon analyst — Richard Sherman was among those who believe the play should have been ruled a catch. Sherman said he's never seen a play like that "be called anything but a catch."

I have never seen a contested catch like this ever be called anything but a catch. Even as a DB you know that if it’s even a Tie it will go to the WR. Can’t believe this decided the game. https://t.co/EfrzgvSdcj

— Richard Sherman (@RSherman_25) January 18, 2026

Dan Orlovsky, who spent seven years in the NFL before joining ESPN, claimed the play should have been ruled "a catch every time."

Ten-year NFL veteran Marshall Newhouse also had a strong response to the play, saying it should have been ruled a catch or — at worst — an incomplete pass.

It’s after midnight and I’ve seen this play 30 times. I’m still livid at how this went down and feel horrible for the Bills.1) It’s a catch, tie goes to offense2) If not, at WORST it’s an incomplete pass3) It was ruled an int on the field, TAKE TIME AND REVIEW THE MFer! pic.twitter.com/C1phru2clx

— marshall newhouse (@MNewhouse73) January 18, 2026

The one former player who agreed with the call on the field was former Broncos star Shannon Sharpe, who recited the rule, which states a receiver must maintain possession throughout the catch.

Unc makes it simple. That McMillian interception holds up. The Calvin Johnson rule confirms it.@ShannonSharpe @ochocinco #Nightcap https://t.co/1WxIf85WNI pic.twitter.com/TgWnxus0kB

— Nightcap (@NightcapShow_) January 18, 2026

Former NFL official Gene Steratore — who said he believed it was an interception on the broadcast — gave a more detailed breakdown of the play Sunday morning.

Steratore cited the NFL rulebook, and then explained the exact reason the play resulted in an interception.

At some point when reviewing plays, the league should consider adding a speed threshold for anything involving the element of time. When you slow plays down to 1/100th the speed, it distorts what actually happened and makes it look like, in this case, Cooks possessed the ball… pic.twitter.com/CgEQqWaqp9

— Gene Steratore (@GeneSteratore) January 18, 2026

While Steratore states Cooks satisfied the first two qualifications of the rule, he determines Cooks did not maintain the ball long enough to perform a clear "act common to the game."

NFL rules analyst Walt Anderson agreed with that assessment, saying the ball was loose once Cooks hit the ground. Anderson argued that the play would have been ruled an incomplete pass if he hit the ground, but since it wound up in McMillian's arms, it was ruled an interception.

NFL rules analyst Walt Anderson on @NFLGameDay: “As the receiver’s going to the ground, as soon as he hits the ground, the ball is immediately loose. That would be an incomplete pass if comes out and hits the ground. Here, the ball never hits the ground.” pic.twitter.com/eQKdPAijyl

— Mike Garafolo (@MikeGarafolo) January 18, 2026

Terry McAulay, another former NFL official, also agreed with the ruling on the field of an interception.

The responses to me quoting the rule here are fascinating. To be clear, by rule, this is not a completed catch by the receiver. It’s an interception. https://t.co/BswEXpsOfe https://t.co/xEQPMj03eG

— Terry McAulay (@tjmcaulay) January 18, 2026

While the NFL rulebook seems to support how the play was called Saturday, some pointed out that the league acted differently on a similar call earlier in the season.

During a Dec. 7 contest, Aaron Rodgers was called for an interception after a ball he threw was tipped at the line of scrimmage.

Here's the problem with last night's overtime interception. On December 7, this was ruled an interception on the field. Replay review overturned it to a catch. NFL V.P. of instant replay Mark Butterworth defended the decision in a pool report. By January 17, the standard changed. https://t.co/ywixyyUj8O

— ProFootballTalk (@ProFootballTalk) January 18, 2026

But upon review, officials ruled Rodgers had possession of the ball when he hit the ground. The interception was overturned, with the Steelers retaining possession of the ball. Mike Florio of Pro Football Talk asked what changed between Dec. 7 and Saturday that resulted in the officials calling the play differently.

McAulay also weighed in on that play, saying that he believed the officials got it wrong earlier in the season. He shared a few tweets he made at the time suggesting the Rodgers play should have been ruled an interception.

By the NFL rulebook, the play was called properly Saturday night. That won't stop Bills fans from questioning the process, especially after another officiating crew called the play differently a month earlier.

Original Article on Source

Source: “AOL Sports”