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 12, 2002 · Cessna 172RG · N888RG

Rochester, NY

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
August 12, 2002
Injury Outcomes
No injuries (1 uninjured)
Location
Rochester, NY
Aircraft
Cessna 172RG
Tail Number
N888RG
Injuries
None
Aircraft Damage
Substantial
NTSB Number
NYC02LA161

The pilot departed and flew directly to his first destination. During the flight, he suspected that the airspeed indicator was indicating low for his altitude and power setting, but was not convinced there was a real problem. The pilot landed, and then immediately took off again. Once airborne, he decided to proceed back to his original departure airport. After completing the en route portion of the flight, the pilot was cleared to land on the main runway, which made him feel like he had to expedite the approach and landing. During the approach, the descent rate and airspeed were higher than "warranted." The airplane touched down, bounced, and then touched down again. The nose of the airplane started to vibrate, and the pilot realized the airplane was damaged. Examination of the pitot system and airspeed indicator revealed that the indicator was reading within prescribed limits, but was "very" slow to respond to airspeed changes. In addition, the system had numerous leaks that were not related to the accident.

NTSB Probable Cause

The pilot's improper flare and recovery from a bounced landing. A factor in the accident was the slow response time of the airspeed indicator.

Full Narrative

On August 12, 2002, about 1045 eastern daylight time, a Cessna 172RG, N888RG, was substantially damaged during a hard landing at the Greater Rochester International Airport (ROC), Rochester, New York. The certificated commercial pilot was not injured. Visual meteorological conditions prevailed for the personal flight that departed the Ledgedale Airpark (7G0), Brockport, New York, destined for Rochester. A flight plan was not filed for the flight which was conducted under 14 CFR Part 91. According to the pilot, he departed Rochester about 1000 and flew directly to Brockport. During the flight, he suspected that the airspeed indicator was indicating low for his altitude and power setting, but was not convinced there was a real problem. The pilot landed at Brockport, and then immediately took off again. Once airborne, he decided not to continue the flight as planned, and proceeded back to Rochester. Once in the terminal area at Rochester, the pilot was cleared by the tower controller to land on runway 22. Because runway 22 was the main runway at Rochester, the pilot felt he needed to expedite the landing. The pilot added it "was not due to the controllers or the tower, as they treated me with total professionalism." The pilot characterized the descent rate and airspeed during the approach as higher than "warranted." The airplane touched down, bounced, and then touched down again. The nose of the airplane started to vibrate, and the pilot realized the airplane was damaged. As the airplane cleared the runway, the tower controller radioed the pilot and asked if he was alright, and if he needed assistance. The pilot said yes to both, and shut down the engine. The pilot added that he should not have allowed himself to feel rushed, and that it was a self-induced feeling of urgency. He also felt that he should have initiated a go-around after the first bounce. Examination of the pitot system and airspeed indicator revealed that the indicator was reading within prescribed limits, but was "very" slow to respond to airspeed changes. In addition, the system had numerous leaks, and the technicians who performed the examination felt the leaks were not related to the accident.

Flight

Event TypeAccident
Event Time10:45 EDT
Nearest AirportGreater Rochester Internationa (0nm)
Runway22
Runway Length8001 ft
Runway Width150 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172RG
Tail NumberN888RG
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-360-F1A6 · Reciprocating · 180
Seats4

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 38 · Second Class · None

Conditions

ConditionsVMC
LightDaylight
Wind210° @ 4 kt
Visibility6 sm
CeilingBroken clouds 20000 ft
Temperature / Dew Point66 F
Altimeter30.04 inHg
Observation Time14:54
Weather SourceWFAC

Appendix: Source Data