Regulations & Safety
NTSB Releases Preliminary Report on San Diego Cessna Citation Crash
Cessna S550 crash near MYF airport under investigation: night IMC approach, equipment issues, and altitude deviations cited in NTSB preliminary findings.
On May 22, 2025, a Cessna Citation S550, registered as N666DS, crashed in a residential neighborhood near Montgomery-Gibbs Executive Airport (MYF) in San Diego, California, claiming the lives of the pilot and five passengers. Eight people on the ground sustained minor injuries. The National Transportation Safety Board (NTSB) has released a preliminary report (WPR25FA161) detailing the circumstances surrounding the accident, which occurred during a night approach under instrument meteorological conditions (IMC). This article provides a comprehensive overview of the incident based on the NTSB’s findings, which remain subject to change as the investigation progresses.
The accident occurred at approximately 3:47 a.m. Pacific Daylight Time (PDT) during a Part 91 personal flight operated by DAVIATOR LLC. The Cessna S550, a twin-engine business jet, departed Teterboro Airport (TEB) in New Jersey on May 21 at around 8:09 p.m. PDT. The flight made a scheduled stop at Colonel James Jabara Airport (AAO) in Wichita, Kansas, where it was refueled with 548 gallons of Jet-A fuel. The aircraft departed Wichita at approximately 12:36 a.m. PDT on May 22, bound for MYF, a tower-controlled airport during daytime hours but uncontrolled at the time of the accident. The flight was conducted under Instrument Flight Rules (IFR), and the pilot communicated with Southern California Terminal Radar Approach Control (SOCAL TRACON) as the aircraft approached San Diego. The pilot, who was based at MYF and held an exemption to fly the Cessna S550 single-pilot since December 15, 2024, requested the RNAV (GPS) instrument approach to Runway 28R. The pilot did not specify whether he intended to fly the localizer performance with vertical guidance (LPV) or lateral navigation (LNAV) approach.
As the aircraft descended toward MYF, the pilot was informed by the SOCAL TRACON controller that the Automated Surface Observing System (ASOS) at MYF was out of service. The pilot acknowledged this and requested weather information for MYF. The controller provided conditions from Marine Corps Air Station Miramar (NKX), located approximately 4 miles north of MYF, reporting calm winds, ½-mile visibility, and an indefinite 200-foot ceiling, indicative of challenging IMC conditions. The controller cleared the aircraft to the NESTY approach fix at 9,000 feet mean sea level (msl) and later instructed the pilot to cross NESTY at or above 3,800 feet msl for the RNAV approach to Runway 28R. The pilot discussed alternate airport options with the controller in case a missed approach was necessary but did not select an alternate during the flight.
Automatic Dependent Surveillance-Broadcast (ADS-B) data revealed the aircraft’s descent and approach. At NESTY, the aircraft was at approximately 3,750 feet msl with a ground speed of 200 knots (191 knots calibrated airspeed, KCAS). By the final approach fix, PENYY, at 3:44:50 a.m., the aircraft was at 2,450 feet msl with a ground speed of 175 knots (167 KCAS). The pilot announced his position on MYF’s common traffic advisory frequency, stating he was 3 miles from the runway, and attempted to activate the pilot-controlled runway lighting by keying the microphone seven times. The aircraft crossed the PALOS waypoint, 2.9 nautical miles from the Runway 28R displaced threshold, at 1,190 feet msl, below the published minimum crossing altitude of 1,380 feet msl, with a ground speed of 120 knots (117 KCAS). The ADS-B data ceased at 3:46:47 a.m., when the aircraft was at 464 feet msl, approximately 60 feet above ground level (AGL).
The first identified point of contact (FIPC) was with power transmission lines approximately 90–95 feet above the ground (about 500 feet msl), located 1.8 nautical miles from the Runway 28R displaced threshold. The impact severed portions of the left horizontal stabilizer, left elevator, and vertical stabilizer, which were found 200 feet downrange. The debris field extended 1,200 feet across brush-covered terrain and a residential neighborhood, on a magnetic heading of approximately 300 degrees. The main wreckage, consisting of the thermally damaged cabin, engines, and left wing, came to rest on a residential street 1.6 nautical miles from the runway threshold. The crash impacted one residential structure and damaged or destroyed 20 vehicles due to impact forces and a post-impact fire. Eight people on the ground sustained minor injuries. The wreckage was relocated to a secure facility for further examination.
The Cessna S550, a Category B aircraft for instrument approach procedures, was not equipped with a flight data recorder (FDR) but had a cockpit voice recorder (CVR), which was recovered and sent to the NTSB Vehicle Recorders Laboratory for analysis. The left and right engine Full Authority Digital Engine Control (FADEC) units were also retained for data extraction. A Notice to Airmen (NOTAM) indicated that the Runway Alignment Indicator (RAI) lights at MYF had been out of service since March 28, 2022, due to delays in repairs pending an environmental study. However, all other runway lighting was operational at the time of the accident.
The RNAV (GPS) Runway 28R approach minimums for Category B aircraft included:
The NTSB’s preliminary report highlights several critical factors that may have contributed to the accident. The aircraft’s descent below the minimum crossing altitude at PALOS suggests a possible deviation from the approach profile. The low visibility and indefinite ceiling, combined with the inoperative ASOS and RAI lights, likely compounded the challenges of executing a night instrument approach at an uncontrolled airport. The pilot’s attempt to activate runway lighting indicates awareness of the need for visual cues, but the aircraft’s low altitude at the FIPC suggests it was significantly below the intended glide path.
The investigation, led by NTSB Investigator in Charge Daniel Baker, is ongoing. Additional participating persons include representatives from the Federal Aviation Administration (FAA), Textron Aviation (the manufacturer of the Cessna S550), and Williams International (the engine manufacturer). The CVR and FADEC data are expected to provide further insight into the pilot’s actions and the aircraft’s performance during the approach. The NTSB has classified this as a Class 3 investigation, and a final report will be issued upon completion, which could take months or years. The crash’s impact on a residential neighborhood underscores the risks of low-altitude operations near populated areas. The destruction of a home and 20 vehicles, along with minor injuries to eight residents, has raised concerns about the safety of flight paths over urban environments. Montgomery-Gibbs Executive Airport, located in a densely populated area of San Diego, serves as a hub for general aviation, and this incident may prompt renewed scrutiny of its operations, particularly during nighttime and low-visibility conditions.
The preliminary report does not assign a cause, but the data suggest potential issues with approach execution, situational awareness, or environmental factors. The aviation community will closely monitor the investigation’s findings, which could lead to recommendations for improved training, equipment, or procedures for single-pilot operations in challenging conditions.
The tragic loss of six lives in the Cessna Citation S550 crash near San Diego is a sobering reminder of the complexities and risks of aviation, particularly in adverse weather and at night. The NTSB’s preliminary report provides a detailed account of the flight’s final moments, but many questions remain unanswered. As the investigation continues, the focus will be on understanding the factors that led to this accident and identifying measures to prevent similar tragedies in the future. For now, the San Diego community mourns the loss and grapples with the aftermath of an incident that has left an indelible mark.
Note: This article is based on preliminary information from NTSB report WPR25FA161, which is subject to change as the investigation progresses.
Flight Details and Timeline
Weather Challenges and Approach
The Crash and Its Aftermath
Aircraft and Equipment
Preliminary Observations and Ongoing Investigation
Community Impact and Safety Implications
Conclusion
Sources
Photo Credit: The Hollywood Reporter