Jayhawk Eurocopter EC 130 B4 accident
Eurocopter EC 130 B4 · Accident while maneuvering
From Aspen-Pitkin County Airport (Sardy Field) (ASE) to Somerset, CO
Event
- NTSB case
- CEN15CA312
- 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
- Charter & commuter
- 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
Eurocopter EC 130 B4
- Aircraft type
- Eurocopter EC-130
- 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
- N974BR
- Operator
- Jayhawk
- Onboard fatalities
- Unknown
- Route
- From Aspen-Pitkin County Airport (Sardy Field) (ASE), Aspen, COTo Somerset, CO
- Aircraft age
- About 6 years (built 2009)
- 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 135: Air Taxi & Commuter
- 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
- Miscellaneous/other
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot had flown multiple trips into and out of the ranch prior to the accident. He also had seen wires in the area and had a discussion with local fishing guides regarding the location of wires in the area. As the pilot was preparing to depart the ranch with the last load of passengers he was approached by a guide who wanted to video the helicopter for their website. The pilot agreed and after lifting off, made a pass near the ranch for the video. The pilot stated he was flying toward the mountains when he heard a "small ting" and he knew the helicopter contacted a wire. He made an uneventful off airport landing in a nearby clearing. Although the pilot stated he never saw the wire it was later determined the helicopter contacted was a small copper static wire. A postaccident inspection of the helicopter revealed two of the three main rotor blades were beyond repair, at least two of the Fenestron blades were beyond repair, and the entire Fenestron stator blade assembly needed to be replaced.
Probable cause
The pilot's decision to fly at a low altitude when he was aware that there were wires in the area which resulted in the helicopter contacting a wire.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN15CA312
- Event ID
- 20150722X52014
- Case number
- CEN15CA312
- 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: 403f89bfc7bb9ea39ee3cfa25fd1f52836faefa9dc120a1bfb4ce5d0f2ed234e; retrieved 2026-09-16T02:33:38.654Z.