Literally the crash here was caused by a fire truck entering the runway.
No one here or anywhere is saying automation would solve or be able to handle everything that human operators handle, that's an argument you invented that no one is making.
People are saying automation could handle a significant portion of the routine things allowing humans to handle the more complex/finicky issues.
Even if automation could handle 10% of the most common situations it would be a huge boon. In reality its probably closer to 50%.
Very possibly. It will be interesting what comes from the investigation.
> No one here or anywhere is saying automation would solve or be able to handle everything that human operators handle, that's an argument you invented that no one is making.
I’m asking if it would have solved even the current situation. The truck presumably saw the red light, and was asking to cross. Would traffic control have said no if more had been automated and if so, what automation would fix this? Unless we are supposing the truck would be autonomously driven and refuse to proceed when planes are landing, in which case, maybe, though that’s not really ATC automation anymore.
To be clear, though, I don’t even have significant aviation knowledge. But this isn’t hard to learn about. That’s part of what irks me so much about this tone. It’s not just “I’m so smart” it’s “I’m so confident that you’re dumb that I don’t need to know anything about the domain you’re working in to know better than you”. Someone could ask ChatGPT why airports don’t have stoplights to stop traffic from crossing the runway and it would reveal the existence of this system.
This frustates me to no end. Is it just an example of the Dunning–Kruger effect?
There are many issues with DK, and the paper’s widely misunderstood. For one, the primary figure demonstrates a positive correlation between confidence and competence, so according to DK’s own paper, high confidence is not an indicator of incompetence, contrary to popular belief. The paper also measured things in a very funny way (by having participants rank themselves against other people of unknown skill), and it measured only very simple things (like basic grammar, and ability to get a joke), and it only polled Cornell undergrads (no truly incompetent people), and there were a tiny number of participants receiving extra credit (might exclude the As and Fs in the class). Many smart people have come to the conclusion that DK is a statistical artifact of the way they did their experiment, not a real cognitive bias. Some smart people have pointed out that DK is probably popular because it’s really tempting to believe - we like the idea of arrogant people getting justice. The paper also primes the reader, telling them what to believe even though the title isn’t truly supported by the data. It’s an interesting read that I think would not pass today’s publication criteria.
Anyway, sorry, slash rant.
My grandfather had a rule at his business for 55-ish years: we welcome your ideas and suggestions, but not for the first year. You spend that time learning our processes, decisions behind them, pain points, areas that need improvement, etc. You also spend that time doing the work and hearing from your colleagues. Then you can (hopefully) make informed suggestions. That's not possible in every situation, but I like the intent.
This is an amazingly positive spin on the behavior.
even my cheap car has geofencing and automatic braking
I've worked on avionics professionally and I haven't crashed any of my planes yet...
It will be interesting to see what the report says. Did the light system not function? Did they override it? Do they ignore it consistently?
> geofencing and automatic braking
I’m not at all sure I want emergency vehicles to be blocked like this. And if they can override then it’s no different. They didn’t roll onto the runway on accident.
> I've worked on avionics professionally and I haven't crashed any of my planes yet...
Is this relevant somehow?
If the reason you have the human there is to handle the unusual cases, you run the real risk that they just aren't paying attention at critical moments when they need to pay attention.
It's pretty similar to the problem with L3 autonomous driving.
Probably the sweet spot is automation which makes clear the current set of instructions on the airport which also red flags when a dangerous scenario is created. I believe that already exists, but it's software that was last written in 1995 or so.
Regardless, before any sort of new automation could be deployed, we need slack for the ATC to be able to adopt a new system. That's the biggest pressing problem. We could create the perfect software for ATC, but if the current air traffic controllers are all working overtime and doing a job designed for 3 people rather than one, they simply won't have the time to explore and understand that new system. It'll get in the way rather than solve a problem. More money is part of the solution here, but we also need a revamped ATC training program which can help to fill the current hole.
Digital comms is available in the US:
* https://www.faa.gov/air_traffic/technology/DataComm
The issue is that the final approach and landing (and taxiing?) environments are probably too dynamic for that: in this particular situation one of the vehicles was responding to an emergency (fire).
In addition to huge planes, there is baggage transportation, passenger buses (to mid-field terminals), fuel pumpers, emergency vehicles, snow plows, deicers, and general maintenance vehicles (clear debris off runways).
I would settle for a good digital system with an ability to issue emergency/priority calls to specific receivers. Oh, and full-duplex communication.
I'm practicing for a sports pilot license, and I really have problems with understanding other pilots and the ATC.
Much of aviation is still based on pre WWII tech and practices like this and people underestimate how slow and difficult it is to change. Many piston aircraft still run on leaded gas, for example, the last existing market for it in the US.
Software routinely solves database coordination problems with millions of users per second.
....if they go around kilometer of the runway the fire will turn into bigger fire
I imagine the training will consist of something like changing the comms protocol to say “runway lights are on, control. Truck 1 confirming cross runway 4D?” prior to crossing. Double check so to speak.
Pilots and controllers speak the same language in the same order; ground vehicles just kinda say stuff.
The aviation-ized version of your proposal would be something like this:
> tower truck 1 short of 4 at delta, red status lights
This isn't a Kubernetes cluster where you can add VMs in 30 seconds.
Even if most of the work is routine, you definitely still want a human in the loop.
A naive view that confuses the map with the territory.
While in a database state you write a row and reality updates atomically....for aircraft they exist in a physical world where your model lives with lag, noise, and lossy sensors, and that world keeps moving whether your software is watching or not. Failed database transactions roll back, a landing clearance issued against stale state does not. The hard problem in ATC is not coordination logic but physical objects with momentum, human agency, and failure modes that do not respect your consistency model.
Or to stick with the language of the analogy, every fruit tree has some fruit that is lower than the others. That doesn't mean all "low-hanging fruit" is within arm's reach of the ground, some fruit just doesn't require as big of a ladder as other fruit.
This comment isn't a judgment of this specific case. I don't know enough about ATC to have any confidence in my opinion on the viability of replacing humans with software.
That was my first comment in this thread, so there was no established goal to change. My sole goal was to clarify the meaning of an idiom that the comment I was replying to was misstating.
I even included a disclaimer that "This comment isn't a judgment of this specific case", so I don't know how you could have received it as such.
>the obvious or easy things that can be most readily done or dealt with in achieving success or making progress toward an objective
So not only can it be "obvious" rather than "easy", it is also in the context of "achieving success or making progress toward an objective". There is nothing in the definition that requires either this specific step or the overall goal to be easy.
[1] - https://www.merriam-webster.com/dictionary/low-hanging%20fru...