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

August 26, 2001 · Cessna 172M · N9869Q

Danbury, CT

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
August 26, 2001
Injury Outcomes
No injuries (3 uninjured)
Location
Danbury, CT
Aircraft
Cessna 172M
Tail Number
N9869Q
Operator
North American Aviation
Injuries
None
Aircraft Damage
Substantial
NTSB Number
NYC01LA219

The pilot reported that the airspeed indicator was operative during the takeoff roll. However, after becoming airborne, it returned to zero, and stayed there. The pilot remained in the traffic pattern and returned for a landing. Full flaps were added prior to touchdown. Upon initial touchdown, the airplane bounced. The pilot added power, and when he removed the power, the airplane bounced again. The pilot reported that the airplane bounced at least twice prior to departing the right side of the runway. Witnesses reported it bounced five or six times. The nose landing gear tire was blown, the firewall was wrinkled, and the supporting structure behind the firewall was bent.

NTSB Probable Cause

An inoperative airspeed indicator and the pilot's improper recovery from the bounced landing.

Full Narrative

On August 26, 2001, at 1102 eastern daylight time, a Cessna 172M, N9869Q, was substantially damage while landing at Danbury Municipal Airport, Danbury, Connecticut. The certificated private pilot and two passengers were not injured. Visual meteorological conditions prevailed for the local flight. No flight plan had been filed for the personal flight that was conducted under 14 CFR Part 91. The pilot stated: "After liftoff, during my scan, I noticed the airspeed read zero...I notified the tower that I was entering the pattern to land and that my airspeed indicator was inop. I slowed the aircraft to 1,800 RPM and lowered 10 degrees flaps. I slowed the aircraft to 1,000 RPM on final. Once I cleared Sears (about 500 feet from end of runway), I applied full flaps and landed. I bounced, added power and removed power to recover. I bounced again. I added a little power and landed; at this point I felt the front tire was flat and I swerved to the right off the runway. Once I hit the muddy turf, the aircraft stopped abruptly...." In a follow-up telephone interview, the pilot reported that the airspeed indicator worked during the acceleration on the runway. It was after the airplane was airborne that he noticed it had returned to zero. The pilot further reported that he had initially requested the longer runway, but was advised by the control tower that there was a crosswind on that runway and he did not pursue it further. According to an inspector from the Federal Aviation Administration (FAA), the pilot was landing on runway 17. The airplane was observed to bounced about five or six times, and then came to rest on the right side of the runway. The inspector further stated: "...When pressure was applied to the pitot tube, the airspeed indicator indicated airspeed." In a follow-up telephone interview, the FAA inspector reported that the nose landing gear strut was bent, the nose tire was blown, the firewall was wrinkled, and supporting structure behind the firewall was bent. The pilot's total flight experience was 229.3 hours with 170 hours as pilot-in-command. His total flight experience in the Cessna 172 was 5 hours. In the preceding 12 months, 90 days, and 30 days, the pilot had flown 8.2 hours, 1.2 hours, and 0 hours respectively. According to data from the FAA, runway 17 was 3,135 feet long and 100 feet wide. The 1053 weather observation at Danbury, reported the winds were from 170 degrees at 6 knots.

Flight

Event TypeAccident
Event Time11:02 EDT
Nearest AirportDanbury Municipal Airport (0nm N)
Runway17
Runway Length3135 ft
Runway Width100 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172M
Tail NumberN9869Q
Aircraft CategoryAir
DamageSubstantial
OperatorNorth American Aviation
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-360-A4M · Reciprocating · 180
Seats4

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 51 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind170° @ 6 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point55
Altimeter30.12 inHg
Observation Time14:53
Weather SourceWFAC

Appendix: Source Data