TheMurrow

A ‘chemical smell’ just froze D.C.’s airspace—5 airports halted at once, and the FAA says it’s happened before this month

A “strong chemical smell” inside Potomac TRACON forced the FAA to hit pause—stopping traffic for five airports at once. The unnerving part: it already happened March 13, blamed then on an overheated circuit board.

By TheMurrow Editorial
March 28, 2026
A ‘chemical smell’ just froze D.C.’s airspace—5 airports halted at once, and the FAA says it’s happened before this month

Key Points

  • 1FAA temporarily stopped traffic after a “strong chemical smell” inside Potomac TRACON, triggering a rare, region-wide ground stop.
  • 2Five airports—DCA, IAD, BWI, CHO, and RIC—were hit at once, with BWI warning delays could linger after reopening.
  • 3Déjà vu: a similar March 13 TRACON shutdown was later blamed on an overheated circuit board, raising resilience questions.

A “strong chemical smell” is not supposed to be able to freeze a region’s air travel. Yet on Friday, March 27, 2026, that’s what happened inside Potomac TRACON, the FAA facility that quietly choreographs arrivals and departures for a huge slice of the Washington–Baltimore–Virginia corridor.

The Federal Aviation Administration responded the way safety systems are designed to respond when uncertainty enters the room: it hit pause. The agency temporarily stopped traffic, triggering ground stops that rippled across five airports at onceRonald Reagan Washington National (DCA), Washington Dulles International (IAD), Baltimore/Washington International (BWI), Charlottesville–Albemarle (CHO), and Richmond International (RIC)—before controllers began returning and operations moved toward normal.

What made the moment feel especially unnerving wasn’t only the breadth of the disruption. It was the déjà vu. The FAA acknowledged that a similar “strong chemical smell” had already forced a major ground stop earlier this month—on March 13, 2026—an incident later attributed by Transportation Secretary Sean Duffy to an overheated circuit board that was replaced.

“A TRACON disruption isn’t an airport problem. It’s a regional choke point—one building, five airports, and a night of knock-on delays.”

— TheMurrow

What happened on March 27: a smell, then a regional ground stop

Reports from the Associated Press describe the latest episode plainly: a “strong chemical smell” was detected inside Potomac TRACON, prompting the FAA to take immediate operational action. The agency temporarily stopped traffic, effectively preventing new departures from launching into airspace that could not be managed safely under the circumstances.

The impact was unusually broad because Potomac TRACON is not a single airport tower. The FAA ground stop affected five airports simultaneously—DCA, IAD, BWI, CHO, and RIC—covering much of the Washington-to-central Virginia travel footprint. Even travelers who never set foot in the region can feel the effects when schedules across airline networks begin to slide.

By later accounts, controllers were returning to work and the FAA expected normal flight operations to resume soon after. That said, “normal” rarely snaps back instantly. BWI warned of lingering delays even after the ground stop lifted, a reminder that air travel works like an interconnected conveyor belt: when it stops, the backlog doesn’t evaporate.

New York City Emergency Management even cautioned travelers that flights to Washington might be significantly delayed Friday night. That’s the hidden consequence of centralized air traffic infrastructure: a localized event can spread outward, not because the problem travels, but because the schedule does.

The key fact pattern—what we know and what we don’t

The public record as reflected in AP reporting is clear on the operational decision—traffic was stopped due to the odor—and on the list of affected airports. What remains unresolved, at least in authoritative reporting so far, is the root cause of the March 27 smell. The FAA had not, in the cited coverage, identified whether the odor came from an electrical component, a ventilation issue, or something else.

For passengers, the distinction matters less in the moment than the outcome: a safety-sensitive facility experienced an environmental condition that made continuing operations unacceptable.

Key Insight

Potomac TRACON isn’t a single airport tower. It’s a regional air-traffic node—so a local facility problem can halt multiple airports simultaneously.

Why Potomac TRACON matters: the “flight center” behind five airports

Most travelers can picture an airport control tower: a glass cab, controllers guiding takeoffs and landings. Potomac TRACON is different. It’s a Terminal Radar Approach Control facility—described in DOT/FAA terms and AP reporting as a “flight center”—that sequences and separates aircraft moving into and out of multiple airports across a region.

AP reporting describes Potomac TRACON’s scope as managing traffic for the Washington, D.C., Baltimore, Richmond, and Charlottesville areas. That geographic reach explains why a single incident can hit airports in Maryland and central Virginia in one stroke. DCA and IAD are obvious neighbors; CHO and RIC underscore the regional design.

TRACONs handle the messy, high-density middle: the space where aircraft are descending, climbing, merging, and being handed off between controllers. The work is continuous and time-sensitive. If controllers must evacuate, relocate, or even simply operate under uncertain conditions—like an unexplained chemical odor—the FAA’s safest move is to reduce complexity immediately.

“Air travel feels decentralized—dozens of airlines, hundreds of gates. Air traffic control is not. Nodes matter.”

— TheMurrow

A tower problem vs. a TRACON problem

A disruption to one airport’s tower can be severe, but it tends to stay more localized. A TRACON disruption has a broader blast radius because it governs shared airspace flows and handoffs. When it pauses, the FAA can’t safely keep feeding aircraft toward airports that rely on that sequencing.

That’s why the March 27 incident didn’t merely slow one runway; it forced a coordinated pause across five.

March 13 déjà vu: another “chemical smell,” another shutdown

The March 27 event landed differently because it wasn’t unprecedented. According to AP reporting, a similar incident occurred on Friday, March 13, 2026, when a strong chemical smell likewise impeded controllers and triggered a major ground stop affecting four airports: DCA, IAD, BWI, and RIC.

That earlier disruption lasted about an hour, AP reported—long enough to scramble schedules but short enough to demonstrate how quickly the FAA will pull the brake when conditions inside a facility are uncertain.

Transportation Secretary Sean Duffy publicly attributed the March 13 odor to a circuit—specifically an overheated circuit board—that was replaced. Firefighters confirmed no danger, and operations resumed. The framing matters: the “chemical smell” may have been the sensory signature of an electrical malfunction, not an external chemical release.

Still, the passenger impact was real. AP reported delays rising to roughly two hours at some airports, with between about 25% and one-third of flights departing the four affected airports delayed. Those are not marginal disruptions; they are system-wide jolts.

“A one-hour stop can become a two-hour delay—because the schedule is a chain, not a set of independent events.”

— TheMurrow

What repetition signals—and what it doesn’t

Two incidents in a month invite speculation, but responsible analysis has limits. AP reporting did not specify a definitive cause for March 27, and it remains unconfirmed whether it resembles the March 13 electrical issue. Repetition alone does not prove a systemic defect, but it does raise a pointed operational question: how resilient is a critical regional facility to environmental and equipment anomalies?

Aviation safety culture prizes caution. The challenge is ensuring that caution doesn’t become routine disruption.
5 airports
The March 27 FAA traffic stop rippled across DCA, IAD, BWI, CHO, and RIC at once—an unusually broad, regional impact.
≈ 1 hour
AP reported the March 13 disruption lasted about an hour—short operationally, but long enough to scramble schedules across multiple airports.
≈ 2 hours
During the March 13 incident, delays at some airports rose to roughly two hours—showing how recovery lags far behind the initial stop.
25%–33%
AP reported about a quarter to a third of departures were delayed at affected airports during March 13—system-level disruption, not a minor hiccup.

Ground stops, explained: the FAA’s blunt instrument—and why it works

A ground stop is one of the FAA’s simplest levers and, from a traveler’s perspective, one of the most frustrating. AP describes the concept in practical terms: it prevents planes from landing at an airport by holding aircraft at their origin or pausing departures so aircraft aren’t launched toward constrained airspace.

The logic is straightforward. When the system can’t safely accept inbound aircraft—because of weather, runway limitations, staffing issues, or, in this case, a facility problem—the safest aircraft is the one that never takes off into uncertainty.

For travelers, the experience is equally straightforward and frequently miserable:

- Departures held at the gate, often with shifting estimates
- Inbound aircraft delayed or rerouted, disrupting arrivals
- Missed connections, crew-timeouts, and rolling cancellations
- Late-night rebookings that spill into the next day

Even after a ground stop lifts, the consequences persist because airplanes and crews are no longer where the schedule expected them to be. The FAA can reopen the valve, but airlines still have to untangle the knot.

Why the FAA chooses “stop” instead of “slow”

Controllers manage complexity. When facility conditions compromise staffing or performance, the FAA’s safety posture is to reduce complexity quickly, then restart in a controlled manner. Slowing traffic while uncertainty persists can be riskier than stopping it briefly—especially in dense airspace where spacing and coordination are already tight.

The March incidents are a reminder that modern aviation’s reliability is built on operational discipline. That discipline shows up as delays when something goes wrong.

Editor's Note

As reflected in AP reporting, the FAA confirmed the odor and operational response on March 27, but did not provide a definitive root cause in the cited coverage.

What we know about the cause—and what remains unknown on March 27

Public attribution matters because it shapes both trust and policy responses. On March 13, Transportation Secretary Sean Duffy said the smell was traced to a circuit/overheated circuit board that was replaced, and firefighters confirmed no danger before operations resumed. That’s a concrete explanation rooted in equipment, not fear.

On March 27, AP reporting did not provide a definitive root cause beyond the “strong chemical smell” inside Potomac TRACON. That gap is not unusual in fast-moving incidents, but it leaves important questions unresolved: Was it another electrical component? A maintenance issue? Something unrelated? Without authoritative details, the only honest answer is that the public does not yet know.

The FAA’s near-term priority is continuity of safe operations; the public’s priority is confidence. Those priorities are aligned, but they require follow-through: identification of cause, corrective action, and transparency proportional to the disruption.

Multiple perspectives: safety-first vs. reliability expectations

From a safety perspective, a temporary stop is a success story. The system detected an anomaly, decision-makers acted conservatively, and operations resumed when conditions allowed.

From a passenger and airline perspective, repeated facility disruptions feel like fragility. Travelers tend to accept weather delays as acts of nature; they accept equipment and facility issues less readily, because those read as preventable. Both perspectives can be true at the same time: the FAA can make the right call operationally while still needing to answer hard questions about infrastructure resilience.

The ripple effect: why Washington delays show up in New York and beyond

Aviation is a network business. Even a local disruption becomes national when aircraft rotations and crew schedules slip. AP’s example is telling: NYC Emergency Management warned travelers that flights to Washington could be significantly delayed Friday night. That warning wasn’t about New York’s airspace; it was about the downstream effects of Washington-area constraints.

Consider a common real-world chain reaction, visible to any frequent flyer:

1. An inbound aircraft is late into DCA due to a ground stop.
2. That aircraft departs late to another city (or can’t depart at all).
3. The crew times out or misses a legal rest window.
4. The next flight cancels or departs hours late—somewhere else.

AP also noted that even after the March 27 ground stop lifted, residual delays were expected—BWI explicitly warned travelers. Residual is the polite word for chaos that has rules: airlines must reposition assets, protect connections, and comply with crew-duty limits.

Case study: March 13’s numbers show how quickly disruption scales

The March 13 incident offers concrete metrics. AP reported:

- The disruption lasted about one hour
- Delays climbed to roughly two hours at some airports
- About 25% to one-third of departing flights at the affected airports were delayed

Those three statistics explain the lived experience: a short operational pause can create a much longer passenger delay window, and when a quarter to a third of departures are impacted, the airport’s entire rhythm changes—lines, rebooking desks, and gate availability.

What travelers can do when TRACON problems hit: practical takeaways

Nobody can “outsmart” a ground stop, but informed travelers can reduce harm. Potomac TRACON’s incidents are a sharp reminder to plan for systemic hiccups—especially in regions where multiple airports share critical air traffic infrastructure.

Before you fly: build in options

- Avoid tight connections when transiting through busy corridors. A ground stop doesn’t have to last long to break a 40-minute connection.
- Choose earlier flights when possible. Delays compound through the day; being first in the queue often helps.
- Know your alternate airports. In this region, that can mean understanding differences among DCA, IAD, and BWI—and the ground transportation tradeoffs if you get rerouted.

During the disruption: act faster than the queue

- Rebook in-app while you wait. Gate lines move slowly; apps sometimes move seats quickly.
- Track the status of the inbound aircraft for your flight. If it hasn’t left its prior station, your departure time is often aspirational.
- Save receipts for expenses when policies allow—especially if delays become overnight.

For business travelers: treat ATC nodes as operational risk

Companies that routinely send staff through Washington-area airports should treat TRACON disruptions as a real, if infrequent, risk factor—similar to severe weather seasonality. Flex tickets, remote-ready plans, and meeting buffers are not luxuries; they’re continuity tools.

None of these steps prevents the FAA from stopping traffic. They simply keep a bad evening from becoming a lost day.

Quick traveler checklist during an ATC ground stop

  • Rebook in the airline app before you reach a gate line
  • Check the inbound aircraft’s status, not just your departure time
  • Identify alternate airports (DCA/IAD/BWI) and ground transport options
  • Save receipts if delays turn into an overnight disruption

What this episode suggests about infrastructure—and what to watch next

The most sobering element of March 27 is not that the FAA stopped traffic. It’s that a single facility condition could affect five airports across such a wide geography. Potomac TRACON’s scope—Washington, Baltimore, Richmond, Charlottesville—means its reliability is a public-interest issue, not a niche technical matter.

The March 13 incident had a clear public explanation from Secretary Sean Duffy: an overheated circuit board. If March 27 turns out to be similar, the question becomes whether redundancy, maintenance practices, or monitoring systems can reduce recurrence. If March 27 has a different cause, the question becomes broader: environmental controls, building systems, and incident response procedures.

Either way, the pattern forces attention on resilience. Travelers experience “the airport.” The system runs on facilities most passengers never see.

Aviation’s legitimacy rests on two promises: safety and reliability. The FAA is designed to protect the first, even when it bruises the second. The next step—after flights resume and delays fade—is accountability about what happened inside Potomac TRACON, and what will keep it from happening again.

“A TRACON disruption isn’t an airport problem. It’s a regional choke point—one building, five airports, and a night of knock-on delays.”

— TheMurrow
T
About the Author
TheMurrow Editorial is a writer for TheMurrow covering breaking news.

Frequently Asked Questions

What is Potomac TRACON?

Potomac TRACON is a Terminal Radar Approach Control facility that manages and sequences aircraft arriving to and departing from multiple airports in the region. AP reporting describes it as the facility that “controls traffic into the airports” across the Washington, D.C., Baltimore, Richmond, and Charlottesville areas—one reason a problem there can affect several airports at once.

Which airports were affected on March 27, 2026?

The FAA’s temporary stop in traffic affected five airports: DCA (Reagan National), IAD (Dulles), BWI (Baltimore/Washington), CHO (Charlottesville–Albemarle), and RIC (Richmond International), according to AP reporting. Even after the ground stop lifted, some airports—BWI notably—warned that delays could linger.

What caused the “strong chemical smell” on March 27?

As reflected in AP reporting, the FAA confirmed the odor and the operational response, but did not publicly specify a definitive cause for the March 27 smell. That leaves open whether it was an electrical issue, a building system problem, or something else. Any answer beyond that would be speculation until authorities release details.

Didn’t this happen earlier in March 2026 too?

Yes. On March 13, 2026, AP reported a similar “strong chemical smell” event that led to a major ground stop affecting four airports: DCA, IAD, BWI, and RIC. Transportation Secretary Sean Duffy said that earlier odor was traced to an overheated circuit board that was replaced, after which operations resumed.

What is a “ground stop,” and why does the FAA use it?

A ground stop is when aircraft are held at their origin or departures are paused so planes aren’t launched toward airports or airspace that can’t safely handle arrivals. AP characterizes it as preventing planes from landing at an airport. The FAA uses ground stops because they reduce complexity quickly—especially important if controller staffing or facility conditions are compromised.

Why do delays last after the ground stop ends?

Delays persist because flights operate in sequences: aircraft and crews are scheduled tightly, and disruptions knock them out of position. AP noted that even after the March 27 stop lifted, residual delays were expected, with BWI warning travelers. Once flights are late, connections break, crews time out, and the recovery can take hours.

More in Breaking News

You Might Also Like