On Dec. 10, 2025, the chair of the National Transportation Safety Board and bipartisan Senate aviation leaders warned that a provision in the new annual defense bill could weaken safety protections around Ronald Reagan Washington National Airport, increasing the risk of midair collisions in the capital’s already congested airspace. The caution follows an investigation into the Jan. 29 midair collision near the airport that killed 67 people, where investigators noted the Army Black Hawk helicopter was not using enhanced tracking technology. The officials said the disputed section would permit military aircraft to disable or waive enhanced tracking on certain missions, a change they contend would reduce transparency for nearby commercial flights. Hours after the warnings, the House approved the defense bill and sent it to the Senate for consideration next week.
Key Takeaways
- The warning was issued on Dec. 10, 2025, by N.T.S.B. chair Jennifer Homendy and bipartisan Senate aviation committee leaders, citing new language in the annual defense bill.
- The contested provision would allow military aircraft to switch off enhanced tracking equipment during national-security missions or when commanders determine the flight poses no commercial risk.
- Investigators of the Jan. 29 crash that killed 67 people focused on the fact that the Army Black Hawk helicopter involved lacked enhanced tracking at the time of the collision.
- Officials say the change could expand military flights in the Washington, D.C., terminal area without broadcasting position information to civilian pilots and air-traffic managers.
- The House passed the defense bill hours after the N.T.S.B. warning; the Senate is scheduled to consider the measure next week, with uncertainty about possible offsets or amendments.
- N.T.S.B. leaders described the provision as a rollback of safeguards in one of the nation’s most complex airspaces, raising concerns about collision risk and situational awareness.
Background
Ronald Reagan Washington National Airport sits under constrained, highly regulated airspace designed to protect flights near the nation’s capital. For years, procedures and technical layers — including transponder-based enhanced tracking systems — have been used to separate military and civilian traffic within the Washington area so that air-traffic controllers and pilots maintain mutual awareness. Past incidents have driven incremental safety requirements; the Jan. 29 collision intensified scrutiny of whether current rules and technologies are sufficient to prevent similar tragedies.
Congress routinely includes aviation-related provisions in broader defense and appropriations measures, and military operational needs sometimes prompt calls for exemptions from civilian procedures. Aviation regulators and safety boards generally balance mission flexibility against airspace safety; the current dispute centers on how that balance should be struck after a high-fatality accident that highlighted gaps in tracking and visibility between aircraft types.
Main Event
On Dec. 10, the N.T.S.B. chair publicly criticized language in the defense bill that she said would permit military pilots to deactivate enhanced tracking when flying through parts of the Washington terminal area during certain national-security missions or under military determinations of no risk. She argued that such a waiver would reduce transparency for other airspace users and complicate traffic coordination.
N.T.S.B. investigators probing the Jan. 29 midair collision have emphasized that the Black Hawk involved was not operating with enhanced tracking at the time, a detail that figures prominently in assessments of how the collision occurred. The board has not yet released a final probable cause determination, but officials say tracking limitations are a material safety concern in a crowded terminal environment.
Lawmakers moved quickly: the House passed the defense bill the same day as the N.T.S.B. warning, and the measure advanced to the Senate calendar. Senate aviation committee leaders from both parties joined the N.T.S.B. in flagging the provision, urging careful review before any final enactment that would alter current tracking requirements.
Analysis & Implications
The proposed waiver shifts decision authority to military operators for when enhanced tracking can be disabled, changing the safety calculus in one of the country’s busiest and most sensitive airspaces. If enacted, the provision could create operational gaps where commercial crews and air-traffic controllers have less information about military traffic, potentially increasing collision risk during peak flows and constrained approaches to Reagan National.
Operationally, enhanced tracking systems provide a common surveillance picture that supports conflict detection and timely separation. Removing or permitting deactivation of that layer decreases redundancy; in high-density terminal areas, redundancy is a primary defense against human and system errors. The Jan. 29 accident, which resulted in 67 fatalities, has made that redundancy a policy priority for regulators and many lawmakers.
Politically, the debate reflects tension between military operational flexibility and civilian safety regulation. The defense authorization process often accommodates classified or time-sensitive missions, but aviation-safety advocates say exemptions should be narrowly tailored and transparent. Passing a broad waiver could prompt administrative or legislative responses later if safety metrics deteriorate.
Comparison & Data
| Event | Date | Fatalities | Tracking Status |
|---|---|---|---|
| Jan. 29 midair collision (D.C. area) | Jan. 29, 2025 | 67 | Helicopter lacked enhanced tracking |
| Typical enhanced-tracking requirement start | Prior policy (varies) | — | Required in terminal area for most flights |
The table summarizes the Jan. 29 crash data and contrasts it with prevailing expectations that enhanced tracking should be active in terminal areas. Industry data show that layered surveillance and automatic broadcasting of position reduce near-miss incidents; removing layers tends to increase residual risk, especially in busy airspace.
Reactions & Quotes
Allowing military aircraft to fly without broadcasting locations in this airspace undermines protections put in place after prior incidents, and it could increase collision risk for civilian flights.
N.T.S.B. Chair Jennifer Homendy (public statement)
We are reviewing the defense bill language and its implications for safety as the Senate considers the measure next week.
Bipartisan Senate aviation leadership (committee statement)
The House voted to advance the defense authorization; any changes to aviation rules will need adjudication in the Senate process.
House leadership (vote summary)
Unconfirmed
- Whether the military aircraft involved in the Jan. 29 collision would have been eligible for the waiver; investigators have highlighted tracking gaps but have not stated waiver use.
- Whether the final Senate markup will include amendments to narrow or remove the helicopter tracking waiver; the outcome remains uncertain as deliberations proceed.
Bottom Line
The proposal in the defense bill would permit greater discretion for military operators to deactivate enhanced tracking through parts of Washington’s terminal area, a change safety officials warn could raise the risk to commercial flights in a densely trafficked airspace. The Jan. 29 collision that killed 67 people has heightened urgency around preserving surveillance and transparency between military and civilian aircraft.
As the Senate prepares to consider the defense measure next week, close attention will fall on whether lawmakers or regulators will adopt narrower language, set oversight conditions, or require compensating safeguards. Absent such adjustments, safety officials and aviation stakeholders say the provision would represent a notable rollback of protections in one of the nation’s most safety-critical airspaces.