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 Wed Sep 21, 2011, 07:04pm
Official Forum Member
 
Join Date: Oct 2005
Posts: 278
Quote:
Originally Posted by billyu2 View Post
From the NFHS Pre-Season Guide the following play is similar to the OP:
Even though team control exists on the throw-in, no player or team control has been established on the court for purposes of a three-second violation.
Thanks for the reference. Looks like the best that we got. I'm sure hoping this makes it to the case book or an interpretation release.
__________________
Developer of phillyref.com -- local, national, global officiating information
Reply With Quote
  #2 (permalink)  
Old Wed Sep 21, 2011, 08:10pm
Adam's Avatar
Keeper of the HAMMER
 
Join Date: Jan 2003
Location: MST
Posts: 27,190
Quote:
Originally Posted by wanja View Post
Unless there is something to contradict rule 4-12, there is player control during a throw-in:

old 4-12: A player is in control of the ball when he/she is holding or dribbling a live ball inbounds.

new 4-12: A player is in control of the ball when he/she is holding or dribbling a live ball.

Again, unless there is a rule reference, case reference or interpretation stating otherwise, this would mean that, by rule, 3 seconds is in effect during a throw-in.Clarification and consistency is definitely needed, since some potential repeated violations would be obvious.
No, the rule still does not affect the time during the throw-in. 9-7-1 requires team control in the front court. OOB is neither FC nor BC in NFHS rules, so 3 sec would not apply during the throw-in.

The only affect the rule change would have would be during the time after the throw-in pass bounces in the FC (TC and FC status are now in place) and before a player gains control inbounds (at which point the applicable rules are the same as last year). At most, we're talking about 2 seconds or so, so it's not really that big of an effect.

And of course, now we have the direction from the committee stating their intent so we can enforce the rule as intended rather than as written.
__________________
Sprinkles are for winners.
Reply With Quote
  #3 (permalink)  
Old Wed Sep 21, 2011, 10:48pm
Official Forum Member
 
Join Date: Dec 2010
Location: Mentor, Ohio
Posts: 544
"The only affect the rule change would have would be during the time after the throw-in pass bounces in the FC (TC and FC status are now in place) and before a player gains control inbounds (at which point the applicable rules are the same as last year). At most, we're talking about 2 seconds or so, so it's not really that big of an effect."

Snaq, I don't think that is correct because it doesn't matter how many seconds elapse when the throw-in pass bounces on the floor and before it is touched by a player since the throw-in still hasn't ended. Obviously, we can't start a 3 count before the TI ends. I think what the caseplay above is saying is, for 3 second purposes, there must be player control (therefore TC) on the floor in the FC before any 3-count begins following a throw-in.

Last edited by billyu2; Wed Sep 21, 2011 at 10:51pm.
Reply With Quote
  #4 (permalink)  
Old Thu Sep 22, 2011, 10:52am
Adam's Avatar
Keeper of the HAMMER
 
Join Date: Jan 2003
Location: MST
Posts: 27,190
Quote:
Originally Posted by billyu2 View Post
"The only affect the rule change would have would be during the time after the throw-in pass bounces in the FC (TC and FC status are now in place) and before a player gains control inbounds (at which point the applicable rules are the same as last year). At most, we're talking about 2 seconds or so, so it's not really that big of an effect."

Snaq, I don't think that is correct because it doesn't matter how many seconds elapse when the throw-in pass bounces on the floor and before it is touched by a player since the throw-in still hasn't ended. Obviously, we can't start a 3 count before the TI ends. I think what the caseplay above is saying is, for 3 second purposes, there must be player control (therefore TC) on the floor in the FC before any 3-count begins following a throw-in.
1. Based on the rule, why is it obvious?
2. When the throw-in ends isn't relevant to the rule.
3. The rule/case play does not say PC must be established in the FC. It says there must be team control and the ball needs to have FC status.
__________________
Sprinkles are for winners.

Last edited by Adam; Thu Sep 22, 2011 at 12:11pm.
Reply With Quote
  #5 (permalink)  
Old Thu Sep 22, 2011, 11:03am
Courageous When Prudent
 
Join Date: Jan 2006
Location: Hampton Roads, VA
Posts: 14,950
Quote:
Originally Posted by Snaqwells View Post
...The only affect the rule change would have would be during the time after the throw-in pass bounces in the FC (TC and FC status are now in place) and before a player gains control inbounds (at which point the applicable rules are the same as last year). At most, we're talking about 2 seconds or so, so it's not really that big of an effect.

...
By that logic then you would have a 10-second b/c count start when a throw-in lands in the back court. (not arguing, just saying)
__________________
A-hole formerly known as BNR
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


Similar Threads
Thread Thread Starter Forum Replies Last Post
A question on a play and a mechanics question. aevans410 Baseball 11 Mon May 12, 2008 09:23am
two questions - start of half question and free throw question hoopguy Basketball 6 Wed Mar 28, 2007 11:12pm
Rule Question and Mechanics Question Stair-Climber Softball 15 Fri May 06, 2005 06:44am
Over the back Question? Sorry mistyped my first question CoaachJF Basketball 15 Thu Feb 27, 2003 03:18pm


All times are GMT -5. The time now is 04:31am.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1