What was up with not stopping the clock on out of bounds? (1 Viewer)

tenordas

Vesti le procè flamber
VIP Contributor
Joined
Aug 31, 1997
Messages
13,023
Reaction score
9,940
Location
Houston via New Jersey, New Orleans, Baton Rouge,
Online
I just looked to see if the rules have changed. According to what I found, the NFL rule is that if a player goes out of bounds making forward progress, the clock stops until the ball is placed at the line of scrimmage by the referee.

Yet at least twice today, I saw the clock continue to run after our player clearly went out of bounds, once a running back and once a receiver. I didn't even see a ref do the windmill motion to indicate he thought the player had been tackled or stopped in bounds. What the heck is going on?
 
I just looked to see if the rules have changed. According to what I found, the NFL rule is that if a player goes out of bounds making forward progress, the clock stops until the ball is placed at the line of scrimmage by the referee.

Yet at least twice today, I saw the clock continue to run after our player clearly went out of bounds, once a running back and once a receiver. I didn't even see a ref do the windmill motion to indicate he thought the player had been tackled or stopped in bounds. What the heck is going on?

Yes! Hurts ran for a first down.. And clock kept running although he went ou of bounds
 
Only stays stopped in last five minutes of game and last two minutes of half of memory serves. Otherwise once the ball is spotted clock starts again.

Yes, that's correct, but it was still running between the end f the play to when the ball was spotted. It's supposed to stop until the ball is spotted, and it did not on either play.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Users who are viewing this thread

    Back
    Top Bottom