# NTSB WPR25FA169: Cessna 414, N414BA, San Diego, CA, June 8, 2025 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Preliminary report - Date: June 8, 2025, 12:30 local (19:30 UTC) - Place: San Diego, CA · In water - Coordinates: 32.695711, -117.28911 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.6957&lon=-117.2891&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) - Highest injury: Fatal - Injuries: 6 fatal - Status: Investigation ongoing - Investigation class: Class 3 - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 200282 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR25FA169 - NTSB preliminary report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200282/pdf - Page: https://openairdocs.org/ntsb/WPR25FA169 ## Preliminary report 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 fourapproaches 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. ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) (defining event); cases with it: [Cessna 414, 1 case](https://openairdocs.org/ntsb-events/000/sequence.md?model=2075908), [All aircraft, 1,703 cases](https://openairdocs.org/ntsb-events/000/sequence.md) ## Aircraft - Registration: [N414BA](https://openairdocs.org/aircraft/N414BA), registered now, S/N 414-0047, built 1970 (OpenAirDocs) - Reported make and model: CESSNA 414 - Registry model: [Cessna 414](https://openairdocs.org/model/cessna-414) (registry code 2075908) (OpenAirDocs) - Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 414-0047 - Year built: 1970 - Airframe hours: 9610 - Damage: Substantial damage - Flight: Business, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, December 3, 2024 - Destination: PHX, Phoenix, AZ - Flight plan: IFR - Airport: SAN, San Diego Intl - Equipment: ADS-B, Electronic flight bag or handheld device ## Weather - Conditions: Instrument (IMC), Day - Wind: 320° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: 1,000 ft overcast - Temperature: 64 °F, dew point 57 °F - Altimeter: 29.99 inHg - Observed at: KNZY, 4 nm away - METAR: KNZY 081852Z 32009KT 10SM OVC010 18/14 A2999 RMK AO2 SLP154 T01780144 ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20250608006219A](https://openairdocs.org/incident/20250608006219A), Jun 8, 2025: Cessna 414, San Diego, CA, Destroyed, 6 fatal. On the day of the accident the pilot filed an IFR flight plan on his ipad through foreflight. He phoned CFI because he wasn’t sure about the procedure.… ## Other investigations on N414BA (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB CHI78FET05](https://openairdocs.org/ntsb/CHI78FET05), Dec 8, 1977: Cessna 414 (N414BA), Valparaiso, IN, substantial damage From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.