NYC01LA219

NTSB accident investigation · Cessna 172M · Danbury, CT · August 26, 2001

Accident · No injuriesLimited investigationFinal report
Date
August 26, 2001, 11:02 local (15:02 UTC)
Place
Danbury, CT
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N9869QCessna 172M
Weather
Visual (VMC) · Day
Status
Completed · report November 28, 2001
Report
Approved by Office Director
Parties
Federal Aviation Administration
FAA report
20010826026159A
Case key
53125

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

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

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Loss of control - on ground/waterLanding - flare/touchdown
Flight/nav instruments,airspeed indicator - inoperativeCause
Recovery from bounced landing - improperPilot in commandCause

Analysis

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.

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.

Aircraft

Registration
N9869Q
Reported as
Cessna 172M
Category
Airplane
Serial number
17265813
Airframe hours
3,243.5
Engine
Lycoming O-360-A4M, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
North American Aviation Inc.
Registered owner
David Enterprises Inc.
Airworthiness certificate
Standard, Utility; Standard, Normal
Last inspection
100 hour · August 24, 2001 · 3.9 hours before
Departed
DXR · Danbury, CT
Destination
DXR · Danbury, CT
Airport
DXR · Danbury Municipal Airport, runway 17, 3,135 × 100 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
51
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Valid Medical--no waivers/lim.
Last flight review
August 1, 1999
Seat
Left
Flight hours
229 total · 5 in this make and model · 170 as pilot in command · 1 in the last 90 days

Weather

Conditions
Visual (VMC) · Day
Wind
170° at 6 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
72 °F, dew point 55 °F
Altimeter
30.12 inHg
Observed at
DXR

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.