You know something is wrong when a triple play seems more like a triple gut punch. Fans are still furious after the New York Mets found themselves in that precise situation during Friday’s game against the Washington Nationals.

Everything was going smooth until the sudden shift in the fourth inning. The Mets were playing fine at Nationals Park on Friday; there were no outs and men on first and second. And then, a clean line drive toward first base by Jesse Winker was caught by the Nationals’ first baseman Nathaniel Lowe. Ruling it a catch, the umpire set off a series whereby Mark Vientos was out at first and Brandon Nimmo was doubled off at second, so producing a triple play that finished the inning. A triple play! Replays, however, showed the ball had really bounced before reaching Lowe’s glove, so it wasn’t a clean catch but a controversial one. Since then, it has left fans, analysts, and players furious.

Was that the right decision? That was the only question on everyone’s mind. This event has generated debate about the shortcomings of MLB’s replay system, particularly when important plays like this one cannot be checked for accuracy. Baseball analyst Ben Verlander succinctly captured the annoyance, “Insane this can’t be reviewed. Mets got screwed. Umpire makes a bad call. Says it’s caught in the air. It results in a TRIPLE PLAY to end the inning. Brutal.”

Mets manager Carlos Mendoza disputed the decision, but under MLB regulations, such infield plays are not subject to video review. A rule that can change the entire game. Is this really acceptable? Well, just like Ben Verlander, the Mets and their fans are finding it so.

MLB’s replay rules say some plays are non-reviewable. Specifically excluded from replay review are “fly balls or line drives fielded by a defensive player in the infield.” Unlike outfield plays, which are subject to review, this one is not.

The reason behind this? MLB wants to keep the game moving and restrict reviews to factual decisions. But, as this event shows, such limitations can result in major game-changing errors.

Maybe it’s time to look back and change the replay rules. Guaranteeing correctness should be a priority.

Déjà Vu for the Mets

The New York Mets have historically been no strangers to late-inning heartaches. Remember the 2011 game against the Atlanta Braves? Where the Queens were in a leading spot, but a triple call changed the whole picture.

A key mistake by José Reyes in the ninth inning back in 2011 caused a 6-3 loss to the Atlanta Braves. Though he had two hits and scored a run, Reyes botched a grounder, letting the go-ahead run score. Reyes said after the game, “I have to make that play.” “No excuse.” This blunder drew attention to the Mets’ continuing battle to obtain late-inning advantages.

Fast forward to 2025, and the Mets were in a similarly annoying scenario. A disputed triple play was called against them in the fourth inning of a game vs the Washington Nationals. Looking at 2025, there have been a couple of foul calls that have sparked controversy.

Let’s recall the latest one. The Aaron’s Judge incident? During a game vs the Tampa Bay Rays at Steinbrenner Field, New York Yankees captain blasted a majestic shot down the left-field line. Third base umpire Scott Barry called it foul. A crew chief review confirmed his ruling since there was not enough solid evidence to reverse it. After contesting the decision, Yankees manager Aaron Boone was thrown out; Judge voiced his unhappiness by saying, “That’s a fair ball.”

These events show that MLB umpiring is still difficult to get right. As technology advances, discussions concerning replay reviews and automated procedures may increase to reduce such disputes.