Refs stole 24 seconds of game clock on last TD drive

[MikeyLikesIowa]

Let me first reaffirm that I am NOT saying this oversight alone cost us the game. However, I do believe it may have affected the outcome considering how the game ended. The error occurred after Rudock scrambled for the first down on 3rd and 15 during our last TD drive in the fourth quarter. The game clock should have stopped at 6:02. However, the refs didn't stop the game clock after he went out of bounds. I was at the game and saw this first hand. Sure enough, I go home, watch the replay on my DVR, and it confirmed what I thought I saw at the game.

If you have a chance to watch the replay, you'll see that Rudock runs out of bounds with 6:02 displayed on ESPN's game clock and you see the clock stop at 6:01. Rudock then takes the next snap with 5:38 left on ESPN's game clock. This is consistent with what I observed at the game, but the actual game clock on the scoreboard was never stopped.

I know that crying about it won't change anything, but this is a huge oversight and I can't be the only one that noticed this.

 

[Bigtenchamp]

Let me first reaffirm that I am NOT saying this oversight alone cost us the game. However, I do believe it may have affected the outcome considering how the game ended. The error occurred after Rudock scrambled for the first down on 3rd and 15 during our last TD drive in the fourth quarter. The game clock should have stopped at 6:02. However, the refs didn't stop the game clock after he went out of bounds. I was at the game and saw this first hand. Sure enough, I go home, watch the replay on my DVR, and it confirmed what I thought I saw at the game.

If you have a chance to watch the replay, you'll see that Rudock runs out of bounds with 6:02 displayed on ESPN's game clock. He takes the next snap with 5:38 left on ESPN's game clock. This is consistent with what I observed at the game.

I know that crying about it won't change anything, but this is a huge oversight and I can't be the only one that noticed this.

clock doesn't stop anymore when you run out of bounds... in the pro's its 2 min 1st half and 5 min in the 2nd half (I think its the same in college -it might even be 2 min in each half).

Not trying to be a arse or anything but have you really thought the clocked stopped when you run out of bounds? its like been this way for a long time ... maybe even 10 years.

 

[MikeyLikesIowa]

clock doesn't stop anymore when you run out of bounds... in the pro's its 2 min 1st half and 5 min in the 2nd half (I think its the same in college -it might even be 2 min in each half).

Not trying to be a arse or anything but have you really thought the clocked stopped when you run out of bounds? its like been this way for a long time ... maybe even 10 years.

The clock should ALWAYS be stopped when a ball carrier runs out of bounds. The 2014 rulebook states that clock should be stopped and restarted at the referee's signal except when there are 2 minutes or less left in a half; in which case the clock starts at the next snap instead of at the referee's signal. In the situation I mentioned, the game clock was not stopped at all. Even if I am wrong about the out of bounds rule, the clock should have been stopped and restarted at the referee's signal due to the first down.

 

[Hawknick]

Those refs were terrible! They cost Iowa a minimum of 3 points.

 

[ihawkeye]

Clock should always stop when you run out of bounce.

 

[NCHawker]

LEARN THE GAME.

http://en.wikipedia.org/wiki/Clock_management

 

[Skeets77]

Maybe if Kirk would of called a TO sooner before the half ended the Hawks could of gotten two plays off and a possible field goal. What was that all about anyway.

 

[BILLBUCKNER]

We got no calls from the refs. We stripped the ball from their qb who was still fighting for yardage that they 'blowed' dead that would have scored us a td. Another time our corner forced a fumble that they ruled the player down.

 

[g11]

The play that drove me nuts was the stoppage to put 2 freaking seconds on the clock when Kinnick was the loudest it's been in 5 years, on a crucial 3rd down. It reminded me of baby Harbaugh back in 85 because Kinnick was too loud.

That stoppage was beyond BS, the timing of it was the most questionable thing I've ever seen.

 

[AHawk1]

LEARN THE GAME.

http://en.wikipedia.org/wiki/Clock_management

It's understandable that a lot of people on a message board don't know all the rules, and how clock management works. With that being said, could you kindly forward this to the football office.

Thanks

 

[ICHawk24]

The clock stops on out of bounds plays during the last two minutes of each half. Otherwise, its supposed to stop until the ball is spotted.

 

[ICHawk24]

The play that drove me nuts was the stoppage to put 2 freaking seconds on the clock when Kinnick was the loudest it's been in 5 years, on a crucial 3rd down. It reminded me of baby Harbaugh back in 85 because Kinnick was too loud.

That stoppage was beyond BS, the timing of it was the most questionable thing I've ever seen.

Totally agreed. The Badgers were just breaking their huddle with 8 seconds on the play clock, with the crowd at 11, and the back judge comes running in to change the clock. As if a second here or there doesn't get lost all game long.

 

[imported_ankle23]

Totally agreed. The Badgers were just breaking their huddle with 8 seconds on the play clock, with the crowd at 11, and the back judge comes running in to change the clock. As if a second here or there doesn't get lost all game long.

when i saw that happen, i immediately thought 'the conference wishes for wisconsin to win the game'....

 

[ryno]

Totally agreed. The Badgers were just breaking their huddle with 8 seconds on the play clock, with the crowd at 11, and the back judge comes running in to change the clock. As if a second here or there doesn't get lost all game long.

I agree. i was at the game as well. the badgers would not have gotten that play off. It completely killed our momentum. However, given our 3rd down defense, we probably wouldn't have stopped them anyway. We need some defensive playmakers in the worst way.

 

[eveningnewsteam]

The play that drove me nuts was the stoppage to put 2 freaking seconds on the clock when Kinnick was the loudest it's been in 5 years, on a crucial 3rd down. It reminded me of baby Harbaugh back in 85 because Kinnick was too loud.

That stoppage was beyond BS, the timing of it was the most questionable thing I've ever seen.

Yep it bailed them out. The play clock started after the penalty and Wisconsin didn't realize it

 

[hawkdrummer1]

Maybe if Kirk would of called a TO sooner before the half ended the Hawks could of gotten two plays off and a possible field goal. What was that all about anyway.

Bingo. Another embarrassing clock screw up.

 

[Eda]

IMO, the bigger mistake by the refs was for charging Iowa a timeout on the two point conversion. KirFer wanted the ball spotted on the left hash and som dip**** ref charged him a timeout. After the officials conferenced I was sure they'd give us that timeout back.
That timeout could've gotten us the ball back with 30 plus seconds only needing a FG. I'm still extremely pizzed about that one.

 

[Eda]

Maybe if Kirk would of called a TO sooner before the half ended the Hawks could of gotten two plays off and a possible field goal. What was that all about anyway.

I'm not saying I agree with the way that sequence went down; but understand the thinking towards the end there. It was fourth-down and they wanted to run the game clock down so Wisconsin couldn't get it back if we failed to convert.

Obviously, we converted and miraculously had a second left to throw up a prayer.

 

[DDThompson]

As bad as the refs were, Iowa was worse.

 

[BigD]

As bad as the refs were, Iowa was worse.

You mean like running the ball three straight times with less than ten minutes left in the game and down by fourteen points? Is that an example of what you mean?