FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA89LA130 · Cushing C2

9 Jul 1989 · John Day, OR, United States

Cushing C2 · Accident: airframe, component or system failure during initial climb

Report a problem

Event

NTSB case
SEA89LA130
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
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
Visual Meteorological Cond

Cushing C2

Aircraft type
Cushing C2
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
N129C
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
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
Initial climb
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
Substantial

Cause areas

  • Pilot in command › Maintenance, design change, improper
  • Pilot in command › Maintenance, inspection, not performed
  • Pilot in command › Operation with known deficiencies in equipment, improper
  • Wing, spar › Deteriorated
  • Wing, spar › Separation

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

NTSB narrative

PRIOR TO THE PLEASURE FLIGHT, THE PILOT REPORTED THAT WHEN ASSEMBLING THE LEFT WING, THE MOUNT BOLTS WOULD NOT ALIGN. THE PILOT DRILLED NEW HOLES ELONGATING THE ORIGINAL HOLES. THE WING WAS ASSEMBLED AND THE PILOT ATTEMPTED A TAKEOFF. JUST AFTER LIFT OFF, THE AIRPLANE BEGAN TO PORPOISE. SHORTLY THERE AFTER, THE LEFT WING FOLDED BACK AND UP. THE AIRPLANE ROLLED INVERTED TO THE LEFT AND SKIDDED DOWN THE RUNWAY. POST CRASH INSPECTION OF THE AIRPLANE REVEALED THAT THE WING BROKE AWAY AT THE SPAR. DRY ROT WAS NOTED THROUGHOUT THE ENTIRE STRUCTURE.

Probable cause

THE PILOT IMPROPERLY CHANGED THE DESIGN OF THE AIRPLANE BY ELONGATING HOLES AT THE WING ATTACHMENT. THE CHANGE WAS NOT INSPECTED BY A QUALIFIED INDIVIDUAL. AS A RESULT OF THE CHANGE, THE WING SEPARATED AT THE SPAR.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA89LA130
Event ID
20001213X28977
Case number
SEA89LA130
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: da6c5782245057a57cd21bb3c516a47cc1b285c54a664066062dd4184131edfb; retrieved 2026-09-21T15:53:02.305Z.