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.
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.
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
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:
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
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.
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.
What is the ALERT Act of 2026? What was Section 373(a) of the FY26 NDAA? What were the casualties of Flight 5342? House Armed Services Committee Press Release
Legislative Response to the Flight 5342 Tragedy
Key Provisions of the ALERT Act
Repealing the “Transparency Loophole”
Background: The Crash and NTSB Findings
AirPro News Analysis
Frequently Asked Questions
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.
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.
The collision resulted in 67 confirmed fatalities: 64 passengers and crew on the regional jet, and 3 crew members on the Army helicopter.Sources
National Transportation Safety Board (NTSB)
Photo Credit: NTSB
Regulations & Safety
NTSB Preliminary Report on Fatal Pelegrin Tarragon Crash in Arizona
The NTSB released a preliminary report on the fatal crash of an experimental Pelegrin Tarragon aircraft in Arizona, with investigation ongoing.
This article is based on an official preliminary report from the National Transportation Safety Board (NTSB) and public FAA registry data.
The National Transportation Safety Board (NTSB) has released its preliminary report regarding the fatal accident involving an experimental amateur-built Pelegrin Tarragon aircraft in Arizona. The crash, which occurred on February 6, 2026, resulted in the death of the pilot and injuries to a surviving passenger.
According to the NTSB’s findings released on February 18, 2026, the aircraft, registered as N35RR, was destroyed after impacting terrain in a remote desert environment near Shawmut, Arizona. The accident site is located near a railroad siding southeast of Gila Bend in Maricopa County. Investigators confirmed that the flight was operating under Part 91 general aviation rules as a personal flight at the time of the incident.
The release of this preliminary document marks the first official step in an investigation that is expected to continue for at least a year. While the report establishes the factual circumstances gathered at the scene, the NTSB emphasizes that it does not yet determine the probable cause of the tragedy.
The accident occurred at approximately 19:30 (7:30 PM) local time on Friday, February 6. The NTSB report indicates that the aircraft was navigating the Gila Bend area when the crash sequence initiated. Visual Meteorological Conditions (VMC) prevailed at the time, suggesting that weather may not have been a primary restricting factor, though specific visibility and wind data will likely be analyzed further in the full factual report.
The crash site in Shawmut is characterized by flat, open desert terrain often utilized for general aviation transit. However, the area presents significant challenges for emergency landings due to uneven ground and scrub brush. The aircraft reportedly sustained substantial damage upon impact.
“Preliminary data suggests the aircraft impacted terrain in a remote desert environment. The specific sequence of events leading to the impact is currently under investigation.”
— National Transportation Safety Board (NTSB) Preliminary Report
Federal investigators are currently examining several critical components of the wreckage. The NTSB has stated that the investigation will focus on the airframe, the flight controls, and the Rotax 915 iS engine (approximately 141 hp) to rule out or identify any pre-impact mechanical anomalies. Additionally, investigators noted that the statement from the surviving passenger will be a “critical component” of the ongoing inquiry. The aircraft involved was a Pelegrin Tarragon, a high-performance tandem-seat ultralight originally designed in Latvia. Known for its carbon-fiber construction and speed capabilities of up to 190 knots, the aircraft is often registered in the United States under the Experimental Amateur-Built category. This classification typically requires the owner to participate significantly in the aircraft’s construction.
According to FAA registry records cited in the report context, the aircraft (N35RR) was registered to Red Baron Snoop Dog LLC based in Lewes, Delaware. The airworthiness certificate was issued in August 2022, listing Robert G. Elves as the manufacturer.
The pilot, identified as Dr. Robert G. Elves, was the sole fatality in the accident. Background information included in the report context describes Elves as a retired U.S. Air Force officer and chemist. He was a recognized member of the aviation community and a member of the Aircraft Owners and Pilots Association (AOPA). Elves was also known for advocating safety measures, specifically the use of helmets in general aviation cockpits.
The release of a preliminary report is a standard procedure for the NTSB, typically occurring within two weeks of an accident. It serves to inform the public and the aviation industry of the basic facts established on-site. However, stakeholders should note that the investigation is far from complete.
The next major milestone will be the release of the Factual Report, which usually arrives several months later. This document will provide a deep dive into pilot logs, maintenance records, and toxicology results, offering a comprehensive view of the human and mechanical factors involved. The final determination of probable cause is generally not released until the Final Report is completed, a process the NTSB estimates will take between 12 and 24 months.
As the investigation progresses, the NTSB will post publicly available factual data, including photos and witness statements, to its Docket Management System.
NTSB Issues Preliminary Findings on Fatal Experimental Aircraft Crash in Arizona
Crash Timeline and Site Details
Investigative Focus
Aircraft and Pilot Background
Pilot Profile
AirPro News Analysis: The Path to a Final Report
Sources
Photo Credit: NTSB
Regulations & Safety
NTSB Preliminary Report on Fatal Carbon Cub Crash in Idaho
The NTSB released a preliminary report on the fatal CubCrafters Carbon Cub crash in Idaho involving a wire strike and two fatalities.
The National Transportation Safety Board (NTSB) has released its preliminary report regarding the fatal aviation accident that occurred on January 27, 2026, near Montour, Idaho. The crash of the CubCrafters CCX-1865 Carbon Cub, registered as N126C, resulted in the deaths of two individuals, including a prominent local meteorologist. The report confirms that the aircraft collided with power lines while operating in the rugged terrain of the Payette River’s Black Canyon.
According to the NTSB’s findings, the flight was part of a “Media Evaluation Program” conducted by the aircraft manufacturer, CubCrafters. The program, which allowed media figures to evaluate aircraft for content creation, has been suspended following the tragedy. Investigators have recovered data recording devices, including GoPro cameras, which may provide critical insight into the final moments of the flight.
The preliminary report outlines the specific timeline and trajectory of the accident. On the morning of January 27, the aircraft was operating under Part 91 general aviation rules in Gem County, Idaho. The flight took place in the Black Canyon area, a region known for its scenic river views but also for the hazards presented by its complex terrain.
Investigators determined that the accident sequence began at approximately 10:58 AM MST. The aircraft struck a set of power lines spanning the Payette River. The collision severed the lines, causing a significant power outage that affected an estimated 7,000 customers in Gem County and Garden Valley. Following the wire strike, the aircraft impacted the frozen surface of the river, coming to rest in the water and ice.
The wreckage was located within the icy river. During the recovery process, investigators secured GoPro cameras from the crash site. The NTSB has indicated that these devices could yield high-definition video evidence regarding the cockpit environment and flight parameters leading up to the collision.
The aircraft involved was a CubCrafters CCX-1865 Carbon Cub FX, a modern Short Takeoff and Landing (STOL) aircraft designed specifically for backcountry operations. The specific airframe, N126C, was owned by the manufacturer, CubCrafters, and had been loaned to the pilot for review purposes.
The flight was conducted under the auspices of CubCrafters’ “Media Evaluation Program.” This initiative provided aircraft to select aviation journalists and influencers for independent review. Following the accident, CubCrafters announced a temporary suspension of the program to review safety protocols. In a statement, the company expressed deep sadness regarding the loss of life and emphasized its cooperation with the NTSB and Federal Aviation Administration (FAA). The crash claimed the lives of two experienced members of the aviation community.
Roland Steadham, 67, was identified as the pilot. Steadham was a well-known figure in Boise, Idaho, serving as the Chief Meteorologist for KBOI-TV (CBS 2). Beyond his broadcasting career, Steadham was a veteran aviator with over 3,000 flight hours. He held a commercial pilot certificate and possessed experience in a variety of aircraft, including gliders and jets.
Dallin Laufenberg was identified as the passenger. Reports suggest Laufenberg was an active member of the local aviation community, with some sources linking him to operations at Nampa Airport, though the NTSB report focuses primarily on the factual circumstances of the crash rather than biographical details.
The preliminary details of this accident highlight the persistent danger of wire strikes in low-level backcountry flying. River canyons often present a “terrain trap” where power lines are strung across gaps, becoming nearly invisible against complex backgrounds like running water, rocks, or snow. While the Carbon Cub is a highly capable STOL aircraft designed for this environment, the visibility of obstacles remains a critical human factor challenge. The recovery of onboard video will likely be pivotal in determining whether the wires were marked or if environmental conditions contributed to the pilot’s inability to see the obstruction in time.
The current document released by the NTSB is a preliminary report, which contains factual information gathered at the scene but does not determine a probable cause. The investigation will proceed through several phases:
What is a Preliminary Report? What is the Carbon Cub FX? Is the investigation complete? Sources: NTSB Preliminary Report, CubCrafters Official Statement, KBOI-TV (CBS 2), Gem County Sheriff’s Office
NTSB Releases Preliminary Findings on Fatal Carbon Cub Crash in Idaho
Accident Sequence and Site Details
Wire Strike and Impact
Wreckage Recovery
Aircraft and Operational Context
Media Evaluation Program Suspended
Victim Profiles
AirPro News Analysis
Investigation Timeline
Frequently Asked Questions
An NTSB preliminary report is an initial document released shortly after an accident. It establishes the basic facts, such as time, location, and aircraft type, but does not analyze the cause or assign blame.
The Carbon Cub FX is a high-performance, lightweight aircraft modernized from the classic Piper Cub design. It is widely used for backcountry and off-airport operations due to its ability to take off and land in very short distances.
No. The investigation is ongoing. A full determination of probable cause typically takes more than a year to complete.
Photo Credit: CubCrafters
Regulations & Safety
Delta Flight Returns to Houston After Passenger Disturbance and Assault
Delta flight from Houston returned due to a passenger disturbance involving an attempted cockpit breach and assault. FAA to investigate.
This article summarizes reporting by Houston Public Media and Adam Zuvanich.
A Delta Air Lines flight departing from William P. Hobby Airports (HOU) in Houston was forced to make an emergency return early Wednesday morning, February 18, 2026, following a significant passenger disturbance. While initial reports from the flight deck indicated a potential attempt to breach the cockpit, the airline has since clarified the nature of the security threat.
According to reporting by Houston Public Media, the incident occurred shortly after takeoff on Delta Flight 2557, a Boeing 717 service bound for Atlanta. The aircraft, carrying 85 passengers and five crew members, returned safely to Houston approximately 15 minutes after departure.
Data from FlightAware indicates that the flight departed HOU at approximately 5:25 a.m. local time. Within minutes of becoming airborne, the flight crew declared an emergency. The Houston Police Department (HPD) confirmed to local reporters that they received a call at 5:38 a.m. regarding a disturbance on board.
Upon the aircraft’s return to Hobby Airport at roughly 5:40 a.m., law enforcement officers met the plane at Gate 32. HPD officers subsequently detained a male suspect. Footage and witness accounts suggest the individual was led off the aircraft in handcuffs. The flight eventually re-departed for Hartsfield-Jackson Atlanta International Airport (ATL) approximately 90 minutes after the security event.
A notable divergence has emerged between the immediate operational communications from the pilots and the subsequent corporate statement released by Delta Air Lines regarding the severity of the threat to the flight deck.
According to audio recordings from Broadcastify, reviewed by AirPro News, the pilot explicitly informed air traffic control of the situation in real-time:
“We had a passenger get up and try to access the cockpit.”
, Pilot transmission, Delta Flight 2557 (via Broadcastify)
This radio message aligns with the initial statement provided by an HPD spokesperson, who noted the call was received because “someone tried to breach a cockpit.”
However, in a later statement, Delta Air Lines provided a nuanced clarification, emphasizing that the physical security of the flight deck was not compromised. The airline stated:
The customer “approached crew members and other passengers but did not make contact with or attempt to access the flight deck.”
, Delta Air Lines Official Statement
The difference between a pilot reporting an attempt to “access the cockpit” and a corporate statement denying an “attempt to access” often comes down to technical definitions. In post-9/11 aviation security, any aggressive movement toward the front galley while the aircraft is in flight is treated by the flight crew as an imminent threat to the cockpit, triggering immediate diversion protocols. Delta’s corporate clarification likely relies on the fact that the passenger did not physically touch or manipulate the reinforced cockpit door, despite moving aggressively in that direction.
Beyond the security concerns regarding the flight deck, verified reports confirm that physical violence occurred in the cabin. During the exchange with air traffic control, the pilot requested paramedics meet the aircraft, stating that the suspect “did assault another passenger.”
Additional reporting by FOX 5 Atlanta included a witness account from a male passenger who stated he was punched by the suspect. The suspect’s identity has not been released, though unverified reports suggest the incident may have involved a mental health crisis.
The Federal Aviation Administration (FAA) has confirmed it will investigate the incident. This event adds to the growing list of unruly passenger reports in 2026. According to FAA data cited in the research report:
Delta Air Lines reiterated its stance on such disturbances in their statement to the press:
“The safety of our customers and crew is paramount, and Delta has zero tolerance for unruly behavior.”
, Delta Air Lines
The airline apologized to customers for the delay, and the flight completed its journey to Atlanta later that morning without further incident.
Delta Flight Returns to Houston Following Passenger Disturbance and Reported Assault
Incident Timeline and Police Response
Discrepancy in “Cockpit Breach” Accounts
AirPro News Analysis
Reports of Physical Assault
Regulatory Context and Statistics
Sources
Photo Credit: AirNav Radar
-
Regulations & Safety7 days agoFour Killed in Tennessee-Registered Plane Crash Near Steamboat Springs
-
Regulations & Safety6 days agoJet2 Flight Diverts to Brussels After Violent Midair Altercation
-
Technology & Innovation6 days agoHorizon Aircraft Partners with North Aircraft for Cavorite X7 Wing Production
-
Regulations & Safety3 days agoNTSB Report Blames FAA Airspace Failures for Deadly Potomac Midair Collision
-
Business Aviation4 days agoPrivate Aviation Faces Trust Crisis Amid Industry Consolidation and FAA Rules
