WPR14LA008 · McDonnell Douglas Heli Co 369 FF
Rogers Aviation McDonnell Douglas Heli Co 369 FF · Accident: loss of control in flight while maneuvering
From Paducah, TX to Paducah, TX
Event
- NTSB case
- WPR14LA008
- 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
- 1 · 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
McDonnell Douglas Heli Co 369 FF
- Aircraft type
- McDonnell Douglas 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
- N530KF
- Operator
- Rogers Aviation
- Onboard fatalities
- Unknown
- Route
- From Paducah, TXTo Paducah, TX
- Aircraft age
- About 19 years (built 1994)
- 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
- Maneuvering · hover
- 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 in flight
- 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
- Tower/antenna (incl guy wires)
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was maneuvering the helicopter into position near a 150-foot-tall power transmission line tower to prepare to attach a line to a rope and pull it through a traveler for power line construction. The wind had increased and was gusting, and the main rotor blades struck the tower. The helicopter spun around, and the tail rotor subsequently struck the tower. The tail rotor and tail rotor gearbox separated from the helicopter as it descended to the ground. A postcrash fire consumed the wreckage. The pilot did not report any mechanical malfunctions or failures with the helicopter that would have precluded normal operation. It is likely that the gusting wind conditions negatively affected the pilot's ability to maintain sufficient clearance from the tower while maneuvering into position.
Probable cause
The pilot’s failure to maintain clearance from a power transmission line tower while maneuvering to pick up a rope in gusting wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14LA008
- Event ID
- 20131007X44153
- Case number
- WPR14LA008
- 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: e58986f44f6ceb8481924f6261ad52ece887e1a8106dd7a63e1c8ecacead1df0; retrieved 2026-09-14T16:04:58.010Z.