I have a pet peeve. Like you, I enjoy watching professional baseball on TV. But nothing irks me more than commentators who call a foul ball a foul tip. Joe Buck is the worst offender, but there are others. Any sharp foul ball that shoots straight back over the catcher's shoulder or off the umpire's mask or otherwise goes uncaught but sharp off the bat, these dingbats call it a foul tip. These are not foul tips, they're foul balls.
Foul balls and foul tips are two distinctly different things. One results in a dead ball, the other is a live ball. One can result in strike three, the other cannot. One of them, by definition, must be caught; the other, again by definition, must not be caught. Foul balls and foul tips could not be more different.
In this article we cover the following:
Let's talk about the foul tip first, because it's the most straightforward.
First off, let's look at the rule-book definition of a foul tip [Definitions (foul tip)]. I'm going to add some boldface and italic for emphasis:
"A FOUL TIP is a batted ball that goes sharp and direct from the bat to the catcher and is legally caught. It is not a foul tip unless caught and any foul tip that is caught is a strike, and the ball is in play."
NOTE: The 2021 edition of the OBR changed the definition of foul tip. Whereas previously the definition read "a batted ball that goes sharp and direct from the bat to the catcher's hands ...," the 2021 update changed "to the catcher's hands" to read, simply, "to the catcher." The change also removed the following sentence: "It is not a catch if it is a rebound, unless the ball has first touched the catcher's glove or hand."
The upshot, then, is this: Any batted ball that goes sharp and direct from the bat to the catcher (any part of the catcher) and is legally caught is a foul tip. It is no longer required that the tipped ball touch the catcher's hand or glove first. A rebound off the mask or chest, for example, qualifies as a foul tip so long as the ball rebounds directly to the catcher's hand or glove and is legally caught.
Definitions (foul ball) begins with the longest, most poorly written and awkwardly tortuous sentence in the entire rule book, and also includes an extended "comment." I won't repeat it here, but ...
First off, there are three foul ball scenarios (and one special case) and you judge the ball to be fair or foul differently for each scenario:
Judged fair or foul by the position of the ball when (a) first touched by a fielder, or (b) where the ball comes to rest. It is not uncommon for the ball to fall in fair territory and then spin into foul territory before it is touched (or the other way around). On balls inside the bags, you must wait until the ball is either touched or comes to rest before judging it fair or foul. Until then it's nothing, so don't rush that call.
Judged fair or foul by where it crosses (and breaks) the blue sheet of glass. It the bounding ball crosses the sheet on or over the bag (that is, breaks the glass), then this is a fair ball. However, if the bounding ball passes the blue sheet in foul territory (and does not break the glass) then it is a foul ball, despite the fact that it may have bounced one or more times in fair territory before reaching the blue sheet.
Judged fair or foul by where the fly ball first touches the ground, or where a fielder first touches the ball in flight. If the ball first touches the ground in fair territory, it is a fair ball. If in foul territory, then it's a foul ball. Similarly, if a fielder first touches the ball while the ball (not the fielder) is over fair territory, then it's a fair ball. Likewise, if first touched over foul territory, it's a foul ball.
Judged fair or foul. The only judgement is whether the batted ball hit the batter while he is still in the batter's box. If it did, then you have a foul ball. Come up fast, big and loud: "FOUL! FOUL!" This call belongs to any umpire who sees it.
This is sometimes difficult to see, particularly for the plate umpire. It can also be tricky because sometimes a batted ball will hit off home plate and come out oddly, making it look like it came off the batter's foot. Experience alone will help you see this clearly. Along with experience comes the ability to infer certain things from the batter's actions. Be careful with this because, at upper levels particularly, batters will try to manipulate you with their acting skills. At lower levels, however, the batter's reactions run truer.
In our articles on Umpire Mechanics we'll discuss at length which umpire owns the fair/foul call, when and where. For now, let's concentrate on the mechanics.
You verbalize a foul ball ("FOUL!") and raise both arms, palms forward. For a foul ball in the outfield you then point in the direction of the foul.
You never verbalize a fair ball. Instead, you simply point into fair territory. If the call is a close one, point emphatically.
Using the basics for a foundation, amend your mechanics as follows:
Implemented in the American League in 1973, the Designated Hitter (DH) rule has migrated to most levels of amateur baseball, but in somewhat different forms. While OBR Rule 5.11 provides for a designated hitter to bat for the pitcher (and only the pitcher), most DH rules in amateur baseball leagues allow the DH to bat for any defensive player.
The original intent of the Major League rule was to enhance offense in the game (and to protect some aging players); however, amateur versions of the DH rule are also intended to increase opportunities for players to get in the game. It is this latter point that has led to yet another innovation, which you see only in amateur baseball, the "extra hitter" (EH).
I won't try to summarize all of the DH rules for all of the leagues. That would require a small book. Instead, I'll present a list of key features of the DH rule and point out where other rule sets are likely to differ. Of course, the key point here is that you must learn the DH rule for the league (or leagues) for which you work.
This is all pretty straightforward. Where it gets messy (and where many leagues go their own way) is in the matter of substitutions involve both the DH and the pitcher. It gets so messy, in fact, that the NCAA requires (by regulation) that at least one umpire on each crew has to carry a laminated cheat sheet to help them negotiate the subtleties of pitcher/DH-related substitutions.
The extra hitter (EH) rule takes the concept of the designated hitter one step further. Instead of just adding a player to bat for a defensive player (ten players, but only nine batters), the EH adds a tenth batter to the batting order. If a team is playing with both the DH and the EH (this is not uncommon), then you have eleven players in the lineup, ten of whom bat.
Of course, the EH rule is not a rule that you'll find in the OBR, and is not used in Major League play. The impetus for the rule is simply to more easily involve a greater number of players in the game, and is particulaly common in youth leagues. Because of that, EH rules are league-level and may vary from league to league. The EH rule generally stipulates the following (but again, you must check your league rules):
There are some loose ends on the EH rule, and variation from league to league (and level to level) so it's essential that you be fully briefed on the rule for the league you work.
You should read this article in alongside its companion, Runner Touched by Live Ball. Originally I had just one article that covered both batter and runner because there is so much overlap. However, because the rule book differentiates between the batter, the batter-runner, and then the runner, I've broken them up.
Let's start by breaking the batter portion into its two main parts:
1. The batter touched by a pitched ball
2. The batter-runner touched by his own batted ball
Because you handle each case differently, well go deep on both. First, though, keep in mind that when we talk about a batted ball, we're talking about a live batted ball. A batter-runner touched by a batted ball over foul territory is just a foul ball (unless he intentionally deflects it [see 6.01(a)(2) ]).
Let's start with a batter hit by a pitched ball. We all know that if a batter is hit by a pitch he is awarded first base (and that other runners advance if forced). Right? WRONG!
In truth, most often it is the case that a batter is awarded first base when he or his clothing is touched by a pitched ball. But not always. Let's look at some exceptions and nuances of the rules covering batters touched by a pitched ball:
And watch out for this one: You'll see some of the older, more experienced batters do that quarter-turn away from the ball, but what they're really doing is slyly moving into the path of the pitch as they make that quarter-turn. It's subtle, and it's easy to get fooled (I've been fooled by this). You won't see this in the younger kids (most of them are too afraid of the ball to begin with), but you can run into this at the upper levels.
Caution: If you have a batter hit by pitch on a checked swing, be alert. If you rule that he went (or if you go to your partner and your partner says "Yes, he went"), then you have a strike (and the batter's out if strike three). If you or your partner rules that "No, he didn't go" then you have a batter hit by pitch and a base award. Be alert for this.
We have an MLB video that captures just this scenario. Miguel Cabrera checks his swing on a pitch that hits him square in the knee. Home plate umpire, Brian Gorman, rules that he went, so instead of hit-by-pitch, it's a strike. Cabrera grouses and is eventually tossed.
In rare situations where, for example, rival teams appear particularly hostile as they prepare for the game, you have the authority to issue the bench warnings preventively at the start of the game.
A batter touched by his own batted ball is either (1) the batter is still in the batter's box when the ball rebounds and hits him or the bat, or a batted ball hits him directly on the foot or ankle, or (2) he is touched by a fair batted ball after he's left the batter's box.
In the first scenario, where the batter is hit by his own batted ball while still in the box, this is simply a foul ball [ 5.09(a)(7) ]. Sometimes it's difficult for the plate umpire to see this, so the base umpire(s) should immediately call "Foul" if they see it.
In the second scenario, where the batter is touched by his fair batted ball after he's left the batter's box, you have interference. The batter is out, the ball is dead, and runners, if moving, must return to their time-of-pitch base. This is no different from other base runners touched by a fair batted ball, which we discuss in the article Runner Touched by Live Ball.
Note that if the batter is touched by the ball over foul territory, that's simply a foul ball, not interference (unless the runner intentionally deflects the batted ball [6.01(a)(2)]).
Here's a video showing an example of a batter being hit by his own batted ball – in this case, on a bunt attempt. You can see that he runs into his own batted ball as he leaves the batter's box. That's interference. No arguments on this one.
Few baseball rules are dealt with incorrectly more frequently than batting out of order. The applicable rule is 6.03(b), which was last revised (and clarified) in 1957. So the rule has been around for a while.
The rule, penalties, and remedies for batting out of order are not difficult to understand. The tricky part is fixing a batting-order infraction once an appeal is upheld. The plate umpire owns this one since the plate umpire owns the lineup.
Note: For an interesting read about the history and confusion surrounding this rule, see an article in the SABR Research Journal entitled, fittingly enough, Batting Out-of-Turn Results in Great Confusion, written by Mark Pankin.
Let's start by clarifying two terms essential to discussing batting out of order: proper batter and improper batter.
When untangling a batting-order infraction, only two batters matter: the batter who is presently at bat, and the player who batted previously. We'll see why shortly.
Important: Batting out of order is an appeal play. You should never point out an improper batter on your own initiative, nor should you let the scorekeeper or anyone else "outside the fence" have any say. Only members of the team on defense can ask for time and appeal a batting order issue, although the offense can ask for time and rectify the mistake while the improper batter is still at bat.
A batting-out-of-order appeal begins with the defense asking for time. The manager approaches the plate umpire and claims there is a batting-order infraction. At this point you consult the the official lineup (which is the one that you carry) to establish whether a player batted (or is batting) out of turn.
A batting order infraction presents itself in one of three ways:
Note: Frequently, what appears to the defense to be a batting-order infraction turns out to be confusion caused by an unannounced substitution [ 5.10(j) ] Be alert for that.
If upon consulting the lineup you confirm that any one of the three cases applies, you have a batting-order infraction and you should uphold the appeal. You must then take one of three courses of action, depending on which of the three cases applies.
Important: If the improper batter's at-bat results in his being put out, and if the defense then appeals the batting order infraction, that put-out is nullified. The defense gets the out from the batting out of order infraction, but they don't also get the put-out on the play. Taking it one step further, if the improper batter's at-bat results in a double-play, an appeal of the infraction nullifies both of those outs. In short, a defensive manager is wise to know this rule well, since sometimes it's best to just leave well enough alone.
This all sounds somewhat confusing, but if you learn the rule and approach it systematically you can usually untangle it without too much trouble. Also note that 6.03(b) Approved Ruling includes several example scenarios. These are useful learning tools.
The flow diagram on the right summarizes how to handle each of the batting-out-of-order scenarios: