Now THAT was a Stupid play By Seattle

Search

Member
Joined
Dec 12, 2006
Messages
16,073
Tokens
I guess we'll see in the next few days if the NFL issues a "we're sorry we fucked you Detroit" apology.
 

New member
Joined
Oct 29, 2010
Messages
40,880
Tokens
I guess we'll see in the next few days if the NFL issues a "we're sorry we fucked you Detroit" apology.

Risk 1,080 to win 1000 on Detroit +9.5

Risk 300 to win 1,305 on Detroit moneyline

I would also like an apology from NFL
 

Member
Joined
Jul 14, 2007
Messages
31,656
Tokens
I thought he said half distance from original LOS, but if it was half distance from where the fumble was then wow.

Seattle getting lucky.
 

Member
Joined
Dec 12, 2006
Messages
16,073
Tokens
I don't know about that. Detroit did nothing offensively until that last drive.

You don't think they tie it up at the very least?

Detroit moved the ball at will on Sea that last drive.

What exactly did Sea do on offense besides get sacked time and time again?

Take away that last long pass by Sea and they didn't do shit.
 

Banned
Joined
Sep 21, 2004
Messages
15,948
Tokens
You don't think they tie it up at the very least?

Detroit moved the ball at will on Sea that last drive.

What exactly did Sea do on offense besides get sacked time and time again?

Take away that last long pass by Sea and they didn't do shit.

Oh yeah. On the last drive they moved it at will, because Wilson's fumble gave them life. Neither team did much Offensively, but to say Detroit looked better than Seattle all night is what I'm disagreeing with.
 

Banned
Joined
Sep 21, 2004
Messages
15,948
Tokens
Now, the NFL in CYA mode is saying that the back judge discussed it and said the Seattle player didn't "Overtly" bat the ball. Wow, just wow. Just admit he blew the call and move on. Don't compound it with nonsense.
"A player may not bat or punch: (a) a loose ball (in field of play) toward opponent's goal line; (b) a loose ball (that has touched the ground) in any direction, if it is in either end zone; (c) a backward pass in flight may not be batted forward by an offensive player."
 

Breaking News: MikeB not running for president
Joined
Dec 19, 2011
Messages
13,179
Tokens
Bat of loose ball by K.J. Wright should have been flagged

Posted by Mike Florio on October 5, 2015, 11:44 PM EDT
Getty Images
Setting aside for now (but not for long) how themost unfair rule in football gave possession of the ball to the Seahawks even though they never recovered the football fumbled by Lions receiver Calvin Johnson, the decision of Seattle linebacker K.J. Wright to bat the ball out of the end zone should have given possession back to the Lions.
As explained by ESPN rules analyst Gerry Austin after the game (and confirmed to ESPN by NFL V.P. of officiating Dean Blandino), Wright committed an illegal bat that should have given the ball back to the Lions at the spot where they lost possession, with the ball moved half the distance to the goal line.
Rule 12, Section 4, Article 1(b) applies the term “illegal bat” when “any player bats or punches a loose ball (that has touched the ground) in any direction, if it is in either end zone.”
So even though the rule that gives possession to the defense when the offense fumbles the ball in the field of play and it goes out of the end zone needs to be changed, a rule change wasn’t needed here. With Wright knocking the ball out of the end zone, the ball should have been given back to the Lions, on the fringe of the end zone.
Amazingly, the non-replacement officials missed the call, a little more than three years after replacement officials missed an offensive pass interference foul that allowed the Seahawks to steal a late win over the Packers on a Monday night.

CQmtHE0VEAUTXsA.jpg





 

Banned
Joined
Nov 4, 2009
Messages
12,115
Tokens
Now, the NFL in CYA mode is saying that the back judge discussed it and said the Seattle player didn't "Overtly" bat the ball. Wow, just wow. Just admit he blew the call and move on. Don't compound it with nonsense.

Oh he overtly batted it. The only way he could have MORE overtly batted it is if he'd turned it into a Musical and sang out "Ahm gunna bat dis ball da fug on out" as he batted it out.
 

Member
Joined
Dec 12, 2006
Messages
16,073
Tokens
Oh yeah. On the last drive they moved it at will, because Wilson's fumble gave them life. Neither team did much Offensively, but to say Detroit looked better than Seattle all night is what I'm disagreeing with.


Det completely dominated the o-line of Sea. They sacked Wilson 6 times and hit him constantly. They forced him into 2 fumbles, one returned for a TD. Sea played better on offense, but that isn't saying much.

Sea was fortunate to win the game after that blown call at the end of the game.
 

Member
Joined
Dec 12, 2006
Messages
16,073
Tokens
Now, the NFL in CYA mode is saying that the back judge discussed it and said the Seattle player didn't "Overtly" bat the ball. Wow, just wow. Just admit he blew the call and move on. Don't compound it with nonsense.
"A player may not bat or punch: (a) a loose ball (in field of play) toward opponent's goal line; (b) a loose ball (that has touched the ground) in any direction, if it is in either end zone; (c) a backward pass in flight may not be batted forward by an offensive player."


I agree. They need to look up the word overtly in the dictionary. The player clearly knocked the ball out with his hands.
 

Member
Joined
Jan 21, 2008
Messages
5,077
Tokens
These batting the ball penalties happen every week on onside kicks yet no one on ESPN has ever heard of this call?
 

Banned
Joined
Sep 21, 2004
Messages
15,948
Tokens
Blandino: “Judgment call on the field. Back judge felt it wasn’t overt. That’s why he didn’t call it on the field."

"A player may not bat or punch: (a) a loose ball (in field of play) toward opponent's goal line; (b) a loose ball (that has touched the ground) in any direction, if it is in either end zone; (c) a backward pass in flight may not be batted forward by an offensive player."

I don't see the word "Overt" anywhere in the rule.
 

New member
Joined
Dec 16, 2011
Messages
13,268
Tokens
Blandino: “Judgment call on the field. Back judge felt it wasn’t overt. That’s why he didn’t call it on the field."

"A player may not bat or punch: (a) a loose ball (in field of play) toward opponent's goal line; (b) a loose ball (that has touched the ground) in any direction, if it is in either end zone; (c) a backward pass in flight may not be batted forward by an offensive player."

I don't see the word "Overt" anywhere in the rule.

The outcome is known.....just need the actors to make it real
 

Member
Joined
Jan 21, 2008
Messages
5,077
Tokens
I agree with no flag in that situation. The refs screw up a lot but taking away a Seattle win over a play where batting the ball gave the Seahawks zero advantage would have been a far worse situation
 

Member
Joined
Jul 14, 2007
Messages
31,656
Tokens
Blandino: “Judgment call on the field. Back judge felt it wasn’t overt. That’s why he didn’t call it on the field."

"A player may not bat or punch: (a) a loose ball (in field of play) toward opponent's goal line; (b) a loose ball (that has touched the ground) in any direction, if it is in either end zone; (c) a backward pass in flight may not be batted forward by an offensive player."

I don't see the word "Overt" anywhere in the rule.

Well it would have to be overt (it was)

Obviously guys could be running for a ball and neither gets it, but their contact makes it go out.
 

Forum statistics

Threads
1,119,946
Messages
13,575,480
Members
100,886
Latest member
ranajeet
The RX is the sports betting industry's leading information portal for bonuses, picks, and sportsbook reviews. Find the best deals offered by a sportsbook in your state and browse our free picks section.FacebookTwitterInstagramContact Usforum@therx.com