BOSTON — Baseball is a game of rules, but sometimes those rules create moments that leave even the umpires bewildered. That was certainly the case Monday night when the Boston Red Sox and Toronto Blue Jays played out a sequence so strange it took a 15-minute review and a call to New York to sort out.
The bizarre chain of events unfolded in the top of the seventh inning at Rogers Centre, with the Red Sox trailing 2-0. Ceddanne Rafaela stepped to the plate with runners on first and third and one out — at least, that was the reality on the field. But the stadium scoreboard told a different story, displaying two outs instead of one.
That small glitch set off a chain reaction. Rafaela hit a routine fly ball to center field. Believing there were two outs, both Red Sox baserunners took off from their bases as the ball was caught, assuming they could advance freely. The Blue Jays, alert to the situation, turned a double play — recording an out at first base on the runner who failed to tag up.
But when the dust settled, everyone on the field seemed to think the inning was over. The umpires, however, weren’t so sure. They huddled, then summoned both managers for a lengthy discussion before announcing a review would be conducted by MLB officials in New York.
After a delay that stretched to 15 minutes, crew chief Chris Guccione emerged to explain the situation — and his opening words did little to reassure anyone that clarity was at hand.
“Okay, so what we have here,” Guccione began, sounding every bit as perplexed as the players and fans hanging on his every word.
The confusion centered on a “time play” — a rule that determines whether a run counts if it crosses home plate before the third out is recorded on a force play or other non-tag situation. In this case, the runner on third had scored before the Blue Jays made the out at first base.
Normally, in such a scenario, the run would count. But there was a twist: the runner on third had not tagged up on the fly ball, which meant Toronto could have appealed and potentially turned the unusual “fourth out” — a rule that allows a team to record an out after three have already been made, often to negate a run that would otherwise count.
The Blue Jays, however, had already left the field, crossing the foul line into their dugout. According to the umpires, that ended any chance of an appeal. The Toronto fielders had effectively forfeited their opportunity to challenge the play by leaving the field of play.
As a result, the run scored. The Red Sox got on the board, though it wasn’t enough to avoid a 2-1 loss.
The play was so rare that it drew comparisons to only a handful of similar instances in recent memory. Broadcasters noted prior examples from 2022 between the Pittsburgh Pirates and Washington Nationals, and another from 2009 involving the Los Angeles Dodgers and Arizona Diamondbacks.
“Bizarre,” the announcers said on the broadcast. “That’s as strange as it gets.”
While the Red Sox ultimately fell short, the game will be remembered less for the final score than for the head-scratching sequence that briefly brought the action to a halt. The scoreboard malfunction was a key contributing factor, and it’s unclear whether any changes will be made to prevent similar confusion in the future.
For the Blue Jays, the frustration was palpable: they had recorded what they believed to be the final out, but a technical glitch and an obscure rule conspired to give Boston an unexpected run. For the Red Sox, it was a small consolation in a losing effort.
As the umpires’ ruling was announced, the crowd at Rogers Centre reacted with a mix of disbelief and confusion. Even seasoned baseball observers acknowledged they had rarely seen anything like it.
In the end, the bizarre sequence served as a reminder that even in a sport built on rules and precision, the unexpected can — and often does — happen.
Source: www.dailywire.com — https://www.dailywire.com/news/mlb-game-delayed-after-bizarre-sequence-confuses-everyone-including-the-umps