Washington Dulles disrupts 100+ flights
- FAA ground stops hit Washington Dulles, Reagan National, and BWI on March 13 after an overheated circuit board shut down Potomac TRACON operations. - Dulles alone saw more than 260 disrupted flights, with average departure delays above 3 hours before traffic resumed around 8 p.m. - The episode matters because one Virginia control facility handles much of the DC region’s airspace, so a single failure can snarl multiple hubs.
Flights at Washington Dulles were not the only problem here — the real story was that one air-traffic-control facility in Virginia briefly became the weak point for the whole Washington region. On Friday, March 13, controllers at Potomac TRACON stopped work after a strong chemical smell was traced to an overheated circuit board. That forced the FAA to issue ground stops for Dulles, Reagan National, and BWI, with ripple effects reaching Richmond and other nearby airports. ### What actually broke? The immediate failure was not weather and not an airline systems issue. It was an equipment problem inside Potomac Consolidated Terminal Radar Approach Control — the facility that sequences and manages traffic for much of the DC-area airspace. Emergency crews and a HAZMAT team responded, the smell was traced to an overheated circuit board, and the board was replaced before controllers returned to work. (aol.com) ### Why did Dulles get hit so hard? Dulles depends on the same regional control system as Reagan and BWI. So when Potomac TRACON went down, the FAA could not just keep feeding planes into Dulles normally while the other airports slowed. The agency halted traffic at all three main Washington-area airports, which meant departures stacked up on the ground and inbound traffic had to be spaced out or diverted. (aol.com) ### How big was the disruption? Pretty big. At the height of the outage, FlightAware data cited by CNBC showed more than 260 flights disrupted at Dulles, alongside more than 325 at Reagan and about 215 at BWI. Average departure delays ran from 1 hour to more than 3 hours across the three airports, and CNN’s reporting said Dulles delays topped 3 hours before easing later in the evening. (aol.com) ### Why did one outage spread across multiple airports? Because air traffic control is a network, not a set of isolated towers. Potomac TRACON handles the crowded shared airspace over Washington and nearby airports, including Dulles, Reagan, BWI, Richmond, Charlottesville, Joint Base Andrews, and others. Think of it like one busy switchboard for several airports at once — if the switchboard goes dark, the slowdown is regional almost immediately. (aol.com) ### Did the FAA get things moving again quickly? Sort of. Flights began resuming around 8 p.m. after more than two hours of halted traffic, but lifting a ground stop does not instantly clear the mess. Aircraft are out of position, crews time out, gates stay occupied, and passengers miss inbound connections. That is why delays were still running high even after the immediate equipment issue was fixed. (aol.com) ### Is this still a problem on May 9? Not in the sense of an active Dulles equipment outage. The FAA’s current National Airspace System dashboard on May 9 shows no live IAD-specific outage tied to that March failure. Today’s FAA air traffic report points instead to weather-related risks in places like New York, Boston, Dallas-Fort Worth, Houston, and San Francisco. ### So why does this story still matter? (cnbc.com) Because it showed how fragile the DC airspace setup can be when a single facility fails. Dulles is a major international gateway, but the bottleneck was upstream in the control network, not at the terminal. That means future disruptions of the same kind can again look like an “airport delay” story when the real issue is regional air-traffic-control infrastructure. (nasstatus.faa.gov) ### Bottom line Washington Dulles did disrupt hundreds of trips, but not because Dulles itself melted down. A failed circuit board at Potomac TRACON briefly choked the control system for the whole DC region — and that is why one technical fault turned into a multi-airport travel mess. (aol.com)
