NTSB investigations: Beech 200

6 cases on aircraft the registry lists as Beech 200, 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

19972026
NTSB investigations: Beech 200 per year, 1997–2026: 6 cases
19971
19991
20011
20042
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 ('1152920')
      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 SEA07FA051Accident · 3 fatalField investigationFinal reportBeech 200 · Belgrade, MTThe pilot's failure to maintain an adequate altitude and descent rate during a night visual approach. Dark night conditions and mountainous terrain are factors in the accident.Feb 7, 2007 · N45MF · Substantial damageNTSB IAD05MA006Accident · 10 fatalClass 1 · MajorFinal reportBeech 200 · Stuart, VAThe flight crew's failure to properly execute the published instrument approach procedure, including the published missed approach procedure, which resulted in controlled flight into terrain. Contributing to the cause of the accident was the flight crew's…Oct 24, 2004 · N501RH · DestroyedNTSB NYC04FA139Accident · 2 fatalField investigationFinal reportBeech 200 · Rupert, WVThe pilot-in-command's improper decision to continue VFR flight into IMC conditions, which resulted in controlled flight into terrain. Factors were the FAA Principle Operations Inspector's inadequate surveillance of the operator, and a low ceiling.Jun 13, 2004 · N200BE · DestroyedNTSB DCA01MA017Accident · 10 fatalClass 1 · MajorFinal reportBeech 200 · Strasburg, COThe pilot’s spatial disorientation resulting from his failure to maintain positive manual control of the airplane with the available flight instrumentation. Contributing to the cause of the accident was the loss of a.c. electrical power during instrument…Jan 27, 2001 · N81PF · DestroyedNTSB NYC00FA006Accident · 2 fatalField investigationFinal reportRaytheon Corporate Jets BE-200 · Williamstown, MAThe pilot-in-command's failure comply with an air traffic control clearance which resulted in a collision with terrain. A factor in this accident was clouds.Oct 5, 1999 · N208MS · DestroyedNTSB MIA97FA232Accident · 1 fatalField investigationFinal reportBeech 200 · Dalton, GAthe pilot's improper IFR procedure, by failing to maintain the minimum descent altitude (MDA) during the ILS localizer approach, until the runway environment was in sight, which resulted in a collision with terrain short of the runway. Factors relating to the…Aug 14, 1997 · N74EJ · Substantial damage