FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC05LA053 · Cessna 140

30 Mar 2005 · Denali Park, AK, United States

Cessna 140 · Accident: loss of engine power during takeoff

From Denali National Park Airport (INR) to Bethel Airport (PABE)

Report a problem

Event

NTSB case
ANC05LA053
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 140

Aircraft type
Cessna 140
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
N2204N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Denali National Park Airport (INR), Denali National, AKTo Bethel Airport (PABE), Bethel, AK
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
Takeoff · roll/run
First occurrenceThe 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
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

  • Reason for occurrence undetermined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The solo private pilot stated that prior to the 14 CFR Part 91, personal cross-country flight, he preheated the airplane engine prior to takeoff. During the takeoff roll the engine started running rough. The pilot said he applied carburetor heat and continued the takeoff because there was not enough runway left to stop. The engine lost all power about 5 miles south of the airport, and during the ensuing emergency forced landing, the left wing struck a tree. The airplane came to rest inverted in a creek. The pilot said there were no preaccident mechanical anomalies with the airplane, but he suspected ice in a gas line, or restricted airflow to the carburetor from fresh snow, or possibly a stuck valve. The airplane sustained structural damage to the wings and fuselage during the accident.

Probable cause

The loss of engine power during takeoff and cruise flight for an undetermined reason, which resulted in an emergency descent/landing, and collision with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC05LA053
Event ID
20050405X00408
Case number
ANC05LA053
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 960e3077fea61de7aafa6d477a13118ce8951d8177e1edc57f1a7a56d0f515ab; retrieved 2026-09-22T06:07:51.872Z.