FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24LA091 · Piper PA-24

16 Jan 2024 · Hugo, OK, United States

Piper PA-24 · Accident: system/component malfunction/failure (non-power) during landing

From Waynesboro Municipal Airport (2R0) to an unrecorded destination

Report a problem

Event

NTSB case
CEN24LA091
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 PA-24

Aircraft type
Piper PA-24
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
N7059P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Waynesboro Municipal Airport (2R0), Waynesboro, MSTo not recorded
Aircraft age
About 64 years (built 1960)
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
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
System/component malfunction/failure (non-power)
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

  • Aircraft › Aircraft systems
  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision

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 reported that after takeoff, he retracted the landing gear but did not receive an “Up” indication. He then lowered the landing gear and noted a “Down” indication but did not receive an “Up” indication upon subsequent retraction of the landing gear a second time. The pilot elected to continue the flight with the landing gear not fully retracted. As the airplane approached its destination, the pilot attempted to lower the landing gear. The circuit breaker tripped and the landing gear motor stopped. The pilot attempted to reset the circuit breaker and cycled the landing gear several times, but the breaker continued to trip and he did not receive either gear “Up” or “Down” indications. The pilot performed a flyby of the airport, and ground observers signaled to him that the landing gear was not extended. He attempted the emergency landing gear extension procedure, but the gear extension lever would not move. The pilot noted that he circled the airport for about 40 minutes while he attempting to diagnose the landing gear issues. He ultimately decided to land with the landing gear not fully extended, and he continued to perform flybys to evaluate the terrain adjacent to the runway for landing. After determining the location where he would perform the landing, the pilot conducted prelanding checks, which included selecting the fullest fuel tank based on the fuel gauge readings. While maneuvering the airplane to land, the airplane’s engine stopped producing power, and the pilot executed a forced landing to a nearby field. The airplane struck small trees during the landing and then impacted the ground. The airplane sustained substantial damage to the fuselage and left wing. After the accident, the push-pull cables were disconnected at the main landing gear, and the gear motor released via the emergency extension release lever, the emergency extension handle still had significant resistance to movement consistent with binding of the main landing gear push pull cables. A postaccident examination also revealed that the left tank, which the pilot reported was the tank with more fuel indicated, was empty. The right tank (which had less fuel indicated) still had about 5 gallons of fuel remaining. After the accident, the fuel selector was found turned to the left (empty) tank. Based on the available evidence, one of the main landing gear push-pull cables became bound, which locked the landing gear in a partially retracted position. Which cable was bound and the reason that the cable was bound was not determined. The loss of engine power while troubleshooting the landing gear was the result of fuel starvation.

Probable cause

The binding of a main landing gear push-pull cable, which rendered the landing gear inoperative in a partially retracted position. Contributing to the accident was the pilot’s delay in executing a landing, which led to a total loss of engine power due to fuel starvation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24LA091
Event ID
20240117193676
Case number
CEN24LA091
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, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2024-01-17.
  • API snapshot SHA-256: b990d127ebb64a34e610dfa258a6d942cd59fc566a7553736fc234d623ff4212; retrieved 2026-09-16T18:26:45.919Z.