CEN20TA030 · Rotary RAF 2000 GTX
Rotary RAF 2000 GTX · Accident: abnormal runway contact during landing
From Millard Airport (MLE) to Millard Airport (MLE)
Event
- NTSB case
- CEN20TA030
- 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
Rotary RAF 2000 GTX
- Aircraft type
- Rotary RAF-2000
- Category
- Gyroplane
- 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
- N47EB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Millard Airport (MLE), Omaha, NETo Millard Airport (MLE), Omaha, NE
- Aircraft age
- About 22 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
- Landing · flare/touchdown
- 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
- Abnormal runway contact
- 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
- Environmental issues › Conditions/weather/phenomena
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was conducting takeoffs and landings in the gyroplane when the airplane encountered windshear just above the runway during landing. The gyroplane veered right, touched down in the grass, became airborne, then impacted terrain, resulting in substantial damage. Another pilot reported that he also experienced windshear during the landing approach and saw that the pilot of the accident aircraft "appeared to be struggling to maintain control." The accident pilot reported that he had not flown the aircraft "in a while" and that the gusting wind conditions were the primary factor that resulted in his loss of control. Recorded wind conditions about the time of the accident included wind at 13 knots with gusts to 17 knots.
Probable cause
The pilot's loss of directional control while landing in gusting wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20TA030
- Event ID
- 20191207X83916
- Case number
- CEN20TA030
- 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: e96ccc8e9d34a7fa2a10d38679bb4309fb7d286068e5bf6c15a9779d211c9512; retrieved 2026-09-16T10:44:37.250Z.