FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL04LA008 · Cessna 182H

5 Oct 2003 · Knoxville, TN, United States Narrative disagrees

Cessna 182H · Accident: loss of engine power en route

From Auburn University Regional Airport (AUO) to Knoxville Downtown Island Airport (DKX)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ATL04LA008
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
Instrument Meteorological Cond

Cessna 182H

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
N1919X
Operator
Jerry L. Norton · private individual
Onboard fatalities
Unknown
Route
From Auburn University Regional Airport (AUO), Auburn, ALTo Knoxville Downtown Island Airport (DKX), Knoxville, TN
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
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
Fuel exhaustion; 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

  • Fuel system, cap › Not secured

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

NTSB narrative

The pilot stated that he topped off both fuel tanks prior to departing Knoxville Downtown Island Airport. The airplane had extended range tanks and held 51 gallons of fuel. The pilot stated that there were 12 gallons of fuel in the left tank and 39 gallons of fuel in the right tank. The flight from Knoxville Downtown Island Airport to Auburn-Opelika Airport was uneventful. On the return trip, from Auburn to Knoxville, the pilot switched the fuel lever to the right fuel tank immediately after departure to compensate for the unequal fuel quantities. Approximately 8 miles east of the Knoxville Downtown Island Airport at 2500 feet, the airplane engine began to sputter and the pilot stated that he moved the fuel lever to the both tanks position. The airplane engine fired, ran shortly and then stopped. The pilot was unable to restart the engine and reported the engine failure to the air traffic controller. The pilot set up the airplane for a slow, full flap descent but was unable to see where to land due to the darkness. The right wing of the airplane struck a tree and the airplane came to rest in a small field. Examination of the airplane revealed the outer section of the right wing and wing strut detached, the nose gear detached and damage to the propeller. Blue fuel stains were found streaking along the top of the left wing and left side of the fuselage, and the left fuel cap was missing. A search for the fuel cap along the crash path and general area of the wreckage was unsuccessful. The examination found no usable fuel in either tank. The fuel caps on this airplane were aftermarket gas caps installed in accordance with STC # SA2376CE. The gas caps are designed to be twisted on and when the cap is completely rotated in a clockwise direction, it will stop in a locked position. The gas cap is visible from the ground but does not have any reference markings to allow a person to visually determine if the gas caps are properly locked in place. During the pilot's post-accident interview and his written statement, he did not report securing the fuel caps during the preflight inspection.

Probable cause

The pilot's inadequate preflight inspection by his failure to secure the left fuel tank cap which resulted in fuel exhaustion, and the loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL04LA008
Event ID
20031009X01694
Case number
ATL04LA008
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: 749300a72e57913cd219a32bb57861b2f8a9d690df9a9a0c8d8edd3bde2a6ddb; retrieved 2026-09-22T08:23:58.206Z.