Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

September 23, 2013 · Piper PA60 602P · N35FD

Sandpoint, ID

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
September 23, 2013
Injury Outcomes
No injuries (3 uninjured)
Location
Sandpoint, ID
Aircraft
Piper PA60 602P (1981)
Tail Number
N35FD
Operator
Donald M Muirhead
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR13LA419

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.

NTSB 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.

Full 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.

Flight

Event TypeAccident
Event Time08:15 PDT
Nearest AirportSandpoint Airport (0nm N)
Runway01
Runway Length5501 ft
Runway Width75 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA60 602P
Tail NumberN35FD
Aircraft CategoryAir
DamageSubstantial
OperatorDonald M Muirhead
Operating RulePart 91
Engines2
Engine TypeReciprocating
Engine DetailsLycoming · TIO-540 · Reciprocating · 350 | Lycoming · TIO-540 · Reciprocating · 350
Seats5

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 55 · Second Class · None

Conditions

ConditionsVMC
LightDaylight
Wind190° @ 4 kt
Visibility10 sm
CeilingBroken clouds 2200 ft
Temperature / Dew Point50 / 45 C
Altimeter29.87 inHg
Observation Time14:43
Weather SourceWFAC

Appendix: Source Data