NYC02LA119
2002-06-20 · Hagerstown, Maryland, United States · Serious · 1 aircraft · Status: Completed
Airport HGR
N3282F has since been reassigned. It is now registered to a different aircraft (VAN'S AIRCRAFT RV-12), which was not involved in this event.
Aircraft involved
Probable cause & findings
The pilot's failure to perform a go-around and obtain the proper touchdown point, which resulted in an overrun. A factor in the accident was the crosswind condition.
Factual narrative
On June 20, 2002, about 1625 eastern daylight time, a Mooney M20, N3282F, was substantially damaged while landing at the Hagerstown Regional-Richard A. Henson Field Airport (HGR), Hagerstown, Maryland. The certificated private pilot and passenger were seriously injured. Visual meteorological conditions prevailed. No flight plan had been filed for the flight, which originated at Jackson County-Reynolds Field Airport (JXN), Jackson, Michigan. The personal flight was conducted under 14 CFR Part 91. In a written statement, the pilot said he was performing his second approach to runway 27, a 5,460-foot long, 150-foot wide, dry, asphalt runway. During the first approach, the airplane came in high and the pilot elected to perform a go-around. During the second approach, the pilot said he encountered a gust of wind, which "threw the airplane off the glide path" and the airplane landed "long," with about 1,500 feet of runway remaining. The pilot added that when he initially applied the brakes, they responded to gentle pressure; however, they "faded quickly." The airplane departed the end of the runway, struck an airport boundary fence and came to rest about 800 feet beyond the departure end of the runway. Witnesses reported they observed the airplane touch down about 4,000 feet beyond the approach end of the runway. The airplane bounced three times, and smoke was observed emanating from the airplane's tires before the airplane "launched" off the departure end of the runway. Examination of the airplane, which included the brake system by a Federal Aviation Administration inspector, did not reveal any pre-impact malfunctions. Winds reported at the airport about the time of the accident, were from 170 degrees at 8 knots. The pilot was performing his second approach to runway 27, a 5,460-foot long, 150-foot wide, dry, asphalt runway. During the first approach, the airplane came in high and the pilot elected to perform a go-around. On the second approach, the pilot said he encountered a gust of wind, and landed with about 1,500 feet of runway remaining. The pilot added that when he initially applied the brakes, they responded to gentle pressure; however, "faded quickly." The airplane departed the end of the runway, struck an airport boundary fence and came to rest about 800 feet beyond the departure end of the runway. Witnesses reported they observed the airplane touch down about 4,000 feet beyond the approach end of the runway. The airplane bounced three times, and smoke was observed emanating from the airplane's tires before the airplane "launched" off the departure end of the runway. Examination of the airplane, which included the brake system, did not reveal any pre-impact malfunctions. Winds reported at the airport about the time of the accident, were from 170 degrees at 8 knots. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2002_NYC02LA119.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (go-around). All research papers
- 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…