No fatalities

Crosswind Landing Results in Runway Excursion and Ground Loop (N5535D)

Prescott, AZ, US

On July 25, 1999, a Cessna 172N (registration N5535D) was involved in an aviation accident near Prescott, AZ. No fatalities were reported. Investigators recorded the probable cause as: the student pilot's premature retraction of the flaps during an aborted landing and his failure to obtain/maintain adequate flying airspeed, which resulted in a stall/mush condition and the airplane settling back onto the ground. 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-07-04Data APIEditorial standards

During a crosswind landing, the aircraft was blown right, touched down left wing low, yawed left, and ran off the runway. The pilot initiated a go-around but lost flying speed, landed hard, bounced, and ground looped to a stop.

Event Summary

During a landing in crosswind conditions, the aircraft unexpectedly drifted toward the right side of the runway. At the time, the airplane was in a left wing low, forward slip configuration with full flaps and at a typical landing airspeed.

Sequence of Events

The left main landing gear touched down first, after which the aircraft yawed left and departed the side of the runway. The pilot reported that he had not applied rudder quickly enough to maintain runway alignment and decided to execute a go-around. He added power and raised the flaps, but once the airplane lifted off, he was unable to sustain adequate flying speed. Attempting to accelerate in ground effect, the aircraft landed hard off the runway surface and bounced. Feeling that control was lost, the pilot abruptly closed the throttle and applied the brakes. The airplane then ground looped to a stop in the grass area beside the runway.

Pilot Statement

The pilot acknowledged that his delayed rudder input contributed to the loss of directional control during the initial landing attempt. He further noted that during the go-around, his actions to add power and retract flaps were insufficient to maintain flying speed after becoming airborne.

Outcome

The aircraft came to rest after a ground loop in the grass alongside the runway. No further details about damages or injuries are provided.

All Cessna 172 accidents →

Frequently asked questions

What happened in the 25 Jul 1999 Cessna 172N accident near Prescott, AZ?

During a crosswind landing, the aircraft was blown right, touched down left wing low, yawed left, and ran off the runway. The pilot initiated a go-around but lost flying speed, landed hard, bounced, and ground looped to a stop.

Were there any fatalities in the 25 Jul 1999 Cessna 172N accident?

No fatalities were recorded in this accident.

What aircraft was involved and where did it happen?

The accident on 25 Jul 1999 involved a Cessna 172N, registration N5535D, at Prescott, AZ.

What was the probable cause of the accident?

the student pilot's premature retraction of the flaps during an aborted landing and his failure to obtain/maintain adequate flying airspeed, which resulted in a stall/mush condition and the airplane settling back onto the ground. The student pilot's failure to maintain directional control during the subsequent ground…

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