Image credit: Tdorante10 via Wikimedia Commons. License: CC BY-SA 4.0.
The Federal Aviation Administration is pursuing discipline against two LaGuardia air traffic controllers who allegedly left work about an hour early on the night of a fatal runway collision, according to a government official who spoke to the Associated Press. The potential action can include firing, but the accident’s cause remains under investigation.
The development adds a serious staffing question to the March 22 collision between Air Canada Express Flight 8646 and an airport fire truck. It does not mean investigators have found that the early departures caused the crash.
- New development: FAA is pursuing discipline, potentially including termination, against two controllers who allegedly left early.
- Source: The Associated Press cites a government official familiar with the matter who was not authorized to discuss it publicly.
- What remains open: NTSB has not issued a final probable cause for the March 22 collision.
- Traveler impact now: No new LaGuardia closure, flight restriction or passenger action was announced.
- What to watch: The FAA employment process, controller scheduling changes and the final NTSB report.
What the new LaGuardia controller report says
The Associated Press report says two controllers left the tower about an hour before their scheduled shifts ended. FAA is pursuing disciplinary action that could include firing them, according to the unnamed official.
The report says their presence could have provided backup during an unusually busy period. That is different from a finding that staying would have prevented the collision, and the final safety investigation must test the entire sequence.
The National Air Traffic Controllers Association told AP that it was discussing the allegations with FAA leadership. The agency said it is committed to accountability and will not compromise the safety or efficiency of the national airspace system.
Leaving when a break falls at the end of a shift has been described in the industry as an early shove. Whether the alleged departures violated timekeeping or staffing rules is part of the employment matter, not a substitute for the NTSB’s accident analysis.
| If you are | What to do now |
|---|---|
| Flying through LaGuardia | Keep the trip unless the airline reports a separate operational change. This disciplinary report does not close the airport. |
| Tracking the crash investigation | Treat the controller allegation as a new fact under review, not the final probable cause. |
| Connecting on Air Canada or Jazz | Use normal flight status checks. No carrierwide schedule change was announced with this report. |
| Concerned about runway safety | Watch the final NTSB findings and any FAA or Port Authority corrective actions tied to staffing, vehicles and warning systems. |
| Writing or sharing the story | Attribute the early departure and possible firing to the official cited by AP, and do not say the controllers caused the crash. |
Why staffing is only one part of the investigation
Two controllers were working in the tower when the collision occurred late on March 22. Weather delays had pushed more traffic into the late evening, while emergency vehicles were responding to a separate aircraft whose crew reported a strong odor.
The fire truck was cleared to cross Runway 4 as the Air Canada Express jet approached. A controller then transmitted urgent stop calls, but the truck was already moving into the runway environment.
The NTSB preliminary report describes the factual sequence available early in the investigation. Preliminary information can change and does not assign probable cause or legal responsibility.
Investigators have examined controller roles, radio communication, traffic volume, runway warning lights, vehicle equipment and the fire response. A major accident is rarely explained by one decision, which is why the employment allegation must remain one line of inquiry among several.
What happened to Flight 8646
Jazz Aviation operated the CRJ900 as Air Canada Express Flight 8646 from Montreal to LaGuardia. The aircraft collided with an aircraft rescue and firefighting vehicle while landing on Runway 4 at about 11:37 p.m.
The two pilots were killed, and dozens of people were taken to hospitals. It was LaGuardia’s first fatal aircraft accident in 34 years.
Deep Arrival’s first report, LaGuardia Crash Exposes How Thin the Margins Are for Air Travel, explains the immediate disruption and system pressure. The detailed collision account, A Fire Truck, a Landing Jet, and the Seconds That Failed at LaGuardia, follows the established event stream.
This August update is materially different because it concerns FAA employment action tied to two people who allegedly left before the collision. It should be read as an accountability development, not a retelling of the initial crash.
For current LaGuardia passengers
- No new airport closure or schedule restriction is attached to the report.
- Check the airline app and FAA airport status for ordinary weather or traffic delays.
- Do not alter a connection solely because an employment process is underway.
For longer term safety tracking
- Watch whether FAA changes overnight staffing or end of shift break practices.
- Look for completed ground vehicle tracking improvements at New York airports.
- Use the final NTSB report for probable cause, not an unnamed source report.
The FAA action and NTSB investigation answer different questions
FAA can decide whether employees violated work or timekeeping rules. NTSB independently determines what happened, why it happened and which safety recommendations could prevent a recurrence.
A controller can face discipline even if a final accident report does not identify the departure as a probable cause. The reverse is also possible: a safety finding can lead to system changes without proving that an individual committed misconduct.
The FAA’s initial incident statement confirmed that Flight 8646 struck a rescue and firefighting vehicle after landing and that FAA and NTSB would investigate. The current disciplinary report goes beyond that brief statement, but the agency has not published a final accident conclusion.
Why the wording matters
The safest headline is not that absent controllers caused a fatal crash. The supported update is that FAA is moving through a disciplinary process after investigators learned two controllers allegedly left before their scheduled end time.
AP’s source was familiar with the investigation but not authorized to speak publicly. That makes the report significant and attributable, while leaving room for the FAA process, union response and documentary record to develop.
The union’s involvement also means the employment outcome may be contested. A proposed firing, final termination, reinstatement and negotiated policy change are separate stages that should not be collapsed into one claim.
What is confirmed and what is not
It is confirmed that the March 22 collision killed both pilots and that the federal accident investigation remains open. FAA also publicly says it is committed to holding employees accountable.
The early departure allegation and potential firing are reported through a government official cited by AP. The public record does not yet establish a final personnel outcome or show that the two departures caused the collision.
No final NTSB probable cause has been issued. Any account that presents one factor as the definitive cause is moving ahead of the investigators.
- Whether FAA issues final discipline or changes the proposed action.
- The air traffic controllers union’s formal response.
- Any revised overnight staffing and break rules.
- NTSB factual updates, hearings and the final probable cause.
- Corrective action involving fire truck transponders and runway conflict alerts.
Were two LaGuardia controllers fired?
Not as a confirmed final outcome. AP reports that FAA is pursuing discipline that could include firing.
Did the controllers leaving cause the crash?
That has not been established. NTSB has not issued a final probable cause.
Is LaGuardia closing because of the report?
No new airport closure or operational restriction was announced with this development.
How many controllers were working when the collision occurred?
Two controllers were in the tower at the time, according to the current reporting.
When will the final answer come?
NTSB investigations can take many months. The agency’s final report, not the preliminary report, will state probable cause.
The bottom line
The report raises a legitimate accountability question about two controllers who allegedly left LaGuardia early before an exceptionally demanding period. FAA’s employment process can address that conduct.
It cannot by itself answer why Flight 8646 and the fire truck collided. Travelers and readers should keep the new staffing allegation in view while waiting for the NTSB to finish the full safety picture.
