coaching strategy?
 

So can I expect that if a batter hits a foul pop fly somewhere in the vicinity of home plate or along the first base line that a) will clearly be a foul ball [unless it falls untouched and takes a weird bounde; and b) a defensive player has settled under the ball in order to make a catch, that the batter can run over to said defensive player, and swat at the ball or pull the defensive player's glove away from the ball and all I can do is probably call a foul ball??

That's a foul call, my friends.

Ted

sigh.... ok my 2 pennies... the batted ball isnt foul till its touched or settles in foul territory or passes a base in foul territory... by that measure the interference occurred during a live "not yet foul" batted ball thereby negating the touch by F1 to make it foul..... BR is out for interference and runners (if any) go back. (no dbl play consideration as in my judgement based on F1 touching it in foul territory, there would be no second play chance)
hope this on a test this year.... its gonna be 50/50.

BTW: this was a very enjoyable topic to try and cipher... .the rule books suck on this matter.

Problem is, the horse is not dead...

I guess you're not getting what I am saying. Rule 1-FOUL BALL-D is inherently self-contradictory. It defines as a foul ball a situation that requires interference where by definition there is no play, which is required for interference to be called. Since there is no play, there can be no interference, since there can be no interference, Rule 1-FOUL BALL-D can never apply.

However, knowing that the writers of the ASA Rule Book are not paragons of Vulcan-level logic, I suspect this self-contradiction is (probably) not intended. This leaves us with 3 alternatives for the rule:

1) ASA considers any fielder attempting to field a batted ball to be making a play, hence the interference call is valid, hence the BR / B is out, or

2) It is interference at the time of the contact (since the status of the ball is not yet determined), but the penalty for interference is not enforced because the act of interference itself defined the status of the ball as foul.

3) ASA is using the term "interferes with" sloppily and merely means generically impedes, rather than commits a defined act of interference.

Whichever way, the rule book has issues with this scenario.

No, my friend, that is a different scenario which is addressed by a different rule.

So Irish,

The discussion of the rule(s) being less than adequate would apply only to a foul ground ball? That would make me feel a little better. If you have the rule reference, I'd appreciate it.

I guess I was thinking the same rule would also apply to a foul fly, which doesn't seem right.

Thanx,

Ted

Already referenced in Post #49 of this thread.

And, I guess you aren't getting what I am saying, either.

You could come up with even more than those three possible alternatives if you wanted to stretch it further, but only one reasonably passes muster.

1. ASA defines a "Play"; in fact, that definition is newly added in 2007. It doesn't include this interpretation, so it isn't that.

2. Since ASA requires a "Play" to have the act of "Interference" that results in the penalty out, and at the moment of contact the definition establishes a foul ball, so there is no "Play", there isn't a penalty out to be enforced. It isn't "not enforced", there isn't one to enforce.

3. Ding-ding-ding!!! The remaining alternative is clearly the winner of the alternative ruling contest. This rule definition (Foul Ball D) misuses the word "interferes" when defined "Interference" cannot be the result.

If you simply accept that conclusion (your #3), all else works together, and there are no contradictions in the Rules 1, 7 and 8 in this play, as you previously stated; and Rule 10 application isn't necessary

#3 IS a contradiction. That is what I am saying. Rule 1-FOUL BALL-D IS a contradiction. With all of the fuss and bother to make the rules concerning interference a couple of years ago consistent with the lack of the word "intent" in the definition of interference, and with the over-precision ASA used in defining "play", this rule becomes self-contradictory. There can be no interference on a foul ground ball, hence the rule needs to be fixed. As can be seen from this very thread, this contradiction DOES result in some umpires calling an out in this scenario. The rule needs to be cleaned up.

"Ding, ding"

Well, being one of the last folks involved in the wording of the definition of "play" in the rule book, I guess I should take exception to this comment :rolleyes:. However, I do not as the reason the wording is precise is to make sure umpires don't go off in multiple directions reading into a rule as we see happen so often.

Which was a result of these umpires not reading and taking into consideration all aspects of the play and applicable rules. Some saw "ran into F3" and were immediately going to the INT.

The rules to cover this scenario are in place, and as previously noted, must be considered as a whole, not in selected portions. This is one reason why allowing coaches onto the field with a rule book is discouraged.

I agree a definition was needed, but the absolute requirement for there to be an attempt to retire a runner (as opposed to, for example, hold a runner), is overly precise, IMO. Having said that, I haven't thought through the implications of a broader definition, either.I agree, but that is no excuse for using the word "interfere" when definitional interference is not possible.I agree with this in principle, and as I posted earlier, the conclusion I come to is this is a dead ball and a foul ball, even though the BR/B did NOT commit interference as required by the rule.

However, given the other situations where a runner can forfeit protection by a base running violation, I can readily see how even diligent umpires could come to the conclusion that the BR is out due to interference.

Or, since interference is not possible, ignore the contact altogether. Either is a reasonable view of the rules as a whole, and both are wrong.

Actually, it says "offensive player", but I don't want to be too precise :cool:. The need to define "play" came from the constant bickering over the term when used in the LBR. If you make it broader, you are going to have umpires stating that simply turning and looking toward a runner in an attempt to "hold" them on the base would be a play and release all other runners.

Where does it say that?

But there is no BR, so 8.2.F does not apply which, I think, is what some folks are missing here.

Which I could understand happening once, ONCE!

No one is suggesting the contact be ignored especially if intentional. There is always USC available and I wouldn't have a problem with an umpire telling a coach, "There is no INT because it is a foul ball. However, that does not mean your runner doesn't have to avoid contact. Failure to do so in the future may come with penalties."

1 - Foul Ball - D

That's my entire point. Agreed that the use of the word "interferes" is poorly chosen. Accepted; taken alone, it is inappropriate, since it cannot be "Interference".

Disagree that we can't get past that, or that anything else is contradictory. Take your book, replace the words "interferes with" in that one location with "hinders"; then tell me where or why there is any other contradiction, or why you insist on invoking Rule 10.

That's all I've been saying all along; yes, that one word in that definition has not been wordsmithed since the Interference revisions. If we accept that, then I see no other contradictions, need for ASA official interpretations, or general confusion; the answers are already in the book.

If the answers were already clearly in the book, then why has this topic grown to 4 pages? Why have other rule orgs clarified this specific situation?

Well, if you remove the contradiction, then there is no contradiction, is there?

But, even a casual reading of this thread, plus the one from 2 years ago, would seem to argue against your view that this is obvious.

The Rule 10 safety valve is because to get to a correct call here requires bypassing at least 2 "cast in concrete" concepts in the rule book, namely that interference requires a play, and interference requires someone to be called out. Not to mention, of course, that a batter is not even mentioned in any of the rules being applied here. Sure, I would explain it was simply a foul ball and hope to get away with only a brief discussion with the DC, but there is that inconvenient use of the word "interferes" that might be brought up.