FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10LA303 · Piper PA-28R-180

6 Jun 2010 · Kingfisher, OK, United States

Piper PA-28R-180 · Accident: hard landing

From Kingfisher Airport (F92) to Kingfisher Airport (F92)

Report a problem

Event

NTSB case
CEN10LA303
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-28R-180

Aircraft type
Piper PA-28
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
N7559J
Operator
Edward L. Hale · private individual
Onboard fatalities
Unknown
Route
From Kingfisher Airport (F92), Kingfisher, OKTo Kingfisher Airport (F92), Kingfisher, OK
Aircraft age
Not recorded
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 · flare/touchdown
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
Hard landing
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 said that this was his second landing on the grass strip that day. The winds were gusty and there was a slight crosswind. He turned onto final approach at 80 knots indicated airspeed with the landing gear down and flaps fully extended. He descended to the round out (flare), but the airplane "floated." He lowered the nose to allow the airplane to settle and he heard the stall warning horn intermittently. He applied full throttle and the engine responded but the airplane continued to descend. The airplane landed "hard." The left wing struck the ground, the airplane bounced, and then the right wing struck the ground. The nose gear collapsed and the airplane skidded to a stop. The pilot said that he didn't take into consideration the density altitude and that if he had maintained a higher landing speed the airplane would not have stalled. An examination of the airplane revealed no preexisting anomalies.

Probable cause

The pilot's inadequate airspeed while landing, which led to an aerodynamic stall and a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10LA303
Event ID
20100607X62443
Case number
CEN10LA303
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: a0671faf2a48d15cd28003296035ce37e481596b74b412c90613329464bc74e8; retrieved 2026-09-15T14:23:08.755Z.