Skip to main content

@BrainDed posted:

That's not how it works.. He needs to be moving forward.   If he is being driven backwards when attempting to go OB, the clock runs as it is considered a tackle.

I get what you're saying, but  it was ruled he was going that way, not that he was driven that way.

In other words, it was his actions that got him out of bounds, not the defenders.

Were it the defender that was the cause of him going out of bounds, yes, the clock would still have been running. In this case, the defender couldn't stop him from getting out of bounds, hence, clock stops.   

@Herschel posted:

I get what you're saying, but  it was ruled he was going that way, not that he was driven that way.

In other words, it was his actions that got him out of bounds, not the defenders.

Were it the defender that was the cause of him going out of bounds, yes, the clock would still have been running. In this case, the defender couldn't stop him from getting out of bounds, hence, clock stops.   

He was moving backwards when he went out of bounds. If he does that then the clock keeps running and doesnโ€™t stop.

The clock should have kept rolling either way.

@Herschel posted:

I get what you're saying, but  it was ruled he was going that way, not that he was driven that way.

In other words, it was his actions that got him out of bounds, not the defenders.

Were it the defender that was the cause of him going out of bounds, yes, the clock would still have been running. In this case, the defender couldn't stop him from getting out of bounds, hence, clock stops.   

Wrong again sir.....they marked the ball UP where he had forward progress not where he went OOB and still stopped the clock.

You have to be moving forward when going OOB to get the clock stopped under 2 minutes. It's been the rule for quite a few years and you can see it in multiple games where refs have kept the clock rolling and given forward progress when a player is pushed OOB going backwards.

So either .....

  1. The ball gets placed where he went OOB and clock stops orrrrr....
  2. The runner is given forward progress and clock keeps rolling.
Last edited by Boris
@Herschel posted:

I get what you're saying, but  it was ruled he was going that way, not that he was driven that way.

In other words, it was his actions that got him out of bounds, not the defenders.

Were it the defender that was the cause of him going out of bounds, yes, the clock would still have been running. In this case, the defender couldn't stop him from getting out of bounds, hence, clock stops.   

RONG as usual.

@Boris posted:

Wrong again sir.....they marked the ball UP where he had forward progress not where he went OOB and still stopped the clock.

You have to be moving forward when going OOB to get the clock stopped under 2 minutes. It's been the rule for quite a few years and you can see it in multiple games where refs have kept the clock rolling and given forward progress when a player is pushed OOB going backwards.

So either .....

  1. The ball gets placed where he went OOB and clock stops orrrrr....
  2. The runner is given forward progress and clock keeps rolling.

The ball was spotted incorrectly for that ruling, yes. I don't think I've seen anyone disagree with that.

It was a judgement call. I can see why they ruled it the way they did whether I like it or not.

Last edited by Herschel
@Herschel posted:

The ball was spotted incorrectly for that ruling, yes. I don't think I've seen anyone disagree with that.

It was a judgement call. I can see why they ruled it the way they did whether I like it or not.

Piss poor judgement, and I can't.l see how they ruled it that way.

Ballentine had MVS wrapped and was pushing him backwards. MVS did not go backwards on his own. The refs had the spot (forward progress) correct, but the clock should've kept running.

I just watched the replay...

@artis posted:

The clock should still run even if you go OB laterally, no? It seems like all the Packers on the sideline behind the official were 100% confident that the clock should keep running.

No. A different example we've seen before is when a first down would be involved. If the receiver catches the ball past the sticks and runs out of bounds behind the sticks, the clock stops and there is no first down.

It's about control.

We know in that sitauation MVS would try to get out of bounds.

The judgement call was that MVS ran out of bounds under his own volition and Ballantine was unable to stop him.

The other way would have been Ballantine  knocked him out of bounds after esstablishing control and ending the play.

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×