Block - Charge Out Of Bounds

[Scrapper1]

Originally Posted by Camron Rust

That is not correct. The OOB player can't have LGP, that is all. The rule doesn't come anywhere near declaring that they are liable for all contact by being OOB, just that they can't be guarding. It doesn't become open season for an opponent to run into them if they see they happen to be touching OOB but are not actively guarding.

This topic deserves a different thread, but I just saw your response and so out of laziness, I'm going to respond here

My understanding is that if a defender is out of bounds and contact occurs on the torso, it's a blocking foul. Of course, the defender is not responsible for intentional or flagrant contact initiated by his/her opponent. But in typical block/charge plays, the defender cannot "draw the charge" with a foot out of bounds.

Have I misunderstood the purpose/ramifications of this rule?

[Camron Rust]

Yes, you have (although not everyone agrees with me)

The RULE says (and only says... actually it doesn't really say it but it has been interpreted to mean it) a defender doesn't have LGP if they have OOB status. Nowhere does it define it to be a blocking foul for being OOB.

The CASE declares the player who is OOB as having committed a block but the read-between-the-lines of the case play is that the player is actively guarding his opponent and steps OOB in the process of moving to maintain position. Thus, the player loses LGP by being OOP and is called for the block as a result of not having LGP.

It is intended to cover the situation where a defender shifts over to cut-off a baseline drive and puts their foot on the line. It isn't intended to apply to a player who was near OOB and happens to be on the line when a player comes along and runs into them.

On top of that, this was the other way for 100 years until someone on the rules committee decided to make an interpretation that flipped the way everyone had been calling it (and coaching it) forever.

[Amesman]

So to be totally clear, if Poindexter has hustled into the forecourt after a made shot and is engrossed in his comic book while having a foot on the sideline and A1 dribbles into him, sending him, the educational reading and his bandaged glasses flying, this is indeed a PC foul? (He didn't have LGP, nor was he necessarily trying to.)

[Camron Rust]

Originally Posted by Amesman

So to be totally clear, if Poindexter has hustled into the forecourt after a made shot and is engrossed in his comic book while having a foot on the sideline and A1 dribbles into him, sending him, the educational reading and his bandaged glasses flying, this is indeed a PC foul? (He didn't have LGP, nor was he necessarily trying to.)

It may or may not be a PC foul. You could certainly call nothing. But one thing it is not is a block.

Nothing he was doing required LGP to be legal...which is what the rule on the issue addresses.

[deecee]

Originally Posted by Camron Rust

It may or may not be a PC foul. You could certainly call nothing. But one thing it is not is a block.

Nothing he was doing required LGP to be legal...which is what the rule on the issue addresses.

Yes but in this case the onus of the contact NEEDS to fall on one or the other. So even though what he was doing didn't require LGP he still is the one that will be held responsible for the contact.

Now here is the fly in my ointment say the offensive player uses the ol stiff arm/shove here. I would be inclined to go with a PC foul here BUT being out of bounds and short of an intentional/flagrant act I would want to keep the foul call here consistent and go with a block. But I don't necessarily feel good or even completely agree with that and I am torn between both sides of the aisle on this one.

[Adam]

The rule clearly states the foot out of bounds means he does not have legal guarding position. Nowhere does it say it is an illegal position on the floor.

[Camron Rust]

Originally Posted by deecee

Yes but in this case the onus of the contact NEEDS to fall on one or the other. So even though what he was doing didn't require LGP he still is the one that will be held responsible for the contact.

Now here is the fly in my ointment say the offensive player uses the ol stiff arm/shove here. I would be inclined to go with a PC foul here BUT being out of bounds and short of an intentional/flagrant act I would want to keep the foul call here consistent and go with a block. But I don't necessarily feel good or even completely agree with that and I am torn between both sides of the aisle on this one.

You'd still be inconsistent.

The player with a foot OOB is equivalent to the player in the lane with his/her back to the ball who is 100% stationary and has been in their spot for a while when an offensive player runs into their back. They're not guarding. They don't have LGP....but it is still PC foul. A stationary player is simply not responsible for other players not watching where they are going.

The situation with the player with a foot on the line, even one actively guarding and moving, could have been charge for 100 years until someone decided to make an "editorial" change to flip the rule. There was no reason to change the rule and the justification for calling it an "editorial change" was a joke.

That said, the only time I"m automatically calling a block is when the defender tries to cut-off a drive and stomps their foot OOB to seal off the baseline.....(making what should be considered a good defensive play). In fact, unless they step way OOB, i'm probably not going to see the location defenders foot anyway since nothing else I'm looking at on the play involves the defenders feet.

[BillyMac]

Originally Posted by Camron Rust

The way everyone had been coaching it.

True. When I coached middle school basketball, before the rule change, and taught trapping on the sidelines and endlines, I would teach my players to be sure to cut off the ball handler by keeping a sneaker on the line, to not even give them a chance of sneaking through the trap. That's the way I was coached in high school in the mid-twentieth century, back when my hair was brown, not gray, as it is today.

[BktBallRef]

Can anyone provide a reference where we can read the actual facts as opposed to someone telling us to "read between the lines" and offering their opinion.

[Camron Rust]

Originally Posted by BktBallRef

Can anyone provide a reference where we can read the actual facts as opposed to someone telling us to "read between the lines" and offering their opinion.

The rule book. It says a player can't have LGP while OOB. That is the fact.

[BktBallRef]

Originally Posted by Camron Rust

The rule book. It says a player can't have LGP while OOB. That is the fact.

No one is disputing that. It's all that other crap you're laying on us.

[Camron Rust]

Originally Posted by BktBallRef

No one is disputing that. It's all that other crap you're laying on us.

The rule being discussed is about the definition of LGP, not the definition of a blocking foul. The case play being referenced is about LGP, not about the definition of blocking fouls.

The only way you get that case to mean anything different than what I'm saying is if you take it out of context.

If you want to start doing that, you're going to have a lot of interesting results.

If they had wanted it to mean as you seem to suggest, they would have changed the definition of a blocking foul, not the definition of LGP.