SEA06GA158 · Eurocopter AS-350-B3
Evergreen Helicopters Eurocopter AS-350-B3 · Accident: in flight collision with object while maneuvering
From Williams Peak, ID (no airport) to Krassel US Forest Service Airport (24K)
Event
- NTSB case
- SEA06GA158
- 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
- 4 · 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
- Government
- 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 AS-350-B3
- Aircraft type
- Eurocopter AS-350
- 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
- N355EV
- Operator
- Evergreen Helicopters
- Onboard fatalities
- Unknown
- Route
- From Williams Peak, ID (no airport)To Krassel US Forest Service Airport (24K), Krassel USFS, ID
- 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
- Public Aircraft
- 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
- First occurrenceThe 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
- In flight collision with object
- 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
- Tree(s)
- 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
- Pilot in command › Altitude/clearance, not maintained
- Pilot in command › Low altitude flight/maneuver, intentional
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The helicopter collided with a tree as it flew over a mountain ridgeline. The helicopter was under contract to the U.S. Forest Service and was assigned to Krassel Helibase (24K), Idaho. The pilot was requested to fly a relief Fire Lookout to a lookout tower on Williams Peak, which was 4 nautical miles (nm) and a 2,844 feet elevation gain away. There were several forest fires in the area and visibility in the lower valley was approximately 1 nm. The relief Fire Lookout, who was dropped off, said that as the helicopter flew up the ridge, visibility got much better. He said that there were two forest service personnel on board, to assist in off-loading and on-loading equipment, supplies, and refuse from the two open-top external cargo baskets that were secured to the helicopter's skid gear. Cargo was secured in the cargo baskets by multiple bungee cords. The return flight would have been flown directly into the late afternoon sun. There were no witnesses to the accident. Thirteen cubitainers (5 gallon plastic containers for potable water), two large plastic refuse bags, yellow crepe paper and several chips of green helicopter paint were found near a freshly downed and up rooted snag (a dead, defoliated conifer) located on the ridgetop. The snag was estimated to have been 90 feet tall. Further down the mountain side was a tail rotor paddle which had separated at its cuff. The burned out wreckage of the helicopter was found on a forest service road, approximately 2,000 feet down the mountain and 1,230 foot elevation loss from the initial downed snag. Postaccident examination of the engine revealed that the power turbine's blades were sheared from their disc, which indicated an over speed event. This would occur with a main rotor blade strike/sudden-stoppage event, and the subsequent compromised engine to main rotor power train. Additionally, 11 of the containers that had been in one cargo basket had 3 to 9 inch slashes in them from the tail rotor. Interviews were conducted by U.S. Forest Service personnel with four Helitack crew members who were assigned to the helicopter. They said the pilot did like to do "showy" flying at times, but would always ask the passengers if they were comfortable. He would "buzz" a ridge every now and then, and perform a maneuver he called the "sleigh ride." One of the Helitack crew members said that a "sleigh ride was where you top a ridge then drop the collective, drop the nose a bit....it was a common maneuver for him." No preimpact engine or airframe anomalies, which might have affected the helicopter’s performance, were identified.
Probable cause
The pilot's intentional low altitude flight and his failure to maintain an adequate altitude to clear the trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06GA158
- Event ID
- 20060824X01237
- Case number
- SEA06GA158
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 5853329e7f35d67933247ef36f2e8f3feefb4735b6a0800eb6cc4b43611dba95; retrieved 2026-09-18T14:34:16.511Z.