Incidents
Browse all 74 published incidents, ordered by incident date, newest first.
FZ1073 diverted to Tabuk after the co-pilot allegedly attacked the captain in the cockpit. Everyone aboard survived. The UAE Attorney General has since said investigators found a planned attack, including an intent to crash the aircraft into Ben Gurion Airport's passenger terminal. These are prosecution findings; no final investigation report has been published.
Incident date:
LEVEL 1 Officially confirmed
An Amazon cargo service landed far down Miami's runway 30 and continued through the airport boundary, striking two occupied vehicles.
Incident date:
LEVEL 2 Preliminary findings
A landing Jazz Aviation CRJ900 struck a rescue truck crossing its runway during a separate airport emergency.
Incident date:
LEVEL 2 Preliminary findings
A runway inspection vehicle escaped onto a taxiway about five seconds before a departing cargo aircraft rotated nearby. Radio clarity and incomplete visual checks left neither participant aware of the conflict.
Incident date:
LEVEL 3 Final report
A cargo MD-11 lost its left engine and pylon during takeoff. It failed to climb clear of buildings south of Louisville's airport.
Incident date:
LEVEL 2 Preliminary findings
A takeoff shock caused severe inertial drift, repeated automation failures and a go-around before a safe Heathrow landing.
Incident date:
LEVEL 3 Final report
Three windshear escapes and a refused diversion left a passenger jet landing at Manchester with 363 kg of fuel.
Incident date:
LEVEL 3 Final report
Five people were seriously injured when the A320 entered a developing convective cell. Late weather detection and incomplete injury communication shaped the consequences.
Incident date:
LEVEL 3 Final report
Thermal relief plugs released tire pressure during takeoff. The left wheels failed, the aircraft tilted, and smoke and fire prompted an evacuation.
Incident date:
LEVEL 3 Final report
An altitude-reference mismatch brought an An-24 approximately 600 metres below the intended approach height near Tynda.
Incident date:
LEVEL 3 Final report
A Boeing 787-8 lost thrust shortly after liftoff from Ahmedabad and struck buildings beyond the airport.
Incident date:
LEVEL 2 Preliminary findings
A regional airliner and an Army helicopter met over the Potomac. The final investigation found failures in route design, visual separation, workload and safety oversight.
Incident date:
LEVEL 3 Final report
A Boeing 737-800 landed with its landing gear retracted, overran runway 19 at Muan and struck an obstacle beyond it.
Incident date:
LEVEL 2 Preliminary findings
A turbine blade fatigue failure reduced left-engine power. Airspeed decayed during the initial climb and the cargo aircraft crashed.
Incident date:
LEVEL 3 Final report
A turbine blade fatigue failure caused an engine fire on low approach. The aircraft landed safely, but the evacuation exposed further hazards.
Incident date:
LEVEL 3 Final report
Nose-down trim progressively reduced the elevator authority available for landing. The left main gear separated on touchdown.
Incident date:
LEVEL 3 Final report
Rainwater reached electrical equipment in a cargo 747, disabling critical systems before an icing encounter corrupted every airspeed indicator.
Incident date:
LEVEL 3 Final report
A missing set of securing bolts let a door plug move out of position. The crew returned to Portland with everyone alive.
Incident date:
LEVEL 3 Final report
An arriving JAL A350 struck a Coast Guard DHC-8 on runway 34R. Interim evidence describes a clearance misunderstanding and undetected runway occupancy; causes remain under investigation.
Incident date:
LEVEL 2 Preliminary findings
A second unstable approach ended with in-flight reverse thrust, loss of control and a crash beside a gravel runway. All ten occupants survived.
Incident date:
LEVEL 3 Final report
A Q300 descended 2,500 ft below its planned profile at night before the captain recognised the error and climbed.
Incident date:
LEVEL 3 Final report
A compressor blade fractured at 25,000 feet. An exhaust-duct fire damaged the right nacelle before the crew shut down the engine and diverted to Kelowna.
Incident date:
LEVEL 3 Final report
An unstable approach, a prolonged float and a late touchdown left too little runway to stop at Kozhikode.
Incident date:
LEVEL 3 Final report
A gear-up runway contact damaged both engines. Oil loss led to engine failures during the go-around, and the A320 crashed in Karachi.
Incident date:
LEVEL 3 Final report
Iran AAIB attributed the loss to missile damage after air-defence misidentification. Canada challenged the explanation and its supporting evidence.
Incident date:
LEVEL 3 Final report
Repeated MCAS nose-down trim followed erroneous angle-of-attack data. The final report and participating authorities disagree about sensor failure and crew performance.
Incident date:
LEVEL 3 Final report
An unintended go-around mode change during descent was followed by spatial disorientation, nose-down inputs and a fatal dive into Trinity Bay.
Incident date:
LEVEL 3 Final report
A miscalibrated angle-of-attack sensor triggered repeated automatic nose-down trim amid conflicting indications and warnings.
Incident date:
LEVEL 3 Final report
A fractured fan blade triggered structural damage, a cabin window loss and an emergency diversion.
Incident date:
LEVEL 3 Final report
An A320 cleared for runway 28R descended over four airliners waiting on taxiway C and escaped a collision through a low-altitude go-around.
Incident date:
LEVEL 3 Final report
A Boeing 777 lifted off after a brief touchdown at Dubai with its engines still at idle, then struck the runway. All 300 occupants survived; a firefighter died after a fuel-tank explosion.
Incident date:
LEVEL 3 Final report
A constant descent angle did not keep the aircraft on the intended approach path.
Incident date:
LEVEL 3 Final report
BEA found that the co-pilot intentionally commanded a descent while alone in the cockpit and prevented re-entry.
Incident date:
LEVEL 3 Final report
An uncommanded autofeather was followed by shutdown of the operative engine and a stall over Taipei.
Incident date:
LEVEL 3 Final report
Repeated rudder limiter faults led to electrical interruption, an abrupt roll and a prolonged stall over the Karimata Strait.
Incident date:
LEVEL 3 Final report
The Dutch Safety Board found that a Buk missile warhead detonated outside the cockpit, causing the aircraft to break up.
Incident date:
LEVEL 3 Final report
A scheduled flight disappeared after leaving its planned route. The 2018 investigation could not determine why.
Incident date:
LEVEL 3 Final report
The crew lost automatic speed control, inadequately monitored airspeed and delayed a go-around while descending below the visual glidepath.
Incident date:
LEVEL 3 Final report
An engine disc burst damaged multiple systems, leaving the crew to manage a complex return to Singapore.
Incident date:
LEVEL 3 Final report
An airspeed inconsistency became a loss of control that the crew never recovered from.
Incident date:
LEVEL 3 Final report
A false radio-altimeter reading drove the autothrottle to idle on approach to Schiphol. The crew recognised the falling airspeed at the stall warning, and the aircraft crashed short of runway 18R.
Incident date:
LEVEL 3 Final report
NTSB found that the captain responded inappropriately to the stick shaker and stalled the aircraft. Monitoring and airspeed-management weaknesses contributed.
Incident date:
LEVEL 3 Final report
A bird encounter left almost no engine thrust, and the Hudson became the landing site.
Incident date:
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 MD-82 took off from Madrid with its flaps and slats retracted. The configuration warning stayed silent, and the aircraft stalled just above the runway.
Incident date:
LEVEL 3 Final report
Ice in the fuel system restricted thrust from both engines during the final approach to Heathrow.
Incident date:
LEVEL 3 Final report
Cleared for runway 22 at Lexington, the crew began takeoff on the shorter, unlighted runway 26.
Incident date:
LEVEL 3 Final report
A snowy landing at Chicago Midway ended beyond the perimeter after delayed reverse thrust. One child in an automobile was killed.
Incident date:
LEVEL 3 Final report
The crew did not identify inadequate cabin pressurization. The aircraft continued automatically until fuel depletion and impact.
Incident date:
LEVEL 3 Final report
A long touchdown in a Toronto thunderstorm left too little runway to stop. The A340 entered a ravine and burned; all 309 occupants escaped.
Incident date:
LEVEL 3 Final report
BFU identified late separation intervention, a descent contrary to TCAS and weaknesses in staffing and collision-avoidance integration.
Incident date:
LEVEL 3 Final report
Alternating rudder inputs during a wake turbulence encounter overloaded the vertical stabilizer shortly after takeoff from New York.
Incident date:
LEVEL 3 Final report
A maintenance-induced fuel leak emptied an A330 over the Atlantic. The crew glided to Lajes, where all 306 occupants survived.
Incident date:
LEVEL 3 Final report
A runway metal strip cut a tyre. BEA found that tyre-impact energy ruptured a fuel tank, producing a major fire and loss of thrust.
Incident date:
LEVEL 3 Final report
Wear in a critical stabilizer mechanism became a loss of pitch control that the crew could not overcome.
Incident date:
LEVEL 3 Final report
A thunderstorm approach ended with an overrun when stopping capability was needed most.
Incident date:
LEVEL 3 Final report
A fire above the forward ceiling spread before its severity was recognised, disabling systems and making a safe landing impossible.
Incident date:
LEVEL 3 Final report
A Boeing 737 descended from 35,000 feet into the Musi River, killing all 104 aboard. Indonesia could not determine the cause; NTSB concluded that intentional pilot action explained the accident.
Incident date:
LEVEL 3 Final report
NTSB found that a center wing tank fuel-air explosion initiated the breakup. The exact ignition source remained uncertain.
Incident date:
LEVEL 3 Final report
A hurried change of approach, an unverified beacon selection and a continuing descent took a Boeing 757 into the mountains east of Cali.
Incident date:
LEVEL 3 Final report
A late touchdown and delayed deceleration left too little runway to stop.
Incident date:
LEVEL 3 Final report
An incorrectly secured windscreen separated in the climb. Cabin crew held the commander while the co-pilot diverted to Southampton.
Incident date:
LEVEL 3 Final report
An engine fragment disabled all three hydraulic systems, leaving thrust as the crew's main control tool.
Incident date:
LEVEL 3 Final report
A left engine fan blade failed. The crew shut down the right engine, and the damaged left engine lost thrust on final approach.
Incident date:
LEVEL 3 Final report
An explosive device in a forward-hold baggage container destroyed the fuselage structure and initiated a rapid breakup over Scotland.
Incident date:
LEVEL 3 Final report
A large section of the upper fuselage separated during an interisland flight. The crew landed the damaged aircraft, while the investigation exposed failures in structural inspection and oversight.
Incident date:
LEVEL 3 Final report
An engine failure punctured a fuel tank during takeoff. Wind drove the resulting fire around the stopped aircraft as smoke and exit restrictions overwhelmed the evacuation.
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
Incorrect fuel calculations and dispatch with blank gauges left a Boeing 767 short of fuel. Both engines stopped, and its crew glided to Gimli.
Incident date:
LEVEL 3 Final report
After a long wait in falling snow, a contaminated aircraft took off with too little thrust. It struck the 14th Street Bridge and entered the ice-covered Potomac River.
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 landing gear malfunction led to prolonged circling at Portland. Fuel exhaustion stopped all four engines before the aircraft could reach the runway.
Incident date:
LEVEL 3 Final report
KLM began its takeoff while Pan Am was still taxiing on the same runway. Low cloud prevented the tower from seeing the developing collision.
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
No incidents match these filters.