GAA19CA463 · Hughes 269A
Hughes 269A · Accident: loss of tail rotor effectiveness while taxiing
From Clarksville–Montgomery County Regional Airport (CKV) to Springfield Robertson County Airport (M91)
Event
- NTSB case
- GAA19CA463
- 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
Hughes 269A
- Aircraft type
- Hughes 269
- 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
- N269RR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Clarksville–Montgomery County Regional Airport (CKV), Clarksville, TNTo Springfield Robertson County Airport (M91), Springfield, TN
- Aircraft age
- About 55 years (built 1964)
- 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
- Taxi · from runway
- 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 oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter pilot reported that, after landing and while hover taxiing and turning right toward the taxiway, the helicopter continued turning right and drifted past the taxiway. He applied full left pedal and then closed the throttle to perform an autorotation to decrease the speed of rotation to no avail. He added collective to reduce the descent rate, but the helicopter landed and slid into a drainage ditch, the main rotor blades impacted a berm near the taxiway, and the helicopter came to rest on its side.
The helicopter sustained substantial damage to the fuselage.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the helicopter that would have precluded normal operation.
The pilot reported that the wind was from 320° at 11 knots, gusting to 16 knots. The pilot landed the helicopter on runway 04 and was turning right.
Probable cause
The pilot’s failure to maintain helicopter control and a loss of tail rotor effectiveness while hover-taxiing and turning toward a taxiway in gusting crosswind conditions, which resulted in a dynamic rollover.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA463
- Event ID
- 20190725X72151
- Case number
- GAA19CA463
- 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. 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: edfbdf4681860597055be2335eecfc85c21a4ccc7ac5004b70e9a25b9e698137; retrieved 2026-09-16T09:33:04.867Z.