FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12CA482 · Nelson Miles Sky Star Kitfox S 5

25 Jul 2012 · Weatherford, TX, United States

Nelson Miles Sky Star Kitfox S 5 · Accident: loss of control in flight during landing

From Parker County Airport (KWEA) to Parker County Airport (KWEA)

Report a problem

Event

NTSB case
CEN12CA482
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

Nelson Miles Sky Star Kitfox S 5

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
N4454U
Operator
Paul D. Eisheid · private individual
Onboard fatalities
Unknown
Route
From Parker County Airport (KWEA), Weatherford, TXTo Parker County Airport (KWEA), Weatherford, TX
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
Loss of control in flight
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 was practicing takeoffs and landings when the accident occurred. During the landing flare, the airplane drifted to the left of the runway centerline. The pilot overcorrected to the right before applying full power in an attempt to go around. The left main wheel contacted grass on the left side of the runway, and the airplane ground looped to the right. The firewall and the lower fuselage longerons sustained substantial damage.

Probable cause

The pilot's failure to maintain directional control during the landing flare. Contributing to the accident was the pilot’s delay in aborting the landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12CA482
Event ID
20120726X74734
Case number
CEN12CA482
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: 422d8ee0292d45279f538a62666fe920703cd6ae697fd8a8ee73986b253f5017; retrieved 2026-09-15T19:05:52.519Z.