Interesting Timing Error

[Camron Rust]

Originally Posted by blindzebra

Care to support that by a rule?

Like I said, replace the 1.2 with 5 seconds and for whatever reason, there was never a count, you going to allow a team to lose a game because of a known timing error? I doubt it.

I don't like it, but it is the rule.

Unless you have definite knowledge of how much time should be put back, you can't put any back. And 1.2 is not the correct amount to put back becasue the clock should have started when the ball was rebounded.

Perhaps the time should be 0.8 or 0.9, but not 1.2. But, since you don't know, you can't put any back.

To put 1.2 back gives the rebounding team more time than they deserve. They would now get to advance the ball down the court with a throwin pass such that the clock would only start on the catch...possibly in a shooting position. If the clock had been properly started, the team would have been forced to make that pass with the clock running (or call a timeout if they had any left).

To put 1.2 back would allow a team an undeserved chance to win the game due to a timing error.