Showing posts with label Umpire Odds/Ends. Show all posts
Showing posts with label Umpire Odds/Ends. Show all posts

Tuesday, September 1, 2026

Rocchio Out Of Base Path, But Did Pitcher Obstruct Him First?

As Guardians batter-runner Brayan Rocchio ran toward first base during a ground ball in Cleveland, he saw a pair of Royals in 1B Salvador Perez and pitcher Daniel Lynch standing in his base path and veered to his left to avoid a tag. 1B Umpire Paul Clemons called Rocchio out for running more than three feet out of his base path to avoid the tag, but did non-fielding pitcher Lynch's presence on the first baseline obstruct Rocchio on his way to first base? Was this indeed out of the base path, or should this have been obstruction instead with Rocchio awarded first base?

Play: With two out and none on, Rocchio hit a soft ground ball up the first baseline, drawing both F3 Perez and F1 Lynch. Perez fielded the ball and BR Rocchio ran to his left to avoid both F1 Lynch and F3 Perez's tag. U1 Clemons called Rocchio out for running more than three feet away from his base path to avoid the tag.

Conflicting Rules: There are two competing rules with opposite penalties to discuss. One pertains to out of the base path, as Clemons called. The other pertains to obstruction regarding Lynch standing in Rocchio's way.

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." This is the rule Clemons enforced in calling Rocchio out.

OBR 6.01(a)(10), which pertains to interference protection, however, states, "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."

This rule is relevant because the non-protected fielder, which in this case was F1 Lynch (F3 Perez was protected), is liable for obstruction if they violate that rule, which states, "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."

When there is a question of violation, whether it pertains to this obstruction rule, runner's lane interference, or any other rule, the benefit of the doubt goes to the team that has not violated.

In this case, we have a clear sequence of events. First, F3 Perez fields the baseball. Second, F1 Lynch who is not protected, stands in the runner's base path. Third, BR Rocchio runs to his left, more than three feet away, to avoid F3 Perez's tag.

Because of this order, it would appear Lynch's illegal positioning and obstruction came before the runner ran more than three feet away to avoid a tag. Had the pitcher not been in the runner's way, could the runner have remained within three feet of his base path? We will never know. There is a question of violation, which means the benefit of the doubt goes to the team that has not violated.

But because both teams violated, we must consider the order in which they violated. Because the defensive team Kansas City violated first, the benefit of the doubt goes to Cleveland batter-runner Rocchio, which suggests F1 Lynch obstructed the runner before the runner ran more than three feet away from his base path to avoid a tag. Because Type 1 Obstruction is an immediate dead ball, the play effectively stopped before the runner committed the base path violation; this is obstruction.

Video as follows:

Friday, August 28, 2026

Cubs PCA Argues Uncalled Balk vs Arizona, Was Chicago Right?

As Chicago baserunner R3 Pete Crow-Armstrong danced down the third base line in Arizona, his distraction prompted Diamondbacks pitcher Eduardo Rodriguez to rush his delivery, with PCA upset at the uncalled balk as umpires determined, after crew consultation, that a balk had not occurred. But was it?

The Play: With two out and a runner on third base, Cubs batter Michael Busch stepped in for a 2-1 pitch from Diamondbacks pitcher Eduardo Rodriguez as Chicago baserunner R3 Pete Crow-Armstrong danced down the third base line. Rodriguez was pitching from Windup Position, having declared Windup while standing in a Hybrid stance (footwork indicating Set Position, but opting to pitch from the Windup), giving R3 PCA a little more time for baserunning antics near 3B, which pitcher Rodriguez noticed mid-delivery and rushed his motion home, turning the 2-1 pitch into a pitchout of sorts to catcher James McCann, who exited his box to receive the ball.

Chicago campaigned for a balk, while 3B Umpire Malachi Moore gestured for the crew to convene. After consultation with 1B Umpire Mike Estabrook and 2B Umpire Lance Barrett, HP Umpire and Crew Chief Alfonso Márquez explained via public address microphone that the crew deemed there was no balk, drawing Cubs manager Craig Counsell for an argument.

Was This is a Balk? To determine whether this was a balk, we first narrow down the types of balks this could conceivably qualify as. Pursuant to Official Baseball Rule 6.02(a)(1), "if there is a runner, or runners, it is a balk when the pitcher, while touching their plate, makes any motion naturally associated with their pitch and fails to make such delivery"; however, pitcher Rodriguez did fire home.

We next investigate the so-called catcher's balk, aka OBR 5.02(a), which states, "the catcher must stand with both feet within the lines of the catcher's box until the ball leaves the pitcher's hand. PENALTY: Balk."

Upon closer inspection, this is a balk pursuant to OBR 6.02(a)(5): "the pitcher makes an illegal pitch" because of Rule 5.07(a) Comment, which states, "The pitcher may not take a second step toward home plate with either foot or otherwise reset their pivot foot in their delivery of the pitch. If there is a runner, or runners, on base it is a balk under Rule 6.02(a); if the bases are unoccupied it should be treated as an illegal pitch under Rule 6.02(b)."

Replays indicate Rodriguez in his rushed delivery reset his pivot foot by stepping off the back of the pitcher's plate/rubber entirely, this disengagement (inadvertent or otherwise) making this an illegal pitch. This was a balk that was not called.

Video as follows:

Tuesday, June 23, 2026

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:

Tuesday, June 16, 2026

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.

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.

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:

Monday, June 8, 2026

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:

Wednesday, April 29, 2026

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.

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:

Thursday, October 9, 2025

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:

Wednesday, September 17, 2025

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:

Tuesday, September 9, 2025

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:

Saturday, August 23, 2025

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:

Wednesday, August 6, 2025

Jen Pawol is First Woman to Umpire MLB Regular Season Game

Jen Pawol will be the first woman to umpire MLB regular season baseball during the Marlins-Braves game in Atlanta this weekend, a move generations in the making. Here's a brief history of why it took so long and why women and minorities—including Angel Hernandez—had to keep suing professional baseball for a chance to take the field.

Bernice Gera, who in 1972 was the first woman to officiate a minor league game had to file litigation against professional baseball in order to compel the powers that be to allow her onto the field.

At the time, Hall of Fame Umpire Al Barlick allegedly said Gera "belongs in the kitchen — where all women belong, or most of them." Years later, Barlick allegedly told then-minor leaguer Al Clark, "I’ll tell you one thing. As long as I’m alive, there will never be another f*n’ Jew umpire in my league."

Barlick served as a National League supervisor after retirement from umpiring on the field and was partially responsible for hiring decisions. He was inducted into the National Baseball Hall of Fame in 1989, despite his history of purportedly sexist and racist statements.

And THAT level of systemic discrimination has been baseball's rot-from-within for years and decades.

Since then, several women, including Pam Postema who made it all the way to Triple-A in the late 1980s, have been stopped short of the major leagues, though multiple sex discrimination lawsuits filed by Postema and others have resulted in settlements along the way.

When Angel Hernandez sued baseball alleging racially-motivated discrimination in 2017, it served as a turning point in how the league treats marginalized groups working their way through the umpiring ranks. In addition to promotions of minority crew chiefs Alfonso Márquez, Laz Diaz, and Kerwin Danley in the years that followed (after a decades-long gap without a non-white chief), professional baseball changed its hiring outlook, both at the MLB level and the MiLB level, with more diverse classes each year.

If you haven't yet read our analysis of Angel Hernandez's lawsuit against MLB alleging racial discrimination, and discussing baseball's historical trend toward a nearly-universal umpiring underrepresentation of protected classes, you might want to consult the following links:
Related Post: Angel Hernandez, MLB, and Discrimination (Part 1) (7/12/17).
Related Post: Angel Hernandez, MLB, and Discrimination (Part 2) (7/13/17).

Video as follows:

Friday, August 1, 2025

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:

Thursday, July 31, 2025

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:

Tuesday, July 22, 2025

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:

Friday, July 18, 2025

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:

Sunday, May 25, 2025

D-Backs Add Insult to Injury on Challenge of Arenado Catch

Arizona added insult to injury for Cardinals third baseman Nolan Arenado on Ketel Marte's fly ball toward the fence down the left field line, as Diamondbacks manager Torey Lovullo successfully challenged that fielder Arenado fell and carried the ball out of play after his catch, resulting in a base award for all runners.

With one out and two on in the top of the 9th inning, Diamondbacks batter Marte hit a fly ball toward the left field stands in foul territory, whereupon Cardinals third baseman Arenado ran to catch the foul pop-fly before crashing into the protective netting in front of the spectator area, injuring his back while also attempting to throw the ball back toward the infield.

Upon Replay Review as a result of a challenge by Diamondbacks manager Torey Lovullo, Replay HQ overturned 3B Umpire Cory Blaser's initial ruling that fielder Arenado (and the ball itself) stayed in play the entire sequence.

Instead, the Replay Official determined Arenado caught the ball on the playing field, but then fell into the stands and out of play, pursuant to Official Baseball Rule 5.06(b)(3), which states, "Each runner, other than the batter, may without liability to be put out, advance one base when—A fielder, after catching a fly ball, steps or falls into any out-of-play area" while 5.06(b)(3)(C) Comment states, "If a fielder, after having made a legal catch, should step or fall into any out-of-play area, the ball is dead and each runner shall advance one base, without liability to be put out, from their last legally touched base at the time the fielder entered such out-of-play area."

Accordingly, the two Arizona baserunners were awarded one base for the catch-and-carry sequence: Alek Thomas to 3rd and Geraldo Perdomo to 2nd (but then Lourdes Gurriel Jr struck out swinging on the next pitch to end the game, so it didn't matter).

Video as follows:

Wednesday, May 7, 2025

Runner Misses Base in Boston, But Replay Says He's Safe???

When Replay Review ruled Rangers batter-runner Wyatt Langford safe at first base, even though he failed to touch it on an infield ground ball, Red Sox manager Alex Cora visited umpire Dan Iassogna for a "call confirmed" explanation. Soon after, Cora walked back to Boston's dugout, appearing satisfied with the crew chief's rationale...so what was the reason Houck was safe?

With one out and two on, Rangers batter Langford hit a ground ball to Red Sox pitcher Tanner Houck, who threw low to first base, where first baseman Romy Gonzalez failed to catch the low throw as batter-runner Langford danced around Gonzalez to avoid him.

1B Umpire Adam Beck slowly gestured "safe" as Boston opted to challenge the call, alleging that Langford was actually out because first baseman Gonzalez did eventually pick up the baseball while standing on first base.

Replay Review returned a "call confirmed" decision, ruling the runner safe at first base, even though the runner missed the bag on his initial run through and even though the fielder's foot was in contact with first base, while he held the baseball, before the runner could return to touch the missed base.

This is an appeal play pursuant to Official Baseball Rule 5.09(c)(2), which states, "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, is tagged."

An appeal is defined as "the act of a fielder in claiming violation of the rules by the offensive team," and the MLB Umpire Manual includes a case play whose scenario mirrors that which occurred in Boston.

It states, "Batter-runner hits a ground ball and beats the play at first base but misses the bag...The proper mechanic is for the umpire to make no call on the play because the batter-runner has not yet touched first base. If the defense appeals by tagging the runner (or base) and appealing that the runner missed first base before the runner returns to first base, the batter-runner would be declared out."

Accordingly, Replay Review applied the MLBUM case play to adjudicate this sequence. The runner is ultimately safe because Boston failed to make a clear and unmistakeable appeal claiming a violation of rules by the offensive team, which is a higher standard than a simple tag out. Whereas inadvertently stepping on the base while holding the baseball might result in an out during a force play, this is insufficient to effect an appeal because it lacks clear communication to the umpire of intent to appeal a violation of the rules.

The only part of this play officiated improperly therefore was the umpire's safe mechanic: the proper mechanic is to make no call until either the defense appeals or the runner returns to touch the missed base. But without a defensive appeal, the runner is safe regardless for having beaten the play.

Video as follows:

Saturday, May 3, 2025

MiLB Ejections - Three Bench Clearings and a HBP

Benches cleared several times between MiLB's Brooklyn Cyclones and Jersey Shore BlueClaws, resulting in three ejections for umpires Dominic Romero and Tatum Littleton, as a violent-but-legal infield collision, home run celebration, and retaliatory intentional hit-by-pitch riled the Single-A series, leaving the two umpires to manage a number of upset players, managers, and coaches.

It all started with a hard infield collision between Cyclones baserunner R2 Eli Serrano, picked off and caught stealing 3rd base, that resulted in rundown, which ended when Serrano ran into BlueClaws right fielder Jordan Viars, the collision knocking Serrano to the ground and bringing Brooklyn out of its dugout. Umpires opted to warn both teams following this bench-clearing incident pursuant to Official Baseball Rule 6.02(c)(9)'s warnings provision: "If, in the umpire’s judgment, circumstances warrant, both teams may be officially “warned” prior to the game or at any time during the game."

Two innings later, Serrano homered and celebrated during his trip around the bases, drawing further BlueClaws ire and an argument from manager Greg Brodzinski, who left the dugout to argue with the umpires several times over the course of this series.

The next day, BlueClaws pitcher Aaron Combs hit Cyclones batter Chris Suero with a pitch immediately after Suero shouted out toward the mound, resulting in yet another benches-clearing event as the bullpens got involved, going back and forth with Suero at first base.

Umpires Romero and Littleton had huddled up to confer after the intentional HBP, as is protocol, and the benches emptied during this discussion that had taken both umpires away from their game management responsibilities...thanks, of course, to pro ball protocol for intent HBP situations which mandate a full-crew conference. The umpires then had another conference before opting to eject BlueClaws pitcher Combs for violation of OBR 6.02(c)(9) ("If, in the umpire’s judgment, such a violation occurs, the umpire may elect either to expel the pitcher, or manager and pitcher, from the game, or [issue warnings]") and batter Suero for his unsporting conduct with the pitcher and bullpen.

BlueClaws manager Brodzinski got the boot for refusing to stop arguing after more than five minutes of discussion with the umpires following the umpires' own conference.

Video as follows:

Sunday, April 27, 2025

Nats Turn Triple Play on Mets When Umps Don't Make a Call

Washington turned a triple play on New York after 1B Umpire Alfonso Marquez's crew didn't signal whether Mets batter Jesse Winker's line drive was caught by Nationals first baseman Nathaniel Lowe, a somewhat similar play to the recent double play that resulted in minor league manager Jose Moreno's ejection in Double-A...but this is really about umpire positioning.

In DC, with none out and runners on first and second baes, Mets batter Winker hit a line drive to Nats first baseman Lowe, who may or may not have fielded the batted ball on a bounce—New York wouldn't know, because none of the four umpires signaled safe or out for the catch / no catch element of this play.

While the Mets stumbled around in confusion after the no-call, Washington turned a triple play with first baseman Lowe ruled to have caught the batted ball for out number one, runner R2 Brandon Nimmo out at second base on appeal for out number two, and R1 Mark Vientos out at first base for out number three.

Umpire positioning led to a coverage vacuum contributing to the catch/no catch chaos, as 2B Umpire Lance Barrett's starting position outside the fielders with runners on base ran afoul of the MLB Umpire Manual's approved teaching for four-person positioning with runner(s).

This isn't just a problem unique to this game, it's systemic in recent MLB memory, as second base umpires have increasingly opted to work outside even with runners, despite the Manual's instruction and assumption that all second base umpires will work inside (at the cut of the infield grass) with runner(s) on base.

The MLBUM coverage responsibilities chart states that the second base umpire has catch/no catch responsibility for a first baseman ranging to their right on an infield line drive, but when U2 is working outside, they lose their advantageous angle to see the play. With the play going away from U1, this was not 1B Umpire Alfonso Marquez's call to make, so, effectively, no one clearly called in real time a line out, and the resulting confusion led to a Nationals' triple play.

So as we initially opined back when umpires began working outside with runner(s), the starting position of U2 outside is problematic for certain plays with runners on base. This is just the latest example of what happens when U2 starts out with runners instead of playing in.

Video as follows:

Saturday, April 26, 2025

Hand Waving Intentional Interference on the Grass

When 2B Umpire Marvin Hudson called interference on Brewers baserunner Jackson Chourio on Christian Yelich's infield ground ball, Milwaukee manager Pat Murphy argued the runner's decision to run on the infield grass is actually legal. Hudson let Murphy have his say, leaving broadcasters to piece together why interference was called...and citing some totally unrelated rules along the way.

With R1 Chourio on first base and one out, batter Yelich hit a ground ball to Cardinals 1B Willson Contreras, who threw to second base to try and force out Chourio. The ball hit Chourio and caromed into left field, drawing an interference call ("Time" and dead ball) by 2B Umpire Hudson.

Official Baseball Rule 5.09(b)(3) states, "Any runner is out when they intentionally interfere with a thrown ball; or hinder a fielder attempting to make a play on a batted ball."

While veering onto the grass on its own generally does not satisfy the intentionality standard of this rule, R1 Chourio's actions in raising his left arm prior to the throw's arrival suggests a proactive attempt to intentionally interfere with the throw.

Thus, R1 Chourio is out not for running on the infield grass or veering, as the broadcaster's incorrectly stated, "out of his baseline" (first, it's a base path not a baseline; and second, the base rule only applies to tag attempts: a thrown ball is not a tag attempt, and therefore the three-foot base path rule does not apply here), but for intentionally interfering with the fielder's throw, as evidenced by his actions in raising his arm prior to the throw's arrival to disrupt the defense's play.

Video as follows: