CEN13LA188 · Piper PA 46-350P
Johnson County Aviation Group Piper PA 46-350P · Accident: runway excursion during takeoff
From Johnson County Executive Airport (KOJC) to Johnson County Executive Airport (KOJC)
Event
- NTSB case
- CEN13LA188
- 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 46-350P
- Aircraft type
- Piper PA-46
- 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
- N715BB
- Operator
- Johnson County Aviation Group
- Onboard fatalities
- Unknown
- Route
- From Johnson County Executive Airport (KOJC), Olathe, KSTo Johnson County Executive Airport (KOJC), Olathe, KS
- 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
- Runway excursion
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the takeoff roll, the airplane veered to the right, and the pilot applied left rudder to correct back to the runway centerline. About the same time, the engine turbocharger became effective, increasing the left yaw. The pilot was unable to counteract the left yaw and aborted the takeoff. The airplane departed the runway and impacted a snow bank, resulting in the collapse of the nose landing gear. A postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The lower section of the engine mount had fractured surfaces consistent with overstress fractures, which were likely caused by the nose landing gear collapse sequence.
Probable cause
The pilot’s failure to maintain directional control during takeoff, which resulted in a runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13LA188
- Event ID
- 20130311X11254
- Case number
- CEN13LA188
- 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: 429264b24555ef90a28fd9b02039074bd8547c21f277bde4c87e5e2999f09944; retrieved 2026-09-15T21:03:38.428Z.