FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12LA128 · Sanderson Pitts Special SPS-1

5 Jan 2012 · Revere, MN, United States

Sanderson Pitts Special SPS-1 · Accident: fuel contamination en route

From Madison Municipal Airport (MDS) to Faribault Municipal Airport-Liz Wall Strohfus Field (FBL)

Report a problem

Event

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

Sanderson Pitts Special SPS-1

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
N330BL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Madison Municipal Airport (MDS), Madison, SDTo Faribault Municipal Airport-Liz Wall Strohfus Field (FBL), Faribault, MN
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
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 systems
  • Aircraft › Fluids/miscellaneous hardware

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane had not been flown for over 6 months prior to the accident flight. Before departure, the pilot added about 3 gallons of fuel to the existing fuel on board the airplane. The pilot did not find contamination when he drained fuel from the main fuel tank sump drain. About 20 minutes after departure, during cruise flight, the airplane experienced a total loss of engine power that led the pilot to conduct a forced landing on a road. The airplane nosed over during the landing. An examination of the airplane revealed that the airplane was not equipped, nor was it required to be equipped, with a fuel sump drain(s) for the wing tank, which drained into the main fuel tank. Water contamination was present in the fuel line leading to the carburetor, but no water contamination was noted when the main fuel tank sump—the only available sump—was drained. Accordingly, water was likely in the wing tanks and fed into the main tank after it was sumped. The water then entered the fuel lines. The lack of sump drains in the wing tanks is an inadequate design because it does not allow a pilot to remove all water from the fuel system.

Probable cause

The total loss of engine power during cruise flight due to fuel contamination and the inadequate design of the fuel system.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12LA128
Event ID
20120110X02454
Case number
CEN12LA128
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, 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: 518f2bcd6aeea950dcc15725417b5f7f3977fadf446075591b5761e3d0f92f01; retrieved 2026-09-15T17:03:10.925Z.