FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19LA150 · Piper PA28 140

23 May 2019 · McKinney, TX, United States

Piper PA28 140 · Accident: abnormal runway contact during landing

From Aero Country Airport (T31) to Aero Country Airport (T31)

Report a problem

Event

NTSB case
CEN19LA150
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 PA28 140

Aircraft type
Piper PA28
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
N1568J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Aero Country Airport (T31), McKinney, TXTo Aero Country Airport (T31), McKinney, 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 · aborted after 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
Abnormal runway contact
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Personnel issues › Task performance

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

NTSB narrative

The pilot and pilot-rated passenger conducted a local flight before returning to the airport for landing on runway 17. The pilot reported that the approach was smooth and normal, but as the airplane was about to touch down, it was "pushed down hard to the surface and quickly sucked back up." She applied engine power for a go-around, and as the airplane gained altitude, a gust of wind occurred; the airplane subsequently impacted a storage facility and a home just west of the airport. Postaccident examination of the airplane and engine revealed no anomalies that would have precluded normal operation. Review of weather reports from a nearby airport about the time of the accident revealed wind from 140° at 11 knots gusting to 23 knots. Another weather station recorded wind from 140° at 16 knots gusting to 29 knots. Based on the available information, the accident was consistent with the pilot's loss of control during an attempted go-around in gusting crosswind conditions.

Probable cause

The pilot's loss of control during an attempted go-around in gusting crosswind conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19LA150
Event ID
20190524X10703
Case number
CEN19LA150
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: fc35ec1b75adba551a158cf6dc9c14e063cedf90a51ce361615cd4e8d113ce98; retrieved 2026-09-16T09:03:09.065Z.