The incident, involving an Air Canada jet and a fire truck at around 11:37 p.m. local time, killed both pilots and has intensified concerns over staffing shortages and operational pressures within U.S. air traffic control.

According to a LaGuardia Tower standard operating procedures document, local air control and ground control roles should not be combined before midnight or within 90 minutes of a shift starting.

The rule was introduced following a 1997 ground collision at the airport and remained in force as of 2026.

Preliminary information suggests that, on the night of the crash, one controller may have been handling both runway operations and ground traffic, a practice inconsistent with those procedures.

The National Transportation Safety Board said it is examining the duties performed by controllers at the time, though it has not confirmed whether roles were combined.

NTSB Chair Jennifer Homendy said two controllers were working in the tower: one overseeing active runways and another acting as controller-in-charge while issuing departure clearances.

However, it remains unclear who was responsible for ground traffic management.Audio recordings reviewed by multiple current and former controllers suggest the runway controller may also have been handling ground movements, though this has not been officially confirmed.

Data showed 70 commercial flights operated at LaGuardia between 10 p.m. and the time of the crash, significantly above the average of 53 for that period in recent years, increasing workload complexity.

Controllers cited by Reuters said such traffic levels would typically require additional staffing rather than consolidation of roles. The Federal Aviation Administration, which oversees air traffic control, did not respond to requests for comment.

Investigators have emphasized that aviation accidents generally result from multiple contributing factors rather than a single cause, with the inquiry into the collision ongoing.

The Federal Aviation Administration (FAA) ordered a temporary ground stop at Ronald Reagan Washington National Airport, Washington Dulles International Airport, Baltimore-Washington International Airport, Charlottesville–Albemarle Airport and Richmond International Airport after reports of the odor at the Potomac Terminal Radar Approach Control (TRACON) facility, which manages aircraft movements in the region.

FAA spokeswoman Kristen Alsop said air traffic controllers had begun returning to their positions and that flight operations were expected to normalize shortly after the halt.

Baltimore-Washington International Airport said on social media that the ground stop had been lifted but warned of lingering delays into the evening.The disruption prompted New York City Emergency Management to advise travelers of significant delays for flights bound for the Washington area.

“Travelers to the DC area should expect possible ground holds, departure delays, and cancellations, and check directly with your airline before heading to the airport,” the agency said.The incident marks the second such disruption this month linked to a chemical smell at the Potomac TRACON facility.

A previous ground stop, lasting about an hour, was traced to a circuit issue, according to U.S. Transportation Secretary Sean Duffy.

In that case, operations resumed after emergency responders confirmed there was no risk to personnel or air traffic control systems.