NTSB CAROL · Event
Event NYC02LA080
Aircraft involved
Probable cause & findings
The student pilot's failure to maintain runway alignment during landing. A factor in the accident was the winds.
Factual narrative
On April 2, 2002, about 1630 eastern standard time, a Piper PA-28-151, N44636, was substantially damaged while landing at the Allaire Airport (BLM), Belmar/Farmingdale, New Jersey. The student pilot was not injured. Visual meteorological conditions prevailed for the instructional flight that departed Martin State Airport (MTN), Baltimore, Maryland, destined for Belmar. A visual flight rules flight plan was filed, and the flight was conducted under 14 CFR Part 91. According to the pilot, he departed Allaire around 0915, and flew to Atlantic City International Airport (ACY), Atlantic City, New Jersey, where he did one landing. He then flew to Ocean City Municipal Airport (OXB), Ocean City, Maryland, and conducted another landing. After that, he did a landing at Millville Municipal Airport (MIV), Millville, New Jersey. The pilot then flew to Martin State where he conducted a couple of landings before parking the airplane for a few hours. After the break, the pilot returned to the airplane, and departed for the Quakertown Airport (UKT), Quakertown, Pennsylvania. Near Quakertown, the pilot decided not to land because of winds, so he continued on to Allaire. Approaching Allaire, the pilot entered a left downwind for runway 14 via a 45-degree entry. He announced the entry and being established on the downwind at 1,000 feet msl. When he was abeam the approach end of the runway, he reduced engine power to 1,500 rpm, and when the airspeed entered the "white arc," he selected one notch of flaps, and announced turning base leg. On base, the pilot selected another notch of flaps, and then turned final. While on final, the pilot did not like his ground track. He also felt that the airplane behind him was too close, so he executed a go-around. The engine responded and the pilot retracted the flaps. The pilot turned crosswind about 700 feet msl, and then downwind at 1,000 feet msl. He announced both the crosswind and downwind turns. Once again, he was abeam the approach end of the runway. He reduced engine rpm to 1,500, and when the airspeed entered the "white arc," he selected one notch of flaps. The pilot turned base, announced his intentions, selected another notch of flaps, and slowed the airplane to 75 knots. The pilot turned final, announcing the turn, and selected full flaps for landing. While on final, the pilot maintained 65 knots of airspeed, and crabbed the airplane into the wind to maintain a proper ground track to the runway. On short final, the pilot applied left rudder to align the airplane with the runway. He flared the airplane, causing it to float for a moment before touching down on the centerline, about 500 feet from the approach end. Shortly afterwards, the airplane drifted off the centerline to the left, and exited the runway. The left main landing gear was sheared off, and the airplane came to a stop. The pilot secured the engine and exited the airplane to move some debris away from the runway. Winds recorded at Allaire about 5 minutes after the accident were from 180 degrees at 11 knots, gusting to 18 knots. After completing several solo cross-country flights during the day, the student pilot was preparing to land at his home airport. During the student's first landing attempt, he executed a go-around because he did not like his ground track, and felt that an airplane following him in the traffic pattern was too close. On the student's second attempt, he turned base leg and then final. On final, he configured the airplane with full flaps, slowed to approximately 65 knots of airspeed, and crabbed the airplane into the wind. On short final, the pilot applied left rudder to align the airplane with runway 14. When he flared the airplane, it floated for a moment before touching down on the centerline, about 500 feet from the approach end. Shortly afterwards, the airplane drifted off the centerline to the left, and exited the runway. The winds recorded at the airport were from 180 degrees at 11 knots, gusting to 18 knots. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2002_NYC02LA080.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 ↗