GAA19CA226 · Guimbal CABRI G2
Precision Flight Training Guimbal CABRI G2 · Accident: loss of control on ground during landing
From McMinnville Municipal Airport (MMV) to McMinnville Municipal Airport (MMV)
Event
- NTSB case
- GAA19CA226
- 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
Guimbal CABRI G2
- Aircraft type
- Guimbal CABRI
- 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
- N367PA
- Operator
- Precision Flight Training
- Onboard fatalities
- Unknown
- Route
- From McMinnville Municipal Airport (MMV), Mc Minnville, ORTo McMinnville Municipal Airport (MMV), Mc Minnville, OR
- Aircraft age
- About 4 years (built 2015)
- 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
- Loss of control on ground
- 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
The pilot reported that the purpose of the training flight was to complete multiple simulated, engine failure autorotations without a power recovery (full-down autorotation). After he completed his first right, 180º turn, full-down autorotation, the airspeed was "too slow." He added that the instructor told him to maintain more speed during the right turn of his second attempt, and the pilot focused on maintaining more airspeed, but the descent rate increased "due to the speed." The pilot added that, after he completed the right turn and aligned with the runway centerline, he felt that the airspeed was fast, so he flared to reduce the ground speed and increase the main rotor rpm. However, the helicopter started to sink during the flare, so due to the low altitude, the pilot leveled the helicopter to prevent a tail strike. The helicopter touched down on its skids with "substantial" ground speed and veered slightly right. The pilot applied full left cyclic and pedal input, but the helicopter continued to veer right. The helicopter exited the runway and rolled over on its left side. The fuselage and main rotor blades were substantially damaged. The pilot reported that there were no preaccident mechanical failures or malfunctions with the helicopter that would have precluded normal operation.
The flight instructor reported that the 180º right turn aligned the helicopter with the runway centerline but at a lower altitude than was desirable because it prevented the pilot from conducting a normal flare "as the tail would have struck the runway." He added that, a normal flare before touchdown in a full-down autorotation would result in a 30º nose-up attitude, but the pilot was only able to achieve about a 10º nose-up attitude "for fear of damaging the tail."
Probable cause
The pilot's improper landing flare during a turning, full-down autorotation, which resulted in a lower-than-normal rotor rpm, a faster-than-normal ground run speed, and the subsequent loss of directional control, a runway excursion, and a roll-over. Contributing to the accident was the flight instructor's delayed remedial action.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA226
- Event ID
- 20190426X01007
- Case number
- GAA19CA226
- 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: 1995d48289703644a07433ca4a242c01e2580960cb3160a694506dde91959ffc; retrieved 2026-09-16T08:48:56.899Z.