The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Basketball (https://forum.officiating.com/basketball/)
-   -   Charge or Block? (https://forum.officiating.com/basketball/89420-charge-block.html)

Dave9819 Thu Feb 23, 2012 11:12pm

Charge or Block?
 
A1 drives the lane.

B1 is set and standing on the lane line and is not moving, is vertical, etc, however, is not facing A1's torso.

On the drive, A1 contacts B1's shoulder.

A1 is not hindered and B1 falls to the ground. Since A1 hit B1's shoulder, would that be a charge on A1, Block on B1, or a "no call" (if B1 decided to embelish and go down to the ground)?

Thanks!

JRutledge Thu Feb 23, 2012 11:18pm

We have had this discussion before, but I would have a charge. The defender did not do anything wrong. LGP is for a player that has established a legal position and has rights to move. This player did not move, they just stood there. Every player has a right to their position on the floor and nothing gives the ball handler the right to run into any player they like.

Peace

Dave9819 Thu Feb 23, 2012 11:28pm

To take this a step further - if you believed that B1 "embelished" and was trying to draw the foul - in other words, the contact was not severe enough that it would cause B1 to be displaced, would you go with a no-call or a block on B1?

JRutledge Thu Feb 23, 2012 11:30pm

Quote:

Originally Posted by Dave9819 (Post 827275)
To take this a step further - if you believed that B1 "embelished" and was trying to draw the foul - in other words, the contact was not severe enough that it would cause B1 to be displaced, would you go with a no-call or a block on B1?

I would try my best to call what the contact created. If the contact did not affect anything, then I got nothing. If the contact really affected the play then I have a call. But if all the defender did was stand there, I cannot see anything I would call on B1 in this case.

Peace

JugglingReferee Thu Feb 23, 2012 11:48pm

Quote:

Originally Posted by Dave9819 (Post 827273)
A1 drives the lane.

B1 is set and standing on the lane line and is not moving, is vertical, etc, however, is not facing A1's torso.

On the drive, A1 contacts B1's shoulder.

A1 is not hindered and B1 falls to the ground. Since A1 hit B1's shoulder, would that be a charge on A1, Block on B1, or a "no call" (if B1 decided to embelish and go down to the ground)?

Thanks!

Quote:

Originally Posted by Dave9819 (Post 827275)
To take this a step further - if you believed that B1 "embelished" and was trying to draw the foul - in other words, the contact was not severe enough that it would cause B1 to be displaced, would you go with a no-call or a block on B1?

Definitely not a block. Ever.

JetMetFan Thu Feb 23, 2012 11:53pm

Quote:

Originally Posted by Dave9819 (Post 827273)
A1 drives the lane.

B1 is set and standing on the lane line and is not moving, is vertical, etc, however, is not facing A1's torso.

On the drive, A1 contacts B1's shoulder.

A1 is not hindered and B1 falls to the ground. Since A1 hit B1's shoulder, would that be a charge on A1, Block on B1, or a "no call" (if B1 decided to embelish and go down to the ground)?

Thanks!

You're saying B1 took that position but wasn't facing A1? Was B1's back to A1?

Dave9819 Fri Feb 24, 2012 12:13am

B1 was to the right of A1 so when A1 ran past B1, there shoulders contacted each other. B1 fell (more so trying to draw the charging call) when A1 contacted B1's shoulder. So, when I said they weren't facing each other, I meant they were not directly in front of each other. I hope that answered your question, JetMetFan.

Camron Rust Fri Feb 24, 2012 01:34am

Quote:

Originally Posted by Dave9819 (Post 827281)
B1 was to the right of A1 so when A1 ran past B1, there shoulders contacted each other. B1 fell (more so trying to draw the charging call) when A1 contacted B1's shoulder. So, when I said they weren't facing each other, I meant they were not directly in front of each other. I hope that answered your question, JetMetFan.

It is commonly said that if the defender doesn't take it in the chest, it is a block. People are commonly wrong.

All that matters is whether B1 got to whatever position they were in before A1 got to it. If A1 is able to divert and not hit B1 in the chest, B1 shouln't be penalized for A1 being able to redirect. You said B1 was "set", which is not really the proper term, but good enough to describe what you meant.....it was NOT a block.

As for a charge, did the contact knock B1 down, or did B1 fall down. If it knocked B1 down, charge, otherwise it would be a no-call.

Being off-center as you describe means it is less likely that the contact knocked B1 down, but it is not impossible.

Adam Fri Feb 24, 2012 09:19am

Quote:

Originally Posted by JetMetFan (Post 827279)
You're saying B1 took that position but wasn't facing A1? Was B1's back to A1?

Doesn't matter.

Welpe Fri Feb 24, 2012 09:37am

If B1 does not have a legal guarding position (and in this case he doesn't) then screening principles are going to apply. In this case, it is even simpler since B1 is stationary. Every player is entitled to their space on the floor.

If A1 contacts B1, then we need to determine if the contact was enough to disadvantage B1. If it was not, we could pass on a whistle here. It certainly cannot be a block.

M&M Guy Fri Feb 24, 2012 11:41am

Quote:

Originally Posted by Snaqwells (Post 827318)
Doesn't matter.

Isn't "legal guarding position" the same as "legal position"? Doesn't that mean the player has to face the opponent? ;)

(Oops, I did say I was done with that, didn't I...) :D

Adam Fri Feb 24, 2012 11:47am

Quote:

Originally Posted by M&M Guy (Post 827344)
Isn't "legal guarding position" the same as "legal position"? Doesn't that mean the player has to face the opponent? ;)

(Oops, I did say I was done with that, didn't I...) :D

You leave me no choice....

Camron Rust Fri Feb 24, 2012 02:44pm

Quote:

Originally Posted by Snaqwells (Post 827348)
You leave me no choice....

Traveling? :p


All times are GMT -5. The time now is 07:18am.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1