WPR18FA232 · Hughes 369 FF
Hughes 369 FF · Accident: loss of visual reference while maneuvering
From Georgetown Executive Airport at Johnny Gantt Field (GTU) to Draughon Miller Central Texas Regional Airport (TPL)
Event
- NTSB case
- WPR18FA232
- 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
- 2 · 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 FF
- 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
- N530FU
- Operator
- Brunner Aerospace
- Onboard fatalities
- Unknown
- Route
- From Georgetown Executive Airport at Johnny Gantt Field (GTU), Georgetown, TXTo Draughon Miller Central Texas Regional Airport (TPL), Temple, TX
- Aircraft age
- About 34 years (built 1984)
- 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
- Maneuvering · low-altitude flying
- 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 visual reference
- 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
- Wire
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Environmental issues › Physical environment
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor was providing emergency procedure refresher training, as part of a contract between the US Army and a private contractor, to special operations pilots with the Jordanian Air Force. The accident was intended to be an introductory orientation flight for the pilot receiving instruction of the airports areas where the training would be occurring.
Radar data indicated that the helicopter traveled east from the departure airport and climbed to an altitude of about 500 ft above ground level (agl). Afterward, the helicopter began to descend, and flew at altitudes that varied between 0 and 120 ft agl at a groundspeed of about 90 knots. A witness saw the helicopter rapidly approaching his location and reported that the helicopter was flying low in a nose-down attitude.
A short time later, the helicopter struck and severed a steel wire power distribution line, and continued to fly until the helicopter impacted the ground about 950 ft beyond the impact point with the line. Most of the severed power line was continuous to the main wreckage location, having likely trailed or been attached to the helicopter after impact. According to the radar data, and impact trajectory, the 36-ft-tall power line support poles would have been hidden from the pilots' view by a stand of trees as the helicopter approached the area.
Postaccident examination revealed no anomalies with the airframe or engine that would have precluded normal operation of the helicopter. The wreckage location, which was well beyond the impact point with the power line, was consistent with the helicopter operating at a high forward speed and likely a high engine power.
The flight instructor was highly experienced in the accident helicopter make and model and had an extensive military career flying attack missions in helicopters. These missions included navigation and aerial gunnery, which would have required low-level flight close to terrain. Likewise, the pilot receiving instruction flew similar attack missions in helicopters with the Jordanian military. Therefore, it is likely that the flight instructor decided to intentionally deviate from the training syllabus and perform, or allow the pilot receiving instruction to perform, a high-speed, nap-of-the-earth flight for personal reasons, possibly to simulate their working environment, make the flight more interesting or engaging, push limits, or impress each other.
The flight instructor had used the sedating antihistamine cetirizine at some time before the accident flight. Although the levels of the drug were well below the therapeutic range, it is not possible to determine if he could have been impaired by the sedating effects during the accident sequence.
Probable cause
The failure of both pilots to see and avoid a power line while maneuvering at low altitude. Contributing to the accident was the flight instructor's decision to not follow the training syllabus and allow the low-level high-speed flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR18FA232
- Event ID
- 20180821X62945
- Case number
- WPR18FA232
- 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: 184a6bf6f7807e674002458b1c2e0da47f24e7f296a8d8ac28bf1bce6f07bf99; retrieved 2026-09-15T06:46:36.049Z.