FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18LA153 · Piper PA24 250

20 May 2018 · San Jose, CA, United States

Piper PA24 250 · Accident: landing gear collapse

From French Valley Airport (F70) to Mineta San Jose International Airport (KSJC)

Report a problem

Event

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

Piper PA24 250

Aircraft type
Piper PA24
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
N244TW
Onboard fatalities
Unknown
Route
From French Valley Airport (F70), Murrieta, CATo Mineta San Jose International Airport (KSJC), San Jose, CA
Aircraft age
About 60 years (built 1958)
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot had rented the airplane and conducted an uneventful personal flight earlier that day. He departed later that afternoon, destined for an airport a few hundred miles away. According to the pilot, after the airplane was established on the downwind leg, he extended the landing gear and observed that the landing gear position indicator light was illuminated green, which denoted that the landing gear was down and locked into position. He verified that indication on the base leg. The approach and touchdown were normal and uneventful, and the pilot then began to brake the airplane. When the airplane was traveling about 30 mph, the landing gear "suddenly collapsed." The airplane slid on its belly and came to a stop on the runway, which resulted in substantial damage to the fuselage.

During recovery of the airplane, the cockpit landing gear handle was found to be in the fully down position. Initial postaccident examination of the airplane revealed that the two main landing gear (MLG) could be fully extended via the normal cockpit landing gear handle but that the nose landing gear (NLG) did not fully extend, the extension motor did not shut off, and the green cockpit indicator light did not illuminate. Manual attempts to fully extend the NLG by pulling it forward were unsuccessful. Aft-directed light-to-moderate force applied to the NLG tire resulted in unlocking the two MLG, which allowed all three gear to be retracted via manually pushing on the NLG. These results demonstrated that the landing gear system was susceptible to uncommanded retraction when the system was not properly adjusted. The reason for the failure of the NLG to fully extend and lock after the accident could not be determined, and the investigation could not determine if this condition existed before the accident.

During subsequent examination, the NLG was mechanically isolated from the rest of the landing gear system. Subsequent landing gear travel tests in this configuration revealed that all three landing gear were able to be independently moved into their respective fully extended and locked positions. When the NLG was fully extended, it was more difficult to dislodge by aft pressure to the NLG tire than during the previous examination. The NLG travel change that resulted from mechanically isolating the NLG indicated that after the accident, there was some physical constraint that limited NLG travel and prevented downlock; however, the investigation was unable to determine the nature or cause of the NLG travel constraint. If the constraint was present before the accident, it is likely that the landing gear motor would not have shut off, the green cockpit light would not have illuminated, and the NLG would not have fully extended to the locked position when the pilot extended the landing gear. The reasons for the differences between the preaccident landing gear functionality reported by the pilot and the postaccident observations of landing gear functionality could not be determined.

Probable cause

A landing gear retraction during the landing rollout for reasons that could not be determined based on the available evidence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18LA153
Event ID
20180521X03556
Case number
WPR18LA153
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2018-05-21.
  • API snapshot SHA-256: 0aff2f196dbedd09577e75d49d22e0b33a603b75005be480cc2be295f24c81ed; retrieved 2026-09-16T07:12:36.539Z.