NTSB CAROL · Event
Event NYC97LA130
Registry · N8139C
FAA Aircraft Registry record.
Make / Model
CIRRUS DESIGN SR22
Year of manufacture
2003
TCDS
A00009CH · CIRRUS DESIGN CORP
Engine
CONT MOTOR IO-550 SERIES (300 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
20030827
ADS-B equipped
Yes — Mode-S AB1817
Registrant of record
ENHANCED AVIATION LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's misjudgment of distance and speed on final approach, and his failure to attain the proper touchdown point during landing. A factor in the accident was the night light condition.
Factual narrative
On June 28, 1997, about 0010 eastern daylight time, a Piper, PA-28R-200, N8139C, was substantially damaged during landing at the Frankfort-Highland Airport, Frankfort, New York. The certificated private pilot and three passengers were not injured. Night visual meteorological conditions prevailed, and a visual flight rules flight plan had been filed for the personal flight which originated at Wiscasset, Maine, about 1010. The flight was conducted under 14 CFR Part 91. In the NTSB Form 6120.1/2, and during a telephone interview, the pilot stated he entered a left downwind for runway 31, a 2,550 foot paved, lighted runway. The pilot said that his approach was normal and that he felt no reason to believe anything was wrong. During the landing flare, the airplane floated. The pilot said that he touched down long and realized he did not have enough runway available to go-around. The airplane departed the end of the runway continued down a 60 foot embankment, and into a swamp. The pilot reported no malfunctions with the airplane or engine. He also reported his total flight experience to be about 165 hours, including about 40 hours in make and model. The pilot was on a night approach to a 2,550-foot paved, lighted runway. The pilot stated that his approach was normal and that he felt no reason to believe anything was wrong. During the landing flare the airplane floated and touched down long. The pilot said he did not have enough runway available to go around. The airplane departed the end of the runway continued down a 60-foot embankment into a swamp. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_NYC97LA130.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 ↗