FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24LA319 · Bell 206L

26 Sept 2024 · Fern Prairie, WA, United States

JL Aviation Bell 206L · Accident: system/component malfunction/failure (non-power) en route

From Pigeon Springs, WA to Fly JLA Airport (OR72)

Report a problem

Event

NTSB case
WPR24LA319
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
Event fatalities
Unknown
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

Bell 206L

Aircraft type
Bell 206
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
N9984K
Operator
JL Aviation
Onboard fatalities
Unknown
Route
From Pigeon Springs, WATo Fly JLA Airport (OR72), Boring, OR
Aircraft age
About 48 years (built 1976)
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
En route
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
System/component malfunction/failure (non-power)
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
  • Aircraft › Aircraft structures
  • Organizational issues › Management

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that, while in cruise flight at about 100 kts and about 1,000 ft above ground level (agl), the helicopter suddenly exhibited a severe vertical oscillation, commonly referred to as a “vertical hop.” Believing a catastrophic mechanical failure was imminent, he lowered the collective to initiate an emergency descent. Just before landing alongside a forest road, the pilot raised the collective and slowed the helicopter, and the vertical hop subsided. After landing, the pilot exited the helicopter and observed substantial damage to the tailboom and fuselage. Postaccident examination revealed the helicopter’s tailboom was buckled around its entire circumference. The tailboom buckling was likely the direct result of abnormally high structural loads imposed on the airframe during the vertical hop. This violent oscillation generated dynamic loads exceeding the normal structural design limits of the tailboom, resulting in it buckling about 13 inches aft of the intercostal support, and displacing it downward about 15° and to the right. The full monocoque construction of the tailboom, while robust under normal flight loads, can sustain damage when under the sudden, cyclically-amplified bending forces associated with this type of resonant vibration event. Although the helicopter’s collective lever could be moved with less force than specified by the manufacturer, it is unlikely that the vertical oscillations were due to collective bounce (an interaction between the pilot’s arm and the vibration of the airframe that can be exacerbated by low friction clamp force on the collective control) because the pilot did not have his hand on the collective lever when the oscillations started. About five months before the accident, the helicopter’s metal Bell main rotor blades were replaced with composite main rotor blades produced by Van Horn Aviation (VHA). The underlying source of the vibration itself was likely an aeroelastic interaction between these main rotor blades and the helicopter's nodal beam transmission mount under a specific set of operating conditions. Based on at least 26 similar reports in Bell 206Ls dating back to 2019, VHA identified the triggering conditions as single-pilot operation, low fuel load, and airspeeds above 85 kts, all of which were present in this accident. In addition, out-of-tolerance maintenance conditions, such as main rotor blades configured with forward sweep, increased the likelihood of a helicopter exhibiting hops, and increased the severity of the oscillations when they occurred. Under these conditions, the light helicopter weight and the shift of the center of gravity aft alters rotor system dynamics, allowing a resonant vibration to develop between the rotor blades and the nodal beam mount. When encountered, this vibration can be lessened or stopped by banking, raising the collective, or slowing the helicopter. About 2.5 years before the accident (or about 2 years before the operator installed the main rotor blades on the helicopter) VHA posted a vertical hop recovery technique on social media and in a newsletter, but did not publish it in their technical library until after the accident. The use of blogs, social media, and a newsletter may have initially been an effective means of alerting operators; however, the lack of a persistent, retrievable reference in VHA’s technical library likely precluded operators from learning about the recovery technique if they had not read the newsletter or seen the posts before they were superseded by more recent posts. According to the pilot, he was not aware of the recovery techniques until after the accident. Had the pilot been aware of and implemented the appropriate recovery techniques, he likely would have been able to prevent the oscillations from reaching a structurally damaging amplitude.

Probable cause

An aeroelastic interaction between the helicopter’s main rotor blades and nodal beam system, which resulted in oscillations that exceeded the design limits of the tailboom. Contributing to the accident was the failure of the main rotor blade manufacturer to adequately publish the appropriate recovery technique for a known flight dynamics issue.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24LA319
Event ID
20240930195230
Case number
WPR24LA319
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, cause areas. 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: 69beb112817d6580a5b1b57ab47c4331fe8c5f1ea22555f8e885c65d0aa68261; retrieved 2026-09-16T19:20:11.137Z.