The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Basketball (https://forum.officiating.com/basketball/)
-   -   Jet Man: Video Request for Dayton-Ohio State (Video) (https://forum.officiating.com/basketball/97551-jet-man-video-request-dayton-ohio-state-video.html)

Mark T. DeNucci, Sr. Thu Mar 20, 2014 03:03pm

Quote:

Originally Posted by AremRed (Post 927903)
No, it's not. JRut was asking about the original play you asked about which happened in the first half. The FF1 play was at the end of the game.


Oops! :eek:

MTD, Sr.

APG Fri Mar 21, 2014 02:11am

<iframe width="640" height="360" src="//www.youtube-nocookie.com/embed/k12aV8qZ-Uw" frameborder="0" allowfullscreen></iframe>

Raymond Fri Mar 21, 2014 07:28am

I can live with the no-call.

VaTerp Fri Mar 21, 2014 08:14am

I can live with the no-call as well.

What I'd like to see is the OOB call at the end of the possession. Tough one but looks like we should have been staying on this end of the floor.

TriggerMN Fri Mar 21, 2014 08:39am

Did the red player gain an advantage by contacting the white player? The white player was passing the ball and completed his pass easily. Absolutely fine with a no call here.

Rob1968 Fri Mar 21, 2014 09:42am

Red certainly gained no advantage by knocking W32 down and away from the lane/basket. However, if the play was intended to be a give-and-go, W32 was severely disadvantaged, and the intended offensive play was nullified.
If we're concerned with illegal advantage/disadvantage, although one might rule that Red gained no advantage, would one not consider that White was caused a disadvantage?
For those who say the no-call was okay, is there a level at which one would call such contact - HS/JV, HS/Varsity, etc.?

Mark T. DeNucci, Sr. Fri Mar 21, 2014 09:43am

Quote:

Originally Posted by TriggerMN (Post 928024)
Did the red player gain an advantage by contacting the white player? The white player was passing the ball and completed his pass easily. Absolutely fine with a no call here.



And if White's play called for W-2 to make a quick return pass to W-1, would be very difficult with W-1 sitting on his tuchus.

R-1 was attempting to defend against W-1 and got there late and made contact with A-1 to knock him to the floor.

Let us say that Red is losing with less than thirty seconds in the game and needs to foul. I would be dollars to donuts that this would be a foul. This contact is a foul in the first 15:06 of the game as well as the last thirty seconds of the game.

MTD, Sr.

JRutledge Fri Mar 21, 2014 09:46am

I could live with it either way. Looked more like an off balance player.

Peace

Blindolbat Fri Mar 21, 2014 12:31pm

There is too much contact to ignore there. A foul in my opinion.

Sharpshooternes Sat Mar 22, 2014 03:37am

He should have taken the shot.

ronny mulkey Sat Mar 22, 2014 09:59am

Inconsistent?
 
If just brushing a dribbler or cutter going to the basket puts the offensive player at a disadvantage (nullifying a possible easy basket) then this play definitely is not a play on. These mandates are making the games look very inconsistent. I'd like to see more scoring just like everybody else but I don't want it to be from the f. throw line.

The games have no flow.

JugglingReferee Sat Mar 22, 2014 04:15pm

I too agree that this is quite a bit of contact to permit. Though I also see at the higher levels this is a non-call. I think it should be called though; not calling it may make it difficult to adjudicate similar plays consistently.

Mark T. DeNucci, Sr. Sat Mar 22, 2014 07:27pm

Quote:

Originally Posted by JugglingReferee (Post 928250)
I too agree that this is quite a bit of contact to permit. Though I also see at the higher levels this is a non-call. I think it should be called though; not calling it may make it difficult to adjudicate similar plays consistently.


One cannot let this contact at any level because if it is not called then rougher play or retaliation is not far away.

MTD, Sr.


All times are GMT -5. The time now is 06:54am.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1