ERA13LA276 · Cessna 170
Cessna 170 · Accident: fuel contamination on approach
From Meriden Markham Municipal Airport (MMK) to Robertson Field (4B8)
Event
- NTSB case
- ERA13LA276
- 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
Cessna 170
- Aircraft type
- Cessna 170
- 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
- N2585V
- Operator
- Suttmeier Robert
- Onboard fatalities
- Unknown
- Route
- From Meriden Markham Municipal Airport (MMK), Meriden, CTTo Robertson Field (4B8), Plainville, CT
- 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
- Approach · VFR pattern downwind
- 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 oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that, as he reduced power, he incrementally increased the flap settings to 10, 20 and 30 degrees on the downwind leg on the west side of the runway. He added that he applied carburetor heat when he increased the flap setting to 20 degrees. At 80 mph, with 30 degrees of flaps extended and before turning to the base leg of the traffic pattern, the engine experienced a total loss of power. During the subsequent forced landing, the airplane flew from west to east across the runway, rather than turning toward the runway, and crashed in marshland on the east side of the runway abeam the numbers. The fuel system was sumped from three points, and each sample contained a significant quantity of water. The fuel system was drained, the airplane was serviced with fresh fuel, and an engine start was initiated. The engine started immediately, accelerated smoothly, and ran continuously without interruption. Examination of the seals around the fuel caps revealed that they were unserviceable, and no longer functioned as designed. Over 3 inches of rain fell between the previous flight and the accident flight and likely entered the fuel tanks through the seals around the fuel caps.
Probable cause
The pilot’s overflight of the landing runway during a forced landing after a loss of engine power. Contributing to the accident was the pilot’s inadequate preflight which resulted in his failure to detect water contamination of the fuel system.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13LA276
- Event ID
- 20130610X90937
- Case number
- ERA13LA276
- 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: 7beab3d968296d51151e0a6f085a98d6b4bfff7f79b18b80bac48a696fc05598; retrieved 2026-09-15T21:49:14.902Z.