The rulebook exists and matters—even if the call didn't follow it
In the thin margin between fair and foul, a single call in the ninth inning of a late April game between the Padres and Cubs became something larger than a disputed grounder — it became a question about the limits of human judgment and the authority of written rules. Major League Baseball, in a rare moment of institutional candor, acknowledged that home plate umpire Dan Merzel's fair call on a Matt Shaw dribbler may not have aligned with the Umpire Manual's standard, which requires a ball to be in contact with fair territory, not merely above it. The Padres won regardless, but the incident left behind a quiet, unresolved tension between the umpire who was closest to the truth and the rulebook that claims to define it.
- With Mason Miller's 34-inning scoreless streak on the line, a weak grounder down the third base line became the most contested few inches in baseball that night.
- Camera angles broadcast to thousands showed the ball appearing to rest in foul territory, yet the umpire standing directly over it called it fair — and the crowd's eruption said everything.
- MLB's own Umpire Manual draws a precise distinction: a ball must touch fair territory to be fair, not simply pass over it, and the league's Tuesday statement quietly implied that standard had not been met.
- Despite stopping short of an outright reversal, the league's acknowledgment was unusual enough to signal that something had gone wrong — even if no one was willing to say so plainly.
- The Padres won 9-7, Miller accepted the end of his streak without complaint, and the game moved on — but the gap between what the rulebook says and what gets called on the field remained open.
On a Monday night in late April, Mason Miller was three outs away from extending one of the most remarkable scoreless streaks in recent memory when Matt Shaw sent a weak grounder rolling toward the third base line. Ty France watched it drift toward the chalk. From every broadcast angle, the ball appeared to settle in foul territory. Umpire Dan Merzel, standing directly over the play, called it fair.
The crowd at Petco Park erupted. Manager Craig Stammen protested. Shaw eventually scored, and Miller's streak — which had stretched past thirty-four innings — came to an end on a call that felt, to many watching, like it shouldn't have stood.
What followed was unusual. On Tuesday, MLB issued a statement that, without using the word "error," pointed reporters to the official Umpire Manual. The manual is specific: a ball rolling along the ground must be in contact with fair territory to be ruled fair. Hovering above the line doesn't count. The league's response implied Merzel's call had not met that standard — though no reversal was issued, perhaps in recognition of how difficult such judgments are in real time.
France said afterward he thought the ball was foul. Miller offered no complaint. The Padres had won 9-7, and that, he said, was what mattered. The game moved on. But the question of what should have been called — and who gets to decide — lingered quietly in the record.
On a Monday night in late April, with the San Diego Padres clinging to a 9-5 lead in the ninth inning, Cubs infielder Matt Shaw stepped up to the plate against Padres closer Mason Miller. Miller had been nearly untouchable all season, running a scoreless streak that stretched past thirty-four innings. The count went to 1-1. Shaw connected on a weak grounder that dribbled down the third base line, the kind of play that lives in the margins between fair and foul.
Ty France, the Padres third baseman, watched the ball roll toward the line. From the camera angles broadcast to the crowd at Petco Park, the ball appeared to settle in foul territory—most of it clearly on the wrong side of the chalk. But home plate umpire Dan Merzel, positioned directly over the play, made the call: fair. The crowd erupted. Manager Craig Stammen protested. The moment hung there, unresolved, as Shaw eventually scored and Miller's historic scoreless streak came to an end.
What happened next was unusual. On Tuesday afternoon, Major League Baseball issued a statement acknowledging the call. The league didn't use the word "error" outright, but the implication was clear. When Dennis Lin, a reporter covering the Padres, pressed the league office for an explanation, they pointed him to the official Umpire Manual. The manual contains a specific rule: a ball in contact with the ground must be in contact with fair territory to be judged fair. Merely hovering over fair territory doesn't count. The distinction matters. It's the difference between touching and being above.
The league's response seemed to suggest that Merzel's call didn't align with this standard. Yet the statement stopped short of a full reversal, perhaps acknowledging the inherent difficulty of the judgment. Umpires work from angles and perspectives that cameras cannot replicate. Merzel was right there, closer than anyone else could be. Still, social media filled with arguments that the rulebook itself contradicted what had been called on the field.
France, asked about it after the game, was measured. The ball stopped rolling, he said. He thought it was foul. But the umpire said otherwise. Miller, when pressed, offered no complaint. The Padres had won 9-7 in the end. That was what mattered to him. The game had moved on, even if the question of what should have been called lingered in the record.
Citas Notables
It stopped rolling, and I thought it was foul, but they said otherwise.— Ty France, Padres third baseman
Padres win. That's what matters at the end of the day.— Mason Miller, Padres closer
La Conversación del Hearth Otra perspectiva de la historia
Why does MLB even bother acknowledging a call after the fact if they can't overturn it?
Because silence looks like complicity. If the league says nothing, it looks like they're defending the umpire. By pointing to the rulebook, they're saying the rulebook exists and matters—even if the call on the field didn't follow it.
But doesn't that undermine the umpire's authority in the moment?
It does, which is why they're careful not to say it outright. They're threading a needle—admitting the rulebook might have been misapplied without saying the umpire was wrong.
Did the call actually change the outcome of the game?
Not really. The Padres won anyway. But that's almost beside the point. If Shaw's run had been the difference, this would be a different conversation entirely.
So what's the real issue here?
It's about whether the rules matter more than the person enforcing them. Baseball has always said the umpire's judgment is final. But now we have rulebooks and slow-motion cameras that can contradict that judgment. The league is caught between two worlds.
Will this change anything?
Probably not. The call stands. The game is over. But it adds another data point to the argument that maybe some calls shouldn't be left to human judgment anymore.