NTSB investigations: Cessna U206F

8 cases on aircraft the registry lists as Cessna U206F, where the first occurrence was “In flight collision with terrain/water”. 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
NTSB investigations: Cessna U206F per year, 1986–2026: 8 cases
19861
19891
19901
19991
20001
20011
20032

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 ('2073333', '207333A')
      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\" = 230))
  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 ANC03LA113Accident · Minor injuriesLimited investigationFinal reportCessna 206 · Chalkyitsik, AKThe pilot's inadequate compensation for wind conditions, and his failure to maintain adequate airspeed during takeoff, which resulted in an in-flight collision with brush, and subsequent stall of the airplane. Factors associated with the accident were a…Sep 11, 2003 · N710MH · Substantial damageNTSB ANC03CA114Accident · No injuriesData collectionFinal reportCessna 206 · Ketchikan, AKThe pilot's selection of an unsuitable takeoff area, which resulted in an in-flight collision with ocean waves. A factor associated with the accident was large waves/swells.Aug 14, 2003 · N59352 · Substantial damageNTSB ANC01LA147Accident · No injuriesLimited investigationFinal reportCessna 206 · Galena, AKThe pilot's inadequate preflight planning and preparation for takeoff from an off-airport, short field site. Factors associated with the accident are a variable wind, and the pilot's inadequate weather evaluation.Sep 24, 2001 · N35962 · Substantial damageNTSB SEA01FA100Accident · 2 fatalField investigationFinal reportCessna U206F · Cambridge, IDAirspeed not maintained and an inadvertent stall while maneuvering. Mountainous terrain was a factor.Nov 16, 2000 · N8529Q · DestroyedNTSB SEA00FA012Accident · 4 fatalField investigationFinal reportCessna U206F · Challis, IDAircraft control was not maintained. The pilot's improper decision to abort the landing and flight into a box canyon were factors.Oct 31, 1999 · N902CT · Substantial damageNTSB LAX90LA315Accident · Serious injuriesLimited investigationFinal reportCessna U206F · Las Vegas, NVThe pilot's loss of visual references during a night approach and his failure to detect and correct a descent. A factor in the accident was the dark night lighting conditions.Sep 6, 1990 · N51299 · Substantial damageNTSB DEN90LA014Accident · No injuriesLimited investigationFinal reportCessna 206F · Opheim, MTPilot's failure to maintain terrain clearance while executing a low pass.Oct 27, 1989 · N33211 · Substantial damageNTSB SEA87FA027Accident · 1 fatalField investigationFinal reportCessna U206F · Moose Creek, IDAfter departure and during the initial cruise climb the plt and pax heard a metallic clicking described as sounding like a 'valve tap' in an automobile and coming from the eng area. The plt executed an immediate course reversal back to the airstrip while…Nov 20, 1986 · N7311Q · Destroyed