Rocky Mountain Helicopter Aerospatiale SA316B accident
Aerospatiale SA316B · Accident: loss of control in flight en route
From an unrecorded airport to No airport
Event
- NTSB case
- DEN90FA172
- 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
- 0 · 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
- Charter & commuter
- 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
Aerospatiale SA316B
- Aircraft type
- Aerospatiale SA316
- 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
- N83776
- Operator
- Rocky Mountain Helicopter
- Onboard fatalities
- Unknown
- Route
- From not recordedTo No airport
- 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 135: Air Taxi & Commuter
- 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
- Loss of control in flight
- 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
- Rotor system, main rotor hub lead-lag stop/damper › Failure, total
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
APPROXIMATELY 2 MINUTES INTO THE FLIGHT, THE PILOT EXPERIENCED A SLIGHT 1 TO 1 VIBRATION THROUGH THE CYCLIC. THIS TYPE VIBRATION IS ASSOCIATED WITH MAIN ROTOR DAMPERS AND THE PILOT 'STIRRED' THE CYCLIC IN AN EFFORT TO PURGE AIR OUT OF THE BLADE DAMPERS. THIS ELIMINATED THE PROBLEM, HOWEVER, IT RECURRED AND COULD NOT BE ELIMINATED. THE VIBRATION INCREASED TO THE POINT OF LOSS OF CONTROL. AN EMERGENCY LANDING WAS ATTEMPTED WITH TOUCHDOWN OCCURRING AT ABOUT 60 KNOTS. THE HELICOPTER CAME TO REST INVERTED AND WAS LARGELY CONSUMED BY POST-IMPACT FIRE. METALLURGICAL ANALYSIS ON A FAILED BLADE RESTRAINING CABLE REVEALED A CATASTROPHIC FAILURE IN A LOW CYCLE FATIGUE MODE CONSISTENT WITH A SECONDARY CAUSE, AND DUE TO SHORT TERM VIBRATIONS. IN ADDITION TO FATIGUE, THERE WAS EVIDENCE OF PLASTIC DEFORMATION DUE TO VIBRATORY LOADS FROM THE DAMPER SYSTEMS. FIRE DAMAGE PREVENTED ADDITIONAL FAILURE ANALYSIS.
Probable cause
A MAIN ROTOR HEAD BLADE DAMPENER FAILURE. A FACTOR IN THE ACCIDENT WAS THE SUBSEQUENT FAILURE OF A BLADE RESTRAINING CABLE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN90FA172
- Event ID
- 20001212X23977
- Case number
- DEN90FA172
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1990-08-20.
- API snapshot SHA-256: 60576bac0bb7097b2398a3c586ec9598760d1df47dccc393743bc7df2cfd067e; retrieved 2026-09-18T18:59:54.243Z.