SEA01TA172 · Bell 205
U.S. Forest Service Bell 205 · Accident: in flight collision with object while maneuvering
From Troy Airport (57S) to MT
Event
- NTSB case
- SEA01TA172
- 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
- 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
Bell 205
- Aircraft type
- Bell 205
- 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
- N458CC
- Operator
- U.S. Forest Service
- Onboard fatalities
- Unknown
- Route
- From Troy Airport (57S), Troy, MTTo MT
- 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 · aerial application
- 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
- Substantial
Cause areas
- Pilot in command › Clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was returning from an external load long-line firefighting flight when he noticed a vertical vibration above 90 knots. After landing at Troy he noticed damage to the main rotor blades. Subsequently, he noticed that pine needles had been ingested by the helicopter's induction system. The pilot reported that he had no memory of hitting any objects during the operation. The weather was clear with 20 miles visibility, and the sky was partially obscured by smoke. There was no report of mechanical failure or malfunction with the helicopter.
Probable cause
The pilot-in-command's failure to maintain seperation/clearance from trees while maneuvering.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA01TA172
- Event ID
- 20010919X01966
- Case number
- SEA01TA172
- 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: 3276955a2e0743e7a4ae35f8b1c5cdfc1a4d13b961e216edefa56c8c962b4473; retrieved 2026-09-18T21:19:58.784Z.