The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Basketball (https://forum.officiating.com/basketball/)
-   -   Legal Guarding position or Blocking Foul? (Video) (https://forum.officiating.com/basketball/104374-legal-guarding-position-blocking-foul-video.html)

JRutledge Tue Feb 12, 2019 01:03am

Legal Guarding position or Blocking Foul? (Video)
 
<iframe width="560" height="315" src="https://www.youtube.com/embed/tymcMLFBrf4" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>

Peace

Camron Rust Tue Feb 12, 2019 01:09am

From the first angle, I thought that the defender got there. However, from the endline view, no. He was still moving in to the path after the shooter jumped.

Pantherdreams Tue Feb 12, 2019 08:14am

PC or no call. He gets his feet to a spot on floor before the shooter gets off the ground. He can turn so that's not on him.

If you want to argue he got the spot but wasn't squared up to the shooter before contact so he never established LGP then you can pass on the charge and go no call if that's your bag.

I still don't feel like shooter is responsible for the contact. He gave him time and space to catch and land, now the player with the ball has no expectation of time and space and has to expect to be guarded must be able to stop. Not punishing d for getting to spot before the offense and the offense going through them anyway.

bob jenkins Tue Feb 12, 2019 08:53am

Pc

Raymond Tue Feb 12, 2019 09:15am

Close. In slow motion the defender is there before shooter goes airborne. In real time speed the defender appears to get there a split second too late.

My concern is that the Lead guessed b/c when he rotated his eyes were directed towards the on-ball match up in front of his partner instead of towards the paint where he had 2 potential secondary defenders moving into his primary.

bucky Tue Feb 12, 2019 12:23pm

Blocking foul

Pantherdreams Tue Feb 12, 2019 12:42pm

Quote:

Originally Posted by bucky (Post 1030152)
Blocking foul

What do you have D doing wrong?

Camron Rust Tue Feb 12, 2019 12:54pm

Quote:

Originally Posted by Pantherdreams (Post 1030155)
What do you have D doing wrong?

Since I also said block....he got his feet down for sure but his torso was not yet in the path until after the shooter jumped. You don't own a spot until your body is over it....your feet only mark the space you own if they are inside your shoulders. Therefore, he didn't have LGP in time.

JRutledge Tue Feb 12, 2019 01:58pm

The defender clearly got in front of the cutter/ball handler. Now in live time this was very close. But his feet are both "set" which is not a requirement and not sure what his torso has to do when both your feet are planted in the ground?

This to me was a charge all the way. I think the lead rotated last and did not see the defender clearly and defaulted and called a foul on the defender as we tend to do.

Peace

Pantherdreams Tue Feb 12, 2019 02:11pm

Not sure I see it that way but I see what you are saying.

However I would still contend that even if he may not have established (LGP which I think he did) by not squaring his chest into the path in time wouldn't mean it has to be block. The title of the OP only gives us those two options but there are alternatives and the shooter is choosing to leave his feet through space that is occupied whether its by a player in LGP or not doesn't mean it has to be a block. Players are still entitled to a spot on the floor and the intent of the rules has never been to penalize with fouls for getting jumped or run into by the player with the ball.

Its bang bang and we are splitting hairs through slow motion replay. I probably would have called PC but if I'm on a crew with a guy who says he saw a block on a play like this I'm not arguing.

Camron Rust Tue Feb 12, 2019 03:52pm

Quote:

Originally Posted by JRutledge (Post 1030168)
The defender clearly got in front of the cutter/ball handler. Now in live time this was very close. But his feet are both "set" which is not a requirement and not sure what his torso has to do when both your feet are planted in the ground?

Peace

Both feet must be on the floor to obtain LGP...you know that. The player must also be in the path...that means torso in the path, not the feet. The space occupied is defined by the body (torso). The feet being down defines the time that the position of the body becomes legal. It does not allow the body to continue to move to a new space if it is too late to do so.

Quote:

Guarding is the act of legally placing the body in the path of an offensive opponent.....

A player who extends an arm, shoulder, hip or leg into the path of an opponent is not considered to have a legal position if contact occurs.
By rule, the player is only legally occupying the space their body is in when the feet come down. They do not legally occupy the space over the feet without the body being over them.

JRutledge Tue Feb 12, 2019 04:18pm

It would be one thing if he was leaning all the way over to make contact, but that is not what happened. It sounds like you are trying to require that he is totally still before any contact takes place. Sorry, but that is not how I read the rules on this situation.

Peace

ilyazhito Tue Feb 12, 2019 04:44pm

Would this be a block of the "straight block" variety or of the "block-point" (block because of restricted area) variety? I would have either, because the defender's right foot is in the restricted area when he is trying to establish position on the offensive player. I also have the defender failing to beat the offensive player to the spot before the offensive player goes airborne. Thus, I cannot call this play a charge.

Raymond Tue Feb 12, 2019 04:55pm

Quote:

Originally Posted by ilyazhito (Post 1030185)
... I would have either, because the defender's right foot is in the restricted area when he is trying to establish position on the offensive player...

You must be watching this on a phone, because on my 19" desktop monitor the defender is clearly outside of the RA.

Camron Rust Tue Feb 12, 2019 05:53pm

Quote:

Originally Posted by JRutledge (Post 1030183)
It would be one thing if he was leaning all the way over to make contact, but that is not what happened. It sounds like you are trying to require that he is totally still before any contact takes place. Sorry, but that is not how I read the rules on this situation.

Peace

Nah, I don't care if he is still or not, but I want the body to be in the path before the shooter jumps as is required by the rule. If the body is still moving sideways or backwards, I don't care, I'll still have a PC if the body got into the path in time. Otherwise the defender has not met the requirements of LGP and I'm not fudging the requirements to favor a defender that is late if it means calling a charge instead. However, if it is an option, I might pass on the contact.

CJP Tue Feb 12, 2019 06:00pm

Punch it. PC.

ilyazhito Tue Feb 12, 2019 06:27pm

Quote:

Originally Posted by Raymond (Post 1030186)
You must be watching this on a phone, because on my 19" desktop monitor the defender is clearly outside of the RA.

I was watching the video on a laptop, and I had the defender in the RA (the "on or over" language comes to mind). Even if he were not in the RA, the defender still failed to beat the offensive player to the spot prior to the offensive player going airborne, so there would be a block anyway.

Raymond Tue Feb 12, 2019 06:29pm

Quote:

Originally Posted by ilyazhito (Post 1030195)
I was watching the video on a laptop, and I had the defender in the RA (the "on or over" language comes to mind). Even if he were not in the RA, the defender still failed to beat the offensive player to the spot prior to the offensive player going airborne, so there would be a block anyway.

He's not in the RA, and if you went to the monitor to review this play you would be getting it wrong by saying he's in the RA.

Sent from my SM-N950U using Tapatalk

Camron Rust Tue Feb 12, 2019 07:31pm

Quote:

Originally Posted by Raymond (Post 1030196)
He's not in the RA, and if you went to the monitor to review this play you would be getting it wrong by saying he's in the RA.

Sent from my SM-N950U using Tapatalk

His right foot was certainly not in the RA. However, I'm not so sure about the left. It appears he may be out, but I can't say with 100% certainty from the angle we have that his heel was not over the RA.

Freddy Tue Feb 12, 2019 08:06pm

Quote:

Originally Posted by JRutledge (Post 1030168)
. . .defaulted and called a foul on the defender as we tend to do. Peace

Why do "we" tend to do that? Because still, in spite of the clinical imprecations of J.D. and others for us to go up with a closed-fist stop clock signal first, too many of "we" still impulsively go up with two fists in the air at first contact which is the habitual precursor of the dynamic fist-banging on the hips, thus the default block. The beginning habit compels the end call, regardless the inaccuracy.

#olderthanilook Wed Feb 13, 2019 10:49am

PC. Slo mo confirms.

Extremely difficult play to rule on in real time, though. B1 made an outstanding athletic play to obtain LGP before A1 became an airborne shooter.

JRutledge Wed Feb 13, 2019 12:23pm

Quote:

Originally Posted by Freddy (Post 1030206)
Why do "we" tend to do that? Because still, in spite of the clinical imprecations of J.D. and others for us to go up with a closed-fist stop clock signal first, too many of "we" still impulsively go up with two fists in the air at first contact which is the habitual precursor of the dynamic fist-banging on the hips, thus the default block. The beginning habit compels the end call, regardless the inaccuracy.

I cannot explain why other people do this, but I think it is easier to justify a blocking foul because most people do not understand the rule. And I am not talking about the officials. I am talking about the coaches and players and even fans. Usually, PC fouls are more controversial in nature. You get all kinds of comments as if to suggest there is no way you could have called a PC foul, even though all the rules requirements are met. Even Camaron's position to me is part of the problem. Because he is asking for the defender to be damn near perfect in order to have a PC foul when the rules and even the administrators like JD are clearly saying things like this should be called a PC foul. No one made a stink over this call when the officials called this foul. It would have been minutes of Bilas going on and on about how that is not a PC foul and how the NCAA needs to address the issue over what appears to many her as a clear PC foul.

Peace

Raymond Wed Feb 13, 2019 01:20pm

Quote:

Originally Posted by Freddy (Post 1030206)
Why do "we" tend to do that? Because still, in spite of the clinical imprecations of J.D. and others for us to go up with a closed-fist stop clock signal first, too many of "we" still impulsively go up with two fists in the air at first contact which is the habitual precursor of the dynamic fist-banging on the hips, thus the default block. The beginning habit compels the end call, regardless the inaccuracy.

Most of the officials who go directly to pounding their hips are veteran, established officials--at the college and HS levels.

Kansas Ref Wed Feb 13, 2019 03:41pm

Quote:

Originally Posted by JRutledge (Post 1030168)
The defender clearly got in front of the cutter/ball handler. Now in live time this was very close. But his feet are both "set" which is not a requirement and not sure what his torso has to do when both your feet are planted in the ground?

This to me was a charge all the way. I think the lead rotated last and did not see the defender clearly and defaulted and called a foul on the defender as we tend to do.
Peace

*Very astute point being made here--and I dare say that this tendency will be extremely difficult [if not impossible] to dis-embed from the collective thought-process.

jeremy341a Wed Feb 13, 2019 03:50pm

Quote:

Originally Posted by Camron Rust (Post 1030159)
Since I also said block....he got his feet down for sure but his torso was not yet in the path until after the shooter jumped. You don't own a spot until your body is over it....your feet only mark the space you own if they are inside your shoulders. Therefore, he didn't have LGP in time.

Looks like his torso is in the path. Offense is just leaving floor.

https://i.ibb.co/fFXsrTC/charge.jpg

Camron Rust Wed Feb 13, 2019 04:21pm

Quote:

Originally Posted by jeremy341a (Post 1030257)
Looks like his torso is in the path. Offense is just leaving floor.

Perhaps so, depending on what the path is....and you can't tell that from a still shot.

#olderthanilook Wed Feb 13, 2019 05:12pm

Quote:

Originally Posted by Camron Rust (Post 1030259)
Perhaps so, depending on what the path is....and you can't tell that from a still shot.

Still shots just aren't necessarily conclusive. Context is typically absent.

We need to see the beginning, middle and end of the play for total assessment.

Rich Wed Feb 13, 2019 05:24pm

The mistake is expecting perfection by the defense. Playing defense is hard.

PC.

Camron Rust Wed Feb 13, 2019 05:58pm

Quote:

Originally Posted by Rich (Post 1030263)
The mistake is expecting perfection by the defense. Playing defense is hard.

PC.

So, you expect perfection from the offense? Isn't it hard too?

rsl Thu Feb 14, 2019 01:33am

Trip.

The foot is outside the shoulder and I think there is first contact there.

Tough call, but I'm sure I would have called it the defense in real time.

jeremy341a Thu Feb 14, 2019 10:58am

Quote:

Originally Posted by Camron Rust (Post 1030259)
Perhaps so, depending on what the path is....and you can't tell that from a still shot.

Unless the offense is jumping completely sideways he is definitely in the path.
I am surprised that anyone could see this as a block with the benefit of slow mo replay. On the video change the slow mo replay speed to .25 and go nearly frame by frame and he is clearly in position before the offense leaves the floor.
Now in fairness I would have called a block in real time.


All times are GMT -5. The time now is 12:26pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1