WPR20CA171 · Enstrom 480 Undesignat
Enstrom 480 Undesignat · Accident: low altitude operation/event while maneuvering
From Renolds Creek, ID to Jordan Valley, OR
Event
- NTSB case
- WPR20CA171
- 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
Enstrom 480 Undesignat
- Aircraft type
- Enstrom 480
- 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
- N130JS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Renolds Creek, IDTo Jordan Valley, OR
- Aircraft age
- About 22 years (built 1998)
- 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 137: Agricultural
- 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
- Low altitude operation/event
- 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
- Substantial
Cause areas
- Environmental issues › Physical environment
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that during the aerial application flight, while maneuvering at low altitude, he came upon some trees and increased altitude to climbed above the treetops. He did not see that there were power lines behind the trees and did not have enough time to avoid colliding with two of the lines. The pilot was unable to maintain control of the helicopter descended in a slow spin to ground impact. The helicopter sustained substantial damage to the fuselage and tail boom. The pilot reported that there were no preaccident mechanical failures or malfunctions with the helicopter that would have precluded normal operation.
Probable cause
The pilot's failure to maintain clearance from a power line while maneuvering during an aerial application flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20CA171
- Event ID
- 20200604X93452
- Case number
- WPR20CA171
- 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, cause areas. 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: 077b1d7b7c3b0eac2d6b7a0901a2b9466e123a296e498d28fb4769d6f237b639; retrieved 2026-09-16T11:46:37.830Z.