NTSB investigations: Airbus Industrie A320-211
14 cases on aircraft the registry lists as Airbus Industrie A320-211. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1990 | 1 |
|---|---|
| 1993 | 1 |
| 1995 | 3 |
| 1996 | 1 |
| 2002 | 1 |
| 2007 | 1 |
| 2009 | 1 |
| 2011 | 1 |
| 2013 | 1 |
| 2015 | 1 |
| 2016 | 1 |
| 2022 | 1 |
Where
Open the mapLatest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3930320'))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3930320'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB DCA23LA067Accident · No injuriesClass 4 · LimitedFinal reportAirbus A320 · Red Oak, IAMultiple bird strikes during descent.NTSB DCA16IA200Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320 211 · Rapid City, SDThe flight crew's misidentification of the desired landing runway due to excess altitude requiring an extended downwind, and failure to use all available navigation information.NTSB OPS15IA020Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320 211 · Max, NEThe flight crew's continued flight into a closing gap between areas of thunderstorm activity and their failure to maintain the required lateral separation from the thunderstorms, which resulted in the airplane's encounter with hail and subsequent airplane…NTSB DCA13CA091Accident · Serious injuriesData collectionFinal reportAirbus 320 · Dallas, TXThe flight attendant's inadvertent trip over the jumpseat that had not retracted automatically.NTSB DCA12CA043Accident · No injuriesData collectionFinal reportAirbus Industrie A320 211 · Minneapolis, MNIn-flight collision with birds during initial climb, which resulted in substantial damage to the aircraft.NTSB DCA09FA047Accident · Minor injuriesField investigationFinal reportAirbus A320 · Denver, COThe first officer’s excessive pitch-up of the airplane while landing with a tailwind, which resulted in a tailstrike following a bounced landing. Contributing to the bounced landing were a high descent rate and excessive thrust resulting from the first…NTSB CHI08IA022Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320-211 · Fargo, NDThe failure of the Brake and Steering Control Unit, which allowed the nose landing gear to turn to the 90-degree position.NTSB CHI03LA031Accident · Serious injuriesLimited investigationFinal reportAirbus Industrie A320-211 · Minneapolis, MNThe cabin flight crew not verifying the galley service cart had been properly stowed prior to departure, which resulted in the inadvertent deployment of the galley service cart during initial climb after takeoff.NTSB CHI97IA034Incident · No injuriesIncident investigationFinal reportAirbus Industrie A-320-211 · Romulus, MIrestricted movement of the autopilot mode engagement/disengagement lever bearing in the rudder artificial feel and trim unit. A factor relating to this incident was: company management not implementing the respective service bulletin.NTSB CHI95LA170Accident · No injuriesLimited investigationFinal reportAirbus Industrie A-320-211 · St Paul, MNthe captain's not maintaining crew/group coordination. Factors were the captain's diverted attention and his not maintaining visual separation.NTSB CHI95IA342Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320-211 · Minneapolis, MNinadequate design of the fly-by-wire flight control system which allowed false signals from the sidestick transducer units to generate uncommanded rolls.NTSB CHI95IA138Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320-211 · Washington, DCthe pilot's excessive use of the flight controls during the landing approach, the company's disregard of information provided by the airplane manufacturer, and the company's failure to identify a potentially hazardous conditions based on the information…NTSB CHI93IA125Incident · No injuriesIncident investigationFinal reportATR ATR 72 · Chicago, ILthe local controller's failure to issue a proper heading clearance which resulted in a loss of radar separation between two departing airplanes.NTSB DCA90IA048Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320-211 · Chicago, ILThe pilot(s) allowed the aircraft to rotate to an excessive nose high attitude, either during a takeoff or landing.