FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12LA228 · Enstrom 280FX

3 Apr 2012 · Corpus Christi, TX, United States

Travland Helicopters Intl Enstrom 280FX · Accident: system/component malfunction/failure (non-power) on approach

From South Texas International at Edinburg Airport (EBG) to Corpus Christi International Airport (CRP)

Report a problem

Event

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

Enstrom 280FX

Aircraft type
Enstrom 280
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
N3042D
Onboard fatalities
Unknown
Route
From South Texas International at Edinburg Airport (EBG), Edinburg, TXTo Corpus Christi International Airport (CRP), Corpus Christi, TX
Aircraft age
Not recorded
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
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

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

NTSB narrative

After an uneventful flight, the pilot slowed the helicopter into a stable hover about 15 feet above the landing point. Although the engine continued to operate, the main rotor rpm suddenly decayed and the helicopter landed hard. The pilot, who had over 5,600 flight hours in helicopters, stated that there was no warning before the loss of main rotor drive. The helicopter was in a position whereby power to the rotor system was essential to conducting a safe landing. Examination of the helicopter revealed that the bolt that retains the clutch drive rod end in the clutch pivot fork had sheared, resulting in the clutch disengaging. Once the clutch disengaged, there was no drive to the rotor system, and the helicopter's descent could not be arrested. With the exception of the failed bolt, examination of the entire drive system did not show any preexisting mechanical malfunction or abnormalities that would have precluded normal operation. The helicopter had operated about 1,350 hours since it was new, and the retaining bolt was the original installation. The reason for the failure of the bolt could not be determined.

Probable cause

The failure of the bolt that retained the clutch drive rod end, which resulted in a loss of main rotor drive and a subsequent hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12LA228
Event ID
20120405X35953
Case number
CEN12LA228
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: e7407d3f53c23fd8b8533c498c2a1f46044396fa2c6d53f189713f4a9c5caf2b; retrieved 2026-09-15T17:40:13.576Z.