ERA11CA430 · Cessna 182
Cessna 182 · Accident: fuel exhaustion on approach
From Dumplin Field (86TN) to Dumplin Field (86TN)
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
- ERA11CA430
- 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 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
- N5813B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dumplin Field (86TN), Dandrige, TNTo Dumplin Field (86TN), Dandrige, 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
- Approach · VFR pattern final
- 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 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he fueled the airplane for two flights with skydivers and thirty minutes of reserve fuel. He further stated that during the second approach he had to adjust his intended flight path for other airplane traffic. Then, as the pilot decreased the pitch of the airplane on final approach, the engine sputtered and lost power. The pilot landed the airplane in a field; however, during the landing roll the airplane nosed over and came to rest inverted which resulted in substantial damage to the left wing spar. The pilot reported that the airplane experienced fuel starvation and that he did not maintain the required reserve. The pilot indicated that more fuel would have been his recommendation to avoid this accident.
Probable cause
The loss of engine power due to fuel exhaustion as a result of poor planning.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA430
- Event ID
- 20110730X10548
- Case number
- ERA11CA430
- 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. 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: 7fd8072073e307d6738c03b0cef1f0c369737e8fd93ac941729a1298f79ff1b0; retrieved 2026-09-15T16:32:08.193Z.