NTSB investigations: Cessna 172S, NM
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
| 2002 | 1 |
|---|---|
| 2004 | 2 |
| 2005 | 2 |
| 2014 | 1 |
| 2016 | 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\" = 'NM' 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" = 'NM' 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 CEN16LA228Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Deming, NMThe pilots’ failure to maintain adequate control of the airplane during the initial climb after takeoff, which resulted in the airplane exceeding its critical angle of attack and an aerodynamic stall at a low altitude. Contributing to the accident was the…NTSB CEN14CA191Accident · No injuriesData collectionFinal reportCessna 172S · Albuquerque, NMThe student pilot's improper flare that resulted in a bounced landing.NTSB DEN06FA023Accident · 1 fatalField investigationFinal reportCessna 172S · Pinon, NMthe pilot's failure to maintain control of the airplane for undetermined reasons.NTSB LAX05CA137Accident · No injuriesData collectionFinal reportCessna 172S · Gallup, NMthe pilot's premature liftoff and inadequate remedial action, which resulted in the airplane inadvertently recontacting the runway.NTSB DEN05FA044Accident · 1 fatalField investigationFinal reportCessna 172S · Roswell, NMthe pilot not maintaining control of the aircraft resulting in an uncontrolled descent and collision on a highway. Factors contributing to the accident were the dark night and the pilot experiencing spatial disorientation.NTSB DEN04LA127Accident · No injuriesLimited investigationFinal reportCessna 172S · Carlsbad, NMthe student pilot's inadequate flare resulting in a hard landing. A contributing factor was the tailwind conditions.NTSB FTW02LA115Accident · No injuriesLimited investigationFinal reportCessna 172S · Angel Fire, NMThe pilots failure to maintain directional control during the crosswind landing. A contributing factor was the gusting wind condition.