mjfelton15
Banned
- Joined
- Mar 14, 2019
- Messages
- 3,059
- Reaction score
- 797
- Points
- 113
Forget this thread
Last edited:
I kept track, and we lost probably a minute or more due to the unstopped clock
Sent from my iPhone using Tapatalk
I noticed at the end of the first half. 4 seconds came off the clock when we spiked it despite snapping it immediately. Obviously not the reason we lost, but thought it was total bull **** and cost us another chance in the end zone.
The rule is to stop the clock on first downs until the chain resets. Across the TV, nothing egregious was apparent other than the offense's inability to run the hurry-up.
Not exactly. The clock stops for the purpose of resetting the chains, but it starts on the referee's signal whether the chains are completely moved or not, and they frequently are not completely set. It doesn't take a lot of imagination to come up with scenarios where always waiting for the chains would harm the team trying to play with pace.
That said, I just rewatched the only Gopher drive of the 4th quarter that had any 1st down conversions and couldn't find a single example of what the OP describes. The weren't playing hurry-up anyway. Didn't happen.
Not exactly. The clock stops for the purpose of resetting the chains, but it starts on the referee's signal whether the chains are completely moved or not, and they frequently are not completely set. It doesn't take a lot of imagination to come up with scenarios where always waiting for the chains would harm the team trying to play with pace.
That said, I just rewatched the only Gopher drive of the 4th quarter that had any 1st down conversions and couldn't find a single example of what the OP describes. The weren't playing hurry-up anyway. Didn't happen.
They changed the mechanics of this in the last couple years to speed the game up. Stop clock, confirm 1st down, and wind the clock when ball is being put on the ground. Pretty much same at HS level now also.