Codify — Article

Requires DoD reports on installing TCAS and ADS‑B IN across military helicopters

Directs the Secretary of Defense to evaluate technical, operational, and cost feasibility of fitting rotary‑wing fleets with collision‑avoidance and traffic‑surveillance receive capabilities and to recommend alternatives if infeasible.

The Brief

This bill directs the Secretary of Defense to study whether traffic alert and collision avoidance systems (TCAS) and automatic dependent surveillance–broadcast IN (ADS‑B IN) capabilities can be installed in U.S. military rotary‑wing aircraft. The Department must assess feasibility across technical, cockpit‑configuration, operational, and budgetary dimensions and propose substitute capabilities where full installation is not practical.

Why it matters: military helicopters routinely operate near civilian airspace and nonmilitary aircraft; improved traffic awareness could reduce midair risk and ease integration with civilian air traffic control. At the same time, retrofitting brings weight, power, electromagnetic emissions, and security tradeoffs that could affect combat and domestic missions and create significant retrofit costs for the services and sustainment infrastructure.

At a Glance

What It Does

The bill requires two separate feasibility reports to Congress—one on installing TCAS and another on installing ADS‑B IN across all military rotary‑wing aircraft. Each report must analyze costs, impacts on civilian airspace safety, cockpit reconfiguration needs, operational implications (combat, training, domestic security), and, if infeasible, recommend alternative systems or capabilities.

Who It Affects

The obligation falls on the Department of Defense and, by extension, the services that own rotary‑wing fleets (Army, Navy, Air Force, Marine Corps, plus the Coast Guard where relevant). It also implicates FAA air traffic operations, defense maintenance depots, avionics contractors, and civilian airspace users who share the same airspace.

Why It Matters

The reports will frame whether the military should pursue fleetwide avionics retrofits that change how helicopters interact with civilian ATC and with nearby traffic. The findings could drive procurement priorities, depot workload, and interagency coordination on airspace safety standards.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

The bill does not itself order installations; it asks the Secretary of Defense to map whether installations make technical and operational sense and what they would cost. For TCAS, that means assessing how an active collision‑avoidance system—one that interrogates transponders and issues proximity alerts—would integrate with existing radios, transponders, and cockpit displays on dozens of helicopter types and mission configurations.

For ADS‑B IN, the focus is on adding receive‑only traffic displays that use broadcast position data from nearby aircraft and ground stations.

Practically, the Department will need to catalogue fleet diversity: from light utility helicopters to heavy lift and specialized platforms. Each airframe presents different constraints—antenna placement, wiring runs, electrical power and cooling, vibration resilience, and cockpit space for displays.

Installation work may range from simple retrofit kits on newer airframes to substantial structural and systems changes on legacy platforms. The reports should identify which platforms could accept off‑the‑shelf solutions and which would require bespoke engineering or be essentially impractical to retrofit.Operational tradeoffs are central.

Active systems and some surveillance capabilities increase electromagnetic emissions and could interfere with emission control (EMCON) procedures in tactical operations; they also risk revealing platform locations if paired with broadcast‑out systems. Conversely, receive‑only ADS‑B IN provides traffic awareness without broadcasting position, but its utility depends on surrounding traffic broadcasting ADS‑B OUT and on coverage—low‑altitude flight over rural areas can have limited ADS‑B signals.

Finally, certification and sustainment matter: the services must consider whether installations require meeting FAA technical standards for shared airspace, how retrofits change maintenance cycles, and whether depot capacity and contractor supply chains can absorb the work and long‑term sustainment costs.

The Five Things You Need to Know

1

The bill mandates two separate feasibility reports: one on traffic alert and collision avoidance systems and one on ADS‑B IN capabilities for military rotary‑wing aircraft.

2

Each report must evaluate cost, impact on civilian airspace safety, required cockpit configuration changes, implications for combat/training/domestic security operations, and recommend alternatives if full installation is not feasible.

3

The statute ties the term “traffic alert and collision avoidance system” to the regulatory standard in 14 CFR 121.356 (or any successor regulation).

4

The obligation covers “all military rotary‑wing aircraft,” creating a fleetwide span that includes multiple services and a wide diversity of airframes rather than a limited subset.

5

If installations are judged infeasible, the Secretary must identify substitute systems or capabilities—meaning Congress expects actionable alternatives, not just a conclusion of impracticality.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 1

Short title

Provides the Act’s name, the “Military Helicopter Training Safety Act of 2025.” This is purely stylistic but identifies the bill’s focus on rotary‑wing safety and signals congressional intent to look at helicopter collision‑avoidance and surveillance capabilities.

Section 2(a)

Feasibility report—TCAS

Directs the Secretary to submit a report on installing a traffic alert and collision avoidance system in each military rotary‑wing aircraft. The provision requires the Department to address technical feasibility, costs, implications for cockpit layout, and how those systems would affect civilian airspace safety and military operations. Practically, this pushes DoD to inventory platform compatibility, estimate retrofit engineering and labor, and flag mission profiles where such systems would impair or improve safety.

Section 2(b)

Definition of TCAS

Defines the statutory meaning of “traffic alert and collision avoidance system” by reference to 14 CFR 121.356 (or successor), anchoring the study to a specific civil regulatory standard. That reference guides technical baselines (performance and interoperability expectations) and shapes how the Department compares military avionics to civilian TCAS requirements.

1 more section
Section 3

Feasibility report—ADS‑B IN

Parallel to Section 2, this section requires a separate report on installing ADS‑B IN capability fleetwide. The DoD must analyze costs, cockpit modifications, safety effects on civilian airspace, operational implications, and recommend alternatives if infeasible. This forces an assessment of receive‑only traffic awareness technology, its dependence on ADS‑B OUT adoption, and where ADS‑B IN would or would not materially improve situational awareness.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Defense across all five countries.

Explore Defense in Codify Search →

Who Benefits and Who Bears the Cost

Every bill creates winners and losers. Here's who stands to gain and who bears the cost.

Who Benefits

  • Civilian pilots and passengers — improved situational awareness and collision‑avoidance data from better integration with military traffic could reduce near‑misses and ease ATC deconfliction in busy shared airspace.
  • Air traffic control (FAA and facility operators) — clearer picture of helicopter traffic when military platforms use compatible systems, potentially simplifying traffic advisories and sequencing near airports and in congested corridors.
  • Local communities and airports — reduced risk of incidents in and near civilian airspace where military helicopters operate for training, search and rescue, or other missions.

Who Bears the Cost

  • Department of Defense and the individual services — acquisition, retrofit engineering, installation labor, and long‑term sustainment would come from Defense budgets or divert program funds.
  • Depot maintenance facilities and defense contractors — increased workload for retrofits and sustainment will require capital and staffing investments or new contractual scopes.
  • Operational units and training commands — adding avionics requires pilot and maintainer training, possible changes to procedures, and temporary aircraft downtime during installation, reducing readiness in the near term.

Key Issues

The Core Tension

The central dilemma is between improving airspace safety through fleetwide avionics upgrades and preserving military operational security, readiness, and affordability: systems that help prevent civilian collisions can also increase emissions, weight, cost, and maintenance burden in ways that degrade mission effectiveness or reveal sensitive movements, and there is no single technical solution that fully resolves those conflicting priorities.

Several practical and policy uncertainties could complicate implementation. First, the technical fit varies dramatically across helicopter models: some newer platforms can integrate modern avionics with modest changes, while legacy airframes may need major structural and electrical work that drives costs beyond practical limits.

Second, a system’s utility depends on the technical ecosystem: ADS‑B IN yields value only when surrounding aircraft or ground infrastructure broadcast useful data, and TCAS performance relies on compatible transponders in other aircraft.

Security and operational tradeoffs are not resolved by a feasibility study alone. Active interrogation and broadcasting raise concerns about revealing positions during domestic security missions or combat operations; receive‑only ADS‑B IN avoids outward emissions but may still be constrained by limited signal coverage at low altitude.

Certification and regulatory alignment with FAA standards present another layer: meeting civil regulatory baselines could be costly and unnecessary for platforms that primarily operate under different military safety regimes. Finally, the bill requires recommendations for alternatives, but it does not prioritize metrics (cost‑benefit thresholds, acceptable mission impacts, protective mitigations), leaving open how DoD should weigh safety gains against mission risks and program budgets.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.