Skip to content

Atlas / NTSB / NYC01LA163

NTSB CAROL · Event

Event NYC01LA163

2001-07-02 Stevensville, Maryland, United States Airport · W29 None 1 aircraft Status: Completed

Registry · N54576

FAA Aircraft Registry record.

Make / Model

CESSNA 172P

Engine

LYCOMING 0-320 SERIES (180 hp)

Seats / Engines

4 seats · 1 engine

Last airworthiness date

19860103

ADS-B equipped

Yes — Mode-S A6EDEB

Registrant of record

RICK AVIATION INC

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's improper flare and his improper recovery from a bounced landing.

Factual narrative

On July 2, 2001, about 1710 eastern daylight time, a Cessna 172P, N54576, was substantially damaged while landing at the Bay Bridge Airport, Stevensville, Maryland. The certificated private pilot and passenger were not injured. Visual meteorological conditions prevailed and no flight plan was filed for the local flight conducted under 14 CFR Part 91. According to the pilot, as he approached the airport, he was advised that the winds were from 060 degrees at 5 knots. The pilot entered the final approach leg to runway 11, a 2,903 foot long, 60 foot wide, asphalt runway, "above glide path and remained too high throughout final." With a view of ample runway ahead, the pilot "decided to continue with the landing rather than go around." The airplane touched down, bounced back into the air, and "ballooned excessively." The pilot added power to recover from the bounced landing, touched down a second time, and the airplane began to porpoise. The nose wheel tire then ruptured and the propeller struck the asphalt. The airplane came to rest upright. According to the Federal Aviation Administration Airplane Flying Handbook, the proper technique for recovery from "excessive" "Floating During Roundout", and "Ballooning During Roundout," was "EXECUTE A GO-AROUND IMMEDIATELY." The winds reported by a nearby airport, about the time of the accident, were calm. While on final approach for the runway, the airplane was "above glide path and remained too high throughout final." With a view of ample runway ahead, the pilot "decided to continue with the landing rather than go around." The airplane touched down, bounced back into the air, and "ballooned excessively." The pilot added power to recover from the bounced landing, touched down a second time, and the airplane began to porpoise. The nose wheel tire then ruptured and the propeller struck the asphalt. According to the Federal Aviation Administration Airplane Flying Handbook, the proper technique for recovery from "excessive" "Floating During Roundout", and "Ballooning During Roundout," was "EXECUTE A GO-AROUND IMMEDIATELY." Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_2001_NYC01LA163.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗