The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Basketball (https://forum.officiating.com/basketball/)
-   -   Player Control? (https://forum.officiating.com/basketball/7183-player-control.html)

rainmaker Tue Jan 28, 2003 01:57am

Quote:

Originally posted by canuckrefguy
FYI, where I come from, we play NCAA rules.

This is the point! On this board, if you're using other than NFHS rules, you should say so the first time you post. Of course, when NCAA rules make this a no-call, it's a no-call. In the NFHS, except for a few areas, it's PC every time. When newbies read this board, they need to understand that high school rules are not the same as what they see on TV, and that they should be calling the system they are assigned under. When you encourage them to think that basketball is only played by your system, it is confusing at best. Please don't muddy the waters, by giving the impression that yours is the only right way. Especially on the calls that are likely to make or break a ref, and that bring huge reactions from the crowd, it's important that the new person know clearly what the rules are and how they should be applied. This board is generally for NFHS rules, unless otherwise stated.

canuckrefguy Tue Jan 28, 2003 02:39am

Sorry....

It's my first chat board!

Jurassic Referee Tue Jan 28, 2003 03:56am

Quote:

Originally posted by canuckrefguy

FYI, where I come from, we play NCAA rules.


The NCAA rule that I quoted(R4-8-1AR6)gives you guidance on how the NCAA wants this type of play called(for men's play,anyway).Basically,you were ignoring this NCAA rule,and you were choosing to make up your own definitive rule,based on your own personal preference.You can get yourself in deep doo-doo following that slippery slope. JMO.

canuckrefguy Tue Jan 28, 2003 04:45am

Quote:

Originally posted by Jurassic Referee
[/B]
The NCAA rule that I quoted(R4-8-1AR6)gives you guidance on how the NCAA wants this type of play called(for men's play,anyway).Basically,you were ignoring this NCAA rule,and you were choosing to make up your own definitive rule,based on your own personal preference. [/B][/QUOTE]

*SIGH*, sorry to drag this out, but....

Rule 4, Section 8, Article 6:

"...When the ball goes through the basket before contact occurs, the contact shall be ignored unless B1 has been placed at a disadvantage by being unable to rebound when the shot is missed or unable to put the ball in play without delay..."

Seems to me if A1 dunks, then hits B1, it's a no-call unless the contact was so severe that B1 can't get up in a timely fashion. The intent of the rule seems to be to penalize a layup/dunker who creates EXCESSIVE contact after the made basket, with a defender who's under the hoop. Judgement here would be on a case-by-case basis and could go EITHER way, and often does.

Article 7 (Women):

"B1 is standing directly under the basket before A1 jumps for a layup. The forward momentum of airborne shooter A1 causes A1 to run into B1. RULING: B1 is not in a legal guarding position. Blocking foul on B1."

This leans more towards my position of the shooter in this situation NOT being at fault.

I am certainly guilty of not communicating well enough in this thread. But to say I am ignoring the rule or making up my own rule based on "personal preference" is inaccurate.

I know I'm new around here, and I will always defer to the more experienced stripes, but I deserve better than that.

Jurassic Referee Tue Jan 28, 2003 05:34am

Quote:

Originally posted by canuckrefguy
[/B]
Rule 4, Section 8, Article 6:

"...When the ball goes through the basket before contact occurs, the contact shall be ignored unless B1 has been placed at a disadvantage by being unable to rebound when the shot is missed or unable to put the ball in play without delay..."

Seems to me if A1 dunks, then hits B1, it's a no-call unless the contact was so severe that B1 can't get up in a timely fashion. The intent of the rule seems to be to penalize a layup/dunker who creates EXCESSIVE contact after the made basket, with a defender who's under the hoop. Judgement here would be on a case-by-case basis and could go EITHER way, and often does.

Article 7 (Women):

"B1 is standing directly under the basket before A1 jumps for a layup. The forward momentum of airborne shooter A1 causes A1 to run into B1. RULING: B1 is not in a legal guarding position. Blocking foul on B1."

This leans more towards my position of the shooter in this situation NOT being at fault.

I am certainly guilty of not communicating well enough in this thread. But to say I am ignoring the rule or making up my own rule based on "personal preference" is inaccurate.

I know I'm new around here, and I will always defer to the more experienced stripes, but I deserve better than that. [/B][/QUOTE]1)The original post in this thread said that the shooter knocked the defensive player down after dunking.You said it is a "no call" in every case,no matter whether the defensive player is now unable to put the ball into play without delay.You never have a foul on the shooter,no matter what.That is contrary to the rule that you quoted above(AR6).Wouldn't you call knocking someone down creating "EXCESSIVE contact" too,Btw?
2)Womens AR7 says it should be a blocking foul.You say it is a "no call" instead.
3)You now say above "Judgement here would be on a case-by case-basis and could go EITHER way,and often does".That's completely different than the stance that you originally took-i.e.it's never a foul on the shooter.

Comments?

[Edited by Jurassic Referee on Jan 28th, 2003 at 05:08 AM]

Nevadaref Tue Jan 28, 2003 06:50am

Quote:

Originally posted by Jurassic Referee

Comments?

My comment is that it is nice to see you arguing with someone besides me for a change!

dhodges007 Tue Jan 28, 2003 08:12am

My question is in a play like this what is the contact? Does he bump him and would b1 have a fair chance of getting the rebound if he was in position to do so? Or does a1 knock him off the court? I am looking at the type of contact in this play. If we have a crash and one or both players get knocked over, not a flop, I have PC. If they both bump or if b1 flops, play on.

canuckrefguy Tue Jan 28, 2003 11:12am

Quote:

Originally posted by Jurassic Referee
You now say above "Judgement here would be on a case-by case-basis and could go EITHER way,and often does".That's completely different than the stance that you originally took-i.e.it's never a foul on the shooter.

Agreed...as I said in my last post, definitely my fault for not communicating my thoughts correctly. The big difference between talking with someone and posting in a chat room, something I am not used to.

My intention was to say that in these "under the basket" situations, PC foul is sometimes but NOT ALWAYS the right call (such as the original situation stated which I still maintain was one where shooter should not be penalized).

My other point was that we officials constantly massage the rules, apply/do not apply them, according to the natural flow of the game, and this may be an example of that.

As Jim Rome says....[B]"I am out".[B]

Jurassic Referee Tue Jan 28, 2003 11:28am

Quote:

Originally posted by canuckrefguy
My intention was to say that in these "under the basket" situations, PC foul is sometimes but NOT ALWAYS the right call (such as the original situation stated which I still maintain was one where shooter should not be penalized).

My other point was that we officials constantly massage the rules, apply/do not apply them, according to the natural flow of the game, and this may be an example of that.
[/QUOTE]Good points!I can see a little bit better now where you are coming from.

In NFHS rules,which you don't use and aren't used to,the play where an airborne shooter knocks a defender(in a legal gaurding position) down when he returns to the floor is usually called an player contol foul.The rules state that that is the way that the play should be called.
NCAA rules give an official more latitude,and allows them to use more judgement in deciding whether to call something or not.IMO,if someone is getting run over big-time,you're usually better off calling the appropriate foul rather than no-calling it,though.

ChuckElias Tue Jan 28, 2003 11:30am

Canuckref, I was pretty much right with you until you said. . .

Quote:

Originally posted by canuckrefguy
As Jim Rome says...."I am out".
I wish Rome's show would go "out". Permanently. :(

Chuck

canuckrefguy Tue Jan 28, 2003 12:03pm

Your name wouldn't be Chris, ERRR, Jim Everett, would it?

Mark T. DeNucci, Sr. Wed Jan 29, 2003 08:42pm

Quote:

Originally posted by Mark Dexter
Quote:

Originally posted by canuckrefguy

Players cannot stand underneath the goal and not expect to have contact if A1 dunks.



Exactly - which is precisely why they stand there.

Quote:

If A1 has a clear path to the hoop, he is entitled to shoot and land however he wants.


Sure, but we can call a foul if he contacts an opponent who has legal guarding position.

Quote:

If B1 is in his way, that's his problem.


If by "his" you mean A1, then I'm in full agreement with you.

I tend to look at this like the game of chess - you can "prevent" a player from moving into a space by putting your knight in a position to capture any piece moved into that square. B1 is allowed to position himself such to force A1 to alter his (A1's) course - it's no different 10 feet out from the basket as it is under the basket. If A1 is not willing to change his direction: PC foul.

Mark,

I could not have said it better myself. Well done.

MTD, Sr.

ChuckElias Wed Jan 29, 2003 10:36pm

Quote:

Originally posted by canuckrefguy
Your name wouldn't be Chris, ERRR, Jim Everett, would it?
No, but that kind of crap is exactly what I hate about "Romey". He and his callers spend the 3 hours trying waaaaayyyyyyyyy too hard to be clever and just aren't smart or funny enough to pull it off. How many times can you say "Have a take. . . and don't suck" and have people think that's good enough to carry a show for 3 hours a day?!?! I just can't stand the stupid show.

Chuck


All times are GMT -5. The time now is 09:10am.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1