Aviation Accident Summaries

Aviation Accident Summary LAX97LA199

EL MONTE, CA, USA

Aircraft #1

N6469D

Cessna 172N

Analysis

The student pilot reported that he had been practicing full stop landings after his previous three approaches. Following a 'cleared for the option' clearance, he elected to perform a touch-and-go landing. The student stated that it had taken a little longer for the airplane to touch down and begin the landing roll on the ground. He then applied full power and raised the flaps. The student stated that he thought the tower controller told him to get off the active runway immediately. He believed he had enough runway to stop, so he reduced power and attempted to stop the aircraft, but was unable before colliding with the perimeter fence. According to a recording of the communications, the controller advised the student to make a left turn off the runway when able, because there was an aircraft on short final.

Factual Information

On May 7, 1997, at 1338 hours Pacific daylight time, a Cessna 172N, N6469D, was substantially damaged when the student pilot aborted takeoff, veered off to the right of the departure end of runway 19, and collided with the airport perimeter fence at the El Monte, California, airport. The aircraft was operated by Valley Flight Center of El Monte, and was on a local solo instructional flight. The student pilot, the sole occupant, was not injured. The flight departed El Monte for the student's first supervised solo in the traffic pattern and was scheduled to terminate at that airport. The student pilot reported that he had been practicing full stop landings. Following a "cleared for the option" clearance from the Federal Aviation Administration (FAA) air traffic control tower, on the accident landing the student elected to perform a touch-and-go landing. The pilot stated that it had taken a little longer for the airplane to touch down and begin the landing roll on the ground. He then applied full power and raised the flaps. The student pilot stated that he heard the tower controller ask him to clear the active runway. The pilot reported that he believed he had enough runway to abort the takeoff and then reduce power. He attempted to stop the aircraft, but was unable to prior to colliding with the perimeter fence. A certified re-recording of air-ground voice communications tape was reviewed by the Safety Board. According to the tape, the controller had cleared the student pilot for landing with the touch-and-go option. The student pilot landed and the controller asked him to turn left when able and depart the active runway for an aircraft on short final. According to the student pilot's flight instructor, the student had made three full stop landings. On the last landing, the student pilot elected to perform a touch-and-go. The flight instructor, who reviewed the communications tapes, reported that the tower controller advised the student pilot to make a left turn off the runway when able due to traffic on short final. The student pilot thought that the controller had asked him to clear the active immediately due to landing traffic on short final. An FAA inspector from the Los Angeles, California, Flight Standards District Office, stated that no pre-existing anomalies were noted with the aircraft. The accident was reported to the Safety Board on June 3, 1997, after substantial damage to the aircraft was confirmed.

Probable Cause and Findings

the student pilot's misunderstanding of the controller's clearance during an aborted touch-and-go 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