Aviation Law Group is investigating the March 23, 2026, collision involving Air Canada Express Flight 8646, a Bombardier CRJ900 operated by Jazz Aviation, and an airport rescue and firefighting vehicle at LaGuardia Airport in New York. The collision occurred at approximately 11:37 p.m. while the aircraft was landing on Runway 4. The aircraft was carrying 72 passengers and four crew members. Two firefighters were in the vehicle. Our deepest condolences go out to the families of the two pilots who were killed in the accident, the seriously injured firefighters, and the many seriously injured crew and passengers on flight 8646.
At this early stage, no responsible analysis should pretend the full answer is known. The NTSB itself has emphasized that major aviation accidents rarely result from a single failure, and the facts released so far are consistent with that view. There are already signs of multiple safety layers that may have contributed to the accident, including runway-crossing clearance timing, the significance of anticipatory landing clearance issued two minutes before the accident, the combined controller duties on the midnight shift, vehicle transponder issues, and the failure of ground surface radar to generate a collision alert.
Preliminary Timeline of the Accident
Facts disclosed at the NTSB’s second public press conference on March 24, 2026, sharpen the focus of the investigation considerably.
According to the NTSB’s preliminary cockpit voice recorder summary, the LaGuardia tower cleared flight 8646 to land on Runway 4 as number two for landing 2 minutes and 17 seconds before the end of the recording. There was no further communication between the pilot and the tower. At 8 seconds, there was a sound consistent with the aircraft touching down on Runway 4.
Concurrently, ATC was handling clearance for Truck 1. 25 seconds before the accident, Truck 1 requested to cross Runway 4 at Taxiway Delta, and five seconds later ATC cleared it to cross the Runway. ATC twice instructed the firetruck to stop crossing the runway at 9 and 4 seconds before the collision.
Truck 1 was the lead of a procession of firetrucks that were responding to an on-airport emergency involving another aircraft. United Flight 2384 declared an emergency after two aborted takeoffs and reports of fumes and smoke in the cabin that sickened flight attendants.
At the time of the accident, there were two people in the tower cab – the local controller and the controller in charge. The local controller was manning two positions: tower controller on one frequency and ground controller on the other.
It is apparently standard practice for the midnight shift at LaGuardia and is a common practice at other airports. NTSB Chair Homendy noted in her remarks that she was concerned that, with over 900 flights per day, LaGuardia is a saturated environment for such staffing.
Large airports are equipped with multiple systems designed to reduce the likelihood of runway incursions. In this instance, it appears that two notable systems failed.
First, the surveillance recording showed the runway status lights functioning, but the system did not provide the warning one would expect in a developing runway conflict, which is normally a set of in-ground red warning lights.
Second, the advanced ground-surface radar known as Airport Surface Detection Equipment, Model X (ASDE-X), failed to issue a warning. LaGuardia is one of only a few high-traffic airports equipped with this system, which is designed to warn controllers of potential conflicts between surface vehicles and aircraft.
The NTSB stated that ASDE-X did not generate an alert because the close proximity of vehicles merging and unmerging near the runway prevented the system from creating a high-confidence track. This failure to determine the precise location of the firefighting trucks was exacerbated by the fact that none of the involved trucks had transponders that reported their location – equipment commonly found on modern airport first-response vehicles.
Anticipatory Landing Clearance
ATC issued the landing clearance over two minutes before the accident and provided no additional guidance to Flight 8646. It is possible that this large time gap, combined with competing requests from both ground and other aircraft, contributed to the local controller’s loss of situational awareness.
Under current FAA procedures, the U.S. system permits landing operations that depend in part on expected runway availability rather than a universally clear runway in every circumstance. That practice has long been part of how traffic is managed at high-density airports. The local controller can tell a plane “Cleared to land” even if there’s a plane landing or departing ahead of it.
By contrast, ICAO-based procedures, which are used throughout Europe, are generally framed more conservatively, with the runway-clear principle given greater emphasis before an aircraft crosses the threshold. Landing clearances are given only when the runway is clear.
In this case, when Tower issued its clearance, it stated, “646, number 2, cleared to land 4.” The pilots were given an anticipatory landing clearance because another aircraft was on final approach and first in line to land on Runway 4.
Had ICAO protocols been followed, Flight 8646 would not have received a landing clearance when it did because there was a preceding plane. To land, the pilots would have had to call the tower again and request landing clearance, which could have reminded ATC of their position on short final.
The fact that flight 8646 was cleared to land as number two does not by itself establish that the clearance was improper. But it does raise an important operational question. When a landing aircraft has already been sequenced and cleared in anticipation of runway availability, the margin for error narrows if additional variables are introduced.
Investigation Timeline and Legal Considerations
This accident occurred against the backdrop of several serious runway and surface conflicts in recent years. One of the most notable occurred less than a week before this accident at Newark Liberty International Airport, where an Alaska Airlines aircraft and a FedEx freighter nearly collided during intersecting runway operations. That event, like other recent close calls in Austin, Boston, and New York, underscores an ongoing concern within an air traffic system that is operating under increasing pressure.
The issue is not simply whether the system works most of the time. The question is whether the margins for error at busy airports have become too thin as traffic volume, controller workload, surface movements, and timing pressures continue to converge. LaGuardia, with its density, physical limitations, and operational complexity, is precisely the type of environment where those margins matter most.
The NTSB’s investigation will take time. Over the coming weeks and months, investigators will complete recorder analysis, conduct detailed interviews, reconcile conflicting operational data, and ultimately issue a preliminary report, followed by a final report and probable cause determination. That process is deliberate and methodical, and it is essential to understanding not just what happened, but why.
For passengers and families affected by this accident, important legal rights may already be in play under international law. Evidence preservation, early investigation, and coordination with the NTSB process can be critical in these cases, particularly where multiple entities may share responsibility.
Aviation Law Group is actively investigating this accident. We encourage anyone affected by Air Canada Express Flight 8646, or anyone with information relevant to this event, to contact our firm at (206) 464-1166 or info@aviationlawgroup.com
We will continue to provide updates as additional verified facts become available and as the NTSB investigation progresses.