Search results
Results from the WOW.Com Content Network
The following is a list of accidents and incidents involving the Airbus A320 family and A320neo family of jet airliners. As of March 2024, 180 aviation accidents and incidents have occurred, [1] including 38 hull-loss accidents, [2] resulting in a total of 1490 fatalities.
Pages in category "Accidents and incidents involving the Airbus A320" The following 27 pages are in this category, out of 27 total. This list may not reflect recent changes .
Airbus A321-200 Terrorist bombing 224 Bomb that was smuggled into rear cargo hold disguised as a soft drink can contained four packs of dynamite, causing the tail section to separate and lead to an in-flight break up, scattering the wreckage in the Sinai Desert 2016-05-19 EgyptAir Flight 804: Mediterranean Sea Airbus A320-200
Airbus A320-200: Kuala Lumpur-Kuching: Runway overrun Flight 1580: Medan: 26 September 2017: Airbus A320: Medan-Penang: Possible bird strike, engine problems [124] AirAsia X; Flight designation Location Date Aircraft type Route Cause Flight 237: Perth: 25 June 2017: Airbus A330: Perth-Kuala Lumpur: Contained engine failure Flight 207: Gold ...
It is the first Airbus A320 crash. 20 January 1992 - Air Inter Flight 148, an Airbus A320, crashed near Mont Sainte-Odile while it was circling to land at Strasbourg, killing 87. 31 March 1992 - Trans-Air Service Flight 671 suffers a double engine separation. A fire subsequently erupts on the wing. It lands at Istres-Le Tubé Air Base.
Ural Airlines Flight 1383 was a scheduled flight from Sochi/Adler to Omsk in Russia. On 12 September 2023, the Airbus A320-214 operating the flight and carrying 159 passengers and 6 crew made an emergency landing in a field.
Pages in category "Accidents and incidents involving the Airbus A320neo" This category contains only the following page. This list may not reflect recent changes .
The Airbus A320 took off from San Diego International Airport at 5:01 p.m. CDT (3:01 pm in San Diego). It was scheduled to land at 8:01 p.m. CDT. [5] Just under two hours after takeoff, at 6:56 p.m. CDT, Air Traffic Control lost radio contact with the aircraft while it was over Denver.