Skip to content

Atlas / NTSB / MIA07CA008

NTSB CAROL · Event

Event MIA07CA008

2006-10-21 Ormond Beach, Florida, United States Airport · KOMN None 1 aircraft Status: Completed

Registry · N401ER

FAA Aircraft Registry record.

Make / Model

CESSNA 172S

Year of manufacture

2020

Engine

LYCOMING IO-360-L2A (180 hp)

Seats / Engines

4 seats · 1 engine

Last airworthiness date

20200901

ADS-B equipped

Yes — Mode-S A4B0CC

Registrant of record

EMBRY-RIDDLE AERONAUTICAL UNIVERSITY INC

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The failure of the student pilot to initiate a recovery from the bounced landing resulting in a hard landing.

Factual narrative

On October 21, 2006, about 1315 eastern daylight time, a Cessna 172S, N401ER, registered to Wells Fargo Bank Northwest NA Trustee, operated by Embry-Riddle Aeronautical University, bounced during landing at the Ormond Beach Municipal Airport, Ormond Beach, Florida. Visual meteorological conditions prevailed at the time and no flight plan was filed for the 14 CFR Part 91 instructional flight from Daytona Beach International Airport, Daytona Beach, Florida, to Ormond Beach Municipal Airport. The airplane was substantially damaged and the student pilot, the sole occupant, was not injured. The flight originated about 1245, from Daytona Beach International Airport. The pilot stated that the flight proceeded to the destination airport and was cleared by air traffic control to land on runway 8. The flight turned from the downwind leg onto base, then onto final approach and with 30-degrees of flaps extended, attempted to maintain 61 knots for the practice short field landing. She began to flare but felt the main landing gear wheels "skid against the pavement" and the airplane then became airborne. She maintained the aft elevator input and again felt the main landing gear wheels skid on the runway and the airplane became airborne again. After the third touchdown the airplane remained on the runway and she taxied to the ramp. According to the NTSB "Pilot/Operator Aircraft Accident/Incident Report" form, a witness reported seeing a flat approach, contact with the runway, then the airplane porpoised. The recommendations section of the report indicates that a go-around should have been performed upon first indication of a faulty approach. The pilot stated that the flight proceeded to the destination airport and was cleared by air traffic control to land on runway 8. The flight turned from the downwind leg onto base, then onto final approach and with 30-degrees of flaps extended, attempted to maintain 61 knots for the practice short field landing. She began to flare but felt the main landing gear wheels "skid against the pavement" and the airplane then became airborne. She maintained the aft elevator input and again felt the main landing gear wheels skid on the runway and the airplane became airborne again. After the third touchdown the airplane remained on the runway and she taxied to the ramp. According to the NTSB "Pilot/Operator Aircraft Accident/Incident Report" form, witness reported seeing a flat approach, contact with the runway, then the airplane porpoised. The recommendations section of the report indicates that a go-around should have been performed upon first indication of a faulty approach. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_2006_MIA07CA008.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 ↗