FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW05CA011 · Piper PA-28

25 Oct 2004 · Abilene, TX, United States

Piper PA-28 · Accident: loss of control on ground/water during landing

From Sherman Municipal Airport (SWI) to Abilene Regional Airport (ABI)

Report a problem

Event

NTSB case
DFW05CA011
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
Instrument Meteorological Cond

Piper PA-28

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
N9284J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sherman Municipal Airport (SWI), Sherman, TXTo Abilene Regional Airport (ABI), Abilene, TX
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
Landing · landing roll
First occurrenceThe 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/water
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

  • Pilot in command › Directional control, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The 3000-hour commercial pilot reported that due to the heavy rain and instrument weather conditions that prevailed, he requested an Instrument Landing System (ILS) approach. During the landing roll, the pilot reported that the airplane hit a patch of water on the wet runway, and as a result, the airplane veered to the left. Subsequently, the pilot applied right rudder to correct the situation, but the nose wheel did not become effective until it came into contact with grass off the left side of the runway. At this time, the pilot attempted to steer the airplane back onto the runway, but the tire of the left main landing gear hit a runway light, and the front of the aircraft hit a taxiway sign.

Probable cause

The pilot's failure to maintain directional control during the landing roll. Contributing factors were the wet runway surface and rain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW05CA011
Event ID
20041129X01878
Case number
DFW05CA011
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2004-10-26.
  • API snapshot SHA-256: d48c555d51ff22bc7eaa6a3e81da196bcdcb7a3e94a656146bb00e56830b5195; retrieved 2026-09-22T06:34:27.606Z.