DEN89FA175 · Bell 206B
Rocky Mountain Helicopter Bell 206B · Accident: in flight collision with object en route
From Provo Municipal Airport (PVU) to Provo Municipal Airport (PVU)
Event
- NTSB case
- DEN89FA175
- 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
- 3 · all aircraft and ground
- Ground fatalities
- 0
- 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 206B
- 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
- N1086C
- Operator
- Rocky Mountain Helicopter
- Onboard fatalities
- Unknown
- Route
- From Provo Municipal Airport (PVU), Provo, UTTo Provo Municipal Airport (PVU), Provo, UT
- 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
- En route · cruise
- First occurrenceThe 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
- In flight collision with object
- 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, transmission; Wire, static
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE HELICOPTER WAS BEING OPERATED ON A SPECIALIZED POWER LINE PATROL TO CONDUCT 'KORONA MEASURING' FOR A 'LEAKAGE' CHECK OF THE TRANSMISSION LINE. THIS CHECK REQUIRED THAT THE HELICOPTER BE FLOWN AT A CONSTANT ALTITUDE & SPEED, & AT A DISTANCE OF 100' OR LESS FROM THE POWER LINE. WHILE PATROLLING EASTBOUND, THE MAIN ROTOR STRUCK THE NORTH STATIC LINE. SUBSEQUENTLY, THE MAIN ROTOR, SWASH PLATE, & TRANSMISSION/ROTOR MAST SEPARATED & THE HELICOPTER CRASHED. WHEN THE HELICOPTER DID NOT RETURN FROM THE PATROL, A SEARCH WAS ORGANIZED. THE WRECKAGE WAS FOUND THE NEXT DAY AT 1045 MDT. THE PLT & 1 PAX WERE DECEASED, BUT THE OTHER PAX APPEARED TO BE ALIVE; HOWEVER, HE DIED BEFORE MEDICAL ASSISTANCE ARRIVED. NO PREIMPACT PART FAILURE OR MALFUNCTION OF THE HELICOPTER WAS FOUND. AN INVESTIGATION REVEALED THIS WAS THE PILOT'S 1ST POWER LINE PATROL. ON HIS APPLICATION FOR RECENT EMPLOYMENT WITH THE COMPANY, HE INDICATED HE HAD OVER 1900 HRS OF FLT TIME; HOWEVER, ONLY 585 HRS OF FLT TIME COULD BE VERIFIED. HE DID NOT RCV MISSION TRAINING FOR THIS FLT.
Probable cause
THE 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 THE COMPANY/OPERATOR'S INADEQUATE SUBSTANTIATION PROCESS TO ASSURE THE EXPERIENCE LEVEL OF NEWLY HIRED PILOTS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN89FA175
- Event ID
- 20001213X28793
- Case number
- DEN89FA175
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 85922c4033a334efdb9abdfe6f5398b8c786714152917e372acd8cf197cf7f3a; retrieved 2026-09-21T03:13:50.245Z.