FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16LA015 · Bell 206L 3

15 Oct 2015 · Dickinson, AL, United States

Couch Helicopter Services Bell 206L 3 · Accident: flight control system malfunction/failure while maneuvering

From Dickinson, AL to Dickinson, AL

Report a problem

Event

NTSB case
ERA16LA015
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

Bell 206L 3

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
N206CJ
Onboard fatalities
Unknown
Route
From Dickinson, ALTo Dickinson, AL
Aircraft age
About 23 years (built 1992)
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 137: Agricultural
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 › Task performance

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

NTSB narrative

During an aerial application flight, the helicopter was flying between 70 and 120 ft above trees, and the pilot heard a "pop" sound followed by an immediate loss of tail rotor thrust. He lowered collective and descended into trees, and the helicopter came to rest on its left side. Examination of the helicopter determined that the loss of tail rotor thrust was precipitated by a disconnect in the tail rotor drive system. A self-locking nut securing one of the two bolts that attached the aft end of the first tail rotor driveshaft (shaft S1) aft of the oil cooler blower to the disc pack coupling was missing. The nut and the bolt that it secured were not recovered at the accident site. The separated hardware allowed misalignment of the driveshaft with the axis of rotation, which led to the fracture of shaft S1 and of the second tail rotor driveshaft (shaft S2) aft of the oil cooler blower. The prevailing or tare torque on two out of the remaining three self-locking nuts securing the forward and aft ends of shaft S1 to the disc pack couplings were below the minimum torque specified in the helicopter manufacturer's standard practices manual. The prevailing torque is a measure of the turning resistance of a lock nut, and the turning resistance generally decreases as nuts are reused.

About 490 hours earlier, the operator had performed a modification to the helicopter that required in part, removal of shaft S1 and the tailboom assembly. Since this modification, the helicopter had been subjected to four 100-hour inspections. Three lots of defective nuts of the type used to secure components of the tail rotor drive system had been identified; however, the operator could not determine whether they had previously had any of the suspect nuts in stock. Although the possibility of a defective nut resulting in the driveshaft disconnect could not be eliminated, given the insufficient prevailing torque on 2 of the remaining 3 self-locking nuts securing shaft S1 to the disc pack couplings, it is more likely that the separated nut also had insufficient prevailing torque. And it was that insufficient prevailing torque of the missing self-locking nut that had been removed and improperly re-installed by the operator's maintenance personnel, which allowed the self-locking nut to back-off. This accident and six previous accidents involving the same make and model of helicopter illustrate an in-service issue with hardware used to secure the tail rotor driveshafts. As a result of these accidents, Transport Canada issued a safety alert notifying maintenance personnel of the need to check the prevailing or tare torque of hardware securing the tail rotor drive system.

Probable cause

The improper installation by company maintenance personnel of the securing hardware of a tail rotor driveshaft section, which resulted in that section of tail rotor driveshaft disconnecting and a complete loss of tail rotor thrust.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16LA015
Event ID
20151015X81026
Case number
ERA16LA015
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: 1115026fcc96521c4ed15e66d32f0270a4f5a3ad2fda261a99b315a69c9559a9; retrieved 2026-09-16T02:53:34.417Z.