FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN20CA074 · Piper PA32 300

3 Feb 2020 · Kingfisher, OK, United States

Piper PA32 300 · Accident: loss of control on ground during landing

From Charles B. Wheeler Downtown Airport (MKC) to Kingfisher Airport (F92)

Report a problem

Event

NTSB case
CEN20CA074
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 PA32 300

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
N711PF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Charles B. Wheeler Downtown Airport (MKC), Kansas City, MOTo Kingfisher Airport (F92), Kingfisher, OK
Aircraft age
About 48 years (built 1972)
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
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 › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

According to the pilot, the airplane landed about 1,000 ft down the 2,800-ft-long runway. During the landing roll, the airplane's ground speed was fast. The pilot applied the brakes, but the airplane continued at a fast ground speed while approaching the end of the runway, so the pilot applied more pressure to the brakes. The airplane exited the left side of the runway onto soft grass, the nose landing gear strut failed, and the airplane came to rest. The airplane sustained substantial damage to the engine mounts. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation and that he should have aborted the landing.

Probable cause

The pilot's improper continuation of a landing in which he landed too far down the runway at too high a speed, which resulted in a loss of directional control and a runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20CA074
Event ID
20200203X53852
Case number
CEN20CA074
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. 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: effafadba20b2c14805c0666dabc4bb215299cdeffd256f56c9d31f188a7d2fd; retrieved 2026-09-16T11:02:23.315Z.