Recently I was given a runway change on pushback. Despite operating out of LAX where runway change is a real likelihood, it’s been quite a while since I’ve had happen to me on taxi. Once we got the changes made –  we ran the ECL Runway Change Checklist to tidy things up. Meanwhile our next refresher phase is bringing the runway change on approach event back into the sim. So, I thought it was time to revisit my PowerPoint on Runway Change.

The Procedures and Techniques document has several sections relating to Runway Change:

Runway Change On Departure

A crew make dozens of entries, selections and decisions during pre-flight that are tied to a specific runway and the departure direction associated. In addition, a complex mental model which includes terrain, weather, NOTAMS, procedural implications and more is established by briefing and other thought developing processes. All of these are typically accomplished through practised, familiar processes that happen in sequence and are the result of learned, practised behaviours.

Hence a runway change – especially once the aircraft has begun to taxi – is a significant disruption to many aspects of safe flight. After a runway change, dozens of changes are often required to ready the aircraft for flight, including changes to the aircraft setup:

  • Airways Clearance and ATIS
  • Take off performance calculation
  • Aircraft Configuration (Flaps, Thrust)
  • FMC (Runway, SID, Takeoff Performance)
  • MCP (Modes, Heading, Altitude)
  • Engine Out Procedure (Fix page, FMC EOAA)
  • Departure Briefing

While most of these changes are mechanical in nature and can be the result of a checklist – such as the Runway Change Procedure shown here – more complex is the development of a pilot’s mental model of the taxi, takeoff and flight departure. This can generally only be achieved – particularly across the flight deck – by repeating/updating the Departure Briefing once the changes have been determined, evaluated and implemented in the flight deck.

Often the first indication of a previously unknown runway change is the direction of pushback in the push/start clearance. In this case the most appropriate response is usually to cancel push/start, remain on stand and action the change. While this can result in a departure delay, it results in a better change action with less time pressure on the crew to accomplish what needs to be done.

Once the aircraft has begun to move, the recommended response to a runway change is to find an appropriate place for the aircraft to stop so all crew can be involved in the procedure. While relief crew can perform some useful preparation for a runway change during taxi, PF and PM should be fully engaged in ensuring safe taxi of the aircraft, rather than actioning a runway change procedure while the aircraft is moving.

The Final FMC Performance Entry procedure must be actioned in full no matter how small the changes involved in takeoff performance – from ZFW verification through to MCP and VNAV Climb Page Altitude/Fuel Checks. Once the Departure Briefing is updated the Departure Review and Before Takeoff Checklist must be completed (or repeated if necessary).

Note the Runway Change Checklist should be actioned after any runway change subsequent to completion of the Final FMC Performance Entry Procedure. The Runway/Clearance/Performance Change Checklist/Procedure is available in the FCOM SPs and the ECL. Note that this procedure can be actioned as a “Done List” (like Normal ECL) or a “Do List” (like NNM ECL).

Runway Change on Arrival

Much like Runway Change on Departure – changing your runway(Instrument Approach, and possibly STAR/Transition) during the descent after all your carefully planned, setup and briefed actions, based on what now turns out to be the wrong runway – can be a High Risk Event that brings with it significant Threat and opportunity for Error.

As before – a quick reference guide like the one shown here can be used as a mitigator against this thing going pear shaped – but is not a replacement for Airmanship and careful, thoughtful execution.

Unlike cruise – the descent environment is one where the Pilot Flying needs to fully focus on flying the aircraft and controlling flight path; even as the Pilot Monitoring becomes totally distracted by the requirement to consider and establish the changes required.

This is one of the few times where out flight tends necessarily towards a single pilot operation – I’m not endorsing this aspect; I’m just saying that this is what happens. So – recognise the threat and deal with it accordingly. During this time if the aircraft suffers flight path changes from ATC; or changes are require to comply with procedural restrictions – the PM should stop and return fully to the Pilot Monitoring role, before getting back on with setting up for the new runway.

Handing over so the PF can do the setup remains an option but handing the aircraft back and forth come with it’s own risks. Maintaining the mental model of situational awareness that is arrival/descent is something both pilots should be doing – but by it’s nature it tends to be something the PF is able to hang onto best if he/she remains the PF.

The Descent Checklist is an interesting one. Anytime you suffer a runway/approach change – or in fact if you divert to your alternate – the Descent checklist should be either re-run or at least it’s requirements considered in the procedural handling of the change.

Route 2 Usage

In the context of a runway change, Route 2 allows you to pre-build an alternative STAR/Transition/Approach and Missed Approach – to be activated when a runway change becomes evident. When activating Route 2 – you’ll need Activate Route 2; find the next waypoint relevant to your revised clearance, go direct to that waypoint and “ConfirmExecute”. Both pilot should give the new active route a check/crosscheck even if they validated Route 2 during Arrival preparations.

KLAX Runway Change / Side Step

KLAX publish side step minima on instrument approach charts for landing on the adjacent runway. In this context, adjacent means a like-numbered runway (eg: RW24L -> RW25R not RW24.. -> RW25..) It’s worth noting that KLAX ATC consider a “side step” to be an instrument approach, or more correctly a visual manoeuvre after an instrument approach, but essentially – NOT a visual approach.

Side Step minima and manoeuvres are in place to maximise traffic throughput in the event of an ILS failure on the landing (outer) runways at KLAX. For example, in the event of a localiser failure on RW25L, pilots might expect to be cleared for the ILS Approach for RW25R, with a sidestep to RW25L. Departures will continue off RW25R during this procedure.

Note that at KLAX all ILS’s radiate irrespective of the nominal “Landing” runway, unless ATIS/NOTAM’d otherwise.

The procedurally correct missed approach off a side step is that associated with the approach flown for the non-landing runway. However, KLAX ATC will always issue a specific heading/altitude for a missed approach of any approach into KLAX – see Missed Approach Procedure – KLAX.

Consideration should be given in the event of a Runway / Approach / Airport change to re-running the Descent and Approach checklists if the change occurs after they were completed. Not always necessary, not always practical – but worth a thought.

Approach to a Side Step Landing

The Bearing/VS information can be particularly useful when transitioning from an approach on one runway to a landing on another in less than optimal visual conditions. The aircraft transitions from an environment where a wealth of distance/altitude/profile information is provided to the PF, to an environment where even basic direct distance to the runway can be unavailable. While manoeuvring to final the Bearing/VS to the Landing Runway improves situational awareness with respect to the desired 3°approach slope. However, while every waypoint in the ARINC database is available to enter into the VNAV DESC page WPT/ALT prompt – a runway that is not active in the LEGS page is not. Of course.

When the FMC is setup for an approach to one runway (eg: KLAX RW06R) but the landing will be on another runway (RW06L) the FMC WPT/ALT prompt will not accept the RW06L waypoint. However if the crew select the landing runway in the DEP/ARR page (eg: RW06L ILS Approach ) without executing the modification, this inserts the waypoint into the LEGS page and therefore makes it available for use elsewhere (FIX, VNAV Off Path Desc, VNAV WPT/ALT) The runway waypoint can then be line selected into the scratchpad, the threshold crossing height added (eg: RW06L/0162) and the result inserted into the WPT/ALT field. The pending modification can then be erased – the waypoint and information will remain on the VNAV Descent or Fix Pages as desired.

Late Runway Change

Airports with multiple parallel runways, particularly closely spaced parallel runways such as KLAX, present crew with the potential challenge of a late runway change.

It’s worth noting that the difference between a runway change / runway side step / circling procedure is a blurred line. If changing the landing runway during an instrument approach is to be considered a circling approach – company A1 minima of 1000 ft AAL and 5000m visibility would be required.

A late runway changes presents a few unique challenges to today’s modern aircraft and is not a manoeuvre to be undertaken or accepted under impulse or without forethought – particular when …

  • Late runway change/sidestep has not been practised in the simulator;
  • Comes at the end of a ULH flight with a moderately fatigued (or worse) crew;
  • Is not reviewed, practised and encountered regularly;
  • Has not been pre-briefed as part of the pre-descent Arrival Briefing.

Of these four points, a thoughtful and concise briefing is a big factor completely within the control of the operating crew. A late runway change presents the following issues that must be addressed during the Arrival Briefing:

  • Weather – what minimum visual conditions will be acceptable to accept a runway change.
  • Altitude – what is the latest point at which the crew will accept a runway change. (A1 requires at least 2000 ft AAL)
  • Stabilisation Criteria – The A1 requires a stabilised approach by 1000 ft (or 500 ft for a visual circuit). Acceptance of a late runway change or sidestep procedure should result in the aircraft established within criteria by 500 ft AGL.
  • FMC Procedures – Crew need to pre-determine what their actions will be with respect to Runway and Approach Selection in the FMC during the manoeuvre. Nothing done or not done in the FMC affects the aircraft’s ability to land on a runway, but if the approach and runway is not selected, the published missed approach will not be available either – or worse, LNAV will engage and attempt to follow the wrong missed approach.

Note that at KLAX all ILS’s radiate irrespective of the nominal “Landing” runway, unless ATIS/NOTAM’d otherwise.

Missed Approach

Which missed approach will you fly? Which one do you have in the FMC? What do ATC expect? These questions should be discussed in the Arrival briefing and if necessary, clarified with ATC. Typically, if you’re cleared to land on RW25R, you expect to fly the RW25R ILS missed approach procedure. But part of the issue depends on when you agree to the runway change. It’s entirely acceptable to be cleared for “ILS Approach RW25L, cleared to land sidestep RW25R” based on the adjacent runway landing minima on the RW25L chart. In this case, based on the rules of manoeuvring for the runway after the instrument segment of an instrument approach – ATC would probably expect some form of the RW25L missed approach flown. Or would they?

Consideration should be given in the event of a Runway / Approach / Airport change to re-running the Descent and Approach checklists if the change occurs after they were completed. Not always necessary, not always practical – but worth a thought.


You may have noticed that I’ve included a TransferWise link on my web site. With my recent redundancy, I am attempting to generate a small, income from my past efforts on Infinidim. I have included a link to create an Account on TransferWise but in the end TransferWise is just a Bank and you can send me money using any normal transactional service that you can send to any bank – via PayPal, bPay or whatever you use, for anyone who may wish to offset some of the time and cost associated with maintaining my content. Many of you have expressed thanks and a willingness to contribute to my efforts towards content, and development and maintenance of the EBA Overtime/Allowance and ATO Allowance Tax calculator. I won’t be charging for anything I do or offer to others; but if you feel like throwing a few $$$ towards my efforts – that would be lovely, thanks.

If you wish to send me a monetary contribution and don’t wish to use TransferWise, please get in contact with me through LinkedIn or my gMail address (ken.pascoe (AT) for transfer details.

Regards, Ken Pascoe