The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Softball (https://forum.officiating.com/softball/)
-   -   Show intent on going to 2nd (https://forum.officiating.com/softball/96145-show-intent-going-2nd.html)

bsnalex Sat Sep 21, 2013 02:50am

Show intent on going to 2nd
 
A few weeks ago I had this come up--

BR safe at first on the throw and then gently turns into the infield - he was probably a yard overrun from first and maybe 1 - 2 feet infield off the baseline. What I noticed when he was safe is that he did not continue his overrun nor peel off to the right. His left shoulder turned inward and to me, while he didn't show blatant intent to go on to 2nd he certainly made no point of showing me as a blue that he WASN'T going to 2nd.

At that point first baseman turned around and tagged him and I called him out on the tag at which point I got some jaw from one of my fellow umpires who was not working the game, but observing.

He told me (in front of both teams!) that I got the call wrong and that the runner should only be out if he showed intent on going to 2nd. I felt that as he turned his body inward that was intent enough for me. I pulled the player aside after the inning and told him (umps do this as it's a small league and we get alot of new players) that to avoid any doubt run straight thru the base and when you return, make sure you turn your body to the right and walk back to the base on the orange side of the base.

Can I have any thoughts on this? We use ISF book.

RKBUmp Sat Sep 21, 2013 06:23am

First off I dont think any other umpire, even if you were being observed should have said anything during the game let alone in front of other teams. It should have waited until after the game when you were alone and could have discussed it in private.

I dont have an ISF rulebook, but in any other rule set there is no requirement the batter turn to the right or straight back down the line when returning to 1st after an overrun. It is perfectly legal for a batter to turn to the left as long as they do not make an aggressive move toward 2nd.

IRISHMAFIA Sat Sep 21, 2013 08:59am

Quote:

Originally Posted by RKBUmp (Post 905641)
First off I dont think any other umpire, even if you were being observed should have said anything during the game let alone in front of other teams. It should have waited until after the game when you were alone and could have discussed it in private.

I dont have an ISF rulebook, but in any other rule set there is no requirement the batter turn to the right or straight back down the line when returning to 1st after an overrun. It is perfectly legal for a batter to turn to the left as long as they do not make an aggressive move toward 2nd.

I'll echo RKBump's comment about your alleged fellow umpire. If anyone should be dressed down, it should have been him.

Secondly, this is obviously a judgment call. However, it is the umpire's responsibility to determine the runner is making an attempt to advance to 2nd, not the runner's to prove s/he is not.

At one time the training (at least in my area) included, probably somewhat similar as you have been told, that ANYTHING, dip of the shoulder, a look back to the left, even a slight drifting of the runner's path into fair territory, WAS to be considered an attempt. I never bought into that theory of dictating what an umpire is to judge.


Over the years, I have learned to use my brain. :rolleyes: Okay, enough! ;) IOW, if the runner did something which my eyes showed my brain to tell my gut I needed to react in a manner to take the runner to 2B, there was an attempt.

This isn't supposed to be a "gotcha" play just so the umpire can ring up one of the 42.

Skahtboi Sat Sep 21, 2013 10:04am

I will echo the two previous posts on the alleged umpire who came out to talk to you in front of both teams.

I also agree with their assessment of your call.

CecilOne Sat Sep 21, 2013 01:33pm

Me too, on both counts. Even though it seems the call was incorrect, the "observer" was way more wrong.

What IM said about reading it is my guide as well.

But, I do think the advice given to the player to always turn right (as youth coaches teach) is what causes people to think that is the rule. Besides, a runner can turn right and still make an attempt toward 2nd. Not by rule, but physically.

EsqUmp Sat Sep 21, 2013 09:42pm

It's not just intent, but ATTEMPT. You have to actually ATTEMPT to advance toward 2nd base.

bsnalex Sun Sep 22, 2013 02:42am

The other ump apologised after the game and said it should have waited.

If I tell a new player to peel to the right, I always say its not the rule to go to the right, just helps remove all doubt of where you're going.

The problem I have is the judgement of an attempt. A player leisurely strolling back to first but also making his way over to the left a bit isn't deliberately making an attempt but could be testing the waters.

Irish, iff I think back to my training I was probably told in class number one that if their in the infield portion and are not returning to first immediately then they're fair game. If anything if I go by that rule internally I'll never waiver in similar calls. It has nothing to do with getting the 42 and going home. BR got to first but he just made zero effort to get back to the bag.

IRISHMAFIA Sun Sep 22, 2013 09:05am

Quote:

Originally Posted by bsnalex (Post 905687)
The other ump apologised after the game and said it should have waited.

If I tell a new player to peel to the right, I always say its not the rule to go to the right, just helps remove all doubt of where you're going.

The problem I have is the judgement of an attempt. A player leisurely strolling back to first but also making his way over to the left a bit isn't deliberately making an attempt but could be testing the waters.

Irish, iff I think back to my training I was probably told in class number one that if their in the infield portion and are not returning to first immediately then they're fair game. If anything if I go by that rule internally I'll never waiver in similar calls. It has nothing to do with getting the 42 and going home. BR got to first but he just made zero effort to get back to the bag.

Then you were given inaccurate information or misunderstood.

The bold portion makes it sound as if you may be confusing to the action to which the rule applies.

The exemption to being put out permits the BR to run through the base and not be required to maintain contact as long as that runner makes no attempt to advance to 2B and returns to the base. Nothing other than an attempt to advance to 2B removes that exemption. If this is the action to which you are referring, IMO, you are looking at it from the wrong side of the rule.

The rule clearly states that if the runner makes an attempt to advance to 2B, that runner is in jeopardy of being put out. It says nothing about losing that given exemption if s/he doesn't return as quick as the umpire desires. It says nothing about infield, outfield, grass, dirt, etc.

Now, back to the bold portion above. If you are referring to a player rounding the base toward 2B, they are "fair game" whether they are returning to 1B immediately or not, as rounding the base is a clear attempt of advancement. That BR/R never obtained an exemption from being put out since there was an immediate indication of possible advancement toward 2B.

chapmaja Mon Sep 23, 2013 07:06am

This play lead to the only ejection I have ever called in 4 or 5 years of adult league games. Ground ball to second base, the throw to first is over the head of F3, who jumps into the path of the batter-runner. The batter-runner has to lean into the field of play and barely touches first as he tries avoiding contact with F3, who has come down right on the middle of 1b. This move by the runner causes him to run into the field of play, but he makes no attempt to advance to second. The catcher had come down to back up the throw, and throws to F4 who tags the runner returning to 1b. I rule safe, no attempt to advance. The "manager" absolutely goes crazy, charges out of the dugout, dropping F-bomb after F-bomb. I didn't get the chance to eject him before he was right at me, but as soon as I could he was tossed for charging and berating an umpire. Luckily his team held him back, because on a 1 umpire system you are alone if someone goes crazy.

I agree with the previous comments, your play should not have resulted in an out, and the observer should not have did what he did either.

MD Longhorn Mon Sep 23, 2013 08:43am

Quote:

Originally Posted by bsnalex (Post 905639)
His left shoulder turned inward and to me, while he didn't show blatant intent to go on to 2nd he certainly made no point of showing me as a blue that he WASN'T going to 2nd.

At that point first baseman turned around and tagged him and I called him out on the tag

Called him out for what? Bad call.

Quote:

at which point I got some jaw from one of my fellow umpires who was not working the game, but observing. He told me (in front of both teams!) that I got the call wrong and that the runner should only be out if he showed intent on going to 2nd.
Worse. Way worse. No umpire should ever do this to another umpire. He's correct, of course, but calling you out, especially in front of teams, is worse than any bad call you could have made.

Quote:

I felt that as he turned his body inward that was intent enough for me. I pulled the player aside after the inning and told him (umps do this as it's a small league and we get alot of new players) that to avoid any doubt run straight thru the base and when you return, make sure you turn your body to the right and walk back to the base on the orange side of the base.
And worse than worse. 1) You've instilled a rule that is not correct in this kid's mind. 2) You've coached the kid - not your job, don't ever do this. If it's a learning league, and your input might help, tell the COACH, not the kid (and be 150% sure you are correct when you're doing this... you were not in this case!)

PS - for you to have an out on this play, the player must make an attempt to advance to second. Period. He doesn't have to turn right. He doesn't have to walk back to first (he can run). What you describe was not even close to enough.

bsnalex Mon Sep 23, 2013 09:59am

Thanks to all for your input...definitely will get it right next time

EsqUmp Tue Sep 24, 2013 06:40am

Quote:

Originally Posted by chapmaja (Post 905747)
This play lead to the only ejection I have ever called in 4 or 5 years of adult league games. Ground ball to second base, the throw to first is over the head of F3, who jumps into the path of the batter-runner. The batter-runner has to lean into the field of play and barely touches first as he tries avoiding contact with F3, who has come down right on the middle of 1b. This move by the runner causes him to run into the field of play, but he makes no attempt to advance to second.

Plus, in all likelihood and fairness, the obstruction that was caused probably carried through the base; so, the BR was protected between 1st and 2nd base. It's similar to a 3rd baseman tripping the runner, causing him/her to go over 3rd base and then tagging the runner saying "she went beyond the base." Here, the effect of the obstruction continued beyond the spot of the initial obstruction.

Manny A Tue Sep 24, 2013 10:31am

Quote:

Originally Posted by EsqUmp (Post 905868)
Plus, in all likelihood and fairness, the obstruction that was caused probably carried through the base; so, the BR was protected between 1st and 2nd base. It's similar to a 3rd baseman tripping the runner, causing him/her to go over 3rd base and then tagging the runner saying "she went beyond the base." Here, the effect of the obstruction continued beyond the spot of the initial obstruction.

I've never heard of that distinction. As far as I'm concerned, the obstruction happened AT first base (and it's quite possible that the BR became hindered as he approached first, given the description of the play). He was never between first and second when hindrance took place. I'm not sure we are allowed to extend the effect of the initial obstruction such that, if he were to attempt to go to second and gets tagged out by a huge margin, he would be allowed to return safely to first.

MD Longhorn Tue Sep 24, 2013 11:04am

Quote:

Originally Posted by EsqUmp (Post 905868)
Plus, in all likelihood and fairness, the obstruction that was caused probably carried through the base; so, the BR was protected between 1st and 2nd base.

No, but he didn't need it - the BR may have fallen toward 2nd, but he made no effort to go to 2nd.

Andy Tue Sep 24, 2013 12:02pm

Quote:

Originally Posted by EsqUmp (Post 905868)
Plus, in all likelihood and fairness, the obstruction that was caused probably carried through the base; so, the BR was protected between 1st and 2nd base. It's similar to a 3rd baseman tripping the runner, causing him/her to go over 3rd base and then tagging the runner saying "she went beyond the base." Here, the effect of the obstruction continued beyond the spot of the initial obstruction.

I have made a call similar to this. Jr College game using NCAA rules.

R1 running to third, F5 obstructs R1, causing R1 to attempt an awkward slide to get around the obstructing fielder. R1 doesn't really slide, but kind of rolls over and past third base into foul territory near the coaches box. F5 receives the ball and tags R1 who is off of third base. I call a dead ball and award third base to R1. Explained the call to the defensive coach who accepted the explanation.

I had the same concern that the obstruction happened between second and third and the runner was tagged out past third base. But the obstruction is what caused the awkward slide and the runner to go past third base. I talked to my JC league assigner about the call and he agreed with it.

AtlUmpSteve Tue Sep 24, 2013 02:34pm

Quote:

Originally Posted by Manny A (Post 905885)
I've never heard of that distinction. As far as I'm concerned, the obstruction happened AT first base (and it's quite possible that the BR became hindered as he approached first, given the description of the play). He was never between first and second when hindrance took place. I'm not sure we are allowed to extend the effect of the initial obstruction such that, if he were to attempt to go to second and gets tagged out by a huge margin, he would be allowed to return safely to first.

So what you are saying is that if F3 sets up just in front of the base at the last moment with BR rounding the base, and to avoid contact the BR swerves last minute, barely touches the base, and needs 5-6 steps after the base to regain solid footing, that you AREN'T protecting after first base, too? If that BR never regains balance, does a face plant 7-8 strides toward second, you have them tagged out and unprotected?

Is obstruction and the resulting hindrence so momentary in your mind that it happens at one absolute spot, that the hindrence didn't actually continue until the BR regained balance and full speed running?

For me, the obstruction started when the runner was first hindered, and continues until the runner is no longer hindered. Anything else makes no sense, and rewards the defense for intentional acts.

Manny A Tue Sep 24, 2013 04:07pm

Quote:

Originally Posted by AtlUmpSteve (Post 905924)
So what you are saying is that if F3 sets up just in front of the base at the last moment with BR rounding the base, and to avoid contact the BR swerves last minute, barely touches the base, and needs 5-6 steps after the base to regain solid footing, that you AREN'T protecting after first base, too? If that BR never regains balance, does a face plant 7-8 strides toward second, you have them tagged out and unprotected?

You award based upon what the runner would have achieved had there been no obstruction. So in your example, I would protect the runner to second base because the runner likely would have achieved second minus the obstruction.

But where the rule states that a runner may not be put out between the bases where the obstruction took place, and the obstruction took place before the runner reached a base, where does it say that the hindrance may continue until such time as the runner regains full speed running?

Take this routine play: BR has to slow down on her approach to first on a base hit in the outfield because F3 is standing short of the bag. Likely, the BR won't regain her full speed until after the base, and she tries to stretch the hit into a double when she sees F8 bobble the ball. But F8 has a gun and throws her out by some 15-20 feet. Are we really to send the BR back to first base?

Again, I simply stated that I've never heard anyone say that it's acceptable to extend a runner's protection from between two previous bases to between two subsequent bases. If that's the case, then we'll have to keep our eyes on the runner to gauge when she regains her full speed.

MD Longhorn Tue Sep 24, 2013 04:42pm

Manny, I think you're missing the boat here quite drastically.

If the fielder is near a base when she obstructs a runner, it is COMPLETELY common for that obstruction to have affected that runner both before and after the base. If you do not rule this way, you're really creating a situation where it's advantageous for a fielder to simply get in the way most of the time. If you're ruling this way, and your my umpire, I'm stationing my first baseman directly in front of the bag on all hits that are in between single/double ... pretty much ensuring they just get a single.

Or worse, my third baseman is going to stand in front of third and push the runner toward home such that they miss third base on any borderline scoring play. You'll only protect them to third unless you're sure they would score, so I'm gaining by obstructing.

Yes, we protect them (and award) those bases that we feel they would have achieved had there been no obstruction ... but the other half of that is just as important. If a fielder obstructs near first - and that obstruction affects the runner AFTER first, they are protected between first and second as well, even if the umpire doesn't think they'd have gotten to 2nd.

jmkupka Mon Sep 30, 2013 10:20am

Seem to recall a recent thread where F5 obstructs R1 as she rounds 3B so completely that she misses the bag on her way home. Running with a full head of steam, she has to lock up her brakes 1/3 of the way down the line & come back to 3B (hoping, I guess, that BU's OBS call would protect her to home).

If she chose, instead, to continue home nonstop (without coming back to touch) would the OBS call forgive the missed base?

I think she'd be liable to be called out on appeal, regardless of the OBS, but I forget how the thread played out.

jmkupka Tue Oct 01, 2013 09:01am

Damn, did I actually ask a question that was literally too dumb to answer?

RKBUmp Tue Oct 01, 2013 09:14am

Rules are pretty clear that all bases must be touched in legal order, including awarded bases. I see nothing in the rules that would indicate a missed base can be considered to have been touched if obstruction were the reason it was missed.

BretMan Tue Oct 01, 2013 09:40am

Quote:

Originally Posted by RKBUmp (Post 906539)
Rules are pretty clear that all bases must be touched in legal order, including awarded bases. I see nothing in the rules that would indicate a missed base can be considered to have been touched if obstruction were the reason it was missed.

I know that in some baseball rule sets an obstructed runner who misses a base because of the obstruction can't be called out for missing the base. I think that is also the case with NCAA softball.

As far as ASA, my only dim memory is that they covered this on their website (Plays and Clarifications), maybe last year?

**EDIT: This is probably what I was thinking of. Close, but not the same situation. But if a runner can be "excused" for passing another runner, if the pass was due to an obstruction, then why not the same exception if an obstruction causes a missed base?

PLAY: With one out, R1 on 2B and R2 on 1B, B4 hits an extra base hit to the outfield. R1 rounds 3B and is obstructed and knocked down. R2 accidently passes R1 as R1 is lying on the ground. The ball is returned to the infield and R1 is tagged out. What is the call?
RULING: When R1 was obstructed between 2B and 3B, the base umpire should signal and call “obstruction.” (Rule 8, Section 5B) The umpire should then rule R2 out when R2 passed R1 with the ball remaining live. (Rule 8, Section 7D EFFECT) When R1 is tagged out between the two bases where the obstruction occurred, the umpire should call “time” and award R1 and all other runners the base or bases they would have reached, had there been no obstruction. (Rule 8, Section 5B[ 2] & [4] EFFECT) This would nullify the out on R2 and both R1 and R2 would be awarded the bases they would have reached had there been no obstruction. In this play, that base appears to be home.

IRISHMAFIA Tue Oct 01, 2013 11:57am

Quote:

Originally Posted by BretMan (Post 906540)
I know that in some baseball rule sets an obstructed runner who misses a base because of the obstruction can't be called out for missing the base. I think that is also the case with NCAA softball.

As far as ASA, my only dim memory is that they covered this on their website (Plays and Clarifications), maybe last year?

**EDIT: This is probably what I was thinking of. Close, but not the same situation. But if a runner can be "excused" for passing another runner, if the pass was due to an obstruction, then why not the same exception if an obstruction causes a missed base?

PLAY: With one out, R1 on 2B and R2 on 1B, B4 hits an extra base hit to the outfield. R1 rounds 3B and is obstructed and knocked down. R2 accidently passes R1 as R1 is lying on the ground. The ball is returned to the infield and R1 is tagged out. What is the call?
RULING: When R1 was obstructed between 2B and 3B, the base umpire should signal and call “obstruction.” (Rule 8, Section 5B) The umpire should then rule R2 out when R2 passed R1 with the ball remaining live. (Rule 8, Section 7D EFFECT) When R1 is tagged out between the two bases where the obstruction occurred, the umpire should call “time” and award R1 and all other runners the base or bases they would have reached, had there been no obstruction. (Rule 8, Section 5B[ 2] & [4] EFFECT) This would nullify the out on R2 and both R1 and R2 would be awarded the bases they would have reached had there been no obstruction. In this play, that base appears to be home.

It's not the same, and this is a relatively recent change in interpretation for some. I'm not a fan of it simply because the OBS obviously did NOT affect the trailing runner if she continued to run. But then the umpire verbalizes "out" and now the runner is affected, but not by the OBS, but the umpire's call :eek:

MD Longhorn Tue Oct 01, 2013 12:05pm

Quote:

Originally Posted by RKBUmp (Post 906539)
Rules are pretty clear that all bases must be touched in legal order, including awarded bases. I see nothing in the rules that would indicate a missed base can be considered to have been touched if obstruction were the reason it was missed.

It's an interpretation. If you don't ignore a miss that is caused by an obstruction then you get into odd awarding of bases that were already achieved. Example:

Runner on 2nd is going to score on double to the outfield. F5 is camped on the base or otherwise physically prevents the runner from touching 3rd. Runner then scores easily anyway.

If you don't accept the interpretation that a miss caused by obstruction, then you end up with the rather absurd situation that you have to award home on the obstruction and the girl has to go touch home, then third, then home.

AtlUmpSteve Tue Oct 01, 2013 12:51pm

Quote:

Originally Posted by RKBUmp (Post 906539)
Rules are pretty clear that all bases must be touched in legal order, including awarded bases. I see nothing in the rules that would indicate a missed base can be considered to have been touched if obstruction were the reason it was missed.

What follows is obviously taking this to the nth degree, but saying it so we can work back. This incorporates two of the recent "but what rule covers this" conversations.

Assume Team A is leading by one run with bases loaded (R3 on 3rd, R4 on 2nd, R5 on 1st,and two outs in final inning; playing defense. Batter singles, so F6 literally lays on top of 2nd base, while F4 blocks R3 off of the base, and, using her best flag football blocking technique, guides her around 2nd base, past the base. As the ball comes back in, F6 takes the throw, and makes a live ball appeal that R5 missed the base, and that no run can score, because this is a force play.

So, the runner has passed the base while obstructed (and not protected from missing the base, say some), and the obstruction initially occurred prior to the base, so not protected between 2nd and 3rd, according to some. While this is obviously unsporting, the penalty (choose your ruleset, restriction/disqualified/ejection) wouldn't make the runner safe.

All of this is "covered" in the rules, so you cannot apply "not specifically covered". This isn't a "penalty", so even the (now-MIA in ASA) "will not penalize .... for any infraction ... when imposing the penalty would be an advantage to the offending team" wouldn't exactly apply.

We also have a rule that clearly states the "intent" of the obstruction rule; to negate any advantage gained by the defense in impeding the offense from free and clear opportunity to run the bases.

So, maybe I can't tell you what exact clause/phrase/interpretation I am using, but NO WAY IN HELL am I calling that runner out. I am awarding the missed 2nd base on the obstruction, I am protecting both before and after, and if some jackleg wants to protest, and anyone wants to uphold that protest, it won't be me.

CecilOne Tue Oct 01, 2013 04:39pm

Quote:

Originally Posted by AtlUmpSteve (Post 906554)
We also have a rule that clearly states the "intent" of the obstruction rule; to negate any advantage gained by the defense in impeding the offense from free and clear opportunity to run the bases.

So, maybe I can't tell you what exact clause/phrase/interpretation I am using, but NO WAY IN HELL am I calling that runner out. I am awarding the missed 2nd base on the obstruction, I am protecting both before and after, and if some jackleg wants to protest, and anyone wants to uphold that protest, it won't be me.

I would have said "negate the disadvantage to the offense", but same thing and I agree. :cool:

txtrooper Tue Oct 01, 2013 10:33pm

An obstructed runner can be called out for a laundry list of violations between the Base(s) they were obstructed, missing a base (appeal) is one of them.

EsqUmp Wed Oct 02, 2013 06:52am

Quote:

Originally Posted by txtrooper (Post 906603)
An obstructed runner can be called out for a laundry list of violations between the Base(s) they were obstructed, missing a base (appeal) is one of them.

While I was not at the table when the exception (missing a base) to an obstructed runner being protected was discussed, I think that common sense should prevail here in trying to figure out WHY they put in the exception.

I'm sure that it wasn't to call a runner out who failed to tippy toe around someone who had no legal right to be positioned where they set up. Rather, it was to prevent an egregious disregard of base running responsibilities. For example, B1 hits the ball to the outfield and is obstructed by F3 just after rounding 1st base. We would all agree that she is protected (yeah, yeah, with some exceptions) between 1st base and 2nd base. Knowing that she is protected and can't be called out, she decides to cut across the infield and go to 3rd base. Let's say she's 10 feet from 2nd base when she decides this. Well, you need the exception to the protection in this case.

Same thing goes for no tagging up. You can't have R1 on 1st base leave when the fly ball is 20 feet from F8 just so she can run into F4 who is mesmerized by the play and hope to be protected. So, there's an exception.

You can't have an obstructed runner plow over a fielder now holding the ball even though the runner had been obstructed. Why? Because this isn't football. Safety and fairness to softball prevail.

What you also see is that a rule of equity (obstruction), that is, a rule to bring things back to the way they ought to have been had something not gone wrong, should NOT protect a runner who decides to disregard normal base running responsibilities. It DOES, however, protect a runner who is offended by the defense doing what the defense is not supposed to be doing and prevents the offense from doing what it otherwise would have done.

Just because we weren't there when the rule books went to print doesn't mean we can't use common sense and logic to figure out why rules were created, especially exceptions to rules.

CecilOne Wed Oct 02, 2013 08:43am

Quote:

Originally Posted by EsqUmp (Post 906609)
While I was not at the table when the exception (missing a base) to an obstructed runner being protected was discussed, I think that common sense should prevail here in trying to figure out WHY they put in the exception.

I'm sure that it wasn't to call a runner out who failed to tippy toe around someone who had no legal right to be positioned where they set up. Rather, it was to prevent an egregious disregard of base running responsibilities. For example, B1 hits the ball to the outfield and is obstructed by F3 just after rounding 1st base. We would all agree that she is protected (yeah, yeah, with some exceptions) between 1st base and 2nd base. Knowing that she is protected and can't be called out, she decides to cut across the infield and go to 3rd base. Let's say she's 10 feet from 2nd base when she decides this. Well, you need the exception to the protection in this case.

Same thing goes for no tagging up. You can't have R1 on 1st base leave when the fly ball is 20 feet from F8 just so she can run into F4 who is mesmerized by the play and hope to be protected. So, there's an exception.

You can't have an obstructed runner plow over a fielder now holding the ball even though the runner had been obstructed. Why? Because this isn't football. Safety and fairness to softball prevail.

What you also see is that a rule of equity (obstruction), that is, a rule to bring things back to the way they ought to have been had something not gone wrong, should NOT protect a runner who decides to disregard normal base running responsibilities. It DOES, however, protect a runner who is offended by the defense doing what the defense is not supposed to be doing and prevents the offense from doing what it otherwise would have done.

Just because we weren't there when the rule books went to print doesn't mean we can't use common sense and logic to figure out why rules were created, especially exceptions to rules.

The exceptions look to me like things that would make me judge that the runner would not have been safe (reached a base) even w/o the obstruction.
e.g., a shortcut to the next base means the runner would have missed the base anyway.

MD Longhorn Wed Oct 02, 2013 09:47am

Quote:

Originally Posted by txtrooper (Post 906603)
An obstructed runner can be called out for a laundry list of violations between the Base(s) they were obstructed, missing a base (appeal) is one of them.

Yes, if they miss a base that was not caused by obstruction, call em out.

If the obstruction CAUSED the miss - you don't. Incidentally, this was discussed with a good deal of vociferousness at a clinic I remember you saying you were at (League City, 2 years ago).

jmkupka Wed Oct 02, 2013 09:52am

That puts a neat bow on it. Thanks Mike.


All times are GMT -5. The time now is 09:57am.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1