An Air Canada Express regional jet collided with an airport fire truck while landing on LaGuardia’s Runway 4, turning two vehicles built around aviation safety into one fatal accident. Both pilots died, dozens of people went to hospitals and the aircraft was substantially damaged. The National Transportation Safety Board has not issued a probable cause.
The collision happened during a late-night landing
Jazz Aviation operated the flight from Montréal to New York using a CRJ-900. At about 11:37 p.m. Eastern time on March 22, the aircraft was landing when it struck Rescue 35, an Oshkosh Striker 1500 aircraft-rescue and firefighting vehicle on the runway.
NTSB investigation DCA26MA161 identifies the service as Jazz Aviation flight 646, doing business as Air Canada flight 8646. The board’s public description is preliminary and subject to change as records, vehicle data, radio transmissions and witness accounts are reconciled.
The two pilots were fatally injured
The captain and first officer died. The aircraft carried two flight attendants and 72 passengers, while two crew members occupied the fire vehicle. NTSB says 39 people were transported to local hospitals and six serious injuries were reported.
Those figures describe the early official record and should not be inflated or redistributed without an update. A hospital transport does not automatically equal a serious injury, while a serious classification has a specific investigative meaning. The deaths and reported injuries establish the scale without revealing why the vehicles occupied intersecting paths.
A runway vehicle follows controlled operating rules
Aircraft-rescue and firefighting vehicles need rapid access to runways, but movement areas are controlled because an arriving jet cannot stop or maneuver like a road vehicle. Investigators will need to establish the clearance, route, communications and situational information available to the truck crew and the flight crew.
FAA material on aircraft rescue and firefighting describes the specialized airport role of ARFF services. That general framework does not determine fault in this accident. It explains why emergency access and runway separation have to coexist within one operating system.
Physical evidence can reconstruct the final seconds
Damage patterns on the CRJ and Rescue 35 can show relative angle and contact sequence. Airport surveillance, surface radar, cockpit recorders, vehicle data and air-traffic audio may establish when each crew could detect the conflict. Weather, lighting and construction or closure information may also enter the timeline.
Reconstruction is not the same as selecting one error. A major accident often reflects several defenses that failed to prevent the final collision. NTSB analysis can examine training, procedures, equipment design and human performance after the factual record has been assembled.
The evidentiary docket will matter more than early speculation
The NTSB docket search is the official location for released reports, photographs, interview summaries and technical exhibits. Docket material can appear well before a final report, but individual documents remain evidence rather than the board’s final probable-cause analysis.
Videos and radio clips circulating online may capture only part of the sequence. Their timestamps, completeness and source need confirmation. A dramatic fragment cannot establish which clearance was issued, what each crew understood or whether equipment presented the same information later visible to investigators.
The open investigation limits the conclusion
The verified record supports a direct account: a landing passenger jet and an airport fire vehicle collided on Runway 4, the pilots died, people in both vehicles were injured and the CRJ sustained substantial damage. It does not support assigning responsibility to the flight crew, truck crew, controller or airport system.
That restraint is not a lack of accountability. It is the process required to make safety recommendations that address causes rather than appearances. Final work may change procedures, technology or training across airports if the evidence reveals a broader vulnerability. Until the board publishes that analysis, the collision remains an active investigation with a known human cost and an unresolved causal chain.
The airport’s emergency mission also makes the case unusually important. A rescue vehicle must be able to reach hazards quickly without becoming one, and flight crews need confidence that a cleared landing surface is protected. Understanding how those expectations diverged can produce lessons beyond LaGuardia, but only if the board separates the final seconds from the organizational decisions that shaped them.
Runway-safety defenses may include lighting, markings, surface surveillance, controller alerts, vehicle radios and read-back procedures. Each can appear robust in isolation while still leaving a gap at the moment traffic conflicts. Investigators will compare what systems were installed with what they displayed and how people used them that night. That layered examination matters because a single added warning may not help if it arrives too late, is ambiguous or competes with another urgent task.
Any recommendation must fit the speed and workload of real airport operations, not only a reconstructed timeline viewed afterward.
This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.
More from Morning Overview
