View Single Post
  #13 (permalink)  
Old Sun Jan 24, 2010, 08:43am
mbyron mbyron is offline
Official Forum Member
 
Join Date: Jul 2004
Location: NE Ohio
Posts: 7,620
Quote:
Originally Posted by Snaqwells View Post
Let me just say this, in some places, a block on this place is an acceptable way to put a stop to it. Personally, if I were to do it that way, I'd accompany it with a warning to the player letting him know why I called it. Next one is a T.
Working in one of the areas where officials call a block on a flop, I agree with your claim.

That said, I don't like the call. For one thing, with no contact it's just not a personal foul, and block is the wrong call. For another, you might end up punishing the offense if they might have had a shot and the foul interrupts the game.

I use a version of "wave, warn, whack." The first instance, when I see the player on the floor I'll wave "upward" in a "get up!" signal. The purpose is to signal that I saw the whole play and the flopper ain't gonna get that call. Next time, I verbally warn the player and coach. Then whack.

I've found that just signaling that I saw what happened and passed on the "contact" usually sends a message and it doesn't happen again. This serves the same purpose as a warning (ending the behavior) without slowing the game.

If a verbal warning is necessary, I find that including the coach lays the groundwork if I have to give a T.

Some of you might find that this method has one layer of warning too many (or wouldn't bother with the coach). I understand -- the method certainly isn't in the manual -- but my rationale for it is that nobody calls that T around here, and nobody expects it. So if I'm going to call it, everybody in the gym needs to know that it's coming. YMMV.
__________________
Cheers,
mb
Reply With Quote