NTSB investigations: Cessna 172N
8 cases on aircraft the registry lists as Cessna 172N, where NTSB found Altitude. 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
| 2008 | 1 |
|---|---|
| 2012 | 1 |
| 2016 | 1 |
| 2017 | 1 |
| 2018 | 1 |
| 2020 | 1 |
| 2021 | 1 |
| 2024 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f.\"findingCode\", '01062012')))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f."findingCode", '01062012')))
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 ERA24FA292Accident · 1 fatalClass 3 · FieldFinal reportCessna 172N · Lock Haven, PAThe student pilot’s premature turn to the crosswind leg of the traffic pattern at low airspeed and altitude, resulting in a collision with trees and terrain.NTSB WPR22LA069Accident · Serious injuriesClass 4 · LimitedFinal reportCessna 172N · Auburn, CAThe pilot’s failure to maintain altitude during an instrument approach, which resulted in an impact with power lines.NTSB WPR20CA125Accident · Minor injuriesData collectionFinal reportCessna 172 · Yakima, WAThe pilot's failure to attain sufficient altitude during a go-around, which resulted in impact with hilly terrain.NTSB WPR18LA241Accident · Serious injuriesClass 3 · LimitedFinal reportCessna 172 · Afton, WYThe pilot’s failure to maintain terrain clearance after an encounter with a downdraft while maneuvering in a valley with a high-density altitude, which resulted in impact with trees and terrain.NTSB WPR17FA196Accident · 1 fatalField investigationFinal reportCessna 172N · Bolinas, CAThe non-instrument rated private pilot's improper decision to embark on a flight and continue to fly into forecasted instrument meteorological conditions and mountain obscuration while conducting a visual flight rules flight.NTSB CEN16FA083Accident · 1 fatalField investigationFinal reportCessna 172N · Gilmer, TXThe pilot's inadequate preflight planning and inspection, which resulted in a total loss of engine power due to fuel exhaustion. Contributing to the accident was the pilot's failure to maintain an appropriate traffic pattern altitude and distance from the…NTSB WPR12LA093Accident · 1 fatalLimited investigationFinal reportCessna 172N · Fresno, CAThe non-certificated pilot’s failure to maintain clearance from power lines. Contributing to the accident was the pilot’s impairment due to performance-impairing drugs.NTSB CHI08CA139Accident · No injuriesData collectionFinal reportCessna 172N · Blue Ash, OHThe separation of the throttle cable from the linkage during the approach to land and the altitude/clearance not being available to the pilot during the forced landing. Contributing to the accident was the electrical wires the airplane impacted.