No offense but pilots are probably at peak automation since their job has mostly been reduced to being a glorified AutoPilot system babysitters mainly needed for regulatory hedging. The ground transportation is still fair game though.
For example, engine falls off. The automation doesn't know that happened, it just sees various problems like the hydraulic pressure falls, and for some reason the engine thrust went to zero.
When I was at Boeing, an incident was recounted to me where the autopilot glitched and rolled the plane over into a vertical dive. It was going so fast it entered "separation", where the airflow no longer flows over the flight controls. In other words, the pilots were just along for the ride.
But the pilot figures, since we're dead anyway, let's try lowering the landing gear and see if it slows the jet down. He did, and it ripped the doors off and bent the gear back, but it slowed enough that the flight controls could get a "bite" and the pilots were able to regain control and landed safely.
Suffice to say that what's in current civil jetliners is very far from the state of the art. I fully expect properly implemented and integrated AI to be far superior to human pilots in the future - it probably would be already, if we put the effort in.
That's correct. But it's an easy problem to automate, because the problem being solved is well understood.
That's not the case for something randomly breaking.
I doubt the FAA would certify an AI running a jetliner, for the simple reason that if something unexpected happens, there's no way to predict what the AI will do. FSD for cars was done by collecting an incredible amount of data from the cameras on Teslas. Yet still, how much data was collected from Teslas having a catastrophic failure, like catching fire? A jetliner has a lot more failure modes than a car.
I'm not sure how the news being delivered by a carbon-based pilot would help with the dying part but I guess hospice care exists for a reason.
How can software engineers maintain a healthy "manual programming" skill set? What employer would be willing to pay for so much wasted time for their software engineers to do deliberate training courses, or willing to accept the productivity loss from their engineers occasionally working manually for practice, when working manually is so much slower?
Lots of regulation or some landmark lawsuits should do it. If airlines operated the way tech companies did, we'd have daily plane crashes.
Pilots have to know all the ins and outs of every single system and subsystem of the machine they operate. If software engineers were required to understand their systems to the same degree in order to ship something, the only way you could do it is by coding yourself.
It's not like the pilot instructs every single control surface individually. Nor does he physically carry every single passenger on his back.
Just because you're using a machine to do your job now doesn't really change anything substantial about the job other than the fact that you now need capital to pay the machine.
Any role where the human is a buffer against chaos should be thought of as secure by everyone involved. All automation and information flow will be in service to this position. This is not a bottleneck, it is the point of the exercise.
Wow. You clearly have zero idea of what a pilot's job is, and it shows.
You are also severely underestimating how much work and regulation would be required to replace pilots. And this work can be undone in a flash the first time automation messes up.
Also note that plane automation heavily relies on sensors. Many plane accidents were caused by faulty sensors even with humans in the loop.