Baseball’s New Tech Fails: Manager Ejected

A baseball bat and ball resting on a baseball diamond

Technology promised to remove human emotion from baseball’s most contentious calls, yet Derek Shelton’s ejection proves the machines have only amplified the drama.

Quick Take

Twins manager Derek Shelton became the first manager ejected over ABS timing rules on March 29, 2026, during a high-leverage ninth inning against Baltimore
Shelton argued that Orioles pitcher Ryan Helsley failed to signal his challenge within the required three-second window before Josh Bell’s called ball became a strike
The ABS system, designed to eliminate umpire error, instead created ambiguity around signal timing that neither MLB nor its managers fully understood
Early season data shows extreme challenge usage across the league, suggesting the new system may need immediate rule clarifications

The Moment That Changed Everything

Top of the ninth inning, Baltimore ahead 8-6, Twins rallying with a runner on first and one out. Ryan Helsley’s 3-2 pitch to Josh Bell appeared to miss. The home plate umpire called it a ball. Bell began his walk to first base. Then Helsley tapped his cap, signaling an ABS challenge. The automated system reviewed the pitch, found it nicked the outside corner, and overturned the call to strike three. Bell was out. The rally died. Derek Shelton erupted from the dugout.

When Technology Meets Ambiguity

Shelton’s argument wasn’t about the pitch location. The automated system made that determination objectively. Instead, he questioned whether Helsley had signaled within the three-second window MLB established for challenges. The timing seemed tight. The signal seemed delayed. The rule seemed unclear. Shelton’s ejection highlighted a fundamental flaw in the ABS rollout: MLB created an objective system for pitch evaluation but left subjective interpretation around its procedural mechanics.

The Twins had taken a 4-0 lead early against Orioles starter Shane Baz. Baltimore’s Tyler O’Neill answered with a three-run homer in the fourth. Dylan Beavers added a two-run double in the sixth. Pete Alonso’s go-ahead single in the seventh gave the Orioles the lead. Royce Lewis homered for Minnesota to tie it at 5-5, but Baltimore pulled ahead again. By the ninth inning, the Twins were desperate. That moment with Bell represented a chance to spark a comeback. Helsley’s challenge killed it.

A System Barely Tested

ABS challenges represent MLB’s most aggressive technological intervention into the game since instant replay. Each team receives two challenges per game. Umpires use automated verification to confirm or overturn calls. The system followed years of minor-league and spring-training testing designed to address umpire accuracy issues. Yet early season results suggest the league underestimated how often teams would challenge and how confused managers would become about enforcement details.

The Precedent Nobody Expected

On March 28, one day before Shelton’s ejection, the Cincinnati Reds and Boston Red Sox played a preview of ABS chaos. Eight challenges were issued in that game alone. Six were overturned. The Red Sox exhausted both their challenges by the third inning. The precedent was set: teams would challenge aggressively and often. Shelton’s ejection became inevitable once MLB implemented a rule nobody could consistently interpret.

Helsley understood Shelton’s frustration. The Orioles pitcher acknowledged the signal delay perception but noted that second-base umpire Laz Diaz had backed the challenge as valid. Shelton’s post-game comment cut to the heart of the problem: “I didn’t think Helsley tapped his cap quick enough. I feel like it’s gotta be something within the three seconds.” Nobody disagreed with him. Nobody could prove him right either. The three-second rule existed, but its enforcement remained mysterious.

What Comes Next

The Twins lost the series 2-1 to Baltimore. Shelton faced potential discipline. The ABS system remained in effect league-wide with ongoing early-season adjustments. Industry observers noted that technology had failed to remove emotions from baseball—it had merely redirected them. Instead of arguing ball-strike accuracy, managers now argued signal timing, challenge eligibility, and procedural compliance. The machines promised objectivity. They delivered bureaucracy.