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.
Flight Details and Timeline
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.
Weather Challenges and 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 Crash and Its Aftermath
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.
Aircraft and Equipment
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:
- an LPV decision altitude (DA) of 673 feet (250 feet AGL with ¾-mile visibility),
- an LNAV/VNAV DA of 750 feet (327 feet AGL),
- and an LNAV minimum descent altitude (MDA) of 840 feet (417 feet AGL).
Preliminary Observations and Ongoing Investigation
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.
Community Impact and Safety Implications
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.
Conclusion
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.
Sources
Photo Credit: The Hollywood Reporter
Regulations & Safety
FAA Proposes Torque Inspection AD for 980 Airbus Helicopters
FAA NPRM targets AS350, AS355, and EC130 helicopters over a nut retainer coating flaw that risks main rotor servo-control disconnection.
This is original reporting and analysis by AirPro News.
The Federal Aviation Administration (FAA) has proposed a new airworthiness directive (AD) mandating torque inspections on the main rotor servo-controls of 980 Airbus Helicopters AS350, AS355, and EC130 aircraft registered in the United States.
Published as a Notice of Proposed Rulemaking (NPRM) on October 19, 2026, the regulatory action addresses a mechanical vulnerability where paint or protective coating on a nut retainer can cause a loss of tightening torque. If left undetected, the FAA warns this condition could lead to the disconnection of the upper ball bearing end from the main rotor (MR) servo-control. Such a failure would result in a complete loss of helicopter control.
Inspection requirements and compliance timelines
The proposed directive targets specific members of the Airbus Helicopters Ecureuil family. The affected models include the AS350B3, AS355F, AS355F1, AS355F2, AS355N, AS355NP, EC130B4, and EC130T2 helicopters. Under the FAA proposal, operators must perform an initial inspection of the nut tightening torque on the upper ball bearing end of all MR servo-controls within 165 flight hours or six months, whichever occurs first.
The NPRM also outlines strict requirements for follow-up inspections to ensure ongoing safety. Any time an MR servo-control featuring an affected part is installed or reinstalled on an aircraft, maintenance personnel must conduct a subsequent torque check. This secondary inspection must take place between two and 10 flight hours after the installation is complete.
The FAA is accepting public comments on the NPRM through December 3, 2026. Following the closure of the comment period, the agency is expected to review industry feedback and issue a final rule mandating the inspections. The current regulatory action is classified as an interim measure. Airbus Helicopters is actively developing a permanent design change to the nut retainer that will eliminate the problematic paint or protective coating entirely, which will likely prompt further regulatory updates once certified.
Tracing the servo-control vulnerability
The engineering investigation that led to the current NPRM originated with a different Airbus Helicopters product line. In 2024, the European Union Aviation Safety Agency (EASA) received reports of two separate instances where torque was lost between the upper ball bearing end and the MR servo-control on Dauphin and EC155 helicopters. In one of those documented cases, the components completely disconnected in flight.
That discovery prompted EASA to issue an AD for the Dauphin family on June 6, 2024. The FAA subsequently mirrored that action with its own directive for U.S.-registered Dauphin helicopters on July 10, 2025. Following those initial reports, Airbus Helicopters launched a broader engineering analysis to determine the root cause of the torque loss. The manufacturer concluded that the presence of paint or protective coating on the lock washer and nut retainer compromised the friction required to maintain proper tightening torque over time.
During this investigation, the manufacturer determined that the AS350, AS355, and EC130 families share this exact design vulnerability in their main rotor flight control systems. In response to these findings, Airbus Helicopters issued Alert Service Bulletins on April 1, 2026, mandating torque checks across the affected Ecureuil fleet. EASA followed up by issuing AD 2026-0132 on July 8, 2026, to mandate the inspections for European operators. The FAA publication of the NPRM on October 19, 2026, aligns U.S. regulations with the European mandates.
Market context and fleet impact
The Airbus Helicopters Ecureuil family, currently marketed under the H125 and H130 designations, represents one of the most successful light utility helicopter programs in aviation history. Airbus Helicopters has delivered more than 7,200 Ecureuil family aircraft worldwide.
The large number of affected U.S. aircraft reflects the heavy utilization of the type across the country. The AS350 and EC130 platforms are heavily utilized across the aviation industry for critical missions, including law enforcement, emergency medical services, aerial firefighting, powerline maintenance, and passenger transport. The 980 helicopters of U.S. registry represent a significant portion of the active domestic rotorcraft fleet.
AirPro News analysis
The sheer volume of U.S.-registered aircraft affected by this NPRM highlights the industry reliance on the AS350 and EC130 platforms. With 980 airframes requiring initial and recurring torque checks, maintenance providers and fleet operators will need to carefully schedule these inspections to avoid grounding critical public service assets. Because the FAA 165-hour compliance window is relatively short for high-utilization operators like air medical and police units, we expect a rapid mobilization of maintenance personnel once the final rule is published. The recurring inspection requirement for newly installed parts will also add a layer of logistical complexity for maintenance, repair, and overhaul facilities until Airbus Helicopters can field its permanent hardware redesign.
Photo Credit: Airbus
Regulations & Safety
Istanbul to Host International Aviation Law Conference on Sanctions, Drones and AI
Hudson Morgan Williams’ International Aviation Law Conference, November 5–6, 2026, features former ICAO Council President Salvatore Sciacchitano as keynote speaker and six panels ranging from arbitration to eVTOLs.
The International Aviation Law Conference will take place in Istanbul, Türkiye, on November 5–6, 2026, bringing together aviation lawyers, regulators, academics and airline and airport executives. The event opens with an invitation-only gala dinner on Thursday, November 5, followed by a full conference day at the Çırağan Palace Kempinski on Friday, November 6. The organisers expect more than 300 attendees and more than 20 speakers.
The conference is organised by Hudson Morgan Williams, a London-based law firm, which describes it as the first Aviation Law Conference in Istanbul. AirPro News is a media partner of the conference.
Six panels, from arbitration to eVTOLs
The conference day opens with a panel on the future of aviation law and the role of arbitration courts, covering aircraft lease and financing disputes, aviation insurance and liability, and contract enforcement. A second panel looks at sanctions and their impact on aviation, including leasing and finance, compliance and jurisdictional challenges. A third turns to the integration of drones into global airspace, from defence and border-security drones to unmanned traffic management and passenger drones.
After the networking lunch, Salvatore Sciacchitano gives the keynote speech at 13:50. The afternoon panels cover how AI will shape the future of aviation, including liability, insurance and regulation; how smart airports and cost-effective airlines can make aviation cheaper to operate; and urban air mobility and eVTOL aircraft, with certification, vertiport regulation, passenger rights, insurance and noise on the agenda.
The organisers note that the programme and speakers are subject to change, and the line-up for each panel has not been announced yet.
Speakers
Sciacchitano led the ICAO Council from 2020 to 2025, a period that included the adoption of the long-term goal of net-zero carbon emissions for international aviation by 2050. He previously served as Executive Secretary of the European Civil Aviation Conference (ECAC) and as Deputy Director General of ENAC, Italy’s civil aviation authority, and is now an ICAO Goodwill Ambassador.
Güliz Öztürk has been CEO of Pegasus Airlines since 2022, after serving as the airline’s Chief Commercial Officer from 2010.
Speakers listed on the conference website also include:
- Selahattin Bilgen, CEO of İGA Istanbul Airport
- Utku Coşar, independent arbitrator and Vice President of the LCIA Court
- Prof. Dr. Elmar Giemulla, professor of aviation law and attorney in Berlin and New York
- Prof. Francesca Pellegrino, Professor of Air and Space Law at the University of Messina
- Haydar Yalçın, former Deputy Director General of Türkiye’s Directorate General of Civil Aviation
- Tasman Tam, barrister in Hong Kong
- Afgan Bakhishov, Advisor to the Chairman of Azerbaijan Airlines
- Mesut Yılmaz, eVTOL Program Director at Gözen Holding
Pegasus Airlines and Corendon Airlines are among the conference’s sponsors, alongside the Turkic Arbitration Association, the International Institute of Air and Space Law at Leiden University, Özyeğin University and Studio Legale Pierallini, with Argela as a supporter.
Why Istanbul
Istanbul is the home base of Turkish Airlines and Pegasus Airlines, and İGA Istanbul Airport ranks among Europe’s busiest airports. The city will also host the Istanbul Aviation Forum on April 27–28, 2027.
How to attend
Tickets for the conference day cost €250 per attendee, and the gala dinner is by invitation only. The full programme, speaker list and registration are available on the International Aviation Law Conference 2026 website.
The conference is also listed in the AirPro News Aviation & Aerospace Events Calendar 2026–2027.
Photo Credit: Hudson Morgan Williams
Regulations & Safety
FAA Proposes Pilot Dashboard for AWOS and ASOS Outage Reports
The FAA seeks public comments on a Surface Weather Status Dashboard letting pilots report AWOS and ASOS outages directly.
The Federal Aviation Administration (FAA) is seeking public comments on a proposed Surface Weather Status Dashboard that will allow pilots and other National Airspace System (NAS) users to crowdsource reports of outages and erroneous data from automated airport weather systems.
Published in the Federal Register on October 6, 2026, the 30-day notice outlines an information collection initiative designed to improve real-time situational awareness. By integrating user-submitted trouble tickets directly into the agency’s maintenance workflow, the FAA aims to expedite repairs for critical weather infrastructure.
Streamlining weather system maintenance
The new dashboard will be hosted on the existing FAA Aviation Weather Cameras website. The agency estimates that completing a report will take a user approximately one minute, with an anticipated volume of 1,825 reports submitted annually.
Once a pilot flags an issue with an Automated Weather Observing System (AWOS) or Automated Surface Observing System (ASOS), the data will undergo verification before entering the official maintenance queue.
“It is anticipated that the information collected will be used after verification to create reports that will trigger trouble tickets within the FAA’s Remote Monitoring and Logging System (RMLS) for corrective action to be taken by the responsible parties, such as technicians within the FAA, NOAA, and non-federal entities,” the FAA stated in its filing.
The primary benefit for pilots in the air or during preflight planning is the rapid update of system status. According to the FAA, once a trouble ticket is logged in the RMLS, the Aviation Weather Cameras website will capture and display the real-time service status of the affected automated weather station within 30 minutes.
Operational impact of automated weather data
AWOS and ASOS installations are critical infrastructure for aviation safety. These automated stations provide continuous, real-time weather information, typically broadcast via radio frequency and distributed globally as Aviation Routine Weather Reports (METARs).
When these systems experience outages or transmit erroneous data, the operational impact can be severe. Pilots relying on accurate altimeter settings, visibility measurements, and cloud ceiling data may be forced to delay departures, divert to alternate airports, or cancel operations entirely.
The FAA noted that the data collected through the new dashboard will serve a dual purpose, facilitating immediate maintenance dispatch while also informing long-term infrastructure planning. The agency stated that because the collected information will be site-specific, it may be used to update future policy decisions regarding surface weather infrastructure, approvals, and audits.
Evolution of the Weather Camera Program
The integration of the Surface Weather Status Dashboard into the FAA’s weather camera portal builds on a decades-long effort to improve weather visibility for pilots. The FAA Weather Camera Program originated in 1999 in Alaska, initially designed to give pilots operating under Visual Flight Rules (VFR) actual views of current weather conditions in remote, mountainous areas where weather reporting was sparse.
Since its inception, the program has expanded to over 600 locations across the United States. The FAA credits the camera network with significantly reducing weather-related flight interruptions and accidents.
Recently, the FAA has been expanding its broader camera network by adding new locations and deploying Visual Weather Observation Systems. These newer installations combine high-resolution imagery with automated surface-weather sensors to provide a more comprehensive picture of airport conditions. The addition of the Surface Weather Status Dashboard is a congressionally mandated enhancement to this existing platform.
Regulatory timeline and next steps
The regulatory process for the dashboard began earlier in the year. On May 11, 2026, the FAA published the initial 60-day comment period notice in the Federal Register to solicit industry feedback on the concept.
The October 6, 2026, publication serves as the 30-day notice, formally requesting approval from the Office of Management and Budget (OMB) for the information collection process.
Public comments on the proposal are due by November 5, 2026. Following the close of the comment period, the FAA will seek final clearance from the OMB to implement the data collection webform and launch the dashboard to the public.
AirPro News analysis
We view the implementation of a crowdsourced reporting tool for AWOS and ASOS infrastructure as a pragmatic shift in how the FAA manages the National Airspace System. Historically, the agency has relied on automated self-reporting diagnostics or internal monitoring to detect sensor failures. However, pilots on the ground or on approach frequently identify discrepancies, such as a frozen precipitation gauge, a stuck wind direction sensor, or an uncalibrated altimeter setting, long before the system flags itself as degraded.
By formalizing a feedback loop that takes only a minute for a pilot to complete, the FAA is effectively deputizing thousands of daily airspace users as quality control inspectors. If the agency can consistently meet its stated goal of updating the public-facing service status within 30 minutes of a verified report, this dashboard will significantly reduce the latency between a localized weather system failure and the broader aviation community being alerted to the hazard.
Photo Credit: Stock – Canva
-
Defense & Military7 days agoS&K Aerospace Wins $4.3B U.S. Air Force PROS 7 Contract
-
Newsletter5 days agoAirPro News Weekly: 12 October – 19 October 2026
-
Defense & Military6 days agoUSAF Renews PTC Servigistics Contract for ESCAPE Program
-
MRO & Manufacturing7 days agoMammoth Freighters Launches 777-200LR Conversion at STAECO China
-
Space & Satellites7 days agoSpaceX CRS-35 Delivers Final iROSA Arrays to ISS