WPR10FA112 · Eurocopter AS350 B3
Air Methods Eurocopter AS350 B3 · Accident: collision with terrain/object (non-CFIT) during autorotation
From Renown Regional Medical Center Heliport (NV57) to Winnemucca, NV
Event
- NTSB case
- WPR10FA112
- 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
- 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
Eurocopter AS350 B3
- Aircraft type
- Eurocopter AS350
- 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
- N904CF
- Operator
- Air Methods
- Onboard fatalities
- Unknown
- Route
- From Renown Regional Medical Center Heliport (NV57), Reno, NVTo Winnemucca, NV
- 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
- Autorotation
- 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
- Collision with terrain/object (non-CFIT)
- 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
- Aircraft › Aircraft propeller/rotor
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he lifted the single-engine helicopter from the helicopter pad for the emergency medical service positioning flight to pick up a patient. The pilot maneuvered the helicopter into a 25-foot hover and, just as he was beginning the transition to forward flight, he heard a loud bang. The helicopter experienced a power loss and the pilot lowered the collective slightly, resulting in a hard landing on the pad. A surveillance camera that captured the accident sequence indicated that after the helicopter lifted into a hover over the pad, the nose abruptly rotated right 90 degrees and the helicopter descended vertically in a slight nose-down attitude, landing hard on the helipad.
The postaccident airframe examination revealed that the nuts that attach the engine-to-main gear box flex coupling were not present on their respective bolts. The nuts and associated washers were located loose and clumped together just forward of the gimbal ring in the transmission input housing. An examination of the bolts and flex coupling by the Safety Board Materials Laboratory concluded that the nuts most likely had been hand tightened and that cotter pins had not been installed on the bolts. The improper installation lead to the failure of the flex coupling and resulted in a loss of power to the rotor system.
Maintenance records showed that 59 flight hours before the accident the engine had been removed, the helicopter painted, and then the engine was reinstalled. The time between the engine removal and the reinstallation was 88 days. The mechanic who removed the engine stated that he removed the bolts to the engine-to-main gear box flex coupling, and then partially reassembled the flex coupling bolts. This action was not in accordance with the AS350 maintenance manual engine removal procedure. The mechanic who installed the engine 88 days later stated that he did not check the flex coupling bolts because the removal of those bolts is not specified in the maintenance manual as part of the engine removal or replacement procedure. The overall maintenance activity involved a 100-hour inspection, which included a visual inspection of the engine-to-main gear box flex coupling. Although a visual inspection of the engine-to-main gear box flex coupling is a required action, the Quality Assurance inspector signed off the maintenance without performing the visual inspection of the flex coupling.
Probable cause
The improper installation of the engine-to-main gear box flex coupling, which resulted in the failure of the flex coupling and a loss of power to the rotor system during takeoff. Contributing to the accident was the mechanic who removed the engine's failure to follow the operator’s maintenance procedures. Also contributing was the Quality Assurance inspector's failure to follow the operator’s post-maintenance inspection requirements.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10FA112
- Event ID
- 20100117X91508
- Case number
- WPR10FA112
- 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: 49a39310e78138132b82748193db2f3b3dd9147d3ffb1ca80679df6c3c1cd1e6; retrieved 2026-09-15T13:37:50.425Z.