Connect with us

Washington

Flights halted across Washington-area airports after chemical smell at control center

Published

 

on

People waiting at airport.

FAA halts DC flights after odor

Federal Aviation Administration (FAA) temporarily halted flights across major Washington, D.C.-area airports on March 27, 2026, after a strong chemical smell was detected inside a regional air traffic control facility. The disruption immediately affected flight operations at multiple airports and prompted emergency response measures.

The odor was reported at the Potomac Terminal Radar Approach Control facility in Virginia, which manages aircraft movements across several busy airports in the region. Air traffic controllers paused operations to ensure safety and allow inspection of the building.

Ground stops remained in place for more than an hour before flights began resuming later in the evening. Even after operations restarted, delays persisted across the network.

People waiting at airport

Five airports impacted at once

The FAA temporarily stopped traffic at five airports on March 27, 2026, after a strong smell was reported at the Potomac TRACON facility in Warrenton, Virginia. The affected airports were Reagan National (DCA), Washington Dulles (IAD), Baltimore/Washington International (BWI), Charlottesville–Albemarle (CHO), and Richmond International (RIC).

All five airports rely on Potomac TRACON for approach and departure control in shared regional airspace. When the facility was evacuated and assessed, flight operations across the region were also interrupted.

Once the ground stop was lifted, flights resumed gradually, but delays continued as airlines and controllers worked through the backlog.

Passenger waiting at the airport terminal stressed about missing her flight.

Ground stops lasted over 90 minutes

Flights were halted for about 90 minutes after ground stops were issued around 6:40 p.m. EDT on March 27, 2026. Air traffic did not resume until later in the evening, once conditions were cleared.

Major airports, including Dulles, Reagan National, and BWI, remained under restrictions until around 8 p.m. ET. During this period, no takeoffs or landings were permitted.

Once restrictions were lifted, operations resumed gradually rather than instantly. Aircraft sequencing and safety checks slowed the return to normal schedules.

View of a woman using a mobile phone inside the airport

Delays hit up to 30% of flights

Flight disruptions quickly escalated across the region, affecting a large share of scheduled arrivals. About 30% of incoming flights at BWI and Reagan National were delayed during the disruption.

At Washington Dulles International Airport, around 13% of arriving flights experienced delays. These delays reflected how quickly operational issues at a control center can affect multiple airports.

Even after flights resumed, the backlog continued to impact schedules. Aircraft spacing, crew timing, and gate availability contributed to extended delays.

flight controller working

TRACON controls regional airspace

The Potomac Terminal Radar Approach Control facility manages aircraft movement across Washington, D.C., Baltimore, and the surrounding Virginia regions. It plays a critical role in directing planes during the approach and departure phases.

Controllers at this facility coordinate traffic between multiple airports within shared airspace. This centralized system allows efficient handling of high flight volumes in a busy corridor.

Any disruption at this location immediately affects multiple airports. The March 27 incident showed how dependent the region is on a single control hub.

italy venice international airport 14 september 2011 air traffic controllers

Second disruption in two weeks

The March 27, 2026, incident marked the second time within two weeks that a chemical odor disrupted operations in the same region. A nearly identical event occurred earlier on March 13.

Both incidents forced temporary ground stops at the same group of airports. This repeated disruption highlighted a vulnerability tied to the Potomac TRACON facility.

The recurrence raised concerns about equipment reliability and operational continuity at one of the region’s most important air traffic centers.

Electronic circuit board close up

Earlier cause traced to circuit board

The March 13 incident was traced to an overheated circuit board inside the Potomac TRACON facility, identifying a specific equipment failure that disrupted operations. Sean Duffy confirmed the cause after internal checks were completed.

The faulty component was removed and replaced, allowing controllers to safely return to their workstations the same evening. Air traffic operations resumed once the equipment was verified to be functioning normally.

This finding showed how a single hardware failure can halt air traffic across multiple airports. The March 27 incident raised new concerns because it showed a similar pattern without a confirmed cause during the initial response.

Female firefighter with fire extinguisher on back closing truck at fire station.

Emergency crews responded and the site was cleared

Emergency crews responded after a strong smell was reported at the Potomac TRACON facility on March 27, 2026. Officials temporarily stopped traffic at several Washington-area airports while the facility was evaluated and cleared.

Local fire-rescue officials later said the source was overheating electrical equipment inside an IT cabinet, and the facility was deemed safe for personnel to reenter. Controllers returned after the building was cleared, and operations resumed.

The response underscored how safety checks at a single control facility can quickly affect multiple airports in the region.

Airport security checkpoint african american security officers using laptop computer

Safety checks cleared staff to return

After the odor was reported on March 27, officials cleared parts of the Potomac TRACON facility while it was inspected. Flights were paused across several Washington-area airports until the facility was deemed safe and controllers could return.

Local fire-rescue officials later reported the source was overheating equipment inside an IT cabinet, and personnel were able to reenter and resume work duties that evening.

The response emphasized precaution and workplace safety, with operations resuming only after conditions were confirmed safe.

Busy airport departure board filled with canceled flights.

Flights resumed but delays continued

Flight operations resumed later in the evening after controllers returned to the facility and systems were confirmed safe. Departures and arrivals gradually restarted across affected airports.

The restart process was controlled and phased to maintain safety, which slowed the return to full capacity. Aircraft sequencing and spacing required careful coordination.

Delays continued for hours after flights resumed. Passengers faced missed connections, late departures, and schedule changes as airlines worked through the backlog.

Smiling airport worker checking documents of young female traveler.

Travelers warned to expect disruptions

Travel alerts warned passengers to expect continued disruptions for flights heading into Washington, D.C. Ground holds, delays, and cancellations were all possible during the recovery period.

Passengers were encouraged to check flight updates before leaving for the airport. Airlines adjusted schedules in real time to manage shifting conditions.

The impact extended beyond local routes, affecting connecting flights and travelers passing through other cities. This showed how regional disruptions can spread across a national network.

Airport flight information board delayed.

Delays created ripple effects

The ground stop and phased restart created ripple effects that lasted beyond the initial interruption. When air traffic is paused at multiple airports simultaneously, airlines often have to reset aircraft rotations, crew schedules, and gate assignments.

Because flights are tightly connected throughout the day, delays at a major hub region can push late departures and missed connections into the evening.

Even after the FAA lifted the stop and traffic began moving again, residual delays were expected as the system returned to normal.

Want to avoid costly Airbnb surprises? Discover the most common booking mistakes travelers make and how to book smarter every time

concentrated detective in glasses reading dossier in dark office

FAA and local officials identified an overheating source

After the March 27 odor report, the FAA stopped traffic at five Washington-area airports while the Potomac TRACON facility was inspected and cleared. Controllers returned only after the building was deemed safe and operations could resume.

Local fire-rescue officials later reported the smell came from overheating equipment—an overheated UPS battery backup inside an IT cabinet—at the facility. Once the issue was addressed and the environment was cleared, personnel were able to reenter and return to duty.

Because the incident followed a similar disruption earlier in March, the back-to-back events renewed attention on equipment reliability at a key regional air traffic hub.

Curious how national parks are changing visitor rules? Explore the full story to see why booking requirements are being dropped this season.

Stay informed with the latest aviation and travel updates. Explore more stories below to see how major policy shifts and infrastructure changes are shaping the U.S.

This slideshow was made with AI assistance and human editing.

Read More From This Brand:

Simon is a globe trotter who loves to write about travel. Trying new foods and immersing himself in different cultures is his passion. After visiting 24 countries and 18 states, he knows he has a lot more places to see! Learn more about Simon on Muck Rack.

Trending Posts