Aviation Accident Summaries

Aviation Accident Summary GAA16LA001

Redding, CA, USA

Aircraft #1

N7837X

CESSNA 172B

Analysis

The private pilot reported that, while landing after a cross-country flight, the landing roll seemed "fast" even though the airplane touched down "not far" past the runway numbers. The pilot determined that he would not be able to stop the airplane on the remaining runway, so he applied full power and aborted the landing. The airplane was in ground effect as it passed over the departure end of the runway. The pilot thought that the airplane was not going to clear the tree line in its flightpath, so he maneuvered the airplane to land on a dirt road. During the landing roll, the left wing impacted a barbed wire fence. The pilot reported that, during the initial landing, he "landed with a stiff tailwind on a short runway." The pilot reported that there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. During the accident, the passenger seated in the front right seat was ejected from the airplane and sustained a serious injury. According to the pilot, the passenger's seat had been in the "full rearward" position, which placed the lap belt attachment points about "mid-thigh" and probably did not allow the shoulder harness to be "tightened securely."

Factual Information

On October 3, 2015, about 1130 Pacific daylight time (PDT), a Cessna 172B airplane, N7837X, struck a barbed wire fence after aborting the landing at Benton Field Airport (O85) about 1 mile west of Redding, California. The private pilot sustained minor injuries and the sole passenger sustained serious injuries. The airplane sustained substantial damage to the fuselage and both wings. The airplane was registered to a private individual and operated by the pilot as a visual flight rules (VFR), personal cross-country flight under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed for the flight, no flight plan was filed. The flight originated from Yuba County Airport (MYV), Yuba City, California about 1030. The pilot reported that the landing roll seemed "fast" despite the fact the airplane touched down "not far passed" the runway numbers. When the pilot determined that he would not be able to stop the airplane on the runway remaining, he applied full power in an attempt to abort the landing. The pilot reported that the airplane was still in ground effect as they passed over the departure end of the runway. He reported that he could see that they were not going to "clear" the tree line in their flight path. The pilot maneuvered to land on a dirt road that was "cut" into the hillside. The pilot reported that as they touched down on the dirt road it was "very loud and rough". During the landing roll the left wing impacted a barbed wire fence. During the accident sequence, the passenger who was seated in the front right seat, was ejected from the airplane, and found about 30 feet from the wreckage. The pilot reported that the passenger's seat and seat belt were both intact and connected. The pilot reported that the passenger's seat was in the "full rearward" position, which placed the lap belt attachment points about "mid-thigh", and probably did not allow the shoulder harness to be "tightened securely". In the operator/owner safety recommendation section of the pilot accident reporting form, the pilot reported "it is clear and obvious to me; I landed with a stiff tailwind on a short runway". The pilot reported that there were no pre-impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. METEOROLOGICAL INFORMATION A review of recorded data from the automated weather observation station located about 6 miles to the southeast, revealed that, at 1153 PDT, conditions were wind 350 degrees true at 12 knots, visibility 10 statute miles, and sky clear.

Probable Cause and Findings

The pilot’s improper decision to land the airplane on a short runway with a tailwind and his subsequent delayed decision to abort the landing.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports