Manager Ejected Over Robo-Ump Call!

Twins manager Rocco Baldelli was ejected in the ninth inning after arguing a robo-ump call, believing the player's challenge was too late. The analysis shows the challenge was actually made instantly, well within the rules.

3 hours ago
4 min read

Manager Ejected Over Robo-Ump Call!

The first ejection of the season has arrived, and it’s all thanks to the new robo umpires and a controversial call in the ninth inning. The Orioles were leading the Twins by two runs in the final inning. With two outs and a runner on first, the Twins had the tying run at the plate. The Orioles brought in their closer to try and seal the win.

A Tense Ninth Inning Unfolds

The count quickly went to 3-0. The batter, Bell, was the tying run. The umpire called ball one, then ball two. On the third pitch, the umpire called it ball three. Then, on a 3-0 count, the umpire called ball four, putting a runner on first base and bringing the tying run to the plate with two outs.

The next pitch was a breaking ball that the batter fouled back, making it a full count. This was a huge moment in the game. The pitcher threw a back-door breaking ball, and the batter swung and missed. Strike three! Instead of having runners on first and second with two outs, the inning was over. The Orioles celebrated, but Twins manager Rocco Baldelli was not happy.

The Ejection

Baldelli came out of the dugout, furious. He immediately argued with home plate umpire Chris Guccione, yelling that the challenge was “way too [expletive] late.” The transcript indicates Baldelli believed the umpire missed the call on the pitch that the batter took for ball four. He felt the umpire’s reaction to the strike three call, specifically the tap on his helmet, was too delayed.

“That’s too [expletive] late,” Baldelli was heard saying. Guccione disagreed, stating, “No, it’s not. That’s way too late.” The argument escalated quickly. Baldelli insisted the tap was too late, while Guccione maintained it was not. Frustrated, Baldelli was ejected from the game. His immediate reaction was disbelief and anger, as he questioned the umpire’s decision.

Understanding the New Rules

The confusion stemmed from the new rules regarding player challenges and umpire calls. In this situation, players can challenge a call by tapping their helmet. The rule, as explained, is that the challenge must be made instantly. Major League Baseball has a guideline of around two seconds for this tap. If there’s a play at a base, like a steal attempt, the catcher is allowed a bit more time to tap after throwing the ball.

The transcript suggests that the umpire, Chris Guccione, made his call on the pitch. The timer for the challenge likely started right after the umpire’s call. Video analysis showed the first tap was less than a second after the call, well within the acceptable timeframe. A second tap occurred just over two seconds later, still within the potential three-second window Baldelli might have been thinking of, but the initial tap was the key.

The Manager’s Misstep

It’s believed that Baldelli might have been focused on the catcher, possibly expecting the catcher to tap. He might have missed the initial, instantaneous tap from the pitcher, which was under one second. He then saw a later tap, which he perceived as too late, leading to his angry outburst and subsequent ejection. The explanation from the analysis suggests Baldelli missed the crucial, immediate tap.

Game Continues, No Spark

Despite the dramatic ejection, the game continued with two outs and a runner on first. The next batter hit a ball that was eventually caught for the final out. The ejection did not provide the spark Baldelli was hoping for. The Orioles held on to win the game, and the ejection served as a stark reminder of the new technology and the manager’s frustration with it.

Broader Implications

This incident highlights the ongoing adjustments teams and managers are making with the introduction of automated ball-strike systems and new challenge rules. Communication and understanding the precise timing of these new protocols are crucial. For the Twins, it was a tough loss, and for Baldelli, a memorable, albeit negative, start to the season with the first ejection.

The first ejection of the season, all due to a late challenge that wasn’t late. This is what happens when new technology meets old-school arguments.

Sponsored Content

This breakdown was brought to you by MLB 9 Innings. With over 2,000 players, real rosters, and multiple game modes, MLB 9 Innings lets you build and play your way, anytime, anywhere. Download and play MLB 9 Innings 26 today using the link in the description.


Source: Manager gets ejected over a late challenge that wasn't late, a breakdown (YouTube)

Written by

Joshua D. Ovidiu

I enjoy writing.

12,057 articles published
Leave a Comment