FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13FA192 · Sikorsky S-76A++

15 Mar 2013 · Grand Lake, LA, United States

ERA Helicopters Sikorsky S-76A++ · Accident: aircraft structural failure while maneuvering

From Lake Charles Regional Airport (KLCH) to Lake Charles Regional Airport (KLCH)

Report a problem

Event

NTSB case
CEN13FA192
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
3 · 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

Sikorsky S-76A++

Aircraft type
Sikorsky S-76
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
N574EH
Onboard fatalities
Unknown
Route
From Lake Charles Regional Airport (KLCH), Lake Charles, LATo Lake Charles Regional Airport (KLCH), Lake Charles, LA
Aircraft age
About 23 years (built 1990)
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
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
Aircraft structural failure
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

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft propeller/rotor

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot and two mechanics were conducting a post-maintenance check flight of the helicopter's avionics system. After testing the avionics, the pilot allowed the mechanic to fly the helicopter at 1,000 feet above ground level. The mechanic maneuvered the helicopter for about 1 minute and then stated that he was transferring control of the helicopter back to the pilot. Two seconds later, the cockpit voice recorder (CVR) cut off. About 1 minute after the CVR cut off, the pilot made a routine radio call to the tower controller that he was returning to land. Two minutes after this call, the pilot radioed the tower controller and his company's dispatcher, stating that he had a problem and would be landing off-airport immediately. Several ground witnesses noticed the helicopter as it flew toward the accident site, and it was making an unusual noise, described as grinding, screeching, or whistling. The helicopter impacted with a high vertical descent rate and a postcrash fire ensued.

Examination of the helicopter revealed that the main rotor and tail rotor systems had low rotational energy at the time of ground impact. Two of the tail rotor blades (yellow and red) were fractured adjacent to the tail rotor hub. The fracture signatures on the red/yellow tail rotor spar assembly were consistent with the red tail rotor blade spar initially fracturing and the red tail rotor blade departing from the tail rotor.

The resultant imbalance of the tail rotor fractured the tail gearbox (TGB) output housing studs and most likely tripped the CVR g-switch, which cut off the CVR. The yellow tail rotor blade spar fractured due to high centrifugal forces as a result of the imbalance, and the yellow blade departed from the tail rotor; the tail rotor was then rebalanced. The two remaining tail rotor blades continued to provide partial tail rotor anti-torque, and tail rotor drive remained continuous through the TGB. The entirety of the red and yellow blade separation event likely occurred very quickly, with only a momentary bump or vibration at the time of blade separation.

As the TGB output housing began to separate from the center housing, the gears likely began going out of mesh, allowing the output bevel gear to eventually contact the TGB center housing. This condition likely resulted in the loud, unusual noise reported by witnesses, as well as a drag force on the tail rotor drive system. As the pilot attempted to land, he likely shut the engines down in conjunction with an autorotative landing. Because the tail rotor drive system and main transmission remained mechanically linked, when the engines were shut down, it is likely that main rotor speed (Nr) degraded due to the compromised TGB. As a result, the helicopter developed a high vertical descent rate until ground impact.

The red blade spar fracture signatures were consistent with a fast-growth failure mode. Plausible fast-growth failure modes that were examined included a discrete impact event (e.g. object strike), anomalous operation of the pivot bearing, and a fracture of the pitch horn box (the structure which attaches the pitch horn to the blade and to which the pivot bearings and bumper attaches). With the lack of available evidence because the red blade was not recovered, the specific failure mode could not be determined during the investigation.

Probable cause

Fracture of the red tail rotor blade spar, which resulted in the separation and departure of the red tail rotor blade from the helicopter and subsequent compromised tail gearbox. The red tail rotor blade was not recovered, thus the cause of the initial fracture could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13FA192
Event ID
20130315X34542
Case number
CEN13FA192
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, coordinates. 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: b8e21f66a23c440f6b2ef01fb403f392357de354198510e6aa4c46bd295867b2; retrieved 2026-09-14T15:54:23.628Z.