Did Ty France's Padres Home Run Really Clear the Wall?

Ty France's long fly ball toward the roof structure at American Family Field in the ninth inning never cleared the fence, and Major League Baseball's Statcast system says it was not close. The San Diego Padres first baseman's drive carried a projected distance of 325 feet, 17 feet short of the ballpark's 342-foot left-field wall, according to OutKick's report for Fox News, written by Ian Miller.

That gap is the center of Miller's argument that the ninth-inning call should not be blamed for San Diego's loss. The ball fell short of the fence by the data's own measurement, regardless of how the play looked in real time at the plate.

What happened on Ty France's ninth-inning drive?

France came to the plate in the ninth inning at American Family Field in Milwaukee and connected on a ball that climbed toward the ballpark's upper structure, the kind of deep fly that can draw an instant home-run reaction from a hitter. According to the framing in MLB's own Statcast data as cited by OutKick, France believed in the moment that he had hit a home run. The drive struck high in the park near the roof, and the ruling on the field — that it was not a home run — became the subject of dispute afterward.

What does Statcast's exit velocity and launch angle data show?

Statcast, MLB's ball- and player-tracking system, projects how far a given batted ball would travel based on the exit velocity and launch angle recorded the instant the bat makes contact. Applied to France's swing, that projection came back at 325 feet. Because the model estimates the ball's expected flight independent of what it eventually struck, the 325-foot figure represents Statcast's read on how far the ball was actually hit, not how far it appeared to travel after clipping stadium structure. Miller's reporting treats that number as the clearest available evidence that the drive did not have home run distance, regardless of how the play unfolded visually off the bat.

The projected 325-foot distance fell short of American Family Field's 342-foot left field wall in Milwaukee.

How does American Family Field's wall distance factor in?

American Family Field's left-field fence sits 342 feet from home plate, per OutKick's report. That figure doesn't change based on how a play develops once the ball leaves the bat. Measured against Statcast's 325-foot projection for France's swing, the shortfall is 17 feet — a margin large enough, in Miller's framing, to settle the question of whether the ball had home run distance in the first place. The comparison is presented as independent of the on-field controversy: one number is a fixed property of the ballpark, the other is a measurement of the swing itself.

Did the ruling actually decide the outcome for San Diego?

No, according to Miller's piece, whose headline states directly that the Padres "didn't lose because of" the ninth-inning ruling. The argument rests on the Statcast numbers rather than on the sequence of events that followed the call. If the ball was 17 feet short of leaving the park under neutral measurement, then reversing the on-field ruling would not have changed the physics of the swing — it still would not have been a home run by distance. That framing pushes back against any version of the game's aftermath that treats the disputed call as the reason San Diego came up short, since the underlying batted-ball data, independent of the umpiring decision, did not support a home run to begin with.

The dispute illustrates a recurring feature of modern baseball coverage: when a borderline power shot draws instant controversy, Statcast's exit velocity and launch angle readings increasingly become the first stop for resolving what actually happened, ahead of replay angles or player reaction. In this case, per OutKick, the numbers did not back up the home run claim that circulated in the moment.

Map Tabs is A coming-soon tabbed map for iPhone. Not downloadable yet.