[Hank 91]

First of all, please know that in no way am I suggesting that this was the reason for yesterday's loss, but something strange happened during the fourth quarter. You might remember that just before the kick off after Stanford's last field goal, the officials announced that there had been a clock error on the previous possession, so the clock was being reset from 5:05 to 4:15, a significant change. I was at the game, so we had no explanation other than that.

I just finished watching the recorded broadcast, and at first I thought they must not have restarted the clock after the penalty on the first field goal try, but that couldn't have accounted for fifty seconds. It turns out that the clock stopped after Hogan's sack on second down, then didn't run at all until after the screen to Sanders on the following play. They ended up getting it right, and I guess that's all that matters, but what's surprising is how far back they went to find the error. I always thought that once a play is run, you can't go back to make corrections involving previous plays, but they went back four plays.

Again, it all worked out for the best. Stanford was lucky to get three points on that sequence, and if the error hadn't been fixed and we had managed to score a touchdown on that final drive and the erroneous stoppage had been discovered after the fact -- as it surely would've been -- all would've broken loose.

[Hank 91]

First of all, please know that in no way am I suggesting that this was the reason for yesterday's loss, but something strange happened during the fourth quarter. You might remember that just before the kick off after Stanford's last field goal, the officials announced that there had been a clock error on the previous possession, so the clock was being reset from 5:05 to 4:15, a significant change. I was at the game, so we had no explanation other than that.

I just finished watching the recorded broadcast, and at first I thought they must not have restarted the clock after the penalty on the first field goal try, but that couldn't have accounted for fifty seconds. It turns out that the clock stopped after Hogan's sack on second down, then didn't run at all until after the screen to Sanders on the following play. They ended up getting it right, and I guess that's all that matters, but what's surprising is how far back they went to find the error. I always thought that once a play is run, you can't go back to make corrections involving previous plays, but they went back four plays.

Again, it all worked out for the best. Stanford was lucky to get three points on that sequence, and if the error hadn't been fixed and we had managed to score a touchdown on that final drive and the erroneous stoppage had been discovered after the fact -- as it surely would've been -- all would've broken loose.

[FarmBoy]

The clock change clearly didn't impact the outcome of the game. Shaw stuck to his run-first  game plan even though the shortened clock would have dictated more of a passing attack for most coaches. If we had lost because we ran out of time, I might be peeved, but clearly, the clock played no role in the outcome.

[FarmBoy]

The clock change clearly didn't impact the outcome of the game. Shaw stuck to his run-first  game plan even though the shortened clock would have dictated more of a passing attack for most coaches. If we had lost because we ran out of time, I might be peeved, but clearly, the clock played no role in the outcome.

[Farm93]

Even during the FG drive I noticed the clock stayed at 5:38 for a LONG, LONG, LONG time.  I have not seen the TV broadcast yet (will get the strength to watch that this weekend I suspect), but I am sure they talked about it in real time.

The clock did not run between plays which I knew was wrong.  And then it did not run DURING a play which was an obvious problem.  The MSU fans were screaming during this time, so I know they saw it too.  My guess is that Coach Shaw's staff knew it was not moving too.  It created a small problem because the play calling MIGHT have changed, but I doubt it.

Stanford needed a TD on that drive with ~6 minutes left.  It was not as if the staff was trying for a FG drive.  Then even with less time on the clock the proper call on the kickoff was to bank on a three and out.  Which Stanford got, btw.

The "problem" is that Hogan is not a come from behind in the 4th quarter QB, but Stanford had plenty of time to get that last drive completed.  I was not happy with the huddles while the clock was running, but...

[Farm93]

Even during the FG drive I noticed the clock stayed at 5:38 for a LONG, LONG, LONG time.  I have not seen the TV broadcast yet (will get the strength to watch that this weekend I suspect), but I am sure they talked about it in real time.

The clock did not run between plays which I knew was wrong.  And then it did not run DURING a play which was an obvious problem.  The MSU fans were screaming during this time, so I know they saw it too.  My guess is that Coach Shaw's staff knew it was not moving too.  It created a small problem because the play calling MIGHT have changed, but I doubt it.

Stanford needed a TD on that drive with ~6 minutes left.  It was not as if the staff was trying for a FG drive.  Then even with less time on the clock the proper call on the kickoff was to bank on a three and out.  Which Stanford got, btw.

The "problem" is that Hogan is not a come from behind in the 4th quarter QB, but Stanford had plenty of time to get that last drive completed.  I was not happy with the huddles while the clock was running, but...

[Hank 91]

There was actually no mention of the stopped clock during the broadcast, even though it was frozen on screen for all to see.

And I agree with you about the huddling on the final drive. They didn't really need to be in frantic hurry-up mode, but they could've saved 5-10 second per play had they just gotten to the line a run a play. At the time, I was worried that even they were able to put together a few first downs, it would be terribly tight at the end. The need to huddle could be because of the playbook, but you'd think they could simplify things in such situations. Also, it will be interesting to see if Hogan gets to the point where he's calling his own plays the way Luck did. That would also alleviate this concern.

[Hank 91]

There was actually no mention of the stopped clock during the broadcast, even though it was frozen on screen for all to see.

And I agree with you about the huddling on the final drive. They didn't really need to be in frantic hurry-up mode, but they could've saved 5-10 second per play had they just gotten to the line a run a play. At the time, I was worried that even they were able to put together a few first downs, it would be terribly tight at the end. The need to huddle could be because of the playbook, but you'd think they could simplify things in such situations. Also, it will be interesting to see if Hogan gets to the point where he's calling his own plays the way Luck did. That would also alleviate this concern.

[JeffInCorvallis]

They ended up getting it right, and I guess that's all that matters, but what's surprising is how far back they went to find the error. I always thought that once a play is run, you can't go back to make corrections involving previous plays, but they went back four plays.

I think official time is kept by the crew on the field.  Once they realized there was a discrpancy all they had to do was tell the scoreboard operator to put the correct time on the clock.

[JeffInCorvallis]

They ended up getting it right, and I guess that's all that matters, but what's surprising is how far back they went to find the error. I always thought that once a play is run, you can't go back to make corrections involving previous plays, but they went back four plays.

I think official time is kept by the crew on the field.  Once they realized there was a discrpancy all they had to do was tell the scoreboard operator to put the correct time on the clock.

[Hank 91]

I think you're right about the officials and the official time, but if this had been later in the game, and the time on the clock had affected play calling, I think it would be a problem to make a correction after the fact like that. Again, it clearly didn't affect this game.

[Hank 91]

I think you're right about the officials and the official time, but if this had been later in the game, and the time on the clock had affected play calling, I think it would be a problem to make a correction after the fact like that. Again, it clearly didn't affect this game.

[jacketree]

The broadcasters did mention the clock stoppage and why it was corrected.  We thought something was odd about the clock not moving. Ref went to both benches, and both coaches nodded in agreement.  Given how Stanford played like they were in no hurry at all with 3:05 left and 70 yards to go, I can't believe it affected the play calling for Stanford. Or MSU for that matter.  They went pretty conservative after the field goal themselves.

[jacketree]

The broadcasters did mention the clock stoppage and why it was corrected.  We thought something was odd about the clock not moving. Ref went to both benches, and both coaches nodded in agreement.  Given how Stanford played like they were in no hurry at all with 3:05 left and 70 yards to go, I can't believe it affected the play calling for Stanford. Or MSU for that matter.  They went pretty conservative after the field goal themselves.