FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA04FA022 · Beech S35

25 Nov 2003 · Warren, OR, United States

Beech S35 · Accident: airframe, component or system failure en route

From Arlington Municipal Airport (AWO) to Rogue Valley International-Medford Airport (MFR)

Report a problem

Event

NTSB case
SEA04FA022
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
4 · 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

Beech S35

Aircraft type
Beechcraft 35
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
N10BX
Operator
Unknown
Onboard fatalities
Unknown
Route
From Arlington Municipal Airport (AWO), Arlington, WATo Rogue Valley International-Medford Airport (MFR), Medford, 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
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
Airframe, component or system failure
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 › Aircraft control, not maintained
  • Pilot in command › Design stress limits of aircraft, exceeded
  • Vacuum system › Failure, total

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

At 0347, the pilot received a standard weather briefing, which indicated instrument flight rules would prevail along the entire route of flight. The pilot was advised of an advisory for mountains to be obscured, an Airmet for occasional moderate turbulence below 15,000 feet msl, icing, occasional moderate rime or mixed in clouds and precipitation, with a freezing level to 16,000 feet msl. At 0540, radar contact was established with the flight. At 0635, while at 11,000 feet msl the pilot requested a higher altitude, and at 0639 the pilot reported that he was at 13,000 feet msl and clear of rime ice. At a time which could not be determined the pilot advised air traffic control that he had just lost his suction gage, and shortly thereafter radioed, "Mayday, Mayday, Mayday." At 0650:52, the airplane was on a south-southwesterly heading at 13,100 feet msl, and at 0650:59 it was at 12,900 feet msl on a southeasterly heading. From 0651:04 until 0651:28 the airplane was between 12,800 feet msl and 13,100 feet msl turning left from a south-southeasterly heading to an east-southeasterly heading. Between 0651:28 and 0651:52 the airplane descended on a northeasterly heading to an altitute of 10,700 feet. The airplane then made a right turn of approximately 60 degrees to a south-southeastly heading, and seven seconds later at 0651:59 was observed at 10,500 feet msl, indicating its descent had been arrested. Six seconds later, at 0652:05, the flight had descended to an altitude of 6,800 feet msl on the same heading. The last radar hit was at 0652:17 when the airplane was on a northwest heading at 6,400 feet msl. The engine and fuselage were located 1 mile northwest of Warren, Oregon, while both wings, the tail section and the left stabilizer were located approximately 1 mile northwest of the main wreckage. Separation signatures were consistent with the left stabilizer separating in an upward and aft direction, while both wings had separated in an upward and positive direction. Examination of the vacuum pump and its history indicates that it is probable that the pump failed due to vane failure as a result of highly worn vanes being subjected to impact bending loads from the uneven interior surface of the housing, with a possible contribution from contaminating material between the vanes and the housing.

Probable cause

The vacuum pump failure and the pilot's failure to maintain control of the airplane. Factors contributing to the accident included the instrument meteorological weather conditions and the pilot's improper recovery from the descent.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA04FA022
Event ID
20031205X02006
Case number
SEA04FA022
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, coordinates. 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: dd116b7ac91ce165c39d3982147b3a6cd3cf3bf2a541c56bf8ad5b72014ace20; retrieved 2026-09-20T18:45:48.833Z.