The Official Forum  

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

Reply
 
LinkBack Thread Tools Rate Thread Display Modes
  #1 (permalink)  
Old Fri Mar 11, 2016, 12:44pm
Official Forum Member
 
Join Date: Nov 2002
Location: The Land Of The Free and The Home Of The Brave (MD/DE)
Posts: 6,425
OBS case(s)

R1 on 1st, fly ball to OF, caught. R1 was running, then was obstructed while returning on the catch. Throw from OF gets through IF, not dead, and R1 tries again to advance. Is R1 protected from out between 1st and 2nd if:

a) R1 did not reach 1st on the original return, or

b) R1 did reach 1st on the original return

ASA ?
NFHS ?
any ?
__________________
Officiating takes more than OJT.
It's not our jobs to invent rulings to fit our personal idea of what should and should not be.
Reply With Quote
  #2 (permalink)  
Old Fri Mar 11, 2016, 01:24pm
Official Forum Member
 
Join Date: Apr 2008
Posts: 648
Since you mentioned "any", I'm going ASA and NCAA.

My take is, it's irrelevant that the ball got through. If she's obstructed while returning to tag a base left too early, the "automatic" protection between the bases is rescinded.
If she'd have been out had there been no OBS, she's out.
If the OBS caused the out, it caused the out. Award the runner. (not "caused", but you know what I mean)

Semi -hijack:
What's the mechanic?
Runner leaves early, obstructed returning. DDB signal, even if she's not (necessarily) protected back to the base?

Last edited by jmkupka; Fri Mar 11, 2016 at 01:31pm.
Reply With Quote
  #3 (permalink)  
Old Fri Mar 11, 2016, 01:37pm
Official Forum Member
 
Join Date: Apr 2008
Posts: 648
Or do you consider F2's backing up the play, then throwing to 1B or 2B, a secondary play that eliminates the OBS call altogether?
Reply With Quote
  #4 (permalink)  
Old Fri Mar 11, 2016, 02:11pm
Official Forum Member
 
Join Date: Sep 2013
Location: Northeast Nebraska
Posts: 776
ASA covers this well in RS #36. The obstructed runner would be called out on the completed live-ball appeal for leaving the base before the fly ball was touched, if in the umpire's judgment the runner would not have been safe absent the obstruction.

If the runner reaches the base they would have been awarded (returned to 1B in this case), the obstruction is cancelled and the runner may be put out anywhere on the base paths if they advance.

The mechanic IMHO would be to signal the DDB per ASA 8-5-B, then make the call based on what happens after the OBS. But if a snowball fight breaks out, don't run around out there with your left arm out. Signal and vocalize, hold, and move on.

In NCAA, my understanding is that the runner who needs to tag up is not protected between the two bases by rule if advancing, per 9.4.3.5 and its Approved Ruling. However, 9.4.3.2 indicates that a runner obstructed while returning can be protected if the "obstruction causes the out"/would have reached safely absent the OBS. There was another thread on the board earlier this year on that topic.

In NFHS, the rule matches my NCAA interp, i.e, runner not protected when advancing; is protected if she is returning, per 8.4.3b.a(2). <--- Not a typo, that's actually how the sections are labeled, at least in my 2015 book.
__________________
Powder blue since 1998. Longtime forum lurker.
Umpiring Goals: Call the knee strike accurately (getting the low pitch since 2017)/NCAA D1 postseason/ISF-WBSC Certification/Nat'l Indicator Fraternity(completed)
"I'm gonna call it ASA for the foreseeable future. You all know what I mean."

Last edited by teebob21; Fri Mar 11, 2016 at 02:15pm.
Reply With Quote
  #5 (permalink)  
Old Fri Mar 11, 2016, 02:44pm
Official Forum Member
 
Join Date: Mar 2008
Posts: 1,210
Quote:
Originally Posted by teebob21 View Post
If the runner reaches the base they would have been awarded (returned to 1B in this case), the obstruction is cancelled and the runner may be put out anywhere on the base paths if they advance.
To lose protection of being called out between the bases, a runner has to reach the base they would have reached AND there then has to be a play on a different runner.

A runner who is obstructed with no chance of getting back to first is still out for leaving early. But if she makes it back to first and then steps off again and there has been no subsequent play, she cannot be tagged out.

Am I missing something here?
Reply With Quote
  #6 (permalink)  
Old Fri Mar 11, 2016, 03:33pm
Official Forum Member
 
Join Date: Sep 2000
Location: USA
Posts: 14,565
Quote:
Originally Posted by CecilOne View Post
R1 on 1st, fly ball to OF, caught. R1 was running, then was obstructed while returning on the catch. Throw from OF gets through IF, not dead, and R1 tries again to advance. Is R1 protected from out between 1st and 2nd if:

a) R1 did not reach 1st on the original return, or
Yes with the exception of an appeal for the base left too soon
Quote:

b) R1 did reach 1st on the original return
Yes
__________________
The bat issue in softball is as much about liability, insurance and litigation as it is about competition, inflated egos and softball.
Reply With Quote
  #7 (permalink)  
Old Thu Apr 14, 2016, 09:58am
Official Forum Member
 
Join Date: Nov 2002
Location: The Land Of The Free and The Home Of The Brave (MD/DE)
Posts: 6,425
OK, another case:
Runners on 1st and 2nd, base hit to LF.
R1 going to 3rd, making wide turn but collides with F5 barely before reaching 3rd. OBS called.
R1 continues toward home, LF throws to catcher, R1 tagged out 15 – 20 feet before home.

Is there any reason, with regard to the OBS, to nullify the out?
For example, R1’s path looked like an attempt to score and the OBS impeded.
__________________
Officiating takes more than OJT.
It's not our jobs to invent rulings to fit our personal idea of what should and should not be.
Reply With Quote
  #8 (permalink)  
Old Thu Apr 14, 2016, 10:23am
Official Forum Member
 
Join Date: Feb 2005
Location: Metro Atlanta
Posts: 870
Quote:
Originally Posted by CecilOne View Post
OK, another case:
Runners on 1st and 2nd, base hit to LF.
R1 going to 3rd, making wide turn but collides with F5 barely before reaching 3rd. OBS called.
R1 continues toward home, LF throws to catcher, R1 tagged out 15 – 20 feet before home.

Is there any reason, with regard to the OBS, to nullify the out?
For example, R1’s path looked like an attempt to score and the OBS impeded.
As written, the runner was only protected between 2nd and 3rd, so out at home would be the call.

Remember, at the time of OBS you judge what base the runner would have achieved. If that judgement was that the runner would have scored without the OBS, then award home. But I do not see that in this sitch.

If you had written that OBS occurred at 3B, then there is the argument that the runner was also protected between 3B and HP, in which case the runner would be returned to 3B.
__________________
Tony
Reply With Quote
  #9 (permalink)  
Old Thu Apr 14, 2016, 04:30pm
Official Forum Member
 
Join Date: Mar 2008
Posts: 1,210
Quote:
Originally Posted by CecilOne View Post
OK, another case:
Runners on 1st and 2nd, base hit to LF.
R1 going to 3rd, making wide turn but collides with F5 barely before reaching 3rd. OBS called.
R1 continues toward home, LF throws to catcher, R1 tagged out 15 – 20 feet before home.

Is there any reason, with regard to the OBS, to nullify the out?
For example, R1’s path looked like an attempt to score and the OBS impeded.
Two possibilities. One if he would have scored absent the obstruction. HTBT, but I'm guessing you're implying no. Second, if a runner is bumped before a base and as a result falls or stumbles past the base, then HTBT, but I'm likely determining that they were obstructed both before and after the base and have them protected on both sides of the bag.
The rulebook isn't super clear on the latter but we've had discussions to this effect here before. It basically comes down to where the obstruction occurred in your judgment and in my mind I tend to judge that it occurred over the space the runner was actively hindered.
Note, you need this interpretation if you have this situation: Runner going to first with no shot at second trips over the inattentive F3 and is now lying between 1st and 2nd where she is tagged.
Reply With Quote
  #10 (permalink)  
Old Thu Apr 14, 2016, 07:00pm
Official Forum Member
 
Join Date: Aug 2004
Location: Woodstock, GA; Atlanta area
Posts: 2,822
Quote:
Originally Posted by youngump View Post
Second, if a runner is bumped before a base and as a result falls or stumbles past the base, then HTBT, but I'm likely determining that they were obstructed both before and after the base and have them protected on both sides of the bag.
The rulebook isn't super clear on the latter but we've had discussions to this effect here before. It basically comes down to where the obstruction occurred in your judgment and in my mind I tend to judge that it occurred over the space the runner was actively hindered..
I'm solidly in that camp. Obstruction, the fact that a runner is hinder or otherwise impeded, should not be considered as existing at exactly and only one spot where it began; it should be considered in its' totality, and for the entire area it results in the runner being impeded. I hardly believe that in the cited post. the runner was hindered just that instant ("barely before reaching third", and was fully recovered and no longer hindered one step later past third.

I often use driving analogies; right of way, etc. This, to me, is like the traffic on my GPS; it barely helps to tell me there is an incident 8.3 miles ahead if they don't also tell me there is already a 2.1 mile back up!! Well, more like the inverse, I suspect; you have to consider the affect and length of space necessary to regain balance and full speed as part of the initial obstruction if the goal (as stated) is to fully negate the effect of the obstruction.

On the field, I'm considering what I read here from CecilOne as obstructed both before and after; the judgement of home may not happen, but I'm not having an out on this, either. To me, any other more literal ruling simply isn't fair to the aggrieved party, and ultimately rewards the defense for obstructing.
__________________
Steve
ASA/ISF/NCAA/NFHS/PGF
Reply With Quote
  #11 (permalink)  
Old Fri Apr 15, 2016, 07:29am
Official Forum Member
 
Join Date: Sep 2000
Location: USA
Posts: 14,565
Question that, IMO, is pertinent:

When making the "wide turn", did this action cause the runner to adjust the path and step toward F5 (who may have believed s/he was clear of the runner's established path) to initiate the contact?
__________________
The bat issue in softball is as much about liability, insurance and litigation as it is about competition, inflated egos and softball.
Reply With Quote
  #12 (permalink)  
Old Fri Apr 15, 2016, 09:48am
Official Forum Member
 
Join Date: Oct 2010
Posts: 1,241
Quote:
Originally Posted by CecilOne View Post
OK, another case:
Runners on 1st and 2nd, base hit to LF.
R1 going to 3rd, making wide turn but collides with F5 barely before reaching 3rd. OBS called.
R1 continues toward home, LF throws to catcher, R1 tagged out 15 – 20 feet before home.

Is there any reason, with regard to the OBS, to nullify the out?
For example, R1’s path looked like an attempt to score and the OBS impeded.
The only question I have is how big was the collision. Was she bumped off her stride then thrown out by 15-20 feet?. I have an out as she exceeded her protection. If she was knocked to the ground I can justify the 15-20 feet was listed as a result of going to the ground and I will award home plate.
Reply With Quote
  #13 (permalink)  
Old Fri Apr 15, 2016, 09:54am
Official Forum Member
 
Join Date: Nov 2002
Location: The Land Of The Free and The Home Of The Brave (MD/DE)
Posts: 6,425
Quote:
Originally Posted by IRISHMAFIA View Post
Question that, IMO, is pertinent:

When making the "wide turn", did this action cause the runner to adjust the path and step toward F5 (who may have believed s/he was clear of the runner's established path) to initiate the contact?
Possibly. Why?
Do you say the F5 thinking changes the call & result?
__________________
Officiating takes more than OJT.
It's not our jobs to invent rulings to fit our personal idea of what should and should not be.
Reply With Quote
  #14 (permalink)  
Old Fri Apr 15, 2016, 07:49pm
Official Forum Member
 
Join Date: Sep 2000
Location: USA
Posts: 14,565
Quote:
Originally Posted by CecilOne View Post
Possibly. Why?
Do you say the F5 thinking changes the call & result?
If the runner is attempting to make contact/draw an OBS call, s/he is no longer attempting to advance to the next base hence cannot be impeded in that effort
__________________
The bat issue in softball is as much about liability, insurance and litigation as it is about competition, inflated egos and softball.
Reply With Quote
  #15 (permalink)  
Old Mon Apr 18, 2016, 12:59pm
Official Forum Member
 
Join Date: Oct 2010
Posts: 1,241
Quote:
Originally Posted by IRISHMAFIA View Post
If the runner is attempting to make contact/draw an OBS call, s/he is no longer attempting to advance to the next base hence cannot be impeded in that effort
I would agree with that. I am not going to reward an offensive player if they are the one going out of their way to make contact and draw an obstruction call. I will add this however, for me to not call the obstruction it had better be a very clear move to initiate the contact.
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
Case 3.3.6 Sit D palmettoref Basketball 48 Mon Oct 31, 2011 12:39pm
Is there a case for this sit? stosh Basketball 13 Thu Jan 06, 2011 02:38pm
The case against two man biggravy Basketball 25 Wed Jan 13, 2010 10:32am
Case 6.3.2 rwest Basketball 8 Thu Oct 28, 2004 04:04pm
case 8.3.1 A biglaz Baseball 3 Thu Mar 27, 2003 01:51pm


All times are GMT -5. The time now is 09:16pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1