FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19LA129 · Piper PA 23 Undesignat

27 Apr 2019 · Sulphur Spring, TX, United States

Piper PA 23 Undesignat · Accident: fuel contamination en route

From Mount Pleasant Regional Airport (OSA) to Mount Pleasant Regional Airport (OSA)

Report a problem

Event

NTSB case
CEN19LA129
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 Undesignat

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
N233P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mount Pleasant Regional Airport (OSA), Mount Pleasant, TXTo Mount Pleasant Regional Airport (OSA), Mount Pleasant, TX
Aircraft age
About 63 years (built 1956)
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
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 contamination
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 › Aircraft power plant
  • Aircraft › Fluids/miscellaneous hardware
  • Not determined › Not determined
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot of a twin-engine airplane was in cruise flight when the left engine lost partial power. He turned on the boost pumps, checked the fuel quantity and engine gauges, verified fuel tank selection, and added throttle. However, the left engine continued to lose power. The pilot reported that, without warning, the right engine lost total power and would not restart. The right propeller went to the feathered position. The pilot initiated a forced landing to a field. During the descent, the left engine lost total power but the propeller continued to rotate, and the left engine was unresponsive to throttle input. During the forced landing, the airplane sustained substantial damage to the left and right wings and the fuselage. Examination of the right engine found the magneto timing at 12.5º (data plate specifies 25º). Otherwise, no preimpact abnormalities were noted during the right engine examination that would have precluded normal operations. The investigation was not able to determine why the right propeller was stopped in the feathered position. Examination of the left engine found the magneto timing at 23º. The bolts that secured the upper and lower halves of the carburetor were found loose. When the carburetor was opened, the inside of the bowl was dry, and the gasket appeared worn, consistent with rubbing between the two carburetor halves. The top set of spark plugs displayed heavy carbon coating consistent with the left engine running at a rich fuel setting. During a test run, the left engine would not produce rated power and ran rich. When the mixture was leaned, the left engine ran smooth and ran normally. The carburetor was bench tested and operated as expected. The carburetor was disassembled, and evidence of water staining was present.

A fuel sample collected from the left side fuel tank appeared divided with the top part blue, consistent with 100 LL avgas, and the lower portion of the liquid was clear with brown sediment visible at the intersection of the two liquids. The fuel strainer bowl revealed rust colored liquid and sediment in the bowl. The fuel strainer screen contained numerous small flakes of an unidentified contaminant. A sample of fuel drained from the left-wing tank tested positive for water when tested with water-finding paste. The loss of power on the left engine is likely due to water contamination.

Probable cause

The pilot’s inadequate preflight inspection, during which he failed to detect the water contamination in the left fuel, which resulted in a partial loss of power in the left engine. Contributing to the accident was the total loss of power in the right engine for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19LA129
Event ID
20190428X45827
Case number
CEN19LA129
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: investigation status, cause areas. 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: d28dea185378eb2c34d2fde1e5c36aa426ac78033aea10d6e630278a2d10d1fe; retrieved 2026-09-16T08:49:48.835Z.