FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11LA172 · Beech G35

19 Mar 2011 · Whidbey Island, WA, United States

Beech G35 · Accident: aircraft structural failure while maneuvering

From Seattle Paine Field International Airport (PAE) to Seattle Paine Field International Airport (PAE)

Report a problem

Event

NTSB case
WPR11LA172
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
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 G35

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
N4211D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Seattle Paine Field International Airport (PAE), Everett, WATo Seattle Paine Field International Airport (PAE), Everett, WA
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
Maneuvering
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
Aircraft structural failure
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

  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

The owner/pilot was cruising on a personal flight in visual conditions and was engaged in correlating the indications of two very high frequency omni-range (VOR) cockpit navigation displays. The pilot also had a handheld global positioning system (GPS) unit mounted in the cockpit. During the VOR correlation effort, the pilot noticed on the GPS that he was about to intrude into restricted airspace. (Although this particular airspace is only restricted at certain times, the GPS always depicts the boundaries, regardless of the airspace restriction status.) He initiated a turn to avoid the restricted airspace and monitored the GPS display to ensure that he would clear the restricted area. When he returned his attention to the airplane, he noticed that the bank angle was about 75 degrees, the pitch attitude was about 20 degrees airplane nose down, and the airspeed was about 190 mph, which was in the yellow (caution) range of the airspeed indicator scale. The pilot leveled the wings and initiated a pull-up, during which he heard three or four "thumps" in rapid succession.

After recovery to level flight, the airplane seemed normal, but the pilot's concern about the thumps prompted him to return to his home airport where he landed uneventfully. The pilot estimated that he loaded the airplane to about 2g during the pullout, while a cockpit mounted g-meter registered a maximum loading of about 2.5g. Postflight examination of the airplane revealed that the aft fuselage side skins were wrinkled and that the aft fuselage lower skin was torn. Detailed evaluation of the ruddervator system revealed some minor discrepancies in control surface travel ranges. Damage patterns were consistent with in-flight overload and were not consistent with flutter. Review of airplane certification requirements and the in-flight events indicated that the airplane was in the region of its flight envelope where flight control inputs could result in structural damage. The control surface travel discrepancies did not contribute to the ability of the pilot to induce the observed structural damage.

Because the restricted airspace is not continuously active, notification of its active status is provided via a Notice to Airmen (NOTAM), which is issued 2 hours in advance of the restriction. The airspace status can also be determined on a real-time basis via radio communications with the controlling facility. The pilot had not checked the NOTAMs and was not in communication with the controlling facility, and he was therefore unaware of the airspace status at the time of his near-penetration of the airspace. Because he was unaware of the status of the airspace, he took evasive action to avoid it, although such action was unnecessary because the airspace was not restricted at the time of the flight. Adequate preflight planning would have allowed the pilot to determine the status of the restricted airspace and would have obviated the need for the avoidance maneuver, which ultimately resulted in structural damage to the airplane. In addition, when it became apparent to the pilot that he was about to penetrate the airspace, he prioritized avoidance of the airspace above retaining control of the airplane, which was a reversal of the "aviate, navigate" priority hierarchy necessary for safe operation of any aircraft.

Probable cause

The pilot's failure to prioritize flying over navigation due to his diverted attention, which allowed the airplane to near a restricted area, which, in turn, led the pilot to enter a rapid avoidance maneuver and subsequently lose airplane control. Contributing to the accident was the pilot's failure to adequately prepare for the flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11LA172
Event ID
20110319X34215
Case number
WPR11LA172
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. 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: 7aa2cc57ab5174c830023e8fef5fd9c4d05135195d68a6d424cd8a299201c60c; retrieved 2026-09-15T15:55:52.590Z.