ERA21LA357 · Enstrom F28 C
Enstrom F28 C · Accident: loss of tail rotor effectiveness while maneuvering
Event
- NTSB case
- ERA21LA357
- 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 F28 C
- Aircraft type
- Enstrom F28
- 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
- N51789
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 43 years (built 1978)
- 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 · hover
- 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
- Loss of tail rotor effectiveness
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot performed a straight in approach to runway 24 and then entered an out-of-ground-effect hover at 30 to 40 ft above ground level. He made a right turn to hover taxi to the fueling area. At that time, he noticed that the rotor rpm was low, and he attempted to increase it; however, the helicopter spun right, descended and impacted a grass area near a taxiway. The recorded wind at the airport about the time of the accident was variable at 4 knots, gusting to 10 knots. The pilot reported 10 to 12 knot gusts from the east at the time of the accident and previous and subsequent weather recordings indicated wind gusts from the south. Examination of the wreckage by a Federal Aviation Administration inspector revealed substantial damage to the lower right fuselage. The examination did not reveal any preimpact mechanical malfunctions, nor did the pilot report any. It is likely that the helicopter was in an out-of-ground effect hover with a direct or quartering tailwind, which resulted in a loss of tail rotor effectiveness.
Probable cause
The pilot’s failure to maintain control of the helicopter during an out-of-ground effect hover in a gusty wind, due to loss of tail rotor effectiveness.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA357
- Event ID
- 20210915103863
- Case number
- ERA21LA357
- 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, 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: eb25e07e72d2a2a5d1778d86cb2eb21297af1ecacb5b788e021fe4364e5449d1; retrieved 2026-09-16T14:31:50.391Z.