23 Sep 2013: PIPER PA60 602P — Donald M Muirhead

23 Sep 2013: PIPER PA60 602P (N35FD) — Donald M Muirhead

No fatalities • Sandpoint, ID, United States

Probable cause

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.

— NTSB Determination

Accident narrative

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.

Contributing factors

  • cause Landing distance — Not attained/maintained
  • cause Descent/approach/glide path — Not attained/maintained
  • cause Pilot
  • Contributed to outcome
  • Tailwind

Conditions

Weather
VMC, wind 190/04kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.