WPR13LA419 · Piper PA60 602P
Piper PA60 602P · Accident: landing area overshoot
From Provo Municipal Airport (PVU) to Sandpoint Airport (SZT)
Event
- NTSB case
- WPR13LA419
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA60 602P
- Aircraft type
- Piper PA60
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N35FD
- Operator
- Donald M Muirhead · private individual
- Onboard fatalities
- Unknown
- Route
- From Provo Municipal Airport (PVU), Provo, UTTo Sandpoint Airport (SZT), Sandpoint, ID
- Aircraft age
- About 32 years (built 1981)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Landing area overshoot
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13LA419
- Event ID
- 20130923X62507
- Case number
- WPR13LA419
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: dc9b4a54ccaac6ba50a29a1146e1ce88f1874d46897dad80e7f863dfead16f17; retrieved 2026-09-15T22:53:57.871Z.