Cessna 172A N7274T
16 March 2025 · Fairbanks, Alaska, United States · Minor injuries
Summary
On 16 March 2025 at about 22:15 local time, a Cessna 172A registered N7274T was involved in an accident near Fairbanks, Alaska, United States. 2 people were on board and one had minor injuries. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 22:15
- Classification
- Accident
- Location
- Fairbanks, Alaska, United States
- Nearest airport
- Fairbanks International (FAI)
- Coordinates
- 64.7866, -147.8982
- Aircraft
- Cessna 172A
- Registration
- N7274T
- Category
- Airplane
- Year built
- 1959
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Fairbanks → Fairbanks
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- ANC25LA025
People
1 person had minor injuries.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 2 | 0 | 0 | 1 | 1 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full 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.
Quoted verbatim from the NTSB record.
Other Cessna 172 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 17 Aug 2025 | Cessna 172 | Baltimore, Maryland, United States | - | No injuries | - |
| 29 Sep 2025 | Cessna 172 | Punxsutawney, Pennsylvania, United States | - | No injuries | - |
| 22 May 2025 | Cessna 172N | Murfreesboro, Tennessee, United States | JKG LLC | No injuries | - |
| 16 Mar 2025 | Cessna 172S | Rusk, Texas, United States | - | No injuries | - |
| 21 Aug 2025 | Cessna 172 | Air Force Academy, Colorado, United States | - | No injuries | - |
| 27 Nov 2025 | Cessna 172 | Nanaimo, Canada | Sealand Flight Ltd. | Fatal | 1 |
All 12,209 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 3 Jun 2025 | Piper PA-18-150 | Willow, Alaska, United States | Blue River Aviation | No injuries | - |
| 12 Jul 2025 | Piper PA-18-150 | Dillingham, Alaska, United States | - | No injuries | - |
| 18 Aug 2025 | Piper PA-18-150 | Willow, Alaska, United States | State of Alaska | No injuries | - |
| 11 Jul 2025 | Piper PA-18-135 | Palmer, Alaska, United States | - | No injuries | - |
| 20 Aug 2025 | Vu Holdings Llc/Dba Vanilla Un VA 001 | Ninilchik, Alaska, United States | VU Holdings LLC | No injuries | - |
| 4 Jan 2025 | Gippsaero GA8 | Nightmute, Alaska, United States | - | No injuries | - |