Last play of half lasted 5 seconds?

Submitted by coldnjl on

While I was at the game, the ending to the second half was a mystery to all the people in our section. How did that play last only 5 seconds? Persa held onto the ball for what seemed like a few seconds onto itself. Is this just a homegame scoreboard or what?

willywill9

October 9th, 2011 at 9:39 AM ^

#1.... it looked like he got both arms on it, but i don't know if his hands got the mask.  More importantly though, they essentially finished the play anyway.... no first down... doesn't matter.  

LSA Aught One

October 9th, 2011 at 10:19 AM ^

It appeared to me that this was the exact definition of a bang-bang play.  Kovacs went for the mid-section when tackling and then Persa pulled away.  As he was pulling away, he started to go down and Kovacs unintentionally hit his helmet (hard).  I believe this is why there was no penalty.  There was nothing malicious about the hit.

willywill9

October 9th, 2011 at 10:24 AM ^

Intention isn't considered... if there's contact like that, it should be a facemask most likely... but it's not like it's a reviewable play.  If the ref didn't see it, he can't assume how the helmet popped off.  I know it would have been a 1st down, but I guess what I meant was... Although the play was ruled dead once the helmet flew off, we got to see them play it out, and they didn't have an answer... so I don't feel too bad about the non-call.

BlueUPer

October 9th, 2011 at 9:49 AM ^

I also posted this on the game thread. I took out a stopwatch and timed the play.  It took more then 6 seconds. 

I believe that this is also what the officials should also do to get rid of any hometown clock keeper bias!

SysMark

October 9th, 2011 at 9:10 AM ^

There were two seconds left when the ball hit the ground.  Will have to go back and check but the clock may have started a little late at the snap.  Even so there probably would been at least one second left - he held it for a few seconds but it was a short throw.

biakabutuka ex…

October 9th, 2011 at 10:27 AM ^

By my recollection there were 2 seconds when he touched it and 1 second when it hit the ground. And then it ran down to 0. I just assumed the clock operator realized he screwed up and that's why he let it run down after it hit the ground. But they clearly didn't review when it started, just when it stopped.

coldnjl

October 9th, 2011 at 9:15 AM ^

Thanks guys...I was in the endzone and we couldn't believe a play just lasted 5 seconds as usually the clock ticks a second or two after the ball has hit the ground.

Brown Bear

October 9th, 2011 at 9:15 AM ^

but the clock stops when the referee signals to stop it. The officiating was horrible in this game and they had no clue what was going on. Having to review that(which I've only seen done in a basketball game) is proof in the pudding.

jblaze

October 9th, 2011 at 9:24 AM ^

watch the BTN replay. There were 2 seconds left when the ball hit the ground. My issue is that I don't know how accurate the BTN was, given their total fail at you know, broadcasting games.

Sac Fly

October 9th, 2011 at 9:32 AM ^

It happened a few times on the last drive when they let the clock run a few seconds longer than it shoud have after incompletions. This worked in our favor because they should have had at least 3 more seconds to work with at the end of the half.

Mr Miggle

October 9th, 2011 at 9:50 AM ^

That play was reminsicent of the last play in the 1998 Rose Bowl. The last two seconds ticked off the clock after the play ended. There was clearly some lag on the scoreboards in that game since receivers were 20-30 yards downfield before the clock started. The refs refused to put the time back then and they probably shouldn't have yesterday..

MileHighWolverine

October 9th, 2011 at 10:12 AM ^

Thankfully it didn't matter.  I look at it as retribution for the Penn State game where got an extra second and the Rose Bowl where the clock ticked off with at least a second still on there.

This time it was out turn to suffer at the hands of the clock and we came away ok. I'm ok with it.

MDave

October 9th, 2011 at 10:32 AM ^

I would be curious to see how this compared to the penn state game in 2005. Are we just complaining to complain when we have benefited from poor clock management also?

Space Coyote

October 9th, 2011 at 10:33 AM ^

I'm not sure about at the end of half, but it seemed like the play was longer than 6 seconds.  

I don't complain about holding by lineman unless it's obvious, so I'm not complaining about many no calls there (there was one on Martin that was obvious and uncalled, but it was on a quick drag route and probably wouldn't have mattered if the lineman held him or not as Persa would have gotten the ball off).  There was some pretty bad holding by the WR on the bubbles that NW was running that was making me angry.

At the same time Kovacs should have been called for either a facemask (it looked like he grabbed the facemask) or a blow to the head.  I hate the blow to the head rule in situations like this (what is the defender supposed to do when the QB ducks like that at the last second?) but it is the rule.

On the next third down for Michigan they clearly got away with a false start too.  So I think it was just a bad performance all around by officials.

imafreak1

October 9th, 2011 at 11:21 AM ^

Oddly, the same type of thing happened a week or so back in a huge game between Auburn and South Carolina. The decison went the other way and the SEC backed up the officials

 

http://content.usatoday.com/communities/campusrivalry/post/2011/10/south-carolina-steve-spurrier-controversy-officials-auburn/1

 

Personally, I think that running an actual play takes 6-7 seconds. NW had no business running another play and should have kicked the FG. Persa did not throw immediately therefore it was possible time would run out. I also think it's pretty clear that the clock did not start at the snap. The refs should not get involved in micromanaging the clock operator's finger.

redfirelx

October 9th, 2011 at 11:22 AM ^

If you watched the clock all game, for some reason on every play it stopped and started late.  Essentially a technical delay in displaying the correct time.  Happened on every play.  So when the refs reviewed it, of course they saw 2 seconds left.  Not sure why on that one...

bklein09

October 9th, 2011 at 12:35 PM ^

IMO, all the bad calls basically resulted in a wash.

We definitely had some things go our way, and those will be highlighted since we won the game. 

But there was some blatantly obvious holding calls against them that went uncalled. Whereas Michigan seemed to get tagged every time we made that kind of mistake.

Bottom line is that we won by 18. Sure NW may have come down to score on their second to last drive and made it a 4 or 3 point game. But we got them to 4th down for a reason. We were playing pretty solid defense in the second half. 

If this had been a one possession game I could beleive that the refs played a bigger role in the outcome. But as it stands, the only thing the refs could have affected was the margin of victory IMO. 

mackbru

October 9th, 2011 at 1:55 PM ^

They don't call blow to the head when a QB contorts at the very last instant, allowing the defender no chance to correct -- especially when the defender was on line for a legal hit below the shoulders.