3 ms·
TL;DR - Don't screw with the defaults (MCP) after landing, especially when it's unnecessary and when the next takeoff crew likely will not remember to set it to
by blinkingled 5y ago
TL;DR - Don't screw with the defaults (MCP) after landing, especially when it's unnecessary and when the next takeoff crew likely will not remember to set it to proper value before takeoff.
I wonder if this is not a detectable condition for the flight software - maybe in some cases you want the MCP to be set to low? Otherwise autopilot could either auto correct it or issue a warning?
- AnimalMuppet 5y ago> the next takeoff crew likely will not remember to set it to proper value before takeoff. If the takeoff depends on it, the next takeoff crew had better remember to set it. What's more, there better be at least one checklist that requires them to set it. And they had better follow the checklists.
- sokoloff 5y agoStandard takeoff procedures would have them rotating at a calculated airspeed and pitching for a climb target before transitioning to follow the FD. This crew’s issues went way past a pre-select mistake.
- ohazi 5y agoThis was 100% pilot error. You don't ever "follow the flight director" to determine when to rotate, you use the airspeed indicator.
- blinkingled 5y agoSure, but the TL;DR was the approach Emirates took - they literally communicated that to the crew and I can't say I disagree with it - why add to process/work if you can leave it at a sane default? (Unless I misunderstand - which is why my question.)