![]() |
Foul on Shooter then PC
A1 drives to the hoop and is fouled in the act of shooting by B1. During the action B2 had set up before A1 was airborne in the path of the shooter and was subsequently ran into by A1.
Do we have a false double foul here and how is it administered? My thoughts are we: 1) Report both fouls on A1 and B1 2) A1 does not get to shoot because of the charge and 3) B ball out of bounds (or do we go arrow) |
not correct...report both fouls on A1 and B1. Basket does not count if it went in because of the PC. Shooter gets two shots because of the foul on B1. Resume play as normal after the second free throw.
|
Quote:
|
I do not want to know the enforcement and here is why.
I understand that there is a rule on how to enforce this. But please do not call this. All you are going to do is cause a problem for yourself. Even if you get this right, no one will understand it and you will spend more time explaining it than enforcing it. If the shooter is fouled, consider the next contact to be a result of the contact on the shot. Or ignore the contact on the shooter if it did not affect the play and move on. I know someone will say enforce the rules the way they are written, but all you are doing is causing a problem for yourself. This to me is like calling a multiple foul. You might be completely right, but no one will understand and they will complain you got it wrong even when you got it right.
Peace |
Quote:
1. Yes. 2. A1 was fouled shooting. S/he gets 2 shots. 3. See JR's response. A's PC foul merely means that s/he cannot score a basket on the play. Unlike Rut's bad advice, call it is that is what it is! If A1 is pushed into B1, don't call the PC, but if there's a hack on the arm while A1 is going up, and A1 charges right into B1, you should call it. I've had this happen once. Totally the correct call. Don't be afraid to have the nuts to call this! |
Quote:
Peace |
Quote:
Shooter gets 2 FT's with no one lined up. If the last FT by A1 is good, team B will get an unrestricted throw-in anywhere along the endline. If the last FT by A1 is missed, team B will get a spot throw-in on the endline. Case book 4.19.9SitA. |
Quote:
|
Quote:
Question: A1 in the act, gets hacked and after the foul, travels, shoots, and the ball goes in. Whatcha got? Did one of those acts cause the other? Edit: Like I said, I've called it once. Was about 5 years ago. I don't recall seeing it before then, and certainly have not seen a situation to call it again - or even closely. It's rare, but A1 still can't bowl over B1. So what calls are you talking about that are tough? Is a PC a tough call for you? A shooting foul? |
Quote:
|
Quote:
If the foul did not cause the travel then I could see a non shooting foul being called. You can't have a try if you travel, correct? |
Quote:
|
Quote:
I've seen double contacts of this kind, but I've never seen them called as a "false double foul". OK, the defender had good position, but the shooting foul put the shooter out of balance. And we know that equilibrium is critical in basketball. I could think of a double call in some very rare situations but, in such cases, I would think whether to call only the charge. Let's look at another situation: A1 is a dribbler, B1 has LGP on A1; B2 pushes A1 who then "charges" B1. Are we calling a foul on A1? No, you say, because the contact between A1 and B1 is a dead ball contact. But why the rules say that the ball does not become dead after a foul on a shooter? Just to allow the shooter to finish their movement and score. Ciao |
Quote:
I had a game this year where we called a simultaneous foul and we spent more time trying to justify this call then we spent enforcing it. Both coaches wanted an explanation and if it was not for me we would have not enforced it right. I had a shooting foul with the ball going in and my partner had an off ball foul. I tried to talk him into either passing on the foul because everyone saw my shooter get creamed to the floor. Hardly anyone saw his foul. I went along with the call because we did blow our whistle at the same time and that is what the rules say. Never again. Peace |
Usually in a situation like this, it isn't a matter of one official making the call, its a matter of two officials calling the two separate fouls. I've encountered this play a couple of times, and both times, that was what happened. Ironically, I called both the "front" and "back" ends of the play the two times (i.e., first I had the shooting foul, and second, I had the PC).
We got together and decided that the rules called for the false double foul, so that's how we enforced it. Just didn't use that term. In the second play I had, it was a boys varsity game with playoff implications. I told both coaches what we had, and both said, "OK." I don't know if I would make both foul calls on my own, but I wouldn't run away from the call if its the correct call. This is different from a multiple foul. A multiple foul, in my view, is for that once or twice a career situation where that sort of penalty is appropriate -- say a blowout and the losing team is trying to goon things up. |
JRut is right on this one. In the real world you are only going to have one foul, the one on B1.
|
foul on shooter then pc
I have seen this situation many times and I do not understand why we do not change the Rules books to basically make it SIMPLE and consistant....... One veteran calls it one way and has his/her reasonings. Another says something 180 dergees different. Lets come together and united. Afterall, this is not politics. This is a call we make for adolescence. We should all agree or have a book that tells us how to agree with each other so the teenagers aren't so confused. Then we all move forward with the same message/rule.
|
Quote:
If B1 reaches in and just gets A1 on the shooting elbow on the way up and doesn't change A1's path in any way, and A1 then charges into B2 who had LGP all the way and knocks B2 into the second row, you're not going to call the charge? Juggling Referee said in his original post that you shouldn't call a PC if B1's foul changed A1's path so that he charges into B2, but then he talked about the play above....where the foul by B1 didn't affect A1's original path in any way. |
Quote:
On the floor, it's not a matter of who is right. It's a matter of who thinks they are right. If both do...... |
Quote:
I'm not saying an official mustn't call it, but just that it's important to think about calling it. Ciao |
Quote:
2) Yes. And the defender was there before the shooter left his feet and never moved. And the defender with legal guarding position then gets knocked down and put into the third row by the charge. Juggling Referee originally said that there shouldn't be a foul called on a shooter who was knocked off balance or into a defender. I agree with that fully. So did you and JRut. Juggler was talking about <b>two</b> different situations though. This situation refers to the play where the airborne shooter is definitely fouled but his path isn't changed one bet. He said that he wouldn't call a foul in the first situation, but he would in this situation. I'm just wondering if you and Jeff are still arguing about the <b>first</b> situation instead of the second. |
Quote:
It seems that we agree that, if the shooter is set off balance by the foul, then the second contact should be ignored. Now let's concentrate on the dubious case: the foul by B1 doesn't change in a sensible way A1's path and doesn't put A1 off balance. I say that we should think before calling B1's foul and the charge by A1. I would be much more inclined to call only the charge and wave off the basket. Assuming, of course that the contact between A1 and B2 is substantial (for example, but not only, when B2 is knocked down). Such a situation seems more likely when the two contacts are almost simultaneous: in case of doubt on which happens first, I'd rather go with the charge. I'm not saying we should ignore B1's contact in every situation like this, nor I'm saying to ignore contact on a shooter who is able to score anyway. I'm saying we must be careful and call the foul (and I admit that at the end, in very special situations, it can be "the fouls"). It should definitely not be "different calls by two officials", do you agree? Ciao |
Call the foul on the shooter.............ignore any foul after this unless it is intentional or flagrant.
|
Quote:
2) And neither was Juggling Referee saying to ignore the contact either. He said <i>verbatim</i>--"If A1 is pushed into B1, <b>DON'T</b> call the foul, but if there's a hack on the arm while A1 is going up and A1 charges right into B1, you should call it." Didn't you just basically kind of agree with him on both <b>different</b> situations? That was my point. You've got two completely different situations being discussed here. One situation where the defensive foul pushes or directs the shooter into another defender, and another situation where the defensive foul doesn't alter the path of the airborne shooter at all before the shooter wipes out a different defender. The defensive foul in the second situation may cause the shot to miss though, or it might even stop the shot from getting off. Juggling Referee stated that they should be called different ways. |
Quote:
Am I reading you right? You're saying that the airborne shooter can run over a defender with LGP? Knock the defender down and put them into the third row? Under all circumstances? And you'd ignore that? If so, I disagree. |
Quote:
Quote:
Again, I'm not saying to ignore a foul: just call the real foul, be it on A1 or B1. Or on both, if there is no other choice. Ciao |
No, if he or she was knocked into the third row, then that would fall under flagrant and should be called but if A1 is fouled on the way up and the other contact is strictly momentum, I would only call the shooting foul. I respect any other opion and I would also say calling a false double foul would not be wrong either.
|
Quote:
Peace |
Quote:
|
Quote:
It doesn't happen often, as you said. But I can see a very specific situation where the false double foul might be the right call. |
Quote:
Peace |
Quote:
You're stating that calling a false double foul is wrong, but calling a false double foul isn't wrong. Momentum really can't be a factor. Once he leaves his feet, the shooter's momentum isn't going to be altered that much. The <b>path</b> of his momentum might be altered though. |
Quote:
|
Quote:
Peace |
Quote:
|
All times are GMT -5. The time now is 11:54am. |