WPR13CA057 · Hughes 369D
P J Helicopters Hughes 369D · Accident: settling with power/vortex ring state while maneuvering
From Sheridan, OR to Sheridan, OR
Event
- NTSB case
- WPR13CA057
- 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
- N163PJ
- Operator
- P J Helicopters
- Onboard fatalities
- Unknown
- Route
- From Sheridan, ORTo Sheridan, OR
- 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
- 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
- Settling with power/vortex ring state
- 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 from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
During a Christmas tree harvest, the pilot was repositioning trees from the harvest field onto a truck bed using an 18-foot tag line. He had completed at least five loads before the accident load. During the accident load, the pilot had just released the load onto the truck when he thought the helicopter was encountering a settling with power condition. The pilot maneuvered the helicopter to land on the road in front of the truck. The pilot thought he was clear of the truck; however, the main rotor blades hit the truck just above the cab. The helicopter impacted the ground and the main rotor blades struck and separated the tailboom from the fuselage. The pilot reported that there were no preimpact mechanical malfunctions or failures with the helicopter or engine that would have precluded normal operations.
Probable cause
The pilot’s failure to prevent the helicopter from entering a vortex ring state (settling with power) condition during an external load operation, which resulted in the helicopter’s main rotor blades impacting the truck.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13CA057
- Event ID
- 20121127X10137
- Case number
- WPR13CA057
- 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: d8b07d50589c6674b08d8b2a990eb42704cc3b3d77706d8fa2c2097473d605d0; retrieved 2026-09-15T20:29:09.073Z.