NYC01LA210
2001-08-12 · Brockport, New York, United States · Serious · 1 aircraft · Status: Completed
Airport 7G0
Aircraft involved
Probable cause & findings
The pilot's delayed go-around during the landing attempt. Factors included the dark night conditions and the pilot's inadequate preflight decision to fly to an airport with inoperative surface lighting.
Factual narrative
On August 12, 2001, at 2255 eastern daylight time, a Cessna 172L, N7878G, was substantially damaged during an off-runway landing at Ledgedale Airpark (7G0), Brockport, New York. The certificated airline transport pilot and the pilot-rated passenger were seriously injured. Night visual meteorological conditions prevailed at the time of the accident. No flight plan was on file for the flight, from Akron Fulton International Airport (AKR), Akron, Ohio, to Brockport. The personal flight was conducted under 14 CFR Part 91. According to the pilot, the flight from Akron was uneventful. Upon arrival at Ledgedale, "the airport beacon was operating, [and] as expected from NOTAM, runway and taxiway lights were inop." The pilot attempted a landing on runway 28, then went around because he couldn't see the runway "soon enough." He flew around the pattern again, made another approach to runway 28, and "attempted another go around for the same reason." Shortly after commencing the second go around attempt, the airplane impacted the ground. A Federal Aviation Administration (FAA) inspector reported that the airplane landed to the right of the taxiway that paralleled runway 28. The left wing struck the ground, the nose wheel collapsed, and the lower part of the cabin was crushed. The airpark was the pilot's home base. According to a police report, the airplane was found approximately 50 feet north of the parallel taxiway, about 700 feet from the approach end of the runway. The taxiway was about 250 feet north of the runway. The pilot did not note any mechanical problems, and a subsequent inspection by FAA personnel, together with investigators from the airframe and engine manufacturers, did not reveal any pre-impact malfunctions. Weather, recorded at an airport 12 nautical miles to the southeast, about the time of the accident, included calm winds, a broken cloud layer at 7,000 feet, and an overcast cloud layer at 8,500 feet. A witness reported that there was no moon, and fire department personnel reported difficulty in finding the airplane due to the darkness. At the completion of a night, cross-country flight, the pilot attempted to land at his home airpark under dark night conditions. The rotating beacon was operating, and per the NOTAM in effect, the runway and taxiway lights were inoperative. The pilot made an approach, then went around because he could not see the runway "soon enough." The pilot made another approach, and again attempted to go around. Shortly after commencing the go-around attempt, the airplane impacted the ground about 300 feet to the right of, and 700 feet from the approach end of the runway. The impact point was also 50 feet to the right of the parallel taxiway. There were no mechanical malfunctions noted. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2001_NYC01LA210.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…