ERA20LA258 · Cessna 182 A
Cessna 182 A · Accident: fuel starvation en route
From Portsmouth International Airport at Pease (PSM) to Smoketown Airport (S37)
Event
- NTSB case
- ERA20LA258
- 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 A
- 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
- N4092D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Portsmouth International Airport at Pease (PSM), Portsmouth, NHTo Smoketown Airport (S37), Smoketown, PA
- Aircraft age
- About 63 years (built 1957)
- 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
- 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 › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During cruise flight, the airplane’s engine lost total power, which resulted in the pilot making an off-field emergency landing on a highway. During the landing, the airplane struck two automobiles and was substantially damaged.
After the accident, when the wings were removed for transport, 4 to 6 gallons of fuel were drained from the left-wing tank, and the right-wing tank was empty. Except for some fuel damping on the left-wing fuel tank feed hose and fuel staining, both of which were consistent with removal of the wing, no anomalies were noted during the examination of the fuel system. A test run of the engine was accomplished with no anomalies noted. Examination of the engine and data from the installed engine data monitor did not reveal evidence of any preimpact failures or malfunctions of the engine that would have precluded normal operation.
Review of the airplane owner’s manual indicated that fuel was supplied to the engine from two rubberized bladder type fuel cells (fuel tanks). Each fuel cell had a single fuel line located in the aft inboard section of the fuel cell. Fuel flowed via gravity from each of these fuel lines through the fuel selector valve and fuel strainer to the carburetor. The manual stated that 1.5 gallons of fuel per fuel tank were unusable and that, when not in level flight, an additional 3.5 gallons of fuel per fuel tank were unusable. This information (the location of the fuel lines in the aft inboard sections of the fuel tanks and the additional unusable fuel when not in level flight) indicated that the engine was susceptible to fuel starvation if the airplane was in a nose-low attitude with insufficient fuel in the fuel tanks.
According to the chief pilot of the skydiving company that used the airplane for its skydiving operations, the pilot told him that when the engine lost power, the airplane was in a nose low attitude and that the engine was “surging” (losing and regaining power). The chief pilot stated that “surging is a characteristic of fuel starvation as the fuel is being unported and then recovered as the fuel sloshes around in the tank.” The chief pilot expressed the opinion that if the pilot had “pitched the aircraft up to level flight the engine would have had enough fuel to [reach] the nearest airport about 7 miles away.”
Given that the amount of fuel recovered from the airplane (4 to 6 gallons) was less than the total unusable fuel when not in level flight (10 gallons) and that the engine operated with no discrepancies following the accident, it is likely that the loss of engine power occurred when the pilot flew the airplane in a nose low attitude with little fuel onboard, which resulted in fuel starvation.
Probable cause
The pilot's failure to ensure that sufficient fuel was onboard for nonlevel flight, which resulted in a total loss of engine power due to fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20LA258
- Event ID
- 20200721X20716
- Case number
- ERA20LA258
- 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: local date, investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2020-07-21.
- API snapshot SHA-256: 840ca186d03525a464c21652b5b8cd2ad1b68ac531990dc908556295aaf164b1; retrieved 2026-09-16T12:13:33.174Z.