I'm sure the NTSB report will cover why this didn't stop the accident. Presumably either the system wasn't working as-expected, or the fire truck proceeded despite the warning lights since they had clearance from the controller.

The system is only advisory at present, so if the truck did see a warning light and proceeded anyway, they were technically permitted to do so.

1700 incursions a year, and other articles mentioning multiple near misses a week at a single airport [1]. It is safe in practice, likely largely due to the pilots here also being heavily trained and looking for mistakes, but it seems a lot like rolling the dice for a bad day.

>I am sure the working conditions of ATC staff might be improved - but being both a pilot and a programmer, I know that there is no easy digitalization magic wand for aviation.

I didn't say it'd be free. Just hard to believe radio voice communication is the best way to go.

[1] https://www.nytimes.com/interactive/2023/08/21/business/airl...

Traffic lights instead of mad max intersections are better.

Then there's subway Automatic Train Control.

I don't know that Air Traffic Control staff don't have computer systems for establishing which plane owns what airspace. They at least did do it manually already following specific processes, so it can be at least augmented and a computer can check for conflicts automatically (if it isn't already). And, sure, ATC could still use radio, but there could be a digital standard for ensuring everybody has access to all local airspace data. Or maybe that wouldn't help.

Your ground vehicle wanting to cross a runway could have the driver punch "cross runway 5" button (cross-referenced with GPS) and try to grab an immediate 30 second mutex on it. The computer can check that the runway is not allocated in that time (i.e. it could be allocated 2 minutes in the future, and that would be fine).

But, as pointed out elsewhere, obviously some of this is already present: stop lights are supposed to be present at this intersection.