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

July 13, 2025 · Cessna T240 · N636CS

San Diego, CA

Overview

Report Status
Probable Cause
Event Type
Accident
Date
July 13, 2025
Injury Outcomes
1 injury (1 fatality)
Location
San Diego, CA
Aircraft
Cessna T240 (2014)
Tail Number
N636CS
Injuries
Fatal
Aircraft Damage
Unknown
NTSB Number
WPR25LA212

A family friend reported the pilot and airplane missing. The friend stated that they drove the pilot to the departure airport, dropped him off and were meeting him at the intended destination airport. The friend became concerned when the pilot did not arrive and she began to track his location on via a commercial sourced ADS-B system. She also attempted to text him but noted that her messages were not being received by the pilot’s cell phone. Review of the recorded communication between the air traffic controller local controller at the destination airport and the accident pilot revealed that the controller had issued landing instructions for a straight-in approach to runway 28R, which the pilot acknowledged. The controller made repeated attempts to reestablish communication with the pilot; however, no further radio communication from the pilot was received. ADS-B data showed that the airplane’s flight track was consistent for an approach to landing on runway 28 at the destination airport, however, the airplane continued on a southwesterly heading for about 470 nautical miles until the ADS-B data was lost. An Alert Notice (ALNOT) was issued about 16 minutes after ADS-B contact had been lost and a search for the pilot and airplane commenced. Neither the pilot or airplane were located. Land and sea-based searches were suspended 2 days after the airplane went missing.

NTSB Probable Cause

Impact with the ocean for reasons that could not be determined because the pilot and airplane were not located.

Full Narrative

A family friend reported the pilot and airplane missing. The friend stated that they drove the pilot to the departure airport, dropped him off and were meeting him at the intended destination airport. The friend became concerned when the pilot did not arrive and she began to track his location on via a commercial sourced ADS-B system. She also attempted to text him but noted that her messages were not being received by the pilot’s cell phone. Review of the recorded communication between the air traffic controller local controller at the destination airport and the accident pilot revealed that the controller had issued landing instructions for a straight-in approach to runway 28R, which the pilot acknowledged. The controller made repeated attempts to reestablish communication with the pilot; however, no further radio communication from the pilot was received. ADS-B data showed that the airplane’s flight track was consistent for an approach to landing on runway 28 at the destination airport, however, the airplane continued on a southwesterly heading for about 470 nautical miles until the ADS-B data was lost. An Alert Notice (ALNOT) was issued about 16 minutes after ADS-B contact had been lost and a search for the pilot and airplane commenced. Neither the pilot or airplane were located. Land and sea-based searches were suspended 2 days after the airplane went missing.

Flight

Event TypeAccident
Event Time16:29 PDT
Nearest Airport0nm
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna T240
Tail NumberN636CS
Aircraft CategoryAir
DamageUnknown
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsCont Motor · TSIO-550-C · Reciprocating · 310
Seats4

People & Injuries

Injury Summary1 injury (1 fatality)
Fatal1
Serious0
Minor0
Uninjured0
Total1
Crew 1Age 67 · Third Class · Unkn

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingOvercast 1100 ft
Temperature / Dew Point66 F / 59 F
Altimeter29.98 inHg
Observation Time01:53
Weather SourceWFAC

Appendix: Source Data