# Incident 20160809023149I: Aero Commander 112, Reno, NV, August 9, 2016

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 9, 2016, 18:42 local time
- Place: Reno, NV
- Airport: Reno-Stead
- Damage: Minor damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 39.6682° N, 119.8764° W: Placed by OpenAirDocs at RENO/STEAD (RTS), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.6682&lon=-119.8764&mi=10
- Aircraft: N112RC, registered now (https://openairdocs.org/aircraft/N112RC) (OpenAirDocs)
- Registry model: Aero Commander 112 (registry code 0144701, https://openairdocs.org/model/aero-commander-112) (OpenAirDocs)
- Registry engine: Continental IO-360 series (registry code 17025, https://openairdocs.org/engine/continental-io-360-series) (OpenAirDocs)
- Reported make and model: AERO COMMANDER 112
- Reported engine: LYCOMING IO-540-G1B5
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 204 total, 54 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/20160809023149I

## Narrative

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

THE COMMANDER HAD BEEN OUT OF SERVICE FOR APPROXIMATELY 2 MONTHS FOR ITS FIRST ANNUAL FOR THE OWNER (EEI; A COMPANY THAT ^PRIVACY DATA OMITTED^ FOUNDED AND RUNS). ^PRIVACY DATA OMITTED^ WAS PLANNING A FLIGHT TO SACRAMENTO THE NEXT MORNING (MONDAY, AUGUST 10).

BECAUSE THE PLANE HAD NOT FLOWN SINCE THE ANNUAL, PILOT DECIDED SOME TO/LANDING PRACTICE WOULD BE PRUDENT.

THE PILOT PRE-FLIGHTED, FUELED, AND COMMENCED SOME LANDINGS AT HOME BASE KRTS. THE FIRST LANDING WAS ON RUNWAY 32 WITHOUT INCIDENT. THE WIND CHANGED AND THE SECOND LANDING ON RUNWAY 26 WAS IN PROGRESS. THE PILOT WAS DISTRACTED BY SUN GLARE (IN LOWER QUADRANT AT THAT TIME) AND WAS FATIGUED AFTER A LONG DAY. AFTER SETTING AND MAINTAINING AN EXCELLENT STABLE LANDING CONFIGURATION THE PLANE SETTLED ON THE RUNWAY AND SKIDDED TO A STOP; PILOT THOUGHT A WHEEL HAD BROKEN, PLANE SETTLED ON THE CENTER OF THE RUNWAY, GRINDING DOWN THE STEPS AND DESTROYING THE PROP. NO OTHER SIGNIFICANT DAMAGE. THE PLANE WAS LIFTED BY THE AIRPORT AUTHORITY, LANDING GEAR DROPPED, AND TOWED TO THE FBO (AVIATION CLASSICS) FOR INSPECTION AND EVALUATION.

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.