FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12LA575 · Cessna 182Q

22 Sept 2012 · Fort Thomas, KY, United States

Cessna 182Q · Accident: loss of engine power (total) on approach

From Cincinnati Municipal Airport Lunken Field (LUK) to Cincinnati Municipal Airport Lunken Field (LUK)

Report a problem

Event

NTSB case
ERA12LA575
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 182Q

Aircraft type
Cessna 182
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N735FJ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Cincinnati Municipal Airport Lunken Field (LUK), Cincinnati, OHTo Cincinnati Municipal Airport Lunken Field (LUK), Cincinnati, OH
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern final
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of engine power (total)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the pilot, he performed preflight carburetor heat checks at the recently overhauled engine's run-up speed and at idle. He thought that the rpm drop was less than the drop before the engine was overhauled, yet he chose to make the flight. After takeoff, the pilot climbed the airplane to about 3,000 ft mean sea level, where he determined that the optional carburetor temperature gauge was inoperative. He subsequently applied carburetor heat in 5-minute intervals when he changed tanks, which he did twice at 20-minute intervals.

Noting precipitation in the area, the pilot decided to cut the flight short and return to the departure airport. He applied full carburetor heat before descending the airplane using the descent procedures checklist. About 9 nautical miles (nm) from the runway, with carburetor heat applied and the fuel tanks set to "both," he continued a slow descent with 10-degrees flaps. About 6 nm from the runway, the pilot felt a "power drop." The engine was still running, but the airplane was descending faster than anticipated. The pilot applied more throttle and felt a "slight boost," but the airplane continued to descend and subsequently impacted trees. During the descent, the pilot repeatedly checked the controls, "pulling them in and out to make sure they were not stuck," including the carburetor heat, throttle, prop pitch (fully in), and fuel mixture (full-rich).

No evidence of any preexisting mechanical anomalies that would have precluded normal operation was found. Although the pilot subsequently noted that he was concerned that a preexisting crimp in the scat tube leading from the heat manifold to the carburetor might have caused the engine to lose power, this scenario was unlikely due to the relative size of the crimp and the fact that the pilot did not note any engine anomalies when he applied carburetor heat during cruise flight with higher air flow requirements.

The temperature and dew point at the time of the accident were conducive to the accumulation of serious carburetor icing at glide power, and the make and model of airplane is known to be more susceptible than most airplanes to carburetor ice formation. In addition, although the pilot reported adding carburetor heat before initiating a long descent, he did not report adding engine power periodically to warm the engine during that descent; thus, it is likely that the carburetor heat manifold cooled to a point where the air being supplied to the carburetor was insufficiently heated to protect it from icing.

A review of Federal Aviation Administration, manufacturer, and advocacy group carburetor icing publications revealed disjointed and incomplete information. The lack of comprehensive, easily accessible carburetor icing information in a single location likely affects the overall pilot community's understanding of the subject and could have affected the pilot in particular.

Probable cause

The pilot’s failure to periodically add engine power during an extended descent in carburetor icing conditions, which resulted in insufficient carburetor heat, the gradual build-up of carburetor ice, and the subsequent loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12LA575
Event ID
20120923X21645
Case number
ERA12LA575
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2012-09-23.
  • API snapshot SHA-256: a8dd24ca5358e53b809ff7101df3842fd58b855ff5309025f8c928c83dbf46d8; retrieved 2026-09-15T20:00:14.641Z.