From Accident to Rule

Aircraft Accident Reports: Every Crash Created a Rule

Landmark accidents in aviation history, based on official investigation reports: chain of events, root causes, subsequent rule changes and "What would you have done?" decision questions.

13 January 1982 · Washington, D.C., USA (14th Street Brid…

Air Florida 90 (1982): Iced Wings and an Erroneous EPR

Buzlanma

On 13 January 1982, a Boeing 737 departing Washington National took off with snow/ice on its wings and with low thrust because of ice-blocked Pt2 probes; it struck the 14th Street Bridge and crashed into the Potomac River. The NTSB cited deficiencies in de-icing/anti-icing and the failure to reject the take-off as the probable cause.

⚖ Clean aircraft principle: no take-off with snow/ice on the wing
2 August 2005 · Toronto/Lester B. Pearson International…

Air France 358 Toronto (2005): Runway Overrun in a Thunderstorm

Weather (wind shear, storms)

On 2 August 2005, an Air France 358 A340-313 overran the end of the runway on landing at Toronto during a severe thunderstorm, fell into a ravine and caught fire. All 309 persons on board were evacuated and there were no fatalities. The TSB issued recommendations on standards limiting approach and landing in convective weather and on the runway end safety area (RESA).

⚖ Clear standards limiting approach and landing in convective weather (Recommendation A07-01)
15 November 1987 · Denver, Colorado, USA (Stapleton Intern…

Continental 1713 Denver (1987): Ice at Takeoff, the Second De-icing

Buzlanma

On 15 November 1987, the DC-9 operating Continental flight 1713 rolled left during the takeoff roll in snowfall at Denver Stapleton and ran off the runway. The NTSB cited as the probable cause the captain's failure to have the aircraft de-iced a second time despite the delay after de-icing, and the contamination on the upper wing surface.

⚖ Prohibition on takeoff with a contaminated aircraft (clean aircraft concept)
12 November 1996 · Charkhi Dadri, Haryana, India (approxim…

The Charkhi Dadri Disaster (1996): A Misunderstood Altitude Clearance

Collision (in air / on runway)

On 12 November 1996, Saudia 763 (Boeing 747) and Kazakhstan 1907 (Il-76) collided in mid-air at 14,000 ft near Delhi; 349 people died. The Court determined the root cause to be the Il-76 descending without clearance to FL140 instead of maintaining its assigned FL150. Inadequate English proficiency, lack of CRM and the absence of ACAS came to the fore.

⚖ ACAS carriage requirement in India (CAR)
11 November 2018 · North-east of Lisbon, Portugal (departe…

Air Astana 1388 (2018): Aileron Cables Connected in Reverse

Maintenance error

On 11 November 2018 an Embraer 190 fresh out of heavy maintenance suffered a control problem after take-off because the aileron cables were crossed on both wings. The crew landed the aircraft at Beja after three approaches. The GPIAAF identified faulty installation and inadequate independent inspection as the probable cause.

⚖ Independent inspection: function and sense verification after work on critical controls
1 June 1999 · Little Rock, Arkansas, USA

American 1420 Little Rock (1999): The Spoilers Did Not Deploy

Weather (wind shear, storms)

On the night of 1 June 1999, American 1420 continued an approach to Little Rock as a thunderstorm moved over the airport, overran the end of the runway and crashed. According to the NTSB, the approach was not discontinued and deployment of the spoilers after touchdown was not verified. The report highlighted spoiler verification, the reverse thrust limit and stabilised approach guidance.

⚖ Two-pilot verification and callout that the spoiler is armed and has deployed
4 April 1977 · New Hope, Georgia, USA

Southern 242 (1977): Dual Engine Failure in a Thunderstorm Cell

Weather (wind shear, storms)

On 4 April 1977, Southern Airways Flight 242, a DC-9, entered a severe thunderstorm near Rome (Georgia); both engines ingested rain and hail and lost thrust. The crew made an emergency landing on a highway. The NTSB cited the lack of weather information and reliance on airborne weather radar as contributing factors.

⚖ Manufacturer's procedure for the DC-9: thrust changes in severe precipitation
2 July 1994 · Charlotte, North Carolina, USA

USAir 1016 Charlotte (1994): Microburst and Go-Around

Weather (wind shear, storms)

On 2 July 1994, a DC-9 flying an ILS approach to Charlotte entered the microburst of a rapidly developing thunderstorm. During the go-around the aircraft lost altitude and struck trees and a house near the runway threshold; 37 passengers died. The NTSB cited the continuation of the approach towards the storm, the late recognition of the wind shear and the failure to carry out the escape manoeuvre among the main causes.

⚖ Recommendation A-95-49: Wind shear escape manoeuvre in training
9 July 1982 · Kenner, Louisiana, USA (New Orleans Int…

Pan Am 759 (1982): Microburst Wind Shear on Take-off

Weather (wind shear, storms)

On 9 July 1982, a Boeing 727 departing New Orleans began to descend at about 100 ft shortly after take-off and struck trees beyond the end of the runway. The NTSB determined the probable cause to be wind shear caused by a microburst. The accident exposed the limits of ground-based detection systems and gaps in pilot training.

⚖ FAA 14 CFR 121.358: airborne wind shear warning/avoidance equipment
2 August 1985 · Dallas/Fort Worth International Airport…

Delta 191 Dallas (1985): Microburst and Wind Shear

Weather (wind shear, storms)

On 2 August 1985, Delta 191 flew into a microburst beneath a thunderstorm on the ILS approach to runway 17L at DFW and struck the ground about 6,300 ft short of the runway. The NTSB determined the probable causes to be the decision to continue the approach into the storm, the lack of low-altitude wind shear training and procedures, and the absence of real-time hazard information.

⚖ USA: Airborne wind shear equipment mandatory on airline aircraft (14 CFR 121.358)
24 June 1975 · John F. Kennedy International Airport…

Eastern 66 JFK (1975): An Approach Through the Storm

Weather (wind shear, storms)

On 24 June 1975, Eastern 66 (Boeing 727) was flying the ILS approach to JFK runway 22L when it encountered the downdraft of a very powerful thunderstorm and a sudden loss of headwind. The aircraft struck the approach light towers; 113 of the 124 people on board died. The accident accelerated awareness of low-level wind shear and the development of detection systems.

⚖ Low Level Windshear Alert System (LLWAS) developed
26 May 1991 · Dan Chang district, Suphan Buri, Thaila…

Lauda Air 004 (1991): In-Flight Thrust Reverser Deployment

Technical / structural failure

On 26 May 1991, a Boeing 767-300ER departing Bangkok lost flight path control in the climb when the left engine thrust reverser deployed without being commanded, and the aircraft broke up in the air. The Committee could not determine the specific cause of the deployment with certainty. Boeing redesigned the system and the FAA mandated the modification.

⚖ FAA AD 91-22-09: B767/PW4000 reverser system modification mandatory
7 July 2017 · San Francisco, California, USA

Air Canada 759 (2017): Approaching a Taxiway Instead of the Runway

Runway incidents

On a night in July 2017, an A320 about to land on runway 28R at San Francisco lined up with parallel taxiway C instead. Four aircraft were waiting on the taxiway. The crew descended to about 60 ft before going around, and no collision occurred. The NTSB highlighted the unnoticed closed-runway NOTAM, expectation bias and fatigue.

⚖ FAA SAFO 17010: Preventing approaches and landings on the wrong airport surface
27 August 2006 · Lexington, Kentucky, USA (Blue Grass Ai…

Comair 5191 (2006): Wrong-Runway Takeoff Accident

Runway incidents

On the morning of 27 August 2006, Comair 5191 took off from Runway 26, which is short and unsuitable for airline aircraft, instead of Runway 22. The aircraft overran the end of the runway and crashed. The NTSB highlighted the failure to confirm the runway position and non-pertinent conversation, and issued recommendations on runway confirmation, cockpit alerting systems and tower surveillance.

⚖ Runway number first in take-off clearance (FAA Notice N JO 7110.468)
12 July 2000 · Vienna-Schwechat, Austria

Hapag-Lloyd 3378 (2000): Gear Down, Fuel Exhausted

Fuel

On 12 July 2000 an A310 flying from Crete to Hannover continued on its way after the landing gear could not be retracted following take-off. Fuel consumption proved higher than expected. The aircraft was diverted to Vienna and, having run out of fuel, made a forced landing a short distance short of the runway. There were no fatalities; the aircraft was damaged beyond repair.

⚖ In an abnormal configuration, base calculations on fuel flow rather than the FMS fuel prediction
6 August 2005 · Off Capo Gallo, Palermo, Italy

Tuninter 1153 (2005): Wrong Fuel Indicator, Empty Tanks

Fuel

During maintenance, an ATR 42 fuel quantity indicator was fitted to an ATR 72 by mistake; the indicator showed more fuel than was actually on board and the low fuel warning did not activate. The aircraft ran out of fuel off Palermo and ditched; 16 of the 39 people on board died.

⚖ Redesign so the FQI cannot be fitted incorrectly (recommendation)
24 August 2001 · Lajes, Terceira Island, Azores, Portugal

Air Transat 236 (2001): Fuel Leak and Glide to the Azores

Fuel

On an A330 flying Toronto–Lisbon, an engine fuel line cracked. The crew took the warning for a fuel imbalance and applied the procedure from memory, which fed the leak. Both engines flamed out, the aircraft glided to Lajes and all 306 people on board survived.

⚖ With a fuel imbalance, first rule out a suspected leak
23 July 1983 · Gimli, Manitoba, Canada

Gimli Glider (1983): Kilograms or Pounds? The Fuel Calculation

Fuel

The Boeing 767 operating Air Canada 143 departed Montreal and Ottawa with fuel calculated using the wrong litres-to-weight conversion factor, and lost both engines in cruise. The flight crew landed the aircraft on a former military airstrip at Gimli; there were no fatalities. The report attributes the event not simply to a units mix-up but to interlinked human and organisational factors.

⚖ Fuel calculation: "fuel weight conversion factor" instead of "specific gravity" to guard against kg/lb confusion
4 November 2010 · Over Batam Island, Indonesia (after dep…

Qantas 32 (2010): A380 Engine Disintegration and the Oil Feed Pipe

Technical / structural failure

On 4 November 2010, the No. 2 engine of an A380 departing Singapore disintegrated in an uncontained failure at about 7,000 ft. Debris damaged many systems in the left wing and fuselage. The crew returned the aircraft to Singapore and landed safely. The ATSB identified the root cause as a manufacturing defect in an oil feed pipe inside the engine.

⚖ Rolls-Royce quality assurance system and non-conforming part management improved
19 July 1989 · Sioux City, Iowa, USA

United 232 Sioux City (1989): Landing Without Hydraulics, Loss of Control

Technical / structural failure

In 1989 the fan disc of the DC-10's tail engine disintegrated and all three hydraulic systems were lost. The crew reached Sioux City using asymmetric thrust alone; the aircraft struck the ground during the landing. The NTSB cited inadequate inspection and insufficient design protection as causes.

⚖ Modification of DC-10 hydraulic systems (AD 90-13-07)
25 January 1990 · Cove Neck, Long Island, New York, USA

Avianca 52 (1990): Out of Fuel, 'Emergency' Never Declared

Fuel

A Boeing 707 was held for about 1 hour 17 minutes because of bad weather and, on its second approach to JFK, ran out of fuel and crashed at Cove Neck. The NTSB gave as the probable cause the crew's failure to manage fuel and to clearly communicate the fuel situation to ATC. Lesson: report your fuel state clearly, in standard terms and, if necessary, with the word emergency.

⚖ Standard terminology for fuel states (recommendation)
28 December 1978 · Portland, Oregon, USA (approximately 6…

United 173 Portland (1978): The DC-8 That Ran Out of Fuel and the Birth of CRM

Fuel

While approaching Portland, United 173 held for about an hour because of a landing gear malfunction. During this time the fuel ran out and all engines stopped; the aircraft crashed into a suburb about 6 nmi east-southeast of the aerodrome. The NTSB highlighted inadequate monitoring of the fuel state and a lack of communication within the crew; the event became a key example in the development of crew resource management (CRM) training.

⚖ Recommendation A-79-17: Training in flight crew management (CRM) principles
27 March 1977 · Los Rodeos Airport, Tenerife (Canary Is…

The Tenerife Disaster (1977): A Lesson in Take-off Clearance and Fog-Bound Runways

Runway incidents

On 27 March 1977, in dense fog at Los Rodeos, KLM 4805 began its take-off run without a take-off clearance and collided with Pan Am 1736, which was taxiing on the runway. CIAIAC gave the take-off without clearance as the primary cause; radio phraseology and tension contributed.

⚖ Strict and full compliance: instructions and clearances
22 August 2015 · Shoreham, West Sussex, England (A27 Sho…

Shoreham 2015: Loop and Escape Manoeuvre at an Airshow

Human factors and CRMGeneral aviation

On 22 August 2015, a Hawker Hunter T7 failed to complete a loop-type manoeuvre (a bent loop) at the Shoreham airshow and crashed onto the A27 road. Eleven people were killed. The AAIB reported that the manoeuvre began with low speed, low thrust and a low entry height, that no escape manoeuvre was flown, and that there were weaknesses in airshow safety oversight.

⚖ Ex-military jets: only low-energy flypasts over land

How are these reports prepared?

Each report is based on the official investigation published by the investigating authority (NTSB, BEA, AAIB, Türkiye's Transportation Safety Investigation Centre, etc.) final report is the basis; the source is given as a link at the bottom of each page. The aim is not to blame anyone, but to learn lessons so that the same error is not repeated. For this reason, the names of crew members and passengers are not used.

The pages are for training purposes; when quoting a detail from a report, always refer to the official report itself. To solve related exam questions: Human Performance · Operational Procedures · Meteorology.