Fatal NTSB investigations: Cessna T303

9 cases on aircraft the registry lists as Cessna T303. 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

19862026
Fatal NTSB investigations: Cessna T303 per year, 1986–2026: 9 cases
19861
19932
19981
20001
20061
20101
20131
20191

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 c.\"highestInjuryLevel\" = 'Fatal'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073820'))
  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 ERA19FA249Accident · 2 fatalClass 3 · FieldFinal reportCessna T303 · Lagrangeville, NYA partial loss of engine power in both engines during initial climb for reasons that could not be determined based on the available information.Aug 17, 2019 · N303TL · DestroyedNTSB CEN13WA527Accident · 2 fatalForeign investigationCessna T303 · JerseySep 4, 2013 · N289CW · Substantial damageNTSB ERA10FA161Accident · 1 fatalField investigationFinal reportCessna T303 · Louisa, VAThe pilot's failure to maintain aircraft control and secure the right engine during a loss of engine power after takeoff. Contributing to the accident was the loss of engine power on the right engine for undetermined reasons.Mar 4, 2010 · N9305T · Substantial damageNTSB CHI07FA022Accident · 5 fatalField investigationFinal reportCessna T303 · Mill Creek, INThe pilot became spatially disoriented and as a result failed to maintain control of the airplane. Factors associated with the accident were the instrument meteorological conditions aloft and the pilot being fatigued.Nov 14, 2006 · N611BB · DestroyedNTSB NYC01WA051Accident · 1 fatalForeign investigationCessna T303 · Dossenheim, GermanyOct 20, 2000 · N9645C · DestroyedNTSB SEA98FA042Accident · 6 fatalField investigationFinal reportCessna T303 · Midvale, IDThe pilot's failure to maintain aircraft control.Mar 3, 1998 · N727RT · DestroyedNTSB FTW94FA038Accident · 2 fatalField investigationFinal reportCessna T303 · Rogers, ARThe pilot's continued flight into known adverse weather conditions, and the ensuing inadvertent stall. Factors were the icing conditions, the fog, the drizzle, the dark night light conditions, and the pilot's disregard for the forecasted weather conditions.Nov 26, 1993 · N2297C · DestroyedNTSB LAX93FA274Accident · 5 fatalField investigationFinal reportCessna T303 · Prescott, AZThe pilot misjudging distance and altitude during a night approach. Factors which contributed to the accident were: the pilot's impairment due to fatigue exacerbated by alcohol consumption, the dark night, and the high density altitude and turbulent weather…Jul 4, 1993 · N9667C · DestroyedNTSB ATL86FA074Accident · 1 fatalField investigationFinal reportCessna 303 · Shippenville, PAN4877V arrived over clarion county airport at about 2100 hours, and commenced a visual approach for landing. Marginal visual weather conditions prevailed at the time of the accident. The flight was observed by another pilot waiting on the ground for the…Feb 13, 1986 · N4877V · Destroyed