Connect with us

Regulations & Safety

U.S. House Passes Revised ALERT Act Mandating ADS-B In Technology

The U.S. House approved the ALERT Act requiring integrated ADS-B In tech for aircraft by 2031 after a fatal 2025 midair collision near DCA.

Published

on

This article is based on an official press release and formal letter from the National Transportation Safety Board (NTSB).

Following months of intense legislative debate and a rare, aggressive public intervention by federal safety investigators, the U.S. House of Representatives has overwhelmingly passed the revised Airspace Location and Enhanced Risk Transparency (ALERT) Act. The bipartisan 396–10 vote on April 14, 2026, marks a significant milestone in aviation safety reform, directly spurred by one of the deadliest domestic aviation accidents in recent history.

The legislative push follows the tragic January 29, 2025, midair collision between American Airlines Flight 5342, a regional jet operated by PSA Airlines, and a U.S. Army UH-60 Black Hawk helicopter near Ronald Reagan Washington National Airport (DCA). The disaster claimed the lives of all 67 individuals involved, including 64 aboard the passenger jet and three in the military helicopter.

According to the official findings and subsequent communications from the National Transportation Safety Board (NTSB), the tragedy was entirely preventable. The agency’s formal opposition to early, weaker drafts of the ALERT Act forced lawmakers back to the drawing board, ultimately resulting in a strict statutory mandate for integrated collision-avoidance technology across congested U.S. airspace.

The Catalyst: Flight 5342 and the ADS-B Gap

During its comprehensive investigation into the DCA collision, the NTSB identified critical gaps in how aircraft communicate their positions in shared airspace. A primary contributing factor was the military helicopter operating in congested civilian airspace without transmitting its location via Automatic Dependent Surveillance-Broadcast (ADS-B) Out technology.

Furthermore, the NTSB concluded that the commercial jet lacked ADS-B In, a complementary technology that allows pilots to receive real-time positional data of surrounding aircraft. According to the NTSB’s analysis, if the regional jet had been equipped with ADS-B In, the flight crew would have received an alert regarding the helicopter 59 seconds prior to the collision. Instead, relying on older systems, the pilots received only 19 seconds of warning. In response, the NTSB issued 50 safety standards, heavily emphasizing a mandate for ADS-B In technology for all aircraft operating in high-volume airspace.

Legislative Battles: ROTOR vs. ALERT Acts

The Fall of the ROTOR Act

The initial congressional response to the NTSB’s recommendations was the Rotorcraft Operations Transparency and Oversight Reform (ROTOR) Act. The bill aimed to close loopholes that allowed military aircraft to fly without ADS-B Out and sought to mandate ADS-B In for aircraft in busy airspace. While the ROTOR Act passed the Senate unanimously in December 2025, it failed in the House on February 24, 2026, by a vote of 264–133, falling short of the required two-thirds majority. The bill’s downfall was precipitated by the Department of Defense withdrawing its support, citing unresolved budgetary burdens and operational security risks.

The NTSB’s Rare Intervention

Days before the ROTOR Act’s failure, House lawmakers introduced a competing measure: the ALERT Act (H.R. 7613). However, in late February 2026, NTSB Chair Jennifer Homendy and the Board took the unusual step of sending a formal letter to House committee leaders, explicitly stating they could not support the ALERT Act in its original form.

In the official letter, the NTSB argued that the initial ALERT Act fell dangerously short of implementing their 50 safety recommendations. Chair Homendy criticized the draft as a “watered-down” measure because it permitted broad exemptions and allowed operators to use portable ADS-B In devices rather than requiring fully integrated cockpit equipment.

“We’ve issued safety recommendations like ADS-B In, over and over and over again… Recommendations that have been rejected, sidelined or just plain ignored.”

, NTSB Chair Jennifer Homendy

Revisions and Overwhelming House Passage

The NTSB’s public opposition, combined with mounting pressure from the families of the Flight 5342 victims, forced House lawmakers to heavily revise the ALERT Act. The amended legislation now strictly requires ADS-B In, alongside corresponding collision prevention technology, to be equipped and operating on virtually all aircraft already required to have ADS-B Out. The bill sets a firm Compliance deadline of December 31, 2031, and addresses the military data-sharing loopholes that contributed to the 2025 crash.

Following these stringent revisions, the NTSB publicly reversed its stance, stating that the updated ALERT Act successfully addresses the critical shortcomings identified in their collision investigation. The aviation industry, including the National Business Aviation Association and the Aircraft Owners and Pilots Association (AOPA), has also endorsed the final House text.

While the families of the victims have welcomed the revisions, they remain cautiously vigilant regarding the implementation timeline.

“Any Safety requirement that routes implementation through negotiated processes… creates opportunities for delay that cost lives.”

, Statement from the families of Flight 5342 victims

AirPro News analysis

We observe that the legislative trajectory of the ALERT Act highlights a persistent tension in U.S. airspace management: balancing the military’s need for operational security during training with the absolute necessity of civilian passenger safety. The NTSB’s formal letter of opposition was a pivotal, albeit rare, maneuver for an independent investigative body. By refusing to accept a compromised bill, the NTSB effectively leveraged public and political pressure to secure a mandate for integrated ADS-B In technology, a recommendation they have been pushing since 2008. The legislative battle now moves to a critical phase, as the Senate (which previously favored the ROTOR Act framework) and the House must negotiate a final compromise bill to send to the President’s desk.

Frequently Asked Questions

What is the difference between ADS-B Out and ADS-B In?

ADS-B Out is a technology that broadcasts an aircraft’s GPS location, altitude, and ground speed to air traffic controllers and other aircraft. ADS-B In is the complementary receiver technology that allows pilots to see the real-time positional data of those surrounding aircraft directly on their cockpit displays, providing crucial situational awareness to prevent midair collisions.

Why did the NTSB initially oppose the ALERT Act?

The NTSB opposed the original draft of the ALERT Act because it allowed for exemptions and permitted the use of portable ADS-B In devices. The NTSB insisted on fully integrated cockpit equipment to ensure maximum reliability and safety, calling the initial draft a “watered-down” measure.

When is the compliance deadline under the revised ALERT Act?

The revised ALERT Act, passed by the House on April 14, 2026, sets a strict compliance deadline of December 31, 2031, for virtually all aircraft operating in designated airspace to be equipped with integrated ADS-B In technology.


Sources:

Photo Credit: Stock image

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