WPR13CA273 · Piper PA-28-140
Piper PA-28-140 · Accident: landing area overshoot
From Cascade Airport (U70) to Cavanaugh Bay Airport (66S)
Event
- NTSB case
- WPR13CA273
- 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 PA-28-140
- Aircraft type
- Piper PA-28
- 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
- N199
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cascade Airport (U70), Cascade, IDTo Cavanaugh Bay Airport (66S), Coolin, ID
- Aircraft age
- Not recorded
- 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
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that prior to arrival at the airport he received a calm wind report from a nearby airport. After turning right base for landing, he realized that he was too close in to the runway, so he reduced the power to idle, turned a 0.5-nautical-mile final approach, and added three notches of flaps. Prior to touchdown, he realized that he was running out of runway, and that it was too late to go around due to obstacles (trees) at the end of the runway. The airplane subsequently touched down, and the pilot retracted the flaps, turned off the ignition, and applied the brakes. The pilot tried to ground loop the airplane, but the landing gear struck one of the horizontal log railings at the end of the runway. The airplane bounced onto and skidded across an asphalt road and into some scrub brush and saplings. The left wing and all three landing gear separated. The pilot stated that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain an adequate glide path, which led to a runway excursion and collision with objects.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13CA273
- Event ID
- 20130617X21100
- Case number
- WPR13CA273
- 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: 2aedee266fbf0f7c74815a2a7a761675ad9846c5eb04b70701987fd769f527d6; retrieved 2026-09-15T21:54:05.266Z.