DFW05FA020 · Piper PA-31-350
Piper PA-31-350 · Accident: loss of control in flight on approach
From Dodge City Regional Airport (DDC) to San Antonio International Airport (SAT)
Event
- NTSB case
- DFW05FA020
- 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
- 5 · 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-31-350
- Aircraft type
- Piper PA-31
- 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
- N40731
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dodge City Regional Airport (DDC), Dodge City, KSTo San Antonio International Airport (SAT), San Antonio, 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
- Approach · IFR final approach
- 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 in flight
- 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
- Pilot in command › Aircraft 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 twin-engine airplane collided with a residential structure and terrain following a loss of control after the pilot experienced difficulties maintaining course during an Instrument Landing System (ILS) approach while on instrument meteorological conditions. The impact occurred approximately 3.7 miles short of the approach end of the runway. Radar data depicted that after the 8,700-hour commercial pilot was vectored to the ILS Runway 3 approach, the airplane remained left throughout the approach before turning right of the localizer approximately 2 miles before the final approach fix (FAF). Radar then showed the aircraft turn to the left of course line. When the aircraft was abeam the FAF, it was approximately 1 mile left of the course line. As the aircraft closed to approximately 1.5 miles from the runway threshold, the aircraft had veered about 1.3 miles left of the course line (at which time air traffic control instructed the pilot to turn left to a heading of 270 degrees). The aircraft continued to turn left through the assigned heading and appeared to be heading back to the ILS course line. According to the radar, another aircraft was inbound on the ILS course line and Air Traffic Control Tower (ATCT) instructed the pilot to turn left immediately. Thereafter, the aircraft went below radar coverage. A witness, located approximately 1.25 miles northwest of the accident site, reported that he heard a very loud noise, and then observed an airplane flying toward a building, approximately 60 feet in height. The airplane was observed to have pitched-up approximately 45 - 90 degrees just before the building and disappeared into the clouds. A second witness located approximately 1 mile northwest of the accident site reported that he heard a low flying aircraft, and then observed a white twin-engine airplane banking left out of the clouds. The airplane leveled out, and flew into the clouds again a few seconds later. The witness stated that the airplane was at an altitude of 100-200 feet above the ground. A third witness located adjacent to the accident site reported that they heard the sound of a low flying airplane in the distance. As the sound became louder and louder, they looked up and observed the airplane in a near vertical attitude as it impacted trees and the side of an apartment complex. Examination of the airplane did not reveal any pre-impact mechanical anomalies. A weather observation taken approximately 15 minutes after the accident included a visibility 4 statue miles, light drizzle and mist, and an overcast ceiling at 400 feet.
Probable cause
The pilot's failure to maintain control during an ILS approach. Contributing factors were the prevailing instrument meteorological conditions( clouds, low ceiling and drizzle/mist), and the pilot's spatial disorientation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05FA020
- Event ID
- 20041124X01866
- Case number
- DFW05FA020
- 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: investigation status, coordinates. 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: efe64d12d93033571dcbf31b15db12f974cfe1e95b22e25387781768c4ccdc8a; retrieved 2026-09-20T18:12:07.430Z.