NEWS
Alonso’s Towering Drive Stands Foul and Flips Orioles Momentum
Pete Alonso’s 410-foot blast ruled foul on review, Yankees score twice in the eighth for a 5-3 win, and Orioles renew calls for better pole technology in 2026.
Pete Alonso crushed a 107.1 mph fly ball 410 feet down the left-field line in a tie game Wednesday night at Camden Yards, pointed skyward, then froze as third-base umpire Will Little called it foul. The review stood. The Yankees scored twice in the eighth and won 5-3.
Baltimore dropped its third straight and sat 1½ games out of the final American League wild-card spot with the series finale still ahead.
The sequence packed a full night of tension into a few pitches. A projected go-ahead homer became a foul ball. A strikeout closed the seventh. Two Yankees runs arrived in the eighth. The Orioles left Camden Yards still searching for a way back into the wild-card picture.
The Swing That Looked Like a Go-Ahead Homer
Bottom of the seventh, score knotted at 3-3, two outs. Left-hander Brent Headrick, working his 65th game of the year, threw a first-pitch slider. Alonso turned on it.
The ball left the bat at 107.1 mph and carried a Statcast-projected 410 feet, appearing to tuck inside the foul pole. Alonso skipped down the line, tossed the bat and jabbed a finger upward. Then Little signaled foul. Arms flew up in the Orioles dugout. Alonso mouthed “No” and later “That’s a fair ball.”
It would have been his second homer of the night and the 30th of his first season in Baltimore after a 423-foot opposite-field shot in the third.
The earlier drive had cleared right-center without debate. This one hugged the line and invited every camera in the ballpark. The contrast was sharp: one swing that counted, one that did not.
- Exit velocity: 107.1 mph on the disputed drive
- Projected distance: 410 feet down the line
- Earlier blast: 423 feet to right-center for a solo shot
- Attendance: 26,453 at Camden Yards
Manager Craig Albernaz challenged. The crew chief review went to New York.
From the plate, Alonso had already started his celebration. From the mound, Headrick had already begun to process a potential deficit. The foul call reset both of those reactions in a single signal.
Why the Call Stood After Every Angle
MLB’s Replay Operations Center watched every available view and issued a clear statement. There was not conclusive evidence the ball left the field in fair territory. The on-field foul call stood.
After viewing all relevant angles, the Replay Official could not definitively determine that the ball left the playing field in fair territory. The call stands, and it is a foul ball.
MLB Replay Operations Center statement
Alonso later said the straight-down-the-line camera looked fair to him, the ball right of the yellow pole. Albernaz noted the dugout iPads showed ball-tracking data that made the “stands” decision hard to accept. “I was really surprised that it came back stands,” he said. “It’s not why we lost the game. But I think that moment was a big moment.”
Yankees manager Aaron Boone said replay coordinator Brett Weber checked the line after the game and confirmed foul. “He’s got it foul. Sorry, Pete. I think it was foul,” Boone told reporters.
Headrick, from the mound, also thought foul and then finished Alonso with a 94 mph fastball for the strikeout that ended the inning.
The standard left no middle ground. Clear and convincing evidence was required to flip the call. Without it, the foul stood and the inning ended on the next pitch.
Bases Loaded and Two Runs in the Eighth
The momentum shift showed immediately. Cam Sanders walked a batter and hit two more to load the bases with two outs in the top of the eighth. Yennier Cano entered.
George Lombard Jr. punched an RBI infield single for the lead. A wild pitch let Jazz Chisholm Jr. score from third. Suddenly it was 5-3 Yankees.
- Sanders loads them: walk plus two hit-by-pitches
- Cano inherits jam: two-out bases loaded
- Lombard single: go-ahead RBI
- Wild pitch: Chisholm scores the insurance run
Alonso called the momentum swing real. “One-hundred percent, absolutely,” he said. “But it is what it is, unfortunately.”
Four batters earlier the Orioles had been one fair ball from a lead. Four batters later they trailed by two. The eighth did not need a long rally. It needed free baserunners and one ball put in play.
Alonso’s First Season in Baltimore Still Delivers Power
The Polar Bear signed with the Orioles and has stayed productive. The night’s first homer pushed him near the 30-homer mark that would have arrived on the disputed swing. His Alonso’s 2026 Orioles season page shows consistent middle-of-the-order production with an OPS north of.850 and double-digit home runs still available in the final weeks.
He has embraced the new colors while the club tries to claw back into October. Wednesday’s near-miss felt like the kind of moment that can light a late push. Instead it left him standing at the plate after the strikeout, then answering questions at his locker.
“Obviously, it sucks for us. It sucks, yeah. It sucks,” Alonso said. “But it is what it is. The umpire made the call on the field, and the review room stood with that call, and that’s what we have to live with and move on.”
Two swings told the story of his night. One cleared the wall in the third. The other hung on the line in the seventh and never counted. The power was there either way.
| Swing | Projected Distance | Result |
|---|---|---|
| Third-inning solo shot | 423 feet to right-center | Home run, counted |
| Seventh-inning drive | 410 feet down the left-field line | Ruled foul after review |
How Close the Wild-Card Race Sits Now
The Orioles entered the night at 61-66. The loss left them 1½ games behind the third AL wild-card position. The Yankees improved their own standing in the chase and took the series edge into Thursday’s finale.
| Team | Record Context | Wild-Card Note |
|---|---|---|
| Yankees | Won 5-3 | Strengthened hold near top of wild card |
| Orioles | 61-66 after loss | 1½ games out of third wild-card spot |
| Next | Series finale Thursday | O’s try to avoid sweep |
Check the current AL wild-card standings for the full picture. Every remaining game carries weight for Baltimore. Three straight losses make the margin tighter.
A win Wednesday would have trimmed the gap and flipped the series narrative. The loss stretched the skid and handed New York the edge heading into the finale. The math is simple and unforgiving at 61-66.
Players Keep Asking for Better Fair-Foul Tools
The argument that followed the call went beyond one night. Starter Chris Bassitt said baseball remains the only major sport still guessing on plays technology could settle. “It costs money. That’s it. That’s literally it,” Bassitt said. He called the absence of definitive tools in 2026 “crazy.”
Alonso pointed to Hawk-Eye, already powering the automated ball-strike challenge system this season, and suggested a laser or camera shooting straight up the foul line the way football uses pylon cameras. Different park dimensions are the reason he has been given for why it has not happened.
Albernaz echoed the frustration with 2026 technology. The dugout tablets already feed ball-tracking data that clashed with the final ruling. The official MLB replay review regulations require clear and convincing evidence to overturn. That standard left the call as foul.
The MLB replay center statement on the call closed the matter for the night. The larger conversation about pole technology will continue as long as close fair-foul decisions keep deciding tight games.
The Review Left Both Dugouts With Different Reads
The same set of angles produced two firm beliefs. Alonso and the Orioles dugout saw fair on the straight-line view and on the tablet tracking. Boone’s club trusted Weber’s postgame check that the ball was foul.
Headrick sided with the foul call from the mound before throwing the 94 mph fastball that ended the at-bat. Little’s original signal never changed. New York’s replay room found no angle strong enough to reverse it.
That gap between what players felt they saw and what the rules allowed to be proven is the core of the night’s dispute. Ball-tracking data reached the dugout iPads in real time. The review standard still demanded a definitive visual that the ball left the field in fair territory.
- Orioles view: straight-down-the-line camera and tablet data favored fair
- Yankees view: Weber’s line check after the game confirmed foul
- Replay standard: no conclusive evidence to overturn the on-field call
- On-field finish: Headrick’s 94 mph fastball for the strikeout
Albernaz separated the call from the final result even while calling it a big moment. Alonso accepted the process while repeating how much it stung. Both readings can be true under the current rules.
How the Seventh and Eighth Innings Linked
The foul call and the Yankees’ two-run eighth were separate events on the scorecard. On the field they felt connected. A potential 4-3 Baltimore lead never arrived. The strikeout that followed kept the game tied. Sanders then walked and hit two batters. Cano inherited the jam. Lombard’s infield single and the wild pitch that scored Chisholm turned a tie into a 5-3 deficit.
- Bottom seventh: Alonso’s 107.1 mph drive ruled foul, then strikeout
- Top eighth: Sanders loads the bases with a walk and two hit-by-pitches
- Still top eighth: Lombard’s two-out RBI single and wild pitch make it 5-3
Alonso put the link in plain terms when he said the momentum swing was real, one-hundred percent. The Orioles never recovered the chance that vanished on the foul pole. The Yankees used the next half-inning to take the lead they would not give back.
Thursday’s finale now carries the weight of a series that tilted on those two frames. Baltimore needs a win to avoid the sweep and keep the wild-card math from stretching further.
Frequently Asked Questions
What was the exit velocity and projected distance of Pete Alonso’s disputed drive?
Statcast tracked the ball at 107.1 mph off the bat with a projected distance of 410 feet down the left-field line. His earlier home run traveled a projected 423 feet to right-center.
Why did MLB’s replay center uphold the foul call?
The official standard requires definitive evidence the ball left the playing field in fair territory to overturn an on-field foul call. After all angles, the Replay Official found no such conclusive view, so the call stood as foul.
What did Chris Bassitt say about the lack of fair-foul technology?
Bassitt said the technology exists and the only barrier is cost. He called it crazy that baseball still lacks a definitive tool for these calls in 2026 when every player and coach would want it.
Would the home run have been Alonso’s 30th of the season?
Yes. It would have been his second of the night after the 423-foot solo shot in the third inning and his 30th overall in his first year with the Orioles.
The Orioles and Yankees close the three-game set Thursday night at Camden Yards.
-
FINANCE3 months agoZcash Patched a Double-Spend Bug as ZEC Climbed 5%
-
ENTERTAINMENT3 months agoSteam Summer Sale 2026 Locks In June 25 to July 9 Dates
-
FINANCE2 months agoCLARITY Act Final Text Expected This Weekend as 60-Vote Hurdle Looms
-
NEWS3 months agoMeta Adds AI Replies to Threads, But Users Can’t Block It
-
NEWS2 months agoNEURA Robotics’ $1.4B Series C Redraws Europe’s Physical AI Bet
-
NEWS2 months agoYouTube Shorts is testing a heart in place of the thumbs-up
-
ENTERTAINMENT3 months ago‘Widow’s Bay’ Review: Apple TV’s Sleeper Horror-Comedy Earns Its Fog
-
FINANCE1 month agoKalshi Loses Major NY Prediction Markets Ruling to Judge Torres
