
Qantas Flight 72
Incorrect sensor-unit data met a flight-control design limitation, causing two sudden pitch-downs and serious cabin injuries.
Incident date:
LEVEL 3 Final report
Causes
Official investigators identified control system damage in 4 of the incidents we cover, from 1974 to 2008. Each account explains how it arose in that case. A shared topic does not mean the same cause.
Last updated
| Date | Flight | Aircraft | Location | Fatalities | Report status |
|---|---|---|---|---|---|
| 7 October 2008 | Qantas Flight 72 | Airbus A330-303 | Indian Ocean, 154 km west of Learmonth, Western Australia | 0 | LEVEL 3 Final report |
| 12 August 1985 | Japan Airlines Flight 123 | Boeing 747SR-100 | Mountainous terrain in Ueno, Gunma, Japan | 520 fatalities | LEVEL 3 Final report |
| 25 May 1979 | American Airlines Flight 191 | McDonnell Douglas DC-10-10 | Open field and trailer park northwest of Chicago O'Hare runway 32R | 273: 271 aboard and two on the ground | LEVEL 3 Final report |
| 3 March 1974 | Turkish Airlines Flight 981 | McDonnell Douglas DC-10-10 | Ermenonville forest, France | 346 fatalities | LEVEL 3 Final report |

Incorrect sensor-unit data met a flight-control design limitation, causing two sudden pitch-downs and serious cabin injuries.
Incident date:
LEVEL 3 Final report

An improperly repaired pressure bulkhead failed in flight, damaging the tail and all four hydraulic systems. The crew struggled with severe oscillations before the aircraft struck mountainous terrain.
Incident date:
LEVEL 3 Final report

Maintenance damage led to engine-pylon separation, slat retraction and lost warnings during takeoff, leaving the crew without an adequate chance to prevent an asymmetric stall.
Incident date:
LEVEL 3 Final report

A cargo door that appeared secured opened during climb. Rapid depressurisation collapsed the cabin floor and disabled controls routed beneath it, leaving the crew unable to recover.
Incident date:
LEVEL 3 Final report