CEN09LA211 · Piper PA-23-160
Piper PA-23-160 · Accident: fuel contamination en route
From Shelbyville Municipal Airport (GEZ) to Spirit of St Louis Airport (SUS)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN09LA211
- 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
- N338WS
- Operator
- Delbert Reiff
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Shelbyville Municipal Airport (GEZ), INTo Spirit of St Louis Airport (SUS), Chesterfield, MO
- 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
- 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 › Fluids/miscellaneous hardware
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane had not been flown for four years. It was on the second leg of a ferry flight when the left engine failed. The pilot made a forced landing to a plowed field, during which the wings and bottom fuselage sustained substantial damage. Prior to the accident flight, the pilot told the airport manager that he could not get all of the water out of the fuel system and that he was sure that more water would be found during sumping, due to sloshing during the flight from the previous airport. The pilot stated that no contamination was found during the preflight. An examination of the airplane showed water in the fuel. No other anomalies were found with the airplane.
Probable cause
The loss of engine power during cruise flight due to fuel contamination. Also causal was the pilot's decision to conduct the flight with known contaminants in the fuel.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09LA211
- Event ID
- 20090316X10236
- Case number
- CEN09LA211
- 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. 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: 1681c0f953bb05f9590ce62233d2ae6e841278aa1ca4891a0974bd329a5380ce; retrieved 2026-09-15T10:50:22.713Z.