The radio crackles. One word: stop. A firefighter in a vehicle on the movement area hears it clearly. But there's no callsign. No vehicle number. No name. In the time it takes to wonder, the moment is already gone.
The NTSB's findings from the LaGuardia ground emergency don't point to a distracted controller or an untrained responder. They point to something quieter and harder to fix: the radio architecture itself.
ATC ground control operates on a shared broadcast frequency. Every transmission goes to everyone monitoring. The system assumes that when a controller issues an instruction, the intended recipient recognizes themselves as the target — because pilots know their own callsigns and are trained to self-identify in milliseconds. It's a protocol built entirely around flight crew cognition.
Emergency responders break that assumption completely. When a firefighter enters an airport movement area, they're required by FAA Advisory Circular 150/5210-20 to monitor ground frequency. But they receive no callsign training equivalent to flight crew. There's no acknowledgment loop. A "stop" command on that frequency could mean an aircraft, a fuel truck, or a fire vehicle. Without a direct-address protocol, the responder has no structured way to know.
This isn't unique to LaGuardia. The NTSB has flagged ground communication ambiguity in runway incursion cases at SFO and ORD. ICAO and the FAA have studied dedicated emergency responder frequencies for movement areas. Implementation across U.S. airports remains inconsistent.
The reflex response is retraining. But you cannot train someone to claim a message that was never addressed to them. The fix requires dedicated channels, direct-address protocols, or both — a systems problem that retraining alone cannot reach.
A shared frequency designed for pilots doesn't stop working when a firefighter arrives. It just stops working for them.