No fatalities

Student Pilot Hard Landing Damages Firewall During Solo Cross-Country Flight (N75816)

Winslow, AZ, US

On November 9, 2003, a Cessna 172N (registration N75816) was involved in an aviation accident near Winslow, AZ. No fatalities were reported. Investigators recorded the probable cause as: The pilot's improper use of flight controls during landing, specifically pulling back on the yoke too aggressively after touchdown, which caused the aircraft to porpoise and strike the ground hard enough to damage the firewall. 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-19Data APIEditorial standards

A student pilot's solo cross-country flight ended in a hard landing that damaged the firewall. The pilot reported touching down on the main gear and pulling back fully, causing the aircraft to porpoise before striking the ground again.

What happened

During a solo cross-country flight, the airplane experienced a severe landing incident resulting in structural damage. The pilot executed the initial touchdown on the main landing gear but immediately pulled the control yoke into the full aft position. This input caused the aircraft to porpoise, leading to a subsequent hard landing that damaged the firewall. The pilot later noted that applying power earlier in the sequence might have prevented the accident.

The investigation

A review of the mechanical condition prior to the event revealed no preimpact malfunctions or failures with the airplane. The damage was consistent with the reported porpoising and hard landing dynamics.

Probable cause

The pilot's improper use of flight controls during landing, specifically pulling back on the yoke too aggressively after touchdown, which caused the aircraft to porpoise and strike the ground hard enough to damage the firewall.

All Cessna 172 accidents →

Frequently asked questions

What happened in the 9 Nov 2003 Cessna 172N accident near Winslow, AZ?

A student pilot's solo cross-country flight ended in a hard landing that damaged the firewall. The pilot reported touching down on the main gear and pulling back fully, causing the aircraft to porpoise before striking the ground again.

Were there any fatalities in the 9 Nov 2003 Cessna 172N accident?

No fatalities were recorded in this accident.

What aircraft was involved and where did it happen?

The accident on 9 Nov 2003 involved a Cessna 172N, registration N75816, at Winslow, AZ.

What was the probable cause of the accident?

The pilot's improper use of flight controls during landing, specifically pulling back on the yoke too aggressively after touchdown, which caused the aircraft to porpoise and strike the ground hard enough to damage the firewall.

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