FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA93LA064 · Robinson R22 BETA

7 Feb 1993 · Bend, OR, United States

Puget Sound Helicopter Robinson R22 BETA · Accident: loss of control in flight while maneuvering

From Sunriver Airport (S21) to Portland Troutdale Airport (TTD)

Report a problem

Event

NTSB case
SEA93LA064
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
0
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
Instrument Meteorological Cond

Robinson R22 BETA

Aircraft type
Robinson R22
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
N4085M
Onboard fatalities
Unknown
Route
From Sunriver Airport (S21), SUN RIVER, ORTo Portland Troutdale Airport (TTD), Troutdale, 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 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 · turn to reverse direction
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
Loss of control in flight
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 › Rotor RPM, not maintained

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

NTSB narrative

THE PILOT REPORTED THAT AT TAKEOFF, THE CEILING WAS 350 FEET AGL AND VISIBILITY WAS TWO MILES. THE FLIGHT TOOK OFF AND HEADED NORTH AT AN ALTITUDE OF 250 FEET AGL, FOLLOWING A HIGHWAY. APPROXIMATELY SEVEN MILES INTO THE FLIGHT, THE CEILING AND VISIBILITY DETERIORATED AND THE PILOT INITIATED A MEDIUM BANK TURN TO THE LEFT. DURING THE TURN, THE AIRSPEED DECLINED AND THE LOW ROTOR RPM HORN SOUNDED. THE PILOT LOWERED THE NOSE AND INCREASED COLLECTIVE. DUE TO THE CLOSENESS OF THE TREES, THE PILOT ESTABLISHED THE BEST RATE OF DESCENT AND 'MILKED' THE RPM FOR A LANDING ON THE HIGHWAY. THE PILOT WAS UNABLE TO EXECUTE THE PROPER POWER OFF LANDING PROCEDURE AND THE HELICOPTER LANDED HARD. THE SKIDS COLLAPSED AND THE HELICOPTER ROLLED ONTO ITS LEFT SIDE.

Probable cause

ROTOR RPM WAS NOT MAINTAINED. FACTORS TO THE ACCIDENT WERE: LOW CEILING AND POOR INFLIGHT PLANNING.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA93LA064
Event ID
20001211X11890
Case number
SEA93LA064
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: 1b3a42f71ad77ff9685e8d8124366253e0abd7603886b7fcb7fd83840a937c34; retrieved 2026-09-21T23:02:25.569Z.