Qantas Flight 72

Qantas Flight 72

VH-QPA, the aircraft involved, pictured in 2016
Accident
Date	7 October 2008
Summary	In-flight upset due to software error resulting in two pitch-downs
Site	80NM from Learmonth 22°14′06″S 114°05′18″E / 22.23500°S 114.08833°E / -22.23500; 114.08833Coordinates: 22°14′06″S 114°05′18″E / 22.23500°S 114.08833°E / -22.23500; 114.08833
Aircraft
Aircraft type	Airbus A330-303
Aircraft name	Kununurra
Operator	Qantas
Registration	VH-QPA
Flight origin	Singapore Changi Airport, Singapore
Destination	Perth Airport, Australia
Occupants	315
Passengers	303
Crew	12
Fatalities	0
Injuries	119
Survivors	315

Qantas Flight 72 (QF72) was a scheduled flight from Singapore Changi Airport to Perth Airport. On 7 October 2008, the flight made an emergency landing at Learmonth Airport near the town of Exmouth, Western Australia following an inflight accident that included a pair of sudden, uncommanded pitch-down manoeuvres that caused severe injuries -- including fractures, lacerations and spinal injuries -- to several of the passengers and crew.^{[1][2][3][4][5]} At Learmonth, the plane was met by the Royal Flying Doctor Service of Australia and CareFlight.^[6][7] Fourteen people were airlifted to Perth for hospitalisation, with 39 others also attending hospital.^{[8][9][10][11]} In all, one crew member and 11 passengers suffered serious injuries, while eight crew and 99 passengers suffered minor injuries.^[12] The Australian Transport Safety Bureau (ATSB) investigation found a fault with one of the aircraft's three air data inertial reference units (ADIRUs) and a previously unknown software design limitation of the Airbus A330's fly-by-wire flight control primary computer (FCPC).

Background[]

On 7 October 2008, Qantas Flight 72 was scheduled to fly from Singapore Changi Airport (SIN) to Perth Airport (PER). The aircraft, VH-QPA, was delivered new to Qantas on 26 November 2003, initially as an A330-301. In November 2004, it had a change in the type of engines fitted, and was re-designated as an Airbus A330-303.^[13]

The crew was led by Captain Kevin Sullivan (53), a former US Navy (1977-1986) pilot. The first officer was Peter Lipsett, and the second officer was Ross Hales. In addition to the three flight-deck crew members, there were nine cabin crew members and 303 passengers, for a total of 315 people on board.^[14] Captain Sullivan had 13,592 flight hours, including 2,453 hours on the Airbus A330. First Officer Lipsett had 11,650 flight hours, with 1,870 of them on the Airbus A330. Second Officer Hales had 2,070 flight hours, with 480 of them on the Airbus A330.^[15]

Flight details[]

On 7 October 2008 at 09:32 SST, Qantas Flight 72, with 315 people on board, departed Singapore on a scheduled flight to Perth, Western Australia. By 10:01, the aircraft had reached its cruising altitude of around 37,000 feet (11,000 m) and was maintaining a cruising speed of Mach 0.82.

The incident started at 12:40:26 WST, when one of the aircraft's three air data inertial reference units (ADIRUs) started providing incorrect data to the flight computer. In response to the anomalous data, the autopilot disengaged automatically. A few seconds later, the pilots received electronic messages on the aircraft's ECAM, warning them of an irregularity with the autopilot and inertial reference systems, and contradictory audible stall and overspeed warnings. During this time, the captain began to control the aircraft manually. The autopilot was then re-engaged and the aircraft started to return to the prior selected flight level. The autopilot was disengaged by the crew after about 15 seconds and would remain disengaged for the remainder of the flight.

At 12:42:27, the aircraft made a sudden, uncommanded pitch down manoeuvre, experiencing –0.8 g,^{[note 1]} reaching 8.4 degrees pitch down and rapidly descending 650 feet (200 m). Twenty seconds later, the pilots were able to return the aircraft to the assigned cruise flight level, FL370. At 12:45:08, the aircraft made a second uncommanded manoeuvre of a similar nature, this time causing an acceleration of +0.2 g,^{[note 2]} a 3.5 degree down angle, and a loss of altitude of 400 feet (120 m); the flight crew was able to re-establish the aircraft's assigned level flight 16 seconds later.^[16][17] Unrestrained (and even some restrained) passengers and crew were flung around the cabin or crushed by overhead luggage, as well as crashing with and through overhead compartment doors. The pilots stabilised the plane and declared a state of alert, which was later updated to mayday when the extent of injuries was relayed to the flight crew.^[8][18]

Investigation[]

The ATSB investigation was supported by the Australian Civil Aviation Safety Authority (CASA), Qantas, the French Bureau d'Enquêtes et d'Analyses pour la sécurité de l'Aviation Civile (BEA) and Airbus.^[3] Copies of data from the aircraft's flight data recorder and cockpit voice recorder were sent to the BEA and Airbus.^[17]

The aircraft was equipped with an ADIRU manufactured by Northrop Grumman; investigators sent the unit to Northrop Grumman in the United States for further testing.^[19][20] On 15 January 2009, the European Aviation Safety Agency (EASA) issued an emergency airworthiness directive^[21] to address the problem of A330 and A340 aircraft, equipped with the Northrop-Grumman ADIRUs, incorrectly responding to a defective inertial reference.

In a preliminary report, the Australian Transport Safety Bureau (ATSB) identified a fault occurring within the Number 1 ADIRU as the "likely origin of the event"; the ADIRU, one of three such devices on the aircraft, began to supply incorrect data to the other aircraft systems.^[22][23]

The initial effects of the fault were:^[4]

• false (contradictory) stall and overspeed warnings
• loss of altitude information on the captain's primary flight display
• several Electronic Centralised Aircraft Monitor (ECAM) system warnings

About two minutes later, ADIRU No. 1, which was providing data to the captain's primary flight display, provided very high (and false) indications for the aircraft's angle of attack (AOA), leading to:^[4]

• the flight control computers commanding a nose-down aircraft movement, resulting in the aircraft pitching down to a maximum of about 8.5 degrees, and
• the triggering of a Flight Control Primary Computer (FCPC) pitch fault.

FCPC faulty design[]

Angle of attack (AOA) is a critically important flight parameter, and full-authority flight control systems, such as those equipping A330/A340 aircraft, require accurate AOA data to function properly. The aircraft was fitted with three ADIRUs to provide redundancy for fault tolerance, and the FCPCs used the three independent AOA values to check their consistency. In the usual case, when all three AOA values were valid and consistent, the average value of AOA 1 and AOA 2 was used by the FCPCs for their computations. If either AOA 1 or AOA 2 significantly deviated from the other two values, the FCPCs used a memorised value for 1.2 seconds. The FCPC algorithm was very effective, but it could not correctly manage a scenario where there were multiple spikes in either AOA 1 or AOA 2 that were 1.2 seconds apart - i.e., if the 1.2-second period of use of the memorised value happened to end while another spike was happening.

As with other safety-critical systems, the development of the A330/A340 flight control system during 1991 and 1992 had many elements to minimise the risk of a design error. These included peer reviews, a system safety assessment (SSA), and testing and simulations to verify and validate the system requirements. None of these activities identified the design limitation in the FCPC's AOA algorithm.

The ADIRU failure mode had not been previously encountered, or identified by the ADIRU manufacturer in its safety analysis activities. Overall, the design, verification and validation processes used by the aircraft manufacturer did not fully consider the potential effects of frequent spikes in data from an ADIRU.

Airbus stated that it was not aware of a similar incident occurring previously on an Airbus aircraft. It released an Operators Information Telex to operators of A330 and A340 aircraft with procedural recommendations and checklists to minimise risk in the event of a similar incident.^[4]

Final report[]

Analysis[]

After detailed forensic analysis of the FDR, the FCPC software, and the ADIRU, it was determined that the CPU of the ADIRU corrupted the angle of attack (AOA) data. The exact nature of the corruption was that the ADIRU CPU erroneously re-labelled the altitude data word so that the binary data that represented 37,012 (the altitude at the time of the incident) would represent an angle of attack of 50.625 degrees. The FCPC then processed the erroneously high AOA data, triggering the high-AOA protection mode, which sent a command to the electrical flight control system (EFCS) to pitch the nose down.^[15]

Potential trigger types[]

A number of potential trigger types were investigated, including software bugs, software corruption, hardware faults, electromagnetic interference and the secondary high-energy particles generated by cosmic rays. Although a definitive conclusion could not be reached, there was sufficient information from multiple sources to conclude that most of the potential triggers were very unlikely to have been involved. A much more likely scenario was that a marginal hardware weakness of some form made the units susceptible to the effects of some type of environmental factor, which triggered the failure mode.^[15]

The ATSB assessment of speculation that possible interference from Naval Communication Station Harold E. Holt or passenger personal electronic devices could have been involved was 'extremely unlikely'.^[15]

Conclusion[]

The ATSB's final report, issued on 19 December 2011, concluded that the incident "occurred due to the combination of a design limitation in the flight control primary computer (FCPC) software of the Airbus A330/A340, and a failure mode affecting one of the aircraft’s three air data inertial reference units (ADIRUs). The design limitation meant that, in a very rare and specific situation, multiple spikes in angle of attack (AOA) data from one of the ADIRUs could result in the FCPCs commanding the aircraft to pitch down."^[15]

Subsequent Qantas Flight 71 incident[]

On 27 December 2008, a Qantas A330-300 aircraft operating from Perth to Singapore was involved in an occurrence approximately 260 nautical miles (480 km) north-west of Perth and 350 nautical miles (650 km) south of Learmonth Airport at 1729 WST, while flying at FL360. The autopilot disconnected and the crew received an alert indicating a problem with ADIRU #1. The crew performed the revised procedure released by Airbus after the earlier accident and returned to Perth uneventfully. The ATSB included the incident in their existing accident investigation of Flight 72.^[24] The incident again fuelled media speculation regarding the significance of the aforementioned Harold E. Holt facility, with the Australian and International Pilots Association calling for commercial aircraft to be barred from the area as a precaution until the events could be better understood,^[25][26] while the manager of the facility claimed that it was "highly, highly unlikely" that any interference had been caused.^[27]

Aftermath[]

VH-QPA sustained minor damage; it was repaired and returned to service with Qantas.^[28]

Compensation[]

In the aftermath of the accident, Qantas offered compensation to all passengers. The airline announced it would refund the cost of all travel on their itineraries covering the accident flight, offer a voucher equivalent to a return trip to London applicable to their class of travel and pay for medical expenses arising from the accident. Further compensation claims would be considered on a case-by-case basis,^[29] with several passengers from the flight pursuing legal action against Qantas. One couple asserted that they were wearing their seatbelts at the time of the incident and questioned Qantas' handling of their cases.^[30][31] Permanently injured flight attendant Fuzzy Maiava was advised not to take an NZ$35,000 compensation payment from Qantas so that he could take part in a class action lawsuit against Airbus and Northrop Grumman. However, the case was dismissed on procedural grounds, leaving Maiava without compensation. He remains unable to work or drive a vehicle.^[32]

Dramatisation and book[]

In 2018, the events of Qantas 72 were featured in "Free Fall" (Season 18, Episode 7) in the Canadian TV series Mayday.^[33] In May 2019, a book on the incident by Kevin Sullivan (captain of the flight) was published in Australia.^[34] In June 2019, Seven Network's Sunday Night featured the events of Qantas 72 through recollections of several passengers and crew that were on board the flight, including Sullivan, flight attendant Fuzzy Maiava, as well as comments from US Airways Flight 1549 captain Chesley "Sully" Sullenberger. However, Qantas has banned any of its current employees from being interviewed about the incident, including Diana Casey, an off-duty customer service manager who helped numerous others on board, despite being injured herself.^[35]

See also[]

• List of accidents and incidents involving commercial aircraft
• Lion Air Flight 610
• Ethiopian Airlines Flight 302
• Boeing 737 MAX groundings

Notes[]

References[]

Further reading[]

External links[]

• Australian Transport Safety Bureau — final report and materials
• Perth Now — photographs of the cabin