WPR14GA281 · American Eurocopter Corp AS350B3 B2
Papillon Grand Canyon Helicopters American Eurocopter Corp AS350B3 B2 · Accident: loss of tail rotor effectiveness while maneuvering
From Fallon, NV to Fallon, NV
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR14GA281
- 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
American Eurocopter Corp AS350B3 B2
- 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
- N832PA
- Onboard fatalities
- Unknown
- Route
- From Fallon, NVTo Fallon, NV
- Aircraft age
- About 2 years (built 2012)
- 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 133: Rotorcraft Ext. Load
- 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 · hover
- 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
- Loss of tail rotor effectiveness
- 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 oper/perf/capability
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was positioning the helicopter with an external load into a mountain supply drop zone located along a barren ridge at an elevation of about 8,600 feet mean sea level (msl). The helicopter had completed numerous drops that day; however, the accident drop was the first since the drop zone had been moved about 100 yards downslope, on the leeward side of the ridge. The helicopter was using a 100-foot long line with a 972-pound external load. According to the pilot, as the helicopter approached the drop zone and the load was about 10 ft above the ground, the helicopter started swaying left and right, suddenly dropped in altitude, and began rotating counterclockwise. The pilot attempted to stop the uncommanded left yaw with right pedal input; he also increased collective to stop the sudden loss of altitude. The pilot set the load down and attempted to release it; however, the long line did not completely release from the hook assembly, most likely due to the helicopter's rotation. The helicopter continued to rotate to the left and descend, despite the pilot's continued application of right pedal and collective. It landed hard and rolled over onto its right side, resulting in substantial damage. The engine could be heard winding down, and a small fire erupted out of the engine compartment. Ground personnel assisted the pilot's egress, and the fire extinguished itself. No preaccident malfunctions or anomalies were identified with the helicopter, and the engine had been operating at maximum power during the accident sequence.
Wind observations taken by the ground crew on scene showed surface wind speeds between 5 and 15 knots from the southwest to west at the time of the accident. The wind just above the surface, however, was likely gusting between 5 and 25 knots as a result of an unstable atmospheric layer between the surface and 25,000 feet msl. As the wind flowed down the leeward side of the ridge, the air followed the contour of the terrain and became increasingly turbulent, resulting in downward pressure and reverse wind flow (eddy). The irregular wind conditions, high operating altitude, and the high-power, low airspeed state of the helicopter, were conducive to the development of a loss of tail rotor effectiveness, which subsequently resulted in a loss of directional control.
Probable cause
A loss of tail rotor effectiveness, which resulted in an uncontrolled rotation and descent into terrain. Contributing to the accident was a sudden shift in wind conditions and the helicopter's high power demand condition due to its load weight and operating altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14GA281
- Event ID
- 20140704X25308
- Case number
- WPR14GA281
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2014-07-04.
- API snapshot SHA-256: 210c4ee199e174f47f1d536c33f4a7575413a4ada395bc1ae0d19c8990a35bfb; retrieved 2026-09-16T00:50:39.267Z.