Regulations & Safety
Senator Ted Cruz Proposes ROTOR Act to Enhance Aviation Safety
The ROTOR Act mandates ADS-B technology and reforms helicopter routes to improve aviation safety after a fatal D.C. mid-air collision.

Sen. Ted Cruz Unveils Aviation Safety Bill After Deadly D.C. Plane Crash
(Edited 7-31-2025) In the wake of a tragic mid-air collision near Washington, D.C., that claimed 67 lives, Senator Ted Cruz (R-TX) has introduced the ROTOR Act, a legislative effort aimed at closing critical gaps in safety. The crash, involving an American Airlines regional jet and a U.S. Army Black Hawk helicopter, marked the deadliest aviation disaster in the United States in over two decades. The incident has since spurred a national conversation about flight-tracking technologies and airspace accountability, particularly when military and civilian aircraft share congested skies.
The ROTOR Act, short for Rotorcraft Operations Transparency and Oversight Reform, seeks to mandate the use of Automatic Dependent Surveillance–Broadcast (ADS-B) technology across virtually all aircraft, including military helicopters. The bill also proposes enhanced oversight of helicopter routes near commercial service airports and demands increased transparency from military aviation operations in civilian airspace, including quarterly reports on ADS-B Out compliance and a study on potential improvements to the airspace around Ronald Reagan Washington National Airport (DCA). With support from several Republican senators and concern from key aviation agencies, the legislation reflects a significant shift in how the U.S. might manage mixed-use airspace moving forward.
The legislation is not only a response to a singular tragedy but also a broader attempt to modernize U.S. air traffic control and align with international safety standards. As the National Transportation Safety Board (NTSB) continues to investigate the circumstances surrounding the crash, the ROTOR Act represents a proactive step toward preventing similar incidents in the future.
Background: The Tragic Catalyst
On January 29, 2025, American Airlines Flight 5342, a Bombardier CRJ700 operated by PSA Airlines, collided mid-air with a U.S. Army Black Hawk helicopter designated Priority Air Transport 25 (PAT25). The crash occurred during the jet’s final approach to Ronald Reagan Washington National Airport, resulting in both aircraft plunging into the Potomac River and the loss of all 67 people on board (64 on the jet, including 2 pilots, 2 flight attendants, and 60 passengers; and 3 crew on the helicopter).
Investigators identified multiple contributing factors, including the Black Hawk’s ADS-B Out system being turned off and altimeter discrepancies that led the helicopter to fly above the maximum allowable altitude for its route. The ADS-B system, which broadcasts an aircraft’s position, altitude, and speed to air traffic control and other aircraft, is a cornerstone of modern airspace safety. With it off, the helicopter did not broadcast enhanced position data, though its Mode S transponder remained active, allowing it to be tracked by ATC radar and visible to the jet’s Traffic Alert and Collision Avoidance System (TCAS).
Military aircraft are currently allowed to disable ADS-B systems during certain operations, even in non-sensitive missions. In this case, the helicopter was flying a routine training mission, not a classified or sensitive operation, yet its ADS-B system remained off. The NTSB later revealed that between October 2021 and December 2024, there were over 15,000 close proximity events (aircraft within one nautical mile) in the DCA airspace, underscoring the systemic risks posed by such exemptions and route overlaps.
Key Provisions of the ROTOR Act
Universal ADS-B Requirements
The cornerstone of the ROTOR Act is the requirement for universal adoption of ADS-B Out and ADS-B In systems across all aircraft in controlled airspace. ADS-B Out ensures that an aircraft’s location and velocity are broadcast to air traffic control and nearby aircraft. ADS-B In allows pilots to receive this data in real-time, providing a comprehensive view of surrounding traffic on cockpit displays.
Under the bill, all aircraft, including military and civilian, must operate with ADS-B Out enabled when flying in congested or controlled airspace. Exceptions are granted only for sensitive government missions, which must be coordinated with the FAA and require temporary airspace closures. It closes a loophole allowing the Department of Defense to fly domestically without ADS-B Out.
This mandate aligns with long-standing NTSB recommendations and reflects growing consensus among aviation experts that ADS-B technology is essential for preventing mid-air collisions, particularly in busy corridors like the D.C. region.
“ADS-B In is a game-changer… It will save lives by giving pilots and controllers a clear view of what’s happening in the skies.”, NTSB Chair Jennifer Homendy
Helicopter Route Reforms
The ROTOR Act also addresses the physical routes taken by helicopters near major airports. One key provision is enhanced oversight of helicopter corridors, including those that pass close to commercial flight paths near Reagan National Airport. Helicopter Route 1, which the Black Hawk was following and had been flagged in earlier assessments, had a maximum altitude of 200 feet but remained active until the January 2025 crash.
The FAA is now tasked with redesigning helicopter corridors to ensure they do not intersect or closely parallel commercial aircraft approaches. These changes are intended to reduce the chances of future conflicts between slow-moving helicopters and fast-approaching jets.
By codifying these route changes into law, the ROTOR Act prevents future administrative reversals and ensures that safety improvements remain in place regardless of changes in leadership or policy priorities.
Accountability and Oversight
The bill includes several oversight mechanisms to ensure compliance and transparency, such as quarterly reports to the FAA detailing any flights conducted without ADS-B Out in civilian airspace. These reports will be made available to Congress and the public, increasing pressure on agencies to adhere to safety protocols.
This level of scrutiny is designed to ensure that military training does not compromise the safety of civilian air traffic and that any deviations from standard procedures are justified and documented.
Recent Developments and Support
NTSB Hearings and Recommendations
In July 2025, the NTSB held a three-day public hearing to investigate the crash. Key topics included the operational status of the Black Hawk’s ADS-B system (which was off), the transponder (which was active), and the actions of air traffic controllers in the moments leading up to the collision. Findings confirmed altimeter discrepancies on the Black Hawk, with the helicopter flying at approximately 278 feet—above the 200-foot limit—and potential issues with ATC transmission reception.
The NTSB issued urgent safety recommendations, including mitigating mid-air collision risks at DCA through route redesigns and ADS-B mandates. These recommendations are reflected in the ROTOR Act, indicating a strong alignment between investigative findings and legislative action.
The hearings also revealed that air traffic controllers received a conflict alert about 20 seconds before the crash, and the jet’s TCAS issued a traffic advisory at the same time, but they were unable to resolve it in time due to the rapid closure and altitude overlap.
FAA and Department of Transportation Actions
In response to the crash and subsequent investigations, the FAA temporarily suspended use of the helicopter route involved in the collision. Transportation Secretary Sean Duffy also announced a $31.5 billion modernization plan for U.S. air traffic control systems, which includes widespread deployment of ADS-B technology.
This plan aims to replace outdated radar systems and integrate more advanced surveillance tools, enhancing situational awareness for both pilots and controllers. Though the ROTOR Act focuses on immediate safety gaps, the broader modernization effort represents a long-term commitment to airspace safety.
The FAA has also begun reviewing its policies on military flight exemptions and is expected to issue new guidance in coordination with the Department of Defense.
Public and Industry Support
The ROTOR Act has received support from victims’ families, aviation industry leaders, and safety advocates. Doug Lane and Tim Lilly, who lost family members in the crash, publicly endorsed the bill, calling it a necessary step to ensure that no other families suffer a similar loss.
American Airlines also voiced its support, emphasizing that the bill would enhance safety for all passengers and crew members. Industry analysts have highlighted that the cost of installing ADS-B systems is minimal compared to the human and economic toll of a major aviation disaster.
With backing from cosponsors including Sens. Jerry Moran (R-KS), Marsha Blackburn (R-TN), and others, and endorsements from key stakeholders, the ROTOR Act appears poised to become a cornerstone of U.S. aviation safety reform.
Conclusion
The introduction of the ROTOR Act marks a significant shift in how the United States approaches aviation safety, particularly in mixed-use airspace where military and civilian aircraft operate side by side. By mandating universal ADS-B usage, reforming helicopter routes, and increasing oversight, the legislation addresses long-standing vulnerabilities that were tragically exposed in the January 2025 crash.
As the bill moves through Congress, its passage could set a new standard for transparency and accountability in aviation operations. With strong support from regulators, industry leaders, and the public, the ROTOR Act has the potential to reshape the future of airspace safety in the U.S. and bring it in line with global best practices.
FAQ
What caused the D.C. plane crash in January 2025?
The crash was caused by a mid-air collision between a regional jet and a military helicopter. Key factors included the helicopter flying above its route’s maximum altitude due to altimeter discrepancies, incomplete reception of ATC instructions, and the helicopter’s ADS-B Out system being turned off, which limited enhanced visibility—though the helicopter remained trackable via its transponder and the jet’s TCAS issued an alert about 20 seconds prior.
What is ADS-B technology?
ADS-B (Automatic Dependent Surveillance–Broadcast) is a surveillance technology that allows aircraft to broadcast and receive real-time position data, improving situational awareness for pilots and controllers.
Who supports the ROTOR Act?
The bill is supported by Senator Ted Cruz and cosponsors including Sens. Jerry Moran, Marsha Blackburn, Ted Budd, Shelly Moore Capito, Roger Marshall, Eric Schmitt, Tim Sheehy, and Todd Young; Transportation Secretary Sean Duffy; NTSB Chair Jennifer Homendy; victims’ families; and American Airlines, among others.
Sources
Photo Credit: Austin American-Statesman
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
-
Defense & Military6 days agoWhisper Aero Launches Collaborative Logistics Aircraft for US Military
-
Commercial Aviation5 days agoIATA 2026 Airline Profit Forecast Cut in Half by Fuel Costs
-
MRO & Manufacturing5 days agoGE Aerospace Q1 2026: LEAP Deliveries Up 60%, $170B Backlog
