![]() |
|
|
|
|||
|
Mike linked to a discussion of a nearly identical situation above somewhere. This discussion was held about 2 years ago. Below I'm relying heavily on a reply I posted in that other discussion.
The definitions support the call of interference, assuming attempting to field a batted ball (not necessarily fair) can be construed as attempting to make a play. What the rules do not support is declaring the batter/batter-runner out. The RS says two things that may pertain to this discussion: Quote:
Quote:
Rule 10 allows the umpire to make a reasonable call, but he should not make up a new rule out of whole cloth. If the runner had contacted the ball instead of the fielder, it would have been a foul ball. If the fielder had been successful in fielding the ball while still in foul territory, it would have been a foul ball. The fielder was not given the opportunity to field the ball while in the playing field. Stringing all of that together, I am still with the dead ball on the interference, no one out since the ball was foul. Rule 10.
__________________
Tom |
|
|||
|
looking a BR only here...
I'm with a couple of you thinking I had this, but the more I read, the cloudier it gets.
One thing a recall from the National Umpire School training last March: if interference is called, there has to be an out somewhere, possibly two given certain conditions. A foul popup on which F1, F2, or F3 is hindered by the batter [becoming a batter-runner because no one should be waiting for the ball to land] should be called interference. I think the issue is a ground ball that is rolling along the 1B line. I know: If the BR contacts the ball in fair territory, the BR is out; if the BR contacts the ball in foul territory [accidentally or intentionally], the ball is ruled foul. There was a situation posted several back where the BR and F1 collided while the ball was currently in foul territory and without being touched, and after BR reached 1B rolled back and settled in fair territory. I guess I'm with several that wonder if that's interference. I also wonder if it might be obstruction since F1 was in the basepath without the ball in her possession. In a similar but slightly different twist, batter hits a chopper off home plate that bounces very high down the 1B line. F3 is straddling the base line waiting for the ball to come down. Before she gets possession, the BR runs into her causing F3 to misplay the ball. F3 was attempting to make a play on a ground ball, and according to rule, if it's a fair ball it's a play, but if it's a foul ball, there can be no play. So after contact, if PU determines the ball was over foul territory, no play, incidental contact, foul ball, batter returns. But if PU determines ball was over fair territory, obstruction, interference, or nothing? I've always been of the opinion that the BR must go around the fielder attempting to make a play [without going down that mink-lined definitional rathole]. Unless the fielder has the ball in her possession, and then the BR could be called out for running outside the basepath. Ted |
|
|||
|
It would only be obstruction if you were ruling that a different fielder was the one who had the play on the ball. As long as F1 is the fielder making the play on the batted ball, she cannot commit obstruction.
__________________
Tom |
|
|||
|
Quote:
Ignoring the contact and calling the ball foul once F1 touched it foul seems to be the only book-supported option. |
|
|||
|
I think I would kill the ball as soon as the contact was made with a fielder attempting to field a batter ball. If the ball was foul at that moment, I would rule a foul ball. If asked by a coach I would have to say "Coach I screwed up I killed the ball out of habit when I saw the contact, the ball was in foul territory so it stays foul since I killed the play, so since it is foul there was no play to interfere with so it's just a foul ball"
|
|
|||
|
Quote:
__________________
Tom |
|
|||
|
Quote:
Quote:
__________________
Tom |
|
|||
|
Quote:
And we still have the USC to prevent the batter from plowing into the fielder. |
|
|||
|
Quote:
A foul fly ball comes to mind, but if you have interference with a foul fly ball you don't immediately call the ball foul. You call it dead for interference and call it foul by implication. You don't say just because it's foul, I have no interference. Now, I'm not sure I remember the foul interference rule. If I had my book I'd look this up, but what do you do with the batter there? Interference by R1 at 3rd with a foul fly ball results in R1 being out, no? And if so, then B2 now has an extra strike. Whereas interference with R1 at 3rd on a fair fly ball results in the B2 becoming R2. ________ Glass Weed Pipe Last edited by youngump; Mon Sep 19, 2011 at 06:35pm. |
|
|||
|
Quote:
If there is INT on a fly ball over foul territory, the ball IS dead and declared foul by rule. Quote:
|
|
|||
|
One thing I think we can all agree on is the rule book has issues with the scenario. Among them are:
o By definition, a play is an attempt to retire a runner or BR o There must be a play for there to be interference o If the call is interference, somebody is declared out o By definition, interference with the fielder while the ball is in foul territory is a foul ball. o A batter cannot commit interference on a batted ball, but our offender here is now a batter (again, still, who cares...) o There is no play (by the definition of a play) on a ground ball in foul territory. Make the call and explain it is the best we can do. The act of interference kills the ball and defines it as a foul ball, which defines the offensive player as a batter, which negates the expected out for the interference call. Dead ball, foul ball, runners (if any) return, batter back in the box. Use Rule 10 to fill in the issues with Rules 1, 7, and 8. It ain't pretty, but it seems to me to be about the best there is to do with this one.
__________________
Tom |
|
||||
|
Quote:
Quote:
Quote:
Quote:
|
|
|||
|
A couple people responded to fragments of my post, but it must be viewed in its entirety to apply (like the rule book); so here it is again:
" batted ball in flight or dribbling near the line or wherever else is not foul until it meets one of the foul ball criteria. We have concluded in at least two other topics that the B to BR transition happens even though the batted ball does not end up being a fair batted ball; because it is not foul until the foul ball criteria apply and because it must be for the application of rules to make sense. In this OP, the player who batted the ball, now the BR, interfered with F3 trying to field the batted ball, so the player who interfered is out, any other runner(s) return. " I don't get calling dead ball if you don't see the play as INT. An incidental collision does not cause a dead ball. Let's ignore the UC possibility, because that would need a separate topic. Also, it is a "play" for a fielder to go after a ground ball in foul territory because it prevents it from going fair; stops progress of BR/R, etc.
__________________
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. |
|
||||||||
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
1. It is NOT a "Play", as defined by ASA, when a fielder is attempting to field a batted ball over foul territory that is not in flight; it may serve a strategic purpose, but it isn't a play. 2. It is NOT, therefore, "Interference", as defined by ASA, because the fielder is not attempting to execute a "Play". There is no out without that definition being met. 3. While the contact is NOT "Interference", it did interfere with the fielder, thus the definition of a "Foul Ball" has been met. The result is a strike on the batter, unless there are already two strikes. 4. When the definition of a "Foul Ball" was met, the status of the "Batter-Runner" reverted to "Batter", since the "Batter" did not hit a fair ball. 5. Since the moment of contact was simultaneous with the status reverting to a "Batter", 8.2-F(1) does not apply, rendering moot the argument that it doesn't state fair batted ball. 6. Rule 10 does not and need apply, since the application of the rules provide for an appropriate ruling. Foul Ball, no out, all runners return to the bases occupied at the pitch. If the contact is judged flagrant, the offender is ejected. 7. The NCAA ruling would be the same; the definitions are (reasonably) the same. 8. The NFHS definition of a "Play" would allow the OP to be a "Play"; but the status of a "Foul Ball" at contact still reverts the offender to a "Batter"; there is no applicable rule rendering a "Batter" out, unless the fielder involved is the catcher. In that limited event, it would be (IMO) OOO to apply a rule that doesn't appear intended to relate to a batted ball.
__________________
Steve ASA/ISF/NCAA/NFHS/PGF Last edited by AtlUmpSteve; Tue Dec 02, 2008 at 12:39pm. |
![]() |
| Bookmarks |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Whats the call | justcallmeblue | Softball | 28 | Wed Jul 09, 2008 12:50am |
| Whats the call? | veg4 | Baseball | 1 | Mon Aug 15, 2005 01:15pm |
| whats the call? | wilkey1979 | Basketball | 7 | Wed Feb 25, 2004 09:03am |
| Whats the call? | Ricejock | Softball | 2 | Sat Apr 20, 2002 10:24am |
| Another ASA whats the call | Gulf Coast Blue | Softball | 3 | Sat Feb 03, 2001 11:29am |