Clearly human-run ATC results in situations like this, so the idea that automated ATC could result in a runway collision and should therefore never be implemented is bad.
You obviously wouldn't authorize the bot to do everything, but you could allow it to autonomously call for stops or go-arounds in a situation like this where a matter of a few seconds almost certainly would have made the difference.
Imagine the human controller gives the truck clearance to cross and the bot immediately sees the problem and interrupts with "No, Truck 1 stop, no clearance. JZA 646 pull up and go around." If either message gets through then the collision is avoided, and in case of a false positive, it's a 30 second delay for the truck and a few minutes to circle the plane around and give it a new slot.
If we aren't confident enough in the automation to allow it to make the call for something simple like a runway incursion/conflict (via total automation), augmentation might be worse than the current approach that calls for 100% awareness by the ATC. Self-driving research shows that at level 2 and level 3, people tune out and need time to get back "in the zone" during a failure of automation.
In doctor's offices it was easy, just listen to the verbal consult and write up a summary so doc doesn't spend every evening charting. What is the equivalent for ATC, in terms of an interface that would help surface relevant information, maintain context while multitasking, provide warnings, etc, basically something that is a companion and assistant but not in a way that removes agency from the human decision-maker or leaves them subject to zoning out and losing context so they're not equipped to handle an escalation?
Depends both on the form the "alarm" takes as well as the false positive rate. If the alarm is simply being told to go around, and if that has the same authority as a human, then it's an inconvenience but there shouldn't be any fatigue. Just frustration at being required to do something unnecessary.
Assuming the false positive rate were something like 1 incident per day at a major airport I don't even think it would result in much frustration. We stop at red lights that aren't really necessary all the time.
Even if it's just a warning to the ATC, distracting them and forcing them to reexamine a false positive call interrupts their flow and airspace awareness. I get what you're saying, that we could err on the side of alert first, out of precaution; but all our proposed solutions would really come down to just how good the false positive and false negative rates are.
BTW, stopping at a red light unnecessarily (or by extension, gunning it to get through a yellow/red light) could get you rear ended or cause a collision. Hard breaking and hard acceleration events are both penalized by insurance driver trackers because of that.
This specific situation I think could instead have been cheaply and easily avoided if the ground vehicle had been carrying a GPS enabled appliance that ingested ADS-B data and displayed for the driver any predicted trajectories in the vicinity that were near the ground. Basically a panel in the vehicle showing where any nearby ADS-B equipped planes were expected to be within the next 30 seconds or so.
> stopping at a red light unnecessarily
Is it not always legally necessary where you live? It certainly is here. When I described them as unnecessary I was recalling situations that would clearly be better served by a flashing yellow.
What you're describing almost sounds like TCAS, a collision avoidance system for planes in the air, and would be a good idea.
As for the redlights, yes, legally you would be required to stop if you're before the stop line. My language wasn't clear, as I was trying to describe those scenarios where a light's turning just as you're getting to/into the intersection. Some people will gun it to get through, others will jump on their brakes to not run what's technically a red.
That is how it is supposed to work. How did it work in reality is an other question of course, and no doubt it will be investigated.
The reason we won't ever have self-driving cars is that no matter how clever you make them, they're only any good when nothing is going wrong. They cannot anticipate, they can only react, too slowly, and often badly.
Self driving cars' reaction times aren't slowed by drugs, alcohol, or a Snapchat notification pulling their attention.
Current systems haven't been proven in all weather conditions and all inclement situations (ie that tesla collision with a white semi-trailer), but it's crazy to say that self-driving cars won't match or exceed human drivers in terms of safe miles driven. Waymo has already shown an 80 to 90% reduction in crashes compared to people.
Compared to unsafe people. It's an important caveat though I agree with the larger point you're making.
As I stated earlier I agree with the broader point you were trying to make. I like what they're doing. It's just important to be clear about what human skill actually looks like in this case - a multimodal distribution that's highly biased by category.
The other person's comment was "we won't ever have self-driving cars" because they aren't good enough: but something like Waymo already is, particularly for the population. If we waved a wand and replaced everyone's car with a Waymo, accident rates would fall, at a population level and at a per-mile driven level.
It's even tough to see that a Waymo would be more dangerous for a good driver: they too have never been the cause of a serious accident and have certainly driven more miles across the fleet than any human driver. All 4 serious injury accidents and both fatalities were essentially "other driver at fault, hit Waymo".
This isn't meant to glaze Waymo, but point out that self-driving cars in certain environments are "solved". They're expensive, proprietary, aren't suitable for trucking or deployment to cold climates (yet?); but self-driving that is safer than people-driving is already here. To your point: human skill in driving is variable: Waymo won't replace Verstappen right now, but just like the AGI argument with LLMs, they're already "smarter" than the average person in certain domains.
We can probably semi automate runway crossing. Someone mentioned red lights when you definitely cannot cross
My suggestion is to restrict the use of smaller jets like crj and turboprops. I know airports like LaGuardia can't handle the big jets either, but they could reduce the slots and require a jet that holds, say, 150 people or more. This would result in fewer flights per day to some airports, but reduce overall congestion while still serving the same number of passengers.
You're left with a bunch of planes in the sky that can't stay there forever, and not enough humans on the ground to manually land them.
Now image the outage is also happening at all airports nearby, preventing planes from diverting.
How do you get the planes out of the sky? Not enough humans to do it manually.
Now imagine the system comes back online. Does it know how to handle a crisis scenario where you have dozens of planes overhead, each about to run out of fuel? Hopefully someone thought of that edge case.
Remember when all the Waymos were confused by a power outage? Now do that, but with airplanes that will fall thousands of feet and kill hundreds instead of park in the middle of the street.
I'm not saying we shouldn't automate things. We should. But, it's not easy. If it was, we would have done it already.
I remember.
Do you remember (before Waymo existed) what happened to traffic in SF anytime the power went out?
I remember. It was pretty much the identical situation.
Traffic goes to hell when the traffic lights stop working properly (without Waymo and also with Waymo).
One of the failure modes should not be “guy forgot thing”.
It just feels wrong that the primary form of control in 2026 is voice over radio.
It already is.
> Now imagine there's a 3 hour outage of the automated system.
Planes divert to another airport, passengers grumble, end of story. Airport closures can and do happen all the time for all kinds of reasons, including weather or equipment malfunctions.
An example of a poorly thought-out implementation elsewhere does not exclude the possibility of coming up with a better one than humans coordinating with their mouths over radio.