We never should have gotten the opportunity to spike the ball. We got the 1st down with 1 second to play and the clock stopped. The clock should have stopped long enough for the refs to reset the ball. The 1 second should have run off the clock before JJ ever got under center. Or, we should have called a timeout, but I'm not sure we had one. The madness started at the 32 yard line. 1st and 10 and instead of running the ball, or a play-action or rolling JJ out we took a frikkin sack.:insane: Then we got tackled for another loss and let about 15 seconds or so run off the clock before we called timeout. :insane: We went from 1st and 10 at the 32 to 4th and 26 from the 48. Back to my original point- Once the refs reset the ball, they should have started the game clock. We should NOT have been able to run any play at all. I still cannot believe, after getting to the 32 yard line, that we lost this game. :crystal::geaux::crystal::geaux::crystal:
It's all unbelieveable, and you're right, the refs GAVE us time to get to the line of scrimmage. Then, our freaking fg unit WASN'T the unit that went out there. Simply unbelieveable.
Clock doesnt start until the chains are reset and it was what a 40 yard play the ball was set but they were waiting on the chains to get down there
The clock stops for first down until the chains are reset. 27 seconds is what is being reported as to how long it took to reset the chains. That is enough time to run the FG unit on the field twice.
I thought that if we could get the ball spiked with :01 we would have a great opportunity to run the option to Shep and put the game out of reach. We talked about it while they were moving the chains and decided that a FG only puts us up by one. Les :wink:
It's the chains that matter, as mentioned before. IIRC they also have to give the defense time to get set as well.
