A passenger aboard United Airlines Flight 1726, operating from Kahului (OGG) to San Francisco (SFO), reported a go-around executed on short final after the crew received an ATC instruction to abort the approach due to a Hawaiian Airlines aircraft still occupying the landing runway. According to the account, the maneuver occurred in the vicinity of the San Mateo Bridge, a landmark commonly used as a visual reference point during Bay Approach arrivals into SFO's Runway 28 complex. The passenger described a firm power application and climb, followed by a left turn during which the Hawaiian Airlines aircraft was visible rolling on the runway below. The captain subsequently confirmed via PA that the go-around was directed by air traffic control specifically because of the traffic conflict on the runway, rather than a wind shear, weather, or unstable-approach trigger.
While go-arounds are a routine and trained-for contingency in commercial operations — occurring at a rate of roughly one in every few hundred to a thousand approaches depending on airport and conditions — this event stands out because the cause was ground traffic occupying the runway rather than the more commonly cited factors of gusty crosswinds, wind shear, low visibility, or an unstable approach. SFO's parallel runway configuration (28L/28R) has a long, well-documented history of operational complexity, including reduced separation standards during simultaneous visual approaches known as SOIA (Simultaneous Offset Instrument Approaches) and past NTSB scrutiny following high-profile incidents such as the 2017 Air Canada near-miss on taxiway C. Runway occupancy conflicts, where a preceding aircraft has not cleared the runway or vacated in time before the next arrival crosses the threshold, remain one of the more serious categories tracked by the FAA's runway safety programs precisely because they compress decision timelines for both controllers and flight crews.
For working pilots, the event is a useful reminder that go-around discipline must remain sharp and unhesitating regardless of the triggering condition. Crews train extensively for weather-related go-arounds, but ATC-directed go-arounds for runway conflicts require the same immediate, disciplined response: firewall power, positive climb confirmation, missed-approach procedure execution, and clear crew coordination — all while processing an unexpected instruction with less lead time than a self-initiated go-around based on visual or instrument cues. The fact that the passenger noted this was their first ground-traffic-related go-around after 60-plus flights per year underscores how comparatively rare these events are from a passenger's perspective, even though controllers and crews rehearse the scenario regularly in recurrent training and simulator sessions.
More broadly, this incident feeds into an ongoing industry conversation about runway safety and incursion prevention that has intensified following a string of high-profile near-miss events at major U.S. airports in 2023 and 2024, including incidents at JFK, Austin, Burbank, and elsewhere that drew NTSB investigations and prompted the FAA to accelerate deployment of surface-detection technology like ASDE-X and runway status lights at busier hub airports. SFO, as one of the most capacity-constrained and operationally complex airports in the National Airspace System, remains a focal point for these safety initiatives. Incidents like this one — where the system worked as designed, with ATC catching the conflict and the crew executing a clean go-around — are ultimately reassuring demonstrations of the safety net functioning correctly, but they also reinforce why continued investment in surface surveillance technology, controller staffing, and go-around training remains a priority for operators and regulators alike, particularly at high-density airports where runway occupancy margins are routinely thin.