Cessna 170 N2585V accident near Plainville, Connecticut

Jun 9, 2013 · NTSB number ERA13LA276 · Final report

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.

NTSB analysis

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.

Text from the NTSB. Open the NTSB docket for ERA13LA276 for the full record.

Event

Date
Jun 9, 2013
Type
Accident
Place
Plainville, Connecticut
Nearest airport
Robertson Field (4B8)
Highest injury
None
Weather
Visual (VMC)
Light
Day

Cessna 170

N-number
N2585V
Category
Airplane
Damage
Substantial
Operating rule
Part 91 (general aviation)
Purpose of flight
Personal

From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.