PurplFrawg
Administrator
Mack was sure they'd put a second back on the clock...just like last time.
At Half: KU 28 @ BC 24
KU's RB Hebert had an 82 yd. run to BC 3 w/0:15 left in half after he’d been tackled for a -22 yd loss on previous play.
I don’t know this to be true but it would seem pretty obvious that they scheduled an out of conference game against each other.
Wat happened to BC's vaunted defense?
Dang, TCU beat me to it.
I guess just karma for UT/Nebeven if the officials in the unc-wf game ruled down due to forward progress the run gave the tar heels a first down which i thought resulted in a clock stoppage to set the chains
That just seems very odd to me but makes sense.
even if the officials in the unc-wf game ruled down due to forward progress the run gave the tar heels a first down which i thought resulted in a clock stoppage to set the chains
Either way, UNC blew a full 1:09 with stupidity.It does AND you can see the official still winding the clock even after the offensive player stepped out. They said that the clock is not considered stopped until the official signals it. Now they are going back to cover their ass. If forward progress was the issue...probably should have three seconds left