OpenAirDocs.org

20160809023149I

Incident · Minor damage
Open the Markdown

FAA incident report · Aero Commander 112 · Reno, NV · August 9, 2016

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
August 9, 2016 · 18:42 local
Place
Reno, NV
Airport
Reno-Stead
Phase of flight
Landing: Approach
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N112RC
Reported as
Aero Commander 112
Reported engine
Lycoming IO-540-G1B5
People aboard
1
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Private pilot
Pilot’s flight hours
204 total54 in this make and model5 in the last 90 days
N112RCRegistered now · Aero Commander 112S/N 79 · Built 1973Airframe modelAero Commander 112Engine modelContinental IO-360 seriesReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

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.

As the FAA filed it

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.