Cessna T240 accident near San Diego, California, July 13, 2025
On July 13, 2025 at about 11:29 pm local time, a 2014 Cessna T240, registered N636CS, was involved in an accident during enroute (cruise) near San Diego, California. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Impact with the ocean for reasons that could not be determined because the pilot and airplane were not located.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 13, 2025 · about 11:29 pm local time · cases in 2025
- Place
- San Diego, California · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna T240, built 2014 · all T240s on the register
- Registration
- N636CS · registry record · serial T24002046
- Damage
- Damage not recorded
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Unknown or undetermined during enroute (cruise) defining event
- Missing aircraft during unknown
The NTSB's findings
- Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Certificate: flight instructor, commercial pilot
- Ratings: single-engine land; single-engine sea; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 3,300 hours in all
- Last flight review: September 25, 2023
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: unk
- Injury: unkn
The aircraft
- Airframe total time: 1,225 hours
- Last inspection: annual inspection, July 1, 2025
- Seats: 4
- Landing gear: retractable
- Engine: Cont Motor TSIO-550-C (piston); 1,225 hours total
The flight
- Departed from: RMN Ramona CA at 8:50 pm
- Destination: MYF San Diego CA
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: overcast at 1,100 ft; clear
- Temperature: 66°F (19°C), dew point 59°F (15°C)
- Altimeter: 29.98 inHg
- Observation at 1:53 am from KMYF
Weather report (METAR): KMYF 130853Z AUTO 00000KT 10SM OVC011 19/15 A2998 RMK AO2 SLP149 T01890150 58005
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
6 documents, released by the NTSB on May 14, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Witness Statements | PDF, 4 pages · our copy | View Download |
| 2 | Excerpt FAA Accident Package Flight Summary | PDF, 9 pages · our copy | View Download |
| 3 | Maintenance Records | PDF, 7 pages · our copy | View Download |
| 4 | ADS-B Data (Kmz File) | map file · our copy | Download |
| 5 | ADS-B Data | spreadsheet · our copy | Download |
| 6 | Flight Path (ADS-B Plot) | PDF, 1 page · our copy | View Download |
Connections how this case links to the rest of the register
- N636CS on the register today · the tail number may have moved to another aircraft since
- Cessna T240 135 registered today · the model family and its accident history
- Cessna 72,677 aircraft on the register
- Engine: Cont Motor TSIO-550-C 479 aircraft carry this series today · as the NTSB recorded it
- Washington Exec/Stafford Regional · departed from
- Montgomery-Gibbs Executive · bound for
- Accidents and incidents in California 9,080 since 1982 · 1,094 in the last ten years
- California 28,286 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR25LA212.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
