The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Softball (https://forum.officiating.com/softball/)
-   -   New partner (https://forum.officiating.com/softball/98092-new-partner.html)

CecilOne Tue Jun 24, 2014 07:41am

Quote:

Originally Posted by CecilOne (Post 936531)
Or is he trying to say the rule is maintaining control throughout the play, not just at the time of the touch/tag? :confused:

Which reminds me, saw this play recently.
R running from 1st, fly ball to RF, caught. F9 throws to 1st in time for the tag up out.
Tag made, runner's slide carries her into F3, ball comes out when they fall.
Out or safe.

RKBUmp Tue Jun 24, 2014 07:58am

Out

MD Longhorn Tue Jun 24, 2014 08:27am

Out.

Manny A Tue Jun 24, 2014 08:41am

Quote:

Originally Posted by Rita C (Post 936584)
I didn't want to assume. I knew it wasn't part of any code I do use.

Rita

Which code is that, Rita? Under most softball codes, any batter-runner hindrance with an uncaught third strike is interference, whether intentional or not.

And for what it's worth, I believe OBR 7.09(a) has new expanded language that does not include intent.

jmkupka Tue Jun 24, 2014 09:03am

MD & Rita, accepting your interps almost as often as Irish's, are you still skeptical about my int call?

Irish, am I correct in assuming you agree with my call?

HTBT sure, but assume no intent, and F2 grabbed at thin air because the ball shot off B/Rs foot...

BTW my online 2014 PONY book has it as 9.7.h (not 8.7.h)

thanks all...

MD Longhorn Tue Jun 24, 2014 09:24am

I'm not sure Irish agreed with the out or disagreed with Rita or I.

I did not say intent was required. It's not. All Irish did was clarify that.

That said, you were there, we were not - but just given your description of the play, I don't see interference.

While it doesn't require INTENT, it still requires INTERFERENCE to be ruled as such. Given the way you describe the play - the ball coming off the catcher toward the batter and then coming out --- what did the batter DO that got the INT call? I guess what I'm saying is that it requires action (or perhaps negligent inaction) on the batters part to have INT here. Just happening to be in the path of the ball that ricochets off the catcher and into his legs is not interference on his part.

If the batter (intentionally or unintentionally) kicked the ball such that the catcher no longer had a play --- then we have INT.

If the batter (intentionally or simply obliviously) remains in the catcher's way longer than necessary, and somehow causes the catcher to no longer have a play --- then again you could have INT.

You, the umpire, has to decide at what point during the action that the batter is responsible for what happened (again, intent not being a factor). Immediately after the ball comes off the catcher, whatever happens is not the batter's fault.

In other words, the way it's been explained to me by my betters is that the batter has to DO something on this play that warrants interference. (Intent being irrelevant, but ACTION being relevant).

(PS - I welcome any elaboration or even contradiction from Irish on this).

Manny A Tue Jun 24, 2014 09:26am

Quote:

Originally Posted by CecilOne (Post 936595)
Which reminds me, saw this play recently.
R running from 1st, fly ball to RF, caught. F9 throws to 1st in time for the tag up out.
Tag made, runner's slide carries her into F3, ball comes out when they fall.
Out or safe.

You didn't say, but did F3 tag the runner or the base?

The question you need to answer to yourself: Did F3 have control of the ball in her hand/glove when she made the tag? If so, then you have an out.

In your play, if F3 tagged the runner, and then the ball popped out on the fall, you could judge that F3 never had control of the ball at the time of the tag. It really depends how quickly things took place (tag, contact, fall, ball comes loose). Any discernable time between the tag and when the ball popped out of the glove, I would judge she controlled it during the tag.

jmkupka Tue Jun 24, 2014 09:40am

MD, completely agree.

Working a men's FP game with a brick backstop, strike 3 went straight past F2 & ricocheted back to batter's foot, bouncing into the IF, before B/R knew it got past F2. No int.

in the OP, B/R was aware of her situation, & got tangled up with the ball as she passed from RH BB, across the plate, into LH BB...

MD Longhorn Tue Jun 24, 2014 09:46am

Quote:

Originally Posted by jmkupka (Post 936611)
in the OP, B/R was aware of her situation, & got tangled up with the ball as she passed from RH BB, across the plate, into LH BB...

I would say that's enough extra information that I'd rule INT as well.

Rita C Tue Jun 24, 2014 12:03pm

Quote:

Originally Posted by Manny A (Post 936599)
Which code is that, Rita? Under most softball codes, any batter-runner hindrance with an uncaught third strike is interference, whether intentional or not.

And for what it's worth, I believe OBR 7.09(a) has new expanded language that does not include intent.

Hmmm. I just checked high school softball and no intent required.

OBR 7.09a expanded language includes intent if it bounces off the catcher or umpire.

Doesn't seem right to penalize the batter for unintentionally interfering after the defense has erred. Especially in such tight quarters.


Rita

AtlUmpSteve Tue Jun 24, 2014 12:29pm

Quote:

Originally Posted by Rita C (Post 936625)
Hmmm. I just checked high school softball and no intent required.

OBR 7.09a expanded language includes intent if it bounces off the catcher or umpire.

Doesn't seem right to penalize the batter for unintentionally interfering after the defense has erred. Especially in such tight quarters.


Rita

Rita, I think we on this board have had that "the defense erred" discussion before. Here's the process:

1) Offense failed to hit strike three; be it swinging or called.
2) Defense failed to catch strike three. Defense needs to make a play to complete the out. Offense catches a break here.

How/why does the offense now get consideration for a free pass if batter-runner's actions keep the defense from completing the out? Sure, defense didn't catch it, but offense didn't hit it.

Rita C Tue Jun 24, 2014 12:48pm

Quote:

Originally Posted by AtlUmpSteve (Post 936628)
Rita, I think we on this board have had that "the defense erred" discussion before. Here's the process:

1) Offense failed to hit strike three; be it swinging or called.
2) Defense failed to catch strike three. Defense needs to make a play to complete the out. Offense catches a break here.

How/why does the offense now get consideration for a free pass if batter-runner's actions keep the defense from completing the out? Sure, defense didn't catch it, but offense didn't hit it.

There ought to be some room for doubt for the batter if it lands at her feet.

But if intent isn't to matter, so be it. I'll call it that way. But doesn't mean I have to like it.

Rita

MD Longhorn Tue Jun 24, 2014 12:51pm

Just don't call BR out if the ball simply hits her right off the catcher and she doesn't DO anything. I've seen umpires insist that because she happened to be where the ball went, she "interfered" because she altered the path of the ball.

Dakota Tue Jun 24, 2014 12:54pm

Quote:

Originally Posted by MD Longhorn (Post 936635)
Just don't call BR out if the ball simply hits her right off the catcher and she doesn't DO anything. I've seen umpires insist that because she happened to be where the ball went, she "interfered" because she altered the path of the ball.

Yes. It still requires "an act".

Manny A Tue Jun 24, 2014 01:02pm

Quote:

Originally Posted by Rita C (Post 936625)
OBR 7.09a expanded language includes intent if it bounces off the catcher or umpire.

Sorry for bringing a baseball discussion here, but the expanded language doesn't include the word "intent". It says it's interference if the batter-runner "clearly hinders the catcher in his attempt to field the ball." You can have clear hindrance without intent.

In softball, that clear hindrance requires an act by the batter-runner, as others have mentioned.


All times are GMT -5. The time now is 06:41am.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1