A350-1000 and other Fleet News
#2911
I’m in the exact same boat.
I will say this - the argument that SET = bad because it increases workload doesn’t hold up. We do lots of things that increase workload and yet manage that increase just fine under appropriate conditions:
Hand flying a departure past the AP engagement altitude increases workload. On a nice VFR day that increase in manageable and happens thousands of times a day. At night in the mountains with thunderstorms is not the time to be hand flying. Same with landing. If we are so concerned about workload increases we would autoland every time it was possible. Yet guys increase the workload every day by taking off the automation and we don’t have planes falling out of the sky. Again, there are definitely situations where hand flying on approach can task overload one or both pilots.
Heck, even doing the taxi checklist after you start taxiiing increases workload, so why isn’t anyone on here pushing to also do the taxi checklist every time right after pushback?
Yes, SET increases workload, but also pilots manage that work with ease each and every day. This just comes down to common sense. Short taxi, complex taxi, low vis taxi, recent new hire, recent upgrade, etc, spin both every time. On lots of other situations SET is completely reasonable (I guess this is also fleet dependent). We are all in agreement that the SET-no-matter-what guys are just dumb. But SET has a place in common sense operations, and just like many other aspects of our job it is left to our discretion instead having hard lines drawn.
I will say this - the argument that SET = bad because it increases workload doesn’t hold up. We do lots of things that increase workload and yet manage that increase just fine under appropriate conditions:
Hand flying a departure past the AP engagement altitude increases workload. On a nice VFR day that increase in manageable and happens thousands of times a day. At night in the mountains with thunderstorms is not the time to be hand flying. Same with landing. If we are so concerned about workload increases we would autoland every time it was possible. Yet guys increase the workload every day by taking off the automation and we don’t have planes falling out of the sky. Again, there are definitely situations where hand flying on approach can task overload one or both pilots.
Heck, even doing the taxi checklist after you start taxiiing increases workload, so why isn’t anyone on here pushing to also do the taxi checklist every time right after pushback?
Yes, SET increases workload, but also pilots manage that work with ease each and every day. This just comes down to common sense. Short taxi, complex taxi, low vis taxi, recent new hire, recent upgrade, etc, spin both every time. On lots of other situations SET is completely reasonable (I guess this is also fleet dependent). We are all in agreement that the SET-no-matter-what guys are just dumb. But SET has a place in common sense operations, and just like many other aspects of our job it is left to our discretion instead having hard lines drawn.
#2912
Gets Weekends Off
Joined APC: Apr 2016
Position: Looking left
Posts: 3,291
Ok. I'll say it. I think the default taxi checks should be done before we taxi. It's mostly a MCDU to WDR verification. It's a two person heads down procedure, when we need two heads up the most. Add in rudder checks while I'm trying to steer.. it resembles texting and driving while I'm steering with my knee. Having prompts that require you to look-point-read at things all over the flight deck while navigating / listing to radio / making 90° turns, moving flt controls.. all in the most incident conducive environment we have each flight. All for 15 seconds of precious latency. Sure, we're all used to it now and manage. But knocking it out with the parking brake set allows full attention to the checklist tasks, traps incorrect data and TOFUs, and allows 2 heads up with SA outside for taxi.
#2913
Ok. I'll say it. I think the default taxi checks should be done before we taxi. It's mostly a MCDU to WDR verification. It's a two person heads down procedure, when we need two heads up the most. Add in rudder checks while I'm trying to steer.. it resembles texting and driving while I'm steering with my knee. Having prompts that require you to look-point-read at things all over the flight deck while navigating / listing to radio / making 90° turns, moving flt controls.. all in the most incident conducive environment we have each flight. All for 15 seconds of precious latency. Sure, we're all used to it now and manage. But knocking it out with the parking brake set allows full attention to the checklist tasks, traps incorrect data and TOFUs, and allows 2 heads up with SA outside for taxi.
#2914
Ok. I'll say it. I think the default taxi checks should be done before we taxi. It's mostly a MCDU to WDR verification. It's a two person heads down procedure, when we need two heads up the most. Add in rudder checks while I'm trying to steer.. it resembles texting and driving while I'm steering with my knee. Having prompts that require you to look-point-read at things all over the flight deck while navigating / listing to radio / making 90° turns, moving flt controls.. all in the most incident conducive environment we have each flight. All for 15 seconds of precious latency. Sure, we're all used to it now and manage. But knocking it out with the parking brake set allows full attention to the checklist tasks, traps incorrect data and TOFUs, and allows 2 heads up with SA outside for taxi.
#2916
Gets Weekends Off
Joined APC: Apr 2020
Posts: 2,250
This 100%, I got some pushback on IOE but was told what I do after that is on me. Totally agree the whole thing will take what maybe 30 seconds tops but it’s longer when I’m trying to taxi and look around a bunch. No thanks, now SET yea there’s a time and a place but for the most part the juice isn’t worth the squeeze.
Wait for ground “delta I’ll call you back”.
#2917
#2918