FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA90LA081 · Hughes 369D

21 May 1990 · Kelso, WA, United States

Hughes 369D · Accident: in flight collision with object during initial climb

Report a problem

Event

NTSB case
SEA90LA081
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
1 · all aircraft and ground
Ground fatalities
1
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 369D

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
N8306F
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo 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 133: Rotorcraft Ext. Load
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
Initial climb
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
None

Cause areas

  • Pilot in command › Clearance, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PILOT TOOK OFF WITH AN EXTERNAL LONGLINE LOAD (BUNDLE OF CEDAR BLOCKS). THE BUNDLE STRUCK TREE BRANCHES IN THE THICK FOREST CANOPY OVER THE PICKUP SITE & CAME APART. A FALLING BLOCK OF WOOD FROM THE BUNDLE STRUCK & FATALLY INJURED THE GROUND HOOK-UP CREWMAN. THE COMPANY OPERATING MANUAL REQUIRED THAT GROUND PERSONNEL BE CLEAR OF THE AREA DURING THE LIFT-OFF & THAT THE PILOT MAKE A VERTICAL TAKEOFF TO AN ALTITUDE THAT WOULD CLEAR THE LOAD OF OBSTRUCTIONS.

Probable cause

FAILURE OF THE PILOT TO KEEP THE EXTERNAL LOAD CLEAR OF OBSTACLES (TREES). FACTORS RELATED TO THE ACCIDENT WERE: FAILURE OF THE PILOT AND GROUND CREWMAN TO FOLLOW SAFETY PROCEDURES, AND THE PROXIMITY OF THE TREES.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA90LA081
Event ID
20001212X23286
Case number
SEA90LA081
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, damage. 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: e666d0323a43d96da80c0d11d762e3a117393d88da7ded3e7fc26308c3dab06c; retrieved 2026-09-21T02:40:45.208Z.