So presumably you would have an alarm that wakes up the pilot if this happens. Here's the problem: humans wake up pretty slowly. For 10 minutes or so after you wake up, you might as well be drunk as far as your reaction time and judgment are concerned. I don't know if this has been tested in high stress situations, and I would guess that the "warm up time" is faster if your adrenaline is pumping, but it's still going to be a lot worse than having already been awake.
The point is that the several hours en route are a good time for the pilots to rest. Takeoff and landing are the riskiest phases of flight. I'm mainly concerned that the pilots are on top of their game then.
I'd say that 'might as well be drunk' period lasts around 30 seconds for me (the process of getting dressed is generally just a foggy blur...). By the time I'm moving toward the truck, I'm more or less firing on all cylinders.
30 seconds is still an awfully long time in a plane when stuff is going sideways...
On the other hand, sleep deprivation (which as the article mentions, can be far worse than being legally drunk) is common and pilots probably often perform the most difficult parts of the flight while under its effects.
I would think the risks of pilots sleeping (and, very rarely, getting caught unprepared for an emergency) would be minimal compared to the risks of pilots being regularly incapacitated by fatigue during the most difficult parts of the flight.
I disagree with the other pilot (but I'm only PPL) on his views about sleeping during boring stages of flight. Say for instance you've piloted badly into a CB, you suffer a freezing on your pitot static systems. The autopilot disengages.
If you were asleep, it might take a while for you to get your act together, co-ordinate to ascertain who has the flight controls and start CRM procedures.
If you were wide awake, thinking how to solve this tricksy problem, you might do a better job as your mind is already warmed up!
('bang their favorite stewardess/steward', wait, that still happens? I suppose it could be fitted around a sleep schedule)
YOU'RE A GLORIFIED BUS DRIVER. JUST GET US WHERE IT SAYS ON THE TICKET.
I hate this type of sentiment. Guess what: most programmers are glorified plumbers!
It makes you think of all those movies where the protagonist, with no experience suddenly leaps into action and pilots the plane to safety.
Question for pilots - if you learn one plane, can you pick them all up? Or are they all vastly different?
I can't start it; I might not be able to taxi it in to the ramp; I surely can't diagnose system faults on an unfamiliar plane, but it's easy to get it to the ground and generally easy to get it stopped (especially if you choose an 8000+ runway, rather than the 5000 foot that might have been the original destination).
The vast differences don't matter much when everything is working and there are plenty of margins and you only have to land/stop.
But they don't feel the need to disturb 500 people every 20 minutes because they like the sound of their own voice.
There's far, FAR more akin to sailing than driving when you fly aircraft. Fluid dynamics are very similar, regardless of whether it's water or air you're sailing through.
I don't think being a sailor has ever been a shameful profession; much the opposite, in fact.
The only phases of flight where you really need humans at the controls are takeoff, landing, and uh-oh what the fuck is going on (this being a broad "catch all" category which encompasses everything from an exploded engine and hydraulic failure, see United Airlines / Sioux City, to a medical emergency).
I would never fly on a pilotless airliner, but I'm fine with the pilots being asleep at the wheel during the en route phase of flight. There really isn't much to do except look at the GPS moving map and say "yep, we're over Iowa...... yep, we're still over Iowa". Course/altitude adjustments could all be beamed in from ATC.
I'd prefer them to be rested up for landing, or in case something unexpected pops up.