Post by sidneyschwartz on Jul 23, 2014 14:11:36 GMT -5
I have a couple of requests to be added to the checklists.
1. Clearance, obtained. Obviously you can't account for every possible item on every panel, but I would think this would be pretty universal.
2. The addition of Interactive Option 4, which would be to wait until CTRL is pressed before proceeding. Internal values and time elapsed would be ignored. This would add the flexibility to account for pretty much any situation, and I would prefer it to options 2 or 3 in those cases where FSFO cannot read internal values.
Speaking of checklists, I've noticed that FSFO will react differently to the same checklist items depending on whether they are being turned off or on. For example, when I get to turning on the APU, the captain calls "APU" and then FSFO waits for me to press CTRL. Same with APU air. I'm assuming FSFO can't read the internal values with this panel. After takeoff when it's time to turn off the APU and APU air, the captain calls "APU" and the FO responds immediately, then the same with the APU air. I tried setting the expected values to 1 for turning the APU and APU air off, but the results were the same. This is a good example of where Option 4 suggested above would be useful.
1. Clearance, obtained. Obviously you can't account for every possible item on every panel, but I would think this would be pretty universal.
2. The addition of Interactive Option 4, which would be to wait until CTRL is pressed before proceeding. Internal values and time elapsed would be ignored. This would add the flexibility to account for pretty much any situation, and I would prefer it to options 2 or 3 in those cases where FSFO cannot read internal values.
Speaking of checklists, I've noticed that FSFO will react differently to the same checklist items depending on whether they are being turned off or on. For example, when I get to turning on the APU, the captain calls "APU" and then FSFO waits for me to press CTRL. Same with APU air. I'm assuming FSFO can't read the internal values with this panel. After takeoff when it's time to turn off the APU and APU air, the captain calls "APU" and the FO responds immediately, then the same with the APU air. I tried setting the expected values to 1 for turning the APU and APU air off, but the results were the same. This is a good example of where Option 4 suggested above would be useful.
