FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19LA217 · Piper PA34 200

10 Jul 2019 · Ypsilanti, MI, United States

Piper PA34 200 · Accident: abnormal runway contact during takeoff

From Willow Run Airport (YIP) to Willow Run Airport (YIP)

Report a problem

Event

NTSB case
CEN19LA217
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 PA34 200

Aircraft type
Piper PA34
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
N2930Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Willow Run Airport (YIP), Ypsilanti, MITo Willow Run Airport (YIP), Ypsilanti, MI
Aircraft age
About 45 years (built 1974)
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
Takeoff
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
Abnormal runway contact
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The commercial pilot was preparing for a checkride with a flight instructor in a multiengine airplane. While taking off for a fifth touch-and-go landing, the pilot retracted the flaps, increased the power, and raised the airplane's nose about 3° to 5°. The instructor stated that, as the airplane lifted and weight was removed from the landing gear, the gear appeared to retract. Subsequently, the airplane began to settle back on the runway, the right wing and propeller impacted the runway, and the right engine lost power. The airplane then banked right, and the instructor then assisted the pilot by retarding the throttle, leveling the wings, and lowering the nose. The airplane slid and came to rest on its belly off the right side of the runway, which resulted in substantial damage to the right wing and the fuselage.

The landing gear doors did not exhibit any damage. The tires were fully retracted into their respective wheel well with no abnormal markings or signs of damage that would be consistent with a landing gear collapse. The airplane was placed on jacks with the landing gear still retracted. When electrical power was applied, the gear extended as designed. The landing gear selector was then placed in the "up" position several times, and each time, the landing gear retracted in about 6 seconds. The examination revealed no evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation.

Following the accident, neither pilot could recall the position of the landing gear during the takeoff. The instructor stated that he was unable to see the landing gear selector during the flight. According to the Pilot's Operating Manual, the landing gear can only retract when the landing gear selector is in the "up" position and the oleo strut is extended more than 8 inches. A microswitch incorporated into the throttle quadrant will activate a warning horn if the landing gear selector is in the "up" position when the airplane is on the ground. Neither pilot reported hearing this warning horn. Therefore, it is unlikely that the landing gear selector was placed in the "up" position when the airplane was still on the ground. Given this evidence, it is likely that the pilot prematurely moved the landing gear selector to the "up" position, which allowed the landing gear to retract before a positive climb rate was established, and the lack of a positive climb rate, which led to the airplane settling back on the runway with the gear retracted.

Probable cause

The pilot's premature movement of the landing gear selector to the "up" position during takeoff, which allowed the landing gear to retract before a positive climb rate was established, and the lack of a positive climb rate, which led to the airplane settling back on the runway with the gear retracted.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19LA217
Event ID
20190710X85327
Case number
CEN19LA217
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. 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: f76dc8dea85a86be0ddd5c62264bd0566d1f9e037b0889b42206b560d1f545e0; retrieved 2026-09-16T09:23:48.121Z.