01-24-2019, 11:42 PM
(01-24-2019, 08:10 PM)JustAnotherFan Wrote: The most obvious was the UCLA game in (I believe) 2016.
You got me to go watch the game again.
https://www.youtube.com/watch?v=b2fiSoFNCB4
I admit I am a little confused as to the clock management error you are concerned about, though maybe I found it.
It doesn't appear to be on our final drive which was well done, in fact rather amazingly brilliant considering how poorly Burns had passed the ball to that point. The drive details: started with 2:05 left, moved 70 yards to score the winning TD with 0:24 left on the clock. There was only one pass completed in bounds for less than a first down - that was an out route to Irwin that Burns simply didn't throw far enough outside. One might quibble with spiking the ball on first and goal with 0:32 left, since there might have been time for four shots to the end zone, but that's debatable at most.
With more digging I found a mistake. Stanford took its final timeout after the unsuccessful UCLA third down play on the previous drive. It seems to have taken about 0:15-0:20 to get the timeout called. The cut up game on youtube doesn't make clear the exact circumstances but it seems to be associated with Stanford initially thinking they had pushed the UCLA receiver out of bounds. Some kind of miscommunication or indecision cost 15 seconds or more, which was a clear mistake.
I had forgotten about this, but am sure it made me throw something at the TV at the time.
