FAA reportedly weighs discipline for LaGuardia controllers after March runway collision

Federal Aviation Administration investigators are reportedly examining whether two LaGuardia Airport air traffic controllers left their duty positions early before a deadly March runway collision, according to a report published Thursday by The Washington Times.

The report states that the incident occurred in March at LaGuardia and that investigators are looking at whether the controllers involved departed work ahead of schedule. The allegation, if substantiated, would involve a core safety and staffing responsibility for controllers tasked with managing runway and aircraft movements.

According to the same report, the FAA may pursue termination of employment as part of the agency response. The FAA’s consideration of firing would reflect the agency’s enforcement of controller fitness-for-duty rules and its internal standards for accountability when violations are linked to operational failures.

Air traffic controllers are federal employees governed by FAA policies and disciplinary processes, and any employment action generally depends on the outcome of internal review, findings on applicable duty requirements, and the evidence used to determine whether misconduct occurred. A controller would typically have avenues to challenge adverse personnel decisions, depending on their employment status and the specific disciplinary mechanism invoked.

The March collision also raised broader questions about runway safety and controller staffing practices, an area where enforcement often focuses on whether procedures were followed and whether any departure from required coverage contributed to an unsafe operating environment. If the FAA proceeds with discipline, the practical effect could include staffing and supervisory changes at LaGuardia and additional scrutiny of controller schedule compliance.

In its report, The Washington Times framed the alleged early departure as a potentially significant factor in the timeline leading up to the collision. The FAA has not been detailed in the reporting with specific findings, dates of any internal hearing, or the identity of the controllers, and the allegations have not been independently confirmed by a primary FAA or court record in the available information.