Cessna 414 accident near San Diego, California, June 8, 2025
On June 8, 2025 at about 7:30 pm local time, a 1970 Cessna 414, registered N414BA, was substantially damaged in an accident during initial climb near San Diego, California (San Diego Intl airport). It was a business flight under general aviation rules (Part 91). 6 people were killed. The weather was instrument conditions (cloud, fog or low visibility).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 8, 2025 · about 7:30 pm local time
- Place
- San Diego, California · San Diego Intl · map
- Type
- Accident
- Injuries
- 6 people were killed.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Cessna 414, built 1970 · all 414s on the register
- Registration
- N414BA · registry record · serial 414-0047
- Damage
- Substantial damage
- Flight
- Business flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On June 08, 2025, at 1230 Pacific daylight time, a Cessna 414A, N414BA, was substantially damaged when it was involved in an accident in San Diego, California. The pilot and five passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 business flight. The day before the accident, the pilot and passengers flew from Phoenix, Arizona, to San Diego. The accident flight was intended to return to Phoenix. The exact radio communication times could not be confirmed for the accident flight. The pilot received an instrument flight rules (IFR) clearance and was issued the BRDR7 (Border 7) departure. The published BRDR7 Standard Instrument Departure (SID) with a takeoff from runway 27 consisted of a “climb on heading 278° until PYG [Poggi VORTAC] 19 DME, then left turn on heading 123° to intercept PGY VPRTAC R-260 and R-069 to BROWS INT.” After departing from runway 27, the pilot made a radio communication to SOCAL departure that he was at 1,600 ft, and shortly thereafter, the controller instructed him to make a left, 180° turn. The airplane began a gradual turn, and after climbing to about 2,000 ft, it made a steep descent to 200 ft. The controller issued the pilot a low altitude alert and instructed him to climb to 4,000 ft immediately to which the pilot replied by repeating the instructions. The controller then asked if he needed any assistance and queried him as to the nature of the problem. The pilot stated that he was “struggling” to try to maintain the airplane on a heading and climb. In response, the controller told him of the closest airport that was one mile away and asked him if he could see it. The pilot responded that he did not see the airport and made a series of erratic maneuvers before making several mayday calls (see figure 1 below). Figure 1: Airplane’s flight path with the pictorial approach procedure A video captured the airplane descending before climbing back into the cloud layer, where it subsequently disappeared from view (see figure 2 below). Figure 2: Flight path and composite video graphic showing the airplane climbing into the cloud layer A police helicopter was ten miles east of the accident site when the flight crew received a request to search for any signs of an airplane impacting the water. In a post-accident interview, the helicopter pilot stated that he estimated the cloud bases at roughly 800 feet in numerous areas, with the highest layer near 1,600 ft (although a majority of the clouds were lower). Upon reaching the search area, he located an oil slick approximately two miles offshore. The accident airplane’s regular pilot, who was also a friend of the accident pilot, stated that he had flown about 50 hours with the accident pilot in the airplane. He stated that two days prior to the accident, the accident pilot flew solo up to Springerville, Arizona. The friend then boarded the airplane and acted as a safety pilot for the accident pilot as he conducted four approaches in simulated instrument meteorological conditions. He recalled that the pilot used a Garmin 430 and iPad with ForeFlight for navigation and was accustomed to hand-flying the airplane, which had no autopilot or glass cockpit. He noted that the pilot had expressed some nervousness about the busy southern California airspace, but appeared to be proficient during their review of the San Diego departure procedure.
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 initial climb defining event
The aircraft
- Airframe total time: 9,610 hours
- Last inspection: 100-hour inspection, December 3, 2024
- Seats: 7
- Landing gear: retractable
The flight
- Destination: PHX Phoenix AZ
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 320° at 9 knots
- Visibility: 10 statute miles
- Sky: overcast at 1,000 ft; a few clouds
- Temperature: 64°F (18°C), dew point 57°F (14°C)
- Altimeter: 29.99 inHg
- Observation at 11:52 am from KNZY, 4 miles away
Weather report (METAR): KNZY 081852Z 32009KT 10SM OVC010 18/14 A2999 RMK AO2 SLP154 T01780144
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flig | 1 | |||
| Passengers | 5 |
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number WPR25FA169.
