NTSB investigations: Airbus A320-232, CA
3 cases on aircraft the registry lists as Airbus A320-232. 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
| 2005 | 1 |
|---|---|
| 2010 | 1 |
| 2014 | 1 |
Where
Latest 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.\"eventStateOrRegion\" = 'CA' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3940004', '3940304'))
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."eventStateOrRegion" = 'CA' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3940004', '3940304'))
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 ENG14IA028Incident · No injuriesIncident investigationFinal reportAirbus A320 232 · Long Beach, CAThe probable cause of the engine failure and subsequent undercowl engine fire was due to the fatigue fracture of a high pressure turbine stage 2 disk blade retaining lug that released two blades which impacted the low pressure turbine case causing a fuel line…NTSB WPR10IA430Incident · Minor injuriesIncident investigationFinal reportAirbus A320-232 · Sacramento, CAThe first officer’s inadvertent activation of the parking brake in flight, which led to the airplane abruptly stopping and all four of its main landing gear tires deflating, and his use of a nonstandard procedure to cancel the airplane's monitoring alert…NTSB LAX05IA312Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320 · Los Angeles, CAThe fatigue failure of two anti-rotation lugs due to repeated cyclic pre-landing tests, which allowed the nosewheels to deviate from the 0-degree position on landing gear retraction. A contributing factor was the design of the Brake Steering Control Unit…