FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Air Z Flying Services Cessna 310 R accident

13 Oct 2022 · Middlefield, OH, United States

Cessna 310 R · Accident: fuel exhaustion en route

From Morristown Municipal Airport (MMU) to Cuyahoga County Airport (CGF)

Report a problem

Event

NTSB case
ERA23LA018
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
Event fatalities
Unknown
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
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Cessna 310 R

Aircraft type
Cessna 310
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
N62368
Onboard fatalities
Unknown
Route
From Morristown Municipal Airport (MMU), Morristown, NJTo Cuyahoga County Airport (CGF), Richmond Heights, OH
Aircraft age
About 47 years (built 1975)
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 135: Air Taxi & Commuter
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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot departed on the fifth and final leg of the evening’s flights with no cargo and an unknown quantity of fuel. He reported that he had to deviate due to weather along the route of flight, and that the right engine began running rough after reaching cruise altitude. About 2.2 hours into the planned 2-hour flight, and about 25 miles from the destination airport, both of the airplane’s engines began “surging” and eventually “stopped producing power.” The pilot stated that he looked at the fuel gauges and they indicated empty. The pilot completed a forced landing to horse pastures, during which the airplane impacted fences, resulting in substantial damage to the wings and the fuselage. There was no evidence of fuel, fuel spillage, or odor of fuel at the scene. The pilot stated that the accident flight was longer than planned due to headwinds and weather diversions. The pilot also explained that there were known discrepancies with the fuel gauges. He also described that there had been a difference between the amount of fuel he requested at one fuel stop, what was actually dispensed, and the total amount he believed was on board when he departed on the accident flight, as he did not get a receipt, or confirm the amount dispensed. Based on the pilot’s own fuel planning numbers, full tanks at initial departure, and the fuel purchased at 2 of his 4 stops, the airplane had a fuel endurance of about 6.8 hours, of which .8 hours was for IFR reserve minimums. The total time of the 5 legs was approximately 7.2 hours.

Probable cause

The pilot’s inadequate fuel planning and inflight fuel management which resulted in exhaustion of his fuel supply and a forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23LA018
Event ID
20221013106123
Case number
ERA23LA018
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, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: c910b152d85bb0bc109eb5ea83b7aaa291402b59ff4992ad1a2d763bc6cfd83d; retrieved 2026-09-16T16:16:40.780Z.