NTSB investigations: Cessna P210N, UT
8 cases on aircraft the registry lists as Cessna P210N. 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
| 1978 | 1 |
|---|---|
| 1979 | 1 |
| 1982 | 1 |
| 1997 | 1 |
| 2007 | 1 |
| 2014 | 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\" = 'UT' 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 ('2073454', '2073462'))
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" = 'UT' 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 ('2073454', '2073462'))
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 WPR21LA078Accident · No injuriesClass 3 · LimitedFinal reportCessna P210N · Moab, UTThe pilot’s improper application of full throttle during takeoff, which resulted in loss of engine power due to an excessive fuel flow and overly rich fuel mixture.NTSB WPR20CA158Accident · No injuriesClass 4 · Data collectionFinal reportCessna P210 · Heber City, UTThe pilots failure to switch the fuel pump to the 'OFF' position during landing, resulting in a loss of engine power and subsequent collision with a fence during landing. Contributing to the accident was a modified before landing checklist which omitted the…NTSB WPR14LA118Accident · No injuriesLimited investigationFinal reportCessna P210N · Bountiful, UTFuel starvation due to the in-flight loosening of the fuel lines attached to the fuel flow indicator as a result of inadequate maintenance.NTSB SEA07FA124Accident · 1 fatalField investigationFinal reportCessna P210N · Spanish Fork, UTAn engine oil line leak and subsequent engine compartment fire while in cruise flight.NTSB FTW98TA051Incident · No injuriesFinal reportCessna P210N · Bryce Canyon, UTThe failure of the resistor (inverter) in the door seal pressurization air pump due to continuous operation. Factors were a failure in the door seal pressurization system, its inadequate design by the manufacturer, its inadequate written instructions for…NTSB DEN82DA032Accident · Minor injuriesFinal reportCessna 210 · Blanding, UTThe pilot reported that the visibility was five miles when he landed. However, according to the airport manager, it was less than one mile with ground fog. During the landing, the left wing struck the ground when the plane touched down short of the runway…NTSB DEN80FTM02Accident · Minor injuriesClosedCessna P210 · Fillmore, UTNTSB DEN79FTM01Accident · No injuriesClosedCessna P210N · Ogden, UT