Interference with F3 on Fly Ball
Juco game (yes, IM, it happened to me again :o). Runners at first and third, one out. Batter hits a popup to F3 who is standing a couple of feet from the first base bag in fair territory, directly in line with first and second.
R2, who took a leadoff on the pitch, is sauntering back to the bag so that she doesn't get doubled up after the catch. She clearly bumps into F3 while the ball is still in the air, but not enough to phase F3, who is able to easily catch the popup just as R2 gets back on the bag. I was doing bases, so I saw the bump from behind the shortstop. My partner and I didn't call anything. Between innings, I asked him if he saw the bump, and he confessed that he was watching the flight of the ball. Reading 12.19.1.4 and the Note that follows the first paragraph, I'm not sure if this was interference or just inadvertent contact. If R2 had stopped or tried to get around F3, she could have been at risk of being tagged off the bag after the catch. But, assuming one of us had killed it the moment of the bump, and ruled R2 had interfered, would the appropriate ruling have been R2 out and the BR placed on first base? Or would we also rule the BR out based upon what is written in the second exception at the end of 12.19.1.4? |
Quote:
|
Quote:
|
Interference on a fly ball. The runner is out and the batter is out.
I assume by R2 you really mean R1 since we are applying NCAA rules. When in Rome... |
Any though on whether the bump actually hindered the fielder?
|
That's U's call, so I didn't really want to disagree with Manny's judgement on that. But I will add this, since you ask... my threshold for whether this is INT or not is going to be VERY low... and also, you need to make that determination at the moment of contact, and not wait to see if it actually affects the fielder. If it IS interference, it's dead at that instant, and the catch/no-catch never happens. If it's not, and you don't call it, and then she drops it, you can't (or well... shouldn't) retroactively change your mind.
|
Quote:
I mentioned in my OP the second Exception at the end of the rule that states, "If the interference prevents the fielder from catching a routine fly ball, the batter is also out." Well, the bump did not prevent F3 from making the catch. She was able to catch it easily. That's why I was leaning towards this being inadvertent contact. If the Exception was written to read, "If the interference occurs when the fielder is attempting to catch a routine fly ball, the batter is also out", that would be much clearer on how to rule in this instance. Quote:
|
Argh! My mistake entirely - was ruling ASA. You're right in NCAA rules that it's only interference if they prevent the fielder from making the catch. I retract all the nonsense I spouted previously. Sorry.
|
Quote:
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
Quote:
|
Quote:
|
Quote:
|
Quote:
Unfortunately, the rule only implies it, and doesn't state it outright. Here's one place: 12.19.1.4 Physical contact by the base runner with a fielder attempting to field a fair batted ball or a foul ball that might become fair shall be interference, provided the fielder had a reasonable chance to make a play and was prevented from doing so. The "and was prevented from doing so" certainly implies that we must wait to see if they are actually prevented. Also under effect: If the interference prevents the fielder from catching a routine fly ball, the batter is also out Again, the wording of "prevents the fielder from catching". It's not as clear as anyone would like - but with the clarifications at clinics, it's is clear what they want here. |
Quote:
Case plays on arbiter, from the NCAA rules editor, constantly use the phase that I highlighted: "interference is an immediate dead ball." It is even part of the rule: Quote:
Quote:
Please, please please have your clinicians send me their materials and/or videos. Because they are wrong. All of the clinics that I have attended (which include ones being hosted and presented by the SUP) have never made this distinction. |
Think what you wish, BS. I would ask you what the purpose of the rule I quoted might mean if the one you quoted is the only rule we should look at here.
But I don't have the energy right now for a semantic argument when I know what I've seen on about 10 different occasions. Call what you want... I hope your bosses like what you call. |
Quote:
|
Quote:
prevented from doing so. I agree that what you said and "provided the fielder had a reasonable chance to make a play" are equivalent. But if that is what the rulesmaker's intent was they would not have added, "and was prevented from doing so". |
Quote:
I used to play with a SS that dove for anything. I mean anything! 20' away when he hit the ground, but he dove for the ball. He was attempting to make a play, but he had no shot at doing so. If a runner was going from 2B to 3B and this guy dove for a ball up the middle that there was no chance to make a play and flew into that runner, I'm not calling INT. To me, that is how that rule reads. Granted, it may not be well written, but that is how this hi skuel gratiate reads it. |
similar sit this weekend, where F3 runs hard into the 1B coach while chasing a fly ball which just crosses the fence out of play (high fence; no chance of reaching over to make the catch).
If I call INT at the time of collision, I clearly have to reverse my call, no? (sorry, didn't realize this was a 5-year old thread) |
Quote:
|
All times are GMT -5. The time now is 11:21pm. |