FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Qantas Flight 72

7 Oct 2008 · Indian Ocean, 80 nmi from Learmonth

Airbus A330-303 · In-flight upset due to software error resulting in two pitch-downs

From Singapore Changi Airport (SIN) to Perth International Airport (PER)

Report a problem

Event

NTSB case
DCA09WA005
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Unknown · led by another country; figures from NTSB notifications
Event fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
Occupants
315
Survivors
315
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
119
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Not recorded

Airbus A330-303

Flight
QF72
Aircraft type
Airbus A330
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
VH-QPA
Operator
Qantas
Onboard fatalities
0
Route
From Singapore Changi Airport (SIN)To Perth International Airport (PER)
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Non-U.S., Commercial
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Not recorded
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Not recorded
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Aircraft › Aircraft systems
  • Organizational issues › Development

From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

Qantas Flight 72 (QF72) was a scheduled flight from Singapore Changi Airport to Perth Airport by an Airbus A330. On 7 October 2008, the flight made an emergency landing at Learmonth Airport near the town of Exmouth, Western Australia, following an in-flight upset 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. At Learmonth, the plane was met by the Royal Flying Doctor Service of Australia and CareFlight. Fourteen people were airlifted to Perth for hospitalisation, with thirty-nine others also attending hospital. In all, one crew member and eleven passengers suffered serious injuries, while eight crew and ninety-nine passengers suffered minor injuries. 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

The aircraft involved was an Airbus A330-303 twin turbofan aircraft, registered as VH-QPA.

The crew was led by Captain Kevin Sullivan (53), a former US Navy (1977–1986) pilot who had moved to Australia. The first officer was Peter Lipsett, and the second officer was Ross Hales. 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.

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.

Flight details

On 7 October 2008 at 09:32 Singapore Standard Time (SST), Qantas Flight 72, with 315 people on board, departed Changi Airport in Singapore en route to Perth Airport in Australia. By 10:01, the aircraft had reached its cruising altitude of around 37000 ft and was maintaining a cruising speed of Mach 0.82.

The incident started at 12:40:26 Australian Western Standard Time (AWST), 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 electronic centralised aircraft monitor, 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 remained disengaged for the remainder of the flight.

At 12:42:27, the aircraft made a sudden, uncommanded pitch-down manoeuvre, experiencing −0.8 g, reaching 8.4 degrees pitch down and rapidly descending 650 ft. 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, a 3.5 degree down angle, and a loss of altitude of 400 ft; the flight crew was able to re-establish the aircraft's assigned level flight 16 seconds later. Unrestrained (and even some restrained) passengers and crew were flung around the cabin or struck by overhead luggage which broke through the 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.

Investigation and cause

Investigation

The Australian Transport Safety Bureau (ATSB) investigation was supported by the Australian Civil Aviation Safety Authority, Qantas, the French Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA) and Airbus. Copies of data from the aircraft's flight data recorder and cockpit voice recorder were sent to the BEA and Airbus.

The aircraft was equipped with an air data inertial reference unit (ADIRU) manufactured by Northrop Grumman; investigators sent the unit to Northrop Grumman in the United States for further testing.

On 15 January 2009, the European Aviation Safety Agency (EASA) issued an emergency airworthiness directive 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 ATSB identified a fault occurring within the number-one 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.

The initial effects of the fault were:

False (contradictory) stall and overspeed warnings

Loss of altitude information on the captain's primary flight display

Several electronic centralised aircraft monitor 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:

The flight control computers commanding a nose-down aircraft movement, resulting in the aircraft pitching down to a maximum of about 8.5 degrees

The triggering of a flight-control primary computer (FCPC) pitch fault.

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 FCPC software of the Airbus A330/A340, and a failure mode affecting one of the aircraft’s three ADIRUs. The design limitation meant that in a very rare and specific situation, multiple spikes in AOA data from one of the ADIRUs could result in the FCPCs commanding the aircraft to pitch down."

Text from the Wikipedia article “Qantas Flight 72” (revision 1371696492, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

NTSB narrative

On October 7, 2008, at 12:42 local time, a Qantas Airways Airbus A330-300, registration VH-QPA, experienced an abrupt pitch down maneuver during cruise near the Learmonth Aerodrome. The flight crew diverted to Learmonth, Australia. The flight was a scheduled passenger flight from Singapore to Perth, Australia. There were 2 crew and 20 passengers who were seriously injured during the pitch event. This accident investigation is being led by the Australian Transport Safety Bureau (ATSB). The U.S. National Transportation Safety Board (NTSB) and the Bureau d'Enquêtes et d'Analyses pour la Sécurité de l'Aviation civile (BEA) of France have provided accredited representatives to assist the ATSB with their investigation.

All inquiries concerning this investigation should be directed to:

Australian Transport Safety Bureau (ATSB) P.O. Box 967, Civic Square Canberra A.C.T. 2608 Australia Website: http://www.atsb.gov.au

Verbatim NTSB factual narrative from the NTSB dataset

Sources

Wikipedia article: Qantas Flight 72
Article
Qantas Flight 72
Revision
1371696492 · 2026-08-27 · retrieved 2026-09-18
Wikidata
Q3562612
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA09WA005
Event ID
20081031X50731
Case number
DCA09WA005
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
Record
Wikipedia article "Qantas Flight 72" (page 19773101, revision 1371696492); merged with NTSB case DCA09WA005 (events / aircraft)
Date
Wikipedia infobox: date
Place and country
Wikipedia infobox: site; country from Wikidata (P17)
Map position
Wikipedia: Wikipedia article coordinates
Aircraft, operator and route
Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA09WA005
Operation
airline flight number in the infobox
Fatalities
Wikipedia: Wikipedia infobox: aircraft fatalities
Ground fatalities
Wikipedia: not stated in the Wikipedia infobox
Summary
Wikipedia infobox: summary
Source notes (2)
  • One occurrence in two sources, merged: the Wikipedia article "Qantas Flight 72" and NTSB case DCA09WA005, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
  • Filled from the NTSB case API where the bulk record had no value: coordinates. Values present in the bulk record are kept.