FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA02FA085 · Robinson R-22 Mariner

23 May 2002 · Merlin, OR, United States Possible conflict

Robinson R-22 Mariner · Accident: in flight collision with object en route

From Grants Pass, OR to an unrecorded destination

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

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

Robinson R-22 Mariner

Aircraft type
Robinson R-22
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
N2322Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Grants Pass, ORTo 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
En route · cruise
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
Wire, static
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Witnesses reported observing the helicopter traveling over the river at an altitude of about 50-100 feet above the water when it collided with an unmarked telephone line support cable. One of the witnesses reported that the engine rpm did not change until the helicopter collided with the cable. After striking the cable, the engine rpm slowed, but did not stop. The helicopter subsequently collided with the ground along the rivers edge and came to rest partially submerged along the bank. The width of the river at the accident site was approximately 75 yards wide. About 300 feet upstream of the main wreckage, two cables running perpendicular to the river were located. One of the two cables was broken and in the water. The other cable was intact, but not taut, and displayed a considerable droop. One end of the 1/8 in diameter cables was attached to a power pole near a restaurant. The other end traveled to the opposite side of the river and over upsloping terrain.

Probable cause

Clearance from a cable running perpendicular to a river was not maintained during low level cruise flight. A cable was a factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA02FA085
Event ID
20020529X00761
Case number
SEA02FA085
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. 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: 853cace7913142658d3d4ea19ac7acabbb938cba02d1950c3965d30d41502d19; retrieved 2026-09-20T20:00:59.382Z.