NTSB investigations: Cessna 172F, NM
9 cases on aircraft the registry lists as Cessna 172F. 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
| 1970 | 1 |
|---|---|
| 1971 | 1 |
| 1972 | 1 |
| 1979 | 2 |
| 1982 | 1 |
| 1992 | 1 |
| 1997 | 1 |
| 2001 | 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 ('2072414'))
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 ('2072414'))
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 FTW01LA075Accident · No injuriesLimited investigationFinal reportCessna 172F · Clovis, NMthe pilot's failure to maintain directional control during take off roll resulting in a ground loop. A contributing factor was the crosswind.NTSB FTW98LA036Accident · No injuriesLimited investigationFinal reportCessna 172F · Hurley, NMthe student pilot's failure to adequately compensate for the wind conditions. Factors included the gusty crosswind conditions and inadequate supervision of the student pilot's solo flight by his flight instructor.NTSB DEN92LA087Accident · No injuriesLimited investigationFinal reportCessna 172F · Folsom, NMCarburetor heat not used and improper use of throttle and mixture control. A factor was: the lack of suitable terrain for a forced landing.NTSB FTW82DA122Accident · No injuriesFinal reportCessna 172 · Gallup, NMOn the second landing of the flight the aircraft veered to the left and departed the runway. The aircraft nosed over after hitting soft dirt and a drainage ditch. The pilot stated that the aircraft swerved on the first landing and he felt that the passenger…NTSB DEN79FQA38Accident · Serious injuriesClosedCessna 172 · Albuquerque, NMNTSB DEN79DQA30Accident · No injuriesClosedCessna 172 · Las Vegas, NMNTSB DEN73FQA07Accident · No injuriesClosedCessna 172 · Grants, NMNTSB DEN72AD014Accident · 2 fatalClosedCessna 172F · Capitan, NMNTSB DEN70DQA02Accident · No injuriesClosedCessna 172 · Los Alamos, NM