FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA07LA022 · McDonnell Douglas 369E

22 Nov 2006 · Lyons, OR, United States

McDonnell Douglas 369E · Accident: airframe, component or system failure while maneuvering

From Lyons, OR to Lyons, OR

Report a problem

Event

NTSB case
SEA07LA022
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
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

McDonnell Douglas 369E

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
N1611W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lyons, ORTo Lyons, OR
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
Maneuvering · hover out of ground effect
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
Airframe, component or system failure
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

  • Miscellaneous rotorcraft › Failure
  • Rotorcraft flight control › Cut/severed

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 said that he was moving Christmas trees during harvesting operations. He said that one of the two slings holding the load failed, and as the trees fell to the ground, the second sling "popped" into his rotor head. The pilot said that both the cyclic and collective were severed, and he lost all flight control. An autorotation was not possible and the helicopter fell to the ground and came to rest on its right side.

Probable cause

A severing of the helicopter's cyclic and collective rods by one of the load lifting slings following the failure of the other sling. A contributing factor was the hard landing due to the fact that an autorotation was not possible.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA07LA022
Event ID
20061231X01857
Case number
SEA07LA022
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: d13336edd66be24d8b7721bef76f54c4445452313ad42146c015ae3dcafdb80e; retrieved 2026-09-22T04:12:58.866Z.