NTSB investigations: Cessna P210N, KS
7 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
| 1980 | 2 |
|---|---|
| 1981 | 1 |
| 1983 | 1 |
| 1985 | 1 |
| 1990 | 1 |
| 1995 | 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\" = 'KS' 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" = 'KS' 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 CHI95LA137Accident · Serious injuriesLimited investigationFinal reportCessna P210N · Dodge City, KSfatigue and subsequent catastrophic failure of the connecting rod originating from the decarburized area on the shank of the rod. Factors were the low cloud weather condition and the ditch.NTSB MKC90FA044Accident · Serious injuriesField investigationFinal reportCessna P210N · Newton, KSLoss of engine power for an undetermined reason. Darkness and the resultant delay in flaring to land were related factors.NTSB MKC86FA026Accident · 4 fatalField investigationFinal reportCessna P210N · Wichita, KSThe acdt occurred during an IFR, non-precision approach to the uncontrolled jabara airport. When the flt was one mile from the faf, ATC told the flt that in the event of a missedapproach N3864P should enter controlled airspace heading 360 deg. The controller…NTSB MKC84LA008Accident · Minor injuriesLimited investigationFinal reportCessna P210N · Lawrence, KSThe plt reported that prior to flt, the fuel gages indicated both tanks were full; however, he did not visually verify the quantity of fuel. During flt, in the vicinity of emporia, KS, the eng lost power while using fuel from the left tank. The plt changed…NTSB MKC82DCQ04Accident · No injuriesClosedCessna P210N · Fort Scott, KSNTSB MKC80FA044Accident · No injuriesClosedCessna P210N · Winfield, KSNTSB MKC80DCQ24Accident · Minor injuriesClosedCessna 210P · Pratt, KS