View Single Post
  #31 (permalink)  
Old Sun Feb 13, 2005, 12:28am
blindzebra blindzebra is offline
Official Forum Member
 
Join Date: Dec 2003
Posts: 2,674
Quote:
Originally posted by Maverick
Quote:
Originally posted by blindzebra
Quote:
Originally posted by Daryl H. Long
Maverick,

Glad someone else has taken BZ to task about his misapplication of which rule covers the situation.

In an earlier post I said this play more closely resembles 5.10.1 Situation A because of the addition of foul before the buzzer.

Sinse Rar (the original poster) has clarified questions I asked and has stated now that the foul occurred after the buzzer to signal the clock ran out.

In that case put the time back on the clock and allow A the throwin they were entitled to. i don't call this a "do over" because they never got to "do" in the first place.
You are spending too much time around MTD, if you think the only case play covering an OFFICIAL'S error causing time to expire, is misapplied in a thread about an OFFICIAL'S error causing time to expire.

Compare the comment under timing mistakes in the case book, 5-9-1 in the rule book, and what happened in the play in question and it all equals one thing...AN OFFICIAL'S ERROR!
I don't think anyone is arguing that it is not an official's error. But I haven't seen any rule book reference saying you can't correct an official's error in this situation.
Rule book 5-10, case book comment about that rule:

Timing mistakes which may be corrected are LIMITED TO THOSE WHICH RESULT FROM THE TIMER'S NEGLECT TO STOP OR START THE CLOCK AS SPECIFIED BY THE RULES.

5-9-1 After time has been out, the clock shall be started when THE OFFICIAL SIGNALS TIME-IN.

You just said this play is an official's error and 5-10 clearly states that the only time the clock can be adjusted is on a timer's error.

There is no rule or case play that allows for time being adjusted on an official's error.

So as I have said since the first post, by rule you cannot fix it.

In practice I'm envoking 2-3, to fix the mistake, but that is fudging since 5.10.1.C does cover the situation.
Reply With Quote