FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC25LA025 · Cessna 172A

16 Mar 2025 · Fairbanks, AK, United States

Cessna 172A · Accident: powerplant system/component malfunction/failure during initial climb

From Fairbanks International Airport (FAI) to Fairbanks International Airport (FAI)

Report a problem

Event

NTSB case
ANC25LA025
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
Event fatalities
Unknown
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 172A

Aircraft type
Cessna 172
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
N7274T
Operator
Unknown
Onboard fatalities
Unknown
Route
From Fairbanks International Airport (FAI), Fairbanks, AKTo Fairbanks International Airport (FAI), Fairbanks, AK
Aircraft age
About 66 years (built 1959)
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
Initial climb
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
Powerplant system/component malfunction/failure
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 power plant
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot, who was also the owner of the airplane, was conducting a familiarization flight with the pilot-rated passenger, who was a prospective buyer of the airplane. The pilot reported having flown the airplane for a total of 35 hours after the engine had been removed, disassembled, and reinstalled just over 3 years before the accident; however, the airframe and engine logbooks show no hours accrued since the engine reinstallation. The pilot reported that, during engine run-up, the engine speed did not decrease when he pulled the carburetor heat knob. He stated that, after he shut down the engine, he “had the pilot actuate the carb heat push/pull knob several times while I observed and felt the mechanism on the air box move in a way that seemed normal.” The pilot then elected to continue the flight. During the initial climb out, the pilot pulled the carburetor heat knob to recheck the functionality of the carburetor heat and immediately experienced a large drop in engine speed. He kept the carburetor heat on, “expecting it to clear quickly if it was ice, as it has always done in the past.” After observing that power was not being restored, he turned back toward the airport. The engine continued to run at low power; however, the airplane was unable to maintain altitude and the pilot elected to land on a frozen river south of the airport. During the landing, the airplane nosed over, which resulted in substantial damage to the wings. Postaccident examination of the engine revealed that the carburetor heat cable was too long, had a visible kink where it attached to the heat control mechanism, and did not properly engage the heat control mechanism in either the fully open or closed position. Due to the excessive length of the carburetor heat control cable, the carburetor heat was always partially on, and this condition could not be changed when actuated by the control knob in the cockpit. The excessive cable length most likely occurred due to inadvertent repositioning of the clamp attaching the carburetor heat control cable sheath to the carburetor airbox during a previous engine removal and reinstall about three and a half years before the accident flight. The environmental conditions at the time of the accident were not conducive to the accumulation of carburetor icing. The carburetor heat control cable’s excessive length and incorrect positioning likely prevented the proper operation of the carburetor heat, resulting in a partial application of carburetor heat and partial loss of engine power during climb out.

Probable cause

The pilot’s decision to initiate the flight despite identifying a malfunction in the carburetor heat system during the pre-takeoff engine run-up, which led to a partial loss of engine power during climb out. Contributing to the accident was maintenance personnel’s improper rigging of the carburetor heat control cable.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC25LA025
Event ID
20250319199877
Case number
ANC25LA025
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: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 346da05cc0c7bad7fee59e0310649cf90d88f7f7a9e6dede0fea02215585006e; retrieved 2026-09-16T19:44:43.764Z.