ERA13CA317 · Piper PA-28-151
Piper PA-28-151 · Accident: aerodynamic stall/spin during takeoff
From Boss Airport (08KY) to Mount Sterling Montgomery County Airport (IOB)
Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA13CA317
- 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-28-151
- 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
- N44293
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Boss Airport (08KY), Bronston, KYTo Mount Sterling Montgomery County Airport (IOB), Mt. Sterling, KY
- 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
- 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
- Aerodynamic stall/spin
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial Possible conflict
Cause areas
- Aircraft › Aircraft oper/perf/capability
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was attempting a soft-field takeoff from a turf runway that he described as “extremely wet and soggy with tall grass.” The airplane became airborne approximately halfway down the 2,500-foot-long runway, and the pilot reported that climb performance was degraded due to hot weather conditions. During the climb, the left landing gear impacted a line of trees past the runway end. The pilot stated that he was unable to maintain airspeed, and the airplane subsequently stalled and impacted an open field, resulting in substantial damage to the left wing. The fuselage was consumed by post-crash fire. The pilot reported there were no mechanical malfunctions or anomalies that would have precluded normal operation of the airplane.
Probable cause
The pilot’s failure to maintain airspeed during takeoff, which resulted in an aerodynamic stall. Contributing to the accident was the airplane’s reduced climb performance due to density altitude, as well as the pilot’s decision to initiate the takeoff from the wet turf runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13CA317
- Event ID
- 20130709X80600
- Case number
- ERA13CA317
- 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: b0992de1705a28975163ac42685f72f38f3ace4c968c33003cb804918ed5d9d0; retrieved 2026-09-15T22:10:36.567Z.