SEA97FA120 · Piper PA-32-301T
Piper PA-32-301T · Accident: airframe, component or system failure en route
From Buchanan Field (CCR) to Roberts Field (RDM)
Event
- NTSB case
- SEA97FA120
- 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
- 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
- Instrument Meteorological Cond
Piper PA-32-301T
- Aircraft type
- Piper PA-32
- 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
- N83211
- Operator
- Suzanne A Isaacs · private individual
- Onboard fatalities
- Unknown
- Route
- From Buchanan Field (CCR), Concord, CATo Roberts Field (RDM), Redmond, 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 · descent
- 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
- Airframe › Overload
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The last radio communications from the pilot indicated that they were in instrument meteorological conditions and experiencing updrafts and picking up ice on the structure. Widely scattered thunderstorms and rain were reported in the area. Light to occasional moderate rime and mixed icing in the precipitation was reported from the freezing level to 12,000 feet. Moderate turbulence was reported for the entire state. Witnesses on the ground heard the sound of the engine but could not see the airplane. The witnesses reported that a 'pretty nasty looking cloud' with the sounds of thunder was in the area when they heard a sound similar to a sonic boom. After this sound, the aircraft's engine was no longer heard. Evidence at the accident site indicated that the aircraft broke-up in flight. The left wing separated at the root, the right wing separated about 109 inches from the root. Both the horizontal stabilizers and the vertical stabilizer separated from the empennage. Metallurgical examination of the fractured components were typical of overstress separations. Both the wings and the horizontal stabilator failed in a downward loading condition.
Probable cause
Overload of the airframe structure. Thunderstorms and turbulence were factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA97FA120
- Event ID
- 20001208X08013
- Case number
- SEA97FA120
- 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: 12eefcca293229504f18ffd89240b1976857042ef129efb542731eef8a0f820b; retrieved 2026-09-20T22:57:14.777Z.