DFW06CA047 · Mooney M20J
Mooney M20J · Accident: overrun during landing
From Addison Airport (ADS) to Victoria Regional Airport (VCT)
Event
- NTSB case
- DFW06CA047
- 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 M20J
- 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
- N5765N
- Operator
- Milton A. Killebrew · private individual
- Onboard fatalities
- Unknown
- Route
- From Addison Airport (ADS), Addison, TXTo Victoria Regional Airport (VCT), Victoria, 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 › Distance/speed, misjudged
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 1,559-hour private pilot was on a 247-nautical mile cross-country flight. The pilot reported that prior to arriving at his final destination, the Automated Weather Observing System reported that instrument flight rules (IFR) conditions prevailed throughout the area. He then contacted the local Flight Service Station (FSS) on the radio to inquire about the closest Visual Fight Rules (VFR) weather conditions. The FSS informed the pilot that the nearest location would be at Yoakum, Texas. A Federal Aviation Administration (FAA) Inspector who responded to the accident scene reported that the pilot flew to Yoakum, Texas, and landed "on the latter end of Runway 13" Runway 13 was reported to be a 3,445-feet long by 60-feet wide asphalt runway. The inspector added that after touchdown, the low-wing tricycle gear airplane departed the left side of the runway and traveled approximately 80-yards, up an embankment, through a barbed wire perimeter fence, across a highway and through a second barbed wire fence. The airplane came to rest upright in a pasture. The pilot reported the wind at T85 were light and variable.
Probable cause
The pilot's misjudged distance/speed which resulted in an overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06CA047
- Event ID
- 20060131X00137
- Case number
- DFW06CA047
- 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: 16c679778561b5e620cdc9c60315d3712f3843b67738c914059859921918640c; retrieved 2026-09-22T05:10:34.012Z.