True; it would only make sense if they had another TO to take in the event of a bad snap on the FG attempt.
I understand, but I’d much rather kick on the last play. Outside of the Romo debacle against the Seahawks, I can’t recall an issue with a snap/hold on a game winning FG attempt.I had presumed stopping the clock at 12 seconds was more of a “in case there’s a bad snap or problem on the hold or something on the attempt, leave enough time that the holder could throw the ball out of bounds and they still try it again” move.
Gotta wonder if Ryan Day let his emotions call that TO early?
GT had a FG blocked on 3rd down, recovered the loose ball and kicked again to beat UGA. Still makes me smile to remember it!I understand, but I’d much rather kick on the last play. Outside of the Romo debacle against the Seahawks, I can’t recall an issue with a snap/hold on a game winning FG attempt.
300+ yards receiving by 1 player…500+ yards passing..and I thought our DB’s were bad[
I don't think Utahs DB's were that bad......It's not every week you get to face a QB like CJ Stroud and WR's like they have, especially Smith-Njigba.... There was a reason why he tore up the best big school hs mecca in America, the Dallas metroplex.
The clock would start on the snap, so technically if he got a grounding penalty I believe there would be a 10 second runoff.If the clock is moving. But under the scenario of Ohio State calling a timeout with three second left, then a ten second runoff wouldn’t have occurred because the clock would have been stopped because of the timeout.