The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Basketball (https://forum.officiating.com/basketball/)
-   -   Start the clock.... (https://forum.officiating.com/basketball/97910-start-clock.html)

Nevadaref Mon May 19, 2014 05:20pm

Quote:

Originally Posted by Adam (Post 934414)
Whether the action should be timed is certainly up for debate, but I fail to see how your reasoning here applies.

Because the throw-in location is now possibly a great distance away from where it was before and the action was not a throw-in violation. How do you account for that without any time coming off the clock?
A play took place which results in a new throw-in from a different location on the court. Doesn't that action need to be timed as part of the game (absent a rule such as the NCAA has)?
That is the logic being my thinking.

Camron Rust Mon May 19, 2014 05:45pm

Quote:

Originally Posted by Nevadaref (Post 934415)
Because the throw-in location is now possibly a great distance away from where it was before and the action was not a throw-in violation. How do you account for that without any time coming off the clock?
A play took place which results in a new throw-in from a different location on the court. Doesn't that action need to be timed as part of the game (absent a rule such as the NCAA has)?
That is the logic being my thinking.

I don't see how the two are related....the location of the new throwin and the clock.

A foul or other non-throwin violation could occur somewhere else on the court before the clock starts. Such an occurrence could result in a throw-in at a different spot all without the clock starting.

I think that the clock starting is acceptable. I also think that the clock not starting is also acceptable. I'm not going to make any correction regardless of which of the two occurs short of the clock running and continuing to run too long.

just another ref Mon May 19, 2014 06:01pm

Quote:

Originally Posted by Nevadaref (Post 934415)
Because the throw-in location is now possibly a great distance away from where it was before and the action was not a throw-in violation. How do you account for that without any time coming off the clock?


If the touch is a violation, the ball is dead. The clock does not start when the ball is dead.


period

Nevadaref Mon May 19, 2014 06:28pm

People should also consider the history of this NFHS rule.
I don't have time at the moment to post the documentation, so I'll edit this post later and do so.
The word legally was added to account for a rule change involving the kicking of the ball by a defender during an AP throw-in. Prior to that the clock started on any touch by a player from a throw-in pass. Now we must understand the wording to have only altered the timing rule for contact by a kick (or fist). Why? Because that is what the NFHS said when making the change.

AremRed Mon May 19, 2014 08:09pm

Quote:

Originally Posted by Nevadaref (Post 934415)
Because the throw-in location is now possibly a great distance away from where it was before and the action was not a throw-in violation. How do you account for that without any time coming off the clock?
A play took place which results in a new throw-in from a different location on the court. Doesn't that action need to be timed as part of the game (absent a rule such as the NCAA has)?
That is the logic being my thinking.

Is your Enter key broken? I agree with your reasoning on the OOB violation location vs. throw-in violation location. I don't think the clock can run if the first touch is a violation. I think that's common sense, and even old interpretations or the "history" you talk about shouldn't apply now. There are some rules where the history matters but I don't think this is one of them.

Quote:

Originally Posted by Adam (Post 934414)
I wouldn't make a correction either way, however, during a game.

I think I would in a late game situation where the timer erroneously runs the clock. Could be important with only a few seconds left.

APG Mon May 19, 2014 08:55pm

I honestly think that if this question was presented to the NFHS powers that be, they would issue an interpretation saying that no time should come off the clock. It doesn't make logistical nor common sense for any time to run off the clock when a violation occurs simultaneously with the first touch.

Raymond Mon May 19, 2014 09:17pm

Quote:

Originally Posted by APG (Post 934425)
I honestly think that if this question was presented to the NFHS powers that be, they would issue an interpretation saying that no time should come off the clock. It doesn't make logistical nor common sense for any time to run off the clock when a violation occurs simultaneously with the first touch.

In theory, yes, no time should come off the clock b/c no official should be chopping the clock in. In practice, officials are going to incorrectly chop the clock and timers are going to incorrectly start the clock.

AremRed Mon May 19, 2014 09:25pm

Quote:

Originally Posted by APG (Post 934425)
I honestly think that if this question was presented to the NFHS powers that be, they would issue an interpretation saying that no time should come off the clock. It doesn't make logistical nor common sense for any time to run off the clock when a violation occurs simultaneously with the first touch.

We should get JAR on that immediately. Or just check what the NCAA-W's interpretation is and go with that... Get it??

Nevadaref Tue May 20, 2014 02:57am

Quote:

Originally Posted by BadNewsRef (Post 934428)
In theory, yes, no time should come off the clock b/c no official should be chopping the clock in. In practice, officials are going to incorrectly chop the clock and timers are going to incorrectly start the clock.

Why is your default that the officials are incorrectly chopping the clock?
For decades the correct procedure has been to chop the clock. The default should be to chop.

Camron Rust Tue May 20, 2014 03:00am

Quote:

Originally Posted by BadNewsRef (Post 934428)
In theory, yes, no time should come off the clock b/c no official should be chopping the clock in. In practice, officials are going to incorrectly chop the clock and timers are going to incorrectly start the clock.

How is the official administering the throwin and chopping time supposed to know whether a player, on the other side of the court, is or is not OOB? The administering official is supposed to chop time in when the ball is touched. The official covering the line is to signal the OOB violation. There very likely will be a slight delay in the whistle. So, the timer starts the clock on the chop and stops it on the whistle. There really is no error there short of an explicit rule or case indicating that this is an error.

JetMetFan Tue May 20, 2014 05:10am

Quote:

Originally Posted by Nevadaref (Post 934412)
As posted above in this thread, the text of the NCAA rule is different from that of the NFHS. The NCAA specifies that the touch must be by an "inbounds player" while the NFHS does not have such a requirement.

I'll go back to the "legally touched" part of the NFHS rule as to why the clock shouldn't start. If a player touches the ball while standing on a sideline or endline it's a violation, which is not a legal touch of the ball.

Raymond Tue May 20, 2014 07:08am

Quote:

Originally Posted by Nevadaref (Post 934449)
Why is your default that the officials are incorrectly chopping the clock?
For decades the correct procedure has been to chop the clock. The default should be to chop.

Quote:

Originally Posted by Camron Rust (Post 934450)
How is the official administering the throwin and chopping time supposed to know whether a player, on the other side of the court, is or is not OOB? The administering official is supposed to chop time in when the ball is touched. The official covering the line is to signal the OOB violation. There very likely will be a slight delay in the whistle. So, the timer starts the clock on the chop and stops it on the whistle. There really is no error there short of an explicit rule or case indicating that this is an error.

IN THEORY, we should not be chopping the clock if the ball is illegally touched.

The official covering the line in question can also be the official administering the throw-in, they are not mutually exclusive. And if I'm covering the line, I'm going to know if the player is standing OOB.

MD Longhorn Tue May 20, 2014 09:11am

Seems to me that it's a given that 0.0000 seconds elapsed between the instant the clock should start and the instant the clock should stop, and we, the officials, have positive knowledge of that. No time should run off in this case.

just another ref Tue May 20, 2014 10:38am

The wild card in all this (I believe this was touched on above) is the timer. In high school games I believe it is much too common that the timer does not look for a signal from the official to start the clock at all. I'm sure this would be even more likely to be the case if the throw-in is a long pass involving another line and a second official.

Camron Rust Tue May 20, 2014 01:27pm

Quote:

Originally Posted by BadNewsRef (Post 934457)
IN THEORY, we should not be chopping the clock if the ball is illegally touched.

The official covering the line in question can also be the official administering the throw-in, they are not mutually exclusive. And if I'm covering the line, I'm going to know if the player is standing OOB.

Certainly, they could be the same person. But, in a 3-person game, the administering official is only going to be covering one line much of the time (sometimes two).

As for illegally touched, I don't think it is illegally touched. It is legally touched in an illegal location. And that is the difference.

The NFHS has previously distinguished between the two in a few ways. For example, a kick is considered a violation before the throwin ends. An OOB violation is treated as if it occurs after the throwin ends. This is demonstrated in how the arrow is treated on a throwin. If the violation is a kick (illegal contact) the arrow is not switched. If the violation is an OOB (legal contact, illegal location) the arrow is switched. Likewise with the right to run the endline when there is a violation on a throw-in.


All times are GMT -5. The time now is 03:33am.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1