Pilots and anonymous safety reporters have for years flagged recurring runway incursions, vehicle near-misses and confusing air traffic control (ATC) instructions at New York’s LaGuardia Airport, according to federal and NASA safety databases. The warnings, logged across decades, gained renewed attention after a deadly collision at LaGuardia earlier this week in which an Air Canada Express regional jet struck a fire truck. Federal records and NASA’s Aviation Safety Reporting System show patterns of incidents involving ground vehicles, maintenance equipment and coordination lapses that industry sources say increase risk during high-traffic periods.
Key Takeaways
- FAA runway-incursion records show at least 132 incidents at LaGuardia since 2000, including 17 involving maintenance, snow or support vehicles on active runways.
- NASA’s anonymous ASRS contains at least 122 reports tied to ground conflicts and incursions at LaGuardia since 2000, with 17 reports specifically naming ground support vehicles.
- There were six FAA-reported runway incursions in 2025 at LaGuardia, including one involving a pedestrian and one involving a ground vehicle; most others involved aircraft-on-aircraft events.
- Documented close calls include a 2001 Airbus A320 takeoff that cleared a snowplow by an estimated 50–75 feet on Runway 4 and a September 2015 event where an Embraer 190 aborted takeoff after an airport vehicle crossed a runway intersection.
- Multiple crew reports describe controllers managing both tower and ground frequencies simultaneously and issuing complex taxi instructions while aircraft are still landing or taking off.
- A July 2024 ASRS report describes a near collision when a taxiing jet was cleared to cross Runway 22 only moments after another aircraft had landed.
- The National Transportation Safety Board (NTSB) is investigating an Oct. 1, 2025, taxiway collision between two regional jets at LaGuardia; one person required hospitalization.
- Industry observers warn that rising operational tempo and weather pressures can magnify the safety margin erosion identified in these reports.
Background
LaGuardia Airport (LGA) serves a dense mix of short-haul commercial flights, general aviation, and frequent ground operations. Its location on a constrained peninsula, combined with tight runway and taxiway geometry, creates a complex operating environment where coordination between ground vehicles, ramp crews and tower controllers is essential. Historically, airports with similar spatial constraints have recorded higher rates of runway incursions and vehicle conflicts, prompting technology and procedural upgrades elsewhere.
Two federal reporting streams document safety events: the FAA’s official runway-incursion database and NASA’s Aviation Safety Reporting System (ASRS), which accepts confidential submissions from pilots, controllers and other personnel. The FAA database records formally validated incursions and close calls; ASRS entries are anonymous, often filed by front-line workers describing operational pressures and near-misses that may not appear in the formal record. Both sources, when reviewed together, reveal recurring themes at LGA over decades.
Main Event
On March 23, 2026, an Air Canada Express regional jet collided with a fire truck at LaGuardia, a crash that resulted in fatalities and prompted immediate groundings and official inquiries. That collision followed a pattern revealed in long-standing safety reports: vehicles or equipment on or near active runways and tightly timed aircraft movements during peak periods. The recent crash has refocused attention on dozens of earlier incidents that crews flagged as close calls or examples of unclear ATC guidance.
Several ASRS submissions describe controllers issuing complex taxi clearances while pilots are still committed to landing, increasing workload and reducing margins for error. In a July 2024 anonymous report, a first officer said the crew was “extremely close” to a landing aircraft when ground control issued a stop—the report adds that ground control “issued a stop command just in time.” Other reports note controllers handling both tower and ground duties at once, a setup crews say can degrade situational awareness.
Specific vehicle-related near-misses include a 2001 Airbus A320 crew who reported clearing a snowplow by an estimated 50–75 feet on Runway 4, and a September 2015 incident in which an Embraer 190 aborted a takeoff when an airport vehicle crossed the Runway 13/Runway 22 intersection; the closest separation was reported at about 1,300 feet. In 2016, a fuel-truck encounter required pilots to brake sharply, causing a flight attendant to fall and sustain a minor injury.
FAA records show six runway incursions at LGA in 2025 alone. While not every report resulted in a collision, the frequency and consistency of the complaints—from unnamed ASRS submissions to FAA entries—paint a picture of recurring operational friction that safety advocates say merits systemic fixes.
Analysis & Implications
The accumulation of reports across two federal systems suggests the issue is not limited to isolated human error but may reflect systemic strains: high traffic volumes, constrained physical layout, and mixed vehicle-aircraft movements. When operations intensify—during thunderstorms or peak scheduling windows—controllers and ramp crews face compressed decision cycles that can increase the likelihood of miscommunication or procedural deviation.
Technology mitigations such as runway status lights, improved surface movement radar, and stricter vehicle access controls have reduced risk at other airports, but ASRS reports indicate intermittent or nonfunctional indicators at LGA in certain incidents. For example, an anonymous captain questioned whether the runway status light system was visible and operational during a close call, implying that technological safeguards did not always provide the intended protection.
Operational fixes would likely require coordination among the Port Authority of New York and New Jersey (the airport operator), the FAA, airlines and ground service contractors. Options include reconfiguring vehicle routing, limiting vehicle access during critical periods, mandating dual-staffed tower positions to separate ground and tower duties, and expediting repairs or upgrades to surface surveillance and runway status systems. Each option carries cost, staffing and implementation trade-offs.
Regulatory and reputational consequences are possible. An NTSB finding pointing to procedural or oversight failures could trigger new FAA mandates or local operational restrictions. Airlines and labor groups may press for faster remediation, while insurers and corporate risk managers will reassess exposure at high-density airports if patterns of incursions continue.
Comparison & Data
| Source / Period | Recorded Events (LaGuardia) |
|---|---|
| FAA runway-incursion database (since 2000) | At least 132 incidents; 17 involved maintenance/support vehicles |
| NASA ASRS (since 2000) | At least 122 anonymous reports of ground conflicts; 17 cited ground support vehicles |
| FAA (2025) | 6 reported incursions at LGA, including 1 pedestrian and 1 ground-vehicle incident |
Combined review of both databases provides a fuller view: FAA entries capture formal incursions and investigations; NASA ASRS often surfaces near-misses and contextual detail from front-line personnel. The overlapping but not identical records indicate underreporting in any single system and underscore the value of parallel reporting streams for safety analysis.
Reactions & Quotes
“Please do something.”
Anonymous airline captain (ASRS submission)
The plea came in a summer ASRS submission describing a landing that occurred about 10 seconds after a departing aircraft crossed the same runway, an incident the captain said lacked timely ATC guidance.
“The worst example of airport vehicle driving I have seen in a 30 year aviation career.”
Anonymous airline captain (ASRS submission)
That 2016 report described a fuel-truck encounter that forced an unusually hard braking event in which a flight attendant was injured, highlighting risks when vehicle operators and aircraft crews are insufficiently coordinated.
“Ground Control issued a stop command just in time.”
First officer (July 2024 ASRS submission)
The July 2024 submission recounts a near collision when a taxiing aircraft was cleared to cross a runway nearly simultaneously with another aircraft’s landing, illustrating slim margins that crews reported as recurring during busy periods.
Unconfirmed
- Whether the runway status light system was intermittently inoperative during specific reported near-misses is asserted in ASRS submissions but not independently verified in FAA maintenance logs available to the public.
- Claims that single controllers regularly manage both tower and ground frequencies at peak times come from anonymous reports and are not corroborated by publicly released staffing rosters or FAA policy documents.
- Any direct causal link between earlier reported near-misses and the March 23, 2026 collision remains under investigation and has not been established by investigators.
Bottom Line
Decades of anonymous safety reports and FAA records show repeated vehicle-related hazards and coordination challenges at LaGuardia. While many incidents did not result in injury, the accumulation of near-misses and localized procedural doubts point to persistent vulnerabilities that industry actors and regulators must address.
Immediate focus should be on well-defined short-term actions—ensuring runway-status systems work reliably, clarifying vehicle access rules during high-intensity periods, and separating tower and ground duties where practicable—while stakeholders pursue longer-term infrastructure and procedural changes. As the NTSB and FAA complete formal investigations, those findings will be critical to shaping mandatory fixes and restoring confidence in daily operations at one of the nation’s busiest and most constrained airports.