The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Basketball (https://forum.officiating.com/basketball/)
-   -   North Carolina @ Indiana (https://forum.officiating.com/basketball/101899-north-carolina-indiana.html)

jpgc99 Fri Dec 02, 2016 10:29am

Quote:

Originally Posted by deecee (Post 994025)
Because once you make that signal you are obligate to make the call. It has it's time and place.

What do you mean by this? Are you suggesting that you would not have called this a violation?

deecee Fri Dec 02, 2016 10:40am

Quote:

Originally Posted by jpgc99 (Post 994030)
What do you mean by this? Are you suggesting that you would not have called this a violation?

This was an obvious violation. What I mean is that once you make that signal you are obligated to make the call, there may be situations where there are circumstances that you may not want to make the call (it's similar to a preliminary on a block charge from the C or T, if you don't signal you don't have a call either way). If the violation happens early enough you can make the signal. This violation happened close enough to the release where the signal wasn't necessary.

SNIPERBBB Fri Dec 02, 2016 10:52am

Technically you are not obligated if the try is successful

RefRich Fri Dec 02, 2016 11:41am

Foul, No Violation
 
Quote:

Originally Posted by ballgame99 (Post 993972)
on the potential BC violation, if he is in the air when he catches the ball doesn't he get to land where he wants? Its hard to see from this angle, but let's say he leaves the floor with both feet (from the FC) and catches the ball while airborne and lands strattled on the line, isn't he considered to still be in BC status?

According to Rule 9.9, there is not violation because there has been no established position in the front court. All of the discussion so far appears to be that the ball is in the front court already. The jumping from the front court to the back court is not a factor because nothing has been established yet.

"in order to have a backcourt violation, “player and team” control must first be established in the frontcourt. This means a player must have been dribbling or holding the ball entirely in the frontcourt."

Isn't this a true statement? Now if his back foot lands in the newly established front court then when his front foot lands in the now defined back court it would be a violation. But in this case it would be a foul (based on the angle that I see visable)

JRutledge Fri Dec 02, 2016 11:53am

The player's location is where he jumped from. He jumped from the FC and touched the ball in the air. Then he appears to land at least in part in the BC. That is a violation.

Peace

SC Official Fri Dec 02, 2016 01:27pm

Quote:

Originally Posted by RefRich (Post 994037)
According to Rule 9.9, there is not violation because there has been no established position in the front court. All of the discussion so far appears to be that the ball is in the front court already. The jumping from the front court to the back court is not a factor because nothing has been established yet.

"in order to have a backcourt violation, “player and team” control must first be established in the frontcourt. This means a player must have been dribbling or holding the ball entirely in the frontcourt."

Isn't this a true statement? Now if his back foot lands in the newly established front court then when his front foot lands in the now defined back court it would be a violation. But in this case it would be a foul (based on the angle that I see visable)

An airborne player retains the status of where he last touched the floor. You have frontcourt status if you jump from the frontcourt and have backcourt status once you land.

And player control is not (necessarily) required in the frontcourt to have a backcourt violation.

Raymond Fri Dec 02, 2016 02:32pm

Quote:

Originally Posted by deecee (Post 994031)
This was an obvious violation. What I mean is that once you make that signal you are obligated to make the call, there may be situations where there are circumstances that you may not want to make the call (it's similar to a preliminary on a block charge from the C or T, if you don't signal you don't have a call either way). If the violation happens early enough you can make the signal. This violation happened close enough to the release where the signal wasn't necessary.

It's really not that complicated in this play. The Slot official missed the violation and the Lead came in with the whistle.

Adam Fri Dec 02, 2016 03:19pm

Quote:

Originally Posted by RefRich (Post 994037)
According to Rule 9.9, there is not violation because there has been no established position in the front court. All of the discussion so far appears to be that the ball is in the front court already. The jumping from the front court to the back court is not a factor because nothing has been established yet.

"in order to have a backcourt violation, “player and team” control must first be established in the frontcourt. This means a player must have been dribbling or holding the ball entirely in the frontcourt."

Isn't this a true statement? Now if his back foot lands in the newly established front court then when his front foot lands in the now defined back court it would be a violation. But in this case it would be a foul (based on the angle that I see visable)

Player and team control had already been established, then a pass was thrown between teammates. The receiving teammate jumped from the FC (he continues to have FC status until he lands) and catches the ball. Now you have player and team control in the FC (player control in the FC is not actually required, but it's hear in this play). As soon as he lands in the BC you have a violation.

AremRed Fri Dec 02, 2016 03:29pm

Quote:

Originally Posted by BadNewsRef (Post 994029)
The person who should have displayed that signal did not, so another official made the call.

I believe the Lead did make the delayed violation call and the whistle heard in the video is his, despite the lack of a delayed violation signal.


All times are GMT -5. The time now is 06:47pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1