A time play (not "timing" play) is when a third out (but not a force out) is made on the bases on the same play in which another runner crosses home plate. If the runner touches home plate before the third out is made on the bases, the run scores. If the third out is made before the runner touches home, then the run does not score.
Example: You have a runner on first (R1) with two outs. The batter-runner (BR) hits a beautiful line drive in the gap in right-center that goes all the way to the fence. The BR is thinking double. At the same time, R1 is approaching third and the base coach is sending him home. But the center fielder gets a carom off the fence and makes an awesome throw to second base just as BR slides in. Base umpire calls him out at second. At just this moment, R1 is crossing the plate.
Well, that plate umpire had better be paying attention because he's got a time play on his hands. He has to see the out at second (not the base umpire's signal of an out, but the actual event), and he has to also see the touch of home plate. Then he has to make a call. We discuss the mechanic for making the time play call a little farther down.
This is pretty simple. The hard part is being alert to a time play developing, and for the plate umpire to position himself so that he can see both the out on the bases and the runner crossing the plate.
Preparing for the possibility of a time play is similar to recognizing that you're in an infield fly situation. As with the infield fly, where the umpires exchange signals to prepare mentally for the possibility, the same is true with a timing play. With two outs and one or more runners in scoring position, the plate umpire should signal his partner(s) two fingers tapping an imaginary wrist watch on the left wrist, to alert everyone to the possibility of a time play.
The only flaw in the time play signal is that you can find yourself with a time play with just one out (or none, for that matter). Both are uncommon, but they can happen. So, again, the lesson here is being alert.
When a time play occurs, and particularly if the play at he plate and the play on the bases are very close, it is very important that the plate umpire verbalize the outcome of the play (either the run scores or it does not). The plate umpire must indicate to the scorekeeper (or whomever is keeping the book):
Failing to announce the outcome of a time play can lead to big problems, particularly if one bench assumes one outcome while the other team assumes the opposite. Two innings later, when everyone discovers that their game scores are not in sync, you're going to have the argument of your life.
The rules for awarding bases are probably the most misunderstood in baseball. No doubt this is due, at least in part, to the large number of rules references (28 rule references), as well as the many nuances in the application of the rules. Trying to learn base awards from the Official Rules will drive you to … well, it'll drive you to lacrosse.
Under a given set of circumstances, an umpire can award a runner (or batter) one, two, three, or even four bases. In some cases, the award is made from the time of the pitch (TOP), while in other cases the award is from the time of a fielder's throw (TOT). Also, while most base awards are dead-ball awards, in a small number of cases the ball remains live (on a base on balls, for example). We'll point out these exceptions.
Important: Most of the base award situations that cause confusion (and arguments) result from a live ball thrown out of play. So let's be sure we're clear what we mean by "out of play." We're not talking about an overthrow into foul territory. We're talking about a ball that goes entirely outside the field of play – over a fence, into the stands, into a dugout, or beyond whatever out-of-play boundaries are established by ground rules at the field you're on. On amateur baseball fields, these boundaries are sometimes arbitrary. It is very important that you clarify out-of-play boundaries at your plate meeting.
The best way to cover this broad canvas is to group by the number of bases awarded – one, two, three, and four. Within each group, where appropriate, we'll discuss TOP vs. TOT situations.
The other portion of the rule (where the pitcher throws the ball out of play) is more common: The pitcher makes a pick-off throw to first base while engaged to the rubber and throws wild out of play. You see this on amateur fields that are not fully enclosed. (Note that if the pitcher has disengaged the rubber before throwing the ball out of play, the award is two bases, not one, because he has committed the error as a defensive fielder, not as a pitcher. For more about this, see The Pitcher. We also cover this in the section Two-base awards, #4.)
Important: There are some important nuances to the offensive interference rule. Be sure to read Offensive Interference carefully.
Important: Normally, we'd include here a note about "catch-and-carry." However, in 2016, Major League Baseball amended the rule, such that catch-and-carry no longer exists. Any live ball that is carried into dead ball territory is now considered a dead ball and runners advance one base. Rule 5.06(b)(3)(C) Comment reads: "If a fielder, after having made a legal catch, should step or fall into any out-of-play area, the ball is dead and each runner shall advance one base, without liability to be put out, from his last legally touched base at the time the fielder entered such out-of-play area."
If a runner from third tries to steal home when there are two outs AND two strikes on the batter, AND IF the ball strikes the runner in the strike zone, then (a) call strike three (batter's out), (b) inning over, (c) run does not count. However, in the same scenario, but before there are two outs, you call strike three (batter's out), runner scores, and the ball is dead. If other runners were moving on the pitch, they must return.
A runner on third base tries to score by means of a squeeze play or steal. The catcher sees him coming and encroaches on home base to get the ball quickly, or else touches the batter or the bat in a rush to get the pitch to make the out. But what the catcher has done is interfere with the batter's opportunity to offer at the pitch, which is defensive interference. In this special case, you do four things: (a) Call "Time" to kill the play; (b) charge the pitcher with a balk ("catcher's balk"); (c) score the run on the balk (other runners also advance one base); and (d) award the batter first base on the defensive interference.
The second part, 5.05(a)(7), extends the ground rule to fair bounding balls that leave the field in foul territory, or that lodge in a fence, scoreboard, "shrubbery or vines," or that otherwise escape the field of play. Note that we're talking about a fair bounding ball that leaves the field in foul territory. Again, the ball is dead and all runners, including the batter-runner, advance two bases from their TOP base.
There's one wrinkle that you need to keep in mind. Rule 5.06(b)(4)(G), Approved Ruling stipulates that "If all runners, including the batter-runner, have advanced at least one base when an infielder makes a wild throw" then the award is two bases from the time of the throw (TOT) instead of TOP. Seems simple enough, doesn't it? But here's the rub. You (all umpires) must see the release at the same time you have clear awareness of runner positions. Not an easy task, but fortunately this is a pretty rare case.
Note: This rule only applies if the detached item actually touches a thrown ball; if an item is thrown but does not touch the ball there is no infraction.
Intentionally touching a fair batted ball with equipment or clothing. [ 5.06(b)(4)(B, C) ]. This is the only three-base award in baseball. Any fair batted ball that is touched by a fielder using detached equipment (catcher's mask, for example), thrown equipment (including the glove), hat, or other paraphernalia, is a three-base award for all runners and the batter-runner. The award is applied to all runners on base (if any), and also for the batter-runner (who gets third). The ball remains live.
This rarely happens any more now that most catchers use the bucket helmet/mask. Back in the day, you might see a catcher reach out with a mask to snag a bunted ball or dribbler. Compare this with the matter of the thrown ball touched with detached equipment, which gets you a two-base award.
Home run [ 5.05(a)(5), 5.06(b)(4)(A) ]. There's only one four-base award, what's better known as a home run – that is, a fly ball that leaves the field of play in fair territory.
Actually, there are some little-known nuances to the home run rule. For example, the wall in fair territory that a fair batted ball must cross "in flight" must be at least 250 feet from home plate. If not, the batter doesn't get a home run, but instead is awarded only second base (ground-rule double). Of course, the 250-foot restriction doesn't come into play at any of our Major League stadiums, so this is more trivia question than restriction.
But there's another issue. If a fielder in fair territory deflects a fly ball into the stands or over a wall in fair territory, you have a home run (think Jose Canseco deflecting a fly ball off his skull). If a fielder in fair territory deflects a fly ball into the stands into foul territory, on the other hand, you have a ground-rule double. This is not a very common scenario, but it's one to be mindful of.
Finally, 5.06(b)(4)(A) restates the obvious – that on a home run the runner must touch all four bases; if not, he is subject to being put out on appeal, which, if upheld, nullifies the run (but not runs scored by preceding runners). The rule also stipulates that an umpire can award a runner four bases (home run) if the ball "in flight" is prevented from going into the stands by a fielder deflecting it with thrown glove, hat, or other paraphernalia.
We learn in our article, Obstruction, [ 6.01(h) ] that for Type 2 (Type B) Obstruction (where the obstruction takes place away from the play), the umpire has complete discretion in making the base award [ 6.01(h)(2) ]. The directive is to make base awards so as to nullify the act of obstruction. In many cases, this means no base award at all. On the other hand, this can mean a one-base award, more rarely a two-base award, and (theoretically, at least) a three-base award, although it's hard to imagine circumstances that would call for a three-base award.
Awarding bases when there is Spectator Interference [ 6.01(e) ] is similar to how you handle Type 2 obstruction, in that the objective is to nullify the interference. There is a twist, however, because while obstruction only affects base runners, spectator interference affects the defense. So awarding bases when there is spectator interference usually involves placing runners back (or stopping them from advancing), and in some cases requires that you call a batter out.
On spectator interference, the ball is immediately dead. Call "Time" right away. The directive then (in the language of the rule) is that "the umpire shall impose such penalties as in the umpire's opinion will nullify the act of the interference." In the case of a fair bounding ball that a spectator touches by reaching into the field of play (live ball territory), place runners at the base they last touched at the moment the interference occurred.
In the case of a spectator disrupting a fielder's opportunity to catch a fly ball, it is very important to note whether the disruptive act takes place over live-ball territory or dead-ball territory. If over live-ball territory (that is, a fan reaches out into live ball territory – typically foul territory, but live nevertheless), then you have spectator interference and you judge that the interference prevented the fielder from catching the ball, you should call the batter out. If you judge that the fielder likely would not have caught the ball, then the ball is dead and you have a foul ball.
However, if it is the fielder reaching into (or entering) dead ball territory, then you cannot have spectator interference; the ball is dead and is simply a foul ball. Note that we cover this subject in much greater detail in Spectator Interference.
You should read this article in tandem with its companion, Batter Touched by Live Ball. Originally I had just one article that covered both scenarios because there is so much overlap. In almost all cases of a base runner (or batter-runner) being touched by a live batted ball, you have interference. The touch does not need to be intentional. A runner touched by a live batted ball is interference. Dead ball, runner is out, and other runners return.
However, there are a handful of important exceptions. The rule is easy, but the exceptions can be tricky, so let's focus on those cases where the runner is not out when touched by a live batted ball.
Unfortunately, the rule book makes this straightforward rule more complicated than necessary. To cover the issue of a runner touched by a live batted ball, you're forced to do a gymnastic mashup of six rules — 5.06(c)(6), 5.05(b)(4), 5.05(a)(4), 5.09(b)(3), 5.09(b)(7), and 6.01(a)(11). You might be tempted to hire a lawyer, but I think we've got you covered.
We're going to cover two areas:
As we said, any runner touched by a live batted ball has committed interference and is out. The ball is dead. The batter-runner is awarded first base (unless he is the one touched by the batted ball), and other runners advance only if forced. Let's focus on the exceptions:
Note 1. Exception to the exception: If, in your judgment, the base runner intentionally touches a batted ball that is misplayed or deflected by a fielder, you should ignore the exception, kill the ball and call the runner out.
Note 2. The concept of "step-and-reach": When judging the fielder's "protection" from interference on a misplayed or deflected ball, there is the generally accepted notion of the "step-and-reach." That is, on a misplayed ball that remains close to the fielder, the fielder is allowed a small halo of protection while he tries to retrieve the ball. But all the fielder gets in terms of protection is a step and a reach. This step-and-reach is not a real measurement, nor will you find it in the rule book; rather, it's the literal description of a fielding gesture. You learn this one on the field.
Note 3. Only on an infield fly is the base a safe haven for runners touched by a live batted ball. On all other batted balls, the base runner must make way for a fielder attempting to field a fly ball, and must not allow himself to be touched by the ball, even if he has to step off the bag to do so.
Again, this is actually a pretty straightforward rule if approached systematically. The rule is made cloudy by the way the rules for the exceptions are written. The best approach is to recognize that a runner (or batter-runner) touched by a batted ball is out for interference. Then, learn the exceptions.
In contrast to a batted ball, being hit by a thrown ball is not interference (it's nothing – live ball, play on) unless the runner intentionally makes contact with the thrown ball or otherwise hinders or impedes a fielder's opportunity to field or throw the ball.
In short, while interference with a batted ball does not require the act to be intentional, interference with a thrown ball requires an intentional act on the part of the runner.
If a runner is touched by a thrown ball and you judge the contact to be intentional, then call "Time" (dead ball), call the offending runner out, and return other runners (if any) to the base last legally acquired at the time the interference occurred.
The base runner (including the batter-runner) is such an integral part of the game that rules governing base running span the majority of Rule 5.0. Additionally, references to the base runner crop up throughout the rule book. So, while some of the material in this article duplicates information found elsewhere, it's helpful, I think, to still bring everything related to the base runner together in a single article.
There is so much ground to cover, I thought it best to break this out into three logical sections, then list the rules (and rule references) as bullet points, discussing each in turn.
The definition keeps it pretty simple: "Runner is an offensive player who is advancing toward, or touching, or returning to any base." That said, there is a slight conflict with Definitions (batter-runner), which is, by definition "… the offensive player who has just finished a time at bat until that player is put out or until the play on which that player becomes a runner ends." As you can see, both definitions apply to the batter-runner.
The latter term, "batter-runner," is typically used in describing base-running scenarios to distinguish runners already on base from the runner whose at-bat initiated the current play. There are some base award situations in which the batter-runner is treated differently from runners on base.
We have to look first at 5.08(a) because this is one of the "golden" rules of baseball, one of the very fundamentals: the rule that specifies how you score a run. Let's read it:
Now we need to look at the "Exception" to 5.08(a). A run does not score if a third out is made on the play in any of the following ways:
The first two exceptions are pretty obvious and likely pretty familiar. The third one, however, frequently causes confusion and arguments. If, with two outs, a runner scores, but a preceding runner (that is, a runner ahead of him) is subsequently called out (for the third out) on appeal for missing a base, then the action of every following runner is nullified because their actions took place, technically, after the third out was made.
We devote an entire article to the matter of Getting Outs, where we list and discuss all of the ways that players on offense can be put out. Twenty of these ways apply to the batter; following are the eleven ways that a base runner can be put out:
The notion of the base path is much misunderstood. In fact, there is no base path on a baseball field. It's definitely not the lines between the bases. There is no such thing as a base path untill …
The base path comes into existence the moment a defensive player with the ball attempts to tag a runner. Then, and only then, does a base path appear (so to speak), and then the base path is a straight line between the base runner and the base to which the runner is advancing or retreating. Additionally, once that base path is established, the runner cannot deviate from it to avoid the tag more than three feet to the left or right (roughly speaking, a step and a reach). If he does, you should call the runner out for leaving the base path.
In most cases this is pretty straightforward. It gets tricky, however, in a pickle. When you're following a runner in a pickle you need to pay very close attention because every time the defense tosses the ball and the runner reverses direction, he is establishing a new base path. If a pickle goes on more than about three or four throws, the base path can migrate pretty far from where it started. This is not an issue (even though someone in the stands will be hollering something like "he's out of the base path, blue!"). The guy in the stands, as usual, doesn't know what he's talking about. There is, theoretically, no limit to where a pickle can go, so long as the runner does not deviate from his base path by more than three feet.
A final note, so long as we're talking about pickles. You must also watch closely for obstruction when you're following a pickle. If the runner contacts the fielder who has the ball, he's out, of course (assuming the tag is on). However, if the runner reverses direction, say, and runs into a fielder who no longer has the ball, you have Type 1 (Type A) obstruction. Don't forget to watch for this.
We have an entire article on the subject of base runners touched by a fair batted ball. In most cases this is offensive interference and the runner is out, the ball is dead, and other runner must return to their last acquried base. But not always! Interference is a big subject and there are several quirks and wrinkles, so you sould read all five of our articles on the subject, starting with Offensive Interference. Incidentally, when a runner touched by a thrown ball, there is no infraction – live ball, play on.
If a base runner is touched by a called infield fly while the runner is in contact with a base, the runner is not out. The batter is out, of course, on the infield fly call. Contrast this with a batted ball that is not an infield fly; even if in contact with the base the runner is out for interference if hit by a batted ball. In other words, a batter is out for interference if he is touched by a fly ball, even if he is in contact with a base, except when it's a called infield fly.
If the base runner is touched by an infield fly while not in contact with a base, however, this is interference and the base runner is out (and the batter out on the infield fly). The ball is dead on the interference.
A base runner who has been put out, struck out, or who has just scored, has an obligation to not impede the defense when making a play on other base runners. Doing so is interference, dead ball, and the runner on whom the play was being made is called out. For it to be interference, however, the offender must actually impede the defense. If a runner simply continues to advance after being put out, this in itself is not necessarily interference.
Rule 6.01(a)(6) deals with actions by the base runner in illegally breaking up a double play, while 6.01(a)(6) deals with the batter-runner breaking up a double-play illegally.
Breaking up a double play illegally under 6.01(a)(6) usually means the offending runner has slid into second illegally with the intention of disrupting the fielder's attempt to complete the double play. This get a bit tricky because the matter of a legal slide vs. an illegal slide is one of those matters that very somewhat from league to league. For example, high school (NHSF) rules say that sliding through/beyond the bag is an illegal slide, whereas most other codes do not. You must be clear about the rule under which you are working.
In my view, the best written rule on the illegal slide and interference resulting from it is the NCAA rule – Rule 8-4: Force-Play-Slide Rule. Compare the high school (NFHS) Rules 2-32-1, 2, which is also a good guide. The two are quite similar, but there are some important differences. We've already mentioned sliding beyond the bag, which is illegal in high school (if you disrupt the play, that is). There's also the matter of the pop-up slide, which is acceptable in NCAA, but not in high school.
This issue should always come up at your plate meeting. In most cases (non-NCAA and non-NFHS), you play what is basically a mash-up of the NCAA and NFHS rule:
The rule on the intentionally dropped fly ball dovetails with the infield fly rule. We'll explain. But first, let's be clear why a fielder would intentionally drop a fly ball or line drive. Simply put, it's to get a cheap double-play on base runners who are holding back because of the fly ball in or near the infield fly, when catching the ball gets you just one out.
As with the infield fly, 5.09(a)(12) is only in force when there are fewer than two outs. Unlike the infield fly, however, the rule can be applied any time there is a force out potential at any base.
It is entirely a judgment call as to whether a ball was intentionally dropped. If you do judge the violation, you must call an immediate dead ball, call the batter out, and base runners return to the original bases without liability to be put out.
Caveat: Note that this rule only applied to an intentionally "dropped" ball. For a ball to be dropped, it must first be touched. If a fielder allows a ball to drop untouched, there is no infraction and the batter is not out (unless, of course, the infield fly rule applies).
Courtesy runner rules are speed-up rules intended to help quicken the game. They typically allow enter a courtesy runner (not a substitute) for the pitcher or catcher, either at any time these players are on base, or when there are two outs. The rules vary considerably from league to league – particulary in club, select, and travel ball leagues.
OBR does not allow courtesy runners; however, this is one of the OBR rules that youth leagues typically override. Most of the Pony, Koufax, and other select leagues provide for courtesy runners.
Little League does not allow courtesy runners. High school (NFHS), on the other hand, does alow courtesy runners and devotes a special section in the rule book to them.
NCAA does not allow courtesy runners, although NAIA does. The NAIA rules for courtesy runners can be found in "Appendix F - Rule Modifications" in the NAIA Baseball Coaches Manual.
Unless you're working exclusively NCAA, Little League, NFHS, or straight-up OBR, it is very important that you cover this issue at your pregame meeting and clarify the courtesy runner rules for your league.
In our article The Batter, we devote an entire section to listing the ways in which a batter becomes a runner, along with discussions and clarifications.
This is the rule that dispells the age old myth (and sandlot rule) that on a close play at first base the tie goes to the runner. In fact, the runner acquires the right to an unoccupied base "when that runner touches it before he is out." In other words, the runner must beat the throw (or tag). Rule 7.01 adds, in its Comment, that after acquiring a base, and once the pitcher is on the mound, the runner may not return to a "previously occupied base."
When preceeding runners are awarded bases, following runners advance if forced. The concept is pretty basic (obvious, really), but let's list the ways that a runner is forced to advance without liability to be put out. This differs from provisions in which all runners advance, whether forced or not (e.g., on a balk, ball thrown out of play, etc.); see Awarding Bases for a complete rundown on these.
If a base runner miss a base while advancing or retreating, he's normally allowed to backtrack and touch the base. But not always. There are conditions under which the base runner loses the right to return.
Let's start with 5.09(b-12). This concerns the case of a runner who slides into home but fails to touch home plate. If the base runner then starts heading for the dugout or otherwise makes no attempt to return to touch home plate, the fielder (normally the catcher) does not need to chase the runner down and tag him. He can, with possession of the ball, simply touch home and appeal to the umpire, who then rules safe or out.
Why, you may ask, is abandonment at home treated in this special way? Because otherwise the offense would have an unfair advantage. The base runner who failed to touch home could force the catcher to chase him, wasting time while other base runners are advancing. He's going to end up being put out, of course, but he could allow a tremendous advantage for runners on base. As you can see, this issue dovetails very closely with the matter of abandonment, which we discuss in the next section.
Rule 5.09(c)(2) deals with appealing that a runner missed a base, but the interesting part is the the Approved Ruling. Here we learn that a base runner cannot return to touch a base that he's missed after a following runner has scored. This would typically happen at home plate with successive runners scoring. If the first one missed home, once the second runner scores the first runner is SOL. He's dead meat … if the defense appeals. If they don't, then both runs score.
Rule 5.09(d) deals with another narrow scenario. In this one, you have multiple runners scoring, but one of them misses home plate. Depending on the situation, your rulings differ:
We've touched on abandonment in some of the preceding sections, but let's put it all together in one place. Abandonment can happen in several ways. Let's touch on each of the rules.
Rule 5.09(b)(2) deals with abandonment on the bases. A batter-runner runs through first on a close play and, for whatever reason, believe he's been put out and begins heading for the dugout. This is a judgment call and requires the umpire to judge "the act of the runner to be considered abandoning his efforts to run the bases." It's hard for me to imagine his teammates and base coach wouldn't be screaming at him to get back on the base well ahead of the time required to judge abandonment, but I suppose it could happen.
This could happen at other bases, too, is a player believes he's been put out and abandons the bases. If it does happen and you call a runner out for abandonment, do not kill the ball. You get the out but the ball stays live and action continues. This is important because, unless there were two outs at the time, other runners could score.
Another important scenario that comes into play is in a walk-off home run. On a walk-off home run the batter-runner and all preceding runners must touch all of the bases and home plate. If a preceding runner incorrectly believes he does not need to run the bases and peels off toward the dugout, he can be called out for abandonment. If his is the third out, the home run will not count.
Rules 5.09(b)(12, 13) deal with the situation where the batter-runner runs through first, then fails to return directly to the base. He must return directly or he can be tagged out (or the base tagged on the appeal).
Important: 5.09(b)(2) Comment tells us that a runner called out at first base for abandonment (after having arrived safely) "has reached first base" for the purpose of scoring runs with respect to 5.08(a) Exception. If the abandonment call is the third out, judge runs scored as though it were a time play.
Rules 5.09(c)(3, 4) reiterate issues that we've already discussed: Overrunning first base and returning immediately in 5.09(c)(3), and the matter of appealing when a runner fails to touch home plate – 5.09(c)(4).
I've placed this item following the section on abandonment because the two are close cousins. This scenario, which you'll typically see in only lower levels of ball (the older guys usually know better), in some respects amounts to abandoning an effort to advance, albeit in a very specific situation. I'll explain.
The specific situation we're talking about is the walk-off. That is, it's the last half of the final inning (either regualation game or extra innings) where there is the potential for a game-ending hit. Let's say, for example, that you have a tie game, home team at bat, fewer that two outs, and a runnr on third. Any hit (almost any hit) wins the game. Okay, so the batter gets the hit – a little blooper over the shortstop's head, let's say. Game over, right? WRONG.
The game is not over until two things happen: (1) The batter-runner must touch first base, and (2) the runner on third must touch home. To be clear, the winning run must actually reach and touch home plate, and the batter-runner must complete his at-bat by acquiring first base. In the case of a walk-off home run, the batter-runner must round the bases and score.
Here's what happens if these two requirements are not met:
We devote an entire article to this issue, covering both base runners and batters. See Awarding Bases.
There is really not very much to cover on this one. When a balk occurs, all runners advance one base. For an extended discussion of balks, see the article Balks and Illegal Pitches.
We devote an entire article to Batting Out of Order; however, there is one wrinkle that is worth discussing here.
We learn in 6.03(b) that when rectifying a batting out of order infraction (in the case where the improper batter has completed his at-bat and there has not yet been a pitch to the next batter), that among other things the umpire nullifies any action that occurred as a result of the improper at-bat. This includes returning base runners to their time-of-pitch base.
However, there is an exception to this. If a runner advances while the improper batter is at bat due to a stolen base, and illegal pitch (i.e., balk), wild pitch or passed ball, then that base runner's advance is legal and supercedes the penalty for batting out of order. In other words, that runner stays where he is.
Contrary to some baseball myths, two runners on a base is not automatically an out. That said, only one of the runners is entitled to and protected on the base, and the other is out if tagged. So which one is out?
Except for two exceptions, which I'll talk about in a moment, the trailing (following) runner is out when tagged. This is based on the principle that a runner is entitled to the protection of a base (that is, he "owns" the base) until he acquires a following base. Until then, he can reverse direction and return to the preceding base and once there he's legally entitled to it, even if a following runner has arrived there too.
So what are the exceptions? Well, the most common exception is on a force situation. If runners are forced to advance, then they are legally entitled to that base. So a preceding runner, who is also forced, is not protected at the base from which he is forced.
The other exception is quite rare. In fact, I've never seen it. However, let's return to the principle we discussed earlier – that a runner "owns" a base until he legally acquires the next base. At that point the previous base is up for grabs. So if a following runner acquires that base after the leading runner has acquired the next base, then the leading runner cannot reverse direction and return to the base he left (which is now occupied by a following runner) and still be protected there. He's out if tagged.
This is really a continuation of our discussion about interference (in the article Offensive Interference). And that said, it's a pretty quirky scenario and pretty had to picture, but rest assured there's a rule for it.
If two runners are hit by the same batted ball, only one runner, the first runner hit, is out for interference. This is because interference is an immediate dead ball, so when the first runner is hit the ball is dead and once the ball is dead there can be no put-outs. The second runner must return to his last acquired base.
A base runner is out if he passes a preceding runner. He must pass him entirely to be in violation. There are two scenarios in which this is typically seen – one of the stupid, one of them not.
The stupid scenario is the case of batter hitting a home run (a walk-off, let's say), and in trotting around the bases triumphantly, a preceding base runner hangs back to high-five him and accompany him home. Stupid move. The batter-runner is fairly likely to pass the preceding runner at some point during this dance around the bases, and there's going to be some woeful complaints when he's called out.
The more common scenario is this: A couple of runners on base and you have a sharp hit to the gap so there's a great opportunity to score multiple runs and everyone is running as hard as they can. But one runner, in his haste, misses a base, realizes it, and reverses quickly to touch it. Oops. The following runner is right on his tail and when he reverses the following runner passes him.
When a runner passes a preceding runner, call the runner out. However, the ball is not dead (unless this is the third out), so don't kill the play. Let action continue. Note that if you are in a walk-off situation, the out you call does not affect the scoring of other runners, unless this is the third out. If it's the third out, then treat it like a time play; that is, any runner who touched home before you called the out, their run counts.
The "flying start" is a move wherein the base runner takes a position behind the base when there is a deep fly ball so he can take a running start and time his touch of the bag with the catch of the ball. This would give him a tremendous advantage in tagging up and advancing. But the move is illegal and the runner may be called out on appeal as if he failed to tag up.
We've now reached my favorite of all of the rules of baseball. And I wonder if this has ever been called. Let's just read it together: "Any runner is out when …"
Now, let's be clear that we're not talking about a runner reversing direction to touch a missed base, to tag up, or to return to a base on a caught fly ball. What we're talking about is … well, making a travesty of the game. If any of you ever call this, please click the feedback link and let me know about it. I'd love to hear the details.