FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13LA417 · Piper PA-22-125

16 Jul 2013 · Mapleton, MN, United States Narrative disagrees

Piper PA-22-125 · Accident: fuel contamination en route

From Wells Municipal Airport (68Y) to Mankato Regional Airport (KMKT)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN13LA417
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-22-125

Aircraft type
Piper PA-22
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
N663A
Onboard fatalities
Unknown
Route
From Wells Municipal Airport (68Y), Wells, MNTo Mankato Regional Airport (KMKT), Mankato, 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 › Fluids/miscellaneous hardware

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

NTSB narrative

The pilot said the airplane's engine started "sputtering" then lost total power. He made a forced landing in a corn field, and the airplane nosed over. The pilot stated that he performed a thorough preflight inspection of the airplane, during which he drained fuel from all three fuel sumps, and he found no evidence of water or sediment contamination. However, postaccident examination of fuel samples taken from both the left and right wing fuel tanks and from the gascolator fuel line revealed a substantial amount of water. The investigation revealed that the airplane had been parked outside and there had been recent heavy rains in the area.

Probable cause

The total loss of engine power due to water contamination of the fuel, which resulted in the pilot's forced landing to unsuitable terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13LA417
Event ID
20130717X02623
Case number
CEN13LA417
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: b260c3f16e6e3934fa7cb938dc83de579e185deb915e47eb659ba3fb72c476fb; retrieved 2026-09-15T22:13:53.720Z.