LaGuardia Airport: Air Canada Flight 8646

You just lost your ARFF unit at the same moment you received an aircraft-with-casualties incident that requires ARFF response. Simultaneously, the two officers on that truck are now patients. Your ARFF capability is degraded or gone at the moment of peak demand for it.

First minutes: you need to immediately determine what additional ARFF resources are available at the airport, what mutual aid ARFF resources exist in your response plan, and whether FDNY aviation assets can fill the gap. You are not just dispatching to a crash — you are dispatching to a crash while managing a simultaneous resource deficit. The ARFF truck that rolled up to Jazz 646 was not a bonus resource; it was the intended primary responder. What is your second line?

This is a resourcing discussion your center should have before an event, not during one. Does your agency or airport have a written protocol for ARFF asset loss during an active ARFF-required event? Who knows where that document is at 11:40 PM?

In a standard aircraft emergency, you expect crew-directed evacuation. Flight crew are trained in emergency procedures, know their aircraft, and provide organized egress. When that leadership is gone — dead, incapacitated, or removed from the aircraft — you have 72 passengers acting on instinct in darkness on a runway, potentially near fuel, in a partially destroyed aircraft.

What does your comm center know, and when? The self-evacuation almost certainly happened before first responders arrived on scene. By the time units reported passengers on the tarmac, some may have been injured further by the evacuation itself, or wandered into active taxiway areas. Does your first-arriving unit know to immediately establish a perimeter to contain evacuees? Are you tracking an unaccompanied minor, who in this case was eventually located and reunited with family?

The absence of crew command structure is also a communication gap: nobody on the aircraft is coordinating with the comm center. Your information about conditions inside the aircraft is zero until responders board it. Plan for that ambiguity from dispatch.

This is not a question about whether the statement was accurate or appropriate. It is a question about what your center's protocol is for the moment after a critical incident when a dispatcher or controller makes a statement on a recorded channel that goes beyond operational necessity.

"I messed up" is a human response to a catastrophic event. It is also now evidence in an NTSB investigation and public record on LiveATC. Most centers have protocols about post-incident communications — relieving personnel, securing recordings, restricting non-operational transmissions on active channels. The question for your supervisors: at what point after a critical incident do you relieve the affected dispatcher, and who makes that call?

This is also a wellness conversation. The controller worked a simultaneous emergency, made a clearance decision, and watched the result in real time. That person needs support, not just procedure. Does your center have a protocol for immediate welfare check on involved personnel?

The United incident was relatively routine — an aborted takeoff, odor complaint, flight attendants feeling ill. It was serious enough to require ARFF response, but it was not a mass casualty event. It was exactly the kind of call that gets handled a hundred times a year. The problem is that handling it required crossing an active runway, at night, with an inbound aircraft in the final seconds of its approach.

The parallel here for 911 comm centers: the most dangerous moment is not always the major incident. Sometimes it is the second, less urgent call that arrives while you are managing the first. The clearance that cleared the truck to cross Runway 4 was given in the context of managing a separate active emergency. Cognitive load, task saturation, and divided attention are real. The question for your shift: what is your center's protocol for recognizing when a dispatcher is at capacity, and how do you redistribute load in real time?

In 911 centers, this often surfaces as: does your supervisor monitor for task saturation, or do they wait for a dispatcher to ask for help?

This is a pre-incident planning question as much as an operational one. In the LaGuardia event, the Port Authority activated emergency response protocols, the FAA issued a ground stop, the NTSB dispatched a go-team, and dozens of arriving flights were diverted — all within the first 30 minutes. Kathryn Garcia held a press conference before most of the city was awake.

For a major airport MCI, the notification cascade runs roughly: comm center supervisor → airport operations center → agency leadership → regional hospitals (trauma activation) → FAA operations center → NTSB duty officer → public information officer → family assistance center activation → mutual aid partners. The airline also has its own notification chain running in parallel — Air Canada stood up a family assistance line at 1-800-961-7099 within hours.

The discussion prompt for your center: pull your airport MCI plan. When was it last exercised? Does your comm center have a laminated notification card for an aircraft mass casualty? If the answer is "it is somewhere in a binder," that is the gap to close before the next event.

Advanced surface surveillance systems use radar and transponder data to alert controllers to potential runway conflicts. LaGuardia has this system. The collision happened anyway. The reasons why are for the NTSB to determine, but the lesson for dispatch professionals is consistent with every prior technology-failure incident in this library: technology raises the floor but does not eliminate human error. It supplements judgment; it does not replace it.

In your center, the parallel might be: CAD alerts that get acknowledged and dismissed, enhanced data displays that do not get read, protocols that assume the technology caught what a human missed. The question for your training staff is whether your dispatchers understand both what their technology does and what it does not do. An alert that a dispatcher does not act on is not a safety layer. It is noise.

Most centers have a post-incident protocol that includes relieving involved personnel, securing recordings, and initiating a welfare check. What varies is the timing and the person responsible for initiating it. At 11:40 PM on a Sunday, who at your center has the authority and responsibility to relieve a dispatcher who just worked a fatal incident? Is it the on-duty supervisor, or does it require a manager on call? How fast can that happen, and does your staffing allow for it without uncovering positions?

The second conversation is legal: involved personnel should be aware of their right to union representation and their right not to speak to investigators without counsel present. That is not a question of guilt — it is standard practice that protects personnel while the facts are determined. Does your center have a relationship with your union rep or legal advisor that would enable a call within an hour of a critical incident?

Most airport MCI plans assume ARFF resources are available and responding. The scenario where an ARFF vehicle is destroyed in the initiating event is less commonly exercised. If your airport has ARFF mutual aid agreements, when were they last tested? Does your comm center have the contact information and response times for secondary ARFF resources in a format that can be accessed in under 60 seconds at 11 PM?

The LaGuardia event also had a second parallel incident already in progress at the time of the collision. ARFF resources were already deployed to a declared emergency when the collision happened. That layered complexity — two incidents, degraded resources, one controller — is worth tabletop-ing specifically. Has your airport ever run a two-simultaneous-incident ARFF exercise?