Cessna 172A N7243T accident near Enumclaw, Washington

Probable cause

The pilot's improper approach for landing, which resulted in the airplane landing long, and his delayed decision to go around with insufficient runway remaining, which resulted in collision with an airport perimeter fence.

NTSB analysis

The student pilot and a noncurrent private pilot were conducting a local, personal flight. The student reported that he did not remember the flight or any details surrounding the accident other than that the private pilot was operating the airplane at the time of the accident. The private pilot did not provide an account of the accident.

A witness reported seeing the airplane making touch-and-go landings and noted that, during the last landing, the airplane landed near the departure end of the runway, attempted to stop, but the left main tire skidded, and with about 40 yards remaining, power was added for a takeoff attempt. The airplane then travelled off the runway end onto grass, impacted the top of the airport's barbed wire perimeter fence, and came to rest nose down.

The fence's top rail and about 260 ft of wire were found separated from the fence, a large part of the wire was twined around the airplane, and the top rail was found on the path between the runway and the wreckage, indicating that the airplane became airborne after the pilot added power.

Examination of the airframe and engine did not reveal evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation. Given the evidence, it is likely that the pilot did not establish a proper approach for landing, which resulted in the airplane landing long, and that his subsequent delayed decision to go around with insufficient runway remaining led to the airplane impacting an airport perimeter fence.

Text from the NTSB. Open the NTSB docket for WPR17LA169 for the full record.