LaGuardia runway crash follows months of pilot warnings
NASA ASRS reports describe close calls and unclear ATC guidance, safety margins erode while responsibility stays split
Images
Officials with the National Transportation Safety Board investigate the site on 23 March 2026, where an Air Canada jet came to rest after colliding with a Port Authority firetruck at LaGuardia airport, shortly after landing Sunday night in New York. Photograph: Seth Wenig/AP
theguardian.com
Click to play video: 'NTSB provides update on Air Canada collision, says investigation could take ‘days’'
globalnews.ca
Pilots filed repeated safety warnings about New York’s LaGuardia airport months before an Air Canada Express jet hit an airport firetruck on a runway, killing two pilots and sending more than 40 people to hospital.
According to The Guardian, the US Aviation Safety Reporting System (ASRS) — a NASA-administered database of anonymous incident reports — contains complaints describing “close calls”, ambiguous air-traffic guidance and a pace of operations that pilots said was being pushed by controllers. One pilot wrote “Please do something” after reporting multiple nearby aircraft and unclear separation, warning that on thunderstorm days LaGuardia was starting to resemble Washington’s Reagan National before its January 2025 mid-air disaster.
The crash itself now sits in the middle of a familiar pattern: risk is observed, reported, normalised, and then reclassified as “unforeseeable” when the margin finally runs out. The Guardian reports that the Air Canada flight from Montreal collided with a firetruck that had been cleared to cross the runway while responding to another aircraft that had reported difficulties. After clearing the truck, the controller attempted to stop it.
Global News identified the pilots killed as Antoine Forest and Mackenzie Gunther, noting the flight carried 72 passengers and four crew members. The two occupants of the firetruck were hospitalised but expected to be released.
ASRS exists because the system relies on voluntary disclosure of near-misses that rarely produce paperwork elsewhere. But the database is also a kind of institutional dead letter office: it can preserve warnings without assigning a bill to anyone. Airports, airlines, the FAA, local authorities and contractors each control a slice of the operation — runways, vehicles, staffing, procedures, schedules — while the cost of thin margins is distributed across passengers, crews and insurers.
LaGuardia’s operational reality intensifies that fragmentation. It is space-constrained, high-volume and weather-sensitive, with constant pressure to keep arrivals and departures moving. In that environment, “efficiency” often means turning judgment calls into routine. The Guardian’s reporting points to pilots describing unclear guidance on how close aircraft can get in intersecting runway scenarios, and to reports of runway lighting being turned off — small degradations that become invisible once they are common.
After a fatal collision, the system typically produces a clean narrative: a controller error, a vehicle incursion, a procedural lapse. The harder question is why repeated warnings could sit in a federal database without forcing a redesign of how risks are priced and owned.
On Sunday night, an aircraft cleared to land met a firetruck cleared to cross.
By Monday, the warnings were still searchable — and the runway was still the runway.