FAA fires two LaGuardia controllers after fatal runway crash involving regional jet

ATC Intelligence
 ⋅ 

Quick summary

The FAA is moving to terminate two air traffic controllers at LaGuardia Airport for leaving their shifts approximately one hour early on the night of March 22, 2026, when an Air Canada Express CRJ-900 collided with a Port Authority fire truck on runway 4, killing both pilots. The agency is treating the early departures — part of an informal practice known as an early shove — as timecard fraud, and has launched a broader review of similar violations at other facilities.

The NTSB investigation remains active and has not established whether the early departures contributed to the crash. Communication failures, high workload, and a runway safety system that failed to alert are already documented in the preliminary record.

Two LaGuardia controllers are facing termination after the FAA determined they left their posts roughly an hour before their scheduled shift end on the night a regional jet and a fire truck collided on a runway, killing both pilots aboard the aircraft. The agency announced the disciplinary action on August 27, 2026 — five months after the crash — framing the early departures not as a scheduling quirk but as fraud.

The collision happened at 11:37 p.m. Eastern on March 22, when Jazz Aviation LP flight 646, operating as Air Canada flight 8646 from Montreal, touched down on runway 4 and struck Rescue 35, an Oshkosh Striker 1500 airport firefighting vehicle crossing the runway. Both pilots died. The 76 passengers and crew on board survived.

The FAA’s move puts a long-tolerated staffing custom under federal scrutiny at a moment when U.S. aviation safety is already under intense public and political pressure. Transportation Secretary Sean Duffy said the government will not tolerate fraud and is taking action to hold individuals accountable. The FAA added that it will not compromise the safety or efficiency of the National Airspace System.

What remains unresolved — and what matters most for the broader policy question — is whether the early departures had any operational effect on the night of the accident. The NTSB has not said they did.

What the preliminary record shows — and what it doesn’t

The NTSB’s preliminary investigation report on flight DCA26MA161 documents that two controllers were on duty in the LaGuardia tower at the time of the collision — consistent with the facility’s planned midnight-shift staffing configuration, and both were current on all tower positions. The report does not identify understaffing as a cause.

What it does flag is a cluster of conditions that compressed the margin for error in the final minutes before impact. Simultaneous coordination with multiple aircraft and ground vehicles stretched tower workload. Communication lapses occurred. And LaGuardia’s surface radar system, ASDE-X, did not generate a runway incursion alert — because the Port Authority fire truck was not equipped with a transponder compatible with that system.

That last detail is significant. A functioning alert might have given controllers seconds to intervene. Without it, the collision unfolded without any automated warning.

The NTSB has confirmed the case remains under active investigation. A final determination on whether the early controller departures played any role — direct or indirect — has not been made.

Key factors in the LaGuardia runway collision, March 22, 2026 — status as of August 2026
Factor Status at time of collision Investigation finding
Tower staffing level Two controllers on duty — matched midnight-shift plan Consistent with planned configuration; no understaffing cited
ASDE-X runway safety alert Did not activate before collision Fire truck lacked compatible transponder; no automated warning issued
Tower workload Simultaneous coordination with multiple aircraft and vehicles Communication and workload issues documented in final minutes
Early controller departures Two controllers left ~1 hour before shift end Under FAA disciplinary review; NTSB has not linked to cause
Weather conditions Poor weather caused disruptions in hours before accident Background factor; role in workload under review

Flight deals
most people never see

Our AI monitors 150+ airlines for pricing anomalies that traditional search engines miss. Air Traveler Club members save $650 per trip per person on average: see how it works.


Each deal saves 40–80% vs. regular fares:

Superdeals to Asia preview

Why the early-shove practice is now a federal accountability issue

The early shove — supervisors permitting controllers to leave during quiet periods while logging a full shift — has existed informally at U.S. facilities for years. It was treated as a low-stakes scheduling accommodation, not a safety matter. The FAA’s decision to classify it as timecard fraud redraws that line entirely.

The timing matters. This disciplinary action arrives against a backdrop of multiple fatal U.S. aviation incidents in 2026, and an administration that has made controller accountability a visible policy priority. The FAA has stated it is expanding controller hiring to address staffing levels — an acknowledgment that the system has been running lean.

For the NTSB, the staffing question is more nuanced. The preliminary record shows the tower was staffed to its planned level when the collision occurred. But “planned level” and “adequate level” are not the same thing, and whether two controllers were sufficient for the workload that night is precisely what investigators are still examining. NBC News reported on the communication and workload findings from the preliminary report in detail.

The National Air Traffic Controllers Association (NATCA) said it is actively discussing the allegations with FAA leadership and considers those discussions the appropriate forum — a measured response that signals the union is not publicly contesting the terminations, at least not yet.

What LaGuardia travelers should do now

The FAA’s crackdown on early departures is already changing how late-night shifts are managed at LaGuardia — and if the NTSB’s final report elevates staffing as a contributing factor, operational changes at major U.S. hubs could follow quickly.

  • Check your flight status on the day of travel. Tighter overnight staffing rules may produce minor schedule adjustments on late-night arrivals and departures at LaGuardia. Use your airline’s app or a tracker like FlightAware for real-time status.
  • Build buffer time on the New York–Montreal corridor. Jazz Aviation LP operates this route under the Air Canada Express banner, and the investigation is ongoing. Extra connection time at LaGuardia is prudent until the NTSB issues its final report and any operational changes are settled.
  • Consider Newark or JFK as alternatives for late-night travel. Both airports serve the broader New York region and offer comparable connections. If your itinerary is flexible, routing through either hub sidesteps any LaGuardia-specific disruption during this period.
  • Monitor the NTSB investigation page directly. The NTSB’s case file for DCA26MA161 is publicly accessible and will be updated as findings are released — more reliable than waiting for media summaries.

Watch: The NTSB’s final report on DCA26MA161 — no release date confirmed — will determine whether controller staffing or the early-shove practice is cited as a contributing factor. If it is, expect the FAA to accelerate its national review of early-departure practices and potentially mandate minimum staffing floors at high-traffic overnight facilities.

Reporting by

ATC Intelligence

ATC Intelligence is the research division of Air Traveler Club. Backed by 15 years in Asia-Pacific aviation, we don't just report on the regional market; we live and work in it. By pairing AI-driven data with strict human fact-checking, we provide actionable, trustworthy journalism designed to make your trips to Asia smarter and more affordable.

Follow our daily coverage on Google News, Google Discover, and social media.

Questions? Answers.

Did the controllers’ early departure directly cause the LaGuardia crash?

The NTSB has not established a causal link. The preliminary report documents that two controllers were on duty at the time of the collision — matching the planned midnight-shift configuration — and focuses on communication lapses, workload, and the failure of the runway safety alert system to activate. Whether the earlier departures of two other controllers affected the overall staffing picture remains an open question in the active investigation.

What is an “early shove” in air traffic control?

An early shove is an informal practice in which a supervisor permits a controller to leave before their scheduled shift ends — typically during a slow period — while the controller is still paid for the full shift. The FAA now classifies this as timecard fraud and has launched a broader review of the practice at facilities beyond LaGuardia.

Why didn’t LaGuardia’s runway safety system warn controllers before the collision?

LaGuardia’s surface radar system, ASDE-X, is designed to detect potential runway incursions and alert controllers. It did not activate before the collision because the Port Authority fire truck involved was not equipped with a transponder compatible with the system. The NTSB has flagged this equipment gap as a key area of concern in its ongoing investigation.

What happens next for the two controllers facing termination?

The FAA has initiated termination proceedings, but federal employees have appeal rights through the Merit Systems Protection Board and, in unionized workplaces, through grievance procedures under their collective bargaining agreement. The National Air Traffic Controllers Association said it is discussing the allegations with FAA leadership. The timeline for final resolution has not been publicly confirmed.