Runway Incursion at LaGuardia: An ICAO Aviation English Case Study
A landing clearance, a crossing clearance, and a conflict that developed faster than it could be resolved. When timing breaks down, separation disappears.
In this episode, we’re breaking down a runway incursion accident at New York LaGuardia Airport, an event that developed in seconds and ended in tragedy. We’ll walk through the sequence of events between a United Airlines 737 MAX 8 declaring an emergency and an Air Canada Express CRJ900 on final approach, then break down the key Aviation English vocabulary from this case, and close with a look at the human factor behind the transmissions.
Before we go any further, a quick note: this is not about assigning individual blame, and this is how NTSB Chairwoman Jennifer Homendy frames it. As she put it, investigators rarely find that a major accident was caused by just one failure, because the aviation system has multiple layers of defense built in to prevent accidents. So when something goes wrong, it usually means many things went wrong at once.
Hello, I’m Emilia Barska, and welcome to Revise Before Flight, your regular check on essential Aviation English. As a General English teacher and Aviation English specialist, my goal is to help you climb and maintain ICAO Level 5 Extended or Level 6 Expert.
Hello, aviators, and welcome back. This is Episode 13, “Runway Incursion at LaGuardia: An ICAO Aviation English Case Study.”
Runway operations, especially during emergencies, involve multiple moving parts, controllers, flight crews, ground vehicles, and rapidly changing priorities. In this case, the workload was clearly extreme. My focus here is on Aviation English and operational clarity, because in high-risk environments, communication is not just support, it is safety-critical.
I would also like to take a moment to express sincere condolences to the families of the two pilots who lost their lives, and to those who were injured and are still fighting for their recovery.
Event Description
Let’s start with the background situation that unfolded at LaGuardia Airport prior to the runway incursion.
“2384 is declaring an emergency. Flight attendants in the back are feeling ill because of the odor. We will need to go into any available gate to descend.” “Okay, roger that.”
On Sunday, March 22, 2026, a Boeing 737 MAX 8 operated by United Airlines, Flight United 2384, experienced a fume event in the cabin following two consecutive rejected takeoffs. As a result, the crew declared an emergency and required immediate assistance. Air traffic control dispatched local fire and emergency vehicles onto the maneuvering area to respond to the situation. This created a highly dynamic and time-critical situation on the ground.
At approximately 23:30 hours local time, a Bombardier CRJ900 operated by Air Canada Express, Flight Air Canada 8646, arriving from Montreal, was cleared to land on Runway 4. At the same time, a fire truck responding to the United aircraft requested and received clearance to cross Runway 4 at Taxiway Delta.
Moments later, with the CRJ900 on short final, the controller issued an urgent stop instruction to the vehicle, repeating it multiple times: “Stop, truck one, stop. Stop, truck one, stop.” “Jazz 646, go around, runway heading, 2,000.” “Jazz 646…” “Jazz 646 is here, colliding with the vehicle.” “Hold position, I know you can’t move, the vehicle’s been responding to you.”
Jazz 646, the callsign for Air Canada Express Flight 8646, touched down and, during the landing roll, collided with the fire truck. ADS-B data indicates the aircraft was traveling at approximately 114 knots at the point of intersection, a speed that left virtually no margin to avoid impact.
Following the collision, the aircraft skidded and exited via a high-speed turnoff before coming to a stop.
Weather Conditions at the Time of the Event
At the time of the event, the weather conditions were not extreme, but they did reduce safety margins. Visibility ranged between approximately 6 and 11 kilometers, meaning pilots could still see ahead, but not as clearly as in ideal conditions. There was light rain and mist in the air, making it more difficult to detect objects and accurately judge distance, especially at night.
The sky was largely overcast, with multiple cloud layers creating a dull, gray environment and limiting natural light. Winds were light, coming from the northeast at around 13 km/h, and were not a significant operational factor.
Overall, this created a wet runway and a visually degraded environment. While these conditions were not extreme, they contributed to reduced visual acquisition and situational awareness, particularly at night.
The Consequences
This accident had severe consequences. The captain and the first officer tragically lost their lives. Two firefighters sustained serious injuries. Nine passengers were seriously injured, and 32 passengers received minor injuries.
The airport was closed, and investigators from the National Transportation Safety Board (NTSB) were deployed to determine the contributing factors.
Key Language: ICAO Level 5 and 6
1. To dispatch local fire and emergency vehicles – To send emergency response units to a specific location to manage a developing situation. ATC dispatched local fire and emergency vehicles following the crew’s emergency declaration.
2. Consecutive rejected takeoffs – Two or more takeoff attempts that are aborted one after another due to a technical or safety issue. The aircraft experienced consecutive rejected takeoffs due to a suspected system malfunction.
3. Reduced visual acquisition – A decreased ability to visually detect and identify objects, traffic, or hazards. Reduced visual acquisition made it difficult for the crew to identify the vehicle on the runway.
The Human Factor: “I Messed Up”
When you hear a controller publicly admit, “I messed up,” it can be tempting to immediately assign blame.
In the aftermath of the collision at LaGuardia, the air traffic controller relayed the information to Frontier 4195, a flight from LaGuardia to Miami, who remarked, “That wasn’t good to watch.” The controller responded, “Yeah, I was here. I tried to reach out when I saw it, and we were dealing with an emergency earlier. I messed up.” Frontier 4195 answered, “No man, you did the best you could.”
Moments like these remind us that behind every transmission is a human being operating under intense pressure, often managing multiple priorities at once. As aviation professionals, or those training to become one, it’s essential to resist the urge to judge too quickly. Accidents are rarely the result of a single mistake. They are complex, layered events that require thorough investigation. Understanding must always come before judgment.
Recap
This event highlights a critical operational reality: runway incursions develop when clearances overlap, timing breaks down, attention is divided, and emergencies are introduced into an already complex environment. When that happens, the system becomes even more fragile.
Thank you for developing your operational Aviation English with me, because in aviation, safety is rarely about one moment. It’s about how multiple moments connect, and how small deviations can align into critical outcomes. This episode is a reminder that behind every procedure is a human system, and behind every system, people doing their best under pressure.
Until next time, clear skies, aviators.
Leave A Comment