Did the clockkeeper do Chicago dirty?
There appears to be a buzz amongst some Bears fans regarding the closing seconds in Sunday’s 22-20 loss to Atlanta. When Matt Ryan drops back to pass what would be a 26-yard completion to Michael Jenkins, there are six seconds remaining in the game. The only problem is the clock doesn’t start ticking until after Ryan is nearly fully set in his stance. And it’s a seven-step drop.
Considering Jenkins is ruled out of bounds with one second left, the implications of a late-starting clock are obviously HUGE. In this case, one second is the difference between winning and losing. But then again, it probably never should have been this close in the first place. You be the judge:
I started yelling right away how there’s no way it could take less than 6 seconds to do that. Unreal.
Good thing this blow isn’t biased…..
Blog**
If you look closely at the play, Jenkins goes out of bounds at the two seconds mark, yet another second rolls by….I understand its a tough loss to take but nitpicking like this is quite pathetic
I just timed this twice with a stop watch. From the hike to when the receiver hits the ground is 5.3 seconds.
[...] (Video via Blog Down, Chicago Bears.) [...]
If you notice, Jenkins is out of bounds with 2 seconds left, but the clock stops with 1 second remaining. I’d say it cancels out.
It does seem highly suspicious. Unfortunately there are screw ups all the time (cough…Ed Hochuli…cough) it just sucks when your team is on the losing end of said screw up.
Man that SUX….Oh well
GO FALCONS
The clock did not stop on that receiver until he hit the ground out of bounds. So that one second is correct, it should not be two seconds.