The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Basketball (https://forum.officiating.com/basketball/)
-   -   Screening (https://forum.officiating.com/basketball/41123-screening.html)

SamIAm Thu Jan 17, 2008 03:33pm

Quote:

Originally Posted by JRutledge
Under NF Rule 4-40-7 says: A player who is screened within his/her visual field is expected to avoid contact by going around the screener. In cases of outside of the visual field, the opponent may make inadvertent contact with the screener and if the opponent is running rapidly, the contact may be severe. Such a case is to be ruled incidental contact provided the opponent stops or attempts to stop on contact and moves around the screen, and provided the screener is not displaced if he/she has the ball.

I think you are reading a little too much into what I said. I clearly am saying that just because you do not see the screen, if there is contact the responsibility of the contact is on the defender (or screened player) and just because they did not see the screen. If the defender has several steps, then they can be called for a foul. The only way you would consider the contact incidental if the defender tries to stop or get around the defender. And just because they do not see the screen does not make them exempt from being called for a foul.

Also looking at the NCAA rules under 4-59, I do not see this reference. Maybe your reference is in one of the guideline sections, but I am not seeing that at this time.

Peace

Reminder - we are not discusing the OP as that screen was seen.

My reference is from page 146 (Appendix III, Section 2. Screening, e.

I think the phrase Such a case is to be ruled incidental contact provided the opponent stops or attempts to stop on contact does exempt a player from being called for a foul.

JRutledge Thu Jan 17, 2008 03:48pm

Quote:

Originally Posted by SamIAm
Reminder - we are not discusing the OP as that screen was seen.

My reference is from page 146 (Appendix III, Section 2. Screening, e.

I think the phrase Such a case is to be ruled incidental contact provided the opponent stops or attempts to stop on contact does exempt a player from being called for a foul.

I was only discussing the OP and the issues with the OP. I was not just grabbing a situation out of the air. And I agree that your reference makes some sense, but it must be noted that this is under a title called "Officiating Guidelines." So this is not the way the rule reads exactly and even though I would take into account if a screened players sees or does not see the screen, but I do not think there is support under the actual rule to just not call a foul just because they are blind. Remember, we are talking about a play where a defender had several steps before contact. We are not talking about a step or two before contact. And I will also say that this issue has been addressed by Hank Nichols (I do not work Women's basketball so I cannot speak for their guidelines) in the NCAA Men's tape that this can be called a foul as well as nothing. I will have to look it up, but I would not be completely surprised if there is a play in the current year's tape.

Peace

M&M Guy Thu Jan 17, 2008 04:14pm

Quote:

Originally Posted by SamIAm
I think the phrase Such a case is to be ruled incidental contact provided the opponent stops or attempts to stop on contact does exempt a player from being called for a foul.

I'm not sure if "exempt" is a good word to use in this case. I had 2 different screen plays last night in the same game that might illustrate the difference.

First one, post player sets a screen up high and waits as the ballhandler runs the defender right into it. Defender hits the screen, didn't try to stop, and crumples into a heap right at the feet of the post player. Post player was knocked back a step, and contact was pretty severe, perhaps even resulted in a slight injury, but definitely incidental - no foul.

Second play, defender sees the screen, slows down a little on contact, but then decides they're going to keep going to get to the ball handler behind the screener. Both players go down, and even though the contact was less than the first play, I called the foul on the defender for displacing the opponent. Yes, they initially slowed down before contact, but the contact caused the screener to go down and put them in a disadvantageous position. I'm not going to exempt the defender from a foul in this case just because they "attempted to stop" first before running over the screener.

Jurassic Referee Thu Jan 17, 2008 04:59pm

Quote:

Originally Posted by SamIAm
I think not,

From the NCAA rules which mirror the Fed rules in this instance (I think)

In cases of blind screens, the opponent may make inadvertent contact
with the screener; and, if the opponent is running rapidly, the contact
may be severe. Such a case is to be ruled as incidental contact, provided
that the opponent stops (or attempts to stop) on contact and moves
around the screen, and provided that the screener is not displaced if he
or she has the ball.

There's your problem right there. The play that we are discussing is <b>NOT</b> a blind screen. Blind screens are screens set outside the opponent's visual field. We're discussing screens that are set <b>within</b> an opponent's visual field.

Apples and oranges. For blind screens, you have to give time/distance-one step for NCAA. For screens within an opponent's visual field, that opponent is expected to stop and go around the screen with no time/distance allowed.

NCAA 4-59-3(a) describes a blind screen(outside the opponent's visual field...i.e. from behind); 4-59-3(b) refers to screens within the visual field of a an opponent...i.e. from the front or side.

You cited (e) from NCAA Appendix 3 above. You should have cited Appendix 3(f), That's what is being discussed.

SamIAm Fri Jan 18, 2008 12:28pm

Quote:

Originally Posted by M&M Guy
I'm not sure if "exempt" is a good word to use in this case. I had 2 different screen plays last night in the same game that might illustrate the difference.

First one, post player sets a screen up high and waits as the ballhandler runs the defender right into it. Defender hits the screen, didn't try to stop, and crumples into a heap right at the feet of the post player. Post player was knocked back a step, and contact was pretty severe, perhaps even resulted in a slight injury, but definitely incidental - no foul.

Second play, defender sees the screen, slows down a little on contact, but then decides they're going to keep going to get to the ball handler behind the screener. Both players go down, and even though the contact was less than the first play, I called the foul on the defender for displacing the opponent. Yes, they initially slowed down before contact, but the contact caused the screener to go down and put them in a disadvantageous position. I'm not going to exempt the defender from a foul in this case just because they "attempted to stop" first before running over the screener.

My post concerned JRut's post #12 indicating he did not think it mattered if the screen was seen or not. I then posted again but only pulled a piece of post #13, still concerning whether the screen was seen or not.

I agree with both your plays.

The OP is a no-brainer for experienced officials knowing the screen was seen.

SamIAm Fri Jan 18, 2008 12:37pm

Quote:

Originally Posted by Jurassic Referee
There's your problem right there. The play that we are discussing is <b>NOT</b> a blind screen. Blind screens are screens set outside the opponent's visual field. We're discussing screens that are set <b>within</b> an opponent's visual field.

Apples and oranges. For blind screens, you have to give time/distance-one step for NCAA. For screens within an opponent's visual field, that opponent is expected to stop and go around the screen with no time/distance allowed.

NCAA 4-59-3(a) describes a blind screen(outside the opponent's visual field...i.e. from behind); 4-59-3(b) refers to screens within the visual field of a an opponent...i.e. from the front or side.

You cited (e) from NCAA Appendix 3 above. You should have cited Appendix 3(f), That's what is being discussed.

My post included a quote for JRut, #12, where JRut indicated he didn't think it mattered if the screen was seen or not. I questioned that point, not the OP. I think that is indicated by having quoted JRut in my post.

JRutledge Fri Jan 18, 2008 12:45pm

Quote:

Originally Posted by SamIAm
My post included a quote for JRut, #12, where JRut indicated he didn't think it mattered if the screen was seen or not. I questioned that point, not the OP. I think that is indicated by having quoted JRut in my post.

With all due respect Sam, I think both M&M and JR took my comments in the context of thread and the OP. You seemed to take my comments in a general way outside of what we were talking about. That is why I believe both responded to your assertion of what should or should not be called. I stand by what I said in the context of what was asked in the OP. Whether they "technically" see a screen coming with multiple steps before contact does not eliminate their responsibility for being called with a foul.

Peace


All times are GMT -5. The time now is 05:31pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1