NTSB investigations: Bell 206B, UT
17 cases on aircraft the registry lists as Bell 206B. 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
| 1976 | 1 |
|---|---|
| 1981 | 3 |
| 1984 | 2 |
| 1989 | 3 |
| 1991 | 1 |
| 1992 | 1 |
| 1993 | 1 |
| 1994 | 1 |
| 2001 | 1 |
| 2002 | 1 |
| 2004 | 1 |
| 2014 | 1 |
Where
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.\"eventStateOrRegion\" = 'UT' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1181511'))
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."eventStateOrRegion" = 'UT' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1181511'))
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 WPR14LA113Accident · No injuriesLimited investigationFinal reportBell 206 · Bountiful, UTThe pilots' inaccurate assessment of the snow depth on the landing zone, which resulted in a landing on snow deeper than that for which the helicopter was equipped and led to dynamic rollover.NTSB DEN05LA024Accident · No injuriesLimited investigationFinal reportBell 206B3 · Eureka, UTthe pilot's improper in-flight planning and decision making and failure to maintain obstacle clearance, resulting in contact with a power transmission line. Contributing factors include the intentional low-level maneuver, the power transmission line, and the…NTSB DEN02LA046Accident · No injuriesLimited investigationFinal reportBell 206B-III · Moab, UTThe pilot's failure to maintain rotor rpm during a forced landing. A contributing factor was fuel starvation.NTSB DEN02LA013Accident · Serious injuriesLimited investigationFinal reportBell 206B · Bryce, UTloss of engine power for reasons undetermined. Contributing factors were the low airspeed and altitude at which to perform an autorotation.NTSB SEA94FA190Accident · 1 fatalField investigationFinal reportBell 206B III · Syracuse, UTUndeterminedNTSB SEA93FA048Accident · 4 fatalField investigationFinal reportBell 206B3 · Ogden, UTThe pilot's continuation of VFR flight into instrument meteorological conditions, and his decision to continue his landing attempts under the adverse weather conditions. Factors contributing to the accident were the low clouds, fog and mountainous terrain.NTSB SEA92FA045Accident · 2 fatalField investigationFinal reportBell 206B · Wellington, UTThe pilot's continued flight into adverse weather conditions and an excessive rate of descent. Factors contributing to the accident were fog, rain, low ceilings, night conditions, snow covered terrain and pilot disorientation.NTSB SEA92FA016Accident · 1 fatalField investigationFinal reportBell 206B · Salt Lake City, UTThe pilot failed to maintain directional control. Factors to the accident were: inadeqaute remedial action, over confidence in personal ability, and lack of recent expereince.NTSB DEN89FA175Accident · 3 fatalField investigationFinal reportBell 206B · Duchesne, UTThe pilot failed to maintain clearance from the power line. Contributing factors were: lack of mission training provided by the company/operator, the pilot's lack of experience in this type of operation, his lack of familiarity with the geographic area, and…NTSB DEN89FA101Accident · No injuriesField investigationFinal reportBell 206B-III · Park City, UTAn encounter with strong down-slope winds and gusts during a critiacal phase of flight which caused power required to exceed power available. Contributing factors to the accident was the downhill terrain and the downdraft conditions.NTSB DEN89LA059Accident · No injuriesLimited investigationFinal reportBell 206B III · Park City, UTThe selection of an unsuitable landing site by the pilot, resulting in tail rotor contact with the terrain and shearing of the tail rotor driveshaft.NTSB DEN85FA027Accident · 4 fatalField investigationFinal reportBell 206B-11 · Bingham Canyon, UTPilot was taking passeengers on a sightseeng flight over the kennecott copper mine, largest open pit copper mine in the world. Helicopter collided with unmarked power lines approx 185 ft AGL. Power lines are supported by two unmarked towers on opposing hills…NTSB DEN84FA102Accident · 1 fatalField investigationFinal reportBell 206B-III · Coalville, UTThe helicopter was equipped with 'bear paws'. Snowshoe-like devices on the skids to distribute weight on soft surfaces. The bear paws on this acft rotated freely around the skids, not tightened down as per design spec. Also, bear paws are not approved for…NTSB DEN82DTM06Accident · No injuriesClosedBell 206B · Fruitland, UTNTSB DEN81FA058Accident · Minor injuriesClosedBell 206B · Escalante, UTNTSB DEN81FTM05Accident · Minor injuriesClosedBell 206B · Vernal, UTNTSB DEN76FTM39Accident · Minor injuriesClosedBell 206B · Coalville, UT