Odor Misses Home, Kim Scores, Odor Out on Appeal for Trying to Return to Touch a Missed Base

Padres baserunner Rougned Odor's 4th inning run against Atlanta was wiped off the board after a successful Braves appeal that Odor failed to touch home plate. HP Umpire Chad Fairchild declared Odor out even though replays show Odor returning to touch home plate. Why is that and how does Odor's teammate Ha-Seong Kim factor in?

With two on (R2, R3) and one out, Padres batter Trent Grisham hit a ground ball to Braves first baseman Matt Olson, who threw to catcher Travis d'Arnaud as Padres baserunner R3 Odor attempted to score from third base. Olson's throw evaded d'Arnaud's catcher's mitt and bounced to the backstop as Odor scampered past home plate and trailing baserunner R2 Kim jogged into score an apparent second run, after which R1 Odor, who had missed touching home plate his first time by, returned to touch the missed base.

After the play, however, Braves manager Brian Snitker spoke with HP Umpire Chad Fairchild and when the ball was put back into play, Braves pitcher Charlie Morton stepped off the rubber and threw to catcher d'Arnaud, who stepped on home plate and, after discussion, Umpire Fairchild ruled Odor out for failing to touch home plate.

Even though replays clearly indicate that Odor did return to touch home plate, he did so illegally.

Official Baseball Rule 5.09(c)(2) regarding appeal plays explains why Odor was out: "Any runner shall be called out on appeal when, with the ball in play, while advancing or returning to a base, they fail to touch each base in order before they, or a missed base, are tagged" while OBR 5.09(c)(2)'s Approved Ruling contains the answer key for this particular play: "No runner may return to touch a missed base after a following runner has scored."

Thus, Odor was called out because he returned to touch the missed base after following runner Kim had already scored, which is not allowed. This might sound akin to runners passing, but these two rules are distinct and different. For one, the Odor missed base play is an appeal play: Odor is not out unless the defense properly appeals (live ball appeals only in professional ball, etc.) while if this was a runners passing situation, Odor would have been declared out immediately upon the infraction (e.g., not an appeal play).

Video as follows:

Teachable - How to Officiate a Runners Passing Play

When 1B Umpire Dan Bellino called Reds batter-runner Nick Senzel out, he invoked Official Baseball Rule 5.09(b)(9), which states that "any runner is out when they pass a preceding runner before such runner is out."

This infrequent play generally occurs on fly balls to the outfield when less than two are out as the existing baserunners try to anticipate whether the fly will be caught—in which case they may be forced to advance—or whether the ball will land safely—in which case they may appreciate a head start while running the bases.

In other situations, a runner beginning play on first base (R1) might be attempting to steal as part of a hit-and-run play, and suddenly find themselves forced to retreat as the batted ball to the outfield may or may not be caught by an outfielder.

For this play, Cincinnati batter Senzel's fly ball was not caught by Baltimore, but baserunner R1 Kyle Farmer, who had advanced to second base, retreats back toward first base, mistakenly believing the ball had been caught, as Senzel stands between first and second base.

The runners pass each-other—by rule, no matter which runner is primarily responsible for the passing, the trailing runner is always out when passing occurs and thus said to be the "passing" violator regardless of which offensive player erred—and Bellino properly enforced OBR 5.09(b)(9) by keeping the ball in play and signaling the back runner, BR Senzel, out for passing the preceding runner, R1 Farmer.

Note that the defense does not need to tag the violative runner (Senzel) for an out to be called. The out is immediate and automatic upon the passing occurring, and Bellino properly called the out before the Orioles tagged Senzel. This would be important for time play purposes if there had been two out and another runner attempting to score.

Video as follows:

Passing Runners - When a Home Run Becomes a Single

In this passing runners Teachable Moment, tmac reviews 1B Umpire Sam Holbrook's out call on batter-runner Adam Duvall after an apparent home run when Braves baserunner R1 Austin Riley, by jogging back toward first base, enabled Duvall to inadvertently pass a preceding runner, comparing this play to Robin Ventura's grand slam single from Game 5 of the 1999 Braves-Mets National League Championship Series when Ventura was declared out for passing preceding New York runner Todd Pratt.

The relevant rule itself is Official Baseball Rule 5.09(b)(9), which states that a runner is out when "they pass a preceding runner before such runner is out." The rule's comment goes on to clarify that "A runner may be deemed to have passed a preceding (i.e., lead) runner based on their actions or the actions of a preceding runner."

The rule applies during any live ball period as well as any dead ball period in which ordinary base-running rules and responsibilities are in effect (e.g., during a home run or "ground rule" double base award, as opposed to during a foul ball, when the rule does not apply because no bases are being run and no runners are advancing once the ball is declared foul).

Because Duvall passed Riley after touching first base but before reaching second, Duvall is credited with a single. Had there been two outs when Duvall hit the not-quite-a-HR, the passing call for the inning's third out would result in a time play for any potential runs scoring.

For more information, refer to our previous series on passing runners.

Video as follows:

No, Giants, A Retired Batter Can't Also Pass A Runner

The Pittsburgh Pirates had to wait a few extra minutes to fully enjoy a walk-off win against San Francisco Friday night after Giants manager Gabe Kapler questioned HP Umpire Tom Hallion about Pittsburgh's baserunning during batter Gregory Polanco's game-ending sacrifice fly that scored Adam Frazier from third base.

Play: With one out and the bases loaded of a tied game in the bottom of the 11th inning, Pirates batter Polanco hit a fly ball to center fielder Austin Slater, scoring baserunner R3 Frazier to break the tie and award Pittsburgh a 3-2 victory.

Kapler Doth Protest: Although at first glance, Kapler's complaint might appear to have been a question of a runner leaving a base too early, this question is discarded for San Francisco never appealed on any of Pittsburgh's runners.

The second possibility, according to at least one of the broadcast crews, was that no runner other than Frazier advanced to and touched their next base...but with a sacrifice fly, no runner was forced to advance.

This leaves us with what Kapler actually argued: that batter-runner Polanco passed teammate and baserunner R1 Caleb Baragar at first base and, thus, the inning should have ended on a double play with no run scoring.

Rule: Official Baseball Rule 5.09(b)(9) states that a runner is out when they pass a "preceding runner before such runner is out." Kapler's argument was that because Polanco passed Baragar before Baragar was out, this is an out and, combined with the caught fly ball, should have been an inning-ending double play.

Double Jeopardy: Not so fast, Giants. Recall that batter-runner Polanco hit a sacrifice fly and was put out by outfielder Slater's catch. Accordingly, Polanco cannot be out for more than one reason: he might be out on the fly ball to the outfield or on the runners passing situation, but not both. Once Polanco is declared out for one of those reasons, he cannot be declared out for the other.

Although situations do exist where a retired runner's actions may cause the runner's teammate to be declared out for the retired runner's actions (e.g., interference), no individual player may be declared out more than once during any individual play.

The Other Runners: Assume that trailing batter-runner Polanco was declared out for passing lead runner Baragar prior to Slater catching the fly ball. Does this absolve all other runners of their tag-up (retouch) responsibilities on the eventually-caught fly ball (since the batter who hit it was already declared out for another reason)? Answer: No. OBR 5.09(c)(1) states that a runner is out on appeal when "After a fly ball is caught, they fail to retouch their original base before they or their original base is tagged."

In sum, batter-runner Polanco is out on the caught fly ball (or [but not and] for passing preceding runner Baragar) for the second out of the inning; Polanco cannot be declared out a second time. All runners appeared to properly tag up on the caught fly ball with Frazier scoring the Pirates' winning run. Game over, score the run.

A retired player cannot be declared out a second time. | Video as follows:

Royals' Runners Passing Replay Stands on Tag Attempt

Royals Manager Mike Matheny unsuccessfully challenged 3B Umpire David Rackley's runners passing no-call Friday night in Kansas City as catcher Salvador Perez ran White Sox runner R3 Zack Collins back to and past third base, into left field, as trail runner R2 Billy Hamilton stood on third base, in rare case where being "too good" at one's job might have cost Kansas City an extra out.

The Play: With one out and two on (R2, R3) in the 7th inning of a 3-0 game, Chicago batter Nick Madrigal hit a ground ball to Kansas City shortstop Nick Madrigal, who threw to catcher Perez as White Sox R3 Collins ran toward home plate and R2 Hamilton advanced to third base. Perez ran Collins back to third base where Hamilton was standing and as Perez attempted to tag Collins, Collins ran past the base and up the left field line.

The Call: 3B Umpire David Rackley signaled Hamilton safe at third base after a collision with Perez and then signaled Collins out for abandoning his effort to run the bases.

The Challenge: Matheny challenged Rackley's runner's passing no-call, asserting that Hamilton (the trailing runner) should have been declared out when Collins (the lead/preceding runner) ran past third base and into left field.

The Rule: A very similar play occurred during Spring Training 2021 when 3B Umpire Sam Holbrook called Tampa Bay's Nathan Lukes (trailing runner) out for passing Vidal Brujan (lead runner). Official Baseball Rule 5.09(b)(9) states that a runner is out when they pass a preceding runner: "A runner may be deemed to have passed a preceding (i.e., lead) runner based on their actions or the actions of a preceding runner." For abandonment, a runner is out pursuant to OBR 5.09(b)(2) when the runner leaves the base path, "obviously abandoning their effort to touch the next base." Finally, though this did not occur here, if two runners are in contact with a base at the same time, OBR 5.06(a)(2) states, "the following runner shall be out when tagged and the preceding runner is entitled to the base, unless [it is a force play and the trailing runner is forced to advance; in this situation, the preceding/lead runner is out when tagged]."

Related Post: Runners Passing Nearly Turns to Lead Abandonment (3/9/21).

As we previously discussed, the abandonment rule means that it is simply not possible for a lead runner in this situation to be out for abandonment until said runner returns to and runs past the base, thus causing a passing situation to occur. In other words, the runner must demonstrate their abandonment through actions, such as running up the left field line well past third base and the only way to do that is to cause the trail runner to be guilty of passing the lead runner prior to the abandonment.

The Replay Review & Result: Thus, the CWS-KC play had all the makings of a double play for passing and abandonment, if not for one crucial piece: catcher Salvy Perez's tag attempt. If Perez was able to tag Collins prior to Collins returning to third base, Collins would be out at the moment of the tag and thus Hamilton would be unable to pass him. Because the Replay Official could not definitively determine whether a tag actually occurred, Rackley's call (abandonment, no passing) stood and Hamilton remained at third base.

This is one situation where Perez's hustle might have actually hurt his team; if Perez didn't attempt to tag Collins, all else equal, Hamilton would have been out for passing followed shortly by Collins being declared out for abandonment: an inning-ending double play.

Video as follows:

Runners Passing Costs Dodgers Run on Opening Day

It took less than three innings for a baseball rules question to find its way to the UEFL inbox and umpire decision quandary takes us to Dodgers-Rockies game in Colorado with Cody Bellinger and Justin Turner combining for a runners passing play, depriving Los Angeles of an early run at Coors Field.

With one out and one on (R1) in the top of the 3rd inning, Dodgers batter Bellinger hits a fly ball to deep left field, off Rockies left fielder Raimel Tapia's glove, and over the wall for an apparent home run.

LA baserunner R1 Turner, however, stops watching the ball as Tapia attempts to catch it, and doesn't see the ball fall over the wall, similarly ignoring both the umpires' home run mechanic and Bellinger's own instruction that the ball cleared the outfield fence.

As a result of Turner's This is Not an April Fools' Joke play, the two Dodgers runners end up passing each other on the base path between first and second base, and the umpires invoke Official Baseball Rule 5.09(b)(9) ("Any runner is out when he passes a preceding runner before such runner is out") to declare Bellinger out, while allowing Turner to complete his free passage to home plate.

The official scoring on this play is an RBI single for Bellinger and the loss of a potential run for Los Angeles. The Rockies subsequently took a 2-1 lead shortly thereafter, and ultimately won the game.

For more detailed analysis and discussion on prior runners passing plays (including why the rule states that the trailing runner is responsible for passing, even if the lead runner was physically more "at fault"), see the following related label. Runners passing featured prominently in our 2020-2021 offseason discussion, including during a Boston-Tampa Bay Spring Training game on March 9, TMU college game on February 12 (also during a home run), and travel ball game we discussed on February 5.

Related Label: Passing Runners.

Wrap: Los Angeles Dodgers vs. Colorado Rockies, 4/1/21 | Video as follows:

Runners Passing Nearly Turns to Lead Abandonment

A runners passing situation during Tuesday's Spring Training game between the Red Sox and Rays in Florida led umpires to declare Tampa Bay baserunner Nathan Lukes out for passing Vidal Brujan, who nearly abandoned his running of the bases and could have been called for a second out on the play. What happened?

Play: With one out and two on (R2 Lukes, R3 Brujan), Rays batter Brett Sullivan took a called fourth ball, drawing a walk. R3 Brujan, who apparently thought the bases were loaded, started jogging toward home plate as Boston alertly trapped Brujan in a rundown, with R2 Lukes hustling to third base. As Red Sox pitcher John Schreiber ran R3 Brujan back to third base, a runners passing situation occurred, identified by 3B Umpire and Crew Chief Sam Holbrook, who declared R2 Lukes out. After confusion, during which Brujan ran back to and entered the Tampa Bay dugout, Brujan was returned to third base, Lukes declared out, and batter-runner Sullivan placed at second base.

Rules: Runners passing occurs when a trailing runner fully passes a preceding runner. According to Official Baseball Rule 5.09(b)(9), which states that a runner is out when "he passes a preceding runner before such runner is out," it doesn't exactly matter who physically passed whom; in all cases, it is the trail who is out: "A runner may be deemed to have passed a preceding (i.e., lead) runner based on his actions or the actions of a preceding runner."

As far as abandonment is concerned—seeing as Brujan clearly ran to and entered the Rays dugout—OBR 5.09(b)(2) states that a runner is out when the runner leaves the base path, "obviously abandoning his effort to touch the next base." The example play is as follows: "PLAY—Runner believing he is called out on a tag at first or third base starts for the dugout and progresses a reasonable distance still indicating by his actions that he is out, shall be declared out for abandoning the bases."

Analysis: So why wasn't this a double play? In the end, Brujan may have been saved by a combination of two factors: First, it's Spring Training and a certainly leniency exists in March that would not in, say, July. Second, 3B Umpire Holbrook appeared to call "Time" before declaring Lukes out for passing.

That "Time" call makes abandonment a little trickier, as during a dead ball situation, runners similarly have a bit more lenience before abandonment sets in. That said....Brujan did enter the dugout, and unless it was for the purposes of uniform repair, it would be reasonable to believe he did so because he had abandoned his base-running role, or, as OBR 5.09(b)(2) PLAY states, because Brujan believed he had been "called out."

Lessons Learned: First, even when players don't know the rules, umpires must maintain both knowledge and awareness. In this situation, R3 Brujan did not know his entitlement to third base, but U3 Holbrook did.

However, the second part of our lesson is patience. Keep the ball alive and in play unless all action has ceased or as otherwise prescribed by rule. For the purposes of this play, runners passing is a simple out declaration: it is not a reason to call "Time" while the ball is loose and other action is taking place. But if "Time" is going to be called, erroneously or otherwise, that moves the goalpost for other calls, such as abandonment: "Time" kills the play and certain events—such as runners advancing—simply cannot occur during a dead ball (unless part of a base award).

That said, an umpire is empowered by Rule 8.02(c) to place runners as if the reversed call had never been made, disregarding events that may have occurred after the call-to-be-reversed: "If the umpires consult after a play and change a call that had been made, then they have the authority to take all steps that they may deem necessary, in their discretion, to eliminate the results and consequences of the earlier call that they are reversing." In this case, abandonment occurred after the "Time" call and may have been reversed pursuant to OBR 8.02(c).

Wrap: Boston Red Sox vs. Tampa Bay Rays (Spring Training), 3/9/21 | Video as follows:

Real World Rules - Teachable Moment Passes to Life

Nary one week after our recent Tmac's Teachable Moment for Passing Runners in Anytown, USA, a similar grand slam caper turned into a real life UEFL Curse as TMU found itself guilty of a base-running infraction against Cumberland in Georgia.

Play: With two outs and the bases loaded (R1 Mikal Mascarello, R2 Andrew Johnston, R3 Josh Johnston), Truett McConnell University batter Ethan Roberts hit what appeared to be a home run. Replays indicate that, similar to our Teachable, one runner stopped short of touching home plate before a following runner continued jogging and did touch home plate. In this case, it was R3 who failed to touch home plate as R2 followed by touching home plate to complete his own baserunning journey.

Analysis: Cumberland University's box score indicates Josh Johnston, TMU's runner on third base, was called out on appeal for failing to touch a base, but this cannot possibly be accurate under the NCAA/college ruleset pursuant to Rule 8-6-b, which, just like professional baseball's OBR, requires the appeal be lodged while the ball is live or (in this case) has been put back into play.

Thus, we know it was not an appeal. Here's what else it could be:

Runners Passing (Teachable): Under OBR 5.09(b)(9), a runner is out when—"he passes a preceding runner before such runner is out," so R1 is out for passing R2 even though it appears R2 caused the passing to occur ("A runner may be deemed to have passed a preceding (i.e., lead) runner based on his actions or the actions of a preceding runner"). There is no greater example of a runner passing another runner than when a lead runner fails to reach a base, only for a following runner to then arrive at and touch that same base.

Abandonment: Home plate provides a unique circumstance for abandonment since a runner is not obliged to stay on home plate, as they would at another base such as second or third. In this instance, a runner may be called for abandonment at home plate when the runner clearly starts for the dugout and the catcher would be required to chase the offensive player during a live ball.

Because the Cumberland-TMU play involved a dead ball, this portion of abandonment's interpretation does not apply.

Instead, we consult the MLB Umpire Manual (similar interpretation for NCAA), which states that an infraction has occurred (all else equal [e.g., assuming no runners other than R3 were entitled to home plate, as would be the case on a dead ball, one-base award]) only when R3 enters the dugout without having completed his base-running responsibility.

With no other runners, R3, by rule, still has the opportunity to correct his baserunning error prior to the first of either A) entering the dugout or B) the ball being put back into play, upon which the defense could appeal the missed base.

Naturally, in this situation, we know the circumstance of runners passing has occurred by virtue of R2 clearly touching home plate while R3's attempt to touch home plate, as it were, came up noticeably short. Thus, R3 had not yet abandoned his base-running responsibility at the time of R2 touching home plate, but R2's touch of home plate did constitute tangible confirmation that R2 had passed R3 on the bases; thus, R2 is out for passing and R3's run shall not count because in order for R2 to have passed R3, we must presume that R3 had not yet scored (e.g., R3 never made it to home plate). Thus, there is no fourth out appeal situation to be had.

In short, R3 is not out for abandonment solely because R2 passed him first, and R2's out was the final out of the inning. Because R2 passed R3 prior to R3 either entering the dugout or returning to complete the final (short) leg of his running of the bases, the third out of the inning caused by the runner passing precedes any potential abandonment or missed base touch situation.

Video as follows:

Teachable - Passing Runners in Anytown, USA

In this Teachable Moment, tmac reviews a travel baseball play that can happen anywhere. Passing Runners in Anytown, USA features a grand slam wherein the excited baserunners start celebrating and swarm their batter-runner before three of the four runners touches home plate. What's an umpire to do: is there an appeal to be made or are all outs automatic in this situation?

First and foremost, we note that the rules are substantially similar across all levels of baseball: the largest difference is that, in the case of an appeal, NFHS (high school) allows for dead ball appeals whereas at the upper levels NCAA/OBR, the ball must be live during an appeal.

That said, we see that during this home run, preceding/lead runner R3 runs to and touches home plate: his run will count regardless of this play's outcome, as the batter-runner will run to and touch first base.

R2, however, stops short of home plate and waits to celebrate with his teammates, inadvertently causing R1 to pass him. Under OBR 5.09(b)(9), a runner is out when—"he passes a preceding runner before such runner is out," so R1 is out for passing R2 even though it appears R2 caused the passing to occur ("A runner may be deemed to have passed a preceding (i.e., lead) runner based on his actions or the actions of a preceding runner").

Next, the batter-runner passes R1 in a similar fashion, so BR is also out for passing a preceding runner. If there was one out to begin play (or two outs), the inning would already be over at this point: R3's run counts and BR is credited with a one-RBI hit.

If there were zero outs to begin play, however, that leaves R2 as the only baserunner on the field who hasn't yet scored and who hasn't yet been declared out. If R2 continues to the dugout without touching home plate (as is the case here), his run shall count and play continues with two outs. The defense, naturally, can then exercise Official Baseball Rule 5.09(c)(2) [or lower level equivalent] and appeal R2's failure to touch home plate to both nullify the run and pick up an inning-ending third out ("he fails to touch each base in order before he, or a missed base, is tagged"). Note that once R2 returns to the dugout, it is too late for him to return to correct his triple play-inducing error.

Video as follows:

Repeat - Abreu Out for Passing Anderson During HR

Every once in awhile, an odd play occurs in MLB that we've seen before. Friday night, White Sox first baseman Jose Abreu passed baserunner Tim Anderson during a home run, resulting in an RBI single—a passing Replay Review scenario we wrote extensively about during a 2016 Case Play in Chicago.

Friday, April 26, 2019: With R1 and R3 with one out, White Sox batter Jose Abreu hits a home run. Baserunner R1 Tim Anderson, afraid the high fly ball may be caught in the outfield, retreats to tag up at first base, causing Abreu to momentarily pass Anderson on the bases. Originally no-called by 1B Umpire Tony Randazzo, the ruling was overturned via Replay Review, upon which Abreu was declared out for having passed Anderson, granting Detroit an out and saving the Tigers one run.

After the game, White Sox Manager Rick Renteria said, "That's the first time I've ever seen it." Too bad Renteria wasn't the White Sox skipper before 2017.

Case Play 2016-11: Runners Passing.

September 10, 2016: Three years earlier, also in Chicago, with one out and one on (R1), White Sox batter Tyler Saladino hit a fly ball to left-center field, where the ball eluded Royals outfielder Jarrod Dyson, bouncing on the warning track and out of play for a two-base award. Similarly, Chicago baserunner R1 Leury Garcia retreated toward first base during the fly ball, causing Saladino to pass him on the bases.

The difference here is that Royals Manager Ned Yost challenged that batter-runner Saladino had passed baserunner Garcia prior to the ball going out of play. Though Saladino did pass Garcia, he did not pass Garcia prior to the ball going out of play. For this reason, the passing no-call was confirmed.

A prior passing scenario during a HR.

Analysis: It doesn't matter if the ball is dead or not, but it does matter how the manager phrases his challenge. MLB Replay Review regulations require the challenging manager to specify exactly what aspect of the play he is challenging.

As we extensively discussed in 2016, Rule 5.06(b)(4)(l) Comment states that runners are not relieved of baserunning responsibilities during dead balls, and OBR 5.09(b)(9) holds that a runner is out when passing a preceding runner not yet retired. The passed runner, naturally, is unaffected by his teammate's illegal action.

Passing can occur during a dead ball, but with replay, the manager must request review of the entire sequence, not just that which concerns a live ball.
Related Post: Case Play 2016-11 - Time to Pass a Runner [Solved] (9/16/16).

After 2016, the MLB Umpire Manual for 2017 wrote, concerning runners passing runners, "Runners passing are not protected from being called out in accordance with Rule 5.09(b)(9) by time being called or other dead ball situation (i.e ground-rule double, home run, etc.) if they are still in the act of running the bases."

Abreu passes Anderson at first base.

Conclusion: What is especially noteworthy, again, is how the 2016 challenge was phrased vs the 2019 version. In its result summary, MLB in 2016 wrote, "After review, the ruling on the field is CONFIRMED. The runner was not passed by another runner prior to the ball going out of play." Friday night, MLB wrote, "After review, the call on the field is OVERTURNED. There was passing runners."

In sum, managers, don't be too specific with the challenges. Yes, that could create headaches for an umpire trying to figure out what is being challenged, but by getting too cute, a technicality could mean the difference between an out and a run.

This is what we wrote in 2016:

NFHS vs NCAA vs OBR: All codes agree, passing can occur during a dead ball. However, only NFHS does not treat runner passing during a dead ball as a time play. PLAY: With two outs and two on, B1 hits a home run. After R3 scores, B1 passes R1 on the bases. Undeterred, R1 completes his HR trot and touches home plate. RULING: In NFHS, R3 & R1's runs both count. In NCAA & OBR, only R3's run counts due to the timing of the third out. NOTE: If the bases are loaded with two outs and B1 walks on a 3-2 pitch, after which R1 passes R2, then R3's run shall count whether or not he touched home plate prior to the third out, since he was forced home.

Video as follows:

Replay Rewind - Arizona's Lost HR & CIN's Bunt for Two

Welcome to Replay Rewind, a look back at some notable video reviews in baseball. In this inaugural edition, Arizona loses a home run due to a base-running blunder and Cincinnati earns a two-base bunt.

Marrero briefly runs past the entirety of Avila.

R-111 (Passing Runners; Overturned): Saturday night at Dodger Stadium, Diamondbacks batter Deven Marrero blasted Dodgers starter Rich Hill's 75th pitch of the ballgame over the left-center field wall for a three-run home run, scoring runners from first and second base. With baserunner R1 Alex Avila retreating toward first base for a potential tag-up play with one out as batter-runner Marrero rounded the bag, Dodgers Manager Dave Roberts elected to challenge the umpires' ruling that Marrero did not pass Avila.

Replay HQ cited the accompanying image, captured from the center field camera, as its Definitive Angle in opting to overturn the umpires' ruling that the BR Marrero did not pass R1 Avila. Thus, Marrero was declared out and his run nullified, for a two-RBI single. No matter, Arizona still won the game in blowout fashion.

Gibson sees the ball, but not the baserunners.

What's odd about this play is Arizona broadcaster Steve Berthiume's observation that 2B Umpire Brian Gorman (and not the first base umpire) signaled the BR/R1 interaction as legal, that 1B Umpire Tripp Gibson appeared to be the only umpire to significantly move during this play (3B Umpire Dan Iassogna appeared to have never left the infield dirt), and that no umpire saw the interaction around first base (replays indicate Gibson, for instance, was looking in the opposite direction as Marrero rounded first base).

In the end, R-111 reads "Passing, 73 Gibson, R-QOCN."

See the following Case Play for more about the rule regarding a trailing runner passing a predecessor.
Related Post: Case Play 2016-11 - Time to Pass a Runner [Solved] (9/16/16).

A poor throw leads to a boundary replay.

R-127 (In Play/Out of Play; Overturned): Sunday in Cincinnati, Reds batter Tucker Barnhart bunted to Cardinals third baseman Greg Garcia, who threw to first baseman Jose Martinez as Barnhart arrived at first base. Garcia's throw was into the batter-runner, bounced off Barnhart, and caromed toward the end of the first-base dugout. Replays indicate BR Barnhart prematurely exited the 45-foot runner's lane, and was on the grass when he was struck by the throw, appearing to block first baseman Martinez from his attempted catch; however, HP Umpire Alan Porter declined to rule interference because Garcia's throw was of poor quality. As the Wendelstedt manual would put it, Garcia's throw could not reasonably retire Barnhart, and for that reason, runner's lane interference was not called.

With RLI out of the picture, offensive manager Bryan Price challenged HP Umpire Porter's ruling that the ball was in play. This is a difficult get for the plate umpire if for no other reason than Porter was on the foul line ruling on Barnart's legality at the time of the potential stadium boundary issue. The Replay Official thus overturned Porter based on the finding that the ball hit an object inside the camera well before bounding back onto the playing field; RLI, obviously, is not reviewable.

Mike Scioscia tried protesting a game based on an RLI no-call in 2016; naturally, MLB denied it.
Related Post: Angels Protest Cuzzi RLI No-Call in Kansas City [Denied] (7/27/16).

See the following analyses regarding batter-runner positioning and potential RLI interference.
Related Post: Running Lane Interference and Advancing to 1st Base (9/6/15).
Related Post: Runner's Lane Interference Plagues Chicago's Heyward (5/24/17).

Videos as follows:

O's Lodge Protest Over Runners Passing Rule Application

Baltimore filed the first protest of the 2018 season Friday night after umpires declined to rule a double play on an odd rundown play during the Orioles-Yankees game that saw New York's lead runner, Giancarlo Stanton, retreat past third base and into left field as teammate and trail baserunner Gary Sanchez stood on the bag itself.

Meals, Kulpa, Hickox & May listen to Buck.

The Play: With one out and two on (R1, R3), Yankees batter Neil Walker hit a ground ball to Orioles pitcher Richard Bleier, who threw to third baseman Tim Beckham, to catcher Caleb Joseph, as baserunner R3 Stanton became trapped in a rundown between third and home. As Joseph ran Stanton back to third base, trail baserunner R1 Sanchez advanced to third, stepping onto the base with his right foot. With R1 Sanchez standing on third base—and even appearing to motion Stanton to stop—R3 Stanton continued his retreat, running straight through third base and up the left field line before veering into foul territory. Catcher Joseph first tagged Sanchez on third base as Stanton ran into left field before giving chase to, and tagging, Stanton as well.

U3 Kulpa observes F2 Joseph's chase of R3.

The Call: 3B Umpire Ron Kulpa gave no signal when catcher Joseph tagged R1 Sanchez while Sanchez was in contact with third base, and ruled R3 Stanton out when Joseph tagged him beyond the base in foul territory. Upon consultation with HP Umpire Ed Hickox, 1B Umpire and Crew Chief Jerry Meals, and 2B Umpire Ben May, Kulpa's ruling stood and Stanton was declared out, Sanchez "safe" at third base, and batter-runner Walker aboard safely at first.

Orioles Manager Buck Showalter filed a protest as a result of the ruling, but because Baltimore ultimately won the game in extra innings, Showalter's protest is effectively retracted and the result final. Had Baltimore lost, here's how Showalter's protest may have turned out...

MLB rules expert Marazzi is on the phone.

Analysis: The first bit of analysis is to applaud YES Network for calling Rich Marazzi and putting him on air. As Rich surmises, the proper outcome is a double play...but why is that? After all, when R1 Sanchez was tagged, 1) he was on the base and 2) Stanton was not.

What Went Right: Kulpa properly did not call R1 Sanchez out on the tag, and properly called R3 Stanton out on Joseph's tag, but this is where Quality of Correctness falls below the Mendoza line.

What Went Wrong: When R3 Stanton retreated past third base while R1 Sanchez was in contact with the base, he caused R1 Sanchez to commit the offense of passing a preceding runner. Thus, while Sanchez was not out as a result of Joseph's tag, he was out for passing Stanton, even though Stanton looked to have caused the situation (it is the trailing runner's responsibility not to pass a preceding runner). The relevant rule is OBR 5.09(b)(9): "Any runner is out when: He passes a preceding runner before such runner is out."

R1 is legal because R2 never retreated past 2B.

When it comes to a trailing runner passing a preceding (lead) runner between the bases, baseball generally requires one runner's body to physically pass the other's—for instance, runners are allowed to touch each other without consequence, for this is not considered "passing."

When it comes to a potential runners passing situation at the base, we consider an MLB Umpire Manual interpretation, which states, "A runner is considered to have passed a base if he has both feet on the ground beyond the back edge of the base or beyond the edge of the base in the direction to which he is advancing."

Diagram of when a runner has passed a base.

Though this base passing interpretation ordinarily applies to forward progress as runners advance, it is also applicable to retreating runners. This most often occurs during fly out/tag-up situations, where an existing baserunner (e.g., R1), generally running on the pitch, runs past a base, only to return to his base of origin in order to tag up on the caught fly ball. In this case, determining whether the baserunner is past or prior is vital to see if the runner must legally retouch the leading base he may have passed (e.g., for the R1-running-on-the-pitch fly-out play, this would be second base).
Related Post: Rare Real-Time Appeal Retires Runner over Retouch Rule (6/15/17).
Related Post: Past or Prior - Deciding When a Runner Has Passed a Base (7/1/17).

Put it all together and you get Rule 5.09(b)(9) Comment, which is actually an approved ruling, or case play, that the Playing Rules Committee inserted into the rules book, and is precisely what Rich refers to when he says, "the new rule":

PLAY—Runners on second base and third base with one out. The runner from third base (i.e., the lead runner) makes an advance toward home and is caught in a rundown between third base and home plate. Believing the lead runner will be tagged out, the runner at second base (i.e., the trailing runner) advances to third base. Before being tagged, the lead runner runs back to and beyond third base toward left field. At this time, the trailing runner has passed the lead runner as a result of the lead runner’s actions. As a result, the trailing runner is out and third base is unoccupied. The lead runner is entitled to third base if he returns to touch it before he is out, see Rule 5.06(a)(1), unless he is declared out for abandoning the bases.

Suffice it to say, 🚨this is exactly what happened🚨. Lead runner R3 Stanton retreated toward third as trailing runner R1 Sanchez advanced to third base. Before being tagged, R3 Stanton ran back to and beyond third base toward left field, thus running through the past/prior barrier, as depicted above. By rule, R1 Sanchez passed Stanton as a result of Stanton's actions, meaning, R1 Sanchez is out and R3 Stanton is entitled to third base if he returns before he is out...except that fielder Joseph tagged Stanton while off his base, meaning that both baserunners were out.

As for abandonment, let's be clear. U3 Kulpa ruled Stanton out on the tag. Abandonment isn't at issue.

Showalter argues his point to no avail.

Long story short, this double play was missed, may have resulted in an affirmed protest if Baltimore lost the game ("may have," because New York failed to score in the 6th inning, so MLB could have ruled that the incorrect rules application did not affect the outcome of the game), and, had there been an ejection, would have resulted in a QOC of "Incorrect."

It's rare that an MLB game is protested, and it's almost unheard of to have a protest with merit. The last upheld protest—in 2014—concerned a grounds crew that botched its unfurling of a tarp during a Chicago rain delay, and this followed 28 years of no protest having been upheld across the major leagues. What's more, the 2014 protest had absolutely nothing to do with a rules application regarding actual gameplay: it was a rain delay and the decision of suspension vs. calling the game as final. MLB even acknowledged its rain delay tarpaulin rules were deficient and changed the applicable rule during the ensuing offseason. Not so much here, as Rule 5.09(b)(9) Comment fits the Stanton/Sanchez play to a T: MLB won't have to change any rule to account for Friday night's play.
Related Post: Protest Upheld for 1st Time in 28 Yrs in SF-CHC Rainout (8/20/14).

MLB punished Culbreth's crew for its mistake.

The last meritorious MLB protest concerning a bungled gameplay rule occurred in 2013 when Angels Manager Mike Scioscia alleged that Crew Chief Fieldin Culbreth and umpires Brian O'Nora, Bill Welke, and Adrian Johnson failed to enforce then-Rule 3.05 (now 5.10(g)), which requires a substitute pitcher to pitch to the batter then at bat or any substitute batter before that pitcher is removed from the game. Culbreth's crew had allowed Astros Manager Bo Porter to replace his just-into-the-game substitute pitcher in response to Scioscia's decision to bring in a pinch hitter, without that pitcher having thrown a single pitch. Faced with a less desirable pitcher on the mound, Anaheim's Los Angeles' batter flew out to end the inning.
Related Post: Angels Protest After Wright Exits Without Throwing a Pitch (5/9/13).

As the Orioles ultimately won Friday's game in New York, the Angels won 2013's game in Houston, meaning that Scioscia's protest was effectively dropped. Nonetheless, MLB publicly punished the umpiring crew for the rules misapplication, suspending Fieldin Culbreth and fining O'Nora, Welke, and Johnson, for failing to apply a rule.
Related Post: Culbreth Suspended; Johnson, Welke & O'Nora Fined for Pitching Change Fiasco (5/11/13).

Will Meals, Kulpa, Hickox, and May suffer a similar fate for their collective rules error? Stay tuned.

Sidebar: Had both runners been tagged while simultaneously occupying third base, lead runner R3 Stanton would be safe and trail R1 Sanchez would be out.
Related Post: Right of Return - When Two Runners Occupy One Base (4/3/18).

Videos (2x) as follows:

Right of Return - When Two Runners Occupy One Base

When two runners converge upon one base, the situation may appear chaotic, but to an umpire well versed in the rules of baseball, such a comedy of errors is simply the product of an obscure rule book test question come to life. Knowing which player to declare out, and how to employ proper mechanics so as to avoid confusing or confounding the situation, is key to adjudicating this "Right of Return" play and looking confident while doing so.

The Right of Return is a good rule to know.

The Play: With one out and runners on first and second (R1 on first and R2 on second), Reds pitcher Austin Brice legally feigns to second before stepping off the mound and trapping lead baserunner R2 Trea Turner between second and third. As F1 Brice runs at R2 Turner, trailing baserunner R1 Brian Goodwin runs toward second base, stepping onto the bag and setting up a situation where both R1 Goodwin and R2 Turner will simultaneously stand on second base. F1 Brice initially tags R2 Turner before tagging R1 Goodwin to conclude the play.

The Call: 2B Umpire James Hoye sees F1 Brice tag the lead runner, R2 Turner, and makes no call. When F1 Brice subsequently tags both R2 Turner and R1 Goodwin in quick succession, only then does 2B Umpire Hoye call R1 Goodwin out, decisively pointing to R1 Goodwin so as to confidently project which runner is out. In basketball, referees call this a "bird dog" (pointing toward the player who has committed the foul), and used to employ this signal on nearly every play. In the modern era, officials use the "bird dog" less often, similar to an umpire refraining from demonstration of a full wind-up "out" call on each and every play at first base. In short, this call is correct and the mechanics are superb.

Hoye's mechanics help communicate the out.

The Rule: On a pickoff play (or any play that isn't a "force play"), the following table shall apply:

Situation: No Force	R1	R2	Who is Entitled to 2B?
Neither Touching	No	No	Either Runner.
R1 Only	Yes	No	Either Runner.
R2 Only	No	Yes	R2 Only.
Both Touching	Yes	Yes	R2 Only.

In other words, on non-force plays, preceding runner R2 is always entitled to his/her base of origin: in this situation, R2 can always go back to second base and if both runners are subsequently tagged while standing on second base, R2 is "safe" and R1 is "out." The only way trail runner R1 is entitled to the base to which (s)he is advancing is if the preceding runner R2 has already vacated that base; as soon as R2 returns to touch R2's original base, R2 becomes the entitled runner.

OBR 5.06(a)(2) tells us everything we need to know: "Two runners may not occupy a base, but if, while the ball is alive, two runners are touching a base, the following runner shall be out when tagged and the preceding runner is entitled to the base, unless Rule 5.06(b)(2) applies." 5.06(b)(2) simply states that if the trail runner is forced to advance, then the trail is entitled to the base and the preceding/lead runner will be out when tagged; in a force play situation, the trail runner is always entitled to the base to the next base until the trail is retired; upon the trail runner being declared out, the preceding runner re-assumes entitlement to the base (see aforementioned "Situation: No Force" table). A batted ball force play is the only time you'd "use the force."

Know the Situation, When to Use the "Force."

Situation: Force	R1	R2	Who is Entitled to 2B?
Neither Touching	No	No	R1 Only.
R1 Only	Yes	No	R1 Only.
R2 Only	No	Yes	R1 Only.
Both Touching	Yes	Yes	R1 Only.

Sidebar: As stated above, if the trail runner (R1) passes the preceding runner (R2) before R2 is out, then R1 is out. However, as soon as R2 is out in a non-force situation, R1 is legally allowed to stand on the base. For example, if R2 was declared out (say, he was tagged off the base) and only then did F1 tag R1 (who was standing on the base), then R1 would be safe. If R1 arrives at and passes second base, and then tries to return to first when R2 retreats to second, he must retouch second base or be liable to be called out on appeal.
Related Post: Solution for Case Play 2013-09: Whose Base is it Anyway? (9/21/13).

Sidebar of the Sidebar (Gil's Call): I just realized the above image showing the situation of two runners (R1, R2) and one out is also a potential infield fly. So in addition to using the "force" on a batted ball, remember that if the batted ball is an infield fly, the table you should use is the "not force" table, since the batter being declared out on the infield fly rule—which will occur before any potential play at second base—removes the force on R1/R2, meaning you shouldn't use the "force."

Drawing even with a teammate is not "passing."

Runners Passing Consideration: If R1's body entirely passes R2 (or if R1 passes a base that R2 is standing on), he is out immediately upon the passing. If R1 is simply touching R2 or even parallel to R2, he has not yet passed his teammate. Passing is an automatic out for time play purposes, and not an appeal play. Rule reference: 5.06(b)(9): "He passes a preceding runner before such runner is out."

See the related post for more information about when a runner has passed a base, which carries a slightly different standard than determining when a runner has passed another runner.
Related Post: Past or Prior - Deciding When a Runner Has Passed a Base (7/1/17).

Video as follows:

Past or Prior - Deciding When a Runner Has Passed a Base

Runner Brandon Belt was ruled out for failing to retouch a base based on the interpretation for passing a base, and specifically, the question of, "when is a runner said to have passed a base?"

Belt runs past second base on his way to first.

With one out and one on (R1) in the top of the 7th inning of Saturday's Giants-Pirates game, Giants batter Brandon Crawford hit a 0-1 slider from Pirates pitcher Tony Watson in the air to center fielder Andrew McCutchen, who caught the fly ball as Giants baserunner R1 Belt arrived at second base as part of a hit-and-run or stolen base attempt. As McCutchen completed his catch, Belt raced back to first base ahead of the throw, while Pirates shortstop Max Moroff called for the ball, claiming that in retreating to first base, Belt failed to retouch second base in violation of Official Baseball Rule 5.06(b)(1), which states, "In advancing, a runner shall touch first, second, third and home base in order. If forced to return, he shall retouch all bases in reverse order, unless the ball is dead."

After 2B Umpire Dan Iassogna ruled Belt safe on appeal, Pittsburgh filed a challenge and Iassogna's call was overturned via Replay Review, Belt ruled out at second base for having failed to fulfill his OBR 5.06(b)(1) responsibility.
Related (More about 5.06): Rare Real-Time Appeal Retires Runner over Retouch Rule (6/15/17).

With replays indicating Belt kept a foot on the second base bag before beginning his sprint back toward first base, the question, naturally, is when is a runner considered to have passed a base, and when is a runner considered to have legally retouched it?

Fortunately, the MLB Umpire Manual specifies an interpretation for this part of "passing a base":

A runner is considered to have passed a base if he has both feet on the ground beyond the back edge of the base or beyond the edge of the base in the direction to which he is advancing.

Interpretations Diagram: Past vs Prior.

Insofar as a play at second base is concerned, a runner has passed the base when both feet are on the left field side of the imaginary line that extends from home plate, through second base, and into center field (with the second base bag itself considered as part of the "not past" side of the field).

The accompanying "past or prior" diagram is the accepted interpretation for all situations where a determination is to be made as to whether a runner has passed a base, such as base award plays (e.g., Type B Obstruction or a forced-to-advance play [e.g., a walk]) or scoring decisions.
*Grammatical note: "Past" is used as a preposition, part of the phrasal "run past" verb, as in, "he ran past the base." The past tense verb is "passed," as in, "he passed the base."

Gibson observes the race to first base.

EXCEPTIONS: On June 29, umpires ruled Diamondbacks batter Eric Fryer out at first base after he overran the bag without touching it and Diamondbacks first baseman Paul Goldschmidt was able to tag first base with his glove before Fryer returned to touch the base. Fryer had initially missed his touch of first base in trying to avoid Goldschmidt, who himself had missed his tag—1B Umpire Greg Gibson thus ruled Fryer "safe" (the mechanically correct thing to do).

The relevant MLBUM interpretation states that, "A runner does not acquire the right to an unoccupied base on an attempt to retire the runner until he touches it before he is put out."

In 2016, first baseman Hanley Ramirez tagged batter-runner Nelson Cruz, who similarly missed first base during a tag avoidance maneuver, affirmed as a real-time appeal out by 1B Umpire Hunter Wendelstedt.

Another exception is home plate, as there is no base past home plate which the runner may advance: a runner never truly "passes" home plate—he just forfeits the right to retouch it upon entry into the dugout. If both the fielder and runner miss their touches (the fielder misses his tag of the runner, and the runner misses home plate), no signal shall be given and no appeal permitted (for the aforementioned "a runner never truly 'passes' home plate" reason); the fielder must tag the runner to retire him (unless the runner begins to exit the field, in which case, an appeal is authorized in order to eliminate a "catcher chasing the runner" situation). This doesn't apply, naturally, to a force play, where simply tagging home plate will retire the runner.

Video via "Read More" >

Case Play 2016-11 - Time to Pass a Runner [Solved]

Runner passing occurs when a trailing baserunner passes a preceding one. Time to Pass a Runner is our 11th Case Play of the 2016 season and, like Case Play 2016-10, concerns a Replay Review decision flagged for discussion by tmac.

Diagram of the Runners Passing Case Play.

The Play: With one out and one on (R1), White Sox batter Tyler Saladino hit a 1-2 fastball from Royals pitcher Matt Strahm to deep left-center field, where the ball fell onto the warning track untouched before bouncing over the outfield wall as Royals outfielder Jarrod Dyson unsuccessfully tried to glove it. Initially ruled a two-base award for Saladino and baserunner R1 Leury Garcia, giving Garcia third base and Saladino second base, the play was challenged by Royals Manager Ned Yost, who alleged that Saladino had illegally passed Garcia on the base paths, and therefore, should have been declared out pursuant to Rule (Garcia would still be awarded third base). After review, however, the Replay Official ruled both runners safe and placed them at second and third base, explaining in his decision to confirm the on-field ruling, that "The runner was not passed by another runner prior to the ball going out of play."

NY/Replay's Explanation in Confirming the Call.

Question: Is this the proper ruling, given visual evidence (or assuming that the evidence indicates) that Saladino did pass Garcia, but only after the ball had become dead by virtue of it bouncing out of the playing field? If not, what is the proper ruling, and who would get credit for the putout (if applicable)?

In other words, assume Crew Chief Fieldin Culbreth ruled the runners did pass each other, but only after the ball was dead, and assume this is visually correct. The question at hand is whether or not the ball becoming dead has any bearing on the legality of the trail runner's passing of the lead runner at some point during the dead ball period. Does the runners passing rule become suspended/not applicable when the ball is dead?

Answer: If Yost specifically challenged that the runners passing action occurred prior to the ball going out of play (as the above graphic and explanation from NY/Replay HQ indicates), then this is the proper ruling, as the passing did not occur during a live ball ("The Replay Official shall have no authority to review any calls other than those included in a Manager's Challenge or those accepted for review by the Crew Chief" Replay Review Regulation II.I).

Otherwise, Rule 5.06(c) states that the when the ball is dead, bases may not be run, no run scored, and no runner may be put out, except "as the result of acts which occurred while the ball was alive." For this play, the batted ball bouncing out of play is a live ball event that results in a dead ball bases-run situation (R1 awarded 3rd, B1 awarded 2nd). By contrast, a foul ball is also a dead ball, but no bases are awarded as result of the foul ball, so no runners may advance or be put out. (There is no potential for illegal base running during a dead foul ball because no runners may advance during a foul ball.)

Rule 5.06(b)(4)(I) Comment specifies that a base award without liability to be put out "does not relieve [a runner] of the responsibility..." For example, a batter-runner who hits a home run must still touch all bases in order. If a base is missed, the defense may appeal when the ball next becomes live. However, does this responsibility extend to other baserunning obligations, such as passing or abandonment?

Abandonment may occur during a home run.

A runner may not be put out during a dead ball—this is why the defense must wait for the ball to become live before lodging an appeal—but this isn't to say a runner may not be declared out during a dead ball. "Put out" is something the defense does, whereas "declare out" is something the umpire does.

For example, with one out and the bases loaded, B1 hits a game-winning home run, and runs across the field to celebrate before the winning run crosses home plate (for simplicity's sake, assume B1 already touched first base). B1's run will not count, as B1 never legally touched home plate and therefore will be declared out for abandonment, even though this action occurs when the ball is dead. The winning run thus will score with two outs.

A passing runners play from earlier in 2016.

A similar circumstance exists with passing runners. This occurred in Case Play 2016-3, when Marlins batter JT Realmuto passed baserunner Marcell Ozuna during an apparent home run. Originally no-called, the Replay Official in overturning the on-field ruing simply explained that runner passing occurred, without regard to the timing relative to live/dead ball (the definitive angle used to overturn the call appears in the image to the left—the ball's location was not considered as it was in Chicago).

Similarly, Orioles batter Javy Lopez was declared out by 2B Umpire Gerry Davis for passing baserunner Miguel Tejada during a 2006 non-home run in Baltimore, while Robin Ventura hit a grand slam single during the 1999 NLCS after failing to legally run the bases during a dead ball. Naturally, the umpire may reverse the passing if doing so will nullify the defense's illegal act (for instance, passing may be reversed/cancelled/nullified if the defense has obstructed the offense, for instance by face guarding, jockeying, or improperly blocking R1's view, and doing so will nullify the obstruction).

F4 is closest to the passing & gets the putout.

The only consideration in regards to the "put out" is scoring the play: the fielder closest to the violation receives credit for an unassisted put out (9.09(c)(4)). Technically, however, the offending trail runner is declared out by the umpire, rather than physically put out by the defense: there is no tag.

Retrosheet.org has a list of notable Passing Runners situations that have occurred over the years, including several instances of batters and runners being declared out for passing that occurred during a dead ball.

NFHS vs NCAA vs OBR: All codes agree, passing can occur during a dead ball. However, only NFHS does not treat runner passing during a dead ball as a time play. PLAY: With two outs and two on, B1 hits a home run. After R3 scores, B1 passes R1 on the bases. Undeterred, R1 completes his HR trot and touches home plate. RULING: In NFHS, R3 & R1's runs both count. In NCAA & OBR, only R3's run counts due to the timing of the third out. NOTE: If the bases are loaded with two outs and B1 walks on a 3-2 pitch, after which R1 passes R2, then R3's run shall count whether or not he touched home plate prior to the third out, since he was forced home.

Official Baseball Rules Library
OBR 5.05(a)(6): "A fair ball, after touching the ground, bounds into the stands, or passes through, over or under a fence, or through or under a scoreboard, or through or under shrubbery, or vines on the fence, in which case the batter and the runners shall be entitled to advance two bases."
5.06(b)(4)(I) Comment: "The fact a runner is awarded a base or bases without liability to be put out does not relieve him of the responsibility to touch the base he is awarded and all intervening bases."
Rule 5.06(c): "While the ball is dead no player may be put out, no bases may be run and no runs may be scored, except that runners may advance one or more bases as the result of acts which occurred while the ball was alive (such as, but not limited to a balk, an overthrow, interference, or a home run or other fair ball hit out of the playing field)."
OBR 5.09(b)(9): "Any runner is out when—He passes a preceding runner before such runner is out."
OBR 5.09(b)(9) Comment: "A runner may be deemed to have passed a preceding (i.e., lead) runner based on his actions or the actions of a preceding runner."

Video available via "Read more"