Wheels Up Cessna 560XL ENCORE incident
Cessna 560XL ENCORE · Incident: landing gear collapse
From Tucson International Airport (TUS) to Mineta San Jose International Airport (SJC)
Event
- NTSB case
- WPR17IA189
- 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
- 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
- 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
Cessna 560XL ENCORE
- Aircraft type
- Cessna 560
- 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
- N503UP
- Operator
- Wheels Up
- Onboard fatalities
- Unknown
- Route
- From Tucson International Airport (TUS), Tucson, AZTo Mineta San Jose International Airport (SJC), San Jose, CA
- Aircraft age
- About 14 years (built 2003)
- 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
- 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
- Landing gear collapse
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and copilot reported that, during the landing roll, the airplane bounced and then veered right and that the pilot then corrected back to the runway centerline. The copilot added that the airplane’s right side seemed to “dip” as it continued to pull right, and the pilot added that the airplane’s right side was lower than its left side, so they assumed that the right main landing gear (MLG) had a flat tire. Subsequently, the pilot was able to taxi the airplane off the runway and park it on a taxiway, and the passengers disembarked without incident.
Examination of the airplane revealed that the aft portion of the right MLG trunnion was protruding through the top of the right wing and that the MLG strut and wheel were positioned out and aft in about a 45° angle from their original position. The right MLG trunnion aft pivot pin was not in the trunnion but remained in the trunnion mount in the aft wing spar; it was easily removed from the mount by hand. The retaining bolt used to keep the pivot pin in the trunnion was in place and secured with a nut and cotter pin.
Review of the airplane’s maintenance records revealed that the left and right MLG trunnions had been replaced with new trunnions and trunnion pivot pins 8 days before the incident. The mechanic who performed the work stated that, after installing the right MLG aft trunnion pivot pin, it must have shifted aft when he went to install the bolt through the pin. He stated that an “air-pocket” must have developed and pushed the pin back out. He added that the pin looked fully engaged and that he noted no faults during postmaintenance operational checks. Therefore, based on the evidence, it is likely that, after the mechanic installed the right MLG aft trunnion pivot pin, it backed out, which led to the retaining bolt not being installed in the hole in the pivot pin and resulted in the pin separating from the trunnion, the trunnion puncturing the right wing, and the right MLG collapsing.
Following the incident, the airplane manufacturer revised the trunnion pivot pin installation procedures in the Airplane Maintenance Manual. The revision included, in part, a step for maintenance personnel to visually check and ensure that the bolt is visible when looking through the pivot pin from the aft side and that, if it is not visible, to remove it, ensure that the pivot pin is fully installed in the trunnion assembly, and reinstall the bolt.
Probable cause
The mechanic’s incorrect installation of the right main landing gear (MLG) aft trunnion pivot pin, which resulted in the pin separating from the trunnion, the trunnion puncturing the right wing, and the right MLG collapsing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR17IA189
- Event ID
- 20170828X92641
- Case number
- WPR17IA189
- 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: local date, investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2017-08-29.
- API snapshot SHA-256: 32b4f9e88c77430fc1ee3e5fc112c61711cb5d2c3bb983a2250ce39f87655744; retrieved 2026-09-16T05:46:17.629Z.