WPR11FA090 · Beech S35
Beech S35 · Accident: loss of control in flight on approach
From Charles M. Schulz Sonoma County Airport (STS) to Rogers Field (O05)
Event
- NTSB case
- WPR11FA090
- 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
- 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
- N5866S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Charles M. Schulz Sonoma County Airport (STS), Santa Rosa, CATo Rogers Field (O05), Chester, CA
- 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
- Approach · VFR pattern crosswind
- Defining eventThe 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The 76-year-old private pilot departed during the hours of darkness on a return trip to his home airport. Radar data revealed a flight track consistent with the pilot hand flying the airplane without the assistance of an autopilot at altitudes appropriate for the terrain elevation. No radar data was available for the approach segments and accident sequence of the flight. Based on witness reports, the airplane appeared to perform a normal crosswind approach over a town and toward the airport runway. During the airport approach, the pilot made a normal radio call and did not appear to be in distress. As the airplane rounded the turn from crosswind to downwind, it continued in a shallow, high-speed descent, directly into the frozen surface of a lake adjacent to the runway.
The debris field was on a heading which approximated the downwind segment of the landing runway. The debris field length was consistent with a high-speed, right-wing-low, gradual descent into the ground. The landing gear and flaps were not in the landing configuration, and the speed brakes were not deployed. All sections of the airplane were located at the accident site, and no anomalies were noted with the airframe or engine that would have precluded normal operation. The damage to the propeller was consistent with the engine producing power at the time of impact.
The airport was located on the outskirts of a town, adjacent to a lake and a sparsely populated national park. The moon, which exhibited a 6 percent visible disk, would have provided limited illumination and would have been located low on the horizon and behind the airplane during the crosswind and downwind turns. The pilot's forward view would also have been dominated by a dark void as the airplane passed over the town, and began the landing approach. The pilot did not possess an instrument rating, which, coupled with the lighting conditions, could have made him vulnerable to spatial disorientation. Additionally, the airplane's impact trajectory was consistent with him encountering this phenomena.
The pilot had experienced a mild heart attack 6 years prior to the accident, with placement of stents in two coronary arteries, and a diagnosis of diabetes. He had denied any medical history in applications for FAA medical certificates. It was not possible to conclusively determine what role, if any, the pilot’s unreported medical conditions played in the accident.
Probable cause
The pilot's loss of control while maneuvering to land, most likely due to spatial disorientation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11FA090
- Event ID
- 20110106X30933
- Case number
- WPR11FA090
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2011-01-07.
- API snapshot SHA-256: e336398ab25f3df672a4da4d1d61c867637023ebf5129d5d1b1c6f13cacbdbdc; retrieved 2026-09-13T21:12:23.027Z.