CHI98LA331 · Cessna 172N
Cessna 172N · Accident: total loss of engine power (non-mechanical) en route
From HCE · Hutchinson, MN to an unrecorded destination
Event
- NTSB case
- CHI98LA331
- 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
- 0
- 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 172N
- 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
- N6703E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From HCE · Hutchinson, MNTo not recorded
- 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
- En route · cruise
- 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
- Total loss of engine power (non-mechanical)
- 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
- Fuel exhaustion
- 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
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
As the airplane neared its destination the pilot did a pre- landing checklist. When he placed the mixture to full 'RICH' the engine began to run rough. He said the application of carburetor heat did not eliminate the roughness. The pilot said he positioned the fuel selector to the 'RIGHT' fuel tank and the engine began to run normally for a short time and then quit. The on-scene examination revealed no usable fuel in the airplane's fuel tanks. The pilot said he had told another pilot to fill the fuel tanks to the filler neck the day before the accident flight. During his preflight inspection of the airplane, the pilot said he did not visually check the fuel level, but relied on the fuel tank guages to confirm that the tanks were 'FULL.'
Probable cause
An inadequate preflight inspection by the pilot which resulted in fuel exhaustion and subsequent loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI98LA331
- Event ID
- 20001211X11012
- Case number
- CHI98LA331
- 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. 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: df47a33ae474c3bf3ed1ddee0dd8901975f32d6d441f141b8b6d71352ca91da5; retrieved 2026-09-22T16:55:58.707Z.