ERA24LA046 · Piper PA-39
Piper PA-39 · Accident: landing gear not configured
From Franklin County State Airport (FSO) to an unrecorded destination
Event
- NTSB case
- ERA24LA046
- 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
- 0
- 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-39
- Aircraft type
- Piper PA-39
- 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
- N289WW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Franklin County State Airport (FSO), Highgate, VTTo not recorded
- Aircraft age
- About 52 years (built 1971)
- 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 not configured
- 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
- 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 during the landing rollout on a 3,001-ft-long, asphalt runway, he intended to retract the flaps, but instead he retracted the landing gear. The result was that all three of the landing gear assemblies retracted into their respective wheel wells during the landing roll. The lower fuselage stringers were substantially damaged. The pilot added that there were no preimpact mechanical malfunctions with the airplane. The airplane was equipped with a squat switch on the left main landing gear that was designed to prevent the landing gear from inadvertently retracting; however, the switch required that sufficient weight be on the landing gear in order to work effectively. The pilot stated, and a video of the landing confirmed, that the airplane was still moving at relatively high speed when he selected the landing gear handle to the retracted position. The pilot reported that the squat switch was tested at the last annual inspection and that it operated normally during the inspection. Based on this information, it is likely that the airplane’s wings were still generating lift when the landing gear handle was selected to the retracted position and the gear struts was not compressed enough to activate the squat switch.
Probable cause
The pilot’s inadvertent retraction of the landing gear during landing rollout, which resulted in a landing gear collapse.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA046
- Event ID
- 20231122193415
- Case number
- ERA24LA046
- 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, 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: 133f3c2a76140bcc2b0ce34419ca85de7e4bdee9db066103ae830edf32d588a3; retrieved 2026-09-16T18:18:47.067Z.