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

December 29, 2018 · Cessna 152 No Series · N6202M

Horseshoe Bay, TX

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
December 29, 2018
Injury Outcomes
2 injuries (2 minor injuries)
Location
Horseshoe Bay, TX
Aircraft
Cessna 152 No Series (1980)
Tail Number
N6202M
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
CEN19LA064

The commercial pilot was conducting a personal, cross-country flight with one passenger onboard. The pilot reported that, about 2 1/2 to 2 3/4 hours into the flight, the engine started to lose power. The pilot contacted air traffic control for vectors to the nearest airport. The pilot then checked the gauges and applied carburetor heat. The engine initially responded; however, a few minutes later, the engine lost all power, and the pilot's additional attempts to restore power were unsuccessful. The pilot did not think that the airplane could reach the nearest airport, so he established a glide for an off-airport forced landing, during which the airplane impacted trees and terrain and sustained substantial damage. During recovery of the airplane wreckage, the fuel tanks were found intact and empty. Additionally, there was no evidence of fuel leakage on the ground. The pilot reported that the airplane ran out of fuel and that the accident could have been prevented by better calculation and review of distance, fuel, and time in flight.

NTSB Probable Cause

The pilot's inadequate preflight and in-flight fuel planning, which resulted in the total loss of engine power due to fuel exhaustion.

Full Narrative

On December 28, 2018, about 2015 central standard time, a Cessna 152 airplane, N6202M, impacted terrain after a loss of engine power en route to Kelly Field Airport (KSKF), San Antonio, Texas. The pilot and one passenger received minor injuries, and the airplane was substantially damaged during a forced landing. The airplane was registered to and operated by Flyokair, LLC, under the provisions of Title 14 Code of Federal Regulations Part 91 as personal flight. Night visual meteorological conditions prevailed at the time of the accident. The airplane departed Shawnee, Oklahoma, about 1655. The pilot reported that he had been airborne about 2 hours, and that he should reach his destination airport in about 15 minutes. About 30-45minutes later, he stated the engine started to lose power. He contacted air traffic control for vectors to the nearest airport. The pilot then looked at the gauges; oil pressure, oil temperature, and fuel gauges, which indicated the following: left fuel gauge ½ and right gauge less than ½. He added that he might have to land on the highway, since he didn't think he could make an airport. In an attempt to restore engine power, the pilot applied carburetor heat, the engine responded, and he was able to climb and gain altitude. Since the engine responded after he applied carburetor heat, he thought the engine may have experienced carburetor icing. A few minutes later, the engine lost power, and additional attempts to restore power were unsuccessful. He established a glide and picked out terrain for the forced landing. The airplane then impacted trees and terrain. The airplane recovery crew noted that the airplane was substantially damaged during the accident. The fuel tanks were empty and no evidence that fuel had leaked onto the ground. They added the fuel tanks had not been breached during the accident. On the NTSB's 6120 form, Pilot/Operator Aircraft Accident/Incident Report, under the section: Recommendation (How could this accident/incident have been prevented?). The pilot noted (in part): Better calculation and review of distance, fuel in time, and time in flight. During a follow-up conversation with a Federal Aviation Administration (FAA) inspector, the pilot did not clarify how he checked the fuel tanks before departure; however, he didn't add fuel before departure. The pilot added that he had talked with the airplane's owner and admitted he ran of fuel.

Flight

Event TypeAccident
Event Time20:15 CST
Nearest Airport0nm
Flight Plan FiledVFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 152 No Series
Tail NumberN6202M
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-235 SERIES · Reciprocating · 110
Seats2

People & Injuries

Injury Summary2 injuries (2 minor injuries)
Fatal0
Serious0
Minor2
Uninjured0
Total2
Crew 1Age 32 · Third Class · Minor

Conditions

ConditionsVMC
LightNight
Wind30° @ 4 kt
Visibility10 sm
CeilingOvercast 6000 ft
Temperature / Dew Point43 C / 32 C
Altimeter30.21 inHg
Observation Time04:15
Weather SourceWFAC

Appendix: Source Data