CEN13LA437 · Enstrom F-28A
Salaika Aviation Enstrom F-28A · Accident: flight control system malfunction/failure while maneuvering
From Salaika Aviation Airport (07TA) to Salaika Aviation Airport (07TA)
Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN13LA437
- 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 F-28A
- Aircraft type
- Enstrom F-28
- 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
- N287Q
- Operator
- Salaika Aviation
- Onboard fatalities
- Unknown
- Route
- From Salaika Aviation Airport (07TA), Danbury, TXTo Salaika Aviation Airport (07TA), Danbury, 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
- 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
- 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 Possible conflict
Cause areas
- Aircraft › Aircraft propeller/rotor
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that, during takeoff, as the helicopter climbed through 300 feet, the private pilot started a right downwind turn. At that time, they heard a loud sound and ricocheting metal directly behind their heads, and the collective control was unresponsive. The flight instructor immediately took control of the helicopter and prepared to land. He lowered the collective to start a descent; however, the collective control was still unresponsive. He then chose to set the helicopter up for a long, shallow approach over an open field to the helipad. During a turn at 60 knots indicated airspeed, the helicopter began to oscillate vertically. The flight instructor heard popping sounds, and the oscillations increased. The main rotor rpm began to decrease, and the flight instructor lowered the collective and increased the throttle; however, the main rotor rpm continued to decrease. The helicopter started to shake violently, and the flight instructor observed that the blade pitch was very high. The shaking increased, and the flight instructor could no longer control the helicopter. A few seconds later, the helicopter impacted the ground.
The collective walking beam was found fractured immediately forward of its pivot point. The aft end of the walking beam remained attached to the upper swashplate assembly, and the pivot point remained attached to the main transmission housing. The collective control linkages forward of the walking beam fracture were consumed by the postimpact fire. Examination of the fractured pieces from two brackets and the lower universal housing of the lower swashplate assembly, the end of the push-pull rod assembly, and the collective walking beam revealed features and deformation patterns on the fracture surfaces consistent with overstress separations. No indications of pre-existing cracks or fatigue cracks were observed. Darkened areas and/or rough surface texture consistent with heat damage were observed on all of the components' surfaces. The reason for the loss of collective control could not be determined due to extensive fire damage.
Probable cause
The loss of collective control for reasons that could not be determined due to extensive fire damage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13LA437
- Event ID
- 20130728X04056
- Case number
- CEN13LA437
- 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: 056b17739789ff7adf054b94a208df97a9b71edf4205f4fff10155f8a821a55b; retrieved 2026-09-15T22:20:24.384Z.