FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI04LA070 · Piper PA-23-160

15 Feb 2004 · Casey, IL, United States

Piper PA-23-160 · Accident: loss of engine power during initial climb

From Casey Municipal Airport (1H8) to Durant Regional Airport - Eaker Field (DUA)

Report a problem

Event

NTSB case
CHI04LA070
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-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
N4332P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Casey Municipal Airport (1H8), Casey, ILTo Durant Regional Airport - Eaker Field (DUA), Durant, OK
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
Initial climb
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

  • Pilot in command › Airspeed(vmc), not maintained
  • Pilot in command › Maintenance, inspection, not obtained
  • Pilot in command › Remedial action, 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 aircraft sustained substantial damage during a forced landing after takeoff, following the loss of power on both engines. The pilot reported that during the previous flight the right engine experienced power fluctuations when he selected the right auxiliary fuel tank. The pilot stated the right fuel selector was "stiff and hard to move." The pilot reported the right engine operated without anomalies when the fuel selector was returned to the main fuel tank position. The flight continued uneventfully for another approximately 1 1/2 hours until the left engine began to experience power fluctuations. The pilot decided to make a precautionary landing at the Casey Municipal Airport. After the precautionary landing, the auxiliary fuel tanks were still full, the right main fuel tank was half full, and the left main fuel tank was nearly empty. The pilot reported the left main fuel tank was nearly empty because "the gas heater which had been burning more fuel than documented." The pilot proceeded to ground test the engines on different fuel selector positions prior to refueling. The pilot stated no anomalies were noted during the ground test and subsequently the airplane was completely refueled. The pilot noted no fuel contamination when he sampled all of the fuel tanks after refueling. The pilot reported he was "very confident" that the initial loss of right engine power was because he had momentarily positioned the right fuel selector in the "off" position prior to selecting the auxiliary tank. The pilot stated an "extensive [engine] run-up was performed, and all indications were once again very acceptable." The pilot reported the takeoff was uneventful until when he would normally have retracted the landing gear. At this point, the right engine began experiencing power fluctuations similar to the first occurrence. The pilot reported he continued to climb as he entered a left traffic pattern to return to the airport. He stated that fuel cross-feed was selected; however, the left engine also began to experience power fluctuations. The pilot reported that while the airplane was on crosswind it entered a downward spiral and he attempted to level the wings using full right aileron. The pilot stated, "Rudder input was as demanding as it was random, due to the varied yaw moments of the aircraft with power spurts from each engine." The pilot reported "not having time to decide which engine to feather, as both were producing random power output, we were close to impact, and I kicked in full right rudder as a last resort to bring the wings level, which worked, and [the passenger] joined me in pulling aft on the yoke to reach a pitch up attitude for impact." A Federal Aviation Administration (FAA) inspector performed the on-scene investigation. The inspector reported the fuel selector valves were in an intermediate or closed position. The inspector stated the cabling between the fuel gauge switch assemblies and the selector arms were corroded and seized. The inspector reported the cockpit fuel selector handles moved with resistance and would not reposition their respective valves. The inspector stated the valves functioned as designed when they were disconnected from the seized control cable.

Probable cause

The pilot not maintaining aircraft control during the loss of engine power and his improper remedial action during the encountered uncommanded roll (VMC roll). An additional cause was the pilot's failure to obtain a maintenance inspection by a qualified mechanic following the two instances of engine power loss during the previous flight. Contributing to the accident was the restricted movement of the fuel selectors due to corroded and seized control cabling, which resulted in fuel starvation and the subsequent loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04LA070
Event ID
20040310X00309
Case number
CHI04LA070
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: ad010f2cd41f2f3491c33252866c8e8991c233fa5d71b9037fbe380e8dcde529; retrieved 2026-09-22T07:57:25.277Z.