ANC14FA030 · Robinson Helicopter Company R44 II
Global Positioning Services Robinson Helicopter Company R44 II · Accident: external load event (Rotorcraft) while maneuvering
From Birchwood Airport (BCV) to Birchwood Airport (BCV)
Event
- NTSB case
- ANC14FA030
- 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
Robinson Helicopter Company R44 II
- Aircraft type
- Robinson R44
- 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
- N392GP
- Operator
- Global Positioning Services
- Onboard fatalities
- Unknown
- Route
- From Birchwood Airport (BCV), Chugiak, AKTo Birchwood Airport (BCV), Chugiak, AK
- Aircraft age
- About 8 years (built 2006)
- 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
- 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
- External load event (Rotorcraft)
- 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
- Personnel issues › Physical
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
***This report was revised on November 29, 2017. Please see the docket for this accident to view the original report.***
The accident flight was one of several recent practice external-load flights that the pilot had been conducting with a 150-ft long-line and weighted barrel. The helicopter approached the airport from the north and then hovered over the approach end of runway 20R. At the time, two airplanes were in the airport traffic pattern for runway 20R, another was in the airport vicinity, and a fourth was departing from runway 2R toward the hovering helicopter. One witness reported hearing the accident pilot attempt to communicate with the departing northbound airplane, but no response was heard, and the airplane passed close to the helicopter. After the northbound airplane passed by, the helicopter moved to its normal landing area on the east ramp, and the accident pilot responded to another pilot's query as to his intentions by stating that he was landing. Immediately after the pilot's response, the helicopter suddenly pitched up, rolled left, and descended to the ground.
Examination of the helicopter revealed no evidence of preimpact mechanical anomalies with the airframe, systems, or powerplant. Damage to the main rotor and associated ground scars and wreckage distribution were consistent with the rotor system operating at normal rpm during the impact sequence. Damage to the helicopter and the location of the main rotor ground scar were consistent with the helicopter having collided with the ground in an extreme left roll. The long-line remained attached to the barrel but was not attached to the helicopter's cargo hook, and the disconnected end was near the main wreckage. The relative orientation of the long-line and the main wreckage indicated that the line was still attached to the helicopter when the helicopter moved laterally at some point; however, no known witness observed when or how smoothly the line and load were released.
Maneuvering a helicopter to land during external load operations requires precision in both helicopter control and timing of load release. Although the accident pilot's workload was increased by the demands of maintaining traffic separation and communicating on the radio in the busy, nontowered airport environment, there was no evidence to suggest that such an operation was beyond his skill level, particularly given his recent practice. The accident pilot was based at BCV and, in the 2 weeks before the accident, had conducted seven flights (including the accident flight) with a 150-foot long-line in the accident helicopter; in the preceding 90 days, the pilot had flown almost 60 hours, most of which involved autorotations, hover maneuvers, and long-line practice.
The pilot's autopsy identified severe coronary artery disease with greater than 75% stenosis in two main arteries. In addition, scarring in the left ventricle was identified, which indicated that the pilot had experienced a previous heart attack. Although the pilot had sought and received in recent years medical care that included cardiac testing, there is no evidence that his previous heart attack was ever diagnosed (research has shown that the tests are not always accurate). Given the presence of two severely stenotic lesions in two main arteries and the presence of scarring from a previous heart attack, the accident pilot's likelihood for experiencing another acute cardiac event (such as a new heart attack, anginal symptoms, or an acute arrhythmia) was inevitable. An acute cardiac event would likely cause symptoms ranging in severity from impairing (such as chest pain and shortness of breath or palpitations) to incapacitating (fainting from low blood pressure or sudden cardiac death). Further, such an event occurring immediately before impact would likely leave no identifiable evidence on autopsy. Considering the precision required while maneuvering to land with an external load, any level of impairment could result in catastrophic consequences; therefore, the pilot likely experienced a sudden, acute cardiac event that adversely affected his performance.
Probable cause
The pilot's loss of control of the helicopter due to impairment or incapacitation from a sudden, acute cardiac event.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC14FA030
- Event ID
- 20140529X73728
- Case number
- ANC14FA030
- 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: 489824c96b1a32b3bb17548d904b289bd6d7ef66aaff0d0a3fe937ca3f0a6531; retrieved 2026-09-14T17:18:33.499Z.