NTSB investigations: Cessna 208B

7 cases on aircraft the registry lists as Cessna 208B, where the sequence of events included Off-field or emergency landing. 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

20092026
NTSB investigations: Cessna 208B per year, 2009–2026: 7 cases
20091
20122
20131
20161
20221
20241

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_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s.\"tier2Number\" = '440' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\")))
  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 ERA24LA094Incident · No injuriesClass 3 · LimitedFinal reportCessna 208 · Dulles, VAThe pilot-in-command’s approach to the critical angle of attack during initial climb, which resulted in a vibration the flight crew improperly identified as an engine issue and resulted in the subsequent off-airport landing. Contributing to the accident was…Jan 19, 2024 · N1983X · Minor damageNTSB CEN22LA134Accident · No injuriesClass 3 · LimitedFinal reportCessna 208B · Campbellton, TXThe pilot’s fuel mismanagement, which resulted in a total loss of engine power due to fuel exhaustion and subsequent impact with trees during a forced landing.Feb 28, 2022 · N108RF · Substantial damageNTSB WPR16LA107Accident · Minor injuriesLimited investigationFinal reportCessna 208B · Acampo, CAA total loss of engine power due to a fatigue fracture of the fuel pressure line that connected the fuel control unit and the fuel flow transducer due to vibration as the result of a fatigue fracture of an associated support clamp. Contributing to the…May 12, 2016 · N1114A · Substantial damageNTSB WPR14FA024Accident · No injuriesField investigationFinal reportCessna 208 · Wailea, HIImproper maintenance that resulted in contamination of the engine's compressor turbine disc and blade assembly by glass bead remnants, which resulted in a blade failure.Oct 22, 2013 · N861MA · Substantial damageNTSB CEN13FA080Accident · Minor injuriesField investigationFinal reportCessna 208B · Bryans Corner, OKThe total loss of engine power as a result of a fractured compressor turbine blade due to fatigue cracking.Nov 30, 2012 · N1324G · Substantial damageNTSB CEN13FA049Accident · 1 fatalField investigationFinal reportCessna 208B · Wichita, KSThe total loss of engine power as a result of a fractured compressor turbine blade due to high-cycle fatigue.Nov 6, 2012 · N793FE · Substantial damageNTSB ERA10IA094Incident · No injuriesIncident investigationFinal reportCessna 208B · Rome, NYThe operator's inadequate engine wash intervals, which resulted in compressor turbine blade sulphidation and subsequent turbine blade failure.Dec 3, 2009 · N701FX · No damage