I was upset about it at the time as well. But if you look at the play by play of the game, Wash ran it's 2nd down play at 1:28 and the fumble out of bounds did not stop the clock. The Giant's timeout was awarded at 1:23 to stop the clock.
So it was the right decision to take the timeout there.
Fumble,so gotta stop the clock. Time out was the right call.
It's under 5:00 in the second half but under 2:00 in the first half.
It only takes a couple of seconds, maybe not even that, to spot the ball.
The running play went off at 1:28 and the TO was granted at 1:23 where clock was reset.
section, if I have the play right, I saw a clear path to the EZ had SB cut back to his left there. But with all his mind facts in reading time, down, and distance, he opted for the safe option.
Quote:
have saved his timeout because we only had 2 going into OT.
It only takes a couple of seconds, maybe not even that, to spot the ball.
The running play went off at 1:28 and the TO was granted at 1:23 where clock was reset.
So a couple of seconds don't help? When I saw the play stop, there was 9 seconds left on the play clock. Even if time was given back, that's better than 40 seconds. Is your argument really that it is only a couple of seconds? Every second helps.
So a couple of seconds don't help? When I saw the play stop, there was 9 seconds left on the play clock. Even if time was given back, that's better than 40 seconds. Is your argument really that it is only a couple of seconds? Every second helps.
The time it takes to spot the ball has no relevance when the ball goes out of bounds and the clock stops, which happened here.
The clock was going to run on the reset of the ball, because the fumble happened in bounds, but Giants were given the TO, no time was lost.
The running play clock shown on the screen was wrong and corrected on the reset.
Quote:
So a couple of seconds don't help? When I saw the play stop, there was 9 seconds left on the play clock. Even if time was given back, that's better than 40 seconds. Is your argument really that it is only a couple of seconds? Every second helps.
The time it takes to spot the ball has no relevance when the ball goes out of bounds and the clock stops, which happened here.
The clock was going to run on the reset of the ball, because the fumble happened in bounds, but Giants were given the TO, no time was lost.
The running play clock shown on the screen was wrong and corrected on the reset.
The time it takes to spot the ball, the play clock is ticking. If a play clock is reset to 25 not 40. It cost us time. There is no arguing that.
The time it takes to spot the ball, the play clock is ticking. If a play clock is reset to 25 not 40. It cost us time. There is no arguing that.
The play clock does not run in that situation when the ball has gone bouncing out of bounds and the officials need to retrieve it. Both time clock and play clock will begin on the reset.
And the situation was not one where the rules specify a 25 second clock rather than a 40.
Quote:
The time it takes to spot the ball, the play clock is ticking. If a play clock is reset to 25 not 40. It cost us time. There is no arguing that.
The play clock does not run in that situation when the ball has gone bouncing out of bounds and the officials need to retrieve it. Both time clock and play clock will begin on the reset.
And the situation was not one where the rules specify a 25 second clock rather than a 40.
When does the play clock stop? Any time a ball is spotted, the play clock is running. That is why you see so many delay of games when player think they have more time on the play clock.