Originally Posted by DozyWannabe
ECAM isn't meant to be used in that way - it will give advice on technical issues and parameters that should not be exceeded, but it can't tell the pilots how to fly the aircraft. Call it "denying info" if you like, but no other airliner does anything similar, and for all it's worth I don't think it should.
What it *will* say is "ADR FAULT" or "ADR DISAGREE", the latter of which implies strongly that UAS procedures should be followed.
I'm not asking for the machine to tell me how to fly the airplane. I'm asking for the machine to tell me why it gave up and gave control to me!
If ECAM can tell me to consider Unreliable Speed procedures after a pitot heat failure, why can't it tell me to consider same when the data is corrupt? If it knows it doesnt have good enough data to fly itself, why not just make the first line of ECAM, "UAS procedure - Apply" ?
People like you want to have it both ways. You want for me, the pilot, to be able to pull your design butt out of the fire when the all knowing automation doesn't know all.....this after you've spent thousands of words explaining to me why I need the automation in the first place.
You need me in the cockpit, but you don't want me there.
In the end, I take solace in the knowledge that you need me more than I need your technology.