CEN18LA163 · Cessna 182F F
Cessna 182F F · Accident: collision during takeoff/landing
From T91 · Luling, TX to T91 · Luling, TX
Event
- NTSB case
- CEN18LA163
- 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 182F F
- 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
- N3291U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From T91 · Luling, TXTo T91 · Luling, TX
- Aircraft age
- About 55 years (built 1963)
- 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
- Landing
- 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
- Collision during takeoff/landing
- 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 › Aircraft systems
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Before taking off for the skydiving flight with four passengers, the commercial pilot refueled the airplane. Shortly after the airplane rotated, the passengers told the pilot that fuel was leaking from the left wing. The pilot believed that the leak was an immediate fire risk, so he decided to perform an off-airport landing. The pilot abruptly lowered the airplane’s nose and landed in a field. The airplane impacted terrain in a left-wing-low attitude and then hit a berm. The engine and right main landing gear separated during the impact sequence, and the left and right wings sustained substantial damage.
Postaccident examination revealed that the left-wing fuel tank cap was not secured and was dangling by the chain. During examination, no issues or anomalies with the left-wing fuel cap or fuel tank filler inlet were found, and the fuel cap was able to be fully secured. An examination of the airframe, engine, and remaining systems revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Given the evidence, it is likely that the pilot did not secure the left-wing fuel cap after refueling the airplane.
The airport was less than 1 mile away when the passengers told the pilot about the leak. It is possible that the pilot could have returned to the airport and landed the airplane at the airport without further incident.
Probable cause
The pilot’s failure to secure the left-wing fuel cap after refueling the airplane, which resulted in a fuel leak on takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18LA163
- Event ID
- 20180509X00947
- Case number
- CEN18LA163
- 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: 672760fee49ad33cf329f69dcff2a2bc9230d15a98a22838c8a3da9187765a48; retrieved 2026-09-16T07:06:09.590Z.