WPR25FA169 · Cessna 414
Cessna 414 · Accident during initial climb
From an unrecorded airport to Phoenix Sky Harbor International Airport (PHX)
Event
- NTSB case
- WPR25FA169
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Ongoing
- API-reported fatalities
- 6 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Cessna 414
- Aircraft type
- Cessna 414
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N414BA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Phoenix Sky Harbor International Airport (PHX), Phoenix, AZ
- Aircraft age
- About 55 years (built 1970)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Initial climb
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Unknown or undetermined
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB 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.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record WPR25FA169
- Event ID
- 20250609200282
- Case number
- WPR25FA169
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 72c49cb6c581e3b03c79668aff0362a886d170c0a03875b9ca3c5bf54d3ada12; retrieved 2026-09-15T09:05:30.662Z.