Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

September 19, 1998 · Cessna 172 · N1729V

Stow, MA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
September 19, 1998
Injury Outcomes
No injuries (1 uninjured)
Location
Stow, MA
Aircraft
Cessna 172
Tail Number
N1729V
Injuries
None
Aircraft Damage
Substantial
NTSB Number
NYC98LA190

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 background. 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.

NTSB Probable Cause

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.

Full 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.

Flight

Event TypeAccident
Event Time15:19 EDT
Nearest AirportMinute Man Air Field (0nm)
Runway3
Runway Length2770 ft
Runway Width48 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172
Tail NumberN1729V
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320E2D · Reciprocating · 150
Seats4

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 60 · First Class

Conditions

ConditionsVMC
LightDaylight
Wind200° @ 8 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point66 F / 63 F
Altimeter29.00 inHg
Observation Time18:56
Weather SourceWFAC

Appendix: Source Data