FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA390 · Piper PA46 310P

22 Jul 2016 · Claremore, OK, United States

Piper PA46 310P · Accident: loss of control on ground during takeoff

From Claremore Regional Airport (GCM) to Wichita Dwight D. Eisenhower National Airport (ICT)

Report a problem

Event

NTSB case
GAA16CA390
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 PA46 310P

Aircraft type
Piper PA46
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
N9111P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Claremore Regional Airport (GCM), Claremore, OKTo Wichita Dwight D. Eisenhower National Airport (ICT), Wichita, KS
Aircraft age
About 29 years (built 1987)
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
Loss of control on ground
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 he was performing the takeoff on a taxiway, due to a notice to airmen (NOTAM) in effect which closed the sole runway at the airport and allowed takeoff's and landing's from the parallel taxiway. During the takeoff roll, the pilot reported that the airplane hit a "dip" in the pavement and became airborne unintentionally. The pilot further reported that he heard the stall warning horn and pitched forward, but the airplane drifted off to the left into a ditch and the nose and main landing gear collapsed.

The left and right wings were substantially damaged.

The pilot did not report any mechanical malfunctions or failures with the airplane that would have precluded normal operation.

The airport manager provided video surveillance of the takeoff. The video showed that about 2,050 feet into the takeoff roll, the airplane pitched up, the nose and left main landing gear became airborne, but the airplane did not climb. Subsequently, the airplane touched back down and attempted to become airborne a second time about 300 feet further into the takeoff roll. The airplane's nose and main landing gear monetarily became airborne, but the airplane quickly touched back down and moved out of camera view.

The pilot reported that the takeoff weight was about 1 pound under the maximum allowable takeoff weight and he was attempting to perform a short field takeoff technique.

The density altitude about the time of departure was 3,168 feet, the pressure altitude was 579 feet, and the temperature was 93 Fahrenheit (34 Celsius). The Federal Aviation Administration (FAA) provides guidance on how density altitude affects aircraft performance. According to the FAA Koch Chart, the airplane would have likely experienced a 35% increase to the normal takeoff distance and a 25% decrease in a normal climb rate.

The FAA Airplane Flying Handbook in part states: "Due to the reduced drag in ground effect, the airplane may seem to be able to take off below the recommended airspeed. However, as the airplane rises out of ground effect with an insufficient airspeed, initial climb performance may prove to be marginal because of the increased drag. Under conditions of high-density altitude, high temperature, and/or maximum gross weight, the airplane may be able to become airborne at an insufficient airspeed, but unable to climb out of ground effect. Consequently, the airplane may not be able to clear obstructions, or may settle back on the runway."

It is likely that the pilot exceeded the critical angle of attack during the two initial climbs and the airplane did not exit ground effect due to insufficient airspeed at rotation.

Probable cause

The pilot's failure to maintain directional control during takeoff after multiple climb attempts at insufficient airspeed, which resulted in a runway excursion, a landing gear collapse, and a collision with a ditch.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA390
Event ID
20160726X63300
Case number
GAA16CA390
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: 77e6e708ccd7c25cf9a4a94d1181579e2e833349d51914c6c2a9d8a49c11f1de; retrieved 2026-09-16T03:42:11.247Z.