FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR22FA087 · Beech K35

29 Jan 2022 · Salem, OR, United States

Beech K35 · Accident: abrupt maneuver during landing

Report a problem

Event

NTSB case
WPR22FA087
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 K35

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
N9530R
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 63 years (built 1959)
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
Landing
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
Abrupt maneuver
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

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

NTSB narrative

The pilot of the accident airplane departed the runway, stating that he was planning to remain in the traffic pattern. The pilot was then cleared to land; on the final approach, after crossing the runway threshold and just before the airplane touched down the airplane pitched up, ascended about 50 ft, and subsequently rolled left before entering a near-vertical descent and then impacting the ground. The airplane’s autopilot was repaired 1.5 flight hours before the accident flight, wherein the auto-pilot pitch servo was sent out for repair, reinstalled, and cable tensions were set. Subsequently, an operational check was conducted, which verified proper installation on the ground. The autopilot pitch servo capability is exhausted by a pitch hold setting, meaning that inadvertent activation would merely maintain the airplane’s present pitch profile at the time of activation. Postaccident examination of the pitch trim actuator revealed a 15° tab down position. The elevator tab limits are 4.5° tab up, to 23° tab down. While the pitch servo had been recently installed, it is not likely that the autopilot was engaged in the airport traffic pattern and specifically during landing. Postaccident examination of the airframe and engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. The cause of the abrupt nose-up pitch attitude during landing could not be determined. Pilot incapacitation was not a factor in this accident.

Probable cause

The airplane’s excessive nose-up pitch attitude during landing for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR22FA087
Event ID
20220130104567
Case number
WPR22FA087
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: investigation status, cause areas. 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: 4a723fb6ee7a827b230ab726fc325cc73066260ae0b978068c8bb4a6bd0fa95c; retrieved 2026-09-15T07:40:29.190Z.