# Incident 20110211003489I: Cessna 172N, Tucson, AZ, February 11, 2011

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 11, 2011, 11:36 local time
- Place: Tucson, AZ
- Damage: No damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 32.2217° N, 110.9265° W: Placed by OpenAirDocs: center of Tucson, AZ, within about 9 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.2217&lon=-110.9265&mi=10
- Aircraft: N75845, registered now (https://openairdocs.org/aircraft/N75845) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 68 total, 60 in this make and model, 4 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20110211003489I

## Narrative

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

GUSTY WINDS PREVAILED AT THE TIME THE AIRMAN WAS CONDUCTING TOUCH AND GO'S AT KRYN AIRPORT.DURING A TOUCH AND GO ON RWY 6R, THE AIRCRAFT EXITED THE RUNWAY ONTO THE ADJACENT GRASS AREA.NO DAMAGE WAS DONE TO THE AIRCRAFTA 44709 RE-EXAM WILL BE INITIATED

## Other reports on N75845 (2)

Matched to the same aircraft by N-number and date.

- [Incident 19800827065709I](https://openairdocs.org/incident/19800827065709I), Aug 27, 1980: Cessna 172N (N75845), Rochester, NY. Flight terminated, returned due to rough running engine. Found a bent intake push rod.
- [Incident 19780528040599I](https://openairdocs.org/incident/19780528040599I), May 28, 1978: Cessna 172 (N75845), White Plains, NY. Pilot was unable to maintain VFR after takeoff. Elected asr approach. Missed, then proceeded to VFR airport.

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.