# Accident 20020510013719A: Cessna 210M, Watertown, MN, May 10, 2002 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: May 10, 2002, 20:59 local time - Place: Watertown, MN - Damage: No damage - Operating rules: General operating rules (Part 91) - Location: 44.9601° N, 93.8392° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=44.9601&lon=-93.8392&mi=10 - Aircraft: N357TC, a cancelled registration (https://openairdocs.org/deregistered/N357TC-2004-08-09) (OpenAirDocs) - Registry model: Cessna 210M (registry code 2073450, https://openairdocs.org/model/cessna-210m) (OpenAirDocs) - Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs) - Reported make and model: CESSNA 210M - Fatal injuries: 0 - NTSB investigation: [NTSB CHI02LA129](https://openairdocs.org/ntsb/CHI02LA129) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20020510013719A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (-23) PILOT HAD BEEN DOING PRACTICE APPROACHES AT LITCHFIELD (KJLF) WHILE ENROUTE FROM MORRIS, MN TO FLYING CLOUD AIRPORT LOCATED IN EDEN PRAIRIE, MN. MR. STAHLE REPORTED THAT ENGINE STARTED TO CHUG AND LOSE POWER JUST AFTER DARK. PILOT ATTEMPTED TO SET AIRCRAFT DOWN ON COUNTY ROAD 122 NEAR WATERTOWN, MN. THE LANDING WAS JUST SHORT OF ROAD IN DITCH WITH AIRCRAFT FLIPPING OVER. AIRCRAFT WAS SUBSTANTIALLY DAMAGED. DURING INTERVIEW PILOT DISCLOSED THAT HE HAD NOT SWITCHED FUEL TANKS WHICH LEAD TO FUEL STARVATION. (.19) ON MAY 10, 2002, AT 2100 CENTRAL DAYLIGHT TIME, A CESSNA 210M, N357TC, PILOTED BY A PRIVATE PILOT, SUSTAINED SUBSTANTIAL DAMAGE DURING A FORCED LANDING FOLLOWING A LOSS OF ENGINE POWER NEAR WATERTOWN, MINNESOTA. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME OF THE ACCIDENT. THE FLIGHT WAS BEING OPERATED UNDER THE PROVISIONS OF 14 CFR PART 91 WITHOUT A FLIGHT PLAN. THE PILOT, THE SOLE OCCUPANT, REPORTED MINOR INJURIES. THE FLIGHT DEPARTED MORRIS MUNICIPAL AIRPORT (MOX), MORRIS, MINNESOTA, AT 1800 AND HAD THE INTENDED DESTINATION OF FLYING CLOUD AIRPORT (FCM), MINNEAPOLIS, MINNESOTA. ACCORDING TO THE PILOT'S WRITTEN STATEMENT, HE HAD FLOWN FROM FCM TO MO X EARLIER IN THE DAY AND WAS RETURNING TO FCM AT THE TIME OF THE ACCIDENT. THE PILOT REPORTED THAT HE DID NOT FLY DIRECTLY BACK TO FCM AND HAD PRACTICED APPROACHES AT FIVE AIRPORTS PRIOR TO RETURNING TO FCM. THE PILOT STATED, "I WAS DESCENDING TO FLYING CLOUD [AIRPORT] & WAS AT ABOUT 2,700 FEET WHEN [ENGINE] POWER FAILED. I ATTEMPTED 'ENGINE OUT' PROCEDURES BUT WAS UNABLE TO RESTORE [ENGINE] POWER. I ATTEMPTED TO LAND ON A ROAD (OR THE FIELD BEYOND) BUT WAS UNABLE TO REACH EITHER ONE & LANDED SHORT OF THE ROAD. THE PROP & NOSE GEAR DUG INTO SOFT GROUND & FLIPPED THE AIRPLANE OVER & IT LANDED ON THE ROAD." THE PILOT REPORTED THAT THE AIRPLANE WAS FUELED WITH 70 GALLONS PRIOR TO THE FLIGHT TO MOX. THE PILOT REPORTED THAT THE FLIGHT FROM FCM TO MOX HAD TAKEN APPROXIMATELY 1.1 HOURS. THE AIRPLANE WAS NOT FUELED PRIOR TO THE RETURN FLIGHT TO FCM. THE PILOT REPORTED THE ACCIDENT FLIGHT WAS APPROXIMATELY 2.5 HOURS IN LENGTH. THE PILOT TOLD A FEDERAL AVIATION ADMINISTRATION (FAA) INSPECTOR, "... HE [THE PILOT] FORGOT TO SWITCH THE FUEL SELECTOR TO THE OTHER TANK." THE PILOT ALSO TOLD THE FAA INSPECTOR THAT HIS BEING INDECISIVE ON A LANDING AREA CONTRIBUTED TO THE AIRPLANE LANDING SHORT OF THE ROAD. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB CHI02LA129](https://openairdocs.org/ntsb/CHI02LA129), May 11, 2002: Cessna 210M (N357TC), Watertown, MN, substantial damage. Probable cause: The improper fuel management by the pilot which resulted in fuel starvation and subsequent loss of engine power. Contributing to the accident was the soft terrain in which the forced landing was… ## Other reports on N357TC (1) Matched to the same aircraft by N-number and date. - [Incident 19960104000089I](https://openairdocs.org/incident/19960104000089I), Jan 4, 1996: Cessna 210M (N357TC), Indianapolis, IN, Minor damage. Narrative: incident was due to loss of visual cues on landing roll-out. Runway had not been plowed. Estimates 3-4" snow on surface. On January 4, 1996, at… From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.