What is a go-around?
A go-around is when a pilot aborts a landing attempt and climbs back to a safe altitude. It can be initiated by the pilot (unstable approach, runway not visible) or instructed by the controller (traffic on the runway, spacing too tight).
Common triggers
- Unstable approach - too fast, too high, not aligned with the runway
- Runway not clear - previous aircraft hasn't exited, vehicle on the runway
- Wind shear - sudden change in wind speed or direction on final
- Visibility - can't see the runway at decision height (200ft on ILS)
- Controller instruction - spacing issue, go-around for re-sequencing
What happens after
The pilot climbs to a predetermined altitude (typically 3,000ft) and follows the missed approach procedure. The controller then re-sequences the aircraft - either vectoring for another approach or putting them back in the arrival sequence.
Go-arounds are not emergencies. They're a normal safety procedure. Controllers expect them and plan accordingly.
In radarcontrol.io
Controller-initiated: Issue ga to instruct a go-around. The aircraft climbs to 3,000ft on runway heading and becomes controllable again for re-vectoring. Costs -50 points.
Automatic missed approach: If you forget to hand the aircraft off to tower (twr) before it reaches decision height (200ft AGL), the pilot will execute a missed approach on their own. They'll announce "going around" on frequency and climb to 3,000ft on runway heading. This costs -75 points - more than a manual go-around since it represents a controller error.
After a go-around, the aircraft is controllable again. Re-vector it for another approach or re-sequence with other traffic.