The reason this one is so bizarre is because the ruling being wrong on the field actually cost the Lions a chance to line up for another play, which directly led to the loss. The Lions had no timeouts left, which means an automatic 10-second runoff was applied, and the Lions lost the game by four with the ball on the 1-yard line.
It was ruled a TD on the field, but the review overturned the call. This is actually an example of the officials getting right and the Lions being hurt by the rules themselves.Īgainst the Atlanta Falcons in Week 3 2017, the Lions scored what appeared to be a game-winning touchdown against the Falcons with nine seconds left. But instead, the Lions didn't get an opportunity with the ball and the Seahawks went on to win. Wright should have incurred a penalty and the Lions should have gotten the ball back on the 1-yard line. That batted ball, however, is against the rules. MORE: Vikings' special teams play nets Minnesota win vs. Wright, leading to a touchback for the Seahawks. On "Monday Night Football," Calvin Johnson fumbled a ball into the end zone that was batted out of the back of the end zone by K.J. The Lions have encountered controversy against the Seattle Seahawks before. Needless to say, the rule that a challenge flag nullifies a review no longer exists. Bizarrely, that NULLIFIED the automatic review on all scoring plays, and the Texans were granted the touchdown. It was egregiously clear Forsett was down, but Jim Schwartz was so zealous to challenge the play he threw his challenge flag on the field. On Thanksgiving in 2012 when the Lions were taking on the Houston Texans, Detroit was up 24-14 in the third quarter when Texans running back Justin Forsett went down, got up, and just - for some surreal reason - got up and ran it into the end zone. You know a situation is controversial when it leads to a rule change. What followed was about six years of hemming and hawing of people wondering "what even is a catch?" That rule has come into some degree of focus in recent years, but this was the perhaps the most high-profile and consequential play the Lions were a part of. The ball came out as Johnson pushed himself back up, and the officials ruled Johnson didn't "complete the process." The question came to the forefront of the league in 2010, when Calvin Johnson scored what looked like a go-ahead touchdown catch with 24 seconds left in the game against the Bears. The poster child for confusing NFL rules is "what is a catch?" Detroit Lions controversies Completing the process - What is a catch? Here's a quick look at some of the Lions' "greatest hits," so to speak. Every NFL team has had calls go against it over the years, of course, but the Lions' track record of it happening is shockingly extensive.
It's the kind of thing that can seemingly only happen to the Lions. The Seahawks went on to win the game 48-45, and that touchdown proved to be the difference in the game. The crowd, naturally, was absolutely irate after the confusing do-over. What would normally be an annoyance immediately became a disaster, as Rashaad Penny broke off a 36-yard touchdown run to make it 38-23 Seahawks. Instead of it being fourth-and-16 after the incompletion, referee Clay Martin announced they would replay the down because the clock wasn't properly set on the previous play. The officiating crew, however, congregated shortly after and conversed about the prior play. Smith spiked an incompletion on what looked like a miscommunication with his receivers, and it looked like the Lions were going to get the ball back in a one-possession game. With the Seahawks already up 31-23 late in the third quarter, Geno Smith's offense was facing a third-and-16 after an intentional grounding penalty. Detroit Lions fans, stop reading if you'd heard this before: The Lions were the victims of questionable officiating.
0 kommentar(er)
