Accident Details
Probable Cause and Findings
The pilot's failure to fly the approach at the appropriate landing speed and attain the correct touchdown point, which resulted in a runway overrun.
Aircraft Information
Registered Owner (Historical)
Analysis
On September 23, 2013, about 0815 Pacific daylight time, a Piper PA60 602P, N35FD, sustained substantial damage as a result of a runway overrun and subsequent impact with the airport's localizer equipment at the Sandpoint Airport, Sandpoint, Idaho. The airplane was registered to Young Living Essential Oils LC, of Lehi, Utah. The commercial pilot and one passenger were not injured, while the remaining passenger sustained minor injuries. Visual meteorological conditions prevailed for the corporate cross-country flight, which was being operated in accordance with 14 Code of Federal Regulations Part 91, and an instrument flight rules flight plan was filed. The flight departed the Provo Municipal Airport, Provo, Utah, about 0600 mountain daylight time, with SZT as its destination.
In a statement submitted to the National Transportation Safety Board investigator-in-charge (IIC), the pilot reported while approaching SZT, he requested and was approved for the GPS approach [for Runway 01]. After descending out of the clouds at about 2,500 feet above ground level (agl), the pilot received the local automated weather; the wind was reported to be from 190 degrees at 4 knots. The pilot stated that as he was set up on a right base leg for runway 01, he considered the 4 knot tailwind minimal for the 5,500-foot runway. The pilot further stated that he landed quite a bit long, but thought he had sufficient room to stop with heavy braking, and [during the landing roll] had the sensation of "…no brakes at all." The airplane subsequently ran off the end of the runway, and impacted the localizer before coming to rest upright. The pilot concluded in his report that this accident could have been prevented by landing into the wind and on the numbers. The pilot reported no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
In a telephone interview with the IIC, the owner of the airplane reported that he was seated in the rear cabin at the time of the accident. The owner stated that during the approach he detected that the pilot was having an alignment problem with the approach. He further reported that the pilot was high, the flaps were full down, the airspeed over the threshold was 132 knots, and that there was a tailwind of about 10 knots; the airplane flight manual states that the approach speed for the reported landing weight of 5,156 pounds and full flaps (45 degrees) would have been about 90 knots. The owner stated that over the runway threshold, the airplane dropped down then went back up, and that the pilot tried to force the airplane down. The owner added that after the airplane went off the end of the runway and came to a stop, he exited the aircraft and noticed that while the brakes were not smoking, they were hot.
A postaccident examination of the airplane's braking system was performed by a Federal Aviation Administration airworthiness inspector, on September 25, 2013. The inspector reported that an inspection of the brake reservoir revealed that all of the brake fluid was gone, however, the inside area of the reservoir was observed to be wet and shiny, indicative that there had been brake fluid present recently. Further, inspection of the brake actuators on the pilot's rudder pedals revealed that all components appeared to be working correctly. The inspector concluded that all evidence observed supports the contention that the brakes were most likely operating properly prior to the airplane leaving the runway.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# WPR13LA419