end of game timing issue

[just another ref]

Visitors ball under their own basket with 1.2 seconds left. A1's pass is intercepted by B1 who unsuccessfully asks for a time out before landing OOB. But, simultaneously with the whistle or a tiny fraction afterward, the buzzer sounds, clock shows 0:00, game over. From the description I got, it sounds like the clock may have started before the pass was touched. The question is, even if the official sees the clock start to move while the pass is in the air, there is no way to make a correction here, correct?

A footnote: Visitors' coach threw a fit, saying time should be put back. Officials apparently had a lengthy discussion about the play, during which visitors' fans threw stuff all over the court. Then, apparently thinking the game was not over, the visiting players scurried around and cleaned up the debris.

[Mark Padgett]

Originally Posted by just another ref

Visitors ball under their own basket with 1.2 seconds left. A1's pass is intercepted by B1 who unsuccessfully asks for a time out before landing OOB.

A better question is why was B1's TO request unsuccessful? If he caught the pass while in the air and asked prior to landing OOB, you grant it. Even if he didn't, it's a dead ball after landing OOB and if he asks then, you should grant it.

[JoeTheRef]

Are you saying that the official saw the clock start while the ball was in the air before it was touched??? Why wouldn't he be able to put time back on?

[just another ref]

Originally Posted by JoeTheRef

Are you saying that the official saw the clock start while the ball was in the air before it was touched??? Why wouldn't he be able to put time back on?

I'm not sure what they saw. I was saying even if they did see the clock start to move before the touch, it would be virtually impossible to have definite knowledge of how many tenths had run off when it actually was touched.

[just another ref]

Originally Posted by Mark Padgett

A better question is why was B1's TO request unsuccessful? If he caught the pass while in the air and asked prior to landing OOB, you grant it. Even if he didn't, it's a dead ball after landing OOB and if he asks then, you should grant it.

I wasn't there. I'm not sure whether they would have granted his request or not, but the buzzer sounded, more or less with the whistle, so it really didn't matter.

[blindzebra]

This is why the fed needs a touching equals X amount of time off rule.

This is a timers error, the last known time is 1.2...there is only a game over provision for an officials error.

This should be A's ball at the spot of the OOB violation with 1.2 remaining.

[JoeTheRef]

Originally Posted by blindzebra

This is why the fed needs a touching equals X amount of time off rule.

This is a timers error, the last known time is 1.2...there is only a game over provision for an officials error.

This should be A's ball at the spot of the OOB violation with 1.2 remaining.

If B called timeout while in control before going OOB then the timeout should be granted and there is no OOB violation.

[blindzebra]

Originally Posted by JoeTheRef

If B called timeout while in control before going OOB then the timeout should be granted and there is no OOB violation.

I'm just going by what was in the OP...in either case it is someones ball at that spot with 1.2 left.

[just another ref]

Originally Posted by JoeTheRef

If B called timeout while in control before going OOB then the timeout should be granted and there is no OOB violation.

This is true if the official recognized the timeout request, then looked at the clock and saw a specific amount of time remaining. Apparently this was not the case. I do not know (yet) if the official recognized the request before the player landed or not.

[just another ref]

To explain further, when I say that the clock may have started early, it may be totally unjustified. How long is a long time for a player to be in the air in a play such as this. I have no information about exactly how much height or distance was covered, but I picture a steal based more on anticipation than on any kind of incredibly athletic play. Also, we must remember that the catch was made while the player was already in the air, so if the timing was correct, the hang time was some amount in excess of 1.2. Is this a long time in the air or not?

[rainmaker]

It seems as though the rules as stated by JR would pretty much match "common sense". One second isn't very much time to control the ball and then signal a TO. I don't see how a coach could think they "deserve" any extra time, regardless of whether the clock was right.

[just another ref]

Originally Posted by just another ref

To explain further, when I say that the clock may have started early, it may be totally unjustified. How long is a long time for a player to be in the air in a play such as this. I have no information about exactly how much height or distance was covered, but I picture a steal based more on anticipation than on any kind of incredibly athletic play. Also, we must remember that the catch was made while the player was already in the air, so if the timing was correct, the hang time was some amount in excess of 1.2. Is this a long time in the air or not?

Did the math myself. If this kid is traveling at 14 mph, (100 yd. dash in 14.6)
in 1.2 seconds he would cover nearly 25 feet. Sounds doubtful to me.

[jdw3018]

Originally Posted by just another ref

Also, we must remember that the catch was made while the player was already in the air, so if the timing was correct, the hang time was some amount in excess of 1.2. Is this a long time in the air or not?

Just to add to this: I watched a Sports Science episode where they timed hang-time for some high-flying NBA players.

None of them were in the air an entire second. Just over .9 was the best.

So, while it has nothing to do with what you can and can't do as an official in this situation, there is absolutely no way 1.2 seconds can come off the clock between the time the player gathers the ball in the air and returns to the ground...

[just another ref]

Originally Posted by blindzebra

This is why the fed needs a touching equals X amount of time off rule.

This is a timers error, the last known time is 1.2...there is only a game over provision for an officials error.

This should be A's ball at the spot of the OOB violation with 1.2 remaining.

Based on what?

[Damian]

If an official has direct knowledge of a timing issue, they can resolve it. In this case, if you knew you had 1.2 sec and a timeout was called at first touch, you could adjust this.