Connect with us

Regulations & Safety

ALERT Act Introduced to Enhance Aviation Safety After Flight 5342 Crash

The ALERT Act mandates collision avoidance tech and repeals military location exemptions following the 2025 Flight 5342 midair collision in the National Capital Region.

Published

on

This article is based on an official press release from the House Armed Services Committee and the House Transportation and Infrastructure Committee.

On February 19, 2026, the bipartisan leadership of the House Transportation and Infrastructure (T&I) and Armed Services Committees introduced comprehensive legislation aimed at overhauling aviation safety protocols in the National Capital Region. The Airspace Location and Enhanced Risk Transparency (ALERT) Act of 2026 serves as a direct legislative response to the catastrophic midair collision between Airlines Flight 5342 and a U.S. Army UH-60 Black Hawk Helicopters earlier last year.

The bill, sponsored by T&I Chairman Sam Graves (R-MO), Ranking Member Rick Larsen (D-WA), Armed Services Chairman Mike Rogers (R-AL), and Ranking Member Adam Smith (D-WA), seeks to implement all 50 safety recommendations issued by the National Transportation Safety Board (NTSB) in its final accident report.

Legislative Response to the Flight 5342 Tragedy

The introduction of the ALERT Act comes just days after the NTSB released its final investigation into the January 29, 2025, disaster over the Potomac River, which claimed 67 lives. According to the joint committee release, the legislation is designed to address the systemic failures identified by investigators, specifically the lack of situational awareness and transparency between military and civil aircraft operating in shared airspace.

In a statement regarding the bill’s introduction, Rep. Sam Graves emphasized the weight of the tragedy on the legislative process:

“The collision… was a terrible tragedy… The best way to serve and honor the victims and their families is by thoughtfully addressing the broad range of safety issues raised by the now-complete accident investigation.”

, Rep. Sam Graves (R-MO), Chairman, Transportation and Infrastructure Committee

Key Provisions of the ALERT Act

Based on the text of the bill and the committee summary, the ALERT Act mandates several critical changes to aviation operations, particularly around high-density Airports like Ronald Reagan Washington National Airport (DCA). Key measures include:

  • Mandatory Collision Mitigation Technology: The Act requires the installation and use of collision avoidance and alerting systems, such as ADS-B, for all civil fixed-wing aircraft and rotorcraft.
  • Airspace Redesign: The Federal Aviation Administration (FAA) is mandated to redesign helicopter routes and separation standards to ensure greater buffers between commercial flights and rotorcraft.
  • ATC Reform: The bill directs enhanced training for Air Traffic Controllers to better manage mixed-use airspace involving both commercial jets and military helicopters.

Repealing the “Transparency Loophole”

A central and politically significant component of the ALERT Act is the repeal of Section 373(a) of the Fiscal Year 2026 National Defense Authorization Act (NDAA). This provision had previously allowed military aircraft to waive requirements for military aircraft to broadcast their location via ADS-B while operating in the National Capital Region.

Critics and safety advocates have argued that this exemption created a dangerous “blind spot” in the airspace. The NTSB investigation into the Flight 5342 crash highlighted that the Black Hawk helicopter involved was not equipped with modern collision avoidance technology that could have alerted the crew to the incoming regional jet.

Rep. Mike Rogers, Chairman of the Armed Services Committee, noted the collaboration required to address this specific defense-related issue:

“Rather than take a piecemeal approach, the Armed Services Committee worked closely with our counterparts… to craft comprehensive legislation that makes our skies safer for airline passengers and for the servicemembers.”

, Rep. Mike Rogers (R-AL), Chairman, Armed Services Committee

Background: The Crash and NTSB Findings

The urgency of this legislation stems from the events of January 29, 2025. American Airlines Flight 5342, a Bombardier CRJ-700 operated by PSA Airlines, collided with a U.S. Army UH-60L Black Hawk approximately 0.5 miles from DCA. The crash resulted in the deaths of all 64 people aboard the jet and the 3 crew members of the helicopter.

The NTSB’s final report, released on February 17, 2026, concluded that the crash was not the result of a single error, but a convergence of flawed airspace design, altitude deviations, and a lack of technological interoperability. Specifically, the investigation found that the helicopter route was positioned directly beneath the active approach corridor for Runway 33 without sufficient vertical separation.

AirPro News Analysis

The speed at which the ALERT Act has moved from concept to introduction, just two days after the NTSB final report, signals a rare alignment between the House Transportation and Armed Services committees. Typically, jurisdictional friction between civilian aviation oversight and military operational security can slow such reforms. However, the explicit repeal of Section 373(a) suggests that Congress is prioritizing the “Written in Blood” doctrine, the grim reality that aviation regulations are often only strengthened following mass casualty events, over previous military transparency exemptions.

Frequently Asked Questions

What is the ALERT Act of 2026?
The Airspace Location and Enhanced Risk Transparency (ALERT) Act is a bipartisan bill introduced to overhaul aviation safety, specifically mandating collision avoidance tech and redesigning airspace routes following the Flight 5342 crash.

What was Section 373(a) of the FY26 NDAA?
It was a provision that allowed military aircraft to opt out of broadcasting their location data in the National Capital Region. The ALERT Act repeals this to ensure all aircraft are visible to ATC and other pilots.

What were the casualties of Flight 5342?
The collision resulted in 67 confirmed fatalities: 64 passengers and crew on the regional jet, and 3 crew members on the Army helicopter.

Sources

House Armed Services Committee Press Release
National Transportation Safety Board (NTSB)

Photo Credit: NTSB

Continue Reading
Click to comment

Leave a Reply

Regulations & Safety

Missouri Skydive Plane Crash Kills 12 at Butler Airport

A Pacific Aerospace 750XL crashed after takeoff from Butler Memorial Airport on June 14, 2026, killing a pilot and 11 skydivers.

Published

on

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

This article summarizes reporting by CBS News, The Washington Post, SFGATE, KEYT, and Fox 10 Phoenix.

A Pacific Aerospace 750XL operated by Skydive Kansas City crashed shortly after takeoff from Butler Memorial Airport (BUM) on June 14, 2026, resulting in 12 fatalities.

The Missouri State Highway Patrol confirmed that the pilot and 11 skydivers died when the single-engine turboprop impacted a field adjacent to the airport and caught fire. The NTSB and the FAA have deployed investigators to the site, located approximately 65 miles south of Kansas City.

Accident sequence and emergency response

The aircraft departed BUM at approximately 11:20 a.m. local time. According to preliminary reports cited by SFGATE, the aircraft made a left turn shortly after takeoff. Emergency responders received a 911 call around 11:30 a.m. reporting that the aircraft had crashed into a field approximately 300 yards from the runway and was engulfed in flames.

Dennis Jacobs, acting airport manager and Bates County Emergency Management Agency director, told reporters that the aircraft appeared to lose power before stalling and impacting the ground nose first. The NTSB has not yet verified this sequence of events, and the official cause of the accident remains under investigation.

The Missouri State Highway Patrol, alongside the Butler Police Department and Bates County Sheriff’s Office, secured the scene. A statement from the highway patrol confirmed that all 12 occupants perished in the crash. The identities of the victims are being withheld pending family notification.

Aircraft and operator background

The aircraft involved was a Pacific Aerospace 750XL manufactured in 2010. The 750XL is a single-engine turboprop frequently utilized in commercial skydiving operations due to its climb rate and payload capacity. The flight was operated by Skydive Kansas City, a commercial skydiving center based at BUM.

This accident follows a previous skydiving-related aviation occurrence near the same airport. On May 25, 2024, a Cessna U206C experienced an in-flight emergency near BUM. In that incident, the pilot and six skydivers successfully evacuated the aircraft via parachute before it crashed into a hayfield, resulting in no fatalities.

AirPro News analysis

We note that the NTSB investigation will likely focus on engine performance, weight and balance, and environmental factors at the time of departure. The Pacific Aerospace 750XL is a specialized utility aircraft, and investigators will examine maintenance records and the operator’s procedures as part of their standard protocol. Until the NTSB releases its preliminary report, usually within 30 days, any statements regarding a loss of power remain unconfirmed eyewitness observations.

Sources: CBS News

Photo Credit: NZAero

Continue Reading

Regulations & Safety

FAA Investigates Southwest Airlines Near Miss at Nashville

Two Southwest Boeing 737s came within 500 vertical feet near Nashville on April 18, 2026, after an ATC error during a go-around.

Published

on

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

This article summarizes reporting by CNN, Fox News, and The Washington Post.

Two Southwest Airlines (WN) Boeing 737 aircraft passed within 500 vertical feet of each other near Nashville International Airport (BNA) on April 18, 2026, after air traffic control instructions placed an aborting arrival into the path of a departing flight.

The incident, which occurred at approximately 5:30 p.m. local time, prompted both flight crews to execute evasive maneuvers following onboard Traffic Collision Avoidance System (TCAS) alerts. The Federal Aviation Administration (FAA) has launched an investigation into the airspace separation loss, which highlights ongoing scrutiny over air traffic control protocols and collision avoidance effectiveness.

Sequence of events and evasive maneuvers

According to statements provided to CNN and Fox News, Southwest Airlines Flight 507 was arriving from Myrtle Beach, South Carolina, when the flight crew initiated a precautionary go-around due to gusty wind conditions at BNA. During this maneuver, air traffic controllers instructed the crew to turn right.

The FAA confirmed in a statement that these instructions placed Flight 507 directly into the departure path of Southwest Airlines Flight 1152, which was taking off from a parallel runway bound for Knoxville, Tennessee. As the aircraft converged, TCAS resolution advisories activated in both cockpits. Flight tracking data from Flightradar24 indicates the two Boeing 737s came within 500 vertical feet of one another before the crews successfully altered their trajectories.

Both aircraft continued to safe landings without further incident. Flight 507 completed its arrival into Nashville on a subsequent approach, while Flight 1152 proceeded to its destination in Knoxville.

Regulatory investigation and safety context

The FAA is currently investigating the circumstances that led to the loss of separation. Southwest Airlines issued a statement emphasizing that the pilots of Flight 507 were complying with air traffic control directives when the conflict occurred, and that the crews responded professionally to the onboard traffic alerts to maintain safety.

The Nashville incident occurs against a backdrop of heightened national attention on mid-air collision risks. The Washington Post notes that aviation safety systems have faced intense public and regulatory scrutiny following a January 29, 2025, collision between an American Airlines aircraft and a military helicopter near Washington, D.C., which resulted in 67 fatalities. While the circumstances of the two events differ, the 2025 accident has amplified focus on the reliability of TCAS and air traffic control coordination in congested airspace.

AirPro News analysis

The activation of TCAS resolution advisories in this incident demonstrates the critical role of automated safety nets when procedural separation fails. While the FAA investigation will ultimately determine the root cause of the controller instructions, the event underscores the vulnerability of the go-around phase. Go-arounds are dynamic maneuvers that rapidly alter an aircraft’s energy state and expected flight path. These maneuvers require immediate and precise coordination between the flight deck and air traffic control, particularly when parallel runway operations are active.

Sources: CNN (via KESQ)

Photo Credit: Flightradar24 – Google Earth via CNN Newsource

Continue Reading

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.

Published

on

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

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