Late Runway Change on Approach: Crew Decision Guide

A runway change issued during taxi or on approach compresses decision-making into seconds. The margins for error narrow sharply: performance calculations may no longer apply, approach aids may differ, and crew coordination can fracture under time pressure. FlySafe analysis shows that unstructured responses to late runway changes remain a contributing factor in runway excursion events worldwide. According to the National Business Aviation Association (NBAA), business aviation recorded 17 runway excursions in 2022 alone — out of a far smaller number of total operations than the airline sector. The Flight Safety Foundation has noted that runway excursions on takeoff account for 21% of all such events, meaning the majority occur during landing, precisely the phase where late runway changes are most disruptive.

This bulletin provides a structured decision framework for flight crews confronting last-minute runway and route changes, drawing on publicly available guidance from ICAO, the FAA, EuroCockpit, and industry best practices.

Defining the Late Runway Change

Not every runway change carries the same operational threat. A change issued during flight planning or even early in the taxi sequence allows adequate time for recalculation, rebriefing, and system reprogramming. The critical distinction lies in timing.

As defined in guidance published by Infinidim, a late runway change is one that "has not been pre-briefed as part of the pre-descent Arrival Briefing." This definition applies symmetrically to departures: any change occurring after the crew has completed the departure briefing and begun to move constitutes a late change requiring a full procedural reset.

For departures, the recommended response is unambiguous. Once the aircraft has begun to move, the crew should find an appropriate place to stop so that all crew members can participate in the revised procedure. The Final FMC Performance Entry procedure must be actioned in full regardless of how minor the changes appear — from zero fuel weight verification through to MCP and VNAV Climb Page altitude and fuel checks. The departure briefing must then be updated, and the Departure Review and Before Takeoff Checklist must be completed or repeated.

For arrivals, the threat is compounded by the fact that the aircraft is already in a descending energy state with limited time available. The crew must assess whether adequate distance remains to accomplish all required setup tasks before reaching a stabilized approach gate.

Personal Minimums and the Decision to Accept

The first and most consequential decision a crew faces is whether to accept the runway change at all. According to BoldMethod, most airlines do not allow their pilots to accept runway changes below certain altitudes. This is not merely procedural conservatism — it reflects the operational reality that below a given altitude, the time required for reprogramming, rebriefing, and stabilization simply cannot be compressed further without introducing unacceptable risk.

Flight crews operating under Part 91 or business aviation rules, where such altitude gates may not be formally codified, should establish personal minimums in advance. A reasonable practice is to define a minimum altitude or distance from the field below which a runway change will not be accepted without requesting vectors for additional time or, if necessary, executing a go-around to set up for the new runway.

The EuroCockpit best practices document is explicit on this point: flight crews should not accept any runway change until "the appropriate set-up, planning, performance calculations (for multi-pilot operations this includes independent calculations and cross-checks by at least two pilots) and re-briefings are completed." If the time available does not permit this, the change should be declined or delayed.

The GAPPRE Checklist: A Structured Response

EuroCockpit provides a specific universal checklist tool for managing late changes, designated the GAPPRE 2.5 (Late) Change Checklist. While specific airline SOPs will vary, the GAPPRE framework offers a useful mnemonic structure that can be adapted to any operation:

Ground / Go-Around Assessment

Before accepting the change, assess whether a go-around or a stop on the ground (for departure changes) is the safer option. The question is not whether the change can be accomplished, but whether it can be accomplished with full procedural compliance.

Approach / Aircraft Setup

Load the new runway's approach into the flight management system. As noted by BoldMethod, one of the best things a crew can do is to get the new runway's approach loaded into the flight plan promptly. For visual approaches, the approach should be backed up with a navigation aid — whether GPS, ILS, or VOR — to that runway. This backup is not optional; it provides a cross-check against visual illusions and serves as a fallback if conditions deteriorate.

Performance

Runway length is the most critical variable. The crew must ask a fundamental question: is there enough room to land, or enough room to depart? BoldMethod emphasizes forming the habit of comparing calculated landing distance to actual runway length early in the process. This habit becomes essential during late changes, when the tendency to assume adequacy is strongest.

For multi-crew operations, performance calculations must be independently verified by at least two pilots with appropriate cross-checks. In calm or variable wind situations, the EuroCockpit guidance advises using a minimum of 5 knots tailwind for calculations — a conservative buffer that accounts for the variability inherent in surface wind reports.

Plates / Procedures

The new approach plate must be loaded, reviewed, and understood. This includes minimum descent altitudes, missed approach procedures, and any NOTAM-driven changes to the approach environment. Based on publicly available NOTAMs, runway construction, lighting outages, or temporary obstacles may affect the new runway differently than the original assignment.

Risk / Runway Environment

Assess the runway environment for factors that may not be immediately apparent. As described in guidance from the California Aeronautical University, runway illusions pose a particular threat during late changes because the crew has not had the benefit of pre-briefing the visual environment. A narrower runway than expected creates an illusion of being higher than actual altitude. A downsloping runway or surrounding terrain can make the aircraft appear closer to the ground than it is. Fog or haze can produce a false sensation of pitch-up. Featureless terrain on approach can lead to an insidiously lower-than-normal approach path.

These illusions are well-documented in stable conditions; during a late change, when cognitive loading is already elevated, their effect is amplified.

Execution Briefing

A compressed but complete briefing must be conducted before the approach is continued. This briefing covers the new approach type, minimums, missed approach procedure, and any unique considerations for the assigned runway. The crew must verbally confirm shared situational awareness.

ATC Coordination and Communication

The ICAO Runway Safety Maturity Checklist establishes that ATC procedures for late notice runway changes require assessment of aircraft type and performance capability, vectoring and resequencing to re-establish the aircraft profile, and tailwind effect on profile speed. ATC is required to provide position and distance information before the approach gate, defined as 5 nautical miles from the airport or 1 nautical mile from the final approach fix, whichever is farther.

Flight crews should not hesitate to request additional time, vectors, or a hold to accomplish the required setup. The ICAO framework recognizes that the responsibility is shared: ATC must assess whether the late change is operationally feasible for the specific aircraft type, and the crew must communicate if additional time or distance is needed.

Airline SOPs further require cross-cockpit communication protocols that minimize internal and external pressures and power gradients, ensuring that the decision to continue can be instantly challenged without recourse. This is particularly relevant during late runway changes, where the pressure to comply with ATC instructions can override sound judgment.

Route Changes: Permits, Slots, and Overflight Approvals

While runway changes are a tactical event, route changes during flight planning or en route present a broader operational challenge. As noted by Universal Weather and Aviation, certain regions — including those with strict overflight permit requirements — are particularly sensitive to revisions. It is recommended practice to have a third-party provider review the desired change before submitting requests.

Departing to a destination without required approvals is never recommended, as the aircraft may be required to divert before arrival or the operator may face penalties upon landing. In some scenarios, passengers may need to be repositioned to an alternate airport, or the trip may need to be delayed until all revised approvals — permits, airport slots, and prior permissions — can be obtained.

Affected routes should be evaluated against current NOTAM restrictions and airspace status. FlySafe analysis shows that route changes driven by airspace restrictions require particular attention to overflight approvals, as these are frequently non-transferable between routes and may carry lead times that exceed the available planning window.

The Pressure to Continue: Managing Cognitive Bias

The NBAA identifies a critical psychological factor in runway excursion events: the myth of saving a bad approach. The misguided notion that "I can save it" has led more than one pilot to continue an unstable approach to landing. This cognitive bias is directly applicable to late runway changes, where the sunk cost of the approach already flown creates pressure to continue rather than go around.

Recommendation: establish a firm policy that any approach resulting from a late runway change that is not stabilized by the published stabilization gate — typically 1,000 feet AGL for instrument conditions and 500 feet AGL for visual conditions — will result in an immediate go-around. No exceptions. The cost of a go-around is fuel and time. The cost of a runway excursion, as the NBAA notes, includes serious and sometimes fatal injuries, substantial aircraft damage, costly litigation, reputational harm, and increased regulatory scrutiny.

Instructors bear a particular responsibility in this area. The EuroCockpit guidance states that instructors should be role models in terms of defensive decision-making and creating an atmosphere that fosters pilot monitoring assertiveness. The culture of accepting late runway changes without adequate preparation is formed in training; it must be corrected there as well.

Key Takeaways

Airspace status and runway assignments are dynamic. Late changes will continue to occur. The differentiator between a routine operational event and a precursor to an excursion is the crew's response structure.

1. Define personal minimums for accepting late runway changes before the flight, not during.
2. Stop the aircraft (on departure) or request additional time (on approach) before accepting the change.
3. Use a structured checklist such as the GAPPRE framework to ensure no step is omitted under time pressure.
4. Independently verify performance calculations with at least two crew members.
5. Back up visual approaches with a navigation aid to the assigned runway.
6. Brief the runway environment for illusions, particularly unfamiliar runway widths and slopes.
7. Go around without hesitation if stabilization criteria are not met.

FlySafe continues to monitor airspace restrictions, NOTAM changes, and operational risk factors that affect route and runway planning worldwide. Flight crews and operators are encouraged to consult current NOTAM data and published safety bulletins before every operation.

Analysis based on publicly available data only.

Frequently Asked Questions

At what altitude should you stop accepting last-minute runway changes?

There is no universal altitude gate, but most airlines establish minimum altitudes below which runway changes are not accepted. Flight crews operating without formal company limits should set personal minimums that allow sufficient time and distance for full FMS reprogramming, performance verification, and a stabilized approach briefing. If adequate setup cannot be completed, a go-around should be executed.

Should you reprogram your flight plan immediately when ATC issues a runway change?

Loading the new approach into the FMS should be prioritized, but not at the expense of aircraft control or monitoring. The pilot flying should maintain the current clearance and flight path while the pilot monitoring begins the reprogramming sequence. As BoldMethod notes, getting the new runway's approach loaded is one of the most valuable steps — but it must be accomplished within a structured workflow, not as a rushed reaction.

When should you ask ATC for additional time to prepare for a runway change?

Immediately upon recognizing that the required setup cannot be completed within the available distance or time. ICAO guidance requires ATC to assess aircraft capability before issuing late changes, and controllers expect crews to communicate when additional vectors or a hold is needed. There is no operational penalty for requesting the time required to fly a safe approach.

What is the difference between briefing a side-step versus a full runway change to the opposite side of the airport?

A side-step to a parallel runway typically preserves the approach course, altitude constraints, and most performance calculations, requiring primarily a lateral offset briefing. A change to the opposite side of the airport may involve a completely different approach type, different terrain and obstacle environment, different runway length and slope, and potentially different wind components. The latter demands a full rebriefing and fresh performance assessment — effectively a new approach from the planning stage.