This article summarizes reporting by Reuters.

Congress Moves to Mandate Military Helicopters Tracking Near DC Following Fatal Collision

Following a year marked by tragedy and alarming safety lapses in the National Capital Region, Congress has unveiled legislation requiring U.S. military helicopters to broadcast their positions when operating near Reagan Washington National Airport (DCA). The provision, included in the National Defense Authorization Act (NDAA) for Fiscal Year 2026, aims to close a critical information gap between military pilots and commercial air traffic controllers.

According to reporting by Reuters, the legislation was released late Sunday, December 7, 2025. It mandates that military helicopters on training missions in the crowded airspace around Washington, D.C., utilize safety alerts to prevent collisions with commercial aircraft. This legislative move comes nearly a year after a catastrophic mid-air collision and a subsequent series of near-miss incidents that have drawn intense scrutiny from lawmakers and safety regulators.

Closing the “Stealth” Gap in Domestic Airspace

The core of the new legislation addresses the military’s historical exemption from using Automatic Dependent Surveillance-Broadcast (ADS-B) technology during certain domestic operations. ADS-B allows aircraft to broadcast their altitude, velocity, and position to ground controllers and other nearby planes. Without this technology active, military helicopters can effectively appear invisible to the automated collision avoidance systems used by commercial airliners.

Under the proposed NDAA provisions, the Department of Defense (DoD) must ensure that helicopters conducting training missions near DCA broadcast this vital data. The goal is to ensure that commercial pilots and air traffic controllers have real-time visibility of military assets operating in one of the nation’s busiest flight corridors.

In addition to the immediate mandate for the Capital region, the bill requires the Pentagon to conduct a feasibility study within 180 days. This study will analyze the implications of installing ADS-B technology across the broader military helicopter fleet, weighing the costs and combat readiness concerns against the imperative for civilian safety.

A Response to Tragedy: The January 2025 Collision

The legislative push is a direct response to the fatal events of January 29, 2025. On that day, a U.S. Army Black Hawk helicopter collided with American Airlines (American Eagle) Flight 5342 near DCA. The crash resulted in 67 fatalities, 64 on the commercial jet and three on the helicopter. Investigations revealed that the Black Hawk was on a training mission and was not broadcasting its position via ADS-B, leaving the commercial pilots unaware of the converging threat until it was too late.

The urgency of the legislation was further underscored by a second incident in May 2025. According to reports summarized by the Washington Post, another Army Black Hawk was involved in a “near miss” with two airliners at DCA. In that instance, the helicopter reportedly took a “scenic route” near the commercial flight path, forcing jets to abort landings. These repeated lapses suggested a systemic failure rather than an isolated error.

Data Reveals a Decade of Risk

While the January crash was the catalyst for the new bill, data from the National Transportation Safety Board (NTSB) indicates that the airspace has been hazardous for years. NTSB records show approximately 15,000 close-proximity events between military and civilian aircraft near DCA between October 2021 and December 2024.

To address this historical lack of transparency, the NDAA includes a retroactive reporting requirement. The Pentagon must disclose to Congress the number of near-miss incidents between military and commercial aircraft over the last 10 years. This provision suggests lawmakers suspect that the scale of the risk has been underreported for a decade.

Stakeholder Reactions and Military Pushback

The legislation has drawn strong support from lawmakers who have criticized the Army’s safety culture. Senator Ted Cruz (R-Texas) has been a vocal proponent of “technological transparency” in domestic airspace.

“The Army chose to protect its bureaucratic [interests]… those deaths will be on the Army’s hands.”

, Senator Ted Cruz (R-Texas), via Senate Commerce Committee records

Senator Maria Cantwell (D-Washington) also condemned the May incident, labeling it “outrageous” and demanding immediate action from the Federal Aviation Administration (FAA) and the Defense Secretary.

Historically, the Army has resisted universal ADS-B adoption, citing Operational Security (OPSEC). The military argument posits that broadcasting movements could compromise sensitive mission profiles. However, the new legislation attempts to bypass this objection by specifically targeting training missions in domestic airspace, where the threat of enemy surveillance is negligible compared to the risk of collision with civilian traffic.

AirPro News Analysis

The inclusion of these mandates in the NDAA signals a significant shift in the balance of power between military autonomy and civilian aviation safety. For years, the “see and avoid” principle was deemed sufficient for visual flight rules (VFR) traffic, including military helicopters. However, the density of modern air traffic and the speed of commercial approach patterns have rendered unassisted visual separation obsolete in complex terminal areas like DCA.

By forcing a 10-year retrospective report, Congress is likely preparing to audit the military’s internal safety reporting culture. If the Pentagon’s internal numbers differ significantly from the NTSB’s data on “close-proximity events,” it could trigger further oversight hearings regarding military aviation conduct in the National Capital Region.

Sources

Sources: Reuters, National Transportation Safety Board (NTSB), Washington Post, Senate Commerce Committee

This article is based on an official press release from the U.S. Navy and accompanying investigation reports.

Navy Investigation Reveals $164 Million in Damages Across Four Major Incidents During Truman Deployment

On December 4, 2025, the U.S. Navy released the findings of four separate investigations into serious mishaps that occurred during the USS Harry S. Truman Carrier Strike Group’s (CSG) recent deployment. Spanning from September 2024 to May 2025, the deployment was marked by high-intensity combat operations in the Red Sea but was also marred by a series of preventable errors, equipment failures, and communication breakdowns.

According to the official release and investigation reports, the incidents resulted in approximately $164 million in damages. While there was no loss of life, the mishaps included a friendly fire shootdown, a collision with a merchant vessel, and the loss of two additional Military-Aircraft. The findings paint a picture of a fleet under extreme strain, operating in a high-threat environment dubbed “Operation Rough Rider.”

Breakdown of the Four Investigated Incidents

The Navy’s investigations detailed four distinct events that contributed to the significant financial and operational toll of the deployment. These incidents ranged from mechanical failures to severe lapses in judgment and situational awareness.

1. Friendly Fire Incident (December 22, 2024)

Perhaps the most alarming incident occurred just one week after the strike group entered the Red Sea. The guided-missile cruiser USS Gettysburg (CG-64) fired an SM-2 missile at a friendly F/A-18F Super Hornet returning to the carrier, destroying the aircraft. Both crew members ejected safely and were rescued.

Investigators found that the incident was driven by a combination of system failures and human error. The cruiser’s Identification Friend or Foe (IFF) system and Link 16 data link were reportedly degraded, preventing automatic identification of the jet. However, the crew failed to report these malfunctions up the chain of command. Compounding the issue were fatigue and a lack of integrated training between the ship and the air wing.

“Watchstanders were operating under extreme fatigue, with some on duty for over nine hours in a high-threat environment.”

, Investigation Findings

As a result of these failures, the Commanding Officer of the USS Gettysburg was relieved of command.

2. Collision at Sea (February 12, 2025)

In February, the USS Harry S. Truman collided with the merchant vessel M/V Besiktas-M near Port Said, Egypt. The collision left a 15-foot gash in the carrier’s hull and damaged a sponson. The investigation deemed the event “fully avoidable,” citing the bridge team’s failure to maintain situational awareness and the decision to travel at an unsafe speed for the conditions.

Following the incident, Capt. Dave Snowden, Commanding Officer of the USS Harry S. Truman, was relieved of duty due to a loss of confidence in his ability to command.

3. Hangar Bay Aircraft Loss (April 28, 2025)

During a high-speed evasive maneuver to avoid an incoming Houthi ballistic missile, an F/A-18E Super Hornet and a tow tractor fell overboard from the hangar bay. The primary cause was identified as a brake system failure on the aircraft, exacerbated by poor communication between the bridge, flight deck control, and hangar bay control.

4. Arresting Wire Failure (May 6, 2025)

The final major incident involved the loss of an F/A-18F Super Hornet during a landing attempt. The #4 arresting wire failed due to a malfunctioning sheave damper caused by improper installation, specifically, a missing or improper clevis washer. The investigation cited “substandard maintenance practices” and low manning levels as contributing factors.

Operational Context and “Signalgate” Controversy

The deployment took place under the banner of “Operation Rough Rider,” a campaign aimed at degrading Houthi capabilities in Yemen. The air wing conducted over 1,000 air strikes and sustained operations for 52 days, including periods of 72 hours of continuous flight. This high operational tempo contributed significantly to crew fatigue and equipment strain.

Parallel to the operational findings, a political controversy known as “Signalgate” has drawn scrutiny to the deployment. Reports allege that Defense Secretary Pete Hegseth used an unsecure Signal group chat to share classified details regarding “Operation Rough Rider.” Critics, including Sen. Mark Warner, have suggested that such breaches may have endangered the lives of pilots by potentially exposing mission details to adversaries.

AirPro News Analysis

The release of these investigation results highlights a critical tension between operational tempo and fleet readiness. While individual commanders were held accountable for specific failures, the recurring themes of “degraded equipment,” “low manning,” and “training gaps” suggest systemic challenges within the fleet. The friendly fire incident, in particular, serves as a stark reminder of the “Fog of War,” demonstrating how quickly technology and communication can degrade in actual combat scenarios. As the Navy continues to face sustained threats in regions like the Red Sea, the balance between maintaining high-intensity operations and ensuring basic maintenance and training standards will likely remain a focal point for naval leadership.

Sources

Sources: U.S. Navy Press Release

This article is based on an official press release from Lockheed Martin.

Lockheed Martin Partners with Hadrian to Deploy “Factory-as-a-Service” for Missile Production

Lockheed Martin (NYSE: LMT) has announced a strategic collaboration with manufacturing technology company Hadrian to integrate advanced automated production capabilities directly into its supply chain. According to a press release issued on December 8, 2025, the two companies have signed a Memorandum of Understanding (MOU) to deploy Hadrian’s “Factory-as-a-Service” model within a Lockheed Martin Missiles and Fire Control (MFC) facility.

The partnership aims to accelerate the production of critical defense munitions, specifically targeting high-demand systems such as the PAC-3 MSE (Patriot Advanced Capability-3 Missile Segment Enhancement), THAAD (Terminal High Altitude Area Defense), PrSM (Precision Strike Missile), and GMLRS (Guided Multiple Launch Rocket System). By embedding Hadrian’s software-defined manufacturing cells directly into Lockheed Martin’s operations, the defense giant seeks to overcome supply chain bottlenecks and meet surging global demand.

The “Factory-as-a-Service” Model

This collaboration represents a departure from traditional defense procurement, where prime contractors typically outsource component manufacturing to external machine shops. Instead, Lockheed Martin is effectively “insourcing” Hadrian’s autonomous manufacturing capabilities.

According to the announcement, Hadrian will install a scalable, automated manufacturing cell at the customer’s site. This cell includes Computer Numerical Control (CNC) machines and robotics, all governed by Hadrian’s proprietary operating system, “Opus.”

Software-Defined Efficiency

The core of this innovation is the Opus software, which automates the end-to-end manufacturing workflow. Hadrian claims this system manages everything from quoting and scheduling to tool path generation and quality inspection. Data provided in the accompanying research report indicates that this approach allows for the production of precision parts up to 10 times faster and 40% more efficiently than legacy machine shops.

Tom Carrubba, Vice President of Production Operations at Lockheed Martin Missiles and Fire Control, emphasized the operational impact of this technology in the company’s statement:

“This project is a key enabler for Lockheed Martin to increase production output capacity, ensuring we can meet the high demand for our customers’ munitions needs.”

Meeting Urgent Production Targets

The integration of Hadrian’s technology comes as Lockheed Martin faces significant pressure to ramp up production rates for key weapon systems. The company is currently executing a plan to increase PAC-3 MSE production to 650 missiles per year by 2027, up from approximately 500 in 2024. Similarly, production for the GMLRS is being pushed toward a target of 14,000 rockets annually.

Chris Power, CEO of Hadrian, framed the partnership as a critical step in revitalizing the American industrial base. Power, who founded Hadrian in 2020 to address supply chain fragility, stated:

“America cannot afford to lose another generation of industrial capacity… We’re building the factories that will secure American leadership.”

The automated cells are designed to handle approximately 80-90% of manual tasks, such as machine programming and part inspection. This automation is intended to mitigate workforce shortages, specifically the lack of skilled machinists, that have historically constrained the U.S. defense industrial base.

AirPro News Analysis

We view this collaboration as a significant indicator of the evolving relationship between traditional “Prime” contractors and the emerging “defense tech” sector. Historically, large defense firms have been slow to modernize legacy manufacturing processes. However, Lockheed Martin’s “1LMX” digital transformation initiative suggests a strategic pivot toward software-defined manufacturing.

By adopting a “Factory-as-a-Service” model, Lockheed Martin is acknowledging that software expertise is as critical to modern warfare logistics as the hardware itself. If successful, this model could set a precedent for how major defense contractors manage their supply chains, moving away from fragmented networks of small suppliers toward centralized, automated production hubs embedded within their own facilities.

Frequently Asked Questions

What is the “Factory-as-a-Service” model?
It is a business model where a technology provider (Hadrian) installs and manages a self-contained, automated manufacturing cell inside a client’s facility (Lockheed Martin), rather than the client buying the machines or outsourcing the work entirely.

Which weapons systems will benefit from this deal?
The collaboration is focused on increasing production for the PAC-3 MSE, THAAD, PrSM, and GMLRS systems.

Who is Hadrian?
Hadrian is a manufacturing technology startup founded in 2020. The company recently raised $260 million in Series C funding in July 2025 and is backed by investors including Founders Fund and Andreessen Horowitz.

Sources

• Lockheed Martin Press Release