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
FAA Investigates Southwest Airlines Ground Collision at PVD
Two Southwest Boeing 737s collided during pushback at Rhode Island T.F. Green Airport on June 11, 2026. FAA investigation opened.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by WPRI, NBC 10, Daily Voice, and CBS News Baltimore.
The Federal Aviation Administration (FAA) has opened an investigation after two Southwest Airlines Boeing 737 aircraft collided during pushback at Rhode Island T.F. Green International Airport (PVD) late on June 11, 2026.
The ground collision resulted in no reported injuries but forced the cancellation of both flights and the grounding of the involved aircraft for mandatory safety inspections. According to reporting by the Daily Voice and NBC 10, the incident highlights ongoing operational challenges on airport ramps, occurring just weeks after a similar event involving the same carrier at another East Coast facility.
Details of the ground collision
At approximately 10:45 p.m. local time, Southwest Airlines Flight 3515, bound for Ronald Reagan Washington National Airport (DCA), was pushing back from its gate. During the maneuver, the aircraft’s wing made contact with the tail of Southwest Airlines Flight 3409, which was scheduled to depart for Chicago Midway International Airport (MDW).
Both aircraft returned to their respective gates following the contact, allowing passengers to deplane normally. Southwest Airlines confirmed that no injuries occurred among passengers or crew members. The carrier subsequently canceled both flights and reaccommodated the affected travelers.
“Southwest Airlines is aware of an incident involving two of our aircraft at Rhode Island T. F. Green International Airport. We are investigating further and will be thoroughly inspecting the two aircraft,”
the airline stated in remarks provided to local media, adding that safety remains its highest priority.
Local media outlets, including NBC 10, reported passenger accounts suggesting that Flight 3515 continued to move briefly after the initial impact. These accounts claim passengers verbally alerted the flight crew to the collision. Neither Southwest Airlines nor the FAA has officially verified these specific passenger narratives, and the official sequence of events remains under investigation.
Regulatory response and recent precedent
The FAA confirmed on June 12, 2026, that it is investigating the circumstances surrounding the collision. Ground operations during pushback rely heavily on coordination between flight crews and ground personnel, particularly in ramp areas where air traffic controllers do not maintain direct communication with the aircraft.
This event follows a comparable occurrence on May 4, 2026, at Baltimore/Washington International Thurgood Marshall Airport (BWI). In that instance, two Southwest Airlines Boeing 737s clipped wings during pushback operations. The FAA investigated the BWI incident, noting the specific communication dynamics between ground crews and the flight deck in non-controlled ramp sectors.
AirPro News analysis
We note that while ground collisions during pushback rarely pose a severe threat to passenger safety, they represent a significant operational and financial burden for carriers. Ramp incidents require immediate grounding of the involved airframes, triggering mandatory structural inspections and potential repairs. The recurrence of pushback-related contact within a single airline’s network over a short period may prompt internal reviews of ground handling procedures, wingwalker positioning, and ramp communication protocols. Until the FAA concludes its investigation, the specific cause of the PVD collision remains undetermined.
Sources: WPRI
Photo Credit: Zachary Reis
Regulations & Safety
Turkish Airlines 777-300ER Wing Strike at Antalya Airport
A Turkish Airlines Boeing 777-300ER struck a radar antenna pole taxiing at Antalya Airport, prompting evacuation and a formal investigation.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by Hürriyet.
A Turkish Airlines (TK) Boeing 777-300ER sustained damage and prompted a passenger evacuation after its right wing struck a ground radar antenna pole while taxiing at Antalya Airport (AYT) on June 11, 2026.
The incident, which occurred at approximately 20:00 local time following Flight TK2430 from Istanbul, resulted in minor injuries among the passengers. According to official statements reported by Hürriyet, the widebody aircraft was maneuvering toward its parking position on Apron-1 when the collision occurred, leading to an immediate evacuation on the tarmac.
Conflicting passenger and injury reports
Following the evacuation, official sources provided conflicting figures regarding the number of passengers on board and the extent of injuries. In a public statement, Turkish Airlines Senior Vice President of Communications Yahya Üstün confirmed the evacuation, stating that 267 passengers were safely removed from the aircraft. The airline reported that one passenger sustained minor injuries and was in good health.
Conversely, the Turkey Ministry of Transport released a separate statement indicating a higher passenger count. The ministry reported that the aircraft was carrying 284 adult passengers and four infants. Furthermore, the government authority stated that three passengers suffered minor injuries during the event. Both entities confirmed that the aircraft, registered as TC-LKD, was towed to a parking area after the necessary safety checks and passenger removal were completed.
Investigation into the ground collision
A technical investigation into the ground collision has been initiated by the Turkey Ministry of Transport and the General Directorate of State Airports Authority (DHMI). The official cause of the incident remains under investigation.
While the airline noted the aircraft was approaching its parking position, preliminary remarks from the Ministry of Transport suggested the Boeing 777-300ER made contact with the radar pole after entering an incorrect taxiway line. Final determinations regarding the aircraft routing, ground control instructions, and the sequence of events will be established by the investigating authorities.
AirPro News analysis
Ground collisions involving widebody aircraft like the Boeing 777-300ER often highlight the tight tolerances required when maneuvering large airframes around airport infrastructure. While we await the official investigation findings, safety reviews following such events typically examine airport taxiway markings, lighting, and the clarity of ground control communications. The discrepancy in passenger manifests between the operator and the regulator is a notable detail, though initial reporting conflicts frequently occur in the immediate aftermath of an evacuation before final reconciliations are completed.
Sources: X.com
Photo Credit: X
Regulations & Safety
NTSB Final Report: Southwest Flight 4273 Turbulence Encounter
NTSB cites ATC communication delays and sector overload in Southwest Airlines turbulence event over Gulf of Mexico.

This is original reporting and analysis by AirPro News.
The National Transportation Safety Board (NTSB) has released its final report on a severe turbulence encounter involving a Southwest Airlines Boeing 737-700, detailing how rapidly developing convective weather and air traffic control communication delays factored into an event that seriously injured two people.
The April 3, 2024, incident aboard Southwest Airlines Flight 4273 over the Gulf of Mexico highlights the operational risks when severe weather systems intersect with technical limitations at air traffic control facilities. According to the NTSB investigation, the aircraft was navigating complex weather en route from New Orleans to Orlando when the encounter occurred, resulting in serious injuries to one flight attendant and one passenger, alongside minor injuries to a second flight attendant.
Weather conditions and the turbulence encounter
Flight 4273, operated by a Boeing 737-700 (registration N567WN) with 140 passengers and five crew members on board, was traveling from Louis Armstrong New Orleans International Airport (MSY) to Orlando International Airport (MCO).
At 11:55 UTC, a Convective Significant Meteorological Information (SIGMET) advisory was issued for the region, warning of cloud tops exceeding 45,000 feet.
At approximately 08:20 Eastern Daylight Time, the aircraft encountered severe turbulence over the Gulf of Mexico. The NTSB confirmed the aircraft itself sustained no damage during the event and the flight crew was able to continue the flight.
Air traffic control workload and technical limitations
The NTSB report outlines compounding factors at the Jacksonville Air Route Traffic Control Center (JAX ARTCC) that affected the flight routing through the weather system.
During the incident, the specific JAX ARTCC sector was managing a traffic volume that exceeded its target capacity of 20 aircraft.
This high workload was exacerbated by a technical limitation involving the facility communication infrastructure. The primary VHF antenna at JAX ARTCC had been rendered inoperative following a fire in October 2023. As a result, controllers were utilizing a temporary satellite relay connection to communicate with aircraft in the sector.
The NTSB determined this satellite relay introduced a 600-millisecond round-trip transmission delay, complicating timely communication between controllers and flight crews navigating the dynamic weather environment.
AirPro News analysis
We note that the findings in this final report underscore a critical vulnerability in the National Airspace System. When primary communication infrastructure fails, the fallback systems must be robust enough to handle high-stress, time-critical scenarios like severe convective weather deviation. A 600-millisecond delay might seem negligible in routine operations, but in a saturated sector where controllers are issuing rapid heading changes to keep aircraft clear of building storm cells, that latency degrades situational awareness and increases the risk of weather encounters. The NTSB documentation of this technical shortfall will likely prompt further scrutiny of contingency communication systems at major en route centers.
Photo Credit: NTSB
-
Technology & Innovation2 days agoAirbus Vision Landing Application Enables AI Autoland
-
Route Development5 days agoDubai International Airport to Close in 2035 for Al Maktoum
-
Commercial Aviation5 days agoIATA 2026 Airline Profit Forecast Cut in Half by Fuel Costs
-
Defense & Military6 days agoWhisper Aero Launches Collaborative Logistics Aircraft for US Military
-
MRO & Manufacturing5 days agoGE Aerospace Q1 2026: LEAP Deliveries Up 60%, $170B Backlog
