MiLB Ejection on Non-Interference with 2 Outs in 9th

An interference no-call when a runner collided with a fielder attempting to field a batted ball with 2 outs in the 9th allowed Double-A's Senators to tie its game with the Eerie SeaWolves, resulting in ejection and extending the minor league game that was ultimately decided in the 10th inning.

3B Umpire Brandon Spevak ejected SeaWolves manager Tony Cappuccilli for arguing the non-interference call when Senators batter Johnathon Thomas singled on a ground ball past third base. Senators baserunner R2 Maxwell Romero Jr, running into third base, collided with SeaWolves third baseman EJ Exposito, allowing the ball to trickle by while Romero scored and Thomas advanced to second base. At the time of the ejection, the Senators had just tied the game at 2-2. The SeaWolves ultimately won the contest, 3-2, in 10 innings.

The relevant rule is Official Baseball Rule 6.01(a)(10): "Any runner is out when—they fail to avoid a fielder who is attempting to field a batted ball, or intentionally interfere with a thrown ball."

Is there an exception, however, to this rule when a runner is either in contact with or running toward a base?

The answer is no. On a batted ball, the fielder has the right to field it.

At any other time, the runner has the right to run the bases.

Bear in mind, only one fielder is deemed 'protected' during a batted ball, which is an umpire's determination as to which fielder is entitled to field the ball. A non-protected fielder may be guilty of obstruction if they impede the runner.

There is one exception during which the base is a safe space when it comes to questions of batted ball interference: "If a runner is touching their base when touched by an Infield Fly, they are not out, although the batter is out" (OBR 5.07(b)(7)).

Other than that, however, the base is not a safe space and this is interference. Video as follows:

MLB Ejections 065-6 - Barrett/Moore (PHI Overrun of 2B)

3B Umpire Lance Barrett ejected Phillies infield coach Bobby Dickerson and HP Umpire Malachi Moore ejected pitching coach Caleb Cotham (Replay Review decision that confirmed 2B Umpire Mike Estabrook's safe / no abandonment call; QOCY) in the bottom of the 8th inning of the #Phillies-#Reds game. With one out and two on, Reds batter Sal Stewart hit a 3-2 sinker from Phillies pitcher Orion Kerkering on the ground to 3B Alec Bohm, who threw to 2B Bryson Stott, to 1B Bryce Harper, as Reds baserunner R1 Elly De La Cruz arrived at second base, ruled safe by 2B Umpire Estabrook and confirmed via Replay Review as the result of a manager's challenge by Phillies manager Don Mattingly. Replays indicate De La Cruz beat the throw to second base, overran second base, was not tagged, and returned to second base immediately after overrunning it, the call was correct.* At the time of the ejection, the Phillies were leading, 4-1. The Phillies ultimately won the contest, 4-1.

This is Lance Barrett (94)'s 4th ejection of 2026.

This is Malachi Moore (44)'s 1st ejection of 2026.

*Official Baseball Rule 5.09(b)(2): "Any runner is out when after touching first base, they leave the base path, obviously abandoning their effort to touch the next base."

MLB’s 2015 Change: "If a runner runs through 2B or 3B on a potential force play and is ruled out on the field, they can be called out for abandonment if they are ruled safe on instant replay but do not attempt to hold the base or advance to the next base."

Enforcement: "Call may only be made by the Replay Official when a force out at second or third is overturned."

Time Play: "If a time play occurs with a runner attempting to score from third base, the Replay Official will determine if the runner going home touched home plate before the abandoning runner passed the base (i.e., when their second foot touched the ground beyond the base)."

These are the 64th and 65th ejection reports of the 2026 MLB regular season.

This is the 11/12th coach ejection of 2026. Ejection Tally: 34 Managers, 12 Coaches, 20 Players.

This is Philadelphia's 3/4th ejection of 2026, 1st in the NL East (PHI 4; MIA 3; NYM 2; ATL, WAS 1).

This is Bobby Dickerson's 2nd ejection of 2026, 1st since June 30 (Cory Blaser; QOC = Y [Replay]).

This is Caleb Cotham's first career MLB ejection.

This is Lance Barrett's 4th ejection of 2026, 1st since May 30 (Brent Suter; QOC = U [Anthem Standoff]).

This is Malachi Moore's 1st ejection since July 13, 2024 (Marcus Thames; QOC = N [Balls/Strikes]).

Wrap: Philadelphia Phillies vs Cincinnati Reds, 7/7/26 | Video as follows:

MLB Ejection 052 - Jordan Baker (5; Craig Counsell [PCR Out])

3B Umpire Jordan Baker ejected Cubs manager Craig Counsell (Replay Review that overturned 2B Umpire Stu Scheurwater's safe call; QOCY) in the top of the 7th inning of the #Cubs-#Mets game. With one out and one on, Cubs batter Michael Busch took a 3-2 slider from Mets pitcher Tobias Myers for a called fourth ball as Cubs baserunner R1 Pete Crow-Armstrong attempted to steal second base. Although HP Umpire Valentine ruled the pitch ball four, Mets catcher Francisco Alvarez threw to shortstop Bo Bichette as runner Crow-Armstrong slid into second base, ruled safe by 2B Umpire Scheurwater, overturned to out via Replay Review as the result of a challenge by Mets manager Carlos Mendoza. Replays indicate Crow-Armstrong touched second base, then momentarily broke contact with the base and was tagged at this time, but did not pass the base, the call was correct.* At the time of the ejection, the Cubs were leading, 7-2. The Cubs ultimately won the contest, 9-6.

This is Jordan Baker (71)'s 5th ejection of 2026.

*Pursuant to the technical rule, this call is correct. Except when it isn't. At issue is Official Baseball Rule 5.05(b)(1) Comment, which states, "If, in advancing, the base runner thinks there is a play and they slide past the base before or after touching it they may be put out by the fielder tagging them."

Meanwhile, OBR 5.09(b)(6) states, regarding force plays, "The force is removed as soon as the runner touches the base to which they are forced to advance, and if they overslide or overrun the base, the runner must be tagged to be put out." (Bear in mind that the runner is forced to advance by virtue of the batter becoming a runner, which is subject to the same standard for 'when does protection end?' as any other force play.)

This pits two different standards against each other for the same play: "past the base" and "overslides the base", which mean different things. Whereas passing a base is defined as having both feet on the ground past the leading edge of the base, "OVERSLIDE (or OVERSLIDING) is the act of an offensive player when his slide to a base, other than when advancing from home to first base, is with such momentum that he loses contact with the base."

Ultimately, the stricter standard of oversliding takes the day and PCR is called out pursuant to OBR 5.09(b)(4): "Any runner is out when they are tagged, when the ball is alive, while off their base."

This is the 52nd ejection report of the 2026 MLB regular season.

This is the 31st manager ejection of 2026. Ejection Tally: 31 Managers, 7 Coaches, 14 Players.

This is Chicago's 3rd ejection of 2026, 2nd in the NL Central (PIT 5; CHC 3; CIN 2; STL 1; MIL 0).

This is Craig Counsell's 3rd ejection of 2026, 1st since June 11 (Louie Krupa; QOC = N [Fair/Foul]).

This is Jordan Baker's 5th ejection of 2026, 1st since May 30 (Brandon Lowe; QOC = N [ABS Denial]).

Wrap: Chicago Cubs vs New York Mets, 6/23/26 | Video as follows:

Interference Ends Rockies-Pirates Game as Runner Clips Fielder

An umpire crew's interference call ended a one-run Rockies-Pirates game when Pittsburgh runner R2 Billy Cook ran in front of Colorado 3B Kyle Karros and, in doing so, interfered with the fielder's ability to field the batted ball. Let's take a look.

With two out and the bases loaded in the top of the 9th inning of a game Colorado led 2-1, Pirates batter Jake Mangum hit a 1-2 changeup from Rockies pitcher Jaden Hill on the ground toward 3B Karros, who prepared to field the ball as Pittsburgh baserunner R2 Cook ran by.

Although neither 2B Umpire Tyler Jones nor 3B Umpire Clint Vondrak called interference in real-time, Crew Chief Todd Tichenor convened his crew and, alongside HP Umpire Adam Hamari, exited the brief consultation by ruling baserunner Cook out for interference, resulting in the third and final out of the inning and of the ballgame itself.

Official Baseball Rule 6.01(a)(10) states "it is interference by a batter or a runner when they fail to avoid a fielder who is attempting to field a batted ball." Meanwhile, "obstruction is the act of a fielder who, while not in possession of the ball and not in the act of fielding the ball, impedes the progress of any runner."

Interference on the other hand is defined as follows: "Offensive interference is an act by the team at bat which interferes with, obstructs, impedes, hinders or confuses any fielder attempting to make a play." Note that contact between runner and fielder is not required for interference to be called. All that is needed is an act by the runner that simply impedes or hinders the fielder in their attempt to, in this case, field a batted ball.

From these rules and definitions, we are able to assemble a general baseball axiom.

During a batted ball, the fielder has the right of way to field the ball.

At any other time, the runner has the right of way to run the bases.

In other words, because 3B Karros was attempting to field a batted ball, that means he as the fielder has the right of way. Therefore, illegal interaction with the runner results in an interference call, even if there was no actual contact between the players, although in this case, the runner's left foot appeared to contact the fielder's glove prior to the ball's arrival.

Video as follows:

Umpire Warns Caballero for Pitch Clock Delay Strategy

When Yankees batter José Caballero delayed looking up at Blue Jays pitcher Spencer Miles in Toronto, HP Umpire Steven Jaschinski warned New York for an illegal delay tactic, leading to widespread confusion and online outrage that one viral content creator described as the umpire creating a new rule mid-game to punish a player he found annoying.

Rather than click-bait our way to viral monetization at the expense of factuality and reason, we've waited a bit to digest the play, research the rules, and cite our sources as we analyze what exactly happened at Rogers Centre.

With none out and one on in the top of the 6th inning, Caballero stepped into the batter's box, but kept his head down as he took his preparatory stance. By doing so, Caballero might have sought to induce pitcher Miles to come set and commit a pitch clock violation for coming set before the batter was alert to (looking at) the pitcher.

When MLB first introduced its pitch clock rules in 2023 Spring Training, it prescribed three timed responsibilities: catchers had to be in the catcher's box by the timer's nine-second mark, batters had to be in the box and alert to the pitcher by eight seconds, and the pitcher had to begin their delivery prior to the expiration of time.

Shortly thereafter, pitcher Max Scherzer attempted to catch batters off-guard by coming set and immediately firing home as soon as the batter began to look up. Nary a week later, MLB issued a new rule prohibiting pitchers from coming set before the batter becomes alert.

Related Post: Is Max Scherzer's Set Position Pitch Clock Strategy Legal? (3/4/23).

Related Post: MLB's Max Scherzer Rule - Pitcher Can't Come Set Before Batter is Ready (3/12/23).

One month later, Red Sox pitcher Kenley Jansen found himself called for three Scherzer Rule pitch timer violations as HP Umpire Derek Thomas ruled that Jansen came set before Cardinals batter Willson Contreras took his position with both feet in the batter's box and became alert to the pitcher. Once again, MLB issued a memo declaring a new pitch clock policy: batters could no longer induce Scherzer Rule violations by delaying their box entry or alertness by momentarily looking at the pitcher and then looking away as the pitcher comes set. Batters would now be considered alert (and thus pitchers eligible to come set) once they placed one foot in the batter's box and upon the first moment they looked at the pitcher, even if they looked away again.

Related Post: Kenley Jansen Called for 3 Pitch Timer Violations in Boston (5/14/23).

Related Post: Pitch Clock Chaos - Introducing The Contreras Rule (5/24/23).

This new Contreras Rule explained Diamondbacks batter Josh Rojas and Phillies pitcher Craig Kimbrel's pitch clock violation duel in May 2023, culminating with a confrontation that umpires had to break up. MLB effectively declared that neither pitchers (Scherzer Rule) nor batters (Contreras Rule) could attempt to circumnavigate the pitch clock rules to try and gain an unfair advantage.

Back to the present day, when Yankees batter Caballero stepped into the box, he briefly flashed a glance at Toronto pitcher Miles before looking down and delaying his gaze at the pitcher. But because of the three-year-old Contreras Rule, HP Umpire Jaschinski warned Caballero for attempting to circumvent the pitch clock rules to gain an advantage by trying to bait the pitcher into a violation, the first infraction of which is a warning. Had Caballero committed a second Contreras Rule violation, he would have been charged a strike.

So while the Daily News declared, "Caballero did nothing wrong," that declaration happens to be devoid of accuracy.

Video as follows:

Did Jays' Clement Run Out of the Base Path to Avoid Henderson?

Did Blue Jays runner Ernie Clement run out of his base path to avoid Orioles SS Gunnar Henderson's tag attempt? 2B Umpire Nic Lentz didn't think so, signaling safe ruling the play legal because the runner was attempting to avoid the fielder who was fielding a batted ball. So what happened? Let's take a look.

With one out and two on (R1, R3) in the bottom of the 6th inning of the #Orioles-#BlueJays game, Blue Jays batter Brandon Valenzuela hit a 1-1 knuckle curve from Orioles pitcher Shane Baz on the ground to Henderson, who fielded the ball and attempted to tag Blue Jays baserunner R1 Clement before ultimately throwing the ball to first baseman Pete Alonso to retire the batter-runner as Baltimore campaigned for an out of the base path call, claiming R1 Clement ran too far to avoid Henderson's tag attempt.

Official Baseball Rule 5.09(b)(1) states, "Any runner is out when they run more than three feet away from their base path to avoid being tagged unless their action is to avoid interference with a fielder fielding a batted ball.  A runner’s base path is established when the tag attempt occurs and is a straight line from the runner to the base they are attempting to reach safely."

Baltimore manager Craig Albernaz discussed the play with Lentz, who ruled that runner Clement remained legal in his circuitous route to second base, stating he did not illegally run more than three feet to avoid a tag.

After the game, Lentz acknowledged that Henderson did reach out for a tag attempt, Clement's base path was nonetheless legal: "The runner has the right to establish his basepath, and so Clement had established his basepath to avoid the fielder from potential interference."

In doing so, Lentz applied the OBR 5.09(b)(1) exception to OOB, ruling that Clement's action was "to avoid interference with a fielder fielding a batted ball."

Even though Henderson had already fielded the ball before Clement veered far to his right, the MLB Umpire Manual's interpretation of what fielding a batted ball actually is provides further context: "If, after a player has fielded a batted ball but before they are able to throw the ball, a runner hinders or impedes such fielder, the runner shall be called out for interference."

Although this MLBUM rules interp extends the act of fielding protection to after the fielder has already fielded the baseball, the fielder's act of running toward a runner with the ball and reaching an arm out in a tag attempt signifies that the fielder has achieved "able to throw the ball" status; they have simply chosen not to throw quite yet.

Whereas at first glance, the runner clearly ran more than three feet from his established base path to avoid a tag, the question thus becomes whether his action was to avoid interference with a protected fielder, which U1 Lentz ruled is precisely what it was.

Added Wendelstedt, "It actually is a very gentlemanly thing to do." He really said that.

Video as follows:

About Cubs LF Matt Shaw's Fair Infield Single in San Diego

What is a fair ball? Cubs batter Matt Shaw hit an infield single in San Diego when Padres 3B Ty France picked up a batted ball as it rolled along the foul line, HP Umpire Dan Merzel explaining to manager Craig Stammen what he saw as Padres fans expressed outrage at the call.

So what happened?

This play comes up every few years, so we refer to the 2023 season's case of a fair infield single in New York, when HP Umpire Lance Barrett ruled Royals batter Bobby Witt Jr's bunt a fair ball after Yankees 3B DJ LeMahieu swiped his glove at the ball in fair territory.

Related Post: Why Was This Ball Called Fair in New York? (7/23/23).

To begin, we review the Official Baseball Rules' definition: "A FAIR BALL is a batted ball that settles on fair ground between home and first base, or between home and third base, or that is on or over fair territory when bounding to the outfield past first or third base, or that touches first, second or third base, or that first falls on fair territory on or beyond first base or third base, or that, while on or over fair territory touches the person of an umpire or player, or that, while over fair territory, passes out of the playing field in flight."

There are two main standards for judging fair/foul: situations that consider whether a ball is on fair territory and situations that consider whether a ball is over fair territory.

A ball must be on fair territory to be considered fair in the case of: a batted ball settling between home and first/third base or first falling on fair territory beyond first/third base (e.g., in the outfield).

A ball must be over fair territory to be considered fair (whether or not it also touches [or is on] fair territory) for: a batted ball bounding to the outfield past first/third base, a batted ball that touches an umpire or player, or passes out of the playing field in flight (home run).

And, finally, a batted ball that touches first/second/third base is a fair ball.

Eagle-eyed viewers might also notice the rulebook's definition of foul ball is extremely similar, just substituting the phrase "foul territory" for "fair territory."

Thus we must also consider the following definitions: "FAIR TERRITORY is that part of the playing field within, and including the first base and third base lines, from home base to the bottom of the playing field fence and perpendicularly upwards. All foul lines are in fair territory"; "FOUL TERRITORY is that part of the playing field outside the first and third base lines extended to the fence and perpendicularly upwards."

Finally, the MLB Umpire Manual interprets FAIR BALL as, "When in contact with the ground, a ball must be in contact with fair territory and not merely over fair territory in order to be adjudged to be fair."

MLBUM added this interpretation following the introduction of Replay Review ahead of the 2014 season, and it works well for outfield fair/foul decisions on reviewable plays in which the ball may or may not fall on the foul line, generally observed from a parallax-prone camera angle.

For the infield fair/foul decision regarding a batted ball that contacts a person, however, a few key differences arise. First, this is the infield not the outfield. Second, this is not presently a reviewable play. Third, the rulebook criteria for this infield play remains on or over fair territory, as opposed to the outfield play's on foul territory criterion. Fourth, the umpire's angle in calling this play generally positions their head above the foul line, not entirely "top-down" but at an angle greater than 45-degrees and, thus, closer to top-down than ground level.

And herein lies the problem: The umpire, looking from above the height of the ball (unless they were to place their head directly on the dirt), generally will see a baseball over fair territory, all else equal, if any part of the baseball is over the foul line, even if the baseball itself is not in contact with the line (it's a sphere, after all). Pursuant to the Official Baseball Rules, the umpire calls this a fair ball when touched by the fielder, which conflicts with the MLBUM interpretation, which itself conflicts with OBR. Lovely.

Video as follows:

Cubs Wanted Infield Fly Rule on Dropped Ball in Chicago

Cubs manager Craig Counsell sought an infield fly rule call after Chicago 1B Michael Busch lost track of Brewers batter William Contreras' fly ball in the sun, allowing Milwaukee to load the bases in the 1st inning of NLDS Game 3.

With runners on first and second base with one out, Contreras hit a high fly ball in front of first base, on the infield.

The Official Baseball Rules defines the infield fly: "An INFIELD FLY is a fair fly ball (not including a line drive nor an attempted bunt) which can be caught by an infielder with ordinary effort, when first and second, or first, second and third bases are occupied, before two are out. The pitcher, catcher and any outfielder who stations themself in the infield on the play shall be considered infielders for the purpose of this rule."

Accordingly, the infield fly rule has four criteria: 1) first and second (or bases loaded), 2) before two are out, 3) the batter hits a fair fly ball (not line drive nor bunt), 4) that can be caught by an infielder with ordinary effort.

The first three criteria were plainly satisfied, which leaves us with #4: the ordinary effort criterion.

We thus turn to OBR's definition of that term: "ORDINARY EFFORT is the effort that a fielder of average skill at a position in that league or classification of leagues should exhibit on a play, with due consideration given to the condition of the field and weather conditions."

Because F3 Busch, the fielder we would expect to make a play on this ball, lost the ball in the afternoon Chicago sun, the "weather conditions" provision of the ordinary effort definition gets triggered: 1B Umpire Lance Barksdale, looking directly at Busch, ruled that this particular weather condition turned Busch's potential catch from requiring effort that was ordinary into extraordinary.

Umpires therefore ruled ordinary effort was not satisfied, which is why an infield fly was not declared.

Video as follows:

Catcher's Interference No-Call in TOR-NYY ALDS

Blue Jays catcher Alejandro Kirk did not interfere with Yankees batter Trent Grisham in Game 3 of the Toronto-New York ALDS, following a Replay Review that upheld HP Umpire Jordan Baker's interference no-call as Grisham's bat came awfully close to making contact with catcher Kirk's mitt.

With none out and none on in the bottom of the 3rd inning of Game 3, batter Grisham attempted to check his swing on a 2-2 knuckle curve from Blue Jays pitcher Shane Bieber, ruled ball three. 

Upon Replay Review as the result of a manager's challenge by Yankees manager Aaron Boone, HP Umpire Baker's call was upheld, with Replay HQ ruling "call stands" as to the question of catcher's interference. 

Specifically, clear and convincing evidence did not exist to indicate whether or not catcher Kirk interfered. Because of the "call stands" ruling, we know the Replay Official judged the play solely on the merits of whether or not Grisham's bat made contact with Kirk's mitt.

The Official Baseball Rules defines catcher's interference as defensive interference: "an act by a fielder that hinders or prevents a batter from hitting a pitch."

Because replay only concerned itself with potential batt-glove contact, the judgment call as to whether hinderance actually existed (beyond the question of whether contact occurred) was not on the table.

In high school (NFHS), catcher's interference is called catcher's obstruction, as NFHS defensive interference is specifically an act that occurs prior to the pitch.

OBR 6.01(c) specifies the penalty for catcher's interference: "The batter becomes a runner and is entitled to first base without liability to be put out (provided they advance to and touches first base) when the catcher or any fielder interferes with them."

Video as follows:

Fan Interference AND HR? Blue Jays-Rays Replay Rewind

Rays batter Brandon Lowe's home run stood on review as umpires called both fan interference and a home run on the same play. Blue Jays manager John Schneider met with 3B Umpire Laz Diaz afterward to discuss the unusual ruling, which we now analyze.

With one out and two on in the bottom of the 3rd inning, Rays batter Lowe hit a 2-2 changeup from Blue Jays pitcher José Berríos on a fly ball to deep right-center field. Blue Jays right fielder Nathan Lukes jumped in an attempt to catch the ball, but a fan reached out of the stands and caught the descending fly ball, ruled a home run by 1B Umpire Brian O'Nora.

Upon Replay Review as the result of a Crew Chief initiated-second look (potential home runs are chief reviews), Replay determined that while the fan did definitively commit spectator interference, the home run would ultimately stand because, absent the fan's interference, the ball would have left the yard anyway.

In crafting this ruling, the Replay Official relied on two different rules concerning spectator interference. The analysis thus relies on two different parts.

First, the Official Baseball Rules definition of terms delineates what spectator interference actually is: "Spectator interference occurs when a spectator (or an object thrown by the spectator) hinders a player’s attempt to make a play on a live ball, by going onto the playing field, or reaching out of the stands and over the playing field."

Upon review, Replay HQ in New York determined clear and convincing evidence did exist to declare that spectator interference did occur. To that end, the call on the field of no interference was overturned.

Second, OBR 6.01(e) is triggered only if the spectator interference definition's criteria are satisfied. OBR 6.01(e) states, "When there is spectator interference with any thrown or batted ball, the ball shall be dead at the moment of interference and the umpire shall impose such penalties as in their opinion will nullify the act of interference." An approved ruling allows the umpire to award an out if the fielder would have caught the ball if not for the interference.

This second part of the equation is where Replay Review encountered more difficulty. Because the video angles available were all from press box/behind the home plate area, and no side angle (e.g., parallel to the fence-line) existed, Replay HQ could not definitely determine what would have happened had interference not occurred. In other words, Replay had trouble with the "nullify the act" portion of the rule.

With a lack of clear and convincing evidence to determine how to nullify the act of interference, that leaves with a peculiar ruling of overturn for the interference part of the equation, but call stands for the nullification portion.

Accordingly, the technically correct language and outcome for this play is that the call on the field of no interference was overturned. It was spectator interference, but because of a lack of clear and convincing evidence to suggest what would have occurred absent the fan's illegal involvement, the home run ultimately stands as called.

Video as follows:

Did Runner Interfere So Teammate Could Score?

Chicago trapped Colorado batter-runner Yanquiel Fernández in a rundown as Rockies lead baserunner Warming Bernabel attempted to score. As Cubs second baseman Nico Hoerner received a throw from Michael Busch, BR Fernández collided with him, 2B Umpire Alan Porter ruling an out on the tag, but not interference, the delay from the collision allowing R1 Bernabel additional time to score, with a slide into home plate just ahead of the tag attempt.

Should this have been ruled interference or, because Fernández hadn't yet been tagged until after the initial collision (although he was tagged while being shoved away by Hoerner), does the relevant rule pertaining to a retired runner not apply? For reference that rule is Official Baseball Rule 6.01(a)(5): "Any batter or runner who has just been put out, or any runner who has just scored, hinders or impedes any following play being made on a runner. Such runner shall be declared out for the interference of his teammate."

Video as follows:

Obstruction in Boston as Runner & Catcher Collide on Batted Ball

"Obstruction!" announced umpire Jordan Baker after Guardians batter-runner José Ramírez and Red Sox catcher Connor Wong collided on a batted ball up the first baseline. Instead of an out, Ramírez was awarded first base and Cleveland's Brayan Rocchio scored from third. What's the rule and did Baker's crew get the call right?

With one out and runners on second and third in the top of the 2nd inning of Wednesday's Guardians vs Red Sox game, batter Ramírez hit a check swing ground ball in front of home plate toward first base. Boston catcher Wong initially pursued the batted ball before stopping once he saw pitcher Steven Matz running to field it, turning around to head back to cover home plate as R3 Rocchio raced in.

But as Wong turned toward home, he collided with batter-runner Ramírez. Initially ruled interference on Ramírez, chief Baker called his crew into consultation, ultimately ruling that, because Wong was not entitled to protection under the rules for fielding a batted ball, he therefore obstructed the batter-runner. Accordingly, the batter-runner was awarded first base and all runners advanced one base.

In general, baseball's right-of-way rules give the fielder the right to field a batted ball (meaning the runners must avoid the fielder lest they be guilty of interference) while the runner has the right to run the bases at any other time (the fielder must get out of the runner's way). However, only one fielder is entitled to right-of-way protection on a batted ball and, in this case, that protected fielder was not the pitcher, not the catcher. As such, the unprotected catcher obstructed the runner's right to run the bases.

This is the correct call pursuant to the following rules:

Official Baseball Rule 6.01(a)(10): "It is interference by a batter or a runner when they fail to avoid a fielder who is attempting to field a batted ball, or intentionally interfere with a thrown ball, provided that if two or more fielders attempt to field a batted ball, and the runner comes in contact with one or more of them, the umpire shall determine which fielder is entitled to the benefit of this rule, and shall not declare the runner out for coming in contact with a fielder other than the one the umpire determines to be entitled to field such a ball."

OBR 6.01(h)(1): "If a play is being made on the obstructed runner, or if the batter-runner is obstructed before they touch first base, the ball is dead and all runners shall advance, without liability to be put out, to the bases they would have reached, in the umpire’s judgment, if there had been no obstruction. The obstructed runner shall be awarded at least one base beyond the base they had last legally touched before the obstruction."

Wrap: Cleveland Guardians vs Boston Red Sox, 9/3/25 | Video as follows:

Runner Touched by Fair Ball in Little League - What's the Call?

What happens when a runner is touched by a fair ball? During the Canada vs Aruba Little League World Series game, a baserunner from first base ran into a batted ball after it passed the drawn-in first baseman, but before it got to the second baseman backing up. Umpires, what's the call here?

With one out and one on, a ground ball to the right side eluded Aruba's diving first baseman, without touching him or his glove, before striking baserunner R1 behind him, as the second baseman ranged to his left to potentially back up the play. After initially ruling runner R1 out, umpires ultimately placed R1 on second base, deeming that he did not interfere with the batted ball.

Official Baseball Rule 6.01(a)(11) states it is interference when "A fair ball touches them on fair territory before touching a fielder. If a fair ball goes through, or by, an infielder, and touches a runner immediately back of him, or touches the runner after having been deflected by a fielder, the umpire shall not declare the runner out for being touched by a batted ball. In making such decision the umpire must be convinced that the ball passed through, or by, the fielder, and that no other infielder had the chance to make a play on the ball."

Little League Rule 5.09(f) is nearly identical in outcome: "If a fair ball goes through, or by an infielder and touches a runner immediately back of said infielder or touches a runner after being deflected by an infielder, the ball is in play and the umpire shall not declare the runner out. In making such decision, the umpire must be convinced that the ball passed through, or by, the infielder and that no other infielder had the chance to make a play on the ball; runners advance if forced."

Given that the ball did not make contact with the first baseman, the operative question, thus, is whether or not the second baseman had the chance to make a play on the ball. If he did, then the runner is out. If he did not, then the runner is not out. What's your call?

Video as follows:

Umpire Ejects Batboy (Ballboy?) After Controversial Call

Umpire Richy Arrendondo ejected a ball boy for arguing a series of calls during a Loons vs River Bandits game in MiLB's Midwest League. Having already tossed Quad Cities catcher Canyon Brown and manager Jesus Azuaje, the umpire mouthed "What are you doing?" toward the ball boy, who used the delivery of replacement baseballs as an opportunity to argue with the umpire, a no-no for auxiliary personnel.

HP Umpire Richy Arredondo ejected River Bandits catcher Canyon Brown, manager Jesus Azuaje, and the ball boy for arguing a ball four call, foul ball no-call, and balk call in the top of the 7th inning of the Loons-River Bandits game of MiLB's High-A Midwest League. With one out and one on, Loons batter Logan Wagner took a 3-1 pitch from River Bandits pitcher Mauricio Veliz for a called fourth ball, resulting in the ejection of catcher Brown. Following a two-RBI double by Jake Gelof, batter Joe Vetrano swung at a pitch for strike two, ruled a wild pitch that allowed Gelof to advance to third base, resulting in an argument from manager Azuaje that batter Vetrano actually fouled the pitch off (Azuaje was ejected here). Shortly thereafter, Gelof scored on a balk, resulting in the ejection of the ball boy for arguing while he delivered replacement baseballs.

Although we don't often encounter it, ball or bat attendant ejections fall under a lower category on officiating's tolerance hierarchy than managers, players, assistant coaches, and bench personnel. Attendants (in this case, a ball boy) are considered auxiliary personnel, are supposed to be impartial (e.g., not to argue or have a competing interest in the game and not to favour one team over the other), and are to be dismissed if they fail to maintain neutrality, as the ball boy did during this game.

Wrap: Great Lakes Loons vs Quad Cities River Bandits (Midwest Lg), 8/21/25 | Video as follows:

MANAGER Hit by Pitch During Ejection Tantrum

Quebec Capitales' manager was hit by a pitch thrown by his pitcher, on purpose, after being ejected by HP Umpire Jordan Alfonso of the Frontier League. Patrick Scalabrini's antics followed Ottawa Titans batter Jackie Urbaez's hit-by-pitch in the 9th inning, Urbaez's fourth HBP of the game.

Scalabrini's lively demonstration suggests an argument concerning whether Urbaez should have really had four HBPs, or whether he failed to follow the rule that would require he attempt to avoid the pitch.

Official Baseball Rule 5.05(b)(2) states, "The batter becomes a runner and is entitled to first base without liability to be put out (provided he advances to and touches first base) when they are touched by a pitched ball which they are not attempting to hit unless (A) The ball is in the strike zone when it touches the batter, or (B) The batter makes no attempt to avoid being touched by the ball."

If the pitch is in the strike zone when it touches the batter, it is a dead ball strike, and if the pitch is out of the zone and touches the batter who makes no attempt to avoid being touched, it is a ball (no award of first base). The batter only gets the base award if they make an attempt to avoid a ball.

Meanwhile, in college, NCAA Rule 7-4-i awards a strike if the batter "is judged to intentionally make a movement to be hit by a pitch, regardless of where the pitch is located; or allows themself to be intentionally hit by a pitch that is not thrown within the boundaries of the batter’s box unless it was not possible to avoid being hit."

High School (NFHS 8-1-d) is similar to professional ball: "If the batter permits the pitched ball to touch oneself (7-3-4), or if the umpire calls the pitched ball a strike, the hitting of the batter is disregarded except that the ball is dead. It is a strike or ball depending on location of the pitch."

Video as follows:

Balk or Ball? When An Umpire Should Ignore a Balk

When is a balk not a balk? Umpires correctly called A's pitcher Jeffrey Springs for a no-stop balk during a 3-2 pitch to Mariners batter Julio Rodríguez, but awarding baserunner R1 Ben Williamson second base was only half of the equation. Instead of Rodríguez awarded first base on ball four (the pitch was low), the crew returned the batter to the plate, where he proceeded to strike out swinging on the next pitch.

We first note Official Baseball Rule 6.02(a)(13) pertaining to balks, which states, "If there is a runner, or runners, it is a balk when the pitcher delivers the pitch from Set Position without coming to a stop."

Because pitcher Springs failed to come to a complete stop while in Set Position, as in OBR 5.07(a)(2), 1B Umpire John Tumpane was correct to call out "balk" when the infraction occurred.

OBR 6.02(a) continues, specifying the penalty for a balk violation: "The ball is dead, and each runner shall advance one base without liability to be put out, unless the batter reaches first on a hit, an error, a base on balls, a hit batter, or otherwise, and all other runners advance at least one base, in which case the play proceeds without reference to the balk."

Although the ball ultimately becomes dead on a balk, if the pitcher pitches, that pitch may still count, as long as it results in the batter-runner reaching first base and all other runners advancing at least one base.

In this situation, the pitch missed low for ball four, which meant that runner R1 Williamson would have been forced to advance to second base, by virtue of batter Rodríguez becoming a runner on the base-on-balls.

But instead of applying the "play proceeds without reference to the balk" portion of the penalty due to both batter and runner advancing at least one base, the umpires enforced the base award for the runner and returned the batter to home plate, where he proceeded to strike out instead of taking his base.

Video as follows:

Narváez Called for CI for 2nd Day in a Row - Balk Too!

Called for catcher's interference one day earlier, Red Sox catcher Carlos Narváez again committed CI, this time with a side of balk as HP Umpire Edwin Jimenez ruling he stepped in front of the back edge of home plate prior during a pitch and prior to receiving the ball as Phillies runner Bryce Harper looked to steal home plate.

Catcher's interference is defined more broadly as defensive interference in the Official Baseball Rules: "an act by a fielder that hinders or prevents a batter from hitting a pitch." In high school (NFHS), catcher's interference is called catcher's obstruction, as NFHS defensive interference is specifically an act that occurs prior to the pitch.

Official Baseball Rule 6.01(g) directly addresses this case of the so-called catcher's balk: "If, with a runner on third base and trying to score by means of a squeeze play or a steal, the catcher or any other fielder steps on, or in front of home base without possession of the ball, or touches the batter or their bat, the pitcher shall be charged with a balk, the batter shall be awarded first base on the interference and the ball is dead."

Video as follows:

Phillies Win on Walk-Off Catcher's Interference

A walk-off win due to catcher's interference in Philadelphia left some Boston fans perplexed as Phillies batter Edmundo Sosa's bat made contact with Red Sox catcher Carlos Narváez during a 2-2 pitch, HP Umpire Quinn Wolcott announcing Replay Review's verdict over the stadium PA much to the delight of the home crowd. Because the bases were loaded at the time of the interference, all runners advanced and the tied game ended in the 10th inning.

Catcher's interference is defined more broadly as defensive interference in the Official Baseball Rules: "an act by a fielder that hinders or prevents a batter from hitting a pitch." In high school (NFHS), catcher's interference is called catcher's obstruction, as NFHS defensive interference is specifically an act that occurs prior to the pitch.

OBR 6.01(c) specifies the penalty for catcher's interference: "The batter becomes a runner and is entitled to first base without liability to be put out (provided they advance to and touches first base) when the catcher or any fielder interferes with them."

It is a rules myth that the batter must actually legitimately swing for catcher's interference to be called. For instance, catcher's interference also occurs when a catcher steps on or across home plate prior to the pitch's arrival, whether or not the batter actually swings at the pitch. Instead, catcher's interference occurs when the catcher's physical positioning (of body and/or glove/mitt) deprives the batter of the opportunity to choose whether to swing or not.

Because batter Sosa is said to have been deprived of this freedom of choice by virtue of the bat-mitt contact, the Replay Official overturned the on-field no-call and awarded the interference penalty, resulting in a walk-off win.

Video as follows:

Little Turf Means It's a Trap & Tag Attempt Base Path Plays

Consecutive plays confused Tigers manager AJ Hinch as Replay upheld a no catch/trap call on Rangers batter Kyle Higashioka's line drive to Riley Greene before 2B Umpire Alfonso Márquez ruled an out of the base path infraction did not occur when runner Higashioka avoided Detroit fielder Javier Báez's tag attemp on Jonah Heim's ground ball, resulting in an error. Let's review.

We begin with one out and none on in the bottom of the 3rd inning with Higashioka's line drive to left fielder Greene, ruled no catch by 3B Umpire Carlos Torres and challenged by Detroit. Replay Review returned a "call stands" verdict, deeming that video evidence was not clear or convincing to suggest the call's quality of correctness. 

The TV broadcast pondered what would happen if half of the ball was cleanly caught by the glove while the other half bounced off the turf. The Official Baseball Rules' definition of catch states, "A CATCH is the act of a fielder in getting secure possession in their hand or glove of a ball in flight and firmly holding it; providing they do not use their cap, protector, pocket or any other part of their uniform in getting possession."

Because "IN FLIGHT describes a batted, thrown, or pitched ball which has not yet touched the ground or some object other than a fielder," a half-glove, half-ground situation would not qualify as a catch.

On the very next play, Rangers batter Heim hit a ground ball to Báez, who attempted to tag baserunner R1 Higashioka before ultimately throwing to first base (an overthrow for an error). 2B Umpire Márquez ruled R1 Higashioka did not run out of his base path, explaining to a befuddled manager Hinch there was no tag attempt.

Although replays indicate there actually was a tag attempt later in the sequence, OBR 5.09(b)(1) states, "Any runner is out when they run more than three feet away from their base path to avoid being tagged unless their action is to avoid interference with a fielder fielding a batted ball. A runner’s base path is established when the tag attempt occurs and is a straight line from the runner to the base they are attempting to reach safely."

Because the runner already ran to the right field side of the baseline between first and second base prior to the fielder's tag attempt, R1's base path was established from this point and, therefore, he did not run more than three feet away from his base path to avoid the tag (even if he ran more than three feet away from the baseline...just not his personal base path).

Video as follows:

Red Sox Score Tie-Breaking Run on Obstruction vs Rays

3B Umpire Scott Barry's obstruction call on Rays third baseman Junior Caminero for base blocking broke a 0-0 tie, giving Boston a lead when Red Sox runner Marcelo Mayer found himself seemingly picked off by Tampa Bay catcher Matt Thaiss, only for umpire Barry to quickly reverse course and rule that Caminero impeded baserunner Mayer's return to third base due to improper footing.

The Official Baseball Rules define obstruction as "the act of a fielder who, while not in possession of the ball and not in the act of fielding the ball, impedes the progress of any runner."

Although Rays fielder Caminero was indeed in the act of fielding at the time of obstruction (by virtue of preparing to receive the throw), umpires ruled that he did not need to block the base in order to do so. Because Caminero blocked the base voluntarily and outside the scope of simply fielding the ball/throw, obstruction was the proper call.

Official Baseball Rule 6.01(h)(1) prescribes the penalty for Type 1 (Type B) obstruction: "If a play is being made on the obstructed runner, or if the batter-runner is obstructed before they touch first base...the obstructed runner shall be awarded at least one base beyond the base they had last legally touched before the obstruction." This is why baserunner R3 Mayer scored, rather than remained at third base.

Umpire Barry initially stated "stay here" in regard to Mayer's slide back into third base, as HP Umpire Adam Beck walked up the line, the umpires ultimately applying the proper ruling in OBR 6.01(h)(1) to award the runner his next base.

Video as follows: