CEN11CA638 · Enstrom F-28F
Enstrom Helicopter Enstrom F-28F · Accident: loss of control in flight while maneuvering
From Menominee–Marinette Twin County Airport (MNM) to Menominee–Marinette Twin County Airport (MNM)
Event
- NTSB case
- CEN11CA638
- 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-28F
- 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
- N228F
- Operator
- Enstrom Helicopter
- Onboard fatalities
- Unknown
- Route
- From Menominee–Marinette Twin County Airport (MNM), Menominee, MITo Menominee–Marinette Twin County Airport (MNM), Menominee, MI
- 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 · 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 control in flight
- 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 oper/perf/capability
- 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
According to the pilot, the purpose of the company test flight was to measure collective stick forces with the collective bias disabled. The pilot, who was the helicopter's only occupant, lifted the helicopter into a hover and then hovered clear of any obstacles. He reported that the collective controls were heavy, as expected, but the helicopter was very controllable. During his attempt to position a force gauge between his hand and the collective grip, the pilot lost control of the helicopter and it landed hard onto the ramp. The helicopter's tail rotor blades impacted the ramp and the helicopter came to rest upright. A postaccident examination of the helicopter showed that the tail rotor blades were bent and the tail rotor driveshaft was sheared. The pilot reported that he should have taken an observer or other personnel on the flight to assist while he concentrated on flying the helicopter.
Probable cause
The pilot's failure to maintain control of the helicopter during a hover.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11CA638
- Event ID
- 20110912X14702
- Case number
- CEN11CA638
- 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: 79e5522cb212ccaf3f5736bf90c8e46c9caf9c414eb3cf3deca0b6b292c437a5; retrieved 2026-09-15T16:43:49.647Z.