WPR12LA099

NTSB accident investigation · Cessna 172M · Cusick, WA · February 9, 2012

Accident · No injuriesLimited investigationFinal report
Date
February 9, 2012, 15:30 local (23:30 UTC)
Place
Cusick, WA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N5100RCessna 172M
Defining event
Enroute-cruise: Loss of engine power (partial)
Weather
Visual (VMC) · Day
Status
Completed · report October 9, 2014
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
Federal Aviation Administration
FAA report
20120209002059A
Case key
82855

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

A total loss of engine power during cruise flight for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.

Findings · 2

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Not determinedNot determined › Not determined · Unknown/Not determinedCessna 172M: 16 casesAll aircraft: 2,247 casesProbable cause
Object/animal/substance: tree(s)Environmental issues › Physical environment · Contributed to outcomeCessna 172M: 16 casesAll aircraft: 933 cases

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot reported that, after takeoff, the engine began to run roughly and lose power. He applied carburetor heat, which did not restore power. The pilot's further troubleshooting attempts were unsuccessful, and he initiated a forced landing. The engine subsequently lost power, and, during the landing to a nearby field, the airplane struck several trees. A postaccident examination of the airframe revealed about 8 gallons of fuel were remaining in the right tank. The left fuel tank was breached during the impact, and it was found empty due to the breach. Further examination of the airplane and a subsequent engine run revealed no mechanical malfunctions or failures that would have precluded normal operation.

Factual narrative

On February 9, 2012, at 1530 Pacific standard time, a Cessna 172M, N5100R, experienced a loss of engine power during cruise flight and the pilot made a forced landing in a forested area approximately 2 miles north of Cusick, Washington. The owner/pilot operated the airplane as a personal cross-country flight under the provisions of 14 Code of Federal Regulations Part 91. The pilot, the sole occupant, was not injured. The airplane sustained substantial damage to the wings and fuselage. The flight departed Coeur d'Alene Airport – Pappy Boyington Field (COE), Coeur d'Alene, Idaho, about 1500, and was destined for Sand Canyon Airport (1S9), Chewelah, Washington. Visual meteorological conditions prevailed for the local area flight, and no flight plan had been filed.According to the pilot, he performed a preflight of the airplane, to include sumping the fuel tanks and checking the oil before his departure from COE; there were no abnormalities noted. He also stated that the run-up was normal. On takeoff, he had 10 degrees of flap extended. The takeoff was normal, but the pilot stated that the airplane did not feel 'as spunky as normal'. All of the indications were good; it just did not seem to be producing power. The pilot stated that about 10 minutes from his destination airport, the engine began to run rough. He thought the engine may have carburetor ice, and he pulled the carburetor heat on; however, it did not clear up. He began looking for a spot to make a forced landing, while also attempting to troubleshoot the engine problem. The troubleshooting included switching from one fuel tank to the other, activation of the carburetor heat, use of the boost pump and primer, and all failed to restore power. The pilot stated that the engine kept missing like it wanted to quit. He saw a field that he thought he initially would make; however, it became apparent to him that he was not going to make the field. At that point, he saw an opening and flew toward it. The pilot recalls turning off the master, magneto, and electrical switches before the airplane struck trees. On scene investigation revealed that the left fuel tank was breached and empty from the impact. About 8 gallons of 100LL fuel were drained from the right fuel tank from wreckage recovery personnel. A post accident examination of the airplane and subsequent engine run revealed no mechanical malfunctions or failures that would have precluded normal operation.

Aircraft

Registration
N5100R
Reported as
Cessna 172M
Category
Airplane
Serial number
17263338
Airframe hours
3,660
Engine
Lycoming O-360-A1A, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Jim Miller
Registered owner
Jim Miller
Airworthiness certificate
Standard, Normal
Last inspection
Annual · July 13, 2011
Departed
COE · Coeur d'Alene, ID
Destination
1S9 · Chewelah, WA

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
58
Injuries
None
Certificates
Private, Commercial
Airplane ratings
Multi-engine land, Single-engine sea, Single-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Last flight review
April 14, 2011
Seat
Left
Flight hours
23,300 total · 2,500 in this make and model · 12,800 as pilot in command · 80 in the last 90 days · 20 in the last 30 days · 10 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
40° at 5 knots
Visibility
10 statute miles
Lowest ceiling
1,800 ft overcast
Temperature
37 °F, dew point 32 °F
Altimeter
30.32 inHg
Observed at
DEW, 27 nm away

Docket · 6

The files NTSB released with the investigation on August 21, 2014, on NTSB’s docket system: statements, records, photos and specialists’ reports. 1.9 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.