# NTSB NYC01LA219: Cessna 172M, N9869Q, Danbury, CT, August 26, 2001 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: August 26, 2001, 11:02 local (15:02 UTC) - Place: Danbury, CT - Coordinates: 41.400226, -73.470726 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=41.4002&lon=-73.4707&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report November 28, 2001 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 53125 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC01LA219 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/53125/pdf - Page: https://openairdocs.org/ntsb/NYC01LA219 ## Probable cause An inoperative airspeed indicator and the pilot's improper recovery from the bounced landing. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, landing - flare/touchdown - flight/nav instruments,airspeed indicator - inoperative (cause) - recovery from bounced landing - improper, pilot in command (cause) ## 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](https://openairdocs.org/aircraft/N9869Q), registered now, S/N 17265813, built 1975 (OpenAirDocs) - Reported make and model: Cessna 172M - Registry model: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17265813 - Airframe hours: 3243.5 - Engines: 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 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 51; injuries: none; 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 (OpenAirDocs). - [Accident 20010826026159A](https://openairdocs.org/incident/20010826026159A), Aug 26, 2001: Cessna 172M, Danbury, CT, No damage. (.19)On August 26, 2001, at 1102 eastern daylight time, a Cessna 172M, N98 69Q, was substantially damage while landing at Danbury Municipal Airport, Danbury,… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.