ERA22LA264 · Cessna 208
Connecticut Parachutist Cessna 208 · Accident: fuel exhaustion en route
Event
- NTSB case
- ERA22LA264
- 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 208
- Aircraft type
- Cessna 208
- 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
- N90JF
- Operator
- Connecticut Parachutist
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 37 years (built 1985)
- 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 · descent
- 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 reported that he planned to refuel the skydiving jump airplane after his third flight of skydivers and experienced about 10 minutes of loading delays with the third flight of skydivers. Then, while climbing, he was “delayed a few minutes” because of traffic in the area. He stated that he was not sure when the low fuel light illuminated, but that on his descent back toward the airport after releasing the third load of skydivers, the red “Reservoir Fuel Low” annunciator illuminated. About 8,000 ft mean sea level, the engine lost all power due to fuel exhaustion. Subsequently, the pilot made an emergency landing at the airport; however, the airplane was “fast and floated.” The airplane touched down midfield, departed the end of the runway, and encountered a tree line, substantially damaging the left wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. After the accident, the pilot stated he “believe[d] the aircraft ran out of fuel due to several unforeseen and unplanned delays.”
Probable cause
The pilot's improper fuel planning, which resulted in a total loss of engine power due to fuel exhaustion, an emergency landing, and runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA264
- Event ID
- 20220609105227
- Case number
- ERA22LA264
- 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: 0e75e366601d849c0044d2dcf2a4f8c01fd2ee969699d285abd09b5c1ff11f6f; retrieved 2026-09-16T15:18:42.303Z.