20160815017519I

Incident · Minor damage

FAA incident report · Cessna 172 · Perryville, MO · August 15, 2016

Date
August 15, 2016 · 16:00 local
Place
Perryville, MO
Phase of flight
Cruise/Level Flight
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N6096A
Reported as
Cessna 172
Reported engine
Continental Engine 0-300-A
People aboard
1
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Private pilot
Pilot’s flight hours
113 total45 in this make and model40 in the last 90 days

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.

Amended 2/13/2017 - corrected K02 Perryville MO. Airport information. The airport information was removed as the incident did not occur on an airport so the airport information should not have been listed.

Amended 1/18/2017 - corrected spelling of airmans first name from privacy data omitted.

On August 15, 2016, the pilot departed gatlinburg-pigeon forge airfield (gkt) in a Cessna 172 (N6069A) with a planned enroute to his home base in new century, Kansas (ixd).

The pilots first stop was metropolis, Illinois (M30) where the aircraft was refuled and the enroute weather was checked on his garmin pilot.

Departing (M30) and heading to (ixd) the pilot noticed a lower layer of clouds ahead and decided to look for an alternate airfield to land.

After checking the garmin pilot on his mobile device and searching for an airfield, the nearest one found was in Perryville, Missouri (K02), which was listed as 10 miles from his current position. Upon flying toward the (K02) airport the pilot noticed his GPS was actually ?frozen? And still showed him being 10 miles from the airport. After this discovery the pilot decided to circle and look for a field to land as the weather was deteriorating rapidly and lower clouds were all around him.

At this point in time the pilot felt like he got himself into an emergency situation and could not continue to safely search for the airport, as he was loosing VFR conditions the pilot decided to declare an emergency on 121.5 and make a precautionary landing at an alternate landing site.

The pilot flew toward a green field as a place to perform this emergency landing. After approching a field that looked safe for landing he started the landing procedure. During the final few feet from the ground he noticed there was cows in the field. As result of this the pilot aborted the landing climbed up again looking for another field to land.

After he identified another field that seem to be safe to perform another landing procedure, the pilot began the approach to land, the aircraft touched the ground normally on the main landing gear, however as the aircraft was rolling on the ground the pilot noticed a barb wire fence in front of the aircraft. At this point he stated the aircraft was too slow and close to the fence to perform a go-around procedure. As a result of this the aircraft nose gear struck the fence and skidded to one side then came to a full stop shortly after, collapsing the nose gear.

As the FAA filed it

AMENDED 2/13/2017 - CORRECTED K02 PERRYVILLE MO. AIRPORT INFORMATION. THE AIRPORT INFORMATION WAS REMOVED AS THE INCIDENT DID NOT OCCUR ON AN AIRPORT SO THE AIRPORT INFORMATION SHOULD NOT HAVE BEEN LISTED.

AMENDED 1/18/2017 - CORRECTED SPELLING OF AIRMANS FIRST NAME FROM ^PRIVACY DATA OMITTED^.

ON AUGUST 15, 2016, THE PILOT DEPARTED GATLINBURG-PIGEON FORGE AIRFIELD (GKT) IN A CESSNA 172 (N6069A) WITH A PLANNED ENROUTE TO HIS HOME BASE IN NEW CENTURY, KANSAS (IXD).

THE PILOTS FIRST STOP WAS METROPOLIS, ILLINOIS (M30) WHERE THE AIRCRAFT WAS REFULED AND THE ENROUTE WEATHER WAS CHECKED ON HIS GARMIN PILOT.

DEPARTING (M30) AND HEADING TO (IXD) THE PILOT NOTICED A LOWER LAYER OF CLOUDS AHEAD AND DECIDED TO LOOK FOR AN ALTERNATE AIRFIELD TO LAND.

AFTER CHECKING THE GARMIN PILOT ON HIS MOBILE DEVICE AND SEARCHING FOR AN AIRFIELD, THE NEAREST ONE FOUND WAS IN PERRYVILLE, MISSOURI (K02), WHICH WAS LISTED AS 10 MILES FROM HIS CURRENT POSITION. UPON FLYING TOWARD THE (K02) AIRPORT THE PILOT NOTICED HIS GPS WAS ACTUALLY ?FROZEN? AND STILL SHOWED HIM BEING 10 MILES FROM THE AIRPORT. AFTER THIS DISCOVERY THE PILOT DECIDED TO CIRCLE AND LOOK FOR A FIELD TO LAND AS THE WEATHER WAS DETERIORATING RAPIDLY AND LOWER CLOUDS WERE ALL AROUND HIM.

AT THIS POINT IN TIME THE PILOT FELT LIKE HE GOT HIMSELF INTO AN EMERGENCY SITUATION AND COULD NOT CONTINUE TO SAFELY SEARCH FOR THE AIRPORT, AS HE WAS LOOSING VFR CONDITIONS THE PILOT DECIDED TO DECLARE AN EMERGENCY ON 121.5 AND MAKE A PRECAUTIONARY LANDING AT AN ALTERNATE LANDING SITE.

THE PILOT FLEW TOWARD A GREEN FIELD AS A PLACE TO PERFORM THIS EMERGENCY LANDING. AFTER APPROCHING A FIELD THAT LOOKED SAFE FOR LANDING HE STARTED THE LANDING PROCEDURE. DURING THE FINAL FEW FEET FROM THE GROUND HE NOTICED THERE WAS COWS IN THE FIELD. AS RESULT OF THIS THE PILOT ABORTED THE LANDING CLIMBED UP AGAIN LOOKING FOR ANOTHER FIELD TO LAND.

AFTER HE IDENTIFIED ANOTHER FIELD THAT SEEM TO BE SAFE TO PERFORM ANOTHER LANDING PROCEDURE, THE PILOT BEGAN THE APPROACH TO LAND, THE AIRCRAFT TOUCHED THE GROUND NORMALLY ON THE MAIN LANDING GEAR, HOWEVER AS THE AIRCRAFT WAS ROLLING ON THE GROUND THE PILOT NOTICED A BARB WIRE FENCE IN FRONT OF THE AIRCRAFT. AT THIS POINT HE STATED THE AIRCRAFT WAS TOO SLOW AND CLOSE TO THE FENCE TO PERFORM A GO-AROUND PROCEDURE. AS A RESULT OF THIS THE AIRCRAFT NOSE GEAR STRUCK THE FENCE AND SKIDDED TO ONE SIDE THEN CAME TO A FULL STOP SHORTLY AFTER, COLLAPSING THE NOSE GEAR.