Week 13 NFL Game Thread

joe dokes

Member
SoSH Member
Jul 18, 2005
32,681
I thought the Raiders strategy was good, honestly. Throw over the middle for 5-10, then spike it. 15 seconds is enough time to safely do that.
It was 3rd down, so no spike after the play if they dont get a 1st down or get sacked. That would be an even more Eberflussian failure.

Pierce said they were trying to just throw it OOB on the botched play so KC would have less time after the FG.

https://www.espn.com/nfl/story/_/id/42686817/raiders-crushed-botched-snap-kills-upset-bid-chiefs

Still, Raiders coach Antonio Pierce wanted to run one more play -- a pass to be thrown away so that Las Vegas, which was out of timeouts, could eat more time off the clock before giving the ball back to the Chiefs and quarterback Patrick Mahomes.
 

cornwalls@6

Less observant than others
SoSH Member
Apr 23, 2010
6,608
from the wilds of western ma
Despite the cluster fuck of officiating at the end, this is all on Pierce. You kick the field goal on third down. Period. Full stop. Then you play defense for a few seconds, and go home with a win. I don’t care who the opposing QB is. The kick(despite the day he was having) was well within his range, and you had virtually nothing to lose. Just inexcusably bad/scared coaching. Worthy of an Eberflusing.
 

Ferm Sheller

Member
SoSH Member
Mar 5, 2007
22,606
No way the Raiders K would have made that FG anyway. Either lose the way they did or on a shank, what's the difference?
 

CoffeeNerdness

Member
SoSH Member
Jun 6, 2012
9,736
Also, they didn't get the throw the ball away play call into the huddle until 12 seconds were on the play clock and they broke the huddle with 9. So dumb. They fawned over the father son Turner duo all game and in the end they absolutely shit the bed over basic clock management.
 

Remagellan

Well-Known Member
Lifetime Member
SoSH Member
Despite the cluster fuck of officiating at the end, this is all on Pierce. You kick the field goal on third down. Period. Full stop. Then you play defense for a few seconds, and go home with a win. I don’t care who the opposing QB is. The kick(despite the day he was having) was well within his range, and you had virtually nothing to lose. Just inexcusably bad/scared coaching. Worthy of an Eberflusing.
This. What is the fear? I understand the "13 seconds" legacy is there, but you're likely leaving him 8-10 seconds after the kickoff, and even if Mahomes should get his kicker in range, Matthew Wright is not Harrison Butker. Carlson might miss the kick, but if he does that's on him. This is on the coach.
 

CoffeeNerdness

Member
SoSH Member
Jun 6, 2012
9,736
I don’t even see an illegal shift. Illegal formation, maybe, and it looked like a false start as well. The ref down bottom also threw a flag, but not to stop the clock. However, whenever one ref runs in to stop the play, it has to be honored, even if he got the call wrong (which I don’t even think happened). That was a big fuckup.

I thought the Raiders strategy was good, honestly. Throw over the middle for 5-10, then spike it. 15 seconds is enough time to safely do that.
It's impossible to tell from the one replay what caused the flags.

The broadcast missed the snap. You can see O'Connell's eyes widen before they cut to the wider angle.

92463

No flags thrown as the ball is under AOC >
92464

First flag gets thrown by the guy at the bottom of the screen>
92465

Ref at the top throws his flag a split second before its recovered>
92467
 

Attachments

CoffeeNerdness

Member
SoSH Member
Jun 6, 2012
9,736
Whether or not there was a flag, LV fumbled and KC recovered. The penalty was inconsequential.
I think some are saying that KC was aided in recovering the ball because the whistle caused players to stop playing and I don't believe the replay shows that to be the case.
 

CFB_Rules

Member
SoSH Member
Nov 29, 2016
1,787
It's impossible to tell from the one replay what caused the flags.

The broadcast missed the snap. You can see O'Connell's eyes widen before they cut to the wider angle.

View attachment 92463

No flags thrown as the ball is under AOC >
View attachment 92464

First flag gets thrown by the guy at the bottom of the screen>
View attachment 92465

Ref at the top throws his flag a split second before its recovered>
View attachment 92467
In the second screenshot the official is already running onto the field shutting the play down. The timing of the flag isn’t really relevant
 

CFB_Rules

Member
SoSH Member
Nov 29, 2016
1,787
Whether or not there was a flag, LV fumbled and KC recovered. The penalty was inconsequential.
The flag was for a dead ball foul. The whistle was blown simultaneously with the snap, the snap didn’t happen by rule. And then the officials changed their minds and allowed dead ball action to be treated as live ball
 

Humphrey

Member
SoSH Member
Aug 3, 2010
3,420
Was there a Hamlin type injury delay? What’s taking this game so long? (Started at 4:35,
Right?)
They shouldn't allow Alan Eck and his flag happy crew near any game where at least one team sucks (Pats Sunday, Bears Thursday). Makes the game interminable. What the teams don't do to earn penalties we'll just make sure we call anyway.
 

Remagellan

Well-Known Member
Lifetime Member
SoSH Member
I think some are saying that KC was aided in recovering the ball because the whistle caused players to stop playing and I don't believe the replay shows that to be the case.
That was my take as well. The Raiders weren't standing around while the Chiefs recovered the ball. They were trying just as hard to recover it.
 

Remagellan

Well-Known Member
Lifetime Member
SoSH Member

Ed Hillel

Wants to be startin somethin
SoSH Member
Dec 12, 2007
48,613
Here
It was 3rd down, so no spike after the play if they dont get a 1st down or get sacked. That would be an even more Eberflussian failure.

Pierce said they were trying to just throw it OOB on the botched play so KC would have less time after the FG.

https://www.espn.com/nfl/story/_/id/42686817/raiders-crushed-botched-snap-kills-upset-bid-chiefs
It was 3rd and 3, which is why throwing it 5-10 yards works. If everyone is covered past the sticks, just throw it away, but KC is undoubtedly covering the sidelines and a 5-10 yard catch should be easy enough. Imo you are at a spot on the field where those 5-10 yards matter, especially given your kicker issues, and it was worth it

Just throwing it OOB for less time is stupid though lol (way too risky for minimal gain), so Pierce is an idiot for that.
 
Last edited:

Ed Hillel

Wants to be startin somethin
SoSH Member
Dec 12, 2007
48,613
Here
Except one ref clearly signaled FALSE START while running in and blowing the play dead and not illegal procedure. The entire ref crew stopped reffing at that point, and half the players stopped moving. Live ball foul, the ref stays out wide and continues to officiate.

Maybe this one ref fucked up by thinking a play that shouldn’t have been blown dead should have been, but once he runs in refs need to own that mistake (or just call a false start) and not fuck over one team to cover for their mistake.
 

Ed Hillel

Wants to be startin somethin
SoSH Member
Dec 12, 2007
48,613
Here
It's impossible to tell from the one replay what caused the flags.

The broadcast missed the snap. You can see O'Connell's eyes widen before they cut to the wider angle.

View attachment 92463

No flags thrown as the ball is under AOC >
View attachment 92464

First flag gets thrown by the guy at the bottom of the screen>
View attachment 92465

Ref at the top throws his flag a split second before its recovered>
View attachment 92467
As long as a single ref is running in calling for a false start and blowing the play dead, refs are required to honor it and follow suit. It’s a great rule of thumb, because otherwise you end up with chaos like this. One ref was clearly doing that.

The refs fucked up and the NFL is covering for them by obfuscating what in theory could/should have happened with what actually did. Orwellian.
 

CFB_Rules

Member
SoSH Member
Nov 29, 2016
1,787
As long as a single ref is running in calling for a false start and blowing the play dead, refs are required to honor it and follow suit. It’s a great rule of thumb, because otherwise you end up with chaos like this. One ref was clearly doing that.

The refs fucked up and the NFL is covering for them by throwing the ref who was blowing the play dead under the bus.
IMO the only remedy isn’t to enforce a false start, which you really can’t have by rule. Just have to admit that you shut it down in error, there is no play and no foul. Just gotta eat it.
 

Ed Hillel

Wants to be startin somethin
SoSH Member
Dec 12, 2007
48,613
Here
IMO the only remedy isn’t to enforce a false start, which you really can’t have by rule. Just have to admit that you shut it down in error, there is no play and no foul. Just gotta eat it.
Well you can still false start in theory and one dude was waving his arms and the outside WR might have also moved (?), so why not just call that? I’m saying instead of illegal procedure, just call it a run of the mill false start. That’s still a dead ball foul, it’s just the illegal procedure that is not, right?

I’m just saying that’s a way of getting around admitting an error on the field that is probably most equitable in the given situation. 5 yards back and play is dead.
 

Mystic Merlin

Member
SoSH Member
Sep 21, 2007
49,575
Hartford, CT
The clock wasn’t running on third down because O’Connell spiked the ball on second down.

This is irrelevant anyways because CFB Rules is correct - they blew the whistle because the guy thought it was a false start or it was inadvertent. If it’s a live ball illegal shift you throw the flag, you aren’t gonna blow the play dead. The NFL knows they fucked it up but it’s convoluted enough, and the coverage of the game I’ve seen has largely ignored this controversy enough, that they can handwave it.
 

CoffeeNerdness

Member
SoSH Member
Jun 6, 2012
9,736
Yeah they’re not lying about the rule, they are lying about what they called
OR, the ref at the top of the screen fucked up because he forgot the difference between the clock being stopped and the clock being live? Do we think that the ref at the bottom was calling a different penalty because he threw his flag - presumably - for the exact same penalty, but didn't run on to the field to try and stop the play because he remembered the rule? Ref at the top of the screen fucked up, they huddle up and came to the correct conclusion. It's also not clear if it was an errant whistle because on the one replay there's no audible whistle until the ball is recovered.

Without a replay that shows exactly what happened from a different angle then this conversation is just spinning in circles.
 

CFB_Rules

Member
SoSH Member
Nov 29, 2016
1,787
OR, the ref at the top of the screen fucked up because he forgot the difference between the clock being stopped and the clock being live? Do we think that the ref at the bottom was calling a different penalty because he threw his flag - presumably - for the exact same penalty, but didn't run on to the field to try and stop the play because he remembered the rule? Ref at the top of the screen fucked up, they huddle up and came to the correct conclusion. It's also not clear if it was an errant whistle because on the one replay there's no audible whistle until the ball is recovered.
The official at the bottom was calling it correctly and the official at the top was not. That is not really in dispute. But the problem is the official at the top called a dead ball foul. The play is dead. The whistle was blown / the ball was signaled as dead. It doesn’t matter if it’s right or wrong, the play is still dead.

Once you carry out the death penalty you can’t bring someone back just because you made a mistake, as much as you might like to.
 

Ed Hillel

Wants to be startin somethin
SoSH Member
Dec 12, 2007
48,613
Here
OR, the ref at the top of the screen fucked up because he forgot the difference between the clock being stopped and the clock being live? Do we think that the ref at the bottom was calling a different penalty because he threw his flag - presumably - for the exact same penalty, but didn't run on to the field to try and stop the play because he remembered the rule? Ref at the top of the screen fucked up, they huddle up and came to the correct conclusion. It's also not clear if it was an errant whistle because on the one replay there's no audible whistle until the ball is recovered.

Without a replay that shows exactly what happened from a different angle then this conversation is just spinning in circles.
You’re probably right in what happened, but the enforcement mechanism was still incorrect. They cannot by their own regulations pretend a whistle was never blown. Once the ref runs in, the play is dead. They either own up to their mistake and replay the down or just call a false start to cover it. You can’t cost a team a game because of your mistake by pretending it never happened. Players stopped playing and refs stopped reffing. They broke their own rules.
 

CoffeeNerdness

Member
SoSH Member
Jun 6, 2012
9,736
The official at the bottom was calling it correctly and the official at the top was not. That is not really in dispute. But the problem is the official at the top called a dead ball foul. The play is dead. The whistle was blown / the ball was signaled as dead. It doesn’t matter if it’s right or wrong, the play is still dead.

Once you carry out the death penalty you can’t bring someone back just because you made a mistake, as much as you might like to.
You’re probably right in what happened, but the enforcement mechanism was still incorrect. They cannot by their own regulations pretend a whistle was never blown. Once the ref runs in, the play is dead. They either own up to their mistake and replay the down or just call a false start to cover it. You can’t cost a team a game because of your mistake by pretending it never happened. Players stopped playing and refs stopped reffing. They broke their own rules.
I think the only way to say that this play was called incorrectly is to say the whistle was blown or not. Please re-watch the replay with the sound up. Granted Arrowhead is loud af but I don't hear a whistle until the ball is recovered. It isn't clear the guy at the top blew his whistle. Players definitely didn't stop playing, nor do I see the ref at the top do anything accept run on the field with no hand signal until the recovery and no definitive whistle.
 

Ed Hillel

Wants to be startin somethin
SoSH Member
Dec 12, 2007
48,613
Here
I think the only way to say that this play was called incorrectly is to say the whistle was blown or not. Please re-watch the replay with the sound up. Granted Arrowhead is loud af but I don't hear a whistle until the ball is recovered. It isn't clear the guy at the top blew his whistle. Players definitely didn't stop playing, nor do I see the ref at the top do anything accept run on the field with no hand signal until the recovery and no definitive whistle.
No, the ref running in IS the signal. The play was objectively blown dead. Period. Players and refs see that they stop playing, which is exactly what happened.
 

Toe Nash

Member
SoSH Member
Jul 28, 2005
5,860
02130
I think that's why the flag came out "late".

The whining about the Chiefs luck in these games is really getting tiresome. The Vikings also lucked their way to a great record two years ago, and they got drubbed in their first playoff game. If the Chiefs don't tighten up, I expect the same will happen to them, Mahomes or no Mahomes.
Some of us want the chiefs to lose and suffer every game.

Also this luck makes the difference between playing in Arrowhead or Buffalo/Baltimore/Pittsburgh and they are plenty likely to get favorable reffing in the playoffs too. Fuck them.
 

CoffeeNerdness

Member
SoSH Member
Jun 6, 2012
9,736
I hope the fans are as forgiving as you when I fuck up my next call
Forgiving? I've been on this guy royally fucking up since last night when you said this >

He didn’t give the wrong signal.
If he actually and definitively blew the whistle errantly than I'll concede that the Raiders got screwed. He was right by the Raiders bench so if he did I'm sure we'll here. Until that point, making assumptions about what happened is doing the heavy lifting for this guy's work last night.
 

Remagellan

Well-Known Member
Lifetime Member
SoSH Member
Some of us want the chiefs to lose and suffer every game.

Also this luck makes the difference between playing in Arrowhead or Buffalo/Baltimore/Pittsburgh and they are plenty likely to get favorable reffing in the playoffs too. Fuck them.
They are not a traditional rival. They did not end our recent run of success. This hatred is bred of petty thinking that assumes anything they do can diminish our recent stretch of sustained excellence. There's nothing they can do that can ever do that.
 
Last edited:

CFB_Rules

Member
SoSH Member
Nov 29, 2016
1,787
If he actually and definitively blew the whistle errantly than I'll concede that the Raiders got screwed. He was right by the Raiders bench so if he did I'm sure we'll here. Until that point, making assumptions about what happened is doing the heavy lifting for this guy's work last night.
Im just coming from knowing the line of scrimmage mechanics. Most fouls are a “throw then blow”, as in you throw the flag, then finish the play and blow the whistle. False start is “blow then throw”, you are supposed to blow the whistle before even reaching for your flag.

Maybe he fucked up the mechanics too, but the NFL is so militant on mechanics and it’s so hard-wired after years of calling false starts that I would be very surprised.
 

DJnVa

Dorito Dawg
SoSH Member
Dec 16, 2010
55,529
Commercial on Peacock touting the SNF game and said "the resurgent Niners..."

Uh, no.
 

Gash Prex

Member
SoSH Member
Apr 18, 2002
7,218
Sounds like Randy is going through some serious medical issues (not a doctor but I assume liver related)