NTSB CAROL · Event
Event DFW05LA080
Aircraft involved
Probable cause & findings
The pilot's misjudgment of airspeed and his failure to abort the landing resulting in an overrun. A contributing factor was the wet runway.
Factual narrative
On March 7, 2005, approximately 0830 central standard time, an Aero Vodochody L-39C experimental military jet trainer, N8098T, registered to and operated by the pilot, was substantially damaged during a runway overrun while landing on Runway 14 at the Shreveport Downtown Airport (DTN), near Shreveport, Louisiana. The airline transport pilot and passenger received minor injuries. Instrument meteorological conditions prevailed, and an instrument flight rules flight plan was filed for the 14 Code of Federal Regulations Part 91 personal flight. The 238-nautical mile cross-country flight originated from the Houma-Terrebonne Airport (HUM), near Houma, Louisiana, approximately 0730, and was destined for DTN. The 7,200-hour pilot reported in the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2) that during a non-precision instrument approach to runway 14, at an airspeed of 140 knots, "the airplane experienced a downdraft causing the airplane to sink to 500 feet" mean sea level (msl), however, the pilot corrected the altitude and leveled off at 700 feet msl. After descending to the minimum descent altitude of 600 feet msl, the pilot saw the runway environment and continued the approach. At this time he noted light rain showers in the area. The pilot stated that after selecting full flaps and verifying the landing gear was down and locked, he performed a "normal landing in the normal touchdown area of runway 14." During the landing roll, he noted that braking action was "poor" and "the runway seemed wavy." The pilot then applied maximum braking using the hand brake while moving the control stick forward "to depress the squat switch on the nose wheel for braking," however, braking action remained poor. The pilot added that due to the 10-second spool-up time from idle power to full power, a go-around was not an option, and he elected to pull the emergency brake handle to assist in stopping the airplane. Subsequently, at an airspeed of approximately 20 knots, the airplane exited the departure end of runway 14, rolled down a shallow hill, and came to rest in a nose low attitude near an airport service road. A witness located on the ramp area of the airport reported in a written statement that he observed the L-39 during the landing roll on runway 14 near the runway 23/5 intersection "traveling quite rapidly." Using the Landing Ground Roll calculation chart (Figure A7-3-TAB) within the operating handbook for the L-39, the pilot calculated that the required landing distance for the estimated landing weight and speed to be approximately 2,612 feet. The chart states that the following conditions must exist: Idle power setting, full flaps, and speed brakes retracted. The pilot stated in the NTSB Form 6120.1/2 under the Recommendation (How This Accident Could Have Been Prevented) section: "more conservative estimation of runway stopping distance on [a] wet runway and better airspeed control on short final after viewing the runway environment." Runway 14 is a 5,018-foot long and 150-foot wide asphalt runway. The airport manager reported the runway features slight upslope mid-length to assist in water draining. Examination of the runway by airport personnel shortly after the accident revealed no pooling of water; however, the surface of the runway was wet. Examination of the airplane, by the pilot revealed the nose structure was crushed downwards and aft. The nose wheel landing gear was also collapsed and pushed aft. At 0753, the automated surface observing system at DTN reported wind from 250 degrees at 3 knots, visibility 2 statute miles, rain, cloud condition overcast at 600 feet, temperature 15 degrees Celsius, dew point 13 degrees Celsius, and an altimeter setting 29.85 inches of Mercury. At 0853, the automated surface observing system at DTN reported wind from 250 degrees at 4 knots, visibility 1 statute mile, rain, cloud condition broken at 400 feet, broken at 1,000 feet, and overcast at 1,700 feet, temperature 16 degrees Celsius, dew point 14 degrees Celsius, and an altimeter setting of 29.86 inches of Mercury. The 7,200-hour pilot reported that during landing roll, the airplane overran the departure of the 5,017-foot long runway. The airplane rolled down a shallow hill, and came to rest on a road. The nose gear was collapsed. The pilot stated that during the non-precision instrument approach at an airspeed of 140 knots, the airplane descended below the minimum descent altitude. After reestablishing the correct altitude, the pilot established visual contact with the runway environment and "performed a normal landing in the normal touchdown area." During the landing roll, on the wet runway, the pilot noted braking action was poor. Despite using the hand brake and emergency hand brake system, braking action remained poor. The pilot reported the accident could have been prevented by "more conservative estimation of runway stopping distance on (a) wet runway, and better airspeed control on short final after viewing the runway environment." Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_DFW05LA080.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes)
Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper
Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…
Browse the full corpus — academia portal ↗