BS penalty. Int. grounding on Jameis. (2 Viewers)

[Sailorsaint]

Ref made the right call on Patrick Mahomes grounding penalty

four years ago

So, wait, if the clock is stopped, you are forced to play the down? Even if you want to just stop the clock? Scenario.......this same play but with only 4 seconds left on the clock....what then?

 

[Yatman]

snap and throw ob?

write ur congressman

if the clock is stopped, why stop it again?

 

[mjf504]

When Winston was rushing to clock the ball the first time I’m sure he didn’t hear the coaches if anything was being said in the headset. He had one thing in mind. Not having much game time over the past 3 years caused this situational awareness. The second again goes to trying to rush being nervous. Not remembering what down it was because of the penalty of loss of down. Again not playing much hinders game situations like this.

For once the refs tried to help the saints by stopping the clock when it shouldn’t have been stopped.

 

[Patman255]

yes, four years ago

Ref made the right call on Patrick Mahomes grounding penalty

Great find, I feel better that the call has precedent. I think it's silly and needlessly punishes a team for making a bad strategic move anyway, but I can take off my tinfoil "the refs hate us" hat now.

 

[brandon8283]

Never ever heard of such a rule. I still cannot figure out the call and what the ruling was.

Is it the Saints fault the clock wasn’t running? Why would the official spot the ball and not start the clock? Why would the officials allow the Saints to even snap the ball?

I DON’T GET IT!

Anybody?

It was legit. Winston thought the clock was still running and that he was tackled in bounds. The refs stopped the clock because Landry got up and ran out of bounds. It’s a penalty to spike on a stopped clock.

You can’t clock the ball if the clock is already stopped. The coaching staff should have told Winston that the refs stopped the clock.

yes, four years ago

Ref made the right call on Patrick Mahomes grounding penalty

snap and throw ob?

write ur congressman

if the clock is stopped, why stop it again?

Great find, I feel better that the call has precedent. I think it's silly and needlessly punishes a team for making a bad strategic move anyway, but I can take off my tinfoil "the refs hate us" hat now.

Yea, none of these explanations explains the fact that spiking a ball that is snapped IS stopping a moving clock. Even if the clock is stopped pre-snap, snapping the ball starts the clock. Thus, you're still spiking a moving clock.

 

[Yatman]

a team can't call b2b timeouts either

reasons

 

[jayd265]

Landry was down inbound though. Clock should not have stopped. Refs messed up led to the penalty.

Luckily saints were able to overcome horrid reffing and atl

 

[jrdbrn]

The clock was stopped, which was weird. Definitely a first game whiff by all parties.

 

[Saint Droopy]

The refs screwing the Saints.. where have I seen this before?

 

[sainthood]

The refs did not need to say anything. The game clock was stopped. That answers the question. It was a mistake by Winston. He compounded the mistake by grounding the ball with time left for the Falcons to still have a chance on third down. Either could have cost the Saints the game. The third down play was worse given you could have easily taken an endzone shot or tried to get the first down. Lack of awareness on Winston's part on both.

 

[Patman255]

Yea, none of these explanations explains the fact that spiking a ball that is snapped IS stopping a moving clock. Even if the clock is stopped pre-snap, snapping the ball starts the clock. Thus, you're still spiking a moving clock.

I think at this point it's pretty clear that it refers to the status of the clock before the play starts. It's a silly rule, but it seems like it's being applied consistently. It's just clearly kicking a team while they're down. It's not preventing some secret competitive edge to spiking the ball.

 

[ktbarthedoor]

I wonder what the coaches were telling him in the earpiece.

 

[brandon8283]

I think at this point it's pretty clear that it refers to the status of the clock before the play starts. It's a silly rule, but it seems like it's being applied consistently. It's just clearly kicking a team while they're down. It's not preventing some secret competitive edge to spiking the ball.

There's another wrinkle to this, though. Intentional grounding usually requires there not be a receiver in the area. When the ball is snapped, the tight end is clearly in the area, so an eligible receiver is in the area. If it's not a spike, it's an incomplete pass, which would also stop the clock. It's not unlike throwing the ball in the dirt on those failed screens we do all the time.

It's not a delayed spike. It's not spiking a stopped clock (because the clock moves when you snap the ball). It might be a legitimate incomplete pass. There's nothing explicit in the rule book that defines this as intentional grounding that I've seen thus far.

 

[MJ in Calif]

Never ever heard of such a rule. I still cannot figure out the call and what the ruling was.

Is it the Saints fault the clock wasn’t running? Why would the official spot the ball and not start the clock? Why would the officials allow the Saints to even snap the ball?

I DON’T GET IT!

Anybody?

It was the correct call actually, just a poor explanation by the ref. You're not allowed to spike it like that unless the clock is running. Clock was stopped due to out of bounds and it wasn't going to start again until ball was snapped. Mental lapse by Winston and the coaching staff.

 

[brandon8283]

Clock was stopped due to out of bounds and it wasn't going to start again until ball was snapped.

You realize they snapped the ball, right?