Casualties unknown

Student Pilot Strikes Runway During Supervised Solo Landing (N734AT)

Easton, MD, US

On February 12, 2004, a Cessna 172N (registration N734AT) was involved in an aviation accident near Easton, MD. Investigators recorded the probable cause as: The student pilot's failure to maintain proper airspeed and attitude during the landing flare, resulting in a high flare and subsequent propeller strike with the runway. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive; 1 related events involving the same aircraft type or operator are linked below.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 2026-06-21Data APIEditorial standards

A student pilot conducting supervised solo flights accidentally struck the runway with the propeller during landing, causing damage to the aircraft as it appeared to flare too high and porpoise.

What happened

The incident occurred while a student pilot was engaged in supervised solo flight operations. During the landing phase of one such flight, the pilot inadvertently allowed the aircraft's propeller to make contact with the runway surface. Following this impact, the airplane was taxied away from the active runway area and secured at the ramp.

According to the flight instructor who was supervising these solo flights, the aircraft exhibited unusual behavior during the approach. The instructor observed that the pilot flared the airplane too high above the runway threshold. This excessive altitude caused the aircraft to begin porpoising, a oscillating motion where the plane repeatedly rises and falls toward the runway surface, ultimately leading to the propeller strike.

The investigation

The flight instructor provided a firsthand account of the landing sequence. His observations focused on the pilot's control inputs during the final approach and flare. The instructor noted that the high flare was the precursor to the porpoising motion that resulted in the ground contact.

Probable cause

The student pilot's failure to maintain proper airspeed and attitude during the landing flare, resulting in a high flare and subsequent propeller strike with the runway.

All Cessna 172 accidents →

Frequently asked questions

What happened in the 12 Feb 2004 Cessna 172N accident near Easton, MD?

A student pilot conducting supervised solo flights accidentally struck the runway with the propeller during landing, causing damage to the aircraft as it appeared to flare too high and porpoise.

What aircraft was involved and where did it happen?

The accident on 12 Feb 2004 involved a Cessna 172N, registration N734AT, at Easton, MD.

What was the probable cause of the accident?

The student pilot's failure to maintain proper airspeed and attitude during the landing flare, resulting in a high flare and subsequent propeller strike with the runway.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20040310X00305. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.