WPR14LA023

NTSB accident investigation · Cessna 172 - M · Hardin, MT · October 21, 2013

Accident · Minor injuriesLimited investigationFinal report
Date
October 21, 2013, 08:00 local (14:00 UTC)
Place
Hardin, MT
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N80257Cessna 172 - M
Defining event
Enroute-cruise: Loss of engine power (partial)
Weather
Visual (VMC) · Day
Status
Completed · report March 17, 2015
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
FAA
FAA report
20131021020859A
Case key
88251

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 rough-running engine and partial loss of power, which resulted from the pilot’s failure to use carburetor heat appropriately while operating in an area conducive to carburetor icing.

Findings · 5

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.

Action: incomplete actionPersonnel issues › Action/decision · PilotCessna 172M: 2 casesAll aircraft: 105 casesProbable cause
Use of equip/info: use of equip/systemPersonnel issues › Task performance · PilotCessna 172M: 11 casesAll aircraft: 1,391 casesProbable cause
Temp/humidity/pressure: conducive to carburetor icingEnvironmental issues › Conditions/weather/phenomena · Contributed to outcomeCessna 172M: 5 casesAll aircraft: 435 casesProbable cause
Ice/rain protection system: intake anti-ice, deiceAircraft › Aircraft systems · Incorrect use/operationCessna 172M: 1 caseAll aircraft: 108 casesProbable cause
Wind: gustsEnvironmental issues › Conditions/weather/phenomena · Contributed to outcomeCessna 172M: 26 casesAll aircraft: 1,199 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, during cruise flight, the engine began running roughly. He began troubleshooting the problem and turned on the carburetor heat but only for a few seconds. The pilot's attempts to restore full engine power were unsuccessful, so he chose to initiate an emergency landing to a field. During the landing flare, the airplane encountered a wind gust, which pitched the airplane's nose down. The nose gear dug into the soil, and the airplane nosed over. A postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. Weather conditions in the area at the time of the accident were conducive to the formation of carburetor icing at cruise power. It is likely that the pilot did not apply carburetor heat long enough to prevent the accumulation of carburetor icing, which caused the engine to run roughly and lose partial power.

Factual narrative

On October 21, 2013, about 0800 mountain daylight time, a Cessna 172M, N80257, was substantially damaged during an emergency landing following reported engine roughness while in cruise flight, about 5 miles northwest of Hardin, Montana. The airplane was registered to and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91. The commercial pilot sustained minor injuries and was the sole person on board. Visual meteorological conditions prevailed and no flight plan was filed. The personal flight departed Broadus Airport, Broadus, Montana, about 0730, with a planned destination of Billings Logan International Airport (BIL), Billings, Montana. In a written statement to the National Transportation Safety Board (NTSB) investigator-in-charge (IIC), the pilot reported a rough running engine and partial power loss while in cruise flight about 1,500 feet, above ground level, and he decided to conduct an emergency landing to a nearby field. The pilot reported that during the landing flare, a gust of wind caused an abnormal landing which resulted in the airplane nosing over. During the accident sequence, the airplane sustained substantial damage to the engine firewall. Local law enforcement reported that fuel was observed leaking out of the wings at the accident site. The airplane was recovered to a secure storage facility for further examination. In a conversation to the NTSB IIC, the pilot reported that after the engine began running rough, he applied carburetor heat, but only for a short duration of a few seconds, while trouble shooting the engine. Despite his efforts the engine was still running rough and the pilot elected to perform an emergency landing. Examination of the recovered airframe by the NTSB IIC revealed that both wings were detached from the fuselage during the recovery efforts. Control continuity was established from the carburetor heat, throttle, and mixture controls to their respective linkages on the engine. Examination of the recovered engine revealed that it remained attached to the fuselage via its mounts. The engine mounting structure was displaced downward about 45 degrees. All engine accessories remained attached to the engine. The magnetos were removed from the engine. The magneto drive shafts were rotated by hand and a blue colored spark was produced on all ignition leads. The crankshaft was rotated by hand by use of the propeller and mechanical continuity was established throughout the engine and valve train. Cylinder compression and suction was obtained on all four cylinders. Fuel system continuity was obtained from both wing tanks inlet lines to the carburetor and no evidence of fuel leakage or loose lines was observed. The carburetor was removed, disassembled and was unremarkable. The gascolator was removed, examined and was unremarkable. About 2 ounces of a blue colored fuel was drained from the gascolator and was clear of debris. The spark plugs were removed from the engine andrevealed normal operating and wear signatures. Examination of the recovered airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. Weather conditions recorded at the BIL, located about 34 miles northwest of the accident site, at 0753, were wind calm, visibility 7 statute miles, clear sky, temperature 45 degrees Fahrenheit, dew point 34 degrees Fahrenheit, and an altimeter setting of 30.08 inches of mercury. According to the Federal Aviation Administration Special Airworthiness Information Bulletin CE-09-35, entitled Carburetor Icing Prevention, the temperature and dew point were conducive to the formation of icing at cruise power.

Aircraft

Registration
N80257
Reported as
Cessna 172 - M (M)
Category
Airplane
Serial number
17266482
Built
1975
Airframe hours
3,009
Engine
Lycoming O-320 SERIES, 160 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Halderman Marc D
Registered owner
Halderman Marc D
Airworthiness certificate
Standard, Utility; Standard, Normal
Last inspection
Annual · July 9, 2013
Departed
00F · Broadus, MT
Destination
BIL · Billings, MT
Equipment
Stall warning system

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
21
Injuries
Minor
Certificates
Flight instructor, Commercial
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 1, With waivers/limitations
Last flight review
June 9, 2012
Seat
Left
Restraint
Lap only
Flight hours
677 total · 270 in this make and model · 639 as pilot in command · 108 in the last 90 days · 50 in the last 30 days · 3 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
240° at 11 knots, gusting 19
Visibility
10 statute miles
Lowest ceiling
12,000 ft broken
Temperature
45 °F, dew point 34 °F
Altimeter
30.07 inHg
Observed at
BIL, 34 nm away

Docket · 5

The files NTSB released with the investigation on February 9, 2015, on NTSB’s docket system: statements, records, photos and specialists’ reports. 922 KB 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.