181 DAY IN THE LIFE: PREPARING FOR THE UNEXPECTED CHAPTER 10 the rest of the simulation “on the fly,” adapting to the team. In cases where the flight control team has not realized the impacts of some failures, the CTO will call for inserting that very failure for the purpose of driving home the lesson of missing these types of cases. Such was the case on the April 24 simulation, when the CTO decided to drive home the criticality of the problem with the LA-1 MDM that the inexperienced flight controllers were missing. The training team will continue to stack failures to force the team to think of options and prepare for the next failure. In a simulation (Figure 3), another failure will always occur. By being constantly hit with numerous failures, the flight controllers can see how the interconnectedness of the systems works. Students also become confident and comfortable around the failures so that when they happen on the real vehicle, they can say, “I know this.” ETHOS: [ETHOS is leading the team in procedure 4.111 ECLSS (Environmental Control and Life Support System)/ ITCS (Internal Thermal Control System)/PTCS (Passive Thermal Control System) RECONFIGURATION FOR LAB1 MDM TRANSITION OR FAILURE.] In my mind the next critical item would be step 2.3, moding my Lab ITCS [Internal TCS] to Single MT [the MT loop running with a single pump] because in the current state right now we’re basically buying into the risk of a next failure, we don’t have any leak detection, for both ammonia and water leak detection. FLIGHT: Ok, so do you want to go ahead and execute that step before you assess the LA-1 MDM failure? ETHOS: FLIGHT I don’t think the conversation will take too long, about our forward path, whether we just troubleshoot really quick or stay in this configuration. FLIGHT: Alright, you have a couple minutes. ETHOS: Copy FLIGHT. CRONUS: FLIGHT, CRONUS, for IACs. FLIGHT: CRONUS, FLIGHT. CRONUS: Yeah FLIGHT my command was not successful so I’ve powered off IAC 1, and I’m thinking about why we got that signature when we powered it up. FLIGHT: Ok, ETHOS and CRONUS, LA-1 MDM, you guys are talking about it, so what’s the thought on it? ETHOS: Alright FLIGHT, so, yes, I have discussed this a little bit with my specialist as well, and I tagged up with CRONUS, and my recommendation right now is that we hold off on any type of trying to regain the LA-1 MDM right now and I will just put the rest of my steps per that 4.111 procedure in work. My rationale here is that my Lab P6 CCAA [Laboratory Port 6 Common Cabin Air assembly], the one that’s associated with this MDM is still running, however I have no insight into it, if we do the troubleshooting it would take my CCAA back down and if we’re not successful with it that CCAA down. That currently is the CCAA that is having condensate collection and we normally like to dry out our CCAAs before we shut them down. So after I configure all my stuff to safe with the LA-1 down, I would work a plan to try and swap that condensate over to another module, most likely we’d like the condensate to condense in Node 3. So, those are the actions I’d look for, and swapping the condensate takes a little while. So, there’s that action, as well as, we’d eventually like to do that anyway, to get on our S6 CCAA to have good insight into it. FLIGHT: Ok, understand. CRONUS: FLIGHT, CRONUS. FLIGHT: Ok, so at that point ETHOS, when you do all that reconfiguration, you’d like to CRONUS to do the LA-1 MDM troubleshooting? ETHOS: Yeah, as soon as we get condensation, and we’re comfortable, making sure that that CCAA is dry. FLIGHT: Ok, understand. ETHOS: As far as impacts, if for some reason we get forced our hand we can do it earlier, it’s not the worst thing in the world, but.. FLIGHT: And so, what’s the estimate time for that? A shift, two shifts, how much time do you need for all that? ETHOS: I would say at least the rest of my shift and [the next] shift FLIGHT, and if we can withstand holding off any troubleshooting till tomorrow that would be plenty of time to make sure we’re dried out on that Lab CCAA. FLIGHT: Ok, CRONUS, your input? CRONUS: Yeah, FLIGHT, CRONUS, I concur with ETHOS’s recommendation. There isn’t a rush to powercycle [rebooting a computer often can recover it just as on the ground with a laptop or desktop] the LA-1 MDM. We need to look at it a little bit more obviously we don’t want to be running in this configuration with the MDM in Min Ops without any insight into it indefinitely, but if it, we’re definitely fine with it staying here in order for him to get into configuration. [Min Ops, or Minimum Operations, is a mode of the MDM that keeps it running some basic functions even though it is not receiving direction from the computer above it.]