NTSB CAROL · Event
Event BFO94LA132
Registry · N8505E
FAA Aircraft Registry record.
Make / Model
AIR TRACTOR INC AT-802A
Seats / Engines
2 seats · 1 engine
ADS-B equipped
Yes — Mode-S ABAA64
Registrant of record
VISSER AG INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
THE PILOT'S MISJUDGEMENT OF SPEED AND DISTANCE WHICH RESULTED IN A LANDING OVERRUN. A CONTRIBUTING FACTOR IS THE PILOT'S DELAY IN INTIATING A GO-AROUND.
Factual narrative
On August 11, 1994, at 1500 eastern daylight time, N8505E, a Piper PA-28-181, exited the runway and collided with the ground during landing at Eagles Nest Airport, Waynesboro, Virginia. The certificated private pilot and his three passengers received minor injuries while the airplane sustained substantial damage. Visual meteorological conditions prevailed and a VFR flight plan was filed. The personal flight was operated under 14 CFR 91 and originated in Georgetown, South Carolina. The destination was Waynesboro, Virginia. According to the pilot, he entered the traffic pattern and the airplane was at an altitude of 2000 feet MSL on final approach. He stated that he continued his approach to runway 6 and at about 50 to 100 feet above the ground, "I realized my ground speed was higher than my airspeed...I decided to go around, I advanced the throttle and the engine sputtered. I realized the engine was not going to produce sufficient power for a go-around...I pulled the power back and put the airplane on the runway with approximately 1000 feet of runway left." A witness reported that, "...the airplane made an extremely high approach and the pilot initiated a slip to lose altitude. Aircraft touched down at approximately 250 to 400 feet from the end of the runway." The aircraft exited the runway over a hill, through a fence and collided with a ditch. An FAA Aviation Safety Inspector reported that the pilot applied the brakes after touching down, but the airplane continued beyond the end of the runway off the 500 foot grass overrun and stopped about 200 yards beyond the airport boundary. He also stated that there was no evidence of mechanical malfunction noted. THE PILOT REPORTED THAT WHILE ON FINAL APPROACH HE REALIZED THAT HIS GROUND SPEED WAS HIGHER THAN HIS AIRSPEED. HE STATED THAT AT AN ALTITUDE OF ABOUT 50 TO 100 FEET HE DECIDED TO GO-AROUND, BUT THE ENGINE SPUTTERED. THE AIRPLANE TOUCHED DOWN LONG AND EXITED THE RUNWAY COLLIDING WITH A FENCE. A WITNESS REPORTED THAT THE PILOT MADE AN EXTREMELY HIGH APPROACH, AND THE PILOT INITIATED A SLIP TO LOSE ALTITUDE. ANOTHER WITNESS REPORTED THAT THE AIRPLANE WAS ABOUT 250 TO 400 FEET FROM THE RUNWAY DEPARTURE END WHEN IT TOUCHED DOWN. AN FAA AVIATION SAFETY INSPECTOR WHO EXAMINED THE AIRPLANE AND THE ACCIDENT SITE STATED THAT THE PILOT APPLIED THE BRAKES AFTER TOUCHING DOWN LONG, AND THERE WAS NO EVIDENCE OF MECHANICAL MALFUNCTION WHEN HE EXAMINED THE AIRPLANE. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1994_BFO94LA132.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 ↗