Fatal NTSB investigations: Bell 206L-3
22 cases on aircraft the registry lists as Bell 206L-3. 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
| 1983 | 1 |
|---|---|
| 1988 | 1 |
| 1989 | 1 |
| 1992 | 1 |
| 1994 | 2 |
| 1995 | 2 |
| 1998 | 1 |
| 2003 | 3 |
| 2005 | 1 |
| 2006 | 1 |
| 2007 | 1 |
| 2013 | 1 |
| 2014 | 1 |
| 2017 | 1 |
| 2019 | 1 |
| 2020 | 1 |
| 2024 | 2 |
Where
Open the mapLatest 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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1182108'))
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.
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1182108'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB ERA25FA005Accident · 3 fatalClass 3 · FieldPreliminary reportBell 206L-3 · Owenton, KYOn October 7, 2024, at 1730 eastern daylight time, a Bell 206L3+, N230AE, was destroyed when it was involved in an accident in Owenton, Kentucky. The pilot, a flight nurse, and a flight medic were fatally injured. The helicopter was operated by Air Evac Life…NTSB CEN24FA094Accident · 3 fatalClass 3 · FieldFinal reportBell 206 · Hydro, OKThe helicopter’s inflight collision with cackling geese, resulting in an inflight breakup.NTSB WPR20LA163Accident · 3 fatalClass 3 · LimitedFinal reportBell 206 · Fairfield, CAThe pilot’s failure to maintain adequate clearance from powerlines while conducting external load operations, which resulted in the main rotor contacting a wire and a subsequent collision with terrain.NTSB WPR19LA071Accident · 1 fatalClass 3 · LimitedFinal reportBell 206 · Ashland, ORThe pilot's decision to continue visual flight into deteriorating weather, which resulted in an encounter with instrument meteorological conditions and spatial disorientation leading to a loss of control.NTSB CEN17FA355Accident · 1 fatalField investigationFinal reportBell 206L 3 · Ancho, NMThe pilot's distraction by a cell phone during a low-altitude flight, which resulted in controlled flight into terrain.NTSB CEN14FA122Accident · 3 fatalField investigationFinal reportBell 206L 3 · Silt, COThe pilot’s inadequate preflight planning for a low-level aerial surveillance flight of power transmission lines, which led to his being unaware of the crossing power line while flying toward the sun and his subsequent failure to maintain sufficient clearance…NTSB CEN14FA004Accident · 1 fatalField investigationFinal reportBell 206L 3 · Venice, LAA total loss of engine power due to the liberation of a second stage turbine blade near the blade root due to a high-cycle fatigue crack and subsequent overload. Although extensive testing and materials analysis was performed, the reason for crack initiation…NTSB NYC08FA071Accident · 3 fatalField investigationFinal reportBell 206L-3 · Cherokee, ALThe pilot's failure to maintain control of the helicopter during an out-of-ground-effect hover. Contributing to the accident was a loss of tail rotor effectiveness.NTSB DFW06IA145Incident · 1 fatalIncident investigationFinal reportBell 206L-3 · Grand Isle 43AAThe pilot's incapacitation and death due to pre-existing cardiac disease.NTSB DFW06FAMS1Accident · 3 fatalMissing aircraftFinal reportBell 206-L3 · Gulf of MexicoUndetermined. The aircraft is missing.NTSB FTW04FA007Accident · 3 fatalField investigationFinal reportBell 206L-3 · W. Cameron 509The pilot's loss of control following an inadvertent encounter with adverse weather conditions. Contributing factors were the prevailing thunderstorms, the low ceilings, and the miscommunication between the pilot and the company's communication center in…NTSB CHI03FA259Accident · 3 fatalField investigationFinal reportBell 206L-3 · E.I. 276, LAThe inadequate compensation for crosswind conditions and the directional control not obtained/maintained by the pilot during takeoff. Contributing factors were the crosswind and the planned approach to position the helicopter with a crosswind in order to…NTSB LAX03GA244Accident · 2 fatalFinal reportBell 206L-3 · Whiteriver, AZThe pilot's failure to maintain a minimum translational lift airspeed while maneuvering in high density altitude conditions at near maximum required torque and above the in ground effect hover altitude, that resulted in a loss of tail rotor effectiveness and…NTSB ATL98FA080Accident · 5 fatalField investigationFinal reportBell 206L-3 · Indian Trail, NCThe pilot's failure to maintain altitude while operating in adverse weather. A contributing factor was the incoming fog and high tension static wire.NTSB FTW95FA308Accident · 1 fatalField investigationFinal reportBell 206-L3 · Borger, TXThe pilot's loss of control due to an encounter with a dust devil/whirlwind and the turbulence and high wind associated with thunderstorm outflow.NTSB FTW95FA186Accident · 1 fatalField investigationFinal reportBell 206L-3 · Venice, LALoss of engine power due to ingestion of exhaust fumes from an oil platform flare boom.NTSB FTW94GA232Accident · 3 fatalFinal reportBell 206L-3 · Mimbres, NMThe pilot's improper decision to attempt to hover out of ground effect under adverse conditions while exceeding the maximum allowable weight for that maneuver. Factors in the accident were: high density altitude and the tailwind.NTSB MIA94FA053Accident · 1 fatalField investigationFinal reportBell 206L3 · Arcadia, FLThe pilot-in-command's improper supervision of an unqualified pilot while attempting a takeoff to a hover. This resulted in an on ground loss of control (dynamic roll over). The improper flight control input (cyclic and collective) by the unqualified pilot…NTSB FTW92FA112Accident · 2 fatalField investigationFinal reportBell 206L-3 · Venice, LAThe pilot's incapacitation due to food poisoning.NTSB DEN89MA130Accident · 4 fatalMajor investigationFinal reportBell 206L-3 · Big Timber, MTFailure of the pilot to maintain control of the aircraft during takeoff, due to spatial disorientation, which resulted in a collision with the terrain. Contributing factors were: dark night, pilot's visual perception, inadequate initial training of the pilot…NTSB DEN89FA019Accident · 2 fatalField investigationFinal reportBell 206L-3 · Deckers, COWhile on a corporate flt thru a canyon in marginal wx conds, the helicopter collided with the static portion of a power transmission line & crashed. The acdnt occurred where a 2,554 ft span of the power line crossed the south platte river. The power line…NTSB FTW83FA097Accident · 2 fatalField investigationFinal reportBell 206L-3 · Goliad, TXThe helicopter collided with trees and the ground in an attempt to reverse directions at low alt & at night after encountering weather. The plt had received a weather briefing and knew the weather was bad with low ceilings and fog. Heradioed he could make it…