ERA24LA327 · Enstrom 280FX
Enstrom 280FX · Accident: settling with power/vortex ring state while maneuvering
Event
- NTSB case
- ERA24LA327
- 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
- Event fatalities
- Unknown
- 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
- N280D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 36 years (built 1988)
- 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 · 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
- Settling with power/vortex ring state
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor uneventfully demonstrated a rapid deceleration maneuver to the fixed-wing pilot-rated passenger into the wind, performed a left pedal turn, and performed another rapid deceleration maneuver (with a tailwind). The flight instructor then initiated another left pedal turn; however, the helicopter failed to turn, and the low-rotor RPM light came on. The flight instructor said that he attempted to recover by lowering the collective and adding full throttle, but the throttle was already fully open. The low-rotor RPM light remained illuminated and engine RPM started to drop. The helicopter landed and slid down a slope adjacent to the runway and came to rest on its left side. This resulted in substantial damage to the main rotor blades and tail cone. The pilot rated passenger provided a similar account of the events and said that after he exited the helicopter, the instructor told him that they had just “settled with power.” The flight instructor reported there were no mechanical deficiencies that contributed to the accident.
Probable cause
The flight instructor’s failure to maintain sufficient rotor rpm while maneuvering the helicopter low to the ground, which resulted in a loss of control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA327
- Event ID
- 20240729194783
- Case number
- ERA24LA327
- 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, cause areas. 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: 5ccb055fd9662f35c33ea030e99e860d00ccc571bb9bd0426f18005c0cd9929b; retrieved 2026-09-16T19:05:33.984Z.