How Flying Works
What Is a Go-Around, and Why Is It Routine?
A few hundred feet above the runway, the engines spool back up, the nose comes up, and instead of touching down the aircraft climbs away for another circuit. To a passenger with no context, it can feel alarming — the one moment in an otherwise routine flight that suddenly, visibly doesn’t go as planned. To the flight crew, it’s one of the most rehearsed, least dramatic maneuvers in the whole flight, briefed before every single approach whether it’s ever needed or not.
A real example most flyers never see up close
A February 2025 incident at Washington Reagan National put this in front of a much wider audience than usual. An American Airlines crew executed a go-around after a military helicopter strayed into the arrival path near the airport — exactly the kind of split-second, precautionary call the maneuver exists for, and CNN’s coverage of it walked through why the response worked precisely as designed: the crew saw a developing conflict, made the call immediately, and converted what could have become a genuine emergency into a non-event, followed minutes later by an uneventful second approach and landing.
Why it actually happens
The single most common trigger isn’t weather or mechanical trouble at all — it’s traffic spacing. Air traffic control occasionally sequences a faster, heavier aircraft in too close behind a slower one, and the trailing aircraft simply can’t maintain safe separation all the way to touchdown; a go-around resets the sequence rather than forcing an unsafe gap to close. The next most common cause is what pilots call an unstabilized approach: the aircraft arrives too high, too fast, or not properly configured (gear, flaps, speed all within a defined window) at the specific point on the approach where the crew’s own airline rules require it to already be stable. Rather than try to salvage a rushed, out-of-parameters approach in the final seconds, the crew goes around and sets up to try again properly. A runway not yet clear of a preceding aircraft, an animal or vehicle incursion, a stray aircraft or vehicle in the arrival path (as at Reagan National), and genuine wind-shear or gusting conditions round out the real causes — in roughly that order of frequency.
What “stabilized” actually means
Airlines define a stabilized approach with hard numbers, not a feeling: by a set altitude on final — commonly 1,000 feet in poor weather, 500 feet in clear conditions — the aircraft needs to be on the correct flight path, at the correct approach speed within a narrow tolerance, in the landing configuration (gear down, flaps set), and with a sink rate within limits. If any one of those boxes isn’t ticked at that altitude, the approach is, by definition, unstabilized — and airline policy at nearly every major carrier requires a go-around at that point, not a judgment call in the moment about whether it still feels salvageable.
The sequence
From approach to go-around, in sequence
Approach in progress
Crew monitors airspeed, configuration and descent path against the airline's own stabilized-approach criteria.
Destabilizing event detected
Too fast, too high, unstable descent rate, ATC spacing issue, or the runway/approach path not confirmed clear — any one is sufficient.
"Go-around" called
a few hundred ftEither pilot can call it. Full go-around thrust is applied immediately, no debate, no second-guessing.
Climb and clean-up
Landing gear and flaps retracted on schedule, same climb performance used minutes earlier on takeoff.
Re-sequenced for another approach
ATC vectors the aircraft back into the pattern for a fresh, fully stabilized attempt.
The real risk is the opposite of what most passengers assume
The aviation-safety data here runs counter to instinct: it isn’t go-arounds that cause accidents, it’s the reluctance to call one. Continuing an unstabilized approach down to the runway is one of the leading contributing factors in landing accidents industry-wide, and research suggests crews only actually go around on a small fraction — an estimated 3–5% — of the approaches that technically warrant it under their own airline’s criteria. Aviation educators who cover incident analysis in depth — Mentour Pilot’s channel is built substantially around exactly this kind of case-by-case breakdown of real flights — return to this pattern repeatedly: the maneuver that looks the most dramatic to a passenger is, by the numbers, the safest possible response to a bad approach, and simulator recurrent training drills every airline pilot on the decision specifically so it never has to be reasoned through in real time — only recognized and executed.
Sources & Further Reading
Common Questions
Frequently Asked Questions
Does a go-around mean something is broken?
Almost never. The overwhelming majority of go-arounds are precautionary — an unstabilized approach, a runway not yet clear, or air traffic control needing more spacing behind a slower aircraft ahead. Mechanical issues are one of the least common reasons.
How often does it actually happen?
At the 30 busiest US airports, the FAA recorded go-arounds on about 0.39% of arrivals in fiscal year 2023 — roughly one in every 250 landings. A typical short-haul airline pilot might fly one or two go-arounds a year; a long-haul pilot may go several years between them.
Why don’t pilots just push through and land anyway if they’re close?
Because the data on this is stark the other way: the absence of a go-around when one was warranted is one of the leading risk factors in approach and landing accidents, and studies suggest only 3–5% of genuinely unstabilized approaches actually result in one — meaning pilots are, if anything, statistically too reluctant to go around, not too eager.
Is a go-around dangerous in itself?
No — it’s a fully rehearsed, briefed maneuver every crew practices in the simulator, using the same engines and the same climb performance the aircraft used minutes earlier on takeoff. It simply converts a landing back into a climb.