![]() |
End of Wisconsin/WKU
Someone please post the video for discussion. Thanks.
|
Can you give specifics? Just the end of the game or what happened that you wanted?
Peace |
It will be pretty obvious when you get there—but 2.0 left, Wisky inbounding
|
Here is the play:
<iframe width="560" height="315" src="https://www.youtube.com/embed/tYBEl8-dv6A" frameborder="0" gesture="media" allow="encrypted-media" allowfullscreen></iframe> Peace |
Correct call; wrong signal
|
I think this should be a no call. We have a legal screen and the player does not see the screen and runs through it.
“ A player who is screened within his/her visual field is expected to avoid contact with the screener by stopping or going around the screener. In cases of screens outside the visual field, the opponent may make inadvertent contact with the screener, and such contact is to be ruled incidental contact, *provided the screener is not displaced if he/she has the ball.” |
Quote:
|
There's no really good signal here. This would be a perfect time to bird dog and point out to everyone who the foul is on. That would avoid all the confusion.
|
Quote:
|
Why is this the right call? It seems like a blind screen and the WKY player does not seem to push his way through the screen - he just sort of falls into it blindly. The screen is effective. I don't see this as a foul. This is a no call to me. Maybe college looks at this differently?
|
Quote:
|
Quote:
|
Quote:
Yes. And in NCAA. And, if the defensive player had stopped on the initial contact, this would be a no call. Be he kept going through the screen -- foul. I think the only issue is whether the screen on a moving player was set in time to give the player enough time / distance to avoid the screen -- and, if not, that would make it an illegal screen, not a "no call." |
It looks like upon initial contact, the screener fell and then the defender tripped over him and fell on top of him. I just don't see it. When I first saw it I didn't think the screener gave him enough time/distance and I thought the official was calling the illegal screen. It wasn't until I watched a second time that I realized he called the foul on the defender. I still kind of think the screen wasn't legal. It's close.
|
Nothing about this makes any sense at all. Are we sure the Wisconsin player's left foot wasn't on the line? That wouldn't constitute legal position.
I've got nothing here either. I've never understood the "if you have a player on the ground, you have to have a whistle" theory. No, if you have a player on the ground you need to determine WHY he's on the ground and then you might have a whistle from there. |
Quote:
This has to do in relation to guarding position and not screening principles I believe (I have to find my rule book to confirm). Although I don't think the player was on the line anyway. |
Quote:
I'm only interested in the "why", but a lot of guys seem to feel obligated to put a whistle on anything that results in a player(s) hitting the deck. |
Quote:
|
Quote:
|
Quote:
|
In my opinion, the call was 100% correct, the signal was just wrong. Screener gave time and distance, and was completely inbounds. Defense went right through the screener.
Rut, can you find another clip from this game? The same Wisconsin player drew a PC foul in the lane with approximately 45-50 seconds remaining in the game that was called by the C opposite. I think that play could warrant a discussion as well. |
Quote:
Peace |
At NCAA-W camps this past summer and at clinics this fall, I was told the only blind screen is the one set behind the player being screened. Side screens were to be considered in the visual field. I agree with others that said right to call a foul, wrong signal given at the spot. It is close, but from the video and watching it live, I thought the screener gave the defender time to stop and/or change direction. He didn't do that and pushed through the screen. Foul on Red.
|
I don't have my rule book handy but there is a line in screens that says if the screener is in legal position to screen and the player does not see the screen and runs into the screener the contact can be severe and should be a no call.
|
Quote:
<iframe width="560" height="315" src="https://www.youtube.com/embed/dVwqhag4MKE" frameborder="0" gesture="media" allow="encrypted-media" allowfullscreen></iframe> Peace |
Correct but that is where the judgment piece comes in. From the clip, the official obviously ruled the player being screened within his visual field had a chance to stop or change direction and instead pushed through the screen.
|
Quote:
It's not about whether player actually saw the screener or not. |
Quote:
|
Quote:
This one is really tight. I'm wondering if folks think that the C should be the primary calling official on this play. The contact occurred outside the lane on the side of the floor opposite the C. On one hand the play seems to be opening up to him, but is this too far to reach as the primary whistle? |
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
Then when I saw the end line view I saw the Wisconsin player crumble to the ground with virtually no contact and the WKU player trip over him. |
Quote:
2. The lead also had a whistle on this play, and should have been given first crack at this play. To be fair, in the heat of the moment, you sometimes don't hear that second whistle, though. Heck, it's not like the lead didn't have a good look at the play, either. 3. I honestly can't tell if it's a block or a charge. At first I thought the defender moved into the dribbler as the dribbler was trying to drive around him, thus a "block" call. But then I thought the defender beat the dribbler to the spot of contact, after having gained LGP, thus a "charge" call. I'm leaning "charge", but not 100%. |
Quote:
|
Quote:
The elbow push off that was called by the C likely would not have been visible to the lead. If the C lays off that, there is a non-insignificant chance the L makes the wrong call (correct from what he could have seen, however). When you have something like that, it is best to take the call rather than risk a partner, who couldn't see what you saw, has something else. |
Quote:
|
This is also not a secondary defender play. This is a primary defender moving to the lane to stop the ball handler that is coming to him. I think it is a very good call and made by the right official. And it appears that the lead had the same thing if you just read how he was coming off the lane.
Peace |
Quote:
Peace |
Quote:
|
Quote:
Imagining myself as the C in that play I figure to be looking at the matchup near the block first, as it's entirely possible for a shot to go up and those two jostling for rebounding position. At the same time keeping an eye on what the dribbler is doing. I wouldn't have been surprised at all if the dribbler decided to pass to his teammate who would be in front of me for a quick shot attempt. I don't have strong feelings against the C taking this call, but this isn't a case where absolutely nothing his happening in his area and therefore it makes more sense for him to be looking across his primary to the other side. And being clearly in the lead's area I'm giving him first crack at this call, instead of immediately making a call without any thought given to my partner (which is why I don't think he even knew the lead blew his whistle). And if the lead was straightlined then why did he blow his whistle in the first place? |
NFHS language not NCAA
Quote:
The NCAA book does not define visual field - but refers to it as blind. If the player didn't see it cause his eyes were fixed on the thrower, it was blind to him. If this screen happened on the playing court, what happened? The screener set a screen which separated his defender from his teammate. The screen was successful and the screened defender did not do anything wrong. Play on. Lastly, we usually call the foul on the defender being screened when we can determine that he peaked at the screen and decided to plow through it anyway. I don't see that as the case in this play. Anytime a coach sets up a play to trick the officials, there should be skepticism |
Quote:
Quote:
Quote:
Quote:
Peace |
Quote:
|
Quote:
This wasn't that, though. |
Quote:
|
Quote:
Center is calling what he sees, which is A1's push off. The Lead had no reason to come with his late whistle, he was straight-lined. |
Quote:
|
Quote:
|
Quote:
If the Trail doesn't back out, and then steps down on the drive to see in between A1 and B1, he would have been in position to see the whole play, to include the initial contact. |
The first time that I saw this play was in an NCAA tournament game by Princeton. I believe it was during the 90s. It has been around at least 30 years.
|
Quote:
|
I guess I am looking for reasons why the C shouldn't have this call, instead of reasons he should.
|
Quote:
|
Quote:
|
Quote:
A to B movement is displacement. |
Quote:
A screen set to the side of the screened player is to considered in the visual field of the screened player has been part of the screening rule is over 55 years old. MTD, Sr. |
Quote:
Blind is about what could/should be seeable, not what the defender actually sees. Blind screens are screens set directly behind the opponent where even looking both left and right it wouldn't be seen. |
The defender is moving and doesn't even get one full step from when the screen is set to contact. It is hard for me to see that as enough time and distance to avoid.
|
Quote:
this would mean that an offensive player would have to keep running to "avoid" any collision with the defense and puts ALL the onus on the offensive player. |
Quote:
|
Quote:
|
WKU head coach says he received a call from the Big Ten saying the call was incorrect and that the official was fined and suspended. Is it normal for the conference to call a non-conference school?
|
Quote:
Sent from my SM-N920P using Tapatalk |
Quote:
|
All times are GMT -5. The time now is 10:29am. |