ERA16LA092 · Piper PA 30
Piper PA 30 · Accident: landing gear not configured
From W H 'Bud' Barron Airport (DBN) to an unrecorded destination
Event
- NTSB case
- ERA16LA092
- 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 30
- Aircraft type
- Piper PA-30
- 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
- N68X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From W H 'Bud' Barron Airport (DBN), Dublin, GATo not recorded
- Aircraft age
- About 53 years (built 1963)
- 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
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was receiving multiengine flight instruction from a flight instructor. The wind was about 20° off the runway heading at 8 knots, gusting to 16 knots. The pilot indicated that, after flying for about 50 minutes then landing, they reviewed procedures for a short-field obstacle takeoff and a short-field obstacle landing. The short-field takeoff was normal, and they joined the traffic pattern for landing. When the airplane was abeam the numbers for the landing runway, they completed the prelanding checklist, which included ensuring the landing gear were extended to the down-and-locked position. The pilot verbally called out the "GUMP" check with acknowledgment from his flight instructor and then turned onto final approach at higher than normal airspeed to compensate for the wind gusts. When the airplane crossed the runway threshold, the pilot further reduced power and closed the throttles. He then descended the airplane toward the runway and started his flare as the airspeed decreased. The pilot reported that all indications of touchdown were normal with weight on wheels for about 50 yards or so when it felt as if the airplane was "shimmying," followed shortly thereafter by a "sandpaper sound" of the propellers striking the runway. According to the flight instructor, during rollout, the pilot reached to select the wing flaps up, simulating a short-field landing, and the brakes were applied. The airplane then settled completely on its belly and slid to the right of centerline where it came to a stop. The instructor noticed that the flaps were partially retracted when the airplane came to rest. Scrape marks and propeller strike marks were found on the runway surface, and the airplane had sustained substantial damage to the belly of the fuselage. Examination of the airplane revealed no evidence of preaccident malfunctions or failures of any of the components that made up the landing gear retraction system that would have precluded normal operation. Postaccident operational checks of the landing gear system, during which the landing gear were extended and retracted several times, also did not reveal any anomalies. The owner’s handbook for the accident airplane make/model included a caution indicating that it was “possible for a pilot to inadvertently reach for the landing gear selector switch instead of the wing flap switch while there is still enough lift on the wings to keep full weight of the airplane off the wheels and thus prevent the actuation of the landing gear safety mechanism, causing retraction during the landing roll.” Thus, it was likely that the pilot inadvertently operated the landing gear selector instead of the flaps, during the practice short-field landing, which resulted in the landing gear retraction. Because the airplane was operating at a higher-than-normal speed due to the gusting wind conditions, enough aerodynamic lift was being produced by wings to keep the full weight of the airplane off of the wheels, which prevented actuation of the landing gear safety mechanism.
Probable cause
The pilot’s inadvertent retraction of the landing gear during the landing roll following a landing approach in gusting wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16LA092
- Event ID
- 20160120X62950
- Case number
- ERA16LA092
- 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: 87e64069c612e05c4f4ad29b3a01368f0c973b0b14dbbb3db79a91e5984a4933; retrieved 2026-09-16T03:06:27.208Z.