FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16FA248 · Bell Helicopter Textron Canada 407

11 Jul 2016 · Hickory, KY, United States

Tennessee Valley Authority Bell Helicopter Textron Canada 407 · Accident: flight control system malfunction/failure on approach

From Clarksville–Montgomery County Regional Airport (CKV) to Hickory, KY (no airport)

Report a problem

Event

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

Bell Helicopter Textron Canada 407

Aircraft type
Bell 407
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
N427TV
Onboard fatalities
Unknown
Route
From Clarksville–Montgomery County Regional Airport (CKV), Clarksville, TNTo Hickory, KY (no airport)
Aircraft age
About 4 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 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
Approach · VFR pattern final
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 oper/perf/capability
  • Aircraft › Aircraft propeller/rotor
  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

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

NTSB narrative

The pilot was performing a visual approach to a landing zone to board an additional crewmember. A witness reported that there were no abnormalities in the helicopter's sound or position, until it was approximately 75 to 100 feet above the ground. Suddenly, the main rotor tilted to the right. Immediately after, the entire helicopter banked to its right and fell to the ground on its right side, where it came to rest. The main rotor blades broke apart during the impact sequence. The engine continued to run after the accident, and was subsequently shut down by responding personnel.

An examination of the wreckage revealed that the collective lever, located at the front and bottom of the swashplate support, was disconnected from the pivot sleeve. The collective lever was designed to move the pivot sleeve vertically on the swashplate support, via direct linkage from the cockpit collective control, to change the pitch on all the main rotor blades simultaneously. The collective lever pins and screws that attached the collective lever to the pivot sleeve were missing; they were later found loose, near the main rotor area. The safety wires intended to secure the screws to the pins were missing. Examination of the hardware at the NTSB Materials Laboratory revealed that the safety wires not present, and the screws backed out over time, resulting in the complete loss of collective control in flight.

Maintenance on the helicopter was performed about 38 flight hours prior to the accident. The maintenance included a 24-month inspection that required examination of the flight control bolts and nuts. The collective lever pins were not specifically included in that inspection. Two mechanics and a maintenance foreman, all employees of the operator, performed the maintenance, and all reported during postaccident interviews that they did not recall removing the safety wire or examining the pins. However, the foreman added, "I could see why it [examination of the collective lever pins] could have been done. The 24-month flight control bolt inspection was being performed, why not pull them and look at them too. I've done it before." Two of the mechanics reported that they would occasionally be "pulled off" one aircraft to work on another, and there was no work interruption policy in place. Thus, given that the safety wires were missing, it is likely that they were removed and not replaced during the most recent maintenance and that maintenance personnel did not recall taking that action due to possible work interruptions.

Subsequent to the accident, the operator implemented numerous safety initiatives to prevent recurrence, including two independent safety audits, a formal fatigue risk management program, a Safety Management System, a formal tool/material accountability program, new work interruption policies, creation of a formally-trained Safety Officer position, and a formal process for the communication of safety-critical information.

Probable cause

Company maintenance personnel's inappropriate removal without replacement of the safety wires on the collective lever pin screws during a recent maintenance inspection, which resulted in the screws backing out and led to a loss of collective control in flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16FA248
Event ID
20160711X32921
Case number
ERA16FA248
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: e17761322eb5251a5511c7406526cad9a18996b3c52dcaa6e261b8691e2e15e9; retrieved 2026-09-14T21:54:03.377Z.