WPR25LA212

NTSB accident investigation · Cessna T240 · San Diego, CA · July 13, 2025

Accident · FatalClass 4 · LimitedFinal report
Date
July 13, 2025, 16:29 local (23:29 UTC)
Place
San Diego, CA · 470 nm west of SAN in the Pacific Ocean
Injuries
1 fatal
Phase of flight
Enroute
Aircraft
N636CSCessna T240
Defining event
Enroute-cruise: Unknown or undetermined
Weather
Visual (VMC) · Day
Status
Completed · report May 14, 2026
Report
Approved by Office Director
Investigation class
Class 4 - Basic report with no Prelim publish
NTSB office
Western Pacific Region
Parties
Federal Aviation Administration
FAA report
20250713007749A
Case key
200551

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

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

Findings · 1

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Not determinedNot determined › Not determined · Unknown/Not determinedCessna T240: 1 caseAll aircraft: 2,247 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

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.

Aircraft

Registration
N636CS
Reported as
Cessna T240
Category
Airplane
Serial number
T24002046
Built
2014
Airframe hours
1,225
Engine
Cont Motor TSIO-550-C, 310 horsepower, reciprocating
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · July 1, 2025
Departed
RMN · Ramona, CA
Destination
MYF · San Diego, CA
Equipment
Unknown

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
67
Injuries
Unknown
Certificates
Commercial, Flight instructor
Airplane ratings
Single-engine land, Single-engine sea
Instrument ratings
Airplane
Medical
Class 3, With waivers/limitations
Last flight review
September 25, 2023
Flight hours
3,300 total

Weather

Conditions
Visual (VMC) · Day
Wind
Calm
Visibility
10 statute miles
Lowest ceiling
1,100 ft overcast
Temperature
66 °F, dew point 59 °F
Altimeter
29.98 inHg
Observed at
KMYF
METAR
KMYF 130853Z AUTO 00000KT 10SM OVC011 19/15 A2998 RMK AO2 SLP149 T01890150 58005

Docket · 6

The files NTSB released with the investigation on May 14, 2026, on NTSB’s docket system: statements, records, photos and specialists’ reports. 15.8 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.