Aviation Accident Summaries

Aviation Accident Summary SEA03LA070

Stanley, ID, USA

Aircraft #1

N8690T

Cessna 182C

Analysis

Prior to departing the pilot attempted refueling; however, no fuel was added as the fueling truck's battery was low. The pilot calculated he had 1 hour and 30 minutes of fuel on board, and that with each of the next two legs being 20 minutes each, he had a good 40 minutes of fuel reserve. The first leg of the flight took 20 minutes. The airplane departed on its second leg, but approximately 10 minutes into the flight the pilot encountered weather which he tried deviating around to the south, then to the north. At this time the pilot checked his watch, noting he had been in the air 30 minutes since departing. The pilot's GPS indicated he was 5 minutes from his destination and that the weather had moved through the area. In another 2 1/2 minutes the airport was in sight, and 30 to 40 seconds later the engine sputtered and quit. The airplane touched down approximately 2 1/2 miles short of the airport. FAA inspectors examined the airplane and found no fuel present. No other anomalies were noted.

Factual Information

On April 27, 2003, approximately 1550 mountain daylight time, a Cessna 182C single-engine airplane, N8690T, was substantially damaged during a forced landing following a complete loss of engine power near Stanley, Idaho. The airplane was registered to a private individual. The commercial pilot, sole occupant of the airplane, was not injured. Visual meteorological conditions prevailed, and a flight plan was not filed for the 14 CFR Part 91 personal flight. The flight originated from the Garden Valley Airport, Garden Valley, Idaho, at 1510 and was destined for the Stanley Airport. According to the Pilot/Operator Aircraft Accident Report (NTSB form 6120.1/2), the pilot reported that prior to departing he attempted to refuel, but the fuel truck would not start and no fuel was added. The pilot calculated that he had 1 hour and 30 minutes of fuel on board the aircraft for his next flight, which would be 20 minutes to his destination, and 20 minutes to return to his base "with a good 40 minutes reserve." The pilot reported that about 10 minutes into his return flight he encountered a "cell", which he tried to go around to the north. The pilot stated "I turned back to the south which I could then see was improving in that direction." The pilot said he then checked his time and that he had used 30 minutes of time since leaving on his final leg. The pilot reported that he considered landing at another airport, but the cell had moved in over that area. The pilot further stated that according to his GPS he was about 5 minutes from his destination, and as the cell had moved on he could see into the valley where his destination airport was located. The pilot reported that "in another 2 1/2 minutes I could see the airport." The pilot further stated that about 30 to 40 seconds later, with the airplane at 9,500 feet mean sea level (3,097 feet above ground level), " the engine sputtered and stopped." The pilot then made an emergency landing, touching down approximately one-half mile short of the airport. Damage to the aircraft included the separation of the nose gear, all three propeller blades were bent, the outboard 3 feet of the right wing tip was damaged, the rear of the fuselage was wrinkled, and the firewall had sustained substantial damage. According to two FAA Aviation Safety Inspectors, who traveled to the accident site and examined the airplane, the presence of fuel was not detected. No other anomalies were found.

Probable Cause and Findings

The pilot's inadequate in-flight planning that resulted in fuel exhaustion and the subsequent loss of engine power during descent. A factor contributing to the accident was the lack of suitable terrain for the forced landing.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports