NYC00LA243
2000-08-29 · DUNKIRK, New York, United States · None · 1 aircraft · Status: Completed
Airport DKK
Current FAA registration · N803SP
- Make / Model
- CESSNA 172S
- Year of manufacture
- 1999 · 1 years old at event
- Engine
- LYCOMING I0360 SER (180 hp)
- Seats / Engines
- 4 seats · 1 engine
- Last airworthiness date
- 19990211
- ADS-B equipped
- Yes — Mode-S AAEEA0
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's improper recovery from a bounced landing.
Factual narrative
On August 29, 2000, at 1000 Eastern Daylight Time, a Cessna 172, N803SP, was substantially damaged during an aborted landing at the Chautauqua County/Dunkirk Airport (DKK), Dunkirk, New York. The certificated commercial pilot and three passengers were not injured. Visual meteorological conditions prevailed. No flight plan was filed for the personal flight that originated at the Erie International Airport (ERI), Erie, Pennsylvania, and was conducted under 14 CFR Part 91. In a telephone interview, the pilot stated that before landing at DKK, he contacted the airport unicom and requested an "airport advisory." He was instructed that Runway 33 was available for landing, and entered the downwind leg of the traffic pattern. After the airplane crossed the threshold of the runway, it "kept floating and floating," and the pilot observed "no decrease in airspeed." The airplane touched down about 1/3 of the length of the runway, and then bounced. Full power was applied and a go-around was initiated. The airplane then "ran out of runway, bounced on the grass, and flipped over nose-first." The pilot reported that he normally flies at 80 mph on final approach, and crosses the threshold at 70 mph. He could not recall what his airspeed was during the accident flight; however, he stated the airspeed was "close to his normal numbers." The pilot stated that his "delayed go-around procedure" contributed to the accident. In a subsequent written statement, the pilot reported he extended 20 degrees of flaps on final, his final approach was "long" and his final approach speed was higher than normal. A statement was provided by the operator, which summarized observations made by the passengers on board the airplane. They stated: "The first touchdown was beyond the intersection. Impact was hard and aircraft bounced. Second touchdown also bounced. Pilot added low power to assist in arresting 'porposing.' Upon final touchdown, the pilot judged insufficient runway remained to stop, and rejected the landing, initiating a go-around. The pilot positioned the flap handle in the fully retracted position and advanced full throttle. The aircraft rolled off the end of the runway, skipped part way across a drainage ditch and impacted the opposite side of the drainage ditch with the nose gear. The aircraft continued on basically a straight path another 100 feet...and then nosed over and came to rest inverted approximately 250 feet from the end of the runway aligned with and approximately 30 west of the runway centerline." According to a Federal Aviation Administration inspector, the airplane incurred substantially damage to the vertical stabilizer, empannage, and both wings. Additionally, the engine was broken off the firewall. At 0953, the winds were reported at DKK as variable, at 5 knots. Runway 33 was a 4,000 foot long, 100 foot wide asphalt runway. The pilot flew an approach to Runway 33, a 4,000 foot long asphalt runway. On final approach, the pilot added 20 degrees of flaps and noticed his airspeed was higher than normal. The airplane touched down about 1/3 of the length of the runway and bounced twice. When the pilot realized there was not sufficient runway to stop the airplane, he applied full power, retracted the flaps, and initiated a 'go-around'. The aircraft proceeded off the runway, and nosed over about 250 feet from the departure end of the runway. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_NYC00LA243.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 2023 · Reprint (Version printed in journal) Finite Element Simulation of Three Full-Scale Crash Tests for Cessna 172 Aircraft
The NASA Emergency Locator Transmitter Survivability and Reliability project was initiated in 2013 to assess the crash performance standards for the next generation of emergency locator transmitter (E…
- NASA NTRS 2019 · Conference Paper Crash Testing and Simulation of a Cessna 172 Aircraft: Pitch Down Impact Onto Soft Soil
During the summer of 2015, NASA Langley Research Center conducted three full-scale crash tests of Cessna 172 (C-172) aircraft at the NASA Langley Landing and Impact Research (LandIR) Facility.
- NASA NTRS 2019 · Technical Memorandum (TM) Simulating the Impact Response of Three Full-Scale Crash Tests of Cessna 172 Aircraft
During the summer of 2015, a series of three full-scale crash tests were performed at the Landing and Impact Research Facility located at NASA Langley Research Center of Cessna 172 aircraft.
- 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…