FAA Investigates Near Collision of United 737 and Army Black Hawk in Santa Ana

This article summarizes reporting by Flightradar24 and Ian Petchenik, with additional context from Aeroin.

On the evening of Tuesday, March 24, 2026, a commercial airliner and a military helicopter experienced a mid-air close call near John Wayne Airport (SNA) in Santa Ana, California. According to reporting by Flightradar24, a United Airlines Boeing 737-800 and a US Army UH-60M Black Hawk converged in the airspace, prompting an automated collision avoidance alert in the commercial jet.

The incident forced the United flight crew to take immediate evasive action by temporarily halting their descent. Both aircraft successfully avoided a collision, and the commercial jet landed safely shortly after the encounter. We are closely following the subsequent Federal Aviation Administration (FAA) investigation, which centers on airspace management protocols and the enforcement of newly implemented separation rules.

Incident Details and Flight Path

The Close Call Over Santa Ana

Flight data published by Flightradar24 indicates that United Airlines Flight UA589, traveling from San Francisco (SFO) to Santa Ana, was descending through 2,000 feet on its final approach. At the same time, a US Army Sikorsky UH-60M Black Hawk helicopter crossed the airliner’s flight path at an altitude of 1,425 feet. Reporting by Aeroin notes that the helicopter, operated by crews from the California Air National Guard, had departed from Los Alamitos Army Airfield and was returning from a low-altitude training mission in the Santa Ana mountains.

At the closest point of proximity, recorded at exactly 03:40:35 UTC, the two aircraft were separated by merely 525 feet vertically and 1,422 feet (approximately 433 meters) laterally. These precise separation metrics were derived from granular ADS-B flight data analyzed by Flightradar24.

Evasive Action and TCAS Activation

The rapidly decreasing distance between the Boeing 737-800 and the Black Hawk triggered a Traffic Collision Avoidance System Resolution Advisory (TCAS RA) in the United cockpit. As detailed by Flightradar24, the United crew responded to the automated warning by arresting their descent, effectively maintaining a safe vertical separation from the military helicopter.

Following the resolution of the traffic conflict, Flight UA589 resumed its approach. The twin-engine aircraft touched down safely at John Wayne Airport approximately three minutes after the incident, with no injuries reported among the passengers or crew.

Regulatory Response and Historical Context

FAA Investigation and New Separation Rules

On Thursday, March 26, 2026, the FAA officially announced the opening of an investigation into the Santa Ana close call. A central focus of the regulatory probe is airspace management and controller procedures. According to the incident research report, investigators are specifically looking into the enforcement of recent regulatory changes.

The investigation will determine “whether a new measure to suspend the use of visual separation between airplanes and helicopters was applied.”

As noted in the research report, the FAA recently implemented a rule change banning the use of “visual separation” between helicopters and fixed-wing aircraft near the busiest airports in the United States. This mandate requires air traffic controllers to utilize active radar separation rather than relying on helicopter pilots to visually confirm they are clear of conflicting traffic.

Echoes of Past Airspace Conflicts

This recent event in Southern California draws immediate parallels to past aviation tragedies. Reporting by Aeroin highlights a fatal mid-air collision in early 2025 over the Potomac River near Washington D.C., which also involved a US Army Black Hawk and a commercial regional jet, an American Eagle Bombardier CRJ-700. In that 2025 accident, investigators cited poor airspace management as the primary contributing factor leading to the collision.

AirPro News analysis

At AirPro News, we observe that the Santa Ana incident underscores the persistent and complex challenges of managing mixed-use airspace. The intersection of low-flying military or general aviation traffic with the established approach paths of commercial airliners remains a critical vulnerability in the national airspace system.

Furthermore, this event highlights the indispensable role of automated safety systems. The successful activation of the TCAS RA likely prevented a catastrophic outcome when standard air traffic control separation margins were compromised. As the FAA continues to enforce its new radar separation mandates for helicopters, we anticipate increased scrutiny on controller training and the technological integration required to monitor these busy terminal areas effectively. The shadow of the 2025 Potomac River collision clearly looms large over this current investigation, indicating that regulators are under immense pressure to ensure strict adherence to the updated separation protocols.

Frequently Asked Questions

What is a TCAS RA?

A Traffic Collision Avoidance System Resolution Advisory (TCAS RA) is an automated alert provided to pilots when their aircraft is on a potential collision course with another transponder-equipped aircraft. It provides specific, mandatory flight path instructions, such as arresting a descent or initiating a climb, to ensure safe separation.

When and where did the Santa Ana close call occur?

The incident occurred on the evening of Tuesday, March 24, 2026, in the airspace near John Wayne Airport (SNA) in Santa Ana, California. The closest proximity between the two aircraft was recorded at 03:40:35 UTC.

What are the new FAA rules regarding helicopter separation?

The FAA recently banned the use of “visual separation” between helicopters and fixed-wing aircraft near the busiest U.S. airports. Controllers must now use active radar separation to keep these aircraft apart, rather than relying on pilots to maintain visual clearance.

Sources

• Flightradar24