WPR13CA344 · Piper PA-18-135
Piper PA-18-135 · Accident: fuel exhaustion during landing
From Jefferson County International Airport (K0S9) to Jefferson County International Airport (K0S9)
Event
- NTSB case
- WPR13CA344
- 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-18-135
- Aircraft type
- Piper PA-18
- 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
- N37JR
- Operator
- Ryder Jerry
- Onboard fatalities
- Unknown
- Route
- From Jefferson County International Airport (K0S9), Port Townsend, WATo Jefferson County International Airport (K0S9), Port Townsend, WA
- 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
- Fuel exhaustion
- 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 › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the airplane ran out of fuel about 16 miles from his destination and he executed a forced landing to a nearby private airstrip. During the approach, the airplane was high and fast, resulting in a long landing. In order to avoid going into the trees, he applied heavy braking. The airplane nosed over which resulted in substantial damage to the wings and fuselage. The pilot reported no preimpact malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
A loss of engine power due to the pilot's inadequate planning and mismanagement of the fuel supply, which resulted in fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13CA344
- Event ID
- 20130728X50318
- Case number
- WPR13CA344
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2013-07-28.
- API snapshot SHA-256: 2e4ff3f271b80f9e9c2e22d1c7077897bfd141228a6121d52ee7718625663417; retrieved 2026-09-15T22:20:34.815Z.