SEA94LA097 · Piper PA-23-160
Piper PA-23-160 · Accident: total loss of engine power (non-mechanical) en route
From Cedar City Regional Airport (CDC) to an unrecorded destination
Event
- NTSB case
- SEA94LA097
- 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
- 0
- 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-23-160
- Aircraft type
- Piper PA-23
- 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
- N4480P
- Operator
- Stout, Keith, A. · private individual
- Onboard fatalities
- Unknown
- Route
- From Cedar City Regional Airport (CDC), Cedar City, UTTo not recorded
- 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
- En route · descent
- 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
- Pilot in command › Airspeed, excessive
- Pilot in command › Refueling, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER TOPPING OFF WITH 72 GALLONS OF FUEL THE PILOT FLEW 1.25 HOURS AND THEN MADE AN INTERMEDIATE STOP DURING WHICH NO FUEL WAS ACQUIRED. UPON DEPARTURE AT 1150 HOURS, THE FUEL GAGES READ SLIGHTLY MORE THAN HALF. DURING THE DESCENT TO HIS FINAL DESTINATION, POWER WAS LOST ON THE LEFT ENGINE. THE PILOT WAS REQUIRED TO HAND PUMP THE GEAR AND FLAPS DOWN DURING WHICH HE 'USED UP MOST OF THE RUNWAY' AND EXECUTED A SINGLE ENGINE GO- AROUND. HE THEN MANUALLY BEGAN HAND PUMPING THE GEAR AND FLAPS UP BUT WAS UNABLE TO ESTABLISH A POSITIVE CLIMB, AND EXECUTED AN INTENTIONAL FORCED LANDING TO AVOID POWER LINES. DURING THE FORCED LANDING (AT 1335 HOURS) THE AIRCRAFT IMPACTED SEVERAL FENCE POSTS. POST CRASH EXAMINATION OF THE AIRCRAFT BY A MECHANIC REVEALED NO FUEL IN THE FUEL TANKS AND NO ODOR OF FUEL IN OR AROUND THE AIRCRAFT. THE PILOT INDICATED THAT IT HAD BEEN A WHILE SINCE HE HAD FLOWN THIS TYPE OF AIRCRAFT.
Probable cause
THE PILOT IN COMMAND'S FAILURE TO REFUEL AND EXCESSIVE AIRSPEED DURING THE APPROACH. FACTOR(S) WERE: FENCEPOST(S) AND THE LACK OF RECENT EXPERIENCE IN TYPE OF AIRCRAFT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA94LA097
- Event ID
- 20001206X01176
- Case number
- SEA94LA097
- 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. 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: e5ca8ff4c1501580dd322a11c8b4fc2722b65ec2c881583af1e647b2685e9822; retrieved 2026-09-23T01:11:48.652Z.