NTSB investigations: Cessna 172M, NE
11 cases on aircraft the registry lists as Cessna 172M. 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
| 1976 | 1 |
|---|---|
| 1977 | 1 |
| 1979 | 1 |
| 1980 | 1 |
| 1983 | 1 |
| 1988 | 1 |
| 1989 | 1 |
| 1993 | 1 |
| 1998 | 1 |
| 1999 | 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.\"eventStateOrRegion\" = 'NE' 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 ('2072418'))
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" = 'NE' 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 ('2072418'))
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 CEN22LA309Accident · No injuriesClass 3 · LimitedFinal reportCessna 172M · Friend, NEA loss of engine power due to a stuck valve.NTSB CHI99LA148Accident · No injuriesLimited investigationFinal reportCessna 172 · Blair, NEThe pilot's misjudged landing flare.NTSB CHI98LA141Accident · No injuriesLimited investigationFinal reportCessna 172M · Superior, NEthe pilot's failure to maintain clearance with the sign. Factors associated with the accident were the sign which the airplane contacted and inadequate preflight planning/preparation.NTSB CHI93LA332Accident · No injuriesLimited investigationFinal reportCessna 172M · Lincoln, NEthe pilot's failure to attain the proper touchdown point.NTSB MKC90LA010Accident · No injuriesLimited investigationFinal reportCessna 172 · Omaha, NEFailure of the throttle cable assembly which resulted in a forced landing and subsequent collision with a fence.NTSB MKC88LA052Accident · No injuriesLimited investigationFinal reportCessna 172 · Kimball, NEThe pilot said that he was using outdated charts for his destination apt. He failed to notice a new runway. He also failed to notice the yellow x's, signifying closure of the old runway. It was almost parallel to the runway, within ten degrees of heading. Ldg…NTSB MKC83FA184Accident · Serious injuriesField investigationFinal reportCessna 172M · Minden, NEA student plt in left seat made the takeoff using 10 deg flaps. At about 50 ft AGL passing over the departure end of therwy, the PIC noticed the acft was sinking & took the controls. The acft impacted trees as the PIC was avoiding power lines. The flaps were…NTSB MKC80DCJ05Accident · No injuriesClosedCessna 172M · Sidney, NENTSB MKC79DCJ12Accident · No injuriesClosedCessna 172 · Kearney, NENTSB MKC77FA024Accident · 4 fatalClosedCessna 172M · Gordon, NENTSB MKC76DCJ49Accident · No injuriesClosedCessna 172 · Mccook, NE