NTSB CAROL · Event
Event NYC01LA219
Registry · N9869Q
FAA Aircraft Registry record.
Make / Model
CESSNA 172M
Year of manufacture
1975 · 26 years old at event
Engine
LYCOMING 0-320 SERIES (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
20040604
ADS-B equipped
Yes — Mode-S ADC510
Registrant of record
FORT SMITH FLYING CLUB INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
An inoperative airspeed indicator and the pilot's improper recovery from the bounced landing.
Factual 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. 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2001_NYC01LA219.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.