Phillies Lose Out After Backswing Interference Loophole, Get it Back After Wrong Count on Batter

[Lindsay]

A loophole in baseball's backswing interference rule nearly cost the Phillies an out in Washington, until HP Umpire Marvin Hudson lost track of the count, giving pitcher Zach Elfin an extra chance to strike out Nationals batter Victor Robles as Philadelphia defeated the Nats, 5-1, on Friday.

With two out and Nationals baserunner R2 Luis Garcia on second base, batter Victor Robles swung at and missed a 2-1 cutter from Phillies pitcher Elfin for a swinging strike as catcher JT Realmuto threw to second base in an attempt to pickoff runner R2 Garcia. Realmuto's initial throw did not retire the runner, but a rundown ensued during which it appeared as if Garcia ran out of the base path to avoid fielder Alec Bohm's tag.

Behind the play, HP Umpire Hudson, however, had called "Time" due to batter Robles' bat making contact with catcher Realmuto's hip on the backswing, an instance of follow-through contact. Pursuant to Official Baseball Rule 6.03(a) Comment, Garcia was returned to second base, safely: "If a batter strikes at a ball and misses and swings so hard they carry the bat all the way around and, in the umpire’s judgment, unintentionally hits the catcher or the ball in back of them on the backswing, it shall be called a strike only (not interference). The ball will be dead, however, and no runner shall advance on the play."

Sidebar: In NFHS/high school, follow-through interference results in an out; pro and NCAA/college do not consider this bona fide interference.

Because the catcher's initial throw did not retire the runner, pursuant to modern interpretation, "Time" is called and play halted; professional baseball does not allow a delayed dead ball situation here to extend past the "initial throw."

With Washington given a second chance, Robles took Elfin's subsequent 2-2 pitch for a called ball, and the next pitch after that for another called ball—but no one on the field seemed to notice that four balls had been thrown to Robles. As such, the count became 3-2 instead of an at-bat-ending 4-2, and with that extra pitch, Elfin struck out Robles...for a cumulative 4-3 count.

Ball/Strike count as well as number of outs and similar scorekeeping variables are reviewable via Crew Chief Review, but with uniformed personnel apparently unaware of the incorrect count, play continued with the improper count becoming the official count, allowing the strikeout to stand.

Video as follows:

Alternate Link: After Nats gain from backswing non-interference loophole, Philly gets extra pitch (CCS)

View the full article

[The Man in Blue]

So ... uh ... this is why they make indicators with 4 balls and 3 strikes on the dials?

[Jimurray]

1 hour ago, The Man in Blue said:

So ... uh ... this is why they make indicators with 4 balls and 3 strikes on the dials?

MLB umpires were required to use indicators when PUs after some occurrences messed up the count in past years but it seems this occurrence might happen to any of us with or without an indicator because stuff happens. But why some of these guys refuse to use one and MLB has backed off the requirement to use one bewilds me. At least have the scorekeeper have input. You 
 

https://umpire-empire.com/discover/content-posted/

[beerguy55]

On 10/1/2022 at 9:12 PM, Jimurray said:

MLB umpires were required to use indicators when PUs after some occurrences messed up the count in past years but it seems this occurrence might happen to any of us with or without an indicator because stuff happens. But why some of these guys refuse to use one and MLB has backed off the requirement to use one bewilds me. At least have the scorekeeper have input. You 
 

https://umpire-empire.com/discover/content-posted/

I don't know if that solves the problem in this scenario.

The ump showed 2-2 before he resumed play - so even after all that running around, killing the play, putting the runner back, and explaining himself about the backswing interference he knew it was 2-2...and then after the next pitch he decided it was 2-2 again.   Not sure if there was some other delay before/after that pitch was thrown, but it seems he literally immediately forgot that next pitch happened - don't know if an indicator fixes that...I can't believe the batter, coaches, runner, other players, other umpires didn't notice that...that's just bad all around....but really, if you're on offense, you better notice this SH*# when it happens...the pitcher isn't gonna help you out.