NTSB investigations: Cessna P210N, OK
6 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
| 1981 | 1 |
|---|---|
| 1982 | 1 |
| 1986 | 1 |
| 1989 | 1 |
| 1996 | 1 |
| 2004 | 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\" = 'OK' 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" = 'OK' 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 DFW05LA027Accident · No injuriesLimited investigationFinal reportCessna P210N · Pawhuska, OKThe pilot's mismanagement of the fuel by his failure to adequately set the fuel selector position which resulted in fuel exhaustion and the loss of engine power.NTSB FTW97LA064Accident · Serious injuriesLimited investigationFinal reportCessna P210N · Muskogee, OKthe pilot's improper planning/decision and inaccurate fuel consumption calculations, which resulted in an inadequate supply of fuel, fuel exhaustion, and a subsequent forced landing at night. Darkness was a related factor.NTSB FTW89LA160Accident · No injuriesLimited investigationFinal reportCessna 210P · Bethany, OKA loose fuel line connection, due to inadequate maintenance, which resulted in fuel starvation. Factors related to the accident were: darkness and the obstructions (hay bale & approach light pole) in the emergency landing area.NTSB FTW86LA148Accident · Serious injuriesLimited investigationFinal reportCessna P210N · Altus, OKThe engine failed at 10,500 feet MSL and the pilot was vectored to a small private sod strip. However, this strip had been closed and plowed up for about a year and was not listed on the current aeronautical charts. The pilot was then revectored to another…NTSB FTW82DA338Accident · No injuriesFinal reportCessna P210N · Ardmore, OKAfter making an NDB approach, the pilot sighted the runway and turned onto a downwind for a visual approach. The aircraft touched down at about the midfield point in calm wind conditions. The runway had just been resurfaced and was wet and slick from…NTSB FTW81DPJ21Accident · No injuriesClosedCessna P210N · Ardmore, OK