The Official Forum  

Go Back   The Official Forum > Basketball

Reply
 
LinkBack Thread Tools Rate Thread Display Modes
  #1 (permalink)  
Old Wed Dec 24, 2008, 02:24pm
Official Forum Member
 
Join Date: Mar 2002
Location: Carrollton, TX
Posts: 135
Send a message via AIM to rpirtle Send a message via Yahoo to rpirtle
Is NFHS Case Book Play 2.10.1 Sit. G(d) (re: corr. error situation) really an error?

Below is an excerpt from a memo posted on the Texas Association of Sports Officials (TASO) - Basketball division's website:
NFHS CASE BOOK UPDATE
Page 11. Play 2.10.1 Situation G(d) is incorrect. By rule, there is no player control during a throw-in, and the alternating possession provisions of rule 4 Sec. 36 art. 2(c) would apply.
Here's the Case Book situation in question:
A1 is fouled prior to the bonus, but erroneously A1 is awarded a one-and-one. The error is discovered: d.) after B1 has the ball for a throw-in after both attempts are successful. Ruling: d.) The successful free-throws are canceled and play continues with a throw-in by Team B as Team B had the ball when the game was interrupted for correction.

I've tried to confirm if any other resource had identified an error in the Fed's publications but I have not been successful. That's why I'm coming to the "brain trust" for your help. Is this case book scenario really an error...or does the TASO website have it wrong. Thanks for your help.
__________________
I'm getting what I want...by helping others get what they want.
Reply With Quote
  #2 (permalink)  
Old Wed Dec 24, 2008, 02:41pm
Official Forum Member
 
Join Date: Nov 2002
Posts: 14,256
No. That play ruling is correct.

Most of us here believe that the new 2.10.1 Situation D is the one that is incorrect.

That is why they conflict.
Reply With Quote
  #3 (permalink)  
Old Wed Dec 24, 2008, 02:57pm
Official Forum Member
 
Join Date: Mar 2002
Location: Carrollton, TX
Posts: 135
Send a message via AIM to rpirtle Send a message via Yahoo to rpirtle
Quote:
Originally Posted by Nevadaref View Post
No. That play ruling is correct.

Most of us here believe that the new 2.10.1 Situation D is the one that is incorrect.

That is why they conflict.
That's the situation (D) TASO says is incorrect. Since I posted this I did find some other threads on "correctable errors" and I now know a little more about how people feel on this subject. Would it be correct to say that the main disagreement is not really about the correctness of the Case Book Ruling (Team A points canceled and Team B's ball) but rather the fairness of the Ruling...???
__________________
I'm getting what I want...by helping others get what they want.
Reply With Quote
  #4 (permalink)  
Old Wed Dec 24, 2008, 03:25pm
Official Forum Member
 
Join Date: Mar 2002
Location: Carrollton, TX
Posts: 135
Send a message via AIM to rpirtle Send a message via Yahoo to rpirtle
Quote:
Originally Posted by rpirtle View Post
That's the situation (D) TASO says is incorrect....
Never mind...I see my error. It is not "Situation D" that TASO questions...but "Situation G". I see what you mean by conflicting...sorry for the confusion.
__________________
I'm getting what I want...by helping others get what they want.
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


Similar Threads
Thread Thread Starter Forum Replies Last Post
NEW Case Book play 2.10.1 Situation A Nevadaref Basketball 14 Tue Sep 30, 2008 07:53am
NFHS Case Play 10.4.5 Situation E page 84 Robert E. Harrison Basketball 15 Thu Oct 18, 2007 11:21pm
Case Book Error? regas14 Football 5 Wed Jul 06, 2005 01:50pm
NFHS 2002 Case book play 1.5.6 Mike Simonds Football 11 Mon Mar 03, 2003 12:45pm
book error devdog69 Basketball 11 Tue Feb 04, 2003 04:01am


All times are GMT -5. The time now is 07:02pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1