FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Grand Aire Express Piper PA-601P accident

11 Sept 1990 · Monroe, MI, United States

Piper PA-601P · Accident: airframe, component or system failure during landing

From Chicago Rockford International Airport (RFD) to D92 · Monroe, MI

Report a problem

Event

NTSB case
CHI90LA261
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
Charter & commuter
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

Piper PA-601P

Aircraft type
Piper PA-601
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
N321GB
Onboard fatalities
Unknown
Route
From Chicago Rockford International Airport (RFD), Rockford, ILTo D92 · Monroe, MI
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 135: Air Taxi & Commuter
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 · landing roll
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

  • Landing gear, main gear strut scissors › Fatigue

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

NTSB narrative

THE PILOT FELT THE AIRPLANE PULL RIGHT AT TOUCHDOWN. COMBINED USE OF FLIGHT CONTROLS, LEFT BRAKE AND DIFFERENTIAL POWER REDUCED BUT DID NOT PREVENT A DRIFT OFF THE RUNWAY. A BROKEN TORQUE LINK ON THE RIGHT MAIN LANDING GEAR SCISSORS ASSEMBLY ALLOWED THE LOWER STRUT TO TURN OUT OF ALIGNMENT, SCRUBBING THE RIGHT MAIN TIRE SIDEWAYS THROUGHOUT THE LANDING ROLL. THERE HAVE BEEN 17 SIMILAR FAILURES SINCE 1985. THE MANUFACTURER HAS USED A REDESIGNED LINK IN NEW PRODUCTION SINCE 1982 WITHOUT FAILURE. SERVICE BULLETIN 746A, ISSUED 5/86, OFFERS A LINK REPLACEMENT.

Probable cause

A FATIGUE FRACTURE OF THE TORQUE LINK ON THE RIGHT LANDING GEAR STRUT SCISSOR ASSEMBLY.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI90LA261
Event ID
20001212X24224
Case number
CHI90LA261
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: bb2de94294676ed0e525c92df34e49bc3d8141c8ff034788be80a05d8df619c0; retrieved 2026-09-18T18:59:29.081Z.
  • The NTSB's operator name is blank for N321GB; the operator shown is the name the NTSB's other records give its FAA operator code, GXPA.