The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Basketball (https://forum.officiating.com/basketball/)
-   -   Video request Ohio State/Purdue (https://forum.officiating.com/basketball/96907-video-request-ohio-state-purdue.html)

OKREF Tue Dec 31, 2013 02:24pm

Video request Ohio State/Purdue
 
11:20 second half. Block/Charge.

No possible way this is a block.

APG Tue Dec 31, 2013 03:41pm

<iframe src='http://www.snappytv.com/snap/pur2_dc9t1v?w=640&h=390' width='640' height='390' frameborder='0' scrolling='no' webkitAllowFullScreen mozallowfullscreen allowFullScreen></iframe>

AremRed Tue Dec 31, 2013 04:13pm

Stupid new rule making refs default clear charges to a block. The upward motion in this play doesn't even occur until after contact!!

Charge or nothing.

Adam Tue Dec 31, 2013 05:12pm

If anyone has a good explanation for why this is a block, I'd love to read it. I can't see it.

Mark T. DeNucci, Sr. Tue Dec 31, 2013 05:48pm

CHARGE!!

MTD, Sr.

JetMetFan Tue Dec 31, 2013 05:56pm

The only – and I mean only – thing I can think of is the L saw P #5’s right foot move just before contact and thought P #5 hadn’t obtained LGP before O #10 began his upward shooting motion. Of course, that would mean the L was watching the ball as it came to him as opposed to watching P #5 but that’s all I’ve got.

Camron Rust Tue Dec 31, 2013 06:05pm

Not a block in any ruleset in any game.

JugglingReferee Tue Dec 31, 2013 06:53pm

I've got a block.





JK.

Adam Tue Dec 31, 2013 08:18pm

Quote:

Originally Posted by JugglingReferee (Post 916470)
I've got a block.





JK.

I'm amazed at how many on another forum (FB) are claiming this is a good call.

They aren't JK.

RSturgell Wed Jan 01, 2014 04:22am

No way is this a block.
These guys had a rough couple of minutes. Right before this OSU player (#3) stole ball then lost it around midcourt. Purdue player started after loose ball and basically was hugged by guard (#3) that had lost the ball to start. Foul called on Purdue player.

Rich Wed Jan 01, 2014 10:20am

Adam's not kidding.

On a rather large Facebook group we're both part of, there is a sizable contingent saying this is a block.

I just can't imagine how. Let's just call this the missed call it is and move on.

JRutledge Wed Jan 01, 2014 12:41pm

This is why it is called judgment. We all do not share the same level of judgment. I think this is clearly a PC foul based on any rules set. But I am not getting paid what the guy was that made this call.

Peace

OKREF Wed Jan 01, 2014 01:16pm

Quote:

Originally Posted by JRutledge (Post 916539)
This is why it is called judgment. We all do not share the same level of judgment. I think this is clearly a PC foul based on any rules set. But I am not getting paid what the guy was that made this call.

Peace

Doesn't matter what he is getting paid. On this play his judgment was horrible, and I don't see how anyone can defend him.

Rob1968 Wed Jan 01, 2014 01:16pm

During the many years I've officiated, I've had many discussions with those who read 4-7-2 b - "If contact occurs on the torso of the defensive player, the dribbler is responsible for the contact." who insert "on the front of the torso" and even more narrowly, "in the center of the front of the torso" into their play-calling on such a block/charge call.
Such narrow interpretation seems to disregard the immediately preceeding sentence stating "If a guard has obtained a legal guarding position, the player with the ball must get his/her head and shoulders past the torso of the defensive player."
This call seems to fit with that perception.
That said, I see this play as unquestionably a charge.

JRutledge Wed Jan 01, 2014 01:19pm

Quote:

Originally Posted by OKREF (Post 916550)
Doesn't matter what he is getting paid. On this play his judgment was horrible, and I don't see how anyone can defend him.

It was just a statement that he is working there and many of us are not, including me. And no I was not defending him. I can't on this play and other plays.

Peace


All times are GMT -5. The time now is 04:14pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1