Accident Details
Probable Cause and Findings
The pilot's inadequate fuel management which resulted in fuel exhaustion and subsequent loss of engine power.
Aircraft Information
Registered Owner (Current)
Analysis
On July 25, 1998, approximately 1015 mountain daylight time, a Cessna TU206G, N102AK, owned and operated by the pilot's company, was substantially damaged during a forced landing following a loss of engine power near Midvale, Utah. The private pilot, the sole occupant onboard, was not injured. The aircraft was being operated as a personal flight under Title 14 CFR Part 91. Visual meteorological conditions prevailed, and no flight plan had been filed. The flight originated at Chico, California, at 0535 Pacific daylight time.
According to the pilot's accident report, he obtained a weather briefing and departed Chico, California, en route to Heber, Utah. When he was fourteen miles west of Heber, he encountered thunderstorms and rain. He contacted Salt Lake City Approach Control and was directed to descend to 5,500 feet and was vectored towards the Salt Lake City Municipal Airport. Approximately 6 miles southeast of the airport, the engine lost power. He switched fuel tanks and tried to restart the engine, but was unsuccessful. He made a forced landing on a rolling field surrounded by power lines. The airplane struck the ground and rolled approximately 100 to 125 feet uphill. The engine separated from the firewall, and a fire erupted between the engine and firewall. As the pilot exited the airplane, he grabbed a fire extinguisher and put out the fire.
The airplane received an annual inspection on July 20, 1998, at which time it was refueled. It did not fly again until the day of the accident. The pilot said he "did not physically inspect" the fuel tanks prior to his departure from Chico.
According to the salvage company that retrieved the airplane, there was no evidence of fuel in the left tank but "a couple of gallons" of fuel were found in the right tank.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# FTW98LA331