LAX05LA168 · Piper PA-23-250
Piper PA-23-250 · Accident: loss of engine power en route
From Tuba City Airport (T03) to Lake Havasu City Airport (HII)
Event
- NTSB case
- LAX05LA168
- 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-23-250
- 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
- N30YC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tuba City Airport (T03), Tuba City, AZTo Lake Havasu City Airport (HII), Lake Havasu, AZ
- 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 · cruise
- 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
- Loss of engine power
- 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 starvation
- 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 › Starvation
- Pilot in command › Emergency procedure, improper use of
- Pilot in command › Fuel management, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The left engine lost power during cruise, and the pilot made a forced landing in an open field with rough uneven terrain. About 45 minutes into the flight, the left engine started to sputter. The pilot attempted to restart the engine. When the engine did not restart, he secured it and then flew towards an alternate airport. Prior to reaching the airport, he attempted to lower the landing gear by placing the landing gear handle in the DOWN position. The landing gear did not extend, so he tried to lower the landing gear via the primary emergency landing gear system (hand pump). When that did not work, he activated the secondary emergency extension system (CO2 blow down tank) by pulling the emergency gear extension ring. The CO2 tank discharged; however, only the right main landing gear extended. The pilot said that with the drag from the partially extended gear they were not going to make the airport, and he made a forced landing in a rough open field. The pilot reported that he believed he had 30 gallons of fuel in each fuel tank. Recovery personnel indicated that the fuel cells had not been breached during the accident, the fuel lines were intact, and they did not see any fuel on the ground surrounding the airplane. They recovered 15 gallons of fuel from right outboard fuel tank, and 15 gallons of fuel from the right inboard fuel tank. Thirty gallons of fuel were drained from the left wing outboard fuel tank. No fuel was found in the left wing inboard fuel tank. The manufacturer's owner's manual for the airplane indicates that if the left engine fails the hydraulic pump will not function (the single system pump is on the left engine), and the emergency landing gear extension system has to be used. The pilot also has to place the landing gear lever in the DOWN position, fully extend the hand pump handle, and then pump the emergency gear handle up and down 30-40 strokes in order to get the landing gear to lower. The pilot can also utilize the CO2 tank for emergency landing gear extension; however, the landing gear selector has to be in the DOWN position for the gas to be correctly ported to the down side of the hydraulic actuators. The airframe, left engine, and landing gear were inspected. The fuel injector manifold was removed and disassembled, with no fuel observed. No fuel was found in the fuel lines from the left wing to the left engine. No discrepancies were found with the left engine's internal mechanical continuity. Investigators noted that the emergency gear handle was pulled out about 2 inches and not fully extended, and the emergency gear extender ring for the CO2 system appeared to be pulled out. The hydraulic system lines were intact. Clean hydraulic fluid was found in the power pack and the hydraulic system filter was clean.
Probable cause
the pilot's fuel system mismanagement that led to a fuel starvation induced loss of power in the left engine. Also causal was the pilot's improper use of the emergency landing gear extension system.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX05LA168
- Event ID
- 20050525X00673
- Case number
- LAX05LA168
- 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: ade4f6110c9a981ab8b343737f3109ebe9baa1099abb48518b0383cd49b3a58d; retrieved 2026-09-22T05:56:13.928Z.