Connect with us

Regulations & Safety

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

A United Airlines 737 and a US Army Black Hawk had a close call near John Wayne Airport, prompting FAA investigation into airspace separation rules.

Published

on

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

Photo Credit: Flightradar24

Continue Reading
Click to comment

Leave a Reply

Regulations & Safety

NTSB: Thermal Plugs Caused AA Flight 3023 Tire Failure

NTSB determines melted thermal relief plugs caused tire failure on American Airlines 737-8 at Denver, triggering emergency evacuation.

Published

on

The National Transportation Safety Board (NTSB) has determined that melted thermal relief plugs caused the left main landing gear tires to fail on an American Airlines Boeing 737-8 during a July 2025 takeoff roll at Denver International Airport (DEN), prompting a high-speed rejected takeoff and emergency evacuation.

The final aviation investigation report, published on August 26, 2026, officially closes the inquiry into American Airlines Flight 3023. The document details the mechanical sequence that led to the tire failure while highlighting significant passenger noncompliance during the subsequent evacuation, as travelers ignored crew commands and retrieved carry-on baggage.

Mechanical sequence and rejected takeoff

The incident occurred on July 26, 2025, involving a Boeing 737-8, registration N306SW, equipped with CFM International LEAP-1B28 engines. According to the NTSB, the flight experienced an approximate 25-minute delay while awaiting departure at runway 34L.

During the subsequent takeoff roll, as the aircraft reached an indicated airspeed between 90 and 100 knots, the captain reported hearing a loud pop accompanied by a noticeable bump. The flight crew initiated a rejected takeoff at speeds above 80 knots.

The NTSB determined the probable cause of the incident was the melting of thermal relief plugs in the left main landing gear. This melting released tire pressure and caused the tires and wheels to fail during the takeoff roll. The agency noted that this failure resulted in abnormal airplane handling characteristics, which prompted the flight crew to reject the takeoff. Debris from the fractured wheels caused minor damage to the aircraft, including a three-inch dent on the lower skin of the left wing.

Emergency evacuation and passenger behavior

Following the rejected takeoff, the flight crew initially instructed the cabin to remain seated. Between 30 and 45 seconds later, after identifying smoke and fire originating from the left main landing gear, the crew ordered an emergency evacuation.

The aircraft carried 175 occupants, comprising 169 passengers and six crew members. The NTSB final report confirms that zero injuries occurred during the event. This official casualty figure supersedes preliminary media reports from July 2025 that had indicated minor injuries and hospital evaluations.

The investigation report draws specific attention to passenger behavior during the emergency egress. The NTSB stated that the cabin crew described the evacuation as rapid but hindered by significant passenger confusion and noncompliance. Despite flight attendants repeatedly commanding passengers to leave their belongings behind, multiple individuals retrieved their carry-on baggage. The NTSB concluded that this noncompliance directly slowed the flow of egress from the aircraft.

AirPro News analysis

The NTSB findings regarding American Airlines Flight 3023 add to a well-documented and growing safety concern within the commercial aviation sector. Passenger retrieval of carry-on baggage during emergency evacuations is a recurring issue that compromises the 90-second evacuation standard mandated by the Federal Aviation Administration (FAA).

When passengers stop to open overhead bins and carry luggage down escape slides, they not only slow the egress rate for those behind them but also introduce the risk of puncturing the evacuation slides or injuring fellow passengers. We continue to see official accident reports cite passenger noncompliance as a negative factor in evacuation efficiency. This recurring behavioral pattern has prompted safety advocates and lawmakers to question whether current FAA evacuation certification tests, which rely on compliant participants, accurately reflect real-world human behavior during an emergency.

Sources: National Transportation Safety Board

Photo Credit: National Transportation Safety Board

Continue Reading

Regulations & Safety

Marine One Loss of Separation at DCA: NTSB Preliminary Report

NTSB cites radio line-of-sight failure after Marine One and Envoy Air E-170 came within 0.82 NM at Reagan National.

Published

on

This is a developing story. Information may change as official details are released.

This is original reporting and analysis by AirPro News.

A loss of separation occurred on August 4, 2026, between a Sikorsky VH-3D operating as Marine One and an Envoy Air Embraer E-170 departing Ronald Reagan Washington National Airport (DCA). The incident took place approximately two miles north of the airport at 14:34 EDT and prompted an immediate Federal Aviation Administration (FAA) relocation of radio equipment after investigators identified a communication failure.

According to a preliminary report released on August 27, 2026, by the National Transportation Safety Board (NTSB), air traffic controllers at DCA did not receive a required three-minute pre-departure warning from the helicopter. The event triggered a review of strict Safety protocols implemented following a fatal midair collision in the same airspace in January 2025.

Incident timeline and separation data

The loss of separation occurred when Marine One departed The Ellipse simultaneously with Envoy Air flight 3742 departing runway 1 at DCA. Preliminary FAA estimates indicate the aircraft came within 0.82 nautical miles (NM) laterally and 700 feet vertically. The NTSB is currently analyzing surveillance data to establish the exact closest point of approach.

President Donald Trump was on board the Sikorsky VH-3D at the time of the incident. In a statement provided to CBS News, White House spokesman Kush Desai confirmed the President was never in danger.

Marine One flights are piloted by the finest aviators in the world, and the White House maintains the utmost confidence in these patriots and other security officials who are responsible for ensuring the President’s safety.

No injuries were reported among the occupants of either aircraft, and both flights continued to their respective destinations without further incident.

Communication failure and FAA response

The NTSB preliminary report points to inadequate radio line-of-sight coverage between The Ellipse and the DCA tower as the primary factor in the missed pre-departure warning. A DCA tower controller reported that the transmission attempt from the helicopter was “broken and unreadable,” according to CBS News.

Following the August 4 incident, FAA technicians evaluated the infrastructure and confirmed the line-of-sight deficiency. To resolve the issue, the agency relocated the helicopter-control radio equipment to the top of the DCA control tower. Subsequent communication checks were successful.

CBS News also reported that recent construction at the White House may have contributed to the radio line-of-sight degradation, though the NTSB has not yet issued a final determination on the cause.

Regulatory context and prior airspace changes

The airspace surrounding DCA operates under highly specific procedural rules designed to deconflict fixed-wing airline traffic from frequent VIP helicopter movements. These procedures were significantly tightened following a fatal midair collision on January 29, 2025, involving an airliner and an Army Black Hawk helicopter near the airport.

Following the 2025 accident, regulators instituted a requirement for a ground stop at DCA anytime a Helicopters passes on a conflicting route. The failure of the three-minute warning on August 4 prevented controllers from initiating this required ground stop for the Envoy Air departure.

Air traffic controllers and Marine One pilots had previously met on July 28, 2026, exactly one week prior to the incident, to discuss ongoing communication challenges in the sector.

AirPro News analysis

The August 4 loss of separation highlights the fragility of procedural deconfliction in the Washington, D.C. airspace. While the FAA characterized the event as a momentary loss of separation, the failure of a critical communication link reveals a single point of failure in the safety protocols established after the 2025 collision. We note that the rapid relocation of the radio equipment by the FAA demonstrates an acknowledgment of the infrastructure gap. As the NTSB continues its Investigation, we will monitor the docket for potential systemic recommendations regarding how VIP helicopter movements integrate with high-volume Commercial-Aircraft traffic at DCA, particularly concerning redundant communication systems.

Sources: National Transportation Safety Board

Photo Credit: National Transportation Safety Board

Continue Reading

Regulations & Safety

FAA Moves to Fire Two LaGuardia Controllers After Fatal Collision

FAA initiates termination proceedings against two LaGuardia controllers for early shift departures on the night of the March 22, 2026 runway collision.

Published

on

This is a developing story. Information may change as official details are released.

This article summarizes reporting by Reuters by David Shepardson and Doyinsola Oladipo.

The FAA has initiated termination proceedings against two air traffic controllers accused of leaving their shifts early on the night of a fatal runway collision at LaGuardia Airport (LGA) in March 2026. The agency is classifying the unauthorized early departures as timecard fraud amid a broader national crackdown on the practice.

The disciplinary action follows the March 22, 2026, accident in which Air Canada Express Flight 8646, operated by Jazz Aviation LP, collided with an aircraft rescue firefighting (ARFF) vehicle while landing on Runway 4. According to Reuters, the two controllers allegedly departed the facility approximately one hour before their scheduled shifts ended, a practice colloquially known as an “early shove.”

Disciplinary actions and union response

The FAA stated its commitment to holding employees accountable, emphasizing that it will not compromise the safety or efficiency of the national airspace system. U.S. Secretary of Transportation Sean Duffy condemned the practice, stating that while most controllers complete their full shifts, the department will not tolerate fraud from individuals who unfairly burden their colleagues and impact the airspace.

The National Air Traffic Controllers Association (NATCA) confirmed it is actively discussing the allegations with FAA leadership. The union indicated that these internal discussions are the appropriate forum for addressing the matter. Reuters reports that the FAA is currently conducting a nationwide enforcement effort targeting employees who leave on break at the end of their shifts and fail to return.

The March 22 collision and investigation

The NTSB continues to investigate the March 22 collision under investigation ID DCA26MA161. The official cause of the accident remains undetermined. The aircraft involved was an MHI RJ Aviation CRJ-900, and the ground equipment was an Oshkosh Striker 1500 ARFF vehicle.

Official NTSB figures confirm that 76 people were on board the aircraft, including 72 passengers, two flight attendants, and two pilots. The captain and first officer sustained fatal injuries. Thirty-nine individuals were transported to local hospitals, with six reported to have serious injuries.

It remains unverified whether the controllers’ early departure directly influenced the events leading to the collision. Speaking in March 2026, NTSB Chair Jennifer Homendy noted that operating with two controllers in the tower cab during a midnight shift is common practice across the national airspace system, suggesting the facility may have been operating at standard staffing levels at the time of the accident.

Regulatory response to surface safety

Following the LaGuardia accident, the FAA accelerated initiatives to improve surface visibility at airports. On May 13, 2026, the agency announced a $16.5 million investment to equip all airport vehicles with transponders.

These vehicle movement area transponders (VMATs) are designed to provide ATC with better situational awareness of ground equipment operating on runways and taxiways.

AirPro News analysis

We note that the FAA’s decision to pursue termination for timecard fraud rather than operational errors highlights a strict administrative approach to facility management. By focusing on the unauthorized absence, the agency addresses the “early shove” culture directly without preempting the NTSB’s ongoing safety investigation into the collision’s root causes. The distinction between administrative violations and operational fault will likely remain a focal point as NATCA engages with FAA leadership.

Sources: Reuters, NTSB

Photo Credit: Mike Segar – Reuters

Continue Reading
Every coffee directly supports the work behind the headlines.

Support AirPro News!

Advertisement

Follow Us

newsletter

Latest

Categories

Tags

Every coffee directly supports the work behind the headlines.

Support AirPro News!

Popular News