![]() |
Belmont-UNC: Block/Push/No-call (video)
Thoughts?
I've often wondered - revised guidelines or not - how these end up being no-calls but that's just me. <iframe width="853" height="480" src="//www.youtube.com/embed/pC_fQfmoqL0?rel=0" frameborder="0" allowfullscreen></iframe> |
Ship it.
|
Quote:
EDIT....and I see that Belmont was able to still pull out the win without getting that deserved call so late in the game....justice prevails. Interesting stat from the game...Belmont was whistleed for substantially more fouls than UNC and UNC shot over twice as many FTs yet Belmont made nearly the same number of FTs as UNC missed more FTs than Belmont attempted....91% vs 46%...ouch. |
I'm not that experienced with 3-man; Since all the players were in the backcourt due to the press, where should the Lead be in this situation? I'm assuming that they wouldn't be all the way down on the other end of the court if no players are there yet.
Since the contact was between the players closest to the Lead (wherever the lead was), would this be the Lead's call? Or is the Lead supposed to stay out of anything in the back court -- meaning that this is the C's primary? |
Quote:
C or L can get this (C is probably looking at the players along the FT line) |
Quote:
|
Should be C's call, but he appears to be looking at all of the guys in the middle of the lane. I would think he would have seen this anyway, but one never knows.
|
I don't blame the officials at all for eating their whistles on the play.
The Belmont player never got legal guarding position, while the player for UNC didn't extend his arms or commit any act like he was pushing. I know the contact was a bit much, but contact alone does not mean there was a foul. If it wasn't for the fact that the defender was a little off balance I bet he doesn't fall, and nobody questions the no-call. But people see a player fall and think there must be a foul somewhere. Most of the time when there is a "crash" like this, there is a penalty somewhere. But this looks like one of those cases where there isn't. |
Quote:
Peace |
Quote:
|
Even if LGP is required, he certainly does have it.
Two feet down, facing his opponent. Moving backwards and laterally the whole time, thus never losing LGP. |
Quote:
|
Quote:
|
Quote:
Like I originally said, the offensive player doesn't lower his shoulder, extend his arms, or lean forward into the defender. So I'm not sure who to blame for the contact, thus making me okay with the non-call. |
Watching this in real time I can see this call going either way. When the play is slowed down: Seems as if the defensive player was anticipating the contact and started to fall prior to.
|
Quote:
As for him moving backwards, he's not required to maintain any speed. He can stop at any moment and if he gets knocked down, it's on the opponent. |
Quote:
|
Quote:
|
Quote:
Peace |
Quote:
|
Quote:
|
Quote:
And as far as the screening comments made earlier, Camron is correct. This is not a screening situation, it is a guarding situation. Offensive players do not get to run over legal defenders. |
Quote:
Quote:
By the way how does one move “backwards and laterally correctly?” The defender had established LGP and never moved forward into the offensive player. Given those two elements what did he do wrong that could have caused him to possibly be blamed for the contact? There’s no requirement for a push/TC foul that a player lower his shoulder, etc. and there’s also no requirement that the defender stand like a statue and get RTFO. You may opt not to blow in the situation – and I would disagree – but if there’s a call in this case it really has to go against the offense. |
My understanding of the rule is that the defender must move in the same direction and at the same speed as the offensive player. The defensive player clearly moves sideways and at a slower pace than the offensive player.
To say it another way, should the offensive player move laterally slower? Is the fact that he's moving quicker than the defender his fault? Both the offensive and defensive player have the right to move to that spot on the floor. And you can't tell me the defender wasn't moving sideways on that play. In fact, he almost seems to "belly up" the offensive player, thus creating the initial contact. If the offensive player was running straight at the defender, that's another story, but in this case there was lateral movement. |
Quote:
Second, you won't find a requirement in the NCAAM/W rule books that a defender has to move in the same direction and at the same speed as the offensive player. Defenders can move any direction other than into the offensive player, i.e., they can't create contact. If the speed/direction requirement you describe existed, defenders would never be able to draw PC fouls. Is the fact A1 is moving faster than B1 A1's fault? No. As a matter of fact it should be expected because A1 knows where he wants to go. However, if B1 gets to that spot first it's his, no matter how fast B1 moved to get there. You said it yourself: Both the offensive and defensive player have the right to move to that spot on the floor. Whoever gets there first - while following the rules - wins. B1 was retreating and got there first. |
Quote:
|
Quote:
The offensive player is trying to run to his left (the guards right). Not by much, but the offensive player is not running directly into the guard. The guard is moving a bit laterally, and while doing so he's not giving the offensive player the time and/or distance to adjust his path in order to avoid contact. The question is whether the offensive player is moving directly into the defender, rather than trying to go around. Personally, I see slight lateral movement. Of course, the angle of the camera to the play is not that good, so it's nearly impossible to see it clearly. Which is why, as I originally stated, that I'm fine with pretty much any call (PC foul, blocking foul, or no call at all). |
Quote:
|
Quote:
|
Quote:
If the guard did not move, and the offensive player ran into him, then a PC foul would be justified thanks to Art.5.a. However, there was movement, so we move to Art.5.b, in which case a foul against the defender would be justified. |
Quote:
Time and distance is required to obtain an INITIAL legal position. Go to 4-23-3 and it tells you what can occur after an initial legal position is obtained. You'll find absolutely nothing that says anything about time or distance. You'll even see that it says once that initial legal guarding position is obtained, that a guard may move laterally or obliquely to maintain that position...provided it is not toward the opponent when contact occurs. Time and distance is only relevant in first obtaining that initial guarding position on a moving opponent. |
Quote:
Take a look at NCAAM/W 4-17-6. It's virtually the same as NFHS 4-23-3 Art. 6. To maintain a legal guarding position after the initial position has been attained, the guard: a. Is not required to continue having the torso face the opponent; b. Cannot have either foot out of bounds; c. May raise the hands or may jump within her own vertical plane; d. May shift to maintain guarding position in the path of the dribbler, provided that the guard does not charge into the dribbler or otherwise cause contact; e. May move laterally or obliquely to maintain position provided such a move is not toward the opponent when contact occurs; f. Is not required to have the feet on the playing court when shifting in the path of the dribbler or when moving laterally or obliquely; and g. May turn or duck to absorb shock when contact by the dribbler is imminent. In such a case, the dribbler shall not be absolved from the responsibility of contact. |
Quote:
Quote:
OBTAINING requires time/distance. MAINTAINING does not. If it did, the defense might as well just step out of the way and let the offense get to the basket because that would make it impossible to play defense without committing a foul on every play. |
All times are GMT -5. The time now is 06:57pm. |