CEN20CA180 · Rotorway EXEC F
Rotorway EXEC F · Accident: dynamic rollover while maneuvering
From Fulton County Airport (RCR) to Fulton County Airport (RCR)
Event
- NTSB case
- CEN20CA180
- 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
Rotorway EXEC F
- Aircraft type
- Rotorway EXEC
- 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
- N311RM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fulton County Airport (RCR), Rochester, INTo Fulton County Airport (RCR), Rochester, IN
- Aircraft age
- About 23 years (built 1997)
- 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
- Dynamic rollover
- 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 commercial pilot reported that he intended to take the helicopter out to practice hover flight. As he started to lift the helicopter off of the ground and move towards the grass, he lost control of the helicopter and it impacted the ground. An examination of the helicopter revealed substantial damage to the tail boom and main rotor. The pilot attributed his inability to maintain control of the helicopter to a stronger than expected crosswind and that he had not flown a helicopter for about 19 years.
Probable cause
The pilot's failure to maintain control of the helicopter during lift off. Contributing to the accident was the pilot's lack of recent experience flying a helicopter.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20CA180
- Event ID
- 20200518X91614
- Case number
- CEN20CA180
- 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: 559bd9c1b7827b57969c6124abbc640033adf8750a5129b678b71a7f582a804f; retrieved 2026-09-16T11:38:33.577Z.