Travelers in and out of the Washington, D.C., and Baltimore region faced a turbulent Friday evening on March 13, 2026, after an unexpected and mysterious chemical odor at a crucial air traffic control facility triggered ground stops at multiple major airports. The Federal Aviation Administration (FAA) and the U.S. Department of Transportation scrambled to identify and resolve the issue, which ultimately traced back to a single overheated circuit board. But for thousands of passengers and airline staff, the ripple effects of that circuit board’s meltdown were felt well into the night—and perhaps even into the following day.
According to WTOP and corroborated by statements from the FAA, the trouble began around 4:50 or 5:30 p.m. when air traffic controllers at the Potomac Consolidated Terminal RADAR Approach Control (TRACON) facility in Warrenton, Virginia, detected a “strong chemical smell.” This facility is no minor outpost; it coordinates airspace for the entire Baltimore-Washington and Richmond-Charlottesville corridor, making its smooth operation essential for flights in and out of the region’s busiest airports.
As a result, the FAA issued immediate ground stops at Ronald Reagan Washington National Airport (DCA), Washington Dulles International Airport (IAD), and Baltimore-Washington International Thurgood Marshall Airport (BWI). Richmond International Airport (RIC) and Charlottesville-Albemarle were also impacted, though Philadelphia International Airport (PHL) only experienced ground delays due to a separate equipment outage. Hundreds of flights were halted on the tarmac, and thousands of travelers suddenly found themselves stuck in terminals or confined to their seats, waiting for updates that were slow to arrive.
“The FAA has temporarily stopped traffic at Ronald Reagan Washington National Airport, Washington Dulles International Airport, and Baltimore-Washington International Airport because of a strong chemical smell at the Potomac TRACON that is impacting some air traffic controllers,” an FAA spokesperson confirmed to WJZ and FOX 5. The agency was quick to assure the public that, while some controllers reported mild symptoms, no injuries required hospital transport, as reported by Fauquier County Fire Rescue System and Prince William County’s hazardous materials team.
Transportation Secretary Sean Duffy took to social media and official channels to provide updates as the situation unfolded. In a post on X, Duffy explained, “The ground stop is over and operations have resumed. Firefighters from Fauquier County and Prince William County confirm there is no danger to air traffic controllers, and they are returning to the Potomac TRACON. The source of the strong odor was traced to a circuit board that overheated, and it was replaced.” Duffy’s assurance was echoed by the FAA, which stated that the incident was under control and that air traffic controllers could safely return to their posts.
But the technical fix didn’t immediately clear the skies. With such a large volume of flights affected, the backlog was immense. Between 25% and one-third of all departing flights from the affected airports were delayed, according to WTOP. By 8:40 p.m., the FAA website showed average ground delays of about 222 minutes at DCA and more than 150 minutes at BWI. “There’s going to be ripple effects all night long because the delays were growing by the second it looked like,” said WTOP transportation reporter Tom Roussey. “If anything throws them off, it creates a ripple effect, and I’m sure they’ll be dealing with this the rest of the night, maybe even into tomorrow.”
Passengers caught in the chaos voiced their frustration and fatigue. Maggy Osha, who was trying to get home to San Francisco, told WJZ, “They just keep delaying it. I don’t know how long it will be delayed for...but it’s super frustrating that now it’s going to land at 3 a.m., so now I won’t get any sleep.” Another traveler, Grace Wilkins Maxwell, found herself stranded at Dulles International, waiting for a flight to Louisville, Kentucky. “I’m not convinced anyone is leaving D.C. tonight,” she said, noting that she might have to take a train home to Richmond if things didn’t improve.
Some passengers, like WTOP anchor Mark Lewis, experienced the ordeal from the tarmac. His flight at Reagan National was scheduled to leave at 5 p.m. but didn’t begin taxiing until 7 p.m. “The whole flight applauded when they heard the good news,” Lewis reported, capturing the sense of collective relief. Others weren’t so lucky. Maureen Dewey, 60, was en route to Hartford, Connecticut, and found her flight canceled after boarding and waiting for more than two hours for her luggage. “The biggest issue I see is the lack of communication from the airlines,” Dewey told The New York Times. “Nobody has been down here telling us what’s going on. Nobody knows what’s going on.”
Meanwhile, airport officials and the FAA urged travelers to keep a close eye on the FAA website and their airlines for the latest updates. “Airlines are once again resuming regular operations and preparing departures. Expect residual delays this evening,” BWI Airport said in a post on X. “For flight-specific updates, please confirm flight status with your airline. We appreciate the patience of passengers impacted by the delays.”
Behind the scenes, emergency responders from Fauquier and Prince William counties worked swiftly to ensure the safety of the TRACON facility. Firefighters and hazardous materials teams responded to the “potential hazardous materials incident,” evaluating employees and confirming there was no ongoing danger. The FAA even relocated some controllers to a training facility to keep operations running, though incoming flights were diverted at times due to congestion, according to independent reports cited by the Hindustan Times.
As the evening wore on, the ground stop was officially lifted, but the domino effect of delays and cancellations continued to disrupt travel plans. The FAA projected that ground delays at Reagan National would last until midnight, and until 1 a.m. at BWI. Dulles and Richmond airports, however, were expected to return to normal operations sooner. Still, as Dulles warned on its website, passengers could expect “residual cancellations and delays.”
For all the inconvenience, the incident served as a stark reminder of just how interconnected and sensitive the nation’s air travel infrastructure can be. A single overheated circuit board—a seemingly minor technical hiccup—brought travel across a major metropolitan corridor to a standstill for hours. As flights gradually resumed and weary travelers finally made their way home, the night ended with a collective sigh of relief and, perhaps, a newfound appreciation for the unseen work of air traffic controllers and emergency responders.