# Incident 20160325024439I: Cessna R172K, March 25, 2016

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: March 25, 2016, 09:58 local time
- Airport: Ernest A. Love Field
- Damage: No damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Aircraft: N3285V, registered now (https://openairdocs.org/aircraft/N3285V) (OpenAirDocs)
- Registry model: Cessna R172K (registry code 2072431, https://openairdocs.org/model/cessna-r172k) (OpenAirDocs)
- Registry engine: Continental IO-360 series (registry code 17025, https://openairdocs.org/engine/continental-io-360-series) (OpenAirDocs)
- Reported make and model: CESSNA R172K
- Reported engine: CONT MOTOR IO-360 SER
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 67 total, 50 in this make and model, 5 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160325024439I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

STUDENT PILOT WAS FLYING SOLO WHILE CONDUCTING PRACTICE LANDINGS ON RUNWAY 3R AT PRESCOTT AIRPORT.

WINDS WERE REPORTED CROSSWAYS TO ACTIVE RUNWAY (300 DEGREES @ 12 KTS) AND WERE GUSTY. AFTER LANDING, DURING ROLL OUT, THE AIRCRAFT ENCOUNTERED A WIND GUST WHICH CAUSED THE AIRCRAFT TO WEATHERVANE. IT DRIFTED TO THE LEFT SIDE OF THE RUNWAY AND GOT THE MAIN WHEEL OFF THE RUNWAY. AIRCRAFT CAME TO A HALT AND THE PILOT TOOK A MOMENT TO CALM HIMSELF. TOWER ASKED IF HE WAS OK OR IF HE NEEDED ASSISTANCE. HE INDICATED THINGS WERE FINE & THE AIRCRAFT WAS OK. THE TOWER CLEARED HIM TO TAXI OFF THE RUNWAY. HE APPLIED POWER AND TAXIED THRU DIRT TO THE TAXIWAY AHEAD. AIRCRAFT WAS ABLE TO TAXI TO RAMP WITH NO FURTHER INCIDENT.

INSPECTION OF AIRCRAFT WAS CONDUCTED. THERE WERE NO INDICATIONS OF DAMAGE TO THE AIRCRAFT.

THE PILOT DID NOTE THAT HE HAD HEARD TWO OTHER AIRCRAFT IN THE PATTERN GO-AROUND PRIOR TO HIS LANDING. THOSE PILOTS HAD MADE COMMENTS TO THE TOWER ABOUT THE CROSSWIND AND A WIND SHEAR NEAR THE RUNWAY. THEY HAD REQUESTED A CHANGE OF RUNWAY TO RWY 30 TO ALIGN BETTER WITH THE WIND. ACCORDING TO THIS PILOT THE TOWER HAD RESPONDED BY SAYING THEY WERE STAYING WITH RWY 3 AS THE ACTIVE RUNWAY.

IT SHOULD BE NOTED: THE TOWER IMMEDIATELY CHANGED TRAFFIC PATTERN TO RWY 30 FOR ALL OTHER AIRCRAFT IN THE PATTERN AFTER THEY CLEARED THIS AIRCRAFT FROM RWY 3.

NO TOWER TAPES WERE AVAILABLE AT THE TIME OF THIS INVESTIGATION TO CONFIRM THE TOWER COMMUNICATIONS.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.