Interesting Timing Error

[Camron Rust]

Originally Posted by blindzebra

I disagree.

You still haven't addressed my alternate version with 5 seconds instead of 1.2...what if the timer started it just before release and all 5 seconds ran off just as the ball is touched?

By rule, no, you don't have any authority to put 5 back on the clock if some time should have run off the clock but you don't know how much. You have to know how much time should have been on the clock to add anything back.

Originally Posted by blindzebra

Even if you started a count in this situation, 1.2, is half an arm flick .4, .5, or .6 seconds? Is that really definite knowledge?

The problem is we need working officials revising the rules and making rule changes.

All that said, what am I going to do in a real game if this happens? I'm not putting 1.2 (or 5) back on the clock. And, I'm not leaving it at 0. I'm going to do the right thing and I'm going to have a "count" that lets me do what should be done....put something on the clock that is "right".