N8667T Cessna 182C accident

NTSB NYC02LA074 · 2002-03-24 · Moneta, VA · near W91

Docket — crew, injuries and powerplant

Summary

After releasing parachutists, the pilot planned to return to the airport. During the descent, about 2,500 feet msl, the engine began to lose power. The pilot thought that carburetor ice caused the power loss, and performed emergency procedures, which included the application of carburetor heat. The engine did not regain power, and the pilot planned an emergency landing to a field. As the pilot began to flare, the engine power returned, and he performed a go-around. During the go-around, about 50 feet agl, the engine began to lose power again. The pilot then attempted to land in a smaller field with an up-sloping incline. During the landing, the nose gear collapsed, and the airplane came to rest. The pilot stated that he departed with 12 gallons of fuel, and did not experience any pre-impact mechanical malfunctions with the airplane. However, the pilot told a Federal Aviation Administration (FAA) inspector that he either experienced carburetor ice or ran out of fuel. The FAA inspector did not find any fuel in the left fuel tank, and found less than 1 gallon of fuel in the right fuel tank. He did not find any fuel in the fuel line to the carburetor, nor the gascolator.

Full narrative

On March 24, 2002, about 1400 eastern standard time, a Cessna 182C, N8667T, was substantially damaged during a forced landing near Smith Mountain Lake Airport (W91), Moneta, Virginia. The certificated commercial pilot was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the parachuting flight conducted under 14 CFR Part 91.

According to the pilot's written statement, about 1330, he departed W91 with parachutists. After reaching a sufficient altitude, the parachutists jumped, and the pilot returned to the airport. During the descent, about 2,500 feet msl, the engine began to "sputter and cough." The pilot thought carburetor ice caused the power loss, and performed emergency procedures, which included the application of carburetor heat. The engine did not regain power, and the pilot planned an emergency landing to a field. As the pilot approached the field and began to flare, the engine power returned, and he performed a go-around.

During the go-around, about 50 feet agl, the engine began to "sputter and cough" again. The pilot then performed a forced landing to a smaller field with an up-sloping incline. During the landing, the nose gear collapsed, and the airplane came to rest upright. The pilot further stated that he departed with 12 gallons of fuel, and did not experience any pre-impact mechanical malfunctions with the airplane.

A Federal Aviation Administration (FAA) inspector observed the airplane situated on sloping terrain, and the right wing was pointed down-slope. He noted that the nose landing gear had collapsed into the firewall. The inspector added that he did not find any fuel in the left fuel tank, and observed less than 1 gallon of fuel in the right fuel tank. He did not find any fuel in the fuel line to the carburetor, nor the gascolator. The inspector did observe approximately 2 tablespoons of fuel in the carburetor. Additionally, he stated that there was no evidence of fuel leakage. The pilot told the Federal Aviation Administration (FAA) inspector that he either experienced carburetor ice or ran out of fuel.

Probable cause

The pilot's inadequate preflight planning, which resulted in fuel exhaustion. The National Transportation Safety Board determined the probable cause of this accident.

Circumstances

Event type
Accident
Highest injury
None
Weather conditions
Visual Meteorological Cond
Light condition
Day
Sky condition
NONE
Ceiling (ft)
0
Visibility (sm)
10
Wind direction
180
Wind speed (kt)
10
Temperature (F)
66
Nearest airport
Smith Mountain Lake Airport
Distance from field
1.0
Airport elevation
892

Aircraft

RegistrationMakeModelDamageFAR part
N8667T Cessna 182C SUBS 091

Sequence of events

#OccurrencePhase
1 353 Cruise
2 230 Cruise

Findings

Finding
17001
24001 cause