GAA16LA182 · Hughes 369 A
Hughes 369 A · Accident: flight control system malfunction/failure during takeoff
From Staggs Heliport (TE93) to Staggs Heliport (TE93)
Event
- NTSB case
- GAA16LA182
- 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 369 A
- 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
- N298SD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Staggs Heliport (TE93), Weatherford, TXTo Staggs Heliport (TE93), Weatherford, TX
- Aircraft age
- About 48 years (built 1968)
- 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
- Takeoff
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot/mechanic stated that, while performing maintenance on the helicopter, he locked the left side antitorque (tail rotor) pedals to keep them out of the way; however, he forgot to unlock them after completing the maintenance. The pilot then conducted a post-maintenance hover check, and, upon increasing collective, the helicopter entered a spin, traveled about 40 feet, and collided with a building and trees.
The pilot stated that there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation, and that the accident was the result of his failure to remove the antitorque pedal lock before flight.
Probable cause
The pilot/mechanic's inadequate postmaintenance and preflight inspections, which resulted in his failure to remove the antitorque pedal lock and a subsequent loss of control during hover operations.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16LA182
- Event ID
- 20160411X25201
- Case number
- GAA16LA182
- 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: a0431f1812ae98cf67b62029adec9288d41a825a49fee84fee1282f3b51038c9; retrieved 2026-09-16T03:16:57.865Z.