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

June 8, 2025 · Cessna 414 · N414BA

San Diego, CA

Overview

Report Status
Factual report
Event Type
Accident
Date
June 8, 2025
Injury Outcomes
6 injuries (6 fatalities)
Location
San Diego, CA
Aircraft
Cessna 414 (1970)
Tail Number
N414BA
Injuries
Fatal
Aircraft Damage
Substantial
NTSB Number
WPR25FA169

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.

Full Narrative

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.

Flight

Event TypeAccident
Event Time12:30 PDT
Nearest AirportSan Diego Intl (0nm WSW)
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 414
Tail NumberN414BA
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines2
Seats7

People & Injuries

Injury Summary6 injuries (6 fatalities)
Fatal6
Serious0
Minor0
Uninjured0
Total6

Conditions

ConditionsIMC
LightDaylight
Wind320° @ 9 kt
Visibility10 sm
CeilingOvercast 1000 ft
Temperature / Dew Point64 F / 57 F
Altimeter29.99 inHg
Observation Time11:52

Appendix: Source Data