Aviation Accident Summaries

Aviation Accident Summary BFO95LA091

MARTINSBURG, WV, USA

Aircraft #1

N68969

CESSNA 152

Analysis

DURING A SOLO TRAINING FLIGHT, THE STUDENT PILOT RETURNED TO THE AIRPORT TO PRACTICE TOUCH AND GO LANDINGS. ON THE SECOND LANDING, THE AIRPLANE BOUNCED TWICE AND BEGAN TO DRIFT LEFT OF CENTERLINE. THE STUDENT PILOT DECIDED TO GO AROUND AND ADDED FULL POWER. AT THIS TIME, THE LEFT DRIFT INCREASED AND THE AIRPLANE LEFT THE RUNWAY. AS THE AIRPLANE BOUNCED ON THE ROUGH TERRAIN, THE PILOT REALIZED THAT HE WAS NOT AIRBORNE. HE PULLED THE THROTTLE TO IDLE AND BEGAN TO BRAKE HEAVILY. THE AIRPLANE IMPACTED TREES 100 FEET LEFT OF THE RUNWAY.

Factual Information

On August 30, 1995, at 1544 eastern daylight time, a Cessna 152, N68969, sustained substantial damage during an aborted landing attempt at Eastern West Virginia Regional/Shepherd Field, Martinsburg, West Virginia. The student pilot received minor injuries. Visual meteorological conditions prevailed and no flight plan had been filed. The flight was conducted under 14 CFR Part 91. The local solo instructional flight originated from Eastern West Virginia Regional/Shepherd Field, Martinsburg, West Virginia, at 1500. The student pilot departed the class "D" airspace for a local solo training flight. Upon return, the student pilot requested touch and go landings. On the second landing attempt, the airplane bounced twice and the student pilot decided to go around. The student pilot stated that the airplane had already begun to drift left and as full power was added, the left drift increased rapidly. After the airplane veered off the runway, it began to bounce on the rough terrain. The pilot stated that in the excitement of the moment he forgot to push the carburetor heat knob in ("off" position) and to raise the flaps to the full up position. When the pilot realized that he was not airborne, he pulled the throttle to idle and began to brake heavily. The airplane impacted a tree located 100 feet left of the runway and abeam the 2000 foot remaining marker. During an interview with the Federal Aviation Administration Inspector, the student pilot stated that the engine and flight controls responded normally the entire flight.

Probable Cause and Findings

the student pilot's failure to maintain control of the airplane during the landing/aborted landing sequence. A related factor is the student pilot's lack of total flight experience.

 

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