A passenger-reported go-around at Amsterdam Airport Schiphol on May 10th, 2026, illustrates a recurring point of confusion between the flying public and the professional aviation community: what passengers commonly describe as a "touch and go" is almost certainly a balked landing or missed approach, a routine and highly practiced flight crew maneuver that requires no mechanical fault, emergency, or failure to initiate. Go-arounds are executed for a wide range of reasons including unstabilized approach criteria, runway incursions, wake turbulence separation requirements, ATC spacing conflicts, wind shear alerts, and late-breaking runway condition changes. At a major hub like Schiphol, which handles over 400 aircraft movements per day across multiple intersecting runway configurations, go-arounds are statistically common and operationally unremarkable.
Schiphol's runway layout presents particular complexity for crews and controllers. The airport operates up to six runways simultaneously, with several intersecting taxiways and crossing traffic patterns that require precise sequencing. The Polderbaan (18R/36L), Zwanenburgbaan (18C/36C), and Kaagbaan (06/24) are frequently used in parallel configurations that demand tight ATC coordination. A runway incursion, late-clearing aircraft, or a sequencing gap that collapses inside minimums can trigger a go-around decision with very little outward indication to passengers. Crew resource management protocols at most carriers establish specific stabilization gates — typically 1,000 feet AFE in IMC or 500 feet in VMC — and any deviation from approach criteria at those gates mandates the go-around without captain discretion.
For professional and corporate pilots seeking post-event information about specific incidents at European airports, several official and semi-official channels exist. The Dutch Safety Board (Onderzoeksraad voor Veiligheid, OVV) investigates serious incidents and accidents under ICAO Annex 13 criteria, but a standard go-around would not qualify for formal investigation unless it preceded or involved an unsafe event. EASA's ECCAIRS database and the Dutch Civil Aviation Authority (ILT) maintain confidential safety reporting systems. Flightradar24 and FlightAware both retain ADS-B track data that can show altitude and speed profiles through the approach corridor, which would confirm whether a go-around occurred and at roughly what altitude. LVNL, the Dutch air navigation service provider, would hold the ATC communications and radar recordings, though those are not publicly accessible absent a formal inquiry.
The broader relevance for working pilots lies in public perception management and passenger communication. Airlines and operators have increasingly recognized that unexplained go-arounds generate significant passenger anxiety and social media activity, with passengers turning to consumer flight-tracking tools to reconstruct what happened. Many carriers now provide cabin crew scripts specifically for go-around announcements, and some operators brief flight attendants on the most common triggers so they can field questions calmly during climb-out. For Part 135 and corporate Part 91 operators where passengers may have direct access to the flight deck, a brief, confident explanation from the crew — delivered before the passenger reaches for a phone — remains the most effective tool for managing the downstream confusion this Reddit post exemplifies.