Aviation Accident Summaries

Aviation Accident Summary FTW96LA358

TULSA, OK, USA

Aircraft #1

N8565W

Piper PA-28-235

Analysis

According to the pilot, he executed a normal approach with two notches of flaps. He added that as 'he pulled the brake handle after touching down, the handle came all the way back and [he] realized the brakes had failed.' The pilot added that he pumped the brake handle a few more times in an attempt to stop, but without success. The pilot further stated that he elected not to abort the landing, because he was too far down the runway and too close to the 25 foot trees, obstructing the departure end of the runway. The airplane subsequently overran the 300 foot grass overrun area and impacted a tree stump and bushes. No tire skid marks were found on the freshly sealed 2,580 foot asphalt runway. Postaccident examination of the airplane confirmed that the brake fluid reservoir was empty. A review of the aircraft maintenance records revealed that maintenance was performed on the brake system during the last annual inspection, which was completed 12 flight hours prior to the accident. The runway sloped downhill in the direction of landing.

Factual Information

On August 24, 1996, at 1230 central daylight time, a Piper PA-28-235, N8565W, was substantially damaged during a runway overrun while landing near Tulsa, Oklahoma. The airplane, owned and operated by a private owner, was being operated as a personal flight under Title 14 CFR Part 91. The private pilot, sole occupant of the airplane, was seriously injured. Visual meteorological conditions prevailed for the cross country flight for which a VFR flight plan was filed. The airplane departed from Kirk Field in Paragould, Arkansas, at approximately 1030. According to witnesses who were waiting for the airplane's arrival at the Harvey Young Airport, the airplane "made a normal approach and touchdown on runway 35." According to the pilot, he executed a normal approach with two notches of flaps. He added that as "he pulled the brake handle after touching down, the handle came all the way back and [he] realized the brakes had failed." The pilot added that he pumped the brake handle a few more times to stop without success. The pilot further stated that he elected not to abort the landing because he was too far down the runway and too close to the 25 foot trees obstructing the departure end of the runway. The airplane subsequently overran the 300 foot grass overrun area at the departure end of the runway and impacted a tree stump and bushes. No tire skid marks were found on the freshly sealed 2,580 foot asphalt runway. Photos submitted by the pilot's sister of the landing sequence of the airplane indicated that the pilot did not land long (as was initially reported by local law enforcement personnel). Post-accident examination of the airplane confirmed that the brake fluid reservoir was empty. A review of the aircraft maintenance records revealed that maintenance was performed on the brake system of the 1963 model airplane during the last annual inspection completed 12 flight hours prior to the accident. Pertinent maintenance records and invoices are enclosed. Both wings, the left side of the fuselage, and the nose section of the airframe sustained structural damage. A pilot who operates a similar single engine airplane from the airport stated that "the fact that runway 35 slopes slightly downhill probably contributed to the airplane's poor deceleration during the landing roll."

Probable Cause and Findings

low fluid level in the hydraulic reservoir, due to inadequate maintenance/inspection, which resulted in an inoperative brake system. Factors relating to the accident were: the down sloping runway, and trees at the departure end of the runway.

 

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