Ameriflight Piper PA-31T-620 incident
Piper PA-31T-620 · Incident: airframe, component or system failure en route
From Portland International Airport (PDX) to Oakland San Francisco Bay Airport (OAK)
Event
- NTSB case
- LAX93IA029
- 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
- Incident
- 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-31T-620
- Aircraft type
- Piper PA-31
- 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
- N131AF
- Operator
- Ameriflight
- Onboard fatalities
- Unknown
- Route
- From Portland International Airport (PDX), Portland, ORTo Oakland San Francisco Bay Airport (OAK), Oakland, CA
- 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
- En route · cruise
- 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
- None
Cause areas
- Flt control syst, elevator control › Disconnected
- Flt control syst, elevator control › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING CRUISE FLIGHT AT FLIGHT LEVEL 230, THE AIRPLANE SUDDENLY PITCHED UP AND THE AUTOPILOT DISENGAGED. THE PILOT WAS UNABLE TO CONTROL THE AIRPLANE WITH THE CONTROL YOKE. USING POWER AND TRIM CONTROL, HE FINALLY REGAINED CONTROL OF THE AIRPLANE AND MADE AN EMERGENCY LANDING AT SACRAMENTO WITHOUT FURTHER INCIDENT. INVESTIGATION REVEALED THAT THE THREADED PORTION OF THE ROD END BEARING, P/N 49261-02, HAD SEPARATED AT THE POINT WHERE THE THREADS ARE INSERTED INTO THE AFT END OF THE ELEVATOR CONTROL TUBE ASSEMBLY, P/N 40847-07. THE ELEVATOR CONTROL TUBE CONNECTS TO THE ELEVATOR PITCH HORN. METALLURGICAL EXAMINATION SHOWED THAT THE SEPARATION WAS DUE TO A FATIGUE FAILURE. THE AIRCRAFT HAD BEEN INSPECTED AT 37 HRS AND 134 HRS BEFORE THE INCIDENT IN ACCORDANCE WITH AN APPROVED AIRCRAFT INSPECTION PROGRAM. NEITHER INSPECTION SPECIFICALLY ADDRESSED AN INSPECTION OF THE ELEVATOR CONTROL TUBE ASSEMBLY.
Probable cause
FATIGUE FAILURE OF THE ELEVATOR CONTROL TUBE ROD END BEARING RESULTING IN A LOSS OF ELEVATOR CONTROL.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX93IA029
- Event ID
- 20001211X16054
- Case number
- LAX93IA029
- 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, damage. 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: 44d0639bf22b28ce53960f6d6064865245d5def1e90ddd9252c9dd6460592aa3; retrieved 2026-09-18T18:43:09.776Z.