Army Pauses Helicopter Flights After D.C. Near Miss

Today at 4:31 pm

3012 posts

Army Pauses Helicopter Flights After D.C. Near Miss \ Newslooks \ Washington DC \ Mary Sidiqi \ Evening Edition \ The U.S. Army has temporarily paused helicopter flights near Ronald Reagan Washington National Airport after two commercial planes were forced to abort landings due to a Black Hawk helicopter. The suspension follows a deadly January midair collision at the same airport. FAA and NTSB investigations are ongoing amid growing scrutiny over military aircraft activity in restricted airspace.

Quick Looks

Army halts 12th Aviation Battalion flights near Reagan National Airport.
Suspension follows two commercial flight go-arounds due to a Black Hawk.
Incident involved a Delta A319 and Republic Airways Embraer E170.
Flights paused since Friday following Thursday’s close calls.
January’s fatal collision killed 67 in worst midair crash in 20+ years.
The same unit’s helicopter was involved in January’s crash.
FAA prohibits helicopters in shared airspace near Reagan post-crash.
Three flights aborted landings Sunday due to a police helicopter.
Investigations underway by both FAA and NTSB.
Newark Airport also saw delays due to cloud cover and staff shortages.

Deep Look

The temporary pause in U.S. Army helicopter operations around Ronald Reagan Washington National Airport may appear to be a precautionary step following another near-disaster. But in truth, it marks the latest development in an escalating pattern of aerial risk in one of the most tightly regulated and sensitive airspaces in the country. Thursday’s incident—where two commercial jets had to abort landings due to a military Black Hawk—adds urgency to what aviation experts say is a failure to modernize and coordinate military-civilian air traffic in real time.

This pause, however temporary, speaks volumes about the systemic fragility and bureaucratic tension between civilian oversight bodies like the FAA and operational branches like the Pentagon. It’s a reflection of how even within the heart of U.S. airspace, chain-of-command clarity and real-time communication failures can push civilian lives into danger.

January’s Tragedy: A Missed Warning

The recent incident came less than five months after the deadliest U.S. midair collision in over two decades, which involved a commercial airliner and a Black Hawk helicopter. That crash, which killed 67 people, should have been a watershed moment—triggering massive airspace reforms near Reagan Airport.

Yet despite emergency policy changes by the Federal Aviation Administration (FAA)—including barring helicopters from overlapping airspace with landing commercial aircraft—Thursday’s close call suggests enforcement remains incomplete or inconsistently applied.

What’s more troubling is that both helicopters in these incidents were operated by the 12th Aviation Battalion, responsible for priority air transport for top Department of Defense officials. These are not rogue pilots. These are missions deeply embedded in the infrastructure of national security, with flight paths approved by Pentagon Air Traffic Control.

Reagan National: An Airspace Like No Other

Reagan is located within restricted Class B airspace, in proximity to the White House, the Pentagon, the Capitol, and Andrews Air Force Base. It’s surrounded by complex flight corridors, temporary flight restrictions (TFRs), and VIP movement routes. The airport is also uniquely structured with a north-south runway orientation, requiring precision landings parallel to the Potomac River.

It’s no surprise, then, that the NTSB flagged Reagan in March as a national hotspot for aviation close calls, citing poor coordination, outdated communication channels, and a failure to learn from previous incidents.

Despite its strategic significance, there is no integrated command system to manage concurrent military and civilian flights dynamically—something critics say is “shockingly archaic” for post-9/11 aviation.

Thursday’s Go-Arounds: A Case Study in Risk

The latest incident involved two jets: a Delta Airbus A319 and a Republic Airways Embraer E170, both ordered into “go-arounds”—a high-risk maneuver typically triggered by runway or airspace conflict.

At the center was PAT25, a Black Hawk helicopter following FAA-approved routes but redirected by Pentagon ATC to overfly the Pentagon’s helipad. Though technically compliant with procedures, its presence disrupted final approach paths. As a result, two heavily loaded jets were forced to ascend, loop, and re-enter approach—a time-consuming, fuel-intensive, and risky process in congested airspace.

This is exactly the kind of confusion the FAA’s March restrictions were designed to prevent. Yet the FAA now finds itself in the awkward position of investigating violations it may have been unable to enforce properly due to conflicting jurisdiction with the Department of Defense.

Military Mission vs. Civilian Safety

Therein lies the deeper problem: Who truly controls American airspace when national security is invoked?

Priority air transport helicopters, such as those operated by the 12th Aviation Battalion, routinely ferry high-ranking officials—including Joint Chiefs, cabinet members, and foreign dignitaries. These missions often override normal airspace restrictions. In moments of urgency, Pentagon ATC can take precedence over Reagan’s FAA tower, resulting in mixed messaging and, at times, split-second decisions with enormous consequences.

Yet that flexibility comes at a steep price. Experts argue that allowing two parallel command structures to issue real-time flight instructions—one for national security, one for public transport—without a unified operational interface is untenable in 2024.

“The system wasn’t built to handle simultaneous command,” said a former FAA regional controller. “And now we’re seeing the consequences of trying to fly 21st-century missions with 20th-century infrastructure.”

A Tactical Pause or Turning Point?

According to sources within the Army, the decision to pause helicopter operations near Reagan since Friday is not a permanent grounding but a strategic timeout—likely to review procedures, coordinate with the FAA, and reset public confidence.

This comes after the battalion only recently resumed flights following the January crash, with a phased return-to-flight plan that was supposed to extend through the summer.

Meanwhile, the FAA has confirmed that even local law enforcement flights—like a police helicopter that disrupted three landings on Sunday—pose similar dangers under current protocol. It’s a larger reminder that military and emergency aviation missions are increasingly rubbing up against civilian traffic in high-volume zones, and the current system isn’t agile enough to adapt.

What Comes Next?

FAA and NTSB investigations into Thursday’s incident are ongoing, with public findings expected in coming months.
A reexamination of Pentagon ATC autonomy over shared airspace is likely, possibly leading to formalized FAA override capabilities during certain windows.
Congressional oversight hearings may be on the horizon if another near-miss or tragedy occurs in D.C. airspace.
Integrated airspace control systems—similar to those used in NATO operations abroad—may become the model for future shared airspace management in the U.S.

In the meantime, millions of passengers will continue to fly into and out of Reagan Airport, often unaware that above them, a quiet turf war over control of the skies is playing out.