Back to home pageVH-VYE Inadvertent Glideslope Capture at FL390

Home > Accident News


Illustrated technical information covering Vol 2 Over 800 multi-choice systems questions Close up photos of internal and external components Illustrated history and description of all variants of 737 Databases and reports of all the major 737 accidents & incidents History and Development of the Boeing 737 - MAX General flightdeck views of each generation of 737's Technical presentations of 737 systems by Chris Brady Detailed tech specs of every series of 737 A collection of my favourite photographs that I have taken of or from the 737 Press reports of orders and deliveries Details about 737 production methods A compilation of links to other sites with useful 737 content Study notes and technical information A compilation of links to major 737 news stories with a downloadable archive A quick concise overview of the pages on this site


28 Apr 2015 - The ATSB has published its final report into the flight path management occurence involving Boeing 737-800, VH-VYE over Queensland on 23 Feb 2013.

What Happened

On the evening of 25 February 2013, a Boeing 737-838 aircraft, registered VH-VYE and operated by Qantas Airways Limited, was conducting a scheduled passenger service from Canberra Airport, Australian Capital Territory to Brisbane Airport, Queensland.

At 2110 Eastern Daylight-saving Time, about 115 NM (213 km) from Brisbane, and as the aircraft approached the descent point for Brisbane Airport, the aircraft’s autopilot unexpectedly commenced climbing the aircraft. The crew disconnected the autopilot and descended the aircraft.

During the descent to an air traffic control-cleared level the aircraft rolled left and deviated laterally from the flight plan track. The autopilot was subsequently re-engaged and the aircraft was manoeuvred to re-intercept the flight-planned track. The remainder of the flight was uneventful and the aircraft landed on runway 01 at Brisbane Airport.


The full report is available here

See more details about the book

All of the information, photographs & schematics from this website and much more is now available in a 374 page printed book or in electronic format.

*** Updated 14 Nov 2021 ***

The 737 Tech Site on Facebook The 737 Tech Site on Twitter The 737 Tech Site on Instagram The 737 Tech Site on Instagram

What the ATSB found

The ATSB found that the auto-flight system allowed the capture of the Brisbane Airport runway 01 instrument landing system (ILS) glideslope and the aircraft unexpectedly climbed to intercept the signal, which had itself been affected by atmospheric refraction. The preconditions for the occurrence were that the Canberra and Brisbane ILS frequencies were the same, this frequency remained active in the aircraft’s navigation system and, shortly after reaching top of climb out of Canberra, the auto-flight system’s approach mode was inadvertently armed. This meant that when the aircraft was within range of the Brisbane ILS signal, the glideslope would become the active vertical flight mode. The configuration of the auto-flight system logic on the operator’s Boeing 737 fleet allowed the aircraft to capture and follow a glideslope signal despite not being on the localiser.

The ATSB also found that contrary to the flight crew’s intent, after dis-engaging the autopilot, it was not re-engaged, resulting in a lateral deviation from the planned flight path.

Safety message

This occurrence highlights the human performance limitations with respect to monitoring and detecting mode reversions and flight mode annunciator (FMA) changes in automated aircraft. Flight crew are reminded of the importance of regularly identifying and confirming the flight modes displayed on the FMA.

Vertical profile of the flight (ATSB Report)



From the evidence available, the following findings are made with respect to the flight path deviation involving Boeing 737-838, registered VH-VYE, about 213 km south-south-east of Brisbane Airport, Queensland on 25 February 2013. These findings should not be read as apportioning blame or liability to any particular organisation or individual.

Contributing factors

• Depending on the auto-flight and instrument landing system frequency selections by the flight crew, the configuration of the auto-flight system logic on the operator's Boeing 737 fleet allowed the aircraft to capture and follow a glideslope signal despite not being established on the localiser.

• The flight crew inadvertently selected the approach push-button after reaching cruising altitude, which was not detected for an extended period, allowing the aircraft's auto-flight system to capture the glideslope signal at cruise altitude while still about 213 km from the destination.

• Following departure from Canberra the instrument landing system frequency for that airport, which was the same as for the system at Brisbane Airport, remained active on the aircraft’s navigation control panel, permitting the auto-flight system to capture and follow the glideslope signal as the aircraft approached Brisbane.

• Contrary to their intent, the flight crew did not re-engage the autopilot after the climb associated with the glideslope capture approaching Brisbane, resulting in the aircraft laterally deviating from the flight planned track.

Other factors that increased risk

• The captain conducted significant non-aviation work when free from flight duty, which had the potential to lead to ineffective rest and cumulative fatigue.

Footer block