# NTSB WPR13LA419: Piper PA60 602P, N35FD, Sandpoint, ID, September 23, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: September 23, 2013, 08:15 local (15:15 UTC) - Place: Sandpoint, ID - Coordinates: 48.340099, -116.450561 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=48.3401&lon=-116.4506&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Landing area overshoot](https://openairdocs.org/ntsb-events/380) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report October 27, 2014 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 88109 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR13LA419 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/88109/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=88109 - Page: https://openairdocs.org/ntsb/WPR13LA419 ## 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Aircraft capability: landing distance](https://openairdocs.org/ntsb-findings/01061030): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper AEROSTAR 602P, 1 case](https://openairdocs.org/ntsb-findings/01061030/cases.md?model=7106014), [All aircraft, 68 cases](https://openairdocs.org/ntsb-findings/01061030/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper AEROSTAR 602P, 1 case](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=7106014), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper AEROSTAR 602P, 2 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7106014), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Object/animal/substance: runway/taxi/approach light](https://openairdocs.org/ntsb-findings/03022012): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Piper AEROSTAR 602P, 1 case](https://openairdocs.org/ntsb-findings/03022012/cases.md?model=7106014), [All aircraft, 106 cases](https://openairdocs.org/ntsb-findings/03022012/cases.md) - [Wind: tailwind](https://openairdocs.org/ntsb-findings/03034015): Environmental issues › Conditions/weather/phenomena · Not specified; cases with it: [Piper AEROSTAR 602P, 1 case](https://openairdocs.org/ntsb-findings/03034015/cases.md?model=7106014), [All aircraft, 594 cases](https://openairdocs.org/ntsb-findings/03034015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Landing area overshoot](https://openairdocs.org/ntsb-events/380) (defining event); cases with it: [Piper AEROSTAR 602P, 1 case](https://openairdocs.org/ntsb-events/380/sequence.md?model=7106014), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper AEROSTAR 602P, 1 case](https://openairdocs.org/ntsb-events/300/sequence.md?model=7106014), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper AEROSTAR 602P, 3 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7106014), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that, while on a right base leg visual approach, he received the current automated weather report and that he did not think that the 4-knot tailwind was an issue because the runway was 5,500 feet long. The pilot reported that, although the airplane landed long, he thought that he had sufficient runway to stop the airplane with heavy braking. However, as he applied the brakes, he felt the sensation of "no brakes" as the end of the runway quickly approached. The airplane's owner, who occupied a seat in the rear cabin, reported that the pilot seemed to be having a problem aligning the airplane with the runway during the approach, that the airplane was high and fast and the flaps were full down, and that the pilot was trying to force the airplane down onto the runway. The passenger reported that he observed that the approach speed was 132 knots; per the airplane's flight manual, the calculated approach speed for the landing weight of the airplane was about 90 knots. The airplane subsequently ran off the end of the runway and impacted the localizer structure, which resulted in substantial damage to the airplane. A postaccident examination of the airplane's braking system revealed that the brakes were likely operating properly before the airplane exited the runway. ## Factual 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 inspectionof 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. ## Aircraft - Registration: [N35FD](https://openairdocs.org/deregistered/N35FD-2018-01-03), registration cancelled 2018-01-03, S/N 62P08828165017, built 1981 (OpenAirDocs) - Reported make and model: PIPER PA60 602P - Registry model: [Piper AEROSTAR 602P](https://openairdocs.org/model/piper-aerostar-602p) (registry code 7106014) (OpenAirDocs) - Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 62P08828165017 - Year built: 1981 - Airframe hours: 2117 - Engines: Lycoming TIO-540 350 horsepower reciprocating; Lycoming TIO-540 350 horsepower reciprocating - Damage: Substantial damage - Flight: Executive/Corporate, Part 91 - Operator: Donald M Muirhead - Registered owner: Young Living Essential Oils LC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, August 7, 2013, 50 hours before - Departed: PVU, Provo, UT - Destination: SZT, Sandpoint, ID - Flight plan: IFR - Airport: SZT, Sandpoint Airport, runway 01, 5,501 × 75 ft, asphalt - Equipment: Auto-pilot, Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 55; injuries: none; commercial; airplane ratings: multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review June 13, 2012; seat: left; restraint: 3-point; flight hours: 3,368 total, 1,137 in this make and model, 3,368 as pilot in command, 60 in the last 90 days, 29 in the last 30 days, 3 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 190° at 4 knots - Visibility: 10 statute miles - Lowest ceiling: 2,200 ft broken - Temperature: 50 °F, dew point 45 °F - Altimeter: 29.87 inHg - Observed at: SZT, 2 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20130923019679A](https://openairdocs.org/incident/20130923019679A), Sep 23, 2013: Piper AEROSTAR 602P, Sandpoint, ID, Substantial damage. Pilot landed long on runway, touching down over half way down the runway. Aircraft departed the end of the runway, traveling over 550 feet further before going… ## Docket (5 files) The files NTSB released with the investigation on September 8, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=88109. 2.5 MB in all. - Pilot-Operator Aircraft Accident-Incident Report form 61201 (item 1, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416148&FileExtension=.PDF&FileName=Pilot-Operator%20Aircraft%20Accident-Incident%20Report%20form%2061201-Redacted.PDF - Weather Data (item 2, .PDF, 215 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40402818&FileExtension=.PDF&FileName=Weather%20Data-Master.PDF - FAA inspector's statement (item 3, .PDF, 193 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40402817&FileExtension=.PDF&FileName=FAA%20inspector%27s%20statement-Redacted.PDF - Record of Conversation - Gary Young (item 4, .PDF, 89 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40402819&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Gary%20Young-Master.PDF - Excerpts from Aerostar AFM – Section 5 Performance (item 5, .PDF, 703 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416149&FileExtension=.PDF&FileName=Excerpts%20from%20Aerostar%20AFM%20%E2%80%93%20Section%205%20Performance-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.