The Official Forum  

Go Back   The Official Forum > Basketball

Reply
 
LinkBack Thread Tools Rate Thread Display Modes
  #16 (permalink)  
Old Wed Feb 04, 2009, 08:46am
Official Forum Member
 
Join Date: Aug 1999
Posts: 18,186
Quote:
Originally Posted by Snaqwells View Post
LDUB is right. If you do issue the DOG, you have no rules backing later when you go straight to the T for what should have been a DOG warning.
I agree that there's no formal / rules book DOG warning here. But, there are certainly occasions where players coaches are told the behavior that's expected rather than being issued an immediate T. Sometimes, those "warnings" are in situations where the T would be for situations which delay the game.
Reply With Quote
  #17 (permalink)  
Old Wed Feb 04, 2009, 08:58am
Administrator
 
Join Date: Sep 1999
Location: Toledo, Ohio, U.S.A.
Posts: 8,140
Quote:
Originally Posted by WreckRef View Post
A is down by 3 with 15 seconds left, gets down the court and with B2 standing perfectly straight up, A1 decides to jump into him while attempting a 3 pointer. Team A, their coach and fans are screaming for a foul as B3 grabs the air ball and dribbles out the clock.

WreckRef:

A number of esteemed posters have said that this is a good no call. I disagree for the following reasons.

1) There is no such thing as a no call. Either an infraction of the rules has occured or an infraction of the rules has NOT occured. But this reason is about semantics and is left to be discussed in another thread.

2) If you would have called this a charging foul in the first fifteen (15) seconds of the game it, then it should have been a charging foul in the last fifteen seconds of the game. You were lucky that A1's field goal attempt was an air ball.

Let me give you a very true life example:
1993 YBOA Boys' National Championship Tournament, Fifth Place game between a team from Florida (Team H) and a team from Tennessee (Team V). Five seconds left in the fourth quarter when Team V makes two free throws to take a three point lead. Team V presses Team H. H1's inbounds pass is caught by H2 at the division line and H2 starts to drive toward his basket, jumps into the air, releases the ball for a three-point field goal attempt, which touches nothing but net (which sends Team H's fans into joyous bedlam) and then, before returning to the court, crashes into V2 who had established a legal guarding position before H2 had become and airborne shooter. I still have a headache from slapping the back of my head with the charging call.

MTD. Sr.
__________________
Mark T. DeNucci, Sr.
Trumbull Co. (Warren, Ohio) Bkb. Off. Assn.
Wood Co. (Bowling Green, Ohio) Bkb. Off. Assn.
Ohio Assn. of Basketball Officials
International Assn. of Approved Bkb. Officials
Ohio High School Athletic Association
Toledo, Ohio
Reply With Quote
  #18 (permalink)  
Old Wed Feb 04, 2009, 08:01pm
Official Forum Member
 
Join Date: Nov 2002
Posts: 15,015
The first situation is either a technical foul or a verbal admonition to the player if the the referee is kind. By rule a technical foul is warranted.
You cannot assess a team delay of game warning for this as it is not one of the four items listed in that rule.

Incorrectly issuing that team DOG warning earlier in the game caused problems later when you had to charge a team T for the breaking of the throw-in boundary plane. That should have been only the first DOG warning. See how important it is to handle the first situation properly?

Your decision on the final play seems fine. By your description this is either a PC foul or nothing. Don't penalize the defender for just standing there. He hasn't done anything wrong.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 05:47pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1