WPR15FA051 · Robinson Helicopter Company R44 II
Native Range Robinson Helicopter Company R44 II · Accident: flight control system malfunction/failure while maneuvering
From Skypark Airport (BTF) to Skypark Airport (BTF)
Event
- NTSB case
- WPR15FA051
- 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
- 2 · 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
- N3234U
- Operator
- Native Range
- Onboard fatalities
- Unknown
- Route
- From Skypark Airport (BTF), Bountiful, UTTo Skypark Airport (BTF), Bountiful, UT
- Aircraft age
- About 7 years (built 2007)
- 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
- Maneuvering · low-altitude flying
- 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
- Flight control system malfunction/failure
- 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 › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Before the accident flight, the commercial helicopter pilot, who was also a mechanic, had re-installed the main rotor blades, which had just been reworked, on the helicopter. The accident flight was a test flight to adjust the track and balance of the rotor blades. A mechanic, who spoke with the pilot a few weeks before the accident, stated that they had a discussion about an elongated pitch change link attachment hole on the accident helicopter and how to address it. On the night before the accident flight, they spoke again; the pilot was having trouble tracking the blades on the accident helicopter. The pilot stated that he could not get the blades to track any better, and that he was trying to change the track with the trim tabs.
Witnesses in the area of the accident site heard "popping" or "banging" sounds, then saw the main rotor and empennage separate from the helicopter. Several of the witnesses then saw the helicopter tumble in flight and impact the roof of a building. The main rotor and empennage came to rest on the ground a few hundred feet from the building. Witness statements and wreckage documentation were consistent with a main rotor blade striking the tail and subsequently, a mast bump, which resulted in the helicopter descending uncontrollably.
The damage observed on the components of the main rotor system was consistent with an in-flight separation of the pitch change link for the red blade, with separation occurring at the location where the pitch change link attached to the swashplate. The swashplate was free of contact marks corresponding to contact with the red pitch change link, which contrasted with the area around the blue blade pitch change link attachment, where multiple contact marks corresponding to contact with the blue pitch change link were observed. Also, the red pitch change link was intact and relatively straight, indicating that separation occurred under loads less than that required to buckle or fracture the pitch change link. The slight bending in the red pitch change links was likely secondary to the separation of the attachment at the lower end as evidenced by the location of the corresponding thread contact marks on the pitch horn. Finally, a series of impressions corresponding to contact with threads on the red blade pitch change link attachment bolt were observed on the attachment hole bore through the swashplate in an area that should have only contacted the grip portion of the bolt. Thus, it is likely that the intact bolt separated from the attachment due to loss of the lock nut and palnut.
Torque measurements were obtained on the locknuts installed on the three recovered pitch change link attachment bolts. All measured torque values were lower than that specified in the helicopter's maintenance manual, indicating that the fasteners were improperly torqued before the accident. While torque for the missing attachment bolt could not be measured, the torque measured on the remaining pitch change link attachment bolts and witness marks on the attachment hole bore in the swashplate suggest that the bolt likely separated due to insufficient torque applied at the time of installation, which led to the loss of the locknut and palnut due to vibrational loads under normal operation.
Probable cause
The pilot/mechanic's failure to properly secure the pitch link hardware of one main rotor blade to the rotating swash plate, which resulted in the pitch link separating in flight and a subsequent loss of control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR15FA051
- Event ID
- 20141202X73240
- Case number
- WPR15FA051
- 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: 814ceb947ca7abc2c1c4495f2089e9cc14e25c08b48a8f04e8c9aff9579e10c9; retrieved 2026-09-14T17:29:28.792Z.