FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW04CA228 · Mooney M20E

18 Aug 2004 · San Antonio, TX, United States

Mooney M20E · Accident: overrun during landing

From Speed Shore Company Headquarters Heliport (11XS) to Kestrel Airpark (1T7)

Report a problem

Event

NTSB case
FTW04CA228
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

Mooney M20E

Aircraft type
Mooney M20
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
N3379X
Onboard fatalities
Unknown
Route
From Speed Shore Company Headquarters Heliport (11XS), Bulverde, TXTo Kestrel Airpark (1T7), 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
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
Overrun
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 › Aborted landing, not performed
  • Pilot in command › Distance, misjudged

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

NTSB narrative

After landing on runway 30 (a 3,000-foot long and 40-foot wide asphalt runway), the airplane overran the departure end of the runway. Upon exiting the airport property, the airplane struck a no parking sign and entered a residential street where it collided with 3 sets of reflectors. The pilot continued taxing up hill and made a left turn as the left wing struck a stop sign. The pilot continued taxiing down a residential street through a 3-way intersection before an "individual forced the pilot to stop the airplane and get it towed back to the airport." The winds at the airport at the time of the accident were reported from 130 degrees at 7 knots.

Probable cause

The pilot's misjudged distance and his failure to abort the landing. A factor was the prevailing tailwind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW04CA228
Event ID
20040929X01516
Case number
FTW04CA228
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: 00b750d174441c8b102863bff1da738b484173deab5b5a0acefb98c1ac3eefce; retrieved 2026-09-22T06:52:53.335Z.