OpenAirDocs.org

20130207007029I

Incident · No damage
Open the Markdown

FAA incident report · Cessna 172F · Arlington, TX · February 7, 2013

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
February 7, 2013 · 15:54 local
Place
Arlington, TX
Phase of flight
Landing: Rollout
Operating rules
General operating rules (Part 91)
Damage
No damage
Aircraft
N7920U
Reported as
Cessna 172F
Reported engine
Continental 0-300 series
People aboard
1
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Private pilot
Pilot’s flight hours
360 total360 in this make and model21 in the last 90 days
N7920URegistered now · Cessna 172FS/N 17251920 · Built 1964Airframe modelCessna 172FEngine modelContinental 0-300 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.

Pilot was returning to kgky (home base) from kslr (sulphur springs, TX) and was cleared to land on runway 34. Winds were (roughly) 280º-290º@ ~13 g~23. Pilot was on a steady final, crabbed for the wind, with everything in a normal landing configuration (flaps were between 20º-30º?(the aircraft has a 40º flap setting available). The tower updated winds on base and one more time on final per pilot request. The pilot had landed in similar wind conditions many times before. He did not think it would be an issue. No other traffic was present either in the air or on the ground. After the mains had touched down (now slightly right of center) a gust came from the left and pushed the aircraft to the right (east). The aircraft was slow. The pilot ran out of roll control, and was unable to correct back onto the runway. The pilot had initially added full power to go around, but since he was drifting toward the t-hangars, the pilot reduced power to idle and concentrated on maintaining control. The pilot felt nothing was wrong with the aircraft and chose to maintain a taxi speed to get out of the grass (mud?) And onto the parallel taxiway ?a?

As the FAA filed it

PILOT WAS RETURNING TO KGKY (HOME BASE) FROM KSLR (SULPHUR SPRINGS, TX) AND WAS CLEARED TO LAND ON RUNWAY 34. WINDS WERE (ROUGHLY) 280º-290º@ ~13 G~23. PILOT WAS ON A STEADY FINAL, CRABBED FOR THE WIND, WITH EVERYTHING IN A NORMAL LANDING CONFIGURATION (FLAPS WERE BETWEEN 20º-30º?(THE AIRCRAFT HAS A 40º FLAP SETTING AVAILABLE). THE TOWER UPDATED WINDS ON BASE AND ONE MORE TIME ON FINAL PER PILOT REQUEST. THE PILOT HAD LANDED IN SIMILAR WIND CONDITIONS MANY TIMES BEFORE. HE DID NOT THINK IT WOULD BE AN ISSUE. NO OTHER TRAFFIC WAS PRESENT EITHER IN THE AIR OR ON THE GROUND. AFTER THE MAINS HAD TOUCHED DOWN (NOW SLIGHTLY RIGHT OF CENTER) A GUST CAME FROM THE LEFT AND PUSHED THE AIRCRAFT TO THE RIGHT (EAST). THE AIRCRAFT WAS SLOW. THE PILOT RAN OUT OF ROLL CONTROL, AND WAS UNABLE TO CORRECT BACK ONTO THE RUNWAY. THE PILOT HAD INITIALLY ADDED FULL POWER TO GO AROUND, BUT SINCE HE WAS DRIFTING TOWARD THE T-HANGARS, THE PILOT REDUCED POWER TO IDLE AND CONCENTRATED ON MAINTAINING CONTROL. THE PILOT FELT NOTHING WAS WRONG WITH THE AIRCRAFT AND CHOSE TO MAINTAIN A TAXI SPEED TO GET OUT OF THE GRASS (MUD?) AND ONTO THE PARALLEL TAXIWAY ?A?