The Worst Referee Calls in NFL History

The National Football League (NFL) is unparalleled when it comes to excitement and competition. However, with such high stakes in every game, it is inevitable that controversial calls by referees can have a significant impact on the outcome of matches. Referee decisions shape the narratives of games, and unfortunately, some of these calls have gone down in history as some of the worst ever made. Below, we will explore a selection of Worst Referee Calls in NFL History, examining the context and repercussions of each call.

1. The No-Call in the 2018 NFC Championship Game

Worst Referee Calls in NFL History

One of the most talked-about officiating blunders occurred during the 2018 NFC Championship Game between the Los Angeles Rams and the New Orleans Saints. Late in the fourth quarter and with the Saints driving for what could have been a game-winning touchdown, a crucial play unfolded. Quarterback Drew Brees threw a pass to wide receiver Tommylee Lewis, who was leveled by Rams cornerback Nickell Robey-Coleman before the ball even arrived. Despite the obvious contact and the clear interference, the referees failed to throw a flag. This glaring error left the Saints to settle for a field goal instead of what could have been a definitive touchdown. The Rams subsequently mounted a game-tying drive and ultimately won the game in overtime. The ramifications of this no-call were tremendous. It not only knocked the Saints out of a Super Bowl berth, but it also led to widespread calls for changes to the NFL’s officiating rules, including the ability for teams to challenge certain pass interference calls.

2. The “Tuck Rule” Play

Worst Referee Calls in NFL History

The Tuck Rule has been a source of contention since its implementation; however, it reached its zenith during the 2001 AFC Divisional Playoff game between the Oakland Raiders and the New England Patriots. In a critical moment in the fourth quarter, Patriots quarterback Tom Brady dropped back to pass but was hit by Raiders cornerback Charles Woodson. The ball was knocked loose, and everyone expected the Raiders to recover, sealing the victory. Instead, the referees reviewed the play based on the “Tuck Rule,” which determined that if a quarterback’s arm was moving forward when the ball was lost, it was considered an incomplete pass, not a fumble. The call was upheld, allowing the Patriots to retain possession. This pivotal decision not only altered the course of the game, allowing the Patriots to proceed downfield and tie the score, but it later paved the way for New England’s Super Bowl victory. Fans still debate the legitimacy of the call, with many wishing the “Tuck Rule” had never existed.

3. The Fail Mary Incident

Worst Referee Calls in NFL History

In 2012, the infamous Fail Mary game occurred on a Monday Night Football matchup between the Seattle Seahawks and the Green Bay Packers. The match was marred by an ongoing referee lockout, resulting in replacement officials taking over officiating duties. The game reached a climactic moment when Seahawks quarterback Russell Wilson launched a Hail Mary pass into the end zone with no time left on the clock. Packers defensive back M.D. Jennings and Seahawks receiver Golden Tate both went up for the ball. One official ruled it a touchdown for Tate, while another signaled an interception for Jennings. The confusion and misinformation led to one of the worst calls in NFL history being recorded in the official scoresheet. The Packers were robbed of an apparent game-winning interception, and the NFL received a barrage of criticism as a result. The “Fail Mary” incident underscored the inherent risks of utilizing replacement referees and ultimately led to the swift reinstatement of the regular officials.

Read More: 5 Best Canadian NFL Players to Watch

4. The Calvin Johnson Incomplete Catch

Worst Referee Calls in NFL History

In 2010, Detroit Lions wide receiver Calvin Johnson secured what looked to be a phenomenal touchdown catch against the Chicago Bears. Johnson made a stunning grab in the end zone, held the ball while falling to the ground, but as he got up to celebrate, the ball slipped from his control. The referees ruled that Johnson had not completed the catch as per the catch rule that dictated a receiver must maintain possession while going to the ground. This call resulted in a lengthy discussion about the definition of a catch in the NFL, leading to multiple revisions of the rule in subsequent years. The judgment call hurt the Lions that day and not only contributed to their loss but also sparked outrage among fans and analysts alike. Many felt the ruling was a misinterpretation of the rules, which would haunt the team and its fan base for years.

5. The Des Bryant No Catch

The Des Bryant No Catch

During the 2014 NFC Divisional Playoff between the Dallas Cowboys and the Green Bay Packers, wide receiver Dez Bryant appeared to catch a crucial pass on a drive with just under five minutes left. However, the catch was contested, and after review, the referees ruled that Bryant did not complete the catch, as he failed to maintain control of the ball while going to the ground. The ruling sparked an intense debate about what constitutes completing a catch and reignited conversation about the inconsistencies plaguing officiating in the NFL. The Cowboys lost the game and were eliminated from playoff contention, leaving fans and players frustrated with yet another controversial call. This incident ultimately contributed to continued scrutiny of the league’s officiating standards and rules regarding catches.

6. The Houston Oilers vs. Pittsburgh Steelers—The Renfro Incident

 The Houston Oilers vs. Pittsburgh Steelers—The Renfro Incident

In a 1979 playoff game, the Houston Oilers faced the Pittsburgh Steelers with a chance to tie the game in the final moments. Oilers receiver Billy White Shoes Johnson caught a pass and appeared to give the team a touchdown; however, side judge Donald Orr ruled that Oilers receiver Mike Renfro had not gotten both feet down inbounds, negating the score. Despite contentious debate over whether Renfro had, in fact, made the catch, the call stood, and the Oilers lost 27-13. This ruling left a bitter taste for Oilers fans, who believed their team was robbed of the chance to play in their first Super Bowl. The game demonstrated how a single decision from an official can drastically alter the course of a team’s legacy and future.

7. The Snowplow Game of 1982

The Snowplow Game of 1982

Perhaps one of the most bizarre moments in NFL history occurred during a game between the Miami Dolphins and New England Patriots on December 12, 1982, known as the Snowplow Game. With the field covered in snow and under difficult conditions, Patriots coach Ron Meyer ordered a snowplow driver to clear a spot on the field for kicker John Smith to make a field goal attempt. Despite the comical nature of the situation, Meyer’s tactics were deemed controversial, and the referees ultimately allowed the attempt. The Patriots won the game 3-0, and Dolphins coach Don Shula expressed his outrage, leading to concerns about the integrity of officiating and the use of such tactics on the field. The incident demonstrates the sometimes unconventional problems that officials face when making decisions.

Conclusion

Officiating mistakes are an unfortunate part of sports, and the NFL has had its share of infamous calls that have had lasting effects on games, teams, and the league as a whole. From the controversial “No Call” in the NFC Championship Game to the bizarre tactics of the “Snowplow Game,” these instances highlight the human element of officiating and how subjective decisions can lead to significant consequences. While the NFL continues to evolve its rules and increase the involvement of technology in officiating, the memories of these blunders remain embedded in the minds of fans and players alike. Maintaining an objective and consistent approach in officiating is essential for the league’s credibility, and these historic missteps serve as important lessons for the future.

Abeer Jawad

Leave a Reply

Your email address will not be published. (required)