SEA82FYM10 · Weatherly 201C
Weatherly 201C · Accident: partial loss of engine power (mechanical failure) during takeoff
From WASCO, OR to WASCO, OR
Event
- NTSB case
- SEA82FYM10
- 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
Weatherly 201C
- Aircraft type
- Weatherly 201
- 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
- N9243W
- Operator
- R. A. Richelderfer · private individual
- Onboard fatalities
- Unknown
- Route
- From WASCO, ORTo WASCO, 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 137: Agricultural
- 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
- Takeoff
- 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
- Partial loss of engine power (mechanical failure)
- 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, transmission; Tree(s)
- 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
- Mixture control › Binding(mechanical)
- Mixture control › Separation
- Mixture control › Worn
- Other maintenance personnel › Maintenance, lubrication, inadequate
Approximate · Estimated position: the centre of Wasco, OR, the place the record names. Not the accident site.
NTSB narrative
THE PILOT REPORTED THAT DURING TAKEOFF, THE ENGINE DID NOT MAINTAIN FULL POWER. WHILE LANDING IN A RESIDENTIAL AREA, THE AIRCRAFT STRUCK A TELEPHONE WIRE AND THREE TREES. AN EXAMINATION OF THE ENGINE REVEALED NO OBVIOUS DEFECTS THAT WOULD CAUSE A LOSS OF POWER. THE THROTTLE QUADRANT, PN 40380, HAD SEVERAL DISCREPANCIES. THERE WAS NO EVIDENCE OF LUBRICATION OF THE QUADRANT, AND THE MOVEMENT OF THE LEVERS WAS STIFF. THE THROTTLE, PROPELLER CONTROL, AND MIXTURE LEVERS WERE VERY CLOSE TOGETHER, AND MOVEMENT OF ONE LEVER WOULD CAUSE RUBBING ON THE LEVER NEXT TO IT. THE QUADRANT HOUSING HAD EVIDENCE OF THE LEVERS RUBBING ON THE BOTTOM OF THE HOUSING. THE MIXTURE LEVER SHOWED EVIDENCE OF EXTENSIVE WEAR AND ELONGATION OF THE ATTACH HOLE. THE CABLE ATTACH HOLE WAS WORN COMPLETELY THROUGH THE END OF THE LEVER, AND THE MIXTURE CABLE WAS NOT ATTACHED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA82FYM10
- Event ID
- 20020917X02626
- Case number
- SEA82FYM10
- 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: 0e3cee3728b3d2dc04b0e6eacb7c01a309deeee00a0d9482cfff3c73ec3e09c5; retrieved 2026-09-24T03:38:20.007Z.