CHI94LA197 · Cessna 182
Cessna 182 · Accident: total loss of engine power (non-mechanical) en route
From Moody Air Force Base (VAD) to St Louis Downtown Airport (CPS)
Event
- NTSB case
- CHI94LA197
- 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 182
- Aircraft type
- Cessna 182
- 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
- N94752
- Operator
- Becker, Joseph J. and Ann E.
- Onboard fatalities
- Unknown
- Route
- From Moody Air Force Base (VAD), Valdosta, GATo St Louis Downtown Airport (CPS), Cahokia, IL
- 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 › Aircraft preflight, inadequate
- Pilot in command › Refueling, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT STATED THE AIRPLANE WAS EQUIPPED WITH EXTENDED RANGE FUEL TANKS (80 GALLONS CAPACITY, 75, GALLONS USABLE FUEL), AND WAS TOPPED OFF WITH FUEL BEFORE DEPARTURE. HIS CALCULATIONS INDICATED HE HAD SUFFICIENT FUEL FOR THE (ESTIMATED) FIVE HOUR FLIGHT, PLUS ONE HOUR RESERVE. THE PILOT REPORTED ALMOST FIVE HOURS AFTER TAKEOFF, THE ENGINE CUT OUT, RESTARTED BRIEFLY, THEN QUIT COMPLETELY. THE PILOT PERFORMED A FORCED LANDING IN A FIELD ABOUT 8 MILES SOUTHEAST OF THE INTENDED DESTINATION. POSTACCIDENT INVESTIGATION REVEALED NO EVIDENCE OF USABLE FUEL IN THE FUEL SYSTEM. THE PILOT STATED THERE WERE FUEL STREAKS ON THE RIGHT WING AND REPORTED A 'FUEL SYSTEM FAILURE (SIPHONED).' AN FAA INSPECTOR WHO INSPECTED THE AIRPLANE OBSERVED THAT THE FUEL TANKS WERE INTACT AND THAT THE FUEL GAUGES INDICATED EMPTY.
Probable cause
the pilot's inadequate aircraft preflight inspection and failure to refuel the airplane prior to fuel exhaustion. Related factors are the loose fuel cap (siphoning) and the uneven terrain encountered during the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI94LA197
- Event ID
- 20001206X01498
- Case number
- CHI94LA197
- 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: 1a23717498994bf1bb809cfe20b10bb8832c960a2c379f7bab74be298a458027; retrieved 2026-09-21T13:51:33.122Z.