FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN20LA042 · Cessna 172 M

21 Dec 2019 · Rush City, MN, United States

Hawk Aviation Cessna 172 M · Accident: fuel starvation during takeoff

From Rush City Regional Airport (ROS) to Rush City Regional Airport (ROS)

Report a problem

Event

NTSB case
CEN20LA042
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 172 M

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
N9646Q
Onboard fatalities
Unknown
Route
From Rush City Regional Airport (ROS), Rush City, MNTo Rush City Regional Airport (ROS), Rush City, MN
Aircraft age
About 44 years (built 1975)
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
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
Fuel starvation
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 › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

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

NTSB narrative

The student pilot and his flight instructor completed an uneventful 15- to 20-minute flight in the airport traffic pattern before the flight instructor deboarded so the student pilot could continue on his first solo flight. The engine was not shut down while the flight instructor deboarded the airplane. The student pilot then taxied to the hold-short line for the runway where he completed an abbreviated before takeoff check, which included verifying that elevator trim was positioned for takeoff, carburetor heat was turned off, flaps were fully retracted, and that the fuel mixture control was full rich. The student pilot did not complete an engine runup before takeoff.

The student pilot stated that after takeoff, the airplane climbed to about 200 ft above the runway where the engine began to splutter briefly before a total loss of power. The airplane sustained substantial damage to the fuselage and both wings during a forced landing in a wooded area.

The flight instructor stated that he taught his students to pull the mixture control knob aft about 1 1/2 inches during taxi to avoid fouling the sparkplugs. The flight instructor recalled that he told the student pilot to lean the fuel mixture while they taxied back to the ramp at the completion of their dual-instruction flight. The flight instructor stated that shortly after the accident, the student pilot told him that the mixture control was pulled aft about 1 1/2 inches and that the carburetor heat control was on.

The student pilot subsequently reported that that he did not lean the fuel mixture during taxi and that leaning typically was only completed during cruise flight. Additionally, before he exited the airplane, the student pilot turned off the electrical master switch and both magnetos, repositioned the fuel selector from both to off, and pulled the mixture control knob full aft.

Postaccident examination revealed uncontaminated 100 low-lead aviation fuel present in the fuel strainer and the carburetor bowl. There was no evidence of fouling or excessive carbon deposits on the sparkplugs that would have prevented normal engine operation. The lack of fouling or excessive carbon deposits on the sparkplugs was consistent with a proper air-fuel mixture and normal carburetor function during the flight. Additionally, a postaccident engine test run did not reveal any mechanical anomalies with the engine that would have prevented normal operation during the flight.

Although the carburetor heat control system did not function properly during the test run, the sparkplugs did not exhibit features consistent with a carburetor icing situation that would have resulted in an excessively rich air-fuel mixture had the airflow through the carburetor venturi become restricted due to carburetor icing during the flight. Additionally, the engine test run confirmed that while at maximum static speed, the engine would stop running due to fuel starvation with the mixture control knob moved aft about 1 1/2 inches. It is likely that the student pilot did not reposition the mixture control to full rich before takeoff, which resulted in a total loss of engine power due to fuel starvation.

Probable cause

The total loss of engine power due to fuel starvation because the student pilot failed to reposition the fuel mixture control to full rich before takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20LA042
Event ID
20191224X44852
Case number
CEN20LA042
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: 2701343983a83bf5f6c9b650f5bff29ed97eefbc8701c3133f0ecdfe85abe6df; retrieved 2026-09-16T10:48:47.292Z.