SEA07CA113 · Piper PA-18
Piper PA-18 · Accident: total loss of engine power (non-mechanical) while maneuvering
From Prineville Airport (S39) to Prineville Airport (S39)
Event
- NTSB case
- SEA07CA113
- 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
- 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
- N40520
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Prineville Airport (S39), Prineville, ORTo Prineville Airport (S39), Prineville, OR
- 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
- Maneuvering
- First occurrenceThe 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
- Total loss of engine power (non-mechanical)
- 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
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › Preflight planning/preparation, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During the preflight inspection, the pilot looked at the fuel level sight gauges and did not see a meniscus point in the clear tubes. He therefore assumed that this meant the tanks were completely full and that the entire sight gauge was filled with fuel. About five minutes after departure the aircraft ran out of fuel, and during the ensuing forced landing the aircraft nosed over on the soft, brushy terrain as the pilot applied "excessive braking" in order to stop before reaching a line of trees. After the accident, the pilot checked his fueling log, and then realized that the fuel tanks had been almost completely empty prior to takeoff, and that the reason he saw no meniscus point in the fuel quantity sight gauges was because the lines were completely full of air. The pilot had not visually checked the fuel tanks during his preflight.
Probable cause
The total loss of engine power due to fuel exhaustion as a result of the pilot failing to correctly read the fuel quantity sight gauges. Factors include soft, brushy terrain, and the pilot's intentional excessive braking during the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA07CA113
- Event ID
- 20070514X00564
- Case number
- SEA07CA113
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: dc23b1198d7aed9086a77f15aad3d90d2d373a2a3557a8302fc7cccc2747529d; retrieved 2026-09-22T03:52:38.176Z.