CEN11LA200 · Hughes 369D
Aerial Solutions Hughes 369D · Accident: flight control system malfunction/failure during landing
From Henryetta, OK to Henryetta, OK (no airport)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN11LA200
- 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 369D
- Aircraft type
- Hughes 369
- 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
- N112AS
- Operator
- Aerial Solutions
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Henryetta, OKTo Henryetta, OK (no airport)
- 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 133: Rotorcraft Ext. Load
- 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
- 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
- Flight control system malfunction/failure
- 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 propeller/rotor
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter was facing into the wind and hovering, with an external load, over an open field adjacent to the work area. The pilot made a 180-degree right pedal turn to enter the work area, approximately 120 feet above the ground. While trimming for the left quartering tailwind, he heard a loud "pop" and felt a "thump" in his seat. He was unable move the cyclic control to the left, and the helicopter started a right banking turn. The helicopter rolled sharply to the right and impacted the ground. A postaccident examination of the helicopter revealed no discrepancies. Flight control continuity was established from the cockpit to the flight controls. When the flight controls were manipulated, no obstructions or binding were noted.
Probable cause
Failure of the cyclic control system for reasons undetermined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11LA200
- Event ID
- 20110223X85903
- Case number
- CEN11LA200
- 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: c9c01531632dcc052f6e2b9a2f136d586154290cfd203332ddaba9da62857cf8; retrieved 2026-09-15T15:50:31.443Z.