Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

October 13, 2022 · Cessna 310 R · N62368

Middlefield, OH

Overview

Report Status
Probable Cause
Event Type
Accident
Date
October 13, 2022
Injury Outcomes
No injuries (1 uninjured)
Location
Middlefield, OH
Aircraft
Cessna 310 R (1975)
Tail Number
N62368
Operator
Air Z Flying Services
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA23LA018

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.

NTSB Probable Cause

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

Full 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.

Flight

Event TypeAccident
Event Time05:30 EDT
Nearest Airport0nm
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 310 R
Tail NumberN62368
Aircraft CategoryAir
DamageSubstantial
OperatorAir Z Flying Services
Operating RulePart 135
Engines2
Engine TypeReciprocating
Engine DetailsContinental · IO-520-MB · Reciprocating · 285 | Continental · IO-520-MB · Reciprocating · 285
Seats2

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 66 · First Class · None

Conditions

ConditionsIMC
LightNight
WindCalm
Visibility10 sm
CeilingBroken clouds 1000 ft
Temperature / Dew Point54 F / 52 F
Altimeter29.66 inHg
Observation Time05:35
Weather SourceWFAC

Appendix: Source Data