CEN17LA044 · Cessna 182P P
Cessna 182P P · Accident: fuel starvation during initial climb
From Bridgeport Municipal Airport (XBP) to New Braunfels National Airport (BAZ)
Event
- NTSB case
- CEN17LA044
- 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 182P P
- 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
- N7392Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bridgeport Municipal Airport (XBP), Bridgeport, TXTo New Braunfels National Airport (BAZ), New Braunfels, TX
- Aircraft age
- About 44 years (built 1972)
- 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
- Initial climb
- 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 starvation
- 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the takeoff was "normal" until about 200 ft above ground level, when the engine "suddenly stopped completely." Her efforts to restore engine power were not successful, and she executed a forced landing straight ahead. The airplane touched down "hard" in a pasture off the end of the runway and impacted a row of trees before coming to a stop. A witness that responded to the accident site stated that the fuel selector was in the off position. A responding law enforcement officer stated that both the pilot and passenger independently informed him that they believed the fuel selector was in the "wrong" position during takeoff. A postrecovery examination of the airframe and engine did not reveal any anomalies consistent with a preimpact failure or malfunction; therefore, it is likely that the engine experienced a total loss of engine power due to fuel starvation.
Probable cause
The pilot's failure to properly position the fuel selector before takeoff, which resulted a total loss of engine power due to fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA044
- Event ID
- 20161129X72258
- Case number
- CEN17LA044
- 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: f5eba6aaed6cafb9e795ecc9a4aeb2f99202e0cfbb08179d377ec1ba2bc3a264; retrieved 2026-09-16T04:52:12.590Z.