ERA22LA112 · Cessna 195
Cessna 195 · Accident: fuel exhaustion on approach
From Spruce Creek Airport (7FL6) to Flagler Executive Airport (FIN)
Event
- NTSB case
- ERA22LA112
- 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
- 0
- 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 195
- Aircraft type
- Cessna 195
- 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
- N597K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Spruce Creek Airport (7FL6), Daytona Beach, FLTo Flagler Executive Airport (FIN), Palm Coast, FL
- Aircraft age
- About 73 years (built 1949)
- 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
- 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 and the pilot-rated passenger departed their home airport to fly to a nearby airport about 20 minutes away. The pilot stated that he did not add any fuel to the airplane before the flight, as he thought he had enough fuel for the intended 20-minute flight. He reported that before takeoff everything was normal. He took off, and upon reaching 1,000 feet above mean sea level (msl), he configured the airplane for cruise. The airplane was operating normally when, about 5 miles from the destination airport, the engine lost power. The propeller continued to windmill, but it produced no power. He attempted to restart the engine without success. The pilot declared an emergency and informed air traffic control (ATC) that he would be landing on an interstate. During the forced landing, the airplane’s right wing contacted a truck, and the airplane came to rest inverted off the right side of the interstate, incurring substantial damage. The passenger said that he was worried about fire, and immediately tried to get out of the airplane. Once the passenger was out of the airplane, though, he did not see any fire or smoke, and there was no smell of fuel. During the wreckage recovery, there was also no smell of fuel at the accident scene, with the exception of a slight smell of fuel near the engine. Additionally, no fuel could be recovered from the airplane. The postaccident examination of the airplane and engine also revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Additionally, the fuel strainer and the carburetor float chamber were absent of fuel. An engine monitor was installed on the airplane that recorded exhaust gas temperature (EGT), cylinder head temperature (CHT), and shock cooling rate. During the accident flight, it recorded a rapid decrease in EGT, a rapid increase in shock cooling, and a rapid decrease in CHT, all of which in combination were indications that were consistent with of a loss of fuel flow. The passenger stated that after the accident the pilot was “absolutely confident” that he had enough fuel for the 20-minute flight, and that the pilot said his fuel totalizer showed 23 gallons. However, the airplane’s fuel totalizer required that a known fuel quantity be programmed at the beginning of the flight. If an accurate quantity had not been entered by the pilot at some previous point, the information indicated by the fuel totalizer would not have been correct. Based on the available information, it is likely that the loss of power was due to the fuel system containing little or no usable fuel, as no fire occurred during the impact sequence, the passenger did not observe fire or smell fuel when he egressed, no fuel was able to be recovered on-scene during the wreckage recovery, the fuel strainer and carburetor float chamber were absent of fuel, and examination of the engine revealed no evidence of any preimpact failures or malfunctions which would have precluded normal operation. The circumstances of the accident were consistent with a total loss of engine power due to fuel exhaustion, which resulted from the pilot’s inadequate fuel planning and preflight inspection.
Probable cause
The pilot’s inadequate fuel planning and preflight inspection, which resulted in a total loss of engine power due to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA112
- Event ID
- 20220201104580
- Case number
- ERA22LA112
- 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, cause areas. 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: 868d1ad24f8067d89911064bf00f90872108ce4f564a1d6b4bbf4c395a7a838f; retrieved 2026-09-16T14:55:32.965Z.