The Official Forum  

Go Back   The Official Forum > Basketball
Register FAQ Community Calendar Today's Posts Search

Reply
 
LinkBack Thread Tools Rate Thread Display Modes
  #1 (permalink)  
Old Mon Dec 20, 1999, 07:59pm
Official Forum Member
 
Join Date: Dec 1999
Posts: 11
Send a message via ICQ to Thom
Post

Had a player step out of bounds on the baseline to avoid a lane violation (3 seconds). Official hit her with a "T". Is this correct?
Reply With Quote
  #2 (permalink)  
Old Mon Dec 20, 1999, 10:34pm
Official Forum Member
 
Join Date: Oct 1999
Posts: 89
Thumbs up

By rule and in theory it is correct. I would have called the 3 seconds and have the team lose the ball. Dont call anything "goofy" unless you are really forced to.
Reply With Quote
  #3 (permalink)  
Old Tue Dec 21, 1999, 01:38am
Official Forum Member
 
Join Date: Nov 1999
Posts: 120
Post

Sorry Richard but I disagree since it was the players intention to avoid a 3-second violation. Therefore I would assess the technical foul.

And that is what makes us all good officials. We listen to others and use what we feel is correct for the situation as it is played out.
Reply With Quote
  #4 (permalink)  
Old Tue Dec 21, 1999, 02:33am
Official Forum Member
 
Join Date: Sep 1999
Posts: 164
Question


Sorry Richard but I disagree since it was the players intention to avoid a 3-second violation. Therefore I would assess the technical foul.


Would someone please post an NF rule on this? Thank you!
Reply With Quote
  #5 (permalink)  
Old Tue Dec 21, 1999, 07:48pm
Official Forum Member
 
Join Date: Oct 1999
Posts: 89
Lightbulb

quote:
[b]Originally posted by b_silliman on And that is what makes us all good officials. We listen to others and use what we feel is correct for the situation as it is played out.

B_Sillman:
What happened to Advantage/Disadvantage?
By calling the 3 seconds,team A loses the ball and the right team gets the ball. By calling a technical, there is nothing gained, except the problems that it causes when trying to explain it to the coach that his or her player got the T (probably does not know the rule anyway).
Like I said previously, in theory you can call it, in practice what is better game management? .
Like you said, it is a great game and we all learn from each other.
Have a great season
Reply With Quote
  #6 (permalink)  
Old Tue Dec 21, 1999, 09:15pm
Official Forum Member
 
Join Date: Nov 1999
Posts: 31
Unhappy

quote:
Originally posted by Paul LeBoutillier on 12-21-1999 01:33 AM Would someone please post an NF rule on this? Thank you!


Well, 10-3-4 says it is a technical for a player to "leave the court for an unauthorized reason or delay returning after legally being out-of-bounds."

While I cannot find a definition for "legal" reasons for being out of bounds, the case book is directly on point to the post that started this thread.

Case 10-3-4a describes the play almost word-for-word and the ruling is a technical.

Case 10-3-4b then describes a play where the thrower, after inbounding the ball, moves along the end line prior to coming inbounds behind a screen. The ruling is a technical foul because, "in this case it should be obvious that [the] movement out of bounds along the endline was to take advantage of the screen."

I must say, without the case book's interpretation, I wouldn't have applied this rule to either situation. In fact, without a definition for "legal" reasons for being out of bounds, I am reluctant to expand the definition beyond the two examples in the case book. Perhaps the rule book [as opposed to the case book] should be clearer on this.

Does anyone else have thoughts on this?

[This message has been edited by Todd (Mike) Mullen (edited December 21, 1999).]
Reply With Quote
Reply

Bookmarks


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 01:11pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1