NTSB investigations: Bell 206B

10 cases on aircraft the registry lists as Bell 206B, where the sequence of events included Miscellaneous/other. 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

20132026
NTSB investigations: Bell 206B per year, 2013–2026: 10 cases
20131
20141
20162
20171
20182
20191
20262

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 ('1181511')
      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\" = '900' 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 WPR26LA277Accident · Serious injuriesClass 4 · LimitedFinal reportBell 206B III · Stonewall, OKThe pilot’s failure to maintain clearance from power lines while conducting a low-altitude aerial application.Jul 21, 2026 · N2193X · Substantial damageNTSB CEN26LA264Accident · Serious injuriesClass 4 · LimitedInvestigation openBell 206B · Saint Joseph, ILJul 17, 2026 · N297CA · Substantial damageNTSB CEN19LA309Accident · No injuriesClass 3 · LimitedFinal reportBell 206 · Walkerton, INThe partial loss of engine power due to fuel contamination.Sep 9, 2019 · N19TV · Substantial damageNTSB GAA18CA512Accident · No injuriesClass 4 · Data collectionFinal reportBell 206 · Battle Mountain, NVThe pilot's failure to maintain the proper altitude and airspeed while flying in a canyon in gusting wind conditions.Aug 18, 2018 · N8052G · DestroyedNTSB CEN18LA290Accident · Minor injuriesLimited investigationFinal reportBell 206 · Todd Mission, TXThe passenger’s inadvertent interference with the tail rotor pedals, which resulted in a loss of helicopter control during takeoff and the subsequent impact with terrain.Jul 20, 2018 · N352CT · Substantial damageNTSB GAA17CA369Accident · No injuriesData collectionFinal reportBell 206B · Entiat, WAThe pilot’s failure to secure a loose item inside the cockpit that interfered with antitorque pedal control and led to a loss of helicopter control due to a loss of tail rotor effectiveness.Jun 26, 2017 · N183TC · Substantial damageNTSB WPR17LA019Accident · Serious injuriesLimited investigationFinal reportBell 206B · Yuma, AZThe pilot’s inability to maintain helicopter control after its skid got caught on the landing pad while he was maneuvering the helicopter to land on it, which resulted in a dynamic roll-over.Nov 11, 2016 · N914HH · Substantial damageNTSB WPR16LA188Accident · No injuriesLimited investigationFinal reportBell 206B · Rockport, WAThe pilot's failure to maintain helicopter control while on the ground, which resulted in mast bumping.Sep 12, 2016 · N6181A · Substantial damageNTSB CEN14LA465Accident · No injuriesLimited investigationFinal reportBell 206B · Spring, TXThe pilot's distraction by a cell phone call, which led to his failure to perform an exterior check of the helicopter and resulted in a tie-down strap remaining attached to the main rotor during the engine start.Jul 30, 2014 · N866H · Substantial damageNTSB ERA13LA236Accident · No injuriesLimited investigationFinal reportBell 206B · Hartford, KYThe pilot’s failure to avoid a powerline that crossed a field that he was spraying. Contributing to the collision was the company’s failure to specifically mention that flight hazards be identified during a pre-work conference.May 10, 2013 · N94PH · Substantial damage