NTSB CAROL · Event
Event NYC02LA052
Aircraft involved
Probable cause & findings
The pilot's failure to achieve a proper touchdown point on the runway which resulted in an overrun. A factor was the pilot's lack of experience in short field operations.
Factual narrative
On January 26, 2002, at 1602 eastern standard time, a Socata TB-9, N28239, was substantially damaged when it overran the runway while landing at Marlboro Airport, Marlboro, Massachusetts. The certificated private pilot was not injured. Visual meteorological conditions prevailed for the business flight. No flight plan had been filed for the flight that was conducted under 14 CFR Part 91. According to the pilot, the flight originated from Westchester County Airport, White Plains, New York. The en route phase was without incident. Arriving in the Marlboro area, he checked the winds at a nearby airport, and observed the windsock at Marlboro Airport. He estimated the wind was a 90 degree crosswind from the left at 7 to 10 knots. The wind was not steady. The first two approaches to runway 32 terminated in a go-around due to excessive speed. On the third approach, he was more aware of his airspeed and was on his desired speed as he passed over the trees. However, when he pushed the nose down, he thought the airplane may have gained about 10 knots, although he was not certain of the actual speed increase. He thought the airplane touched down about 1/3 of the way down the runway; however, the brakes were not immediately effective. Around midfield there was more weight on the main landing gear wheels, and the brakes became effective. The pilot was unable to stop the airplane on the runway and struck a chain link fence located about 10 feet beyond the departure end of the runway. The pilot reported that he had never landed at Marlboro before. However, he did reference various sources to gain information about the airport prior to making the flight. He also checked the amount of runway required for landing and found there was sufficient runway. Further, the pilot reported that although he had made short field landings before, and stopped the airplane well within the distance of the available runway at Marlboro, he had never actually landed on a runway that short. Additionally, he did not raise the wing flaps after landing. According to an inspector from the Federal Aviation Administration (FAA), a witness reported that the airplane touched down about mid-field, and then departed the runway at the end. Further, the FAA inspector reported that there were skid marks for about 400 feet on the runway, which terminated at the location where the airplane came to rest. When he examined the airplane, he observed that the wings of the airplane had struck the poles on the fence and crushed the leading edge rearward. In addition, there were areas on the wings where the rivets had popped, and the wing skin was no longer held in place. There were creases in the wing skin on the left wing, and the spar was bent. According to data from the FAA, the runway was 1,682 feet long, 50 feet wide, and had an asphalt surface. According to the landing performance chart for the Socata TV-9, at maximum gross weight, under the atmospheric conditions reported, the airplane would have required 1,423 feet to clear a 50 foot obstacle at the end of the runway, and stop on the remaining runway. The pilot reported his total flight experience as about 98 hours, with 96 hours in make and model. He had received his private pilot certificate on December 4, 2001, and had logged 36 hours in the preceding 90 days, including 20 hours as pilot-in-command. The pilot made two approaches to a runway which terminated in go-arounds. On the third approach, the airplane touched down about halfway down the runway. The airplane overran the runway end and went into a chain link fence, located about 10 feet beyond the departure end of the runway. Skid marks were visible on the last 400 feet of the runway, and terminated where the airplane struck the fence. The runway was 1,682 feet long, with an approach over trees. The pilot reported that during training, he had stopped the airplane using less runway that was available; however, he had never landed on a runway as short as this runway. The pilot also reported a left crosswind of about 90 degrees at 7 to 10 knots. The pilot had received his private pilot certificate 48 days prior to the accident. His total flight experience was 98 hours with 96 hours in make and model, including 26 hours as pilot-in-command (PIC). He had logged 36 hours in the preceding 90 days, all in make and model, including 20 hours as PIC. The landing performance chart indicated the airplane would required 1,432 feet to clear a 50 foot obstacle, and stop on the runway. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2002_NYC02LA052.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 ↗