NTSB investigations: Cessna 172S, LA
7 cases on aircraft the registry lists as Cessna 172S. 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
| 2001 | 2 |
|---|---|
| 2012 | 1 |
| 2013 | 1 |
| 2017 | 1 |
| 2020 | 1 |
| 2021 | 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.\"eventStateOrRegion\" = 'LA' 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 ('2072439', '2072442'))
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" = 'LA' 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 ('2072439', '2072442'))
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 CEN21LA268Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Saint James, LAThe in-flight fatigue failure of an air-conditioning system hose which resulted in a precautionary landing and impact with a road sign.NTSB CEN20CA195Accident · No injuriesClass 4 · Data collectionFinal reportCessna 172 · Houma, LAThe pilot's failure to maintain adequate clearance from a ground obstacle during landing.NTSB OPS17IA021IncidentClass 3 · IncidentFinal reportCessna 172S · New Orleans, LAThe air traffic controller not following Federal Aviation Administration directives to establish sequencing and spacing between aircraft operating to the same runway.NTSB CEN14CA070Accident · No injuriesData collectionFinal reportCessna 172 · New Orleans, LAThe pilot's failure to maintain aircraft control after starting the engine, which resulted in a collision with a building.NTSB CEN12CA240Accident · No injuriesData collectionFinal reportCessna 172S · Monroe, LAThe student pilot's improper landing flare, which resulted in a bounced landing and loss of directional control.NTSB FTW01LA145Accident · No injuriesLimited investigationFinal reportCessna 172S · Baton Rouge, LAthe student pilot's improper recovery from a bounced landing.NTSB FTW01IA062Incident · No injuriesIncident investigationFinal reportCessna 172S · Ruston, LAthe loss of engine power while manuevering as a result of an incorrect mixture control adjustment. A contributing factor was the lack of suitable terrain for the ensuing forced landing.