FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA92FA100 · Aerospatiale SA-341G

16 May 1992 · Yamhill, OR, United States

Teufel Nursery Aerospatiale SA-341G · Accident: in flight collision with terrain/water while maneuvering

From Portland Hillsboro Airport (HIO) to Flying M Airport (OR05)

Report a problem

Event

NTSB case
SEA92FA100
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
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
Visual Meteorological Cond

Aerospatiale SA-341G

Aircraft type
Aerospatiale SA-341
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
N9000E
Onboard fatalities
Unknown
Route
From Portland Hillsboro Airport (HIO), Hillsboro, ORTo Flying M Airport (OR05), FLYING M RANCH, 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
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 terrain/water
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Altitude, inadequate
  • Pilot in command › Maneuver, misjudged

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

NTSB narrative

WHILE GIVING RIDES TO EMPLOYEES AT A COMPANY PICNIC, THE PILOT LOADED FOUR PASSENGERS, FLEW TO HIS BASE, REFUELED, HAD A MINOR REPAIR COMPLETED, THEN DEPARTED ON THE RETURN FLIGHT. DURING THE RETURN FLIGHT, HE TOLD THE PASSENGERS THAT THE HELICOPTER WAS THE AIRCRAFT USED IN A TELEVISION SERIES, THEN DEMONSTRATED A SERIES OF MANEUVERS RELATED TO THOSE USED IN THE TELEVISION SHOW. DURING A MANEUVER, THE HELICOPTER COLLIDED WITH TREES AND THE SURFACE IN HILLY WOODED TERRAIN, AND BURNED AFTER IMPACT. ONE PASSENGER ASSISTED THE OTHER THREE PASSENGERS OUT OF THE AIRCRAFT. ONE PASSENGER DIED WHILE WAITING FOR RESCUE.

Probable cause

THE PILOT MISJUDGED A MANEUVER PERFORMED AT INADEQUATE ALTITUDE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA92FA100
Event ID
20001211X14716
Case number
SEA92FA100
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: 93671e1d4408a4cd7b8c21a106d022c7077c3f35417b82537bdbdefb7722bbbb; retrieved 2026-09-21T01:12:08.447Z.