FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA83FYM07 · Maule M-5-235C

27 Jun 1983 · Silverton, OR, United States

Maule M-5-235C · Accident: total loss of engine power (non-mechanical) en route

From PRIVATE STRIP, OR to an unrecorded destination

Report a problem

Event

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

Maule M-5-235C

Aircraft type
Maule M-5
Category
Airplane
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
N6205M
Operator
Unknown
Onboard fatalities
Unknown
Route
From PRIVATE STRIP, 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
Total loss of engine power (non-mechanical)
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
Fuel contamination
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 › Aircraft preflight, inadequate
  • Pilot in command › Refueling, not corrected

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

NTSB narrative

THE ACFT LANDING GEAR COLLAPSED DURING A FORCED LANDING AFTER AN ENGINE FAILURE. THE ACFT HAD CLIMBED TO 1000 FT AGL AFTER TAKEOFF WHEN THE PILOT SWITCHED THE FUEL SELECTOR TO THE RIGHT FUEL TANK. IMMEDIATELY THE ENGINE QUIT AND SWITCHING BACK TO THE LEFT TANK DID NOT HELP. THE PILOT IN THE RIGHT SEAT TOOK OVER AND MADE A FORCED LANDING WHICH WAS HARD ENOUGH TO COLLAPSE THE LANDING GEAR. THE TWO FRONT SEAT OCCUPANTS RECEIVED SERIOUS BACK INJURIES FROM THE LANDING. POST ACCIDENT EXAMINATION OF THE ACFT SHOWED WATER IN THE CARBURETOR AND IN BOTH MAIN TANKS ALONG WITH RUST AND SEDIMENTTHE ACFT WAS REFUELED FROM A TANK ON THEIR FARM WHICH WAS ALSO CONTAMINATED WITH WATER, RUST AND SEDIMENT. THE FILTERS IN THE SYSTEM WOULD NOT PREVENT WATER FROM COMING OUT THE DISPENSING NOZZLE AND THE FILTERS WERE REPLACED ONLY ONCE A YEAR. THE FILTERS ARE NOT DESIGNED TO STOP WATER. THE FARM SUPPLY TANK HAD SAT OUTDOORS PRIOR TO BEING FILLED.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record SEA83FYM07
Event ID
20001214X43533
Case number
SEA83FYM07
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: a21d237a68cb8366052397a1169ac2db655a42f7c1626152ac07bfb816502405; retrieved 2026-09-21T17:54:13.961Z.