NTSB CAROL · Event
Event NYC98LA190
Aircraft involved
Probable cause & findings
The pilot's improper recovery from a bounced landing. Contributing factors were the pilot's lack of a single engine experience/certification. Also a factor was the flying club's inadequate oversight of pilot qualifications.
Factual narrative
On September 19, 1998, at 1519 eastern daylight time, a Cessna 172, N1729V, owned and operated by the Oxford Flying Club, was substantially damage after it departed the runway environment while landing at the Minute Man Airfield, Stow, Massachusetts. The certificated airline transport pilot was not injured, and visual meteorological conditions prevailed for the personal flight being conducted under 14 CFR Part 91. No flight plan was filed and the flight departed Waterbury-Oxford Airport, Oxford, Connecticut, about 1400. The pilot stated that the purpose of the flight was to familiarize himself with the Minute Man Airfield and to assess transportation from the airport to the hotel for a future business meeting. According to the pilot, he checked weather and then departed Oxford, Connecticut, for Stow. While approaching the airport, the pilot tried four times, but was unable to contact anyone on the Unicom frequency to obtain the winds and the preferred runway. He also checked for other aircraft in the traffic pattern, but received no response. Unable to contact anyone by radio, the pilot tried to identify the winds by over flying the airport. This also was unsuccessful, so the pilot elected to make left traffic for Runway 3. The pilot stated that the first indication of trouble came when he flared the airplane and it started to float down the runway. The airplane bounced three times, and after the third bounce, he drove the airplane "hard" onto the runway and applied maximum braking. At that point he realized there was insufficient runway to stop, but elected not to execute a go-around because of limited runway remaining, and the fact the airport was set in a valley surrounded by trees. The airplane departed the departure end of the runway, sheared off the nose wheel and nosed over. After exiting the airplane the pilot estimated the winds to be from 210 degrees magnetic at 10 knots. The pilot stated that he had not identified the windsock until after the accident. After the accident, he was informed by another pilot that the windsock was not visible while maintaining traffic pattern altitude, and that he needed to be 400 feet below the traffic pattern to see it. The pilot added that the majority of his 25,000 hours of flight time was accumulated in transport category aircraft, and that he just recently started flying general aviation aircraft. He further stated he had about 5 hours in the Cessna 172, and about 20 hours in the PA-28-180. On the NTSB form 6120.1/2, the pilot did not check airplane single engine land as a rating, and a review of Federal Aviation Administration (FAA) record's also revealed that the pilot didn't have a single land rating. According to the operator's maintenance officer, the club was not aware the pilot did not possess a single engine land rating. The maintenance officer stated that when the pilot joined the flying club, everyone was so impressed with his flight experience, and the fact he was a retired airline pilot, no one asked. The maintenance officer added that the club did give the pilot a proficiency ride before allowing him to rent airplanes, and they had all of their members bring in their FAA Certificates and Medicals for verification after the accident. The Safety Board made several attempts, without success, to contact the pilot once it was determined he did not poses a single engine land rating. At his destination airport the pilot was unable to reach anyone by radio or verify the winds visually, so he made left traffic for Runway 3. When the pilot flared the airplane it floated down the runway. The pilot then bounced the airplane three times. After the third bounce he drove the airplane hard onto the runway and applied maximum braking. Unable to stop, the airplane then departed the departure end of the runway, shearing the nose gear and ultimately nosing over. The pilot had over 25,000 hours of flight experience, but only 25 hours in small general aviation airplanes. He also did not have a single engine land rating nor was he operating the airplane as a student pilot. When the pilot approached the flying club to become a member no one from the club asked him if he had an airplane single engine land rating because of his airline pilot back ground. It was just assumed. The club did require the pilot to take a proficiency ride before he was allowed to rent from them. The pilot estimated the winds to be from 210 degrees magnetic at 10 knots at the time of the accident. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1998_NYC98LA190.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, maintenance). 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 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.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- 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.
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- 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…
Browse the full corpus — academia portal ↗