Regulations & Safety
US House Rejects ROTOR Act Mandating Aircraft Locator Systems
The ROTOR Act mandating ADS-B In technology for aircraft failed in the US House amid Pentagon opposition and competing aviation safety proposals.

This article summarizes reporting by the Associated Press and journalist Josh Funk.
House Rejects ROTOR Act: Mandate for Anti-Collision Tech Stalls Amid Pentagon Opposition
Legislation designed to mandate advanced aircraft locator systems near busy airports failed to pass the U.S. House of Representatives on Tuesday, dealing a blow to safety advocates who have championed the technology for nearly two decades. The bill, known as the Rotorcraft Operations Transparency and Oversight Reform (ROTOR) Act (S. 2503), was introduced in direct response to a fatal midair collision near Washington Reagan National Airport (DCA) in January 2025.
According to reporting by the Associated Press, the measure failed to win necessary approval despite the backing of the National Transportation Safety Board (NTSB). NTSB Chair Jennifer Homendy has long argued that the technology, which her agency first recommended in 2008, is essential for preventing tragedies like the one that claimed 67 lives last year.
While the bill received a majority of votes (264–133), it was brought to the floor under a suspension of the rules, a procedural move that requires a two-thirds supermajority for passage. The failure highlights a deepening rift between safety regulators, the military, and general aviation groups over how best to modernize airspace surveillance.
The ROTOR Act and the Push for ADS-B In
The ROTOR Act sought to close a critical technological gap in safety by mandating the installation of Automatic Dependent Surveillance-Broadcast (ADS-B) “In” technology. While most aircraft in controlled airspace are already required to have ADS-B “Out” (which broadcasts their location to ground controllers), ADS-B “In” allows pilots to see the precise location of other aircraft directly on their cockpit displays.
The legislation aimed to require this receiving technology for all aircraft operating in complex airspace by December 31, 2031. Additionally, it sought to repeal Section 373(a) of the National Defense Authorization Act (NDAA), a provision that currently permits military aircraft to disable their location broadcasters during sensitive missions.
The “Blood on Hands” Argument
The NTSB has been vocal about the necessity of this technology. Following the failure of the vote, proponents of the bill pointed to the agency’s longstanding frustration with regulatory delays. According to the Associated Press, the NTSB head noted that the system has been a standing recommendation for 18 years.
In testimony regarding the legislation, Chair Homendy emphasized the human cost of inaction:
“The question is: How many more people need to die before we act?”
— Jennifer Homendy, NTSB Chair (via legislative records)
Why the Bill Failed: Security and Bureaucracy
Despite passing the Senate unanimously, the ROTOR Act faced a coalition of opposition in the House that ultimately prevented it from reaching the two-thirds threshold.
Pentagon Opposition
A primary factor in the bill’s defeat was late-breaking opposition from the Department of Defense. The Pentagon withdrew its support due to concerns regarding the repeal of NDAA Section 373(a). Defense officials argued that strict requirements for military aircraft to broadcast their location at all times could compromise operational security, particularly during classified or sensitive training missions.
Competing Legislation: The ALERT Act
The ROTOR Act also faced resistance from general aviation groups and House leadership who favor a competing bill, the Airspace Location and Enhanced Risk Transparency (ALERT) Act of 2026 (H.R. 7613). Supported by the Aircraft Owners and Pilots Association (AOPA) and the National Business Aviation Association (NBAA), the ALERT Act proposes a regulatory rulemaking process rather than a legislative mandate.
Supporters of the ALERT Act argue that a rulemaking process allows for necessary industry input and cost-benefit analyses, ensuring that mandates do not place an undue financial burden on small aircraft owners. However, critics, including the Air Line Pilots Association (ALPA), contend that this approach merely delays life-saving implementation through bureaucracy.
Context: The 2025 DCA Tragedy
The urgency behind these legislative efforts stems from the catastrophic midair collision on January 29, 2025, near Washington Reagan National Airport. The crash involved an American Airlines regional jet (operated by PSA Airlines) and a U.S. Army UH-60 Black Hawk helicopter, resulting in the deaths of all 67 people aboard both aircraft.
Investigations revealed a fatal blind spot in the current system:
- The Black Hawk was on a training mission and was not broadcasting its location via ADS-B Out.
- The regional jet lacked ADS-B In, leaving the pilots without a digital display of surrounding traffic.
NTSB analysis determined that if the regional jet had been equipped with ADS-B In, the pilots would have had approximately one minute of warning, enough time to alter course. Instead, they had only 19 seconds of visual warning, which proved insufficient to avoid the collision.
AirPro News Analysis
The failure of the ROTOR Act illustrates the complex tension between civil aviation safety and national security interests. While the NTSB’s mandate is singular, preventing accidents, the legislative branch must weigh these recommendations against the Department of Defense’s operational requirements.
We observe that the “suspension of the rules” procedure was a calculated risk by the bill’s sponsors that ultimately backfired. By bypassing the standard amendment process to expedite the vote, proponents required a higher threshold for passage that they could not meet once the Pentagon signaled its disapproval. The focus now shifts to the ALERT Act, where the battle will likely move from the House floor to the slow-moving corridors of FAA rulemaking. For passengers, this likely means that the “technological safety net” envisioned by the NTSB remains years away from universal implementation.
Sources
Associated Press / WRAL. (link)
Photo Credit: NBC News
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.

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
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.

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
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.

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.
Photo Credit: Mike Segar – Reuters
-
Technology & Innovation6 days agoSkyband Systems M100 LRU Validates GNSS Jamming Protection
-
MRO & Manufacturing6 days agoBoeing SPEEA Engineers Reject Contract, Authorize Strike
-
Military Technology6 days agoSaab Unveils A3-001 Supersonic Stealth Drone Concept
-
Business Aviation5 days agoFTAI Aviation Closes $2B Warehouse Financing for 2026 SPV
-
Business Aviation6 days agoSyberJet SJ30-2 Sets Transcontinental Speed Record
