FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09LA341 · Huston Charles D PITTS S-12

4 Jun 2009 · Spicewood, TX, United States

Huston Charles D PITTS S-12 · Accident: fuel contamination before flight

From Austin Air Ranch Airport (88R) to Austin Air Ranch Airport (88R)

Report a problem

Event

NTSB case
CEN09LA341
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

Huston Charles D PITTS S-12

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
N922TP
Onboard fatalities
Unknown
Route
From Austin Air Ranch Airport (88R), Spicewood, TXTo Austin Air Ranch Airport (88R), Spicewood, TX
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
Prior to flight
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

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

NTSB narrative

The airplane was on departure when the engine started sputtering and lost power. The pilot turned toward the runway and landed beside the runway in the dirt, substantially damaging the airplane. Postaccident examination revealed that the fuel flow sensor, which was located upstream of the fuel flow filter, was clogged with an unidentified substance and there was particulate matter in the fuel lines. The source of the substances could not be determined. The experimental airplane manufacturer installed the fuel flow sensor upstream of the fuel flow filter as depicted on a fuel flow schematic, provided for information only, by the airplane airframe kit manufacturer. The installation instructions for the fuel flow sensor indicated the fuel flow sensor should be installed downstream of a fuel filter.

Probable cause

A total loss of engine power due to fuel starvation as a result of the presence of an unidentified contaminant in the fuel system which clogged the fuel flow sensor. Contributing to the accident was the manufacturer’s installation of the fuel flow sensor upstream of the fuel filter and the misleading fuel schematic published by the airplane kit manufacturer.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09LA341
Event ID
20090608X02229
Case number
CEN09LA341
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2009-06-05.
  • API snapshot SHA-256: bee65a9beceff2f4a34d059523a42345a1b2c98f1d00d6bc1b3616b78761c44e; retrieved 2026-09-15T11:19:04.511Z.