SEA01FA032 · Hughes 369HS
Hughes 369HS · Accident: in flight collision with object while maneuvering
From LOWELL, ID to an unrecorded destination
Event
- NTSB case
- SEA01FA032
- 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
- 2 · 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 369HS
- 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
- N9186F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From LOWELL, IDTo not recorded
- 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 91: General Aviation
- 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
- 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
During an aerial survey flight, the aircraft was maneuvering to position for another run along a contour line in mountainous terrain. The flight elevation along the contour was reported about 150 feet above the ground level. The terrain was covered with deciduous and coniferous trees varying in height to about 50 feet. The surviving passenger reported that the helicopter was making a descending right turn when he suddenly felt a jolt. The passenger, seated directly behind the pilot on the left side, saw the pilots head jerk up, as the helicopter pitched straight up, then fall backwards and collided with the terrain in an inverted and nose low attitude at the base of a dead tree located on an outcropping along a ridge. This tree was taller than any of the surrounding trees and the top was broken off. This snag was also dark in coloration and void of branches. Plexiglas fragments and two rivets were found embedded in the section that broke off. Structural impact signatures noted that the helicopter came in contact with the tree on the right side lower fuselage section with rearward crushing damage through the anti-torque pedals and traveling aft to the cyclic control stick socket. Wood particles were embedded within the deformed fuselage structure and also to the forward section of the landing skids. The passenger reported that he did not detect any mechanical anomalies prior to the jolt, nor did the pilot indicate any problems over the headset prior to the collision. Post-crash inspection of the wreckage did not reveal evidence of a mechanical failure or malfunction.
Probable cause
While maneuvering, clearance from an object was not maintained. A tree was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA01FA032
- Event ID
- 20010104X00011
- Case number
- SEA01FA032
- 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: 7f18c28760ade87bcdf934ebf2de9864c8ed0f78b0eadc14f20bbe611fc1b7c5; retrieved 2026-09-20T20:43:05.617Z.