FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24LA122 · Piper PA32 260

23 Feb 2024 · Tulsa, OK, United States

Piper PA32 260 · Accident: hard landing

From Paradise Air Haven Airport (39OK) to an unrecorded destination

Report a problem

Event

NTSB case
CEN24LA122
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
Event fatalities
Unknown
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 PA32 260

Aircraft type
Piper PA32
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
N3645W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Paradise Air Haven Airport (39OK), Goldsby, OKTo not recorded
Aircraft age
About 58 years (built 1966)
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 · flare/touchdown
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
Hard landing
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 oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that, while landing, the flaps were inadvertently retracted from the full position. The airplane touched down abruptly on the right side of the runway and headed off the runway toward the runway safety area. The pilot attempted to correct with opposite rudder but overcorrected and the airplane exited the left side of the runway. The pilot reported he then attempted a go-around but was not able to establish enough airspeed to become airborne, so he aborted the maneuver. During the runway excursion, the nose landing gear collapsed, and the right wing struck the ground, which resulted in substantial damage to the engine mount.

The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

At the time of the accident, the pilot was landing the airplane on runway 1R in a variable wind of 5 knots, gusting to 20 knots.

Probable cause

The pilot's inadvertent retraction of the flaps while landing which resulted in a hard landing and loss of directional control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24LA122
Event ID
20240226193837
Case number
CEN24LA122
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, cause areas. 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: 62ad53969cff4bf0d593ff787fc9593df82d0391ecab815224d0a7fe02512ac4; retrieved 2026-09-16T18:32:22.878Z.