NTSB investigations: Cessna P210N, 1996

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

19782026
NTSB investigations: Cessna P210N, 1996 per year, 1978–2026: 256 cases
19784
19796
19806
19819
198210
19833
19846
19857
19869
19874
19886
19896
19904
19913
19922
19934
19947
19957
19968
19978
19981
19998
20004
20015
20023
20033
20047
20054
20065
20072
20085
20093
20107
20115
20125
20133
20144
20152
20166
20175
20189
20194
20205
202110
20225
20234
20244
20255
20264

Latest 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 year(c.\"eventDate\") = 1996
    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.

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.Dec 18, 1996 · N210BG · Substantial damageNTSB SEA97FA027Accident · 1 fatalField investigationFinal reportCessna P210N · Boring, ORThe pilot's attempt to conduct visual flight into instrument meteorological conditions. A factor contributing to the accident was the presence of thick fog.Nov 15, 1996 · N7823K · DestroyedNTSB LAX96LA253Accident · Minor injuriesLimited investigationFinal reportCessna P210 · Grand Canyon, AZfailure of the pilot to use his brakes to maintain directional control.Jun 29, 1996 · N4766K · DestroyedNTSB LAX96LA260Accident · No injuriesLimited investigationFinal reportCessna P210N · San Bernardino, CAfailure of the landing gear to go and/or remain in a down-and-locked condition for undetermined reason(s).Jun 27, 1996 · N4844K · Substantial damageNTSB IAD96LA079Accident · Minor injuriesLimited investigationFinal reportCessna P210N · Carrollton, OHThe pilot's inadequate fuel management. Factors in this accident were the pilot's reliance on a fuel data computer and his untimely reaction to a known fuel quantity discrepancy.May 20, 1996 · N731NC · Substantial damageNTSB NYC96FA101Accident · 2 fatalField investigationFinal reportCessna P210N · Ridgefield, CTimproper planning/decision by the pilot, which led to flight into icing conditions; and his failure to use all anti-ice and deicing equipment, as specified by the airplane operator's manual for inadvertent flight into icing conditions. This resulted in loss…May 6, 1996 · N450T · DestroyedNTSB ATL96FA074Accident · 2 fatalField investigationFinal reportCessna P210N · Marathon, FLfailure of the pilot to maintain sufficient altitude during an over-water approach at night. Factors relating to the accident were darkness and pilot fatigue.Apr 1, 1996 · N6427W · Substantial damageNTSB IAD96LA046Accident · Minor injuriesLimited investigationFinal reportCessna P210N · Hazard, KYfailure of the engine crankshaft, which resulted in loss of engine power, a forced landing, and subsequent damage to the airplane. A factor relating to the accident was: lack of suitable terrain for a forced landing.Feb 23, 1996 · N90AD · Substantial damage