CEN11FA053 · Bell 206 B
Mile High Helicopter Bell 206 B · Accident: low altitude operation/event while maneuvering
From Grand Junction Regional Airport (GJT) to Meeker Airport (EEO)
Event
- NTSB case
- CEN11FA053
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Bell 206 B
- Aircraft type
- Bell 206
- Category
- Helicopter
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N8533F
- Operator
- Mile High Helicopter
- Onboard fatalities
- Unknown
- Route
- From Grand Junction Regional Airport (GJT), Grand Junction, COTo Meeker Airport (EEO), Meeker, CO
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering · low-altitude flying
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Low altitude operation/event
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Environmental issues › Physical environment
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter pilot was conducting a low-altitude pipeline patrol in a valley in a remote mountainous area. Two witnesses observed the helicopter flying toward them at a low altitude when the helicopter struck the wires of a three-phase electrical distribution line that was suspended 95 feet above the valley. The main rotor system separated from the helicopter in flight and came to rest about 200 feet from the main wreckage. The pilot stated that he never saw the wires, but that as he felt the impact, he knew immediately that he had struck wires. The on-scene investigation found no preimpact anomalies.
Probable cause
The pilot's failure to maintain clearance from electrical power lines during the low-altitude flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11FA053
- Event ID
- 20101103X83727
- Case number
- CEN11FA053
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 14125c58836115abf83af294fabf8a65606e62d9e9b3bb75207c1565c432d035; retrieved 2026-09-13T21:07:19.694Z.