NTSB investigations: Cessna 208B

7 cases on aircraft the registry lists as Cessna 208B, where the first occurrence was “In flight collision with object”. 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

19892026
NTSB investigations: Cessna 208B per year, 1989–2026: 7 cases
19891
19951
19971
20001
20011
20051
20071

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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073701', '2073700', '2073705')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
  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 CHI07FA068Accident · Serious injuriesField investigationFinal reportCessna 208B · Alliance, NEThe pilot's descent below minimum descent altitude while on a nonprecision approach. A contributing factor was a low ceiling.Feb 8, 2007 · N1116Y · Substantial damageNTSB DFW05IA150Incident · No injuriesIncident investigationFinal reportCessna 208B · Clarendon, TXThe loss of total engine power due to damage of the compressor stator vanes caused by a foreign object. A contributing factor was an in-flight ingestion of bird(s).Jun 7, 2005 · N9505B · No damageNTSB MIA02FA037Accident · 2 fatalField investigationFinal reportCessna 208B · Bessemer, ALThe poor in-flight planning by the pilot-in-command for his initiation of the ILS approach to runway 05 with weather conditions below minimums for the approach contrary to the federal aviation regulations, and the failure of the pilot to maintain control of…Dec 1, 2001 · N499BA · DestroyedNTSB SEA01FA001Accident · 1 fatalField investigationFinal reportCessna 208B · Lummi Island, WAThe pilot's attempted flight into known adverse weather conditions, and his subsequent failure to maintain altitude above, or clearance with, trees. Factors contributing to the accident included low ceilings, fog, the pilot's low-altitude flight, rising…Oct 9, 2000 · N941FE · Substantial damageNTSB NYC97LA054Accident · No injuriesLimited investigationFinal reportCessna 208B · Covington, KYThe pilot's failure to maintain the airplane on the ILS glide slope, which resulted in a descent below the glide path, and the inadvertent in-flight collision with a utility pole. Contributing factors were sleet/snow, dark night conditions, and the pole.Feb 14, 1997 · N922FE · Substantial damageNTSB LAX95FA077Accident · 1 fatalField investigationFinal reportCessna 208B · Pleasanton, CAfailure of the pilot-in-command to maintain visual contact with terrain and sufficient altitude for terrain clearance. Factors in the accident were the pilot's decision to initiate a descent 14 miles from the airport, and weather, specifically cloud…Jan 13, 1995 · N754FE · DestroyedNTSB ATL89FA071Accident · Serious injuriesField investigationFinal reportCessna 208B · Madison, NCImproper IFR procedure by the pilot and his failure to maintain the minimum descent altitude (mda). Contributing factors were: low ceiling, fog, delayed missed approach by the pilot, and trees.Jan 11, 1989 · N9330B · Destroyed