FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA19CA140 · Piper PA24 260

12 Feb 2019 · Slaton, TX, United States

Piper PA24 260 · Accident: runway excursion during landing

From Yoakum County Airport (F98) to Slaton Municipal Airport (F49)

Report a problem

Event

NTSB case
GAA19CA140
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 PA24 260

Aircraft type
Piper PA24
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
N9184P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Yoakum County Airport (F98), Plains, TXTo Slaton Municipal Airport (F49), Slaton, TX
Aircraft age
About 52 years (built 1967)
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 · landing roll
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 › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

The student pilot reported that, during landing, he became complacent and did not compensate for a right crosswind. The airplane exited the left side of the runway, crossed over the taxiway, and the right main landing gear collapsed. Subsequently, the right wing and the stabilator struck the ground.

The airplane sustained substantial damage to the right wing and the stabilator.

The student reported that there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

The student reported that the wind about the time of the accident was from 220° at 9 knots. The student landed the airplane on runway 18.

Probable cause

The student pilot's complacency, which led to his improper crosswind correction and subsequent failure to maintain directional control during the landing roll, which resulted in a runway excursion and ground collision.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA19CA140
Event ID
20190218X11140
Case number
GAA19CA140
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: 789340f79b5666f70e1112de9a725af7dbd6db0a4e715a5220634f1d82ce9457; retrieved 2026-09-16T08:36:07.172Z.