FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12FA193 · Cessna 560XL

27 Apr 2012 · Eugene, OR, United States

Pape Group Cessna 560XL · Accident: landing gear collapse

From Centennial Airport (APA) to Eugene Airport (EUG)

Report a problem

Event

NTSB case
WPR12FA193
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
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
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

Cessna 560XL

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
N101PG
Operator
Pape Group
Onboard fatalities
Unknown
Route
From Centennial Airport (APA), Denver, COTo Eugene Airport (EUG), Eugene, 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
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
Substantial

Cause areas

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot-in-command (PIC) reported that, during the visual approach to the airport, he and the second-in-command (SIC) lowered the landing gear and verified that all cockpit indications showed that the landing gear were in the down-and-locked position. The airplane touched down smoothly on the main landing gear (MLG) and then touched down on the nose landing gear (NLG). The PIC had his hand on the thrust reversers when he and the SIC heard the landing gear unsafe horn; the left MLG then collapsed followed immediately by the collapse of the right MLG and the NLG. The airplane slid on its belly for about 1,500 ft before it came to rest on the runway. Cockpit voice recorder data confirmed that the unsafe landing gear configuration warning did not occur before touchdown as reported by the PIC.

Postaccident examination revealed that, although the landing gear handle was in the down-and-locked position, all of the landing gear were fully retracted and engaged in their respective uplocks. Extensive testing of the airplane's hydraulic and electrical systems did not reveal any malfunctions that would have resulted in an uncommanded gear retraction. Some small, fine particulate matter was observed within the hydraulic manifold assembly; however, testing was unable to determine if these particles contributed to the uncommanded landing gear retraction.

Probable cause

An uncommanded landing gear retraction after touchdown for reasons that could not be determined because postaccident examination did not reveal any mechanical malfunctions or failures that would have precluded normal operation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12FA193
Event ID
20120502X01340
Case number
WPR12FA193
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: investigation status, coordinates. 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: feb03e6939a6550c4b38212cf86559f1df059f603c0c2ccbe8d366de4954fa08; retrieved 2026-09-15T17:57:39.067Z.