FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN15CA188 · Piper PA 46-350P

12 Feb 2015 · Akron, OH, United States

Piper PA 46-350P · Accident: loss of control on ground during landing

From Eagle Creek Airpark (EYE) to Akron Fulton International Airport (AKR)

Report a problem

Event

NTSB case
CEN15CA188
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
N427AB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Eagle Creek Airpark (EYE), Indianapolis, INTo Akron Fulton International Airport (AKR), Akron, OH
Aircraft age
About 13 years (built 2002)
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 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

  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airplane veered off the left side of the runway during landing with a left gusting crosswind. The maximum demonstrated crosswind velocity for the airplane was 17 knots. The pilot stated that he had applied right rudder and left aileron control inputs for the landing. The airplane left main landing gear touched down first and when the right main landing gear contacted the runway, a gust of wind lifted the left wing, resulting in a loss of directional control. The airplane veered off the left side of the runway and into a grass area adjacent to the runway where the nose landing gear collapsed. The airplane sustained substantial damage to the engine firewall. The pilot and passenger were uninjured. The pilot stated that there was no mechanical malfunction/failure of the airplane.

Probable cause

The pilot's failure to maintain directional control during a crosswind landing in gusting crosswind conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN15CA188
Event ID
20150403X41941
Case number
CEN15CA188
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: 1fef4ab64297e916d6b6a47d6b1d308fc3700010c376df27fe9e4ff600792ded; retrieved 2026-09-16T02:12:21.293Z.