WEBVTT FILE 1 00:01:12.501 --> 00:01:15.434 -Good morning, and welcome to the Countdown Status Briefing, 2 00:01:15.434 --> 00:01:19.801 the first briefing for the STS-103 countdown. 3 00:01:19.801 --> 00:01:24.234 We have with us today NASA Test Director Steve Altemus 4 00:01:24.234 --> 00:01:26.000 to deliver our countdown status, 5 00:01:26.000 --> 00:01:29.767 STS-103 Payload Manager Steve Ernest, 6 00:01:29.767 --> 00:01:31.567 giving our payload status, 7 00:01:31.567 --> 00:01:35.367 and finally Shuttle Weather Officer Ed Priselac. 8 00:01:35.367 --> 00:01:36.634 We'll begin the briefing this morning 9 00:01:36.634 --> 00:01:38.534 with comments from each of our panelists, 10 00:01:38.534 --> 00:01:41.601 and then we'll open up the floor for questions from the media. 11 00:01:41.601 --> 00:01:43.400 We'll start with the briefing from Steve Altemus. 12 00:01:43.400 --> 00:01:44.667 Steve? -Thank you, Joel. 13 00:01:44.667 --> 00:01:46.167 Well, good morning. 14 00:01:46.167 --> 00:01:48.667 It's good to be back in countdown again, 15 00:01:48.667 --> 00:01:50.067 and over the past several weeks, 16 00:01:50.067 --> 00:01:51.434 that you're aware of, that we've worked through 17 00:01:51.434 --> 00:01:54.534 a significant number of nonstandard work items 18 00:01:54.534 --> 00:01:56.434 have gotten to the point where the vehicle 19 00:01:56.434 --> 00:01:58.834 is configured for a nominal countdown. 20 00:01:58.834 --> 00:02:01.467 Last night we successfully closed out the aft compartment 21 00:02:01.467 --> 00:02:02.767 for flight 22 00:02:02.767 --> 00:02:06.667 and picked up the countdown at 1:30 this morning. 23 00:02:06.667 --> 00:02:08.701 The countdown itself is fairly straightforward, 24 00:02:08.701 --> 00:02:11.000 approximately 68 hours in length. 25 00:02:11.000 --> 00:02:14.334 We don't have any payload or mid-deck experiment work 26 00:02:14.334 --> 00:02:15.734 in the countdown with the exception 27 00:02:15.734 --> 00:02:21.033 of a T-0 conditioning purge on the payload instruments. 28 00:02:21.033 --> 00:02:22.934 I'd like to run through the countdown summary, 29 00:02:22.934 --> 00:02:25.334 some milestones for you. 30 00:02:25.334 --> 00:02:28.100 Like I said, we did pick up call to stations this morning. 31 00:02:28.100 --> 00:02:30.801 The count actually picked up at 1:30. 32 00:02:30.801 --> 00:02:32.133 Through the day today 33 00:02:32.133 --> 00:02:35.300 we'll be performing our preparations for PRSD load. 34 00:02:35.300 --> 00:02:37.968 We'll clear the pad at 5:30 this evening 35 00:02:37.968 --> 00:02:40.067 for a shuttle pick resistance test, 36 00:02:40.067 --> 00:02:45.133 then pick up with the PRSD Cryo load at 9:30 this evening. 37 00:02:45.133 --> 00:02:47.868 That'll be an 8-hour load with no boil-off 38 00:02:47.868 --> 00:02:49.634 or off-load, fairly standard, 39 00:02:49.634 --> 00:02:54.033 and then Wednesday we'll work the engine final preparations 40 00:02:54.033 --> 00:02:56.167 and TSM securing through the day, 41 00:02:56.167 --> 00:02:57.868 and then we'll activate the comms systems 42 00:02:57.868 --> 00:03:02.901 for launch 8:30 Wednesday evening. 43 00:03:02.901 --> 00:03:07.701 Thursday, the RSS is set to come back at 3:45 in the morning, 44 00:03:07.701 --> 00:03:09.901 and we'll configure the pad, 45 00:03:09.901 --> 00:03:12.901 do our final load preps for ET tanking. 46 00:03:12.901 --> 00:03:17.067 Tanking we have set at 12:30 Thursday afternoon, 47 00:03:17.067 --> 00:03:20.334 and that should be complete about 3 hours later. 48 00:03:20.334 --> 00:03:24.801 The flight crew is set to arrive on the pad just after 6 o'clock 49 00:03:24.801 --> 00:03:28.467 Thursday evening, and in the terminal count you can -- 50 00:03:28.467 --> 00:03:32.167 We have two planned holds: a 10-minute hold at T-minus 20 51 00:03:32.167 --> 00:03:35.000 and a 40-minute hold at T-minus 9. 52 00:03:35.000 --> 00:03:37.868 Our launch is set for 21:18, 53 00:03:37.868 --> 00:03:41.033 or 9:18 Eastern Standard Time on Thursday evening, 54 00:03:41.033 --> 00:03:43.701 with a landing just before 7 o'clock on Sunday. 55 00:03:43.701 --> 00:03:46.634 the 26th of December. 56 00:03:46.634 --> 00:03:51.033 So overall, like I said, we're into the countdown successfully. 57 00:03:51.033 --> 00:03:53.000 The vehicle is in great shape. 58 00:03:53.000 --> 00:03:55.934 The launch team is once again well-prepared, 59 00:03:55.934 --> 00:03:57.601 and I think, as Ed is going to tell you, 60 00:03:57.601 --> 00:03:59.467 it looks like the weather is going to cooperate, 61 00:03:59.467 --> 00:04:01.501 so we're all expecting a spectacular launch 62 00:04:01.501 --> 00:04:03.167 on Thursday night. 63 00:04:03.167 --> 00:04:04.467 That's all I have, Joel. 64 00:04:04.467 --> 00:04:05.968 -Thanks, Steve. 65 00:04:05.968 --> 00:04:08.400 And now we'll going to Steve Ernest with the payload status. 66 00:04:08.400 --> 00:04:09.467 -Thank you, Joel. 67 00:04:09.467 --> 00:04:12.834 We're expecting an exciting mission 68 00:04:12.834 --> 00:04:15.667 to repair the Hubble Space Telescope. 69 00:04:15.667 --> 00:04:20.234 We have seven highly experienced crew members on this flight 70 00:04:20.234 --> 00:04:23.834 that will perform four EVAs. 71 00:04:23.834 --> 00:04:25.133 The primary objective 72 00:04:25.133 --> 00:04:27.567 is to replace the gyros that have failed, 73 00:04:27.567 --> 00:04:32.200 and place the telescope in a safe mode condition, 74 00:04:32.200 --> 00:04:36.367 non-science gathering, and so we except an exciting mission. 75 00:04:36.367 --> 00:04:38.634 We're flying two carriers for the mission. 76 00:04:38.634 --> 00:04:41.100 One is the flight support system, for birthing 77 00:04:41.100 --> 00:04:43.300 and positioning the telescope. 78 00:04:43.300 --> 00:04:44.701 The other is an ORU carrier, 79 00:04:44.701 --> 00:04:47.300 which provides storage and protective enclosures 80 00:04:47.300 --> 00:04:50.267 for the replacement hardware that the crew will remove 81 00:04:50.267 --> 00:04:52.634 and replace on the telescope. 82 00:04:52.634 --> 00:04:56.033 Going over some of the timeline activities for the payload, 83 00:04:56.033 --> 00:04:59.868 the carriers arrived at KSC back on August 12th. 84 00:04:59.868 --> 00:05:02.601 The final Rate Sensor Unit, the rate gyro, 85 00:05:02.601 --> 00:05:04.400 was delivered on September 17th. 86 00:05:04.400 --> 00:05:06.000 It was a late delivery. 87 00:05:06.000 --> 00:05:09.834 We transferred to the pad on November 8th. 88 00:05:09.834 --> 00:05:13.801 Following that, we installed into Discovery on November 16th, 89 00:05:13.801 --> 00:05:15.801 performed our interface verification tests 90 00:05:15.801 --> 00:05:19.968 with Discovery on November 19th, and then preferred 91 00:05:19.968 --> 00:05:22.901 an end-to-end test with Mission Control Houston 92 00:05:22.901 --> 00:05:26.467 and the Goddard Space Flight Center on November 22nd. 93 00:05:26.467 --> 00:05:28.367 The payload bay doors were closed for flight 94 00:05:28.367 --> 00:05:30.400 on November 24th. 95 00:05:30.400 --> 00:05:33.534 We don't have any significant launch countdown activities. 96 00:05:33.534 --> 00:05:36.834 We're non-powered for the ascent. 97 00:05:36.834 --> 00:05:39.767 We have a GN2 purge, as Steve mentioned, 98 00:05:39.767 --> 00:05:43.334 to maintain cleanliness on a science instrument, 99 00:05:43.334 --> 00:05:46.400 the Fine Guidance Sensor, one of the replacement ORUs, 100 00:05:46.400 --> 00:05:48.434 and we expect an exciting mission. 101 00:05:48.434 --> 00:05:49.667 That's all I have, Joel. 102 00:05:49.667 --> 00:05:51.033 -Thank you, Steve. 103 00:05:51.033 --> 00:05:53.634 And finally we'll go to Ed Priselac with the weather. 104 00:05:53.634 --> 00:05:55.801 -Thank you, Joel, and good morning. 105 00:05:55.801 --> 00:05:57.734 In spite of conditions outside right now, 106 00:05:57.734 --> 00:05:59.400 we've got quite a bit of cloudiness 107 00:05:59.400 --> 00:06:02.033 working its way through the KSC area. 108 00:06:02.033 --> 00:06:03.601 That is one frontal system 109 00:06:03.601 --> 00:06:06.467 now actually pushing southeast of our area, 110 00:06:06.467 --> 00:06:08.434 then we'll have dry air coming in. 111 00:06:08.434 --> 00:06:11.501 Then, believe it or not, we have another front approaching, 112 00:06:11.501 --> 00:06:14.968 being here Wednesday, and should be through the area late 113 00:06:14.968 --> 00:06:17.434 Wednesday into very early Thursday. 114 00:06:17.434 --> 00:06:19.801 Given all of that, we do anticipate high pressure 115 00:06:19.801 --> 00:06:23.267 building into the area, and right now conditions look 116 00:06:23.267 --> 00:06:27.167 pretty good for getting off the ground on Thursday night. 117 00:06:27.167 --> 00:06:30.234 If we can look now just to a surface chart. 118 00:06:30.234 --> 00:06:31.934 Again, this is valid Thursday evening. 119 00:06:31.934 --> 00:06:35.801 You can see the second front offshore south and east of us, 120 00:06:35.801 --> 00:06:37.901 high pressure building in. 121 00:06:37.901 --> 00:06:40.868 We look now to the tanking forecast, 122 00:06:40.868 --> 00:06:42.300 and I apologize, it looks like 123 00:06:42.300 --> 00:06:44.267 we're not going to be able to read that very well. 124 00:06:44.267 --> 00:06:48.334 We have few layered clouds with that second front going through. 125 00:06:48.334 --> 00:06:49.701 No thunderstorms in the area. 126 00:06:49.701 --> 00:06:52.033 No concerns about temperatures or winds, 127 00:06:52.033 --> 00:06:53.901 so we've got a zero probability 128 00:06:53.901 --> 00:06:58.767 that weather would impact any tanking operations. 129 00:06:58.767 --> 00:07:01.000 Looking to the launch forecast, 130 00:07:01.000 --> 00:07:03.634 which you probably can't read unfortunately, 131 00:07:03.634 --> 00:07:05.734 just some scattered low clouds, 132 00:07:05.734 --> 00:07:09.434 and a slight chance of a ceiling around 3,000 feet 133 00:07:09.434 --> 00:07:12.567 that would potentially impact through the range optics 134 00:07:12.567 --> 00:07:13.701 for launch, 135 00:07:13.701 --> 00:07:17.267 or the 5,000-foot ceiling for RTLS, 136 00:07:17.267 --> 00:07:19.467 but we only anticipate a 20 percent chance 137 00:07:19.467 --> 00:07:20.834 that that would occur. 138 00:07:20.834 --> 00:07:22.868 We do expect winds out of the northwest 139 00:07:22.868 --> 00:07:26.467 at about 10 to 18 knots at the SLF, 140 00:07:26.467 --> 00:07:28.901 and a little stronger at the pad. 141 00:07:28.901 --> 00:07:31.801 We have a 34-knot launch commit criteria 142 00:07:31.801 --> 00:07:33.534 for our northwest winds at the pad, 143 00:07:33.534 --> 00:07:36.033 so we're in good shape with regards to that. 144 00:07:36.033 --> 00:07:38.734 Temperatures will be down into the lower 50s, 145 00:07:38.734 --> 00:07:43.033 and one concern we do, or the NASA folks do have, 146 00:07:43.033 --> 00:07:45.434 is ice secreting on the tank 147 00:07:45.434 --> 00:07:47.634 with those types of temperatures. 148 00:07:47.634 --> 00:07:50.567 One thing, if the winds stay up, that would help ameliorate 149 00:07:50.567 --> 00:07:54.234 that condition, though, so we'll see how that plays out. 150 00:07:54.234 --> 00:07:57.200 With regard to 24-hour delay forecast, 151 00:07:57.200 --> 00:08:00.067 basically the similar conditions except winds coming out 152 00:08:00.067 --> 00:08:05.300 of the north, northeast 0, 3, 0, and just a slight chance, 153 00:08:05.300 --> 00:08:09.501 again, of a ceiling at around 3,000 feet. 154 00:08:09.501 --> 00:08:11.501 Given that, again, the 20 percent chance 155 00:08:11.501 --> 00:08:14.167 that weather might keep us on the ground. 156 00:08:14.167 --> 00:08:16.634 If we go on to Saturday, 157 00:08:16.634 --> 00:08:18.467 looks like we'll pick up some sort of easterly 158 00:08:18.467 --> 00:08:21.334 of southeasterly fetch in the local area, 159 00:08:21.334 --> 00:08:26.200 and given that, we'd have a chance of both low cloud 160 00:08:26.200 --> 00:08:28.501 and a small chance of bands of showers 161 00:08:28.501 --> 00:08:30.767 working their way in the KSC area, 162 00:08:30.767 --> 00:08:32.934 so we've forecast a 30 percent chance 163 00:08:32.934 --> 00:08:36.000 we might be kept on the ground on Saturday. 164 00:08:36.000 --> 00:08:39.167 And if we could go back to the SRB recovery forecast, 165 00:08:39.167 --> 00:08:45.300 which I missed, looks like some brisk winds offshore, 166 00:08:45.300 --> 00:08:51.968 running about 320 at 18, peak 24 knots. 167 00:08:51.968 --> 00:08:54.901 We've also had a number of storms to our distant east, 168 00:08:54.901 --> 00:08:56.601 which are creating swells offshore, 169 00:08:56.601 --> 00:08:57.901 so we're figuring sea is probably 170 00:08:57.901 --> 00:09:03.067 running 5 to 7 feet offshore, but still relatively 171 00:09:03.067 --> 00:09:08.167 good conditions for SRB pickup offshore. 172 00:09:08.167 --> 00:09:12.133 Looking to Edwards on launch day, 173 00:09:12.133 --> 00:09:15.767 SMG folks just forecasting a few clouds at 25,000 feet, 174 00:09:15.767 --> 00:09:20.334 good visibility, winds northeast at 8 to 12 knots, no issues. 175 00:09:20.334 --> 00:09:25.801 The same with the white sands, some broken cirrus at 25,000, 176 00:09:25.801 --> 00:09:29.868 good visibility, winds southwest 10 to 16 knots. 177 00:09:29.868 --> 00:09:32.234 Looking to the TALs, 178 00:09:32.234 --> 00:09:34.667 Banjul looking good with scattered clouds 179 00:09:34.667 --> 00:09:39.234 at 25,000 feet, good visibility and winds northeast at 7 knots, 180 00:09:39.234 --> 00:09:41.434 0. 2. 0 at 7 knots. 181 00:09:41.434 --> 00:09:44.934 Ben Guerir scattered clouds at 3,000 feet, good visibility 182 00:09:44.934 --> 00:09:46.834 and a very slight chance, 183 00:09:46.834 --> 00:09:49.834 or a chance of, crosswind violation, 184 00:09:49.834 --> 00:09:54.167 winds from 0, 5. 0 at 12 peak 20 knots. 185 00:09:54.167 --> 00:09:56.400 and I'll conclude at that point, gentleman. 186 00:09:56.400 --> 00:09:58.334 -Thanks, Ed. At this time we'll go ahead 187 00:09:58.334 --> 00:09:59.767 and take questions from the media. 188 00:09:59.767 --> 00:10:01.801 If you'd please just state your name and affiliation 189 00:10:01.801 --> 00:10:02.801 before you ask your question. 190 00:10:02.801 --> 00:10:04.400 We'll start over here with Todd. 191 00:10:07.300 --> 00:10:11.033 -Todd Halvorson of Space.com for Steve. 192 00:10:11.033 --> 00:10:14.000 You mentioned that you guys have had a lot of challenges 193 00:10:14.000 --> 00:10:16.868 in terms of ground processing in this particular flow, 194 00:10:16.868 --> 00:10:20.267 and seems like every time you disposition one problem 195 00:10:20.267 --> 00:10:21.601 another crops up, 196 00:10:21.601 --> 00:10:25.701 and I was wondering what the launch team, 197 00:10:25.701 --> 00:10:29.400 you know, thought about all these problems cropping up, 198 00:10:29.400 --> 00:10:33.667 and especially this late in the game over the past weekend? 199 00:10:33.667 --> 00:10:38.133 -Well, let me just say that the fact that we're discovering 200 00:10:38.133 --> 00:10:41.100 these problems is really a testament to the workforce. 201 00:10:41.100 --> 00:10:45.901 In that what they're doing is they're looking really hard, 202 00:10:45.901 --> 00:10:48.367 and the fact that we're finding these things and repairing 203 00:10:48.367 --> 00:10:53.067 these things really speaks to their diligence, 204 00:10:53.067 --> 00:10:55.534 and we'd much rather find them on the ground 205 00:10:55.534 --> 00:10:57.234 than we would during ascent or on orbit, 206 00:10:57.234 --> 00:11:01.200 so that the team is comfortable when we identify these problems 207 00:11:01.200 --> 00:11:02.934 and go ahead and fix them. 208 00:11:05.801 --> 00:11:10.534 -Follow-up, Todd? -Yeah, just a quick follow-up. 209 00:11:10.534 --> 00:11:12.767 I'm wondering if you can tell us what your strategy 210 00:11:12.767 --> 00:11:16.234 is going to be in terms of launch attempts here. 211 00:11:16.234 --> 00:11:19.267 You have a sort of a drop-dead date of the 18th to get off, 212 00:11:19.267 --> 00:11:22.000 and I understand you might position yourself 213 00:11:22.000 --> 00:11:25.667 to go three in a row if necessary. 214 00:11:25.667 --> 00:11:28.200 -Well, that's correct, Todd. 215 00:11:28.200 --> 00:11:31.067 What we have is, as you know, a year-end constraint 216 00:11:31.067 --> 00:11:32.601 for the year 200 rollover. 217 00:11:32.601 --> 00:11:35.434 We would like to be powered down at that time, 218 00:11:35.434 --> 00:11:39.801 and go through the rollover with no critical systems powered up. 219 00:11:39.801 --> 00:11:41.400 So that what means with a 10-day mission, 220 00:11:41.400 --> 00:11:43.400 we have to be on the ground 221 00:11:43.400 --> 00:11:47.167 and be in a posture secured before that rollover period, 222 00:11:47.167 --> 00:11:50.400 so what we need to do is attempt to launch on the 16th, 223 00:11:50.400 --> 00:11:52.100 hopefully get off on the 16th. 224 00:11:52.100 --> 00:11:54.868 We will plan for a 24-hour scrub turnaround, 225 00:11:54.868 --> 00:11:58.400 which would put us on the 17th and landing following that, 226 00:11:58.400 --> 00:12:01.334 and then there is a chance 227 00:12:01.334 --> 00:12:07.100 that we may attempt a third launch attempt on the 18th. 228 00:12:07.100 --> 00:12:10.033 We're looking at at that now from a perspective of quantity 229 00:12:10.033 --> 00:12:13.734 of cryogenics, hydrogen and liquid oxygen at the pad. 230 00:12:13.734 --> 00:12:17.367 We believe technically we have enough margin there. 231 00:12:17.367 --> 00:12:20.100 We're looking at the launch team itself 232 00:12:20.100 --> 00:12:21.334 and how stressed they would be 233 00:12:21.334 --> 00:12:24.067 in a three-attempt kind of scenario, 234 00:12:24.067 --> 00:12:25.734 and I think what it's going to come down to 235 00:12:25.734 --> 00:12:28.534 is basically how stressful the scrub 236 00:12:28.534 --> 00:12:30.167 is itself on a launch team, 237 00:12:30.167 --> 00:12:32.901 what the nature of the scrub is and what type of people, 238 00:12:32.901 --> 00:12:34.901 what systems we need to keep over and work 239 00:12:34.901 --> 00:12:36.400 to resolve any problems. 240 00:12:36.400 --> 00:12:40.467 And so, like I said, we are planning and looking at that, 241 00:12:40.467 --> 00:12:42.300 but it's going to be determined by the situation 242 00:12:42.300 --> 00:12:45.534 or specifics of the day. 243 00:12:45.534 --> 00:12:50.000 -We'll go ahead and go over to Mike, and then we'll come back. 244 00:12:50.000 --> 00:12:51.501 -Mike Cabbage with the Orlando Sentinel. 245 00:12:51.501 --> 00:12:53.868 My question is for Steve also. 246 00:12:53.868 --> 00:12:56.734 It's been almost 5 months since the last shuttle launch. 247 00:12:56.734 --> 00:12:59.601 Could you talk a bit about the sort of challenges a layoff 248 00:12:59.601 --> 00:13:01.767 like that poses for the launch team, 249 00:13:01.767 --> 00:13:04.701 the team's state of readiness and the sorts of things 250 00:13:04.701 --> 00:13:09.434 that you do to make sure that everybody stays sharp? 251 00:13:09.434 --> 00:13:10.667 -Okay, Mike. 252 00:13:10.667 --> 00:13:14.634 Well, I guess since STS-93, 253 00:13:14.634 --> 00:13:16.834 really the launch team preparations 254 00:13:16.834 --> 00:13:20.467 have been somewhat segregated from the launch rate, 255 00:13:20.467 --> 00:13:25.868 in that we simulate launch countdowns 256 00:13:25.868 --> 00:13:29.234 on a fairly regular basis every month or month 257 00:13:29.234 --> 00:13:32.901 and a half or so, so we've run through 258 00:13:32.901 --> 00:13:36.167 I'd say about six launch countdown simulations 259 00:13:36.167 --> 00:13:38.934 August, September and November. 260 00:13:38.934 --> 00:13:42.567 We've run through mission management team simulations 261 00:13:42.567 --> 00:13:45.067 to exercise the management folks. 262 00:13:45.067 --> 00:13:47.534 We've run through simulations 263 00:13:47.534 --> 00:13:49.100 with the facilities side of the house, 264 00:13:49.100 --> 00:13:52.000 to exercise those folks in a launch countdown environment. 265 00:13:52.000 --> 00:13:55.467 We've exercised the pad rescue forces 266 00:13:55.467 --> 00:13:57.467 and Closeout Crew activities. 267 00:13:57.467 --> 00:14:02.601 All these training activities have helped 268 00:14:02.601 --> 00:14:05.634 to heighten our preparedness 269 00:14:05.634 --> 00:14:08.534 and ensure that we're ready to go for launch, 270 00:14:08.534 --> 00:14:10.801 above and beyond the normal processing activities 271 00:14:10.801 --> 00:14:14.534 that would be occurring with an increased flight rate. 272 00:14:17.200 --> 00:14:18.200 -Follow-up? 273 00:14:18.200 --> 00:14:19.901 Come back over to Todd, please. 274 00:14:22.701 --> 00:14:26.334 -For Steve again, could you elaborate on the hold time 275 00:14:26.334 --> 00:14:30.434 you have on the pad in terms of consumables, liquid hydrogen, 276 00:14:30.434 --> 00:14:32.100 liquid oxygen, et cetera? 277 00:14:32.100 --> 00:14:33.534 -Sure. 278 00:14:33.534 --> 00:14:38.501 Turns out that the PRSD hold times for LH2 is about 8 days, 279 00:14:38.501 --> 00:14:40.067 and LOx is 21 days, 280 00:14:40.067 --> 00:14:44.667 which gives us plenty of margin to try and get off this month. 281 00:14:44.667 --> 00:14:46.968 We don't have any near-term range constraints, 282 00:14:46.968 --> 00:14:48.667 and, like I stated earlier, 283 00:14:48.667 --> 00:14:51.167 there's no payload or mid-deck experiment constraints 284 00:14:51.167 --> 00:14:54.501 that'll keep us on the ground, or keep us in a scrub -- 285 00:14:54.501 --> 00:14:56.601 affect our scrub turnaround scenarios. 286 00:14:58.767 --> 00:15:01.567 -Over here on the right side, please. 287 00:15:01.567 --> 00:15:06.501 -Franco Malerba, supporting the Italian Right TV. 288 00:15:06.501 --> 00:15:08.868 I would like to ask a question, one of the two Steves, 289 00:15:08.868 --> 00:15:11.567 about the crew activities. 290 00:15:11.567 --> 00:15:16.601 I see from the launch day schedule that they will be 291 00:15:16.601 --> 00:15:20.167 waking up at 12:30 p.m., so they will be shifted. 292 00:15:20.167 --> 00:15:21.300 Are they already shifted? 293 00:15:21.300 --> 00:15:24.934 Are they already in the launch schedule, 294 00:15:24.934 --> 00:15:29.501 or will they move to that in the next few days? 295 00:15:29.501 --> 00:15:31.968 -At this point they're already shifted to a sleep schedule, 296 00:15:31.968 --> 00:15:35.601 I believe, of they go to sleep at 3:30 each night 297 00:15:35.601 --> 00:15:36.968 and wake up about 11:30, 298 00:15:36.968 --> 00:15:41.701 so they're already shifted to their prime shift. 299 00:15:41.701 --> 00:15:44.100 With the delays in launch, 300 00:15:44.100 --> 00:15:45.801 we've had to slip those 30 minutes 301 00:15:45.801 --> 00:15:49.133 to an hour to catch them back up to put on schedule, 302 00:15:49.133 --> 00:15:51.701 so right now they're in their sleep cycle 303 00:15:51.701 --> 00:15:56.100 and their mission cycle, and they're ready to go. 304 00:15:56.100 --> 00:15:58.534 -Let's go over to Mark Caro, please. 305 00:16:03.400 --> 00:16:06.067 -Mark Caro from the Houston Chronicle for Steve Altemus. 306 00:16:06.067 --> 00:16:10.234 Could you just discuss the launch window 307 00:16:10.234 --> 00:16:11.567 and the exact launch time, 308 00:16:11.567 --> 00:16:13.300 sort of when do you expect to adjust it, 309 00:16:13.300 --> 00:16:17.234 or do you think you won't have to do that this time? 310 00:16:17.234 --> 00:16:20.667 -With the easterly trajectory on this mission, 311 00:16:20.667 --> 00:16:24.801 we have no window open versus preferred window 312 00:16:24.801 --> 00:16:26.467 discussion that needs to occur. 313 00:16:26.467 --> 00:16:30.067 We can target the window open, which is 9:18 Thursday night, 314 00:16:30.067 --> 00:16:33.033 and that'll be our time we'll count to, 315 00:16:33.033 --> 00:16:37.968 and we'll stay with if we have no technical issues. 316 00:16:37.968 --> 00:16:40.567 -Any other questions? Mike? 317 00:16:40.567 --> 00:16:42.667 -I have a question for Ed. 318 00:16:42.667 --> 00:16:44.100 What do the TAL sites look like 319 00:16:44.100 --> 00:16:46.634 as you move on into Saturday and Sunday? 320 00:16:46.634 --> 00:16:48.234 -Okay. 321 00:16:50.834 --> 00:16:53.300 Banjul still looking good with just scattered clouds 322 00:16:53.300 --> 00:16:58.267 at 25,000 feet, good visibility and northeast winds at 10 knots. 323 00:16:58.267 --> 00:17:00.667 Scattered clouds at Ben Guerir, but still a concern 324 00:17:00.667 --> 00:17:03.100 about crosswinds of the east/northeast 0, 325 00:17:03.100 --> 00:17:05.300 6. 0 at 12 to 20. 326 00:17:05.300 --> 00:17:07.901 and then finally Saturday both TALs look good. 327 00:17:07.901 --> 00:17:11.367 Scattered clouds at both places, good visibility 328 00:17:11.367 --> 00:17:15.601 and both locations forecast winds 0, 3, 0 at 12 knots, 329 00:17:15.601 --> 00:17:22.868 so Banjul looks like a problem for the first 2 days. 330 00:17:22.868 --> 00:17:26.367 -Come back to Todd, please. 331 00:17:26.367 --> 00:17:28.300 -This may be a question for Johnson, 332 00:17:28.300 --> 00:17:29.501 but I'll throw it out anyway. 333 00:17:29.501 --> 00:17:31.934 Steve, do you know where Hubble will be relative 334 00:17:31.934 --> 00:17:36.067 to the Kennedy Space Center at the time of launch 335 00:17:36.067 --> 00:17:40.868 and how far behind the orbiter will be 336 00:17:40.868 --> 00:17:44.567 when it gets on it's initial orbit? 337 00:17:44.567 --> 00:17:47.167 -That is probably a good question for Houston. 338 00:17:47.167 --> 00:17:50.734 I didn't go look at it. That's the phase angle of 339 00:17:50.734 --> 00:17:52.267 after launch, and where we're going to -- 340 00:17:52.267 --> 00:17:53.868 how we're going to catch up in so many revs, 341 00:17:53.868 --> 00:17:55.567 so they'd be better equipped to answer 342 00:17:55.567 --> 00:17:57.567 that than I would at this point. 343 00:17:57.567 --> 00:18:00.901 -We'll get that for you, Todd. -Quick correction to my summary: 344 00:18:00.901 --> 00:18:02.300 Banjul looks good all the way through. 345 00:18:02.300 --> 00:18:05.567 Ben Guerir has a problem first 2 days, crosswinds. 346 00:18:05.567 --> 00:18:07.834 -Any other questions here in the room? 347 00:18:07.834 --> 00:18:09.434 We have no other questions at the other center, 348 00:18:09.434 --> 00:18:11.501 so that will conclude this briefing. 349 00:18:11.501 --> 00:18:14.133 We'll remind you that we do have our 4 p.m. pre-launch 350 00:18:14.133 --> 00:18:16.601 briefing for STS-103 today. 351 00:18:16.601 --> 00:18:18.033 Thank you for joining us. 352 00:21:38.133 --> 00:21:39.434 -Good afternoon. 353 00:21:39.434 --> 00:21:42.033 Welcome to our STS-103 Pre-Launch News Conference. 354 00:21:42.033 --> 00:21:44.901 We have with us today Ron Dittemore, 355 00:21:44.901 --> 00:21:47.200 the shuttle program manager from the Johnson Space Center 356 00:21:47.200 --> 00:21:52.667 in Houston, Dave King, Director of Shuttle Operations 357 00:21:52.667 --> 00:21:55.467 here at Kennedy Space Center, 358 00:21:55.467 --> 00:21:58.067 and Captain Clif Stargardt, the Staff Meteorologist 359 00:21:58.067 --> 00:22:00.534 for the 45th Weather Squadron. 360 00:22:00.534 --> 00:22:02.701 And we'll start with opening comments from each person, 361 00:22:02.701 --> 00:22:04.968 and then we'll take your questions. 362 00:22:04.968 --> 00:22:06.067 Go ahead. 363 00:22:06.067 --> 00:22:08.467 -Okay, well, I've got to start off 364 00:22:08.467 --> 00:22:11.234 by saying it's finally good to be here. 365 00:22:11.234 --> 00:22:13.534 Last time we were here was in July, 366 00:22:13.534 --> 00:22:16.801 and we've done a lot working on our vehicles from July 367 00:22:16.801 --> 00:22:18.300 until now. 368 00:22:18.300 --> 00:22:22.767 A good friend of mine mentioned to me last week that -- 369 00:22:22.767 --> 00:22:24.167 reminded me of a saying 370 00:22:24.167 --> 00:22:29.167 that "the road to success is always under construction." 371 00:22:29.167 --> 00:22:30.501 And I think he was saying that 372 00:22:30.501 --> 00:22:32.534 because every time we seemed to turn around, 373 00:22:32.534 --> 00:22:35.000 we hit another pothole, another curb, 374 00:22:35.000 --> 00:22:38.000 another bump that we had to overcome, 375 00:22:38.000 --> 00:22:40.534 and it certainly seems that that was the case. 376 00:22:40.534 --> 00:22:43.634 We spent a lot of our time looking in nooks 377 00:22:43.634 --> 00:22:47.367 and crannies on this vehicle over the last 4 or 5 months, 378 00:22:47.367 --> 00:22:49.601 and I believe, and the team believes, 379 00:22:49.601 --> 00:22:55.367 that this vehicle is safe to fly as it has been in years. 380 00:22:55.367 --> 00:23:00.133 The scrutiny that was used to inspect the wires 381 00:23:00.133 --> 00:23:02.400 and other areas of the vehicle, 382 00:23:02.400 --> 00:23:05.300 the intensity of the work teams and the inspectors 383 00:23:05.300 --> 00:23:07.801 and the awareness of everybody in the system 384 00:23:07.801 --> 00:23:12.434 was increased because of this 4-month period, 385 00:23:12.434 --> 00:23:14.901 and I think it will show itself 386 00:23:14.901 --> 00:23:16.634 in the overall increase in safety. 387 00:23:16.634 --> 00:23:19.501 Not only of the vehicle and its readiness, 388 00:23:19.501 --> 00:23:22.834 but also of the teams. 389 00:23:22.834 --> 00:23:25.767 We did, as you know, find a problem on STS-93, 390 00:23:25.767 --> 00:23:28.300 which turned in to a much bigger problem. 391 00:23:28.300 --> 00:23:31.267 As we got into it, we found more wires 392 00:23:31.267 --> 00:23:34.033 that had insulation that was damaged, 393 00:23:34.033 --> 00:23:36.334 and what we thought would be a fairly simple thing 394 00:23:36.334 --> 00:23:38.000 to go identify and repair these wires 395 00:23:38.000 --> 00:23:41.234 turned out to be several months of activity. 396 00:23:41.234 --> 00:23:45.567 We did overall inspect over 100 miles of wires. 397 00:23:45.567 --> 00:23:47.234 We repaired wires. 398 00:23:47.234 --> 00:23:49.334 We modified procedures. 399 00:23:49.334 --> 00:23:51.968 We will improve access platforms, 400 00:23:51.968 --> 00:23:57.501 and we will implement a better inspection routine from now on. 401 00:23:57.501 --> 00:24:02.968 Columbia, which was the STS-93 mission, is out at Palmdale. 402 00:24:02.968 --> 00:24:04.934 Because we could not inspect 100 percent 403 00:24:04.934 --> 00:24:09.033 of all the wires on a vehicle here at Kennedy, 404 00:24:09.033 --> 00:24:11.968 we have begun inspecting those areas we could not reach, 405 00:24:11.968 --> 00:24:15.167 or didn't feel it was prudent to go in and inspect 406 00:24:15.167 --> 00:24:16.567 while we were here at Kennedy. 407 00:24:16.567 --> 00:24:18.901 We are inspecting those areas out at Palmdale, 408 00:24:18.901 --> 00:24:24.434 and so far we are finding similar results, 409 00:24:24.434 --> 00:24:26.734 and so we do plan, 410 00:24:26.734 --> 00:24:28.534 while we have Columbia at Palmdale, 411 00:24:28.534 --> 00:24:31.100 to do 100 percent inspection of our wires, 412 00:24:31.100 --> 00:24:34.334 and we're prudent we will add more protection 413 00:24:34.334 --> 00:24:36.033 for the types of things that we have seen here 414 00:24:36.033 --> 00:24:37.634 over the last 4 months. 415 00:24:39.701 --> 00:24:42.734 Let me talk a little bit about this mission. 416 00:24:42.734 --> 00:24:45.133 The mission to the Hubble Space Telescope 417 00:24:45.133 --> 00:24:47.934 is a textbook mission for the shuttle, 418 00:24:47.934 --> 00:24:51.200 where we can rendezvous, 419 00:24:51.200 --> 00:24:54.601 grapple with the Remote Manipulator System, 420 00:24:54.601 --> 00:24:58.567 use our EVA capability and go repair, 421 00:24:58.567 --> 00:25:01.734 and those are the types of flexibilities and capabilities 422 00:25:01.734 --> 00:25:05.033 that the shuttle has that will be necessary in the future, 423 00:25:05.033 --> 00:25:08.133 especially in the Space Station environment. 424 00:25:08.133 --> 00:25:10.901 We leveraged the last servicing mission's flight design, 425 00:25:10.901 --> 00:25:13.133 so that we can do this particular mission 426 00:25:13.133 --> 00:25:14.167 in a short amount of time. 427 00:25:14.167 --> 00:25:16.200 We had planned a flight in October 428 00:25:16.200 --> 00:25:18.934 that would have been about an 8-month template, 429 00:25:18.934 --> 00:25:21.167 and we were ready to fly in October 430 00:25:21.167 --> 00:25:24.367 from a flight design and team readiness point of view. 431 00:25:24.367 --> 00:25:26.167 All we had to do was get our vehicles up to speed, 432 00:25:26.167 --> 00:25:27.934 and we have done that. 433 00:25:27.934 --> 00:25:30.367 We have talked to our workforce, 434 00:25:30.367 --> 00:25:33.367 both from the management down to the people on the floor. 435 00:25:33.367 --> 00:25:34.834 We have emphasized to them, 436 00:25:34.834 --> 00:25:36.367 not only the safety aspects of what 437 00:25:36.367 --> 00:25:38.834 we are trying to accomplish in the Space Shuttle program, 438 00:25:38.834 --> 00:25:42.100 but we've talked to them about their workload. 439 00:25:42.100 --> 00:25:45.834 How do they feel about what they have done? 440 00:25:45.834 --> 00:25:47.033 Do they feel good about it? 441 00:25:47.033 --> 00:25:49.934 Do they feel like we're rushed? 442 00:25:49.934 --> 00:25:52.434 And to a majority of those folks, 443 00:25:52.434 --> 00:25:55.033 they have come back and told us that they are excited 444 00:25:55.033 --> 00:25:56.434 about what they have done. 445 00:25:56.434 --> 00:25:58.901 They're very proud of what inspections 446 00:25:58.901 --> 00:26:01.067 that they have performed on the vehicle, 447 00:26:01.067 --> 00:26:03.834 and their intent is to have the safest vehicle 448 00:26:03.834 --> 00:26:08.901 that a crew member could fly, and I believe that is true. 449 00:26:08.901 --> 00:26:10.734 The teams in Johnson, and Goddard and here 450 00:26:10.734 --> 00:26:13.534 at the Kennedy Space Center are ready to fly. 451 00:26:13.534 --> 00:26:14.868 They're rested. 452 00:26:14.868 --> 00:26:16.434 They're not pressed. 453 00:26:16.434 --> 00:26:21.467 We do plan to launch on Thursday evening. 454 00:26:21.467 --> 00:26:23.400 -Thank you. Dave? 455 00:26:23.400 --> 00:26:26.634 -As Ron said, it is really good to be here again. 456 00:26:26.634 --> 00:26:29.400 Looking forward to a lot of hard work 457 00:26:29.400 --> 00:26:31.667 culminating in a good launch on Thursday evening. 458 00:26:31.667 --> 00:26:34.200 We have been through a very careful process 459 00:26:34.200 --> 00:26:36.133 of trying to disposition everything that 460 00:26:36.133 --> 00:26:41.534 we've found very carefully and thoroughly. 461 00:26:41.534 --> 00:26:45.901 Over the past months, this workforce, here at Kennedy, 462 00:26:45.901 --> 00:26:48.534 has worked very hard at making sure 463 00:26:48.534 --> 00:26:50.534 that we look at everything very carefully, 464 00:26:50.534 --> 00:26:53.901 and I think we found some things that needed to be fixed, 465 00:26:53.901 --> 00:26:57.200 and we obviously have a much better vehicle 466 00:26:57.200 --> 00:27:00.200 as a result of that. 467 00:27:00.200 --> 00:27:02.734 We did take the time to do this right, 468 00:27:02.734 --> 00:27:06.000 and to go look in the areas that we needed to go look, 469 00:27:06.000 --> 00:27:10.701 and I'm very confident that we have a good vehicle. 470 00:27:10.701 --> 00:27:14.033 As Ron said, we are ready to go fly Thursday night. 471 00:27:14.033 --> 00:27:16.100 We did pick up the count last night. 472 00:27:16.100 --> 00:27:18.767 Got through a good -- Got the aft doors on, 473 00:27:18.767 --> 00:27:21.501 and got through a good aft confidence check, 474 00:27:21.501 --> 00:27:23.133 which gives us a good feeling 475 00:27:23.133 --> 00:27:25.834 that everything was done properly. 476 00:27:25.834 --> 00:27:29.234 And we'll be picking up with PRSD load tonight, 477 00:27:29.234 --> 00:27:31.834 and continuing on with a fairly standard countdown, 478 00:27:31.834 --> 00:27:36.601 looking forward to a great launch on Thursday night. 479 00:27:36.601 --> 00:27:38.167 -Thanks, Dave. Weather? 480 00:27:38.167 --> 00:27:39.267 -Thanks, Lisa. 481 00:27:39.267 --> 00:27:40.934 Good afternoon, ladies and gentlemen. 482 00:27:40.934 --> 00:27:42.934 I suppose it would be a real bummer 483 00:27:42.934 --> 00:27:45.501 if Mother Nature threw us another delay 484 00:27:45.501 --> 00:27:47.033 after all the hard work the launch team 485 00:27:47.033 --> 00:27:48.601 has done to get us here. 486 00:27:48.601 --> 00:27:50.734 Fortunately, it looks like chances are pretty good 487 00:27:50.734 --> 00:27:52.467 that's not going to happen. 488 00:27:52.467 --> 00:27:54.601 After a noticeable cold front passing this morning, 489 00:27:54.601 --> 00:27:56.501 high pressure will continue to move into the area 490 00:27:56.501 --> 00:27:57.734 over the next couple of days, 491 00:27:57.734 --> 00:27:59.534 and it will actually start to feel a little bit 492 00:27:59.534 --> 00:28:01.667 like Christmas around here. 493 00:28:01.667 --> 00:28:05.000 Skies will be partly cloudy and temperatures much cooler, 494 00:28:05.000 --> 00:28:07.100 but with little threat of rain 495 00:28:07.100 --> 00:28:10.400 until possibility into late Saturday. 496 00:28:10.400 --> 00:28:12.067 For tanking on Thursday afternoon, 497 00:28:12.067 --> 00:28:15.634 scattered clouds and breezy with northwest winds at 18, 498 00:28:15.634 --> 00:28:17.634 peaking at 26 knots. 499 00:28:17.634 --> 00:28:20.801 Zero percent chance that weather will prohibit tanking. 500 00:28:20.801 --> 00:28:22.567 For launch time, Thursday evening, 501 00:28:22.567 --> 00:28:26.200 scattered clouds at 3,000 and 25,000 feet, 502 00:28:26.200 --> 00:28:29.200 with a chance for a broken deck at 3,000 feet 503 00:28:29.200 --> 00:28:32.868 that would violate RTLS or range optics criteria, 504 00:28:32.868 --> 00:28:36.200 but with good visibility northwest winds at 12, 505 00:28:36.200 --> 00:28:40.200 peaking at 20, and temperature a brisk 52 degrees Fahrenheit, 506 00:28:40.200 --> 00:28:42.934 so overall only a 20 percent chance 507 00:28:42.934 --> 00:28:47.200 that KSC weather would prohibit launch on Thursday. 508 00:28:47.200 --> 00:28:50.734 For SRB recovery, broken clouds at 4,000 feet 509 00:28:50.734 --> 00:28:53.601 and good visibility out over the ocean, 510 00:28:53.601 --> 00:28:57.734 gusty winds northwest at 18, peaking at 24 knots. 511 00:28:57.734 --> 00:29:00.300 Those winds will kick up the seas to about 5 to 7 feet, 512 00:29:00.300 --> 00:29:04.868 but still no real concerns for recovering the SRBs. 513 00:29:04.868 --> 00:29:08.067 Should we get into a 24-hour delay for Friday, 514 00:29:08.067 --> 00:29:09.801 little change from Thursday. 515 00:29:09.801 --> 00:29:13.067 Still a chance for a broken cloud deck at 3,000 feet, 516 00:29:13.067 --> 00:29:15.501 and winds will turn northeasterly at 8, 517 00:29:15.501 --> 00:29:18.868 peaking at 15 knots. 518 00:29:18.868 --> 00:29:20.400 Still only 20 percent chance 519 00:29:20.400 --> 00:29:24.300 that weather would prohibit launch on Friday. 520 00:29:24.300 --> 00:29:26.667 Forty-eight-hour delay into Saturday, 521 00:29:26.667 --> 00:29:28.467 we'd bump up the probability of weather 522 00:29:28.467 --> 00:29:31.133 prohibiting launch to 30 percent. 523 00:29:31.133 --> 00:29:32.467 That's because the winds are going to turn out 524 00:29:32.467 --> 00:29:35.767 at southeast at 8 knots, peaking at 12, 525 00:29:35.767 --> 00:29:38.000 which will bring the temperatures up a little bit, 526 00:29:38.000 --> 00:29:40.167 and a chance for some coastal showers around the Cape, 527 00:29:40.167 --> 00:29:42.067 and that's why we bump up the probability 528 00:29:42.067 --> 00:29:44.801 just another 10 percent. 529 00:29:44.801 --> 00:29:48.200 For abort once around basis, Edwards and White Sands 530 00:29:48.200 --> 00:29:50.300 look really good Thursday and Friday 531 00:29:50.300 --> 00:29:52.300 with a few clouds and light winds. 532 00:29:52.300 --> 00:29:53.901 On Saturday, the winds at Edwards 533 00:29:53.901 --> 00:29:55.634 will kick up to 12 knots, 534 00:29:55.634 --> 00:29:58.267 peaking at 22 knots from the northeast, 535 00:29:58.267 --> 00:30:00.834 but that's right down runway 04. 536 00:30:00.834 --> 00:30:03.167 White Sands will see a few clouds and winds southwest 537 00:30:03.167 --> 00:30:06.267 at 10, peaking at 20 knots, on Saturday. 538 00:30:06.267 --> 00:30:09.167 For the TAL sites, Ben Guerir will have winds from 0, 539 00:30:09.167 --> 00:30:11.234 5. 0 at 12 knots. 540 00:30:11.234 --> 00:30:14.701 peaking at 20 knots on Thursday and Friday. 541 00:30:14.701 --> 00:30:18.200 That potentially puts them out of crosswind limits. 542 00:30:18.200 --> 00:30:21.234 The winds then ease up a bit on Saturday, 543 00:30:21.234 --> 00:30:22.634 but throughout the period Thursday, 544 00:30:22.634 --> 00:30:25.801 Friday and Saturday, Banjul looks just fine, 545 00:30:25.801 --> 00:30:27.501 so all in all, the launch weather team 546 00:30:27.501 --> 00:30:30.100 is looking forward to a beautiful show on Thursday. 547 00:30:30.100 --> 00:30:31.300 -Thank you. 548 00:30:31.300 --> 00:30:32.534 We'll start with questions here at KSC. 549 00:30:32.534 --> 00:30:35.701 Please identify yourself by name and affiliation. 550 00:30:35.701 --> 00:30:37.601 Craig Covault. 551 00:30:37.601 --> 00:30:39.767 -Craig Covault, "Aviation Week," 552 00:30:39.767 --> 00:30:42.100 Ron, Terra launch is still on the 16th, 553 00:30:42.100 --> 00:30:45.000 and what has to be done 554 00:30:45.000 --> 00:30:47.734 and just explain how that will play out 555 00:30:47.734 --> 00:30:49.167 if there's any risk at all Tidras 556 00:30:49.167 --> 00:30:51.801 could be still hung up with Terra. 557 00:30:51.801 --> 00:30:55.534 -See, Terra launch is going to be on Thursday morning 558 00:30:55.534 --> 00:31:00.200 about 10:30 Pacific Time, 1:30 or so Eastern Time. 559 00:31:00.200 --> 00:31:02.000 Our launch is at 9:18 in the evening. 560 00:31:02.000 --> 00:31:04.434 We've asked our Tidras folks whether they can support both. 561 00:31:04.434 --> 00:31:06.367 They said they can. 562 00:31:06.367 --> 00:31:10.234 I don't have the details, Craig, on exactly what their time line. 563 00:31:10.234 --> 00:31:11.601 We just asked them that simple question, 564 00:31:11.601 --> 00:31:13.734 do they have the margin to reconfigure and support both? 565 00:31:13.734 --> 00:31:16.467 And they do. 566 00:31:16.467 --> 00:31:20.901 -Todd Halvorson. -Todd Halvorson, space.com, 567 00:31:20.901 --> 00:31:24.167 I was wondering if you could elaborate 568 00:31:24.167 --> 00:31:26.200 on whatever engine issues 569 00:31:26.200 --> 00:31:30.000 there might have been to disposition at the MMT today 570 00:31:30.000 --> 00:31:32.167 and whether there are any other problems 571 00:31:32.167 --> 00:31:35.400 being worked at the pad right now. 572 00:31:35.400 --> 00:31:36.501 -Let's see. 573 00:31:36.501 --> 00:31:37.834 Dave can talk about whatever problems 574 00:31:37.834 --> 00:31:39.067 he may be working at the pad. 575 00:31:39.067 --> 00:31:41.200 Engine issues were just cleanup issues 576 00:31:41.200 --> 00:31:42.667 from our flight readiness review. 577 00:31:42.667 --> 00:31:44.601 We had a couple of open items that they just needed 578 00:31:44.601 --> 00:31:46.834 to clean up, nothing significant, 579 00:31:46.834 --> 00:31:49.801 and we just talked about those, pressed on. 580 00:31:49.801 --> 00:31:51.400 They were nothing major. 581 00:31:53.567 --> 00:31:57.534 -Okay, Dan Billow and then Bill Harwood. 582 00:31:57.534 --> 00:32:02.033 -I'm Dan Billow from WESH-TV for Ron Dittemore. 583 00:32:02.033 --> 00:32:04.534 You mentioned that the workforce has been asked 584 00:32:04.534 --> 00:32:07.868 whether they feel rushed and pressured and said 585 00:32:07.868 --> 00:32:12.000 that they feel excited and proud about the work that they do, 586 00:32:12.000 --> 00:32:15.767 but do they indeed feel rushed and pressured? 587 00:32:15.767 --> 00:32:18.501 -Well, see, I'm going to defer to Dave 588 00:32:18.501 --> 00:32:21.667 to answer that for Kennedy because he lives and works, 589 00:32:21.667 --> 00:32:23.467 breathes and sees them every day. 590 00:32:23.467 --> 00:32:24.834 Let me talk a little bit about more than 591 00:32:24.834 --> 00:32:26.667 the workforce here at Kennedy 592 00:32:26.667 --> 00:32:28.667 because when you start talking about a shuttle launch, 593 00:32:28.667 --> 00:32:29.834 you're talking about a lot of people. 594 00:32:29.834 --> 00:32:31.167 You're talking about folks 595 00:32:31.167 --> 00:32:32.667 at Goddard that support this flight, 596 00:32:32.667 --> 00:32:34.934 and you're talking about folks at the Johnson Space Center 597 00:32:34.934 --> 00:32:36.901 and other areas around the country, 598 00:32:36.901 --> 00:32:39.701 and we just don't talk to Kennedy Space Center employees. 599 00:32:39.701 --> 00:32:41.834 We talk to each one of them. How do they feel? 600 00:32:41.834 --> 00:32:47.000 Because they all have additional work that they've had to perform 601 00:32:47.000 --> 00:32:49.801 over the last couple of months to get ready. 602 00:32:49.801 --> 00:32:52.400 Johnson and Goddard are ready to go. 603 00:32:52.400 --> 00:32:53.734 They are excited. 604 00:32:53.734 --> 00:32:57.100 In fact, they would prefer not to do any more delays 605 00:32:57.100 --> 00:33:00.100 as the rest of us would. 606 00:33:00.100 --> 00:33:03.501 There is no pressure to launch in December, none at all. 607 00:33:03.501 --> 00:33:05.467 We can just as well go in January. 608 00:33:05.467 --> 00:33:08.467 There's nothing that says we have to go in December. 609 00:33:08.467 --> 00:33:13.634 When we look at that, we look at the training of the team, 610 00:33:13.634 --> 00:33:14.868 the efficiency of the team, 611 00:33:14.868 --> 00:33:16.534 and we have found that our teams, 612 00:33:16.534 --> 00:33:18.667 both at Kennedy, Johnson and Goddard, 613 00:33:18.667 --> 00:33:21.033 are at their peak training periods, 614 00:33:21.033 --> 00:33:23.033 and they are ready to go, 615 00:33:23.033 --> 00:33:25.334 and because the vehicle is ready, 616 00:33:25.334 --> 00:33:29.734 we think the right thing to do is launch this week. 617 00:33:29.734 --> 00:33:32.734 If we were to delay further like in January, 618 00:33:32.734 --> 00:33:35.934 we would actually have to back out of certain activities 619 00:33:35.934 --> 00:33:38.200 that we have already performed on the vehicle, 620 00:33:38.200 --> 00:33:40.934 and then we also believe our teams would suffer some 621 00:33:40.934 --> 00:33:43.400 because they would have a 3-week layoff, 622 00:33:43.400 --> 00:33:44.701 and then we'd have to bring them back up 623 00:33:44.701 --> 00:33:48.000 into their peak training period, 624 00:33:48.000 --> 00:33:51.000 and so there is some loss you suffer by going into January, 625 00:33:51.000 --> 00:33:54.400 so it's just not a casual decision that says, 626 00:33:54.400 --> 00:33:57.300 "Let's go into January because there's no rush in December." 627 00:33:57.300 --> 00:33:59.067 There is no rush in December, 628 00:33:59.067 --> 00:34:01.701 but when you are ready to go, and your teams are ready, 629 00:34:01.701 --> 00:34:03.300 then you ought to take the opportunity to launch, 630 00:34:03.300 --> 00:34:06.901 and that's exactly what we're going to do. 631 00:34:06.901 --> 00:34:10.300 -I'll address the workforce here at Kennedy. 632 00:34:10.300 --> 00:34:12.167 I've spent a lot of time in the last couple of weeks 633 00:34:12.167 --> 00:34:15.701 out talking to folks about how they feel 634 00:34:15.701 --> 00:34:17.467 and how they're doing, and I say, "A couple of weeks," 635 00:34:17.467 --> 00:34:19.000 really for longer than that 636 00:34:19.000 --> 00:34:21.801 but specifically the last couple of weeks, 637 00:34:21.801 --> 00:34:25.400 and this team is anxious to go fly. 638 00:34:25.400 --> 00:34:27.934 I don't want to say that anxious in a negative way at all. 639 00:34:27.934 --> 00:34:29.567 I really think they're just excited 640 00:34:29.567 --> 00:34:32.100 about getting back to flying again. 641 00:34:32.100 --> 00:34:35.100 Everybody here has worked very diligently 642 00:34:35.100 --> 00:34:36.834 to try to get this vehicle ready to go fly, 643 00:34:36.834 --> 00:34:40.234 and we all think it's a very solid vehicle 644 00:34:40.234 --> 00:34:42.534 and ready to go do that, 645 00:34:42.534 --> 00:34:47.534 and folks are ready to perform those tasks. 646 00:34:47.534 --> 00:34:49.968 Getting back to the other question that Todd asked 647 00:34:49.968 --> 00:34:52.200 about what kind of issues we're dealing with 648 00:34:52.200 --> 00:34:55.868 in this specific launch countdown, 649 00:34:55.868 --> 00:34:58.000 we have had a couple of things that we've been working, 650 00:34:58.000 --> 00:35:01.601 but I wouldn't call them -- Even though they're nonstandard, 651 00:35:01.601 --> 00:35:04.000 I wouldn't call them, you know, out of family. 652 00:35:04.000 --> 00:35:05.567 We had a couple of valves in the MLP 653 00:35:05.567 --> 00:35:09.400 that we've had to change out in the last couple days, 654 00:35:09.400 --> 00:35:12.567 but those have been replaced, and retest is complete, 655 00:35:12.567 --> 00:35:14.300 so we've got that behind us now. 656 00:35:14.300 --> 00:35:16.968 We really aren't working any kind of problems 657 00:35:16.968 --> 00:35:19.100 that pose any threat at this point. 658 00:35:19.100 --> 00:35:22.033 We think we've got a good, clean vehicle 659 00:35:22.033 --> 00:35:26.367 and clean ground-support system to go fly. 660 00:35:26.367 --> 00:35:27.467 -Okay. 661 00:35:27.467 --> 00:35:28.234 We'll take one from Bill Harwood. 662 00:35:28.234 --> 00:35:29.701 Then we'll come back. 663 00:35:29.701 --> 00:35:31.667 You have a follow-up, Dan? What is it? 664 00:35:31.667 --> 00:35:34.667 -Yeah, it's fairly closely related if I may 665 00:35:34.667 --> 00:35:39.167 for Ron Dittemore again, and this is on, again, 666 00:35:39.167 --> 00:35:42.167 the pressure or nonpressure to launch 667 00:35:42.167 --> 00:35:44.367 because we're for an organization 668 00:35:44.367 --> 00:35:46.567 that is not under pressure to launch, 669 00:35:46.567 --> 00:35:52.133 you're making or willing to make some fairly unusual 670 00:35:52.133 --> 00:35:54.734 or even unprecedented changes in your philosophy 671 00:35:54.734 --> 00:35:58.501 in order to get this thing done before January 1st. 672 00:35:58.501 --> 00:36:00.434 One would be as Steve Altman has told us 673 00:36:00.434 --> 00:36:03.267 this morning the possibility of three launch countdown 674 00:36:03.267 --> 00:36:05.467 attempts in a row on consecutive days. 675 00:36:05.467 --> 00:36:08.701 The other would be the possibility of shortening 676 00:36:08.701 --> 00:36:11.634 and sacrificing parts of this mission 677 00:36:11.634 --> 00:36:14.234 in order to get down before January 1. 678 00:36:14.234 --> 00:36:17.601 You know, a day in space is -- 679 00:36:17.601 --> 00:36:21.367 I'm not trying to tell you, not trying to lecture to you. 680 00:36:21.367 --> 00:36:24.567 As you know, a day in space is a very valuable thing, 681 00:36:24.567 --> 00:36:27.834 and you're willing to potentially give it up 682 00:36:27.834 --> 00:36:29.868 in order to get back by January 1, 683 00:36:29.868 --> 00:36:33.267 so if all that is the case, 684 00:36:33.267 --> 00:36:35.000 how can you say that there's no pressure 685 00:36:35.000 --> 00:36:36.434 or that you're not pressuring yourselves 686 00:36:36.434 --> 00:36:38.334 to launch before January 1? 687 00:36:38.334 --> 00:36:40.634 You're doing things that indicate 688 00:36:40.634 --> 00:36:44.133 that you are racing the calendar. 689 00:36:44.133 --> 00:36:45.434 -So you said a lot there. 690 00:36:45.434 --> 00:36:47.033 What was your question? 691 00:36:49.167 --> 00:36:51.400 -The question is what I said at the end. 692 00:36:51.400 --> 00:36:56.000 If there is no pressure to launch 693 00:36:56.000 --> 00:36:58.133 and get back by January 1, 694 00:36:58.133 --> 00:37:01.167 then why would you do things or be willing to do things 695 00:37:01.167 --> 00:37:04.000 that indicate that you are indeed racing the calendar? 696 00:37:04.000 --> 00:37:05.467 -Let's go back to the formulation 697 00:37:05.467 --> 00:37:08.968 of the mission to begin with. 698 00:37:08.968 --> 00:37:14.434 There's a desire to go to HST to replace... 699 00:37:14.434 --> 00:37:16.968 That is the fundamental reason that we're going to visit 700 00:37:16.968 --> 00:37:20.067 this particular spacecraft so that we can replace the gyros 701 00:37:20.067 --> 00:37:21.767 and get it back into working condition. 702 00:37:21.767 --> 00:37:25.400 As you know, they've had another failure of a gyro, 703 00:37:25.400 --> 00:37:29.167 and it's basically in a zero-gyro Sun point mode, 704 00:37:29.167 --> 00:37:31.300 and it's waiting for us to come visit. 705 00:37:33.501 --> 00:37:36.534 When we first planned the mission, 706 00:37:36.534 --> 00:37:39.734 that was the highest priority event. 707 00:37:39.734 --> 00:37:42.033 As we looked at the opportunities 708 00:37:42.033 --> 00:37:44.000 once we were there, we said, "Now since we're there, 709 00:37:44.000 --> 00:37:46.367 and we have the consumables available, 710 00:37:46.367 --> 00:37:49.767 can we do some tasks that would actually get ahead 711 00:37:49.767 --> 00:37:52.000 for the next servicing mission 712 00:37:52.000 --> 00:37:54.567 not this time but the next one following?" 713 00:37:54.567 --> 00:37:58.300 and the folks put together actually two EVAs, 714 00:37:58.300 --> 00:37:59.334 the third and the fourth 715 00:37:59.334 --> 00:38:01.934 that are predominately get-ahead tasks 716 00:38:01.934 --> 00:38:05.300 for the follow-on servicing mission. 717 00:38:05.300 --> 00:38:09.968 Now it's Goddard's position that they need two mandatory 718 00:38:09.968 --> 00:38:13.634 EVAs and a third one for some flexibility 719 00:38:13.634 --> 00:38:16.667 in case they need to -- task took a little longer. 720 00:38:16.667 --> 00:38:19.901 They can fault over into the third EVA and finish the task. 721 00:38:19.901 --> 00:38:22.167 Their position is they need three. 722 00:38:22.167 --> 00:38:26.667 We put in a fourth EVA basically to do some get-ahead tasks. 723 00:38:26.667 --> 00:38:29.100 Now is that mandatory? 724 00:38:29.100 --> 00:38:31.167 Absolutely not, and Goddard has told us 725 00:38:31.167 --> 00:38:33.601 as they're the customer they would accept, 726 00:38:33.601 --> 00:38:37.534 they would desire to launch and only do the mandatory items 727 00:38:37.534 --> 00:38:40.901 and protect for three EVAs as their minimum. 728 00:38:40.901 --> 00:38:42.868 We believe that's an acceptable position. 729 00:38:42.868 --> 00:38:46.200 There's no reason that says we have to do the get-ahead tasks, 730 00:38:46.200 --> 00:38:47.834 so again given that, 731 00:38:47.834 --> 00:38:50.000 there's no real requirement to do four EVAs, 732 00:38:50.000 --> 00:38:52.501 and we built four EVAs on there because we wanted to make 733 00:38:52.501 --> 00:38:55.868 the most efficient use of our time on orbit. 734 00:38:55.868 --> 00:38:57.767 Then we have to go back and look at what I just told you, 735 00:38:57.767 --> 00:39:00.367 and that is, where are we in the processing of the vehicle? 736 00:39:00.367 --> 00:39:03.767 Where are we in the training of the teams, and are they ready? 737 00:39:03.767 --> 00:39:05.601 And since they are ready, and we believe 738 00:39:05.601 --> 00:39:08.234 that the mandatory items of the mission can be protected 739 00:39:08.234 --> 00:39:10.968 and can be completed with margin, 740 00:39:10.968 --> 00:39:12.801 then we think we have opportunities to launch 741 00:39:12.801 --> 00:39:16.267 on the 16th and the 17th, and even on the 18th 742 00:39:16.267 --> 00:39:19.267 is when we would drop off possibly the fourth EVA, 743 00:39:19.267 --> 00:39:22.467 and we're still looking at that. 744 00:39:22.467 --> 00:39:24.501 -Two questions, 745 00:39:24.501 --> 00:39:26.434 and I don't remember the numbers. 746 00:39:26.434 --> 00:39:28.767 It OI-26-B that's on board this orbit, or is it -- 747 00:39:28.767 --> 00:39:30.033 -That's right. OI-26-B is -- 748 00:39:30.033 --> 00:39:31.334 -Is that Y2K-compliant? 749 00:39:31.334 --> 00:39:32.701 In other words if you did roll over into the next year, 750 00:39:32.701 --> 00:39:35.167 do you have to have different set of flight software? 751 00:39:35.167 --> 00:39:36.567 -No, no. 752 00:39:36.567 --> 00:39:39.868 The flight software itself has always been Y2K-compliant. 753 00:39:39.868 --> 00:39:44.334 What we have done to protect ourselves for Y2K 754 00:39:44.334 --> 00:39:45.901 is to ground tools 755 00:39:45.901 --> 00:39:49.767 that build software and check it out and certify it. 756 00:39:49.767 --> 00:39:52.033 We made a decision back in September 757 00:39:52.033 --> 00:39:58.367 when we felt perhaps we might be pressed to roll over to January 758 00:39:58.367 --> 00:40:02.067 that we asked our, not the flight software, 759 00:40:02.067 --> 00:40:03.634 the guys that do the ground software 760 00:40:03.634 --> 00:40:06.000 and the mission control center software 761 00:40:06.000 --> 00:40:08.000 to go certify their software 762 00:40:08.000 --> 00:40:10.334 so that if we did go into January, 763 00:40:10.334 --> 00:40:13.000 there would be no Y2K problems, so the flight software, 764 00:40:13.000 --> 00:40:15.934 there were no changes to that to go into January. 765 00:40:15.934 --> 00:40:20.167 The ground tools were certified to be Y2K-compliant 766 00:40:20.167 --> 00:40:21.901 from September to now, 767 00:40:21.901 --> 00:40:24.000 and so there is no problem of going into January. 768 00:40:24.000 --> 00:40:25.868 -Oh, I see. ...the stuff on board 769 00:40:25.868 --> 00:40:27.634 the orbiter itself this particular increment 770 00:40:27.634 --> 00:40:29.634 was okay if you roll over that same set. 771 00:40:29.634 --> 00:40:30.868 -That's correct. 772 00:40:30.868 --> 00:40:33.400 There are no Y2K concerns with OI-26 software 773 00:40:33.400 --> 00:40:35.801 or OI-27 or any flight software. 774 00:40:35.801 --> 00:40:38.834 -And just to follow up on Dan's and other questions 775 00:40:38.834 --> 00:40:42.634 on the push to get off here in December, 776 00:40:42.634 --> 00:40:44.901 I know obviously with Hubble out of action, 777 00:40:44.901 --> 00:40:47.801 there's certainly some pressure in that context to get up there 778 00:40:47.801 --> 00:40:49.334 as soon as you can to get Hubble back in action. 779 00:40:49.334 --> 00:40:50.634 Everybody understands that. 780 00:40:50.634 --> 00:40:52.033 I know Dave Cronin is here. I was just wondering. 781 00:40:52.033 --> 00:40:53.400 I know he's not on the panel, but if perhaps 782 00:40:53.400 --> 00:40:55.000 he could just address Hubble, 783 00:40:55.000 --> 00:40:56.767 the project's desire to get the mission up 784 00:40:56.767 --> 00:41:01.534 and get Hubble serviced if we could, please. 785 00:41:01.534 --> 00:41:03.434 -We'll bring the mic over to you, Dave. 786 00:41:06.601 --> 00:41:08.868 -Well, it's absolutely true that we really want to get up there 787 00:41:08.868 --> 00:41:11.501 and get Hubble serviced to get it back online doing science, 788 00:41:11.501 --> 00:41:14.968 and it's also absolutely true that the fourth EVA activities 789 00:41:14.968 --> 00:41:18.367 were very low priority relative to everything else we're doing. 790 00:41:18.367 --> 00:41:21.133 So we as a project have no problems whatsoever 791 00:41:21.133 --> 00:41:22.334 deferring that work 792 00:41:22.334 --> 00:41:26.334 until SM-3B if we absolutely had to. 793 00:41:26.334 --> 00:41:29.667 We don't anyone to feel pressure because of this. 794 00:41:29.667 --> 00:41:32.100 Hubble will still be there waiting for us in January 795 00:41:32.100 --> 00:41:33.467 if we have to defer to January. 796 00:41:33.467 --> 00:41:35.167 We certainly don't want to put anyone at risk, 797 00:41:35.167 --> 00:41:37.033 the system at risk at all, 798 00:41:37.033 --> 00:41:38.567 but given the choice of going now 799 00:41:38.567 --> 00:41:42.868 and getting Hubble back online is the perhaps almost important 800 00:41:42.868 --> 00:41:45.133 and valuable and productive scientific tool 801 00:41:45.133 --> 00:41:50.367 that I'm aware of in this many-decade period, 802 00:41:50.367 --> 00:41:52.033 getting that valuable tool back up 803 00:41:52.033 --> 00:41:54.434 and running is a high priority for us, 804 00:41:54.434 --> 00:41:57.267 and we would like to do that. 805 00:41:57.267 --> 00:42:00.400 -And just a reminder, we do have a Hubble briefing tomorrow 806 00:42:00.400 --> 00:42:02.567 at 10 a.m. in this room. 807 00:42:02.567 --> 00:42:06.033 I believe Mark Caro had his hand up. 808 00:42:06.033 --> 00:42:07.801 -I'm Mark Caro from the "Houston Chronicle." 809 00:42:07.801 --> 00:42:09.467 I had a question and a follow, 810 00:42:09.467 --> 00:42:11.767 and the first one is for Ron Dittemore 811 00:42:11.767 --> 00:42:15.167 in regards the 100 miles of wiring 812 00:42:15.167 --> 00:42:17.968 you mentioned early in your comments. 813 00:42:17.968 --> 00:42:19.934 Could you just summarize 814 00:42:19.934 --> 00:42:23.367 what proportion of shuttle wiring that is 815 00:42:23.367 --> 00:42:26.234 and the areas you focused on and the areas 816 00:42:26.234 --> 00:42:32.367 that maybe you didn't and why and the rationale for that? 817 00:42:32.367 --> 00:42:33.467 -Well, let's see. 818 00:42:33.467 --> 00:42:34.868 I don't know the exact percentage, 819 00:42:34.868 --> 00:42:38.934 but let me say it's the majority, okay, if that helps. 820 00:42:38.934 --> 00:42:40.734 We focused on areas 821 00:42:40.734 --> 00:42:44.701 that where workers worked around those general areas 822 00:42:44.701 --> 00:42:47.200 a lot where there could be collateral damage 823 00:42:47.200 --> 00:42:49.167 where people were going in and out of the vehicles, 824 00:42:49.167 --> 00:42:51.767 where we were making modifications, 825 00:42:51.767 --> 00:42:53.334 and because of the modifications 826 00:42:53.334 --> 00:42:56.367 and just the fact that we had people working in that area, 827 00:42:56.367 --> 00:42:58.534 we could get collateral damage. 828 00:42:58.534 --> 00:43:02.467 We looked at the parts of the forward module. 829 00:43:02.467 --> 00:43:05.200 We looked in the crew cockpit. 830 00:43:05.200 --> 00:43:08.400 We did extensive inspections of the midbody 831 00:43:08.400 --> 00:43:10.567 because that's where we do a lot of our reconfiguration 832 00:43:10.567 --> 00:43:12.000 from flight to flight when we have payloads 833 00:43:12.000 --> 00:43:13.300 go in and payloads go out. 834 00:43:13.300 --> 00:43:16.234 We put new cables in and put new power connections. 835 00:43:16.234 --> 00:43:19.567 All those types of thing go in, so that was an extensive review, 836 00:43:19.567 --> 00:43:22.200 and then we went and looked at the aft. 837 00:43:22.200 --> 00:43:26.934 Now the aft was a little harder to do when we were in the OPF. 838 00:43:26.934 --> 00:43:28.734 Because of the way the platforms are situated, 839 00:43:28.734 --> 00:43:31.667 you just can't see all the wires as well as you can 840 00:43:31.667 --> 00:43:33.534 as when you are in the vertical. 841 00:43:33.534 --> 00:43:35.834 We knew that, and so we fully expected 842 00:43:35.834 --> 00:43:37.100 that when we went out to the pad 843 00:43:37.100 --> 00:43:38.968 and put in the platforms that you use 844 00:43:38.968 --> 00:43:40.934 when you're out in the vertical that we would be able 845 00:43:40.934 --> 00:43:44.133 to do further wire inspections in the aft, 846 00:43:44.133 --> 00:43:46.601 and that's exactly the way it came to pass. 847 00:43:46.601 --> 00:43:47.868 When we did those wire inspections, 848 00:43:47.868 --> 00:43:53.234 we found more damage, and we repaired it. 849 00:43:53.234 --> 00:43:58.634 -I had a follow-on question, and I realize that a little bit, 850 00:43:58.634 --> 00:44:01.400 some of this, maybe a lot of it is kind of beyond your control 851 00:44:01.400 --> 00:44:04.634 as to what kinds of numbers of shuttle missions 852 00:44:04.634 --> 00:44:09.334 you can fly next year, but just on a general basis, 853 00:44:09.334 --> 00:44:12.100 can you sort of jump-start from three 854 00:44:12.100 --> 00:44:14.934 to whatever you might fly next year, 855 00:44:14.934 --> 00:44:17.801 whatever number higher than that you might fly next year 856 00:44:17.801 --> 00:44:19.234 without a lot of difficulty? 857 00:44:19.234 --> 00:44:21.534 Is there anything looming out there 858 00:44:21.534 --> 00:44:26.968 that you really have to address before you can take that on? 859 00:44:26.968 --> 00:44:28.934 -It certainly is true that our flight rate has been lower 860 00:44:28.934 --> 00:44:30.601 than what we'd like it to be. 861 00:44:30.601 --> 00:44:32.567 We're fully capable of doing seven, eight, 862 00:44:32.567 --> 00:44:35.367 nine missions a year. 863 00:44:35.367 --> 00:44:37.234 That's what we had been doing, 864 00:44:37.234 --> 00:44:40.601 and the reason our flight rate has been low is really 865 00:44:40.601 --> 00:44:42.267 because the customers that we had planned 866 00:44:42.267 --> 00:44:44.601 to fly weren't ready to fly. 867 00:44:44.601 --> 00:44:48.000 Our space station program has been delayed, 868 00:44:48.000 --> 00:44:50.868 and so we're not ready to move forward on that 869 00:44:50.868 --> 00:44:52.501 and those particular missions. 870 00:44:52.501 --> 00:44:57.467 Chandra itself was delayed, and we finally launched in July, 871 00:44:57.467 --> 00:44:59.033 but it was delayed for some period of time, 872 00:44:59.033 --> 00:45:01.767 so it really has upset the apple cart on our manifest 873 00:45:01.767 --> 00:45:04.734 because of our customers not being ready. 874 00:45:04.734 --> 00:45:07.734 Then we added to it by looking at our vehicles 875 00:45:07.734 --> 00:45:12.734 and finding some deficiencies that we needed to repair 876 00:45:12.734 --> 00:45:16.534 and to fix and to correct. 877 00:45:16.534 --> 00:45:20.067 As we start looking ahead, we think this year 878 00:45:20.067 --> 00:45:23.868 maybe six missions in the calendar year, 879 00:45:23.868 --> 00:45:25.801 but again, a large part of that 880 00:45:25.801 --> 00:45:28.400 is based upon our customers' readiness. 881 00:45:28.400 --> 00:45:29.634 We'll fly HST. 882 00:45:29.634 --> 00:45:33.834 We'll fly SRTM in probably late January, 883 00:45:33.834 --> 00:45:37.334 maybe early February depending on what happens at HST, 884 00:45:37.334 --> 00:45:40.167 and then the bulk of the manifest 885 00:45:40.167 --> 00:45:42.534 is space station missions, 886 00:45:42.534 --> 00:45:45.567 and as you know, there's a lot of work going on with 887 00:45:45.567 --> 00:45:48.033 when we're going to launch the service module, 888 00:45:48.033 --> 00:45:50.234 and that has a lot to do with what we do not 889 00:45:50.234 --> 00:45:52.167 only in the content of our shuttle missions 890 00:45:52.167 --> 00:45:54.601 but when we go fly them. 891 00:45:54.601 --> 00:45:56.901 As far as the workforce goes, I think we're fully capable 892 00:45:56.901 --> 00:46:00.234 of flying six missions this given year. 893 00:46:00.234 --> 00:46:04.767 Now we have reviewed what we have been able to do 894 00:46:04.767 --> 00:46:06.501 over the last year or 2. 895 00:46:06.501 --> 00:46:08.400 We've had a lower workforce here in Florida. 896 00:46:08.400 --> 00:46:10.400 Our flight rate has been lower, 897 00:46:10.400 --> 00:46:13.467 and all that has worked out just fine, 898 00:46:13.467 --> 00:46:15.934 but as we look ahead based on the efficiencies 899 00:46:15.934 --> 00:46:18.167 that have been implemented here at Kennedy 900 00:46:18.167 --> 00:46:21.067 and really checking those efficiencies, you know, 901 00:46:21.067 --> 00:46:23.701 sometimes you project what efficiencies 902 00:46:23.701 --> 00:46:25.200 and gains you're going to get. 903 00:46:25.200 --> 00:46:28.234 We've had some opportunity now to put those efficiencies 904 00:46:28.234 --> 00:46:31.067 in place and really validate them. 905 00:46:31.067 --> 00:46:34.934 We believe that we need to plus up our workforce 906 00:46:34.934 --> 00:46:38.467 a little bit here in the Kennedy Space Center, 907 00:46:38.467 --> 00:46:40.834 and we're in the process of doing that. 908 00:46:40.834 --> 00:46:45.267 We were at some 3,650 people here in the USA this summer, 909 00:46:45.267 --> 00:46:48.100 and we're up to over 3,700 today, 910 00:46:48.100 --> 00:46:51.200 and we plan to be at 3,800 by March or April, 911 00:46:51.200 --> 00:46:52.834 and that would put us in a good position 912 00:46:52.834 --> 00:46:56.234 to fly these six flights in the summer months 913 00:46:56.234 --> 00:46:59.801 where we think we're going to have three or four. 914 00:46:59.801 --> 00:47:01.234 -Justin Ray. 915 00:47:01.234 --> 00:47:04.267 -Justin Ray with spaceflightnow.com, 916 00:47:04.267 --> 00:47:06.033 I was wondering you could 917 00:47:06.033 --> 00:47:09.834 sort of put 1999 into perspective, Ron. 918 00:47:09.834 --> 00:47:12.234 So far, only two missions, would you say the year 919 00:47:12.234 --> 00:47:16.234 has been disappointing, frustrating, challenging? 920 00:47:16.234 --> 00:47:19.601 So far to date, what do you say about the year? 921 00:47:19.601 --> 00:47:21.200 -Yes. 922 00:47:23.601 --> 00:47:26.267 Our flight rate is lower than we'd like it to be. 923 00:47:26.267 --> 00:47:29.667 Okay, and there's not much we can do about that, 924 00:47:29.667 --> 00:47:32.501 and I just explained why, 925 00:47:32.501 --> 00:47:35.434 but we've had a lot of good success. 926 00:47:35.434 --> 00:47:37.868 We visited the space station twice, 927 00:47:37.868 --> 00:47:41.100 once last December and then again in the May time frame, 928 00:47:41.100 --> 00:47:46.367 and then we deployed the Chandra telescope in July, 929 00:47:46.367 --> 00:47:48.601 so what we had to do we did, and we did it very well, 930 00:47:48.601 --> 00:47:50.167 so we've had a lot of good successes 931 00:47:50.167 --> 00:47:51.601 in the shuttle program, 932 00:47:51.601 --> 00:47:54.267 and now we're working on getting ready to fly again, 933 00:47:54.267 --> 00:47:57.868 and we're certainly ready to fly again here in the next few days, 934 00:47:57.868 --> 00:48:01.334 and then we'll have to see what the future brings this next year 935 00:48:01.334 --> 00:48:02.868 to see if our customers are ready 936 00:48:02.868 --> 00:48:06.334 when we'd like them to be ready, and we'll just go do that. 937 00:48:06.334 --> 00:48:07.567 -Okay. 938 00:48:07.567 --> 00:48:08.734 We'll move over to this side of the room here 939 00:48:08.734 --> 00:48:10.667 for some people who haven't had a chance. 940 00:48:10.667 --> 00:48:12.901 Marcia Dunn. 941 00:48:12.901 --> 00:48:15.334 -Marcia Dunn, Associated Press, two questions for Ron, 942 00:48:15.334 --> 00:48:18.701 firstly in light of the two Mars failures 943 00:48:18.701 --> 00:48:21.801 and all of the shuttle problems, how important is it for you 944 00:48:21.801 --> 00:48:25.200 to see NASA get this flight off finally 945 00:48:25.200 --> 00:48:28.767 and to have a big win up there with Hubble? 946 00:48:28.767 --> 00:48:33.400 -Well, I don't look at the Mars activities that have gone on 947 00:48:33.400 --> 00:48:35.400 and what you have reported on the press 948 00:48:35.400 --> 00:48:38.267 as any factor on the shuttle program. 949 00:48:38.267 --> 00:48:41.501 I've got to have my head in the game 950 00:48:41.501 --> 00:48:44.667 of launching shuttles and doing them safely 951 00:48:44.667 --> 00:48:48.234 and doing them when they're ready to fly, 952 00:48:48.234 --> 00:48:51.601 and so, you know, I read your press reports, 953 00:48:51.601 --> 00:48:54.667 and I see what might have happened with the Mars programs, 954 00:48:54.667 --> 00:48:56.567 but that does not affect my thinking. 955 00:48:56.567 --> 00:48:59.467 It does not affect my planning. 956 00:48:59.467 --> 00:49:01.234 I'll go back to the success 957 00:49:01.234 --> 00:49:03.501 I just mentioned over the last year. 958 00:49:03.501 --> 00:49:05.634 If you try to put these in perspective, you know, 959 00:49:05.634 --> 00:49:11.100 the Mars two missions were maybe $400 million worth of missions. 960 00:49:11.100 --> 00:49:15.133 Chandra alone, spacecraft was $1 billion. 961 00:49:15.133 --> 00:49:17.100 The shuttle did that mission. 962 00:49:17.100 --> 00:49:21.300 Every time we go to the station, we support that significantly, 963 00:49:21.300 --> 00:49:22.801 so if you put those in perspective, 964 00:49:22.801 --> 00:49:25.901 the shuttle program is doing a significant amount 965 00:49:25.901 --> 00:49:28.801 of successful activities in the past year, 966 00:49:28.801 --> 00:49:32.367 and so we ought not to lose perspective 967 00:49:32.367 --> 00:49:35.234 all of the successes that go on around NASA, 968 00:49:35.234 --> 00:49:36.834 and I'm just talking about the shuttle program, 969 00:49:36.834 --> 00:49:39.634 and I'm sure there are many other successes 970 00:49:39.634 --> 00:49:42.834 that go on from day to day that just aren't as visible. 971 00:49:42.834 --> 00:49:45.534 It just so happens that the latest two activities 972 00:49:45.534 --> 00:49:47.834 going to Mars have been very visible, 973 00:49:47.834 --> 00:49:49.067 but let me say again, 974 00:49:49.067 --> 00:49:52.567 that activity and their success or failure 975 00:49:52.567 --> 00:49:54.601 does not affect what we do in the shuttle program. 976 00:49:54.601 --> 00:49:57.367 It does not rush us. It does not change our planning. 977 00:49:57.367 --> 00:50:00.234 We keep our head down in the foxhole, and we work, 978 00:50:00.234 --> 00:50:03.701 and we plan, and we get ourselves ready to fly. 979 00:50:03.701 --> 00:50:05.434 -Okay. Thanks. 980 00:50:05.434 --> 00:50:08.133 Besides seven astronauts, if they're up on Christmas, 981 00:50:08.133 --> 00:50:10.501 how many other people are going to be working on Christmas Day, 982 00:50:10.501 --> 00:50:12.300 and do you have any idea of what that's going to cost 983 00:50:12.300 --> 00:50:14.834 in overtime? 984 00:50:14.834 --> 00:50:19.601 -Well, I would say that just by rough numbers of people, 985 00:50:19.601 --> 00:50:22.901 you'll probably have about 100 or so, 986 00:50:22.901 --> 00:50:24.701 probably more than that at the Johnson Space Center 987 00:50:24.701 --> 00:50:28.000 just doing the mission control activities 988 00:50:28.000 --> 00:50:30.701 and keeping the control center running. 989 00:50:30.701 --> 00:50:33.133 You'll have another 100 from Goddard 990 00:50:33.133 --> 00:50:35.267 that'll be located at the Johnson Space Center, 991 00:50:35.267 --> 00:50:37.801 so those people will be away from their home 992 00:50:37.801 --> 00:50:39.868 for Christmas to support the mission, 993 00:50:39.868 --> 00:50:41.501 and you'll have remote facilities 994 00:50:41.501 --> 00:50:43.367 that people will work, 995 00:50:43.367 --> 00:50:46.734 so you're going to have I'd estimate 200, 996 00:50:46.734 --> 00:50:50.000 300 people that will be engaged 997 00:50:50.000 --> 00:50:54.801 and work over the Christmas Eve and Christmas Day. 998 00:50:54.801 --> 00:50:59.334 Now if we launch on the 16th, 17th or even the 18th. 999 00:50:59.334 --> 00:51:01.934 we don't land until the 26th, 1000 00:51:01.934 --> 00:51:05.100 so here in Florida once they get through the launch, 1001 00:51:05.100 --> 00:51:07.801 their level of activity really drops off until we land, 1002 00:51:07.801 --> 00:51:09.834 and then they start preparing for landing, 1003 00:51:09.834 --> 00:51:13.234 so the predominant effort will be at the Johnson Space Center 1004 00:51:13.234 --> 00:51:16.567 for mission control once we launch. 1005 00:51:16.567 --> 00:51:20.934 -Any idea what this is costing above and beyond the, uh... 1006 00:51:20.934 --> 00:51:22.300 -No, I really haven't. 1007 00:51:22.300 --> 00:51:24.434 That's another one of those things that, you know, 1008 00:51:24.434 --> 00:51:27.300 I haven't even worried about because we're going to do it, 1009 00:51:27.300 --> 00:51:30.367 and the cost is the cost, and that's the way it is. 1010 00:51:30.367 --> 00:51:33.901 We'll just go do the mission and be safe about doing it. 1011 00:51:33.901 --> 00:51:39.868 -Sue Butler. -We talked a lot about people 1012 00:51:39.868 --> 00:51:42.701 being nervous about this mission. 1013 00:51:42.701 --> 00:51:45.634 I've heard some certain expressions 1014 00:51:45.634 --> 00:51:48.934 such as snake pit, seen it in the paper. 1015 00:51:48.934 --> 00:51:54.334 Now to give you an analogy, the FAA administrator 1016 00:51:54.334 --> 00:51:56.667 is planning to fly around the country in New Year 1017 00:51:56.667 --> 00:52:01.267 to prove that there will be no problem with the computers. 1018 00:52:01.267 --> 00:52:06.200 What can you do to reassure the public 1019 00:52:06.200 --> 00:52:09.067 that you have dotted every I? 1020 00:52:11.868 --> 00:52:15.334 -Well, I don't know where the nervousness is. 1021 00:52:15.334 --> 00:52:18.934 I think most of the nervousness comes from you, the press. 1022 00:52:18.934 --> 00:52:22.868 As I read the papers and see articles, 1023 00:52:22.868 --> 00:52:29.200 I consistently see a theme that, "Y2K is a problem. 1024 00:52:29.200 --> 00:52:31.801 We are rushing to launch in the December. 1025 00:52:31.801 --> 00:52:35.267 The workforce is too low. Are we really ready to fly?" 1026 00:52:35.267 --> 00:52:39.033 and in actuality, those things are being generated. 1027 00:52:39.033 --> 00:52:40.801 If you wanted me to reassure the public, 1028 00:52:40.801 --> 00:52:46.701 I would ask you to report back to the public what we have done. 1029 00:52:46.701 --> 00:52:48.834 We have spent a tremendous amount of effort 1030 00:52:48.834 --> 00:52:50.801 and time and intensity 1031 00:52:50.801 --> 00:52:52.200 on making these vehicles safe to fly. 1032 00:52:52.200 --> 00:52:55.934 They are safer today than they ever have been. 1033 00:52:55.934 --> 00:52:59.734 When the crews go on board, they ought to feel really good. 1034 00:52:59.734 --> 00:53:02.434 I know they do because they have commented 1035 00:53:02.434 --> 00:53:04.801 how safe they believe the vehicle is. 1036 00:53:04.801 --> 00:53:06.234 They've flown these vehicles before, 1037 00:53:06.234 --> 00:53:08.300 and they know what has gone on over the last 4 months, 1038 00:53:08.300 --> 00:53:09.667 and it is safer. 1039 00:53:09.667 --> 00:53:10.901 We've inspected that wiring. 1040 00:53:10.901 --> 00:53:13.701 We put in protection. We have repaired. 1041 00:53:13.701 --> 00:53:15.868 Even though most of what we found was minor, 1042 00:53:15.868 --> 00:53:18.100 it is much cleaner. 1043 00:53:18.100 --> 00:53:21.000 Even the intensity of the inspectors, 1044 00:53:21.000 --> 00:53:23.968 when we close out the aft compartment, 1045 00:53:23.968 --> 00:53:28.033 and we found this latest 4-inch manifold that had a dent in it, 1046 00:53:28.033 --> 00:53:29.968 again, it's a part of the inspection process 1047 00:53:29.968 --> 00:53:33.868 where our overall level of scrutiny has been raised, 1048 00:53:33.868 --> 00:53:36.834 and so our standards are up from where they were 1049 00:53:36.834 --> 00:53:40.634 which has been very healthy for the shuttle program. 1050 00:53:40.634 --> 00:53:42.667 We've had some folks come and help us. 1051 00:53:42.667 --> 00:53:44.167 We've had some independent assessments 1052 00:53:44.167 --> 00:53:46.334 come and look at our program 1053 00:53:46.334 --> 00:53:49.067 and see where they can find weaknesses, 1054 00:53:49.067 --> 00:53:50.534 and where they find weaknesses, 1055 00:53:50.534 --> 00:53:53.300 we will go correct and make those strengths, 1056 00:53:53.300 --> 00:53:56.801 and so I would ask you to report to the American public 1057 00:53:56.801 --> 00:53:58.567 that we are in good shape. 1058 00:53:58.567 --> 00:54:00.534 We are flying these vehicles safely. 1059 00:54:00.534 --> 00:54:04.467 We're in no rush to launch, but we use our judgment, 1060 00:54:04.467 --> 00:54:06.400 and it's the right judgment to launch this week. 1061 00:54:06.400 --> 00:54:08.567 If we didn't think so, we wouldn't be here to tell you 1062 00:54:08.567 --> 00:54:10.534 that's what we plan to do. 1063 00:54:10.534 --> 00:54:11.801 If we wanted to launch in January, 1064 00:54:11.801 --> 00:54:14.234 I wouldn't feel bad about saying that, too. 1065 00:54:14.234 --> 00:54:16.868 We could launch in January. That's no big deal. 1066 00:54:16.868 --> 00:54:18.200 There's nothing driving me to December 1067 00:54:18.200 --> 00:54:20.400 except what I've already told you about, 1068 00:54:20.400 --> 00:54:23.100 so I'm very pleased with the shuttle program, 1069 00:54:23.100 --> 00:54:24.601 very pleased with the workforce. 1070 00:54:24.601 --> 00:54:26.534 I think they've done a tremendous job, 1071 00:54:26.534 --> 00:54:28.234 a commendable job. 1072 00:54:28.234 --> 00:54:32.367 Our overall awareness has been heightened. 1073 00:54:32.367 --> 00:54:35.067 I think the workforce feels better 1074 00:54:35.067 --> 00:54:38.100 about what they have produced, and they are getting 1075 00:54:38.100 --> 00:54:41.400 a lot of attention, and we get a lot of attention. 1076 00:54:41.400 --> 00:54:43.834 They feel better about that, also. 1077 00:54:43.834 --> 00:54:48.501 You know, many times the attention they get is negative. 1078 00:54:48.501 --> 00:54:51.834 What we'd like to see is more positive attention, 1079 00:54:51.834 --> 00:54:53.467 not negative attention. 1080 00:54:53.467 --> 00:54:55.801 You can do more to help the shuttle program 1081 00:54:55.801 --> 00:54:58.067 than you realize, so if you ask me, 1082 00:54:58.067 --> 00:55:03.667 Sue, about what can I say to help the American public 1083 00:55:03.667 --> 00:55:05.667 feel better about the space program, 1084 00:55:05.667 --> 00:55:10.100 I'll ask you to help me to do that. 1085 00:55:10.100 --> 00:55:13.567 -Okay, Stefano. -Stefano Coledan with UPI 1086 00:55:13.567 --> 00:55:14.968 and "Popular Mechanics," 1087 00:55:14.968 --> 00:55:17.501 have you determined how the pipe, 1088 00:55:17.501 --> 00:55:19.801 the jacket was crushed, 1089 00:55:19.801 --> 00:55:24.267 and also, was the inner liner damaged after all? 1090 00:55:24.267 --> 00:55:27.901 -Well, we took the part out, and we don't intend to scrap it. 1091 00:55:27.901 --> 00:55:29.667 We intend to take it on the bench 1092 00:55:29.667 --> 00:55:32.234 and do a lot of testing 1093 00:55:32.234 --> 00:55:36.400 and, you know, similar do CAT-scan types of things 1094 00:55:36.400 --> 00:55:40.501 and see exactly if there was any damage to the inner liner. 1095 00:55:40.501 --> 00:55:42.100 We don't know yet, too premature, 1096 00:55:42.100 --> 00:55:43.767 but that is in our plans. 1097 00:55:43.767 --> 00:55:46.334 What caused it? 1098 00:55:46.334 --> 00:55:48.501 When you work in the aft compartment, 1099 00:55:48.501 --> 00:55:51.200 it is difficult to do that. 1100 00:55:51.200 --> 00:55:53.667 It's a very cramped space. 1101 00:55:53.667 --> 00:55:55.701 You have to be somewhat of a contortionist 1102 00:55:55.701 --> 00:55:58.601 to go in and do that. 1103 00:55:58.601 --> 00:56:01.567 If you're not limber, you don't work in the aft compartment. 1104 00:56:01.567 --> 00:56:03.567 I mean, you've got to be able to bend 1105 00:56:03.567 --> 00:56:07.601 and kneel and crawl and slide, and it's difficult, 1106 00:56:07.601 --> 00:56:09.467 and we ask these guys to do a lot, 1107 00:56:09.467 --> 00:56:11.767 and they do it very well, 1108 00:56:11.767 --> 00:56:14.834 but that doesn't mean that we won't get collateral damage 1109 00:56:14.834 --> 00:56:18.701 from time to time by a misstep or a knee in the wrong place. 1110 00:56:18.701 --> 00:56:21.334 What we need to do is help them out, 1111 00:56:21.334 --> 00:56:24.100 and what we plan to do is look at the aft compartment 1112 00:56:24.100 --> 00:56:26.934 more closely from a human factors point of view. 1113 00:56:26.934 --> 00:56:28.634 Maybe we're asking them to do too much, 1114 00:56:28.634 --> 00:56:31.634 and we haven't helped them with design. 1115 00:56:31.634 --> 00:56:36.167 We put elephant hide over this 4-inch recirculation manifold. 1116 00:56:36.167 --> 00:56:38.834 That's not enough because obviously we can step on it 1117 00:56:38.834 --> 00:56:42.100 or kneel on it and damage the line. 1118 00:56:42.100 --> 00:56:45.634 Maybe we need to put some platforms in there 1119 00:56:45.634 --> 00:56:48.033 whether plastic or whether it's metal. 1120 00:56:48.033 --> 00:56:50.968 We need to do something to help the workforce 1121 00:56:50.968 --> 00:56:53.667 so that we don't have these delays 1122 00:56:53.667 --> 00:56:56.767 that are caused by workmanship. 1123 00:56:56.767 --> 00:56:59.167 You know, we're not on the ground 1124 00:56:59.167 --> 00:57:02.634 because of pieces of hardware that are breaking. 1125 00:57:02.634 --> 00:57:06.467 We're on the ground because we have broke it, 1126 00:57:06.467 --> 00:57:09.267 and we need to fix that, 1127 00:57:09.267 --> 00:57:12.200 and part of it is it's not that the workforce is not skilled. 1128 00:57:12.200 --> 00:57:14.200 It's not that they're not trained. 1129 00:57:14.200 --> 00:57:17.267 I think in large part we have set them up. 1130 00:57:17.267 --> 00:57:20.067 We need to get our design folks in step 1131 00:57:20.067 --> 00:57:21.567 with our processing folks 1132 00:57:21.567 --> 00:57:25.501 and see what we can do to make this orbiter easier to work on, 1133 00:57:25.501 --> 00:57:27.267 and that's part of the thrust that we're going to have to do 1134 00:57:27.267 --> 00:57:31.167 over the next months and years. -Okay. 1135 00:57:31.167 --> 00:57:32.868 Jay Barber, do you have your hand up? 1136 00:57:32.868 --> 00:57:34.200 -Yes. 1137 00:57:34.200 --> 00:57:36.934 Jay Barber of NBC for Ron and Dave. 1138 00:57:36.934 --> 00:57:38.300 Ron, you said a while ago, I believe, 1139 00:57:38.300 --> 00:57:41.300 that if we launched 16, 17 or 18. 1140 00:57:41.300 --> 00:57:44.000 come-home day would still be the 26th. 1141 00:57:44.000 --> 00:57:47.334 What is the real drop-dead day that you really have to get back 1142 00:57:47.334 --> 00:57:50.601 and get on the ground date to put everything away? 1143 00:57:50.601 --> 00:57:52.300 Can you do that as late as the 30th, 1144 00:57:52.300 --> 00:57:53.734 and are you really figuring in here 1145 00:57:53.734 --> 00:57:56.701 with this 27th a couple of contingency days 1146 00:57:56.701 --> 00:57:58.400 just in case you have bad weather? 1147 00:57:58.400 --> 00:58:01.100 -Let me tell you the days, and I'll let Dave give me 1148 00:58:01.100 --> 00:58:05.601 a break and talk about what's driving the -- 1149 00:58:05.601 --> 00:58:08.100 once you land to Y2K. 1150 00:58:08.100 --> 00:58:11.133 The 26th is our target landing date, 1151 00:58:11.133 --> 00:58:14.334 and we always protect for 2 days of weather extension, 1152 00:58:14.334 --> 00:58:17.934 so if you target for the 26th, that means you need, 1153 00:58:17.934 --> 00:58:21.534 no, Sherlock, you got to land on the 28th if you had bad weather, 1154 00:58:21.534 --> 00:58:26.133 so based on the 28th given we have used 1155 00:58:26.133 --> 00:58:29.667 all our weather extension days, then we land. 1156 00:58:29.667 --> 00:58:32.868 Now Dave takes over because he's got to process the vehicle. 1157 00:58:32.868 --> 00:58:34.100 He's got to have it secured. 1158 00:58:34.100 --> 00:58:36.601 He's got to have it safe so that we can have 1159 00:58:36.601 --> 00:58:38.834 an orderly shutdown of computer systems, 1160 00:58:38.834 --> 00:58:42.501 ground computer systems prior to Y2K. 1161 00:58:42.501 --> 00:58:44.133 -And the answer to that is we feel like we need 1162 00:58:44.133 --> 00:58:46.434 to be on the ground on the 28th in the evening 1163 00:58:46.434 --> 00:58:52.000 to be able to get the orbiter secured, get the PRSD offloaded, 1164 00:58:52.000 --> 00:58:55.701 get all of our requirements met postlanding 1165 00:58:55.701 --> 00:58:59.801 such that we've made sure that we have a good vehicle 1166 00:58:59.801 --> 00:59:02.734 technically and power down the vehicle, 1167 00:59:02.734 --> 00:59:06.000 and then we have about a 12-hour bar beyond that 1168 00:59:06.000 --> 00:59:09.701 to get all of our computer systems powered down and be down 1169 00:59:09.701 --> 00:59:14.434 before actually 19:00 Eastern Time on the 31st 1170 00:59:14.434 --> 00:59:17.033 because we work to GMT time, 1171 00:59:17.033 --> 00:59:19.801 so that backs you up to the 29th. 1172 00:59:19.801 --> 00:59:22.033 The work is a little longer at Dryden than it 1173 00:59:22.033 --> 00:59:23.334 is here just because of 1174 00:59:23.334 --> 00:59:26.234 the physical attributes of trying to get work done 1175 00:59:26.234 --> 00:59:29.234 and get into the...device 1176 00:59:29.234 --> 00:59:30.467 and get hooked up to the sling 1177 00:59:30.467 --> 00:59:33.100 and leveled such that you can get into 1178 00:59:33.100 --> 00:59:35.100 all of that securing work that needs to be done, 1179 00:59:35.100 --> 00:59:38.400 and that's really what drives you there. 1180 00:59:38.400 --> 00:59:41.801 -The must-land date is then the 28th. 1181 00:59:41.801 --> 00:59:46.000 You can come down the 29th and still make it, Dave. 1182 00:59:46.000 --> 00:59:47.801 -That's correct. 1183 00:59:47.801 --> 00:59:49.167 That's what we are planning to today. 1184 00:59:49.167 --> 00:59:54.234 We need the 29th and 30th to get the vehicle secured, 1185 00:59:54.234 --> 00:59:57.834 and then we'd have the 31st to get the rest 1186 00:59:57.834 --> 01:00:02.133 of the computer equipment here at Kennedy secure. 1187 01:00:02.133 --> 01:00:04.300 -So evening landing on the 28th. 1188 01:00:04.300 --> 01:00:05.734 -That's correct. 1189 01:00:05.734 --> 01:00:08.767 -That protects for the Edwards landing should we have to do it. 1190 01:00:08.767 --> 01:00:10.234 -Thank you. 1191 01:00:10.234 --> 01:00:12.734 -Phil Chin. 1192 01:00:12.734 --> 01:00:13.901 -Phil Chin. 1193 01:00:13.901 --> 01:00:15.834 Let me start a follow-up on that. 1194 01:00:15.834 --> 01:00:17.534 Is there any scenario where you'd consider 1195 01:00:17.534 --> 01:00:19.033 launching on the 19th? 1196 01:00:19.033 --> 01:00:20.434 Obviously wouldn't try four times in a row, 1197 01:00:20.434 --> 01:00:22.868 but this sounds a lot like the previous mission 1198 01:00:22.868 --> 01:00:24.400 where you tried to get additional range attempts, 1199 01:00:24.400 --> 01:00:26.968 but if you fired off the igniters 1200 01:00:26.968 --> 01:00:29.133 and then needed the time to turn it around 1201 01:00:29.133 --> 01:00:31.400 and then accept the fact that you're going to have 1202 01:00:31.400 --> 01:00:32.801 to compress the end of the mission, 1203 01:00:32.801 --> 01:00:35.100 that if the weather is bad here, go immediately for a dry run 1204 01:00:35.100 --> 01:00:36.701 so you can still make your 28th landing, 1205 01:00:36.701 --> 01:00:39.367 something like that, or take off one or two EVAs, 1206 01:00:39.367 --> 01:00:40.968 plus the crew up, 1207 01:00:40.968 --> 01:00:42.400 make up the -- I'm just thinking. 1208 01:00:42.400 --> 01:00:44.667 Is there any scenario like this where you'd want to go -- 1209 01:00:44.667 --> 01:00:46.667 -The launch will not go past the 18th. 1210 01:00:46.667 --> 01:00:48.367 -Mm-hmm. -That's the simple answer. 1211 01:00:48.367 --> 01:00:49.767 We're not going to go past the 18th, 1212 01:00:49.767 --> 01:00:51.734 and the 18th leaves you with an 8-day mission 1213 01:00:51.734 --> 01:00:56.734 with 2 weather-extension days and three EVAs. 1214 01:00:56.734 --> 01:00:58.634 -And, Ron, in your opening remarks, 1215 01:00:58.634 --> 01:01:00.667 you made a comment about, "The majority of the workers 1216 01:01:00.667 --> 01:01:03.067 are happy with everything that's being done now." 1217 01:01:03.067 --> 01:01:04.534 How about the minority? 1218 01:01:04.534 --> 01:01:06.167 I suppose these are the guys who are reading all the stories 1219 01:01:06.167 --> 01:01:08.267 about the nervousness and everything else. 1220 01:01:08.267 --> 01:01:11.334 What do you do to assure them that everything is okay, 1221 01:01:11.334 --> 01:01:12.767 ameliorate their concerns? 1222 01:01:12.767 --> 01:01:14.834 And I suppose a lot of people are concerned about the fact 1223 01:01:14.834 --> 01:01:16.667 that we've found all of these problems. 1224 01:01:16.667 --> 01:01:19.067 We've fixed them all, but what else might there be 1225 01:01:19.067 --> 01:01:22.667 that we haven't done that may or may not catch us? 1226 01:01:22.667 --> 01:01:25.567 -Well, I say the majority because I -- 1227 01:01:25.567 --> 01:01:26.901 Certainly, it wouldn't feel truthful 1228 01:01:26.901 --> 01:01:28.701 about telling you 100 percent. 1229 01:01:28.701 --> 01:01:30.667 I mean, we have a tremendous workforce, 1230 01:01:30.667 --> 01:01:32.901 and I'd have to believe that out of that workforce, 1231 01:01:32.901 --> 01:01:36.901 there's got to be a few that, no matter what I do, 1232 01:01:36.901 --> 01:01:40.234 they would still feel uneasy, and I don't think 1233 01:01:40.234 --> 01:01:42.367 that's anything unique about the Shuttle Program. 1234 01:01:42.367 --> 01:01:47.000 That's just human nature which reminds me about a question 1235 01:01:47.000 --> 01:01:48.767 that was asked over here that I wanted to talk about, 1236 01:01:48.767 --> 01:01:51.167 and that's three launch attempts in a row, 1237 01:01:51.167 --> 01:01:54.334 and it was implied that that was unusual for us to do that. 1238 01:01:54.334 --> 01:01:57.167 It is not unusual for us to do that. 1239 01:01:57.167 --> 01:01:58.701 Typically, we don't do it 1240 01:01:58.701 --> 01:02:02.734 because the time of day of launch is not -- 1241 01:02:02.734 --> 01:02:06.634 and the preparations that lead up into the final day 1242 01:02:06.634 --> 01:02:09.334 are not in the wake hours, you know? 1243 01:02:09.334 --> 01:02:11.767 Like, if it were 2 or 3 a.m. in the morning, 1244 01:02:11.767 --> 01:02:15.434 now you're having people work 3 days in a row 1245 01:02:15.434 --> 01:02:17.501 that is not their normal sleep pattern, 1246 01:02:17.501 --> 01:02:20.367 not their normal work pattern, 1247 01:02:20.367 --> 01:02:23.801 and so we don't press 3 days in a row when that happens. 1248 01:02:23.801 --> 01:02:27.367 If, however, the launch is, and the preparation time, 1249 01:02:27.367 --> 01:02:30.801 is predominantly in the awake hours, 1250 01:02:30.801 --> 01:02:33.200 then we go back and ask the team 1251 01:02:33.200 --> 01:02:36.234 if that is an acceptable condition for you 1252 01:02:36.234 --> 01:02:40.434 to use your workforce for 3 days in a row. 1253 01:02:40.434 --> 01:02:42.167 And we asked Dave to go determine 1254 01:02:42.167 --> 01:02:46.834 whether that was an acceptable capability for this flight 1255 01:02:46.834 --> 01:02:50.300 because the first launch is 9:18 on the 16th, 1256 01:02:50.300 --> 01:02:52.234 and the next day its a half an hour earlier, 1257 01:02:52.234 --> 01:02:53.667 and the next day it's earlier than that, 1258 01:02:53.667 --> 01:02:55.434 and so it's all generally 1259 01:02:55.434 --> 01:02:58.934 in your awake hours from the morning, 1260 01:02:58.934 --> 01:03:02.334 midmorning, all the way through the later evening. 1261 01:03:02.334 --> 01:03:04.000 And Dave has talked to us 1262 01:03:04.000 --> 01:03:05.834 and told us that from the workforce point of view, 1263 01:03:05.834 --> 01:03:08.767 that's a feasible thing to consider. 1264 01:03:08.767 --> 01:03:11.601 Not that we will do it, but it's a feasible thing to consider, 1265 01:03:11.601 --> 01:03:14.100 and we would consider that depending upon 1266 01:03:14.100 --> 01:03:17.000 what caused us to scrub. 1267 01:03:17.000 --> 01:03:18.567 We had some flights earlier in the year. 1268 01:03:18.567 --> 01:03:22.033 We asked the very same question, and we determined at that point 1269 01:03:22.033 --> 01:03:23.834 we thought we could do three in a row 1270 01:03:23.834 --> 01:03:25.501 for the very same reasons. 1271 01:03:25.501 --> 01:03:27.601 It's just that sometimes because a launch time 1272 01:03:27.601 --> 01:03:28.767 is in the middle of the night, 1273 01:03:28.767 --> 01:03:30.567 you don't hear about it very often, 1274 01:03:30.567 --> 01:03:33.133 but when it is in the late afternoons 1275 01:03:33.133 --> 01:03:35.434 or in the early evenings, it's a perfect capability 1276 01:03:35.434 --> 01:03:38.334 that we ought to take advantage of if we can. 1277 01:03:38.334 --> 01:03:39.601 So it's not unusual. 1278 01:03:39.601 --> 01:03:42.601 It's just that you don't see it very often. 1279 01:03:42.601 --> 01:03:44.467 -Joe Barbary? -Yeah. 1280 01:03:44.467 --> 01:03:47.400 Just to follow up, Ron, you were saying there a while ago, 1281 01:03:47.400 --> 01:03:49.734 "If we launch on the 16th, it's a 10-day mission. 1282 01:03:49.734 --> 01:03:51.701 Launch on the 17th, a 9-day mission. 1283 01:03:51.701 --> 01:03:54.734 Launch on the 18th, an 8-day mission"? 1284 01:03:54.734 --> 01:03:56.133 -That's exactly right. -Okay, thank you. 1285 01:03:56.133 --> 01:03:57.300 -You got it. 1286 01:03:57.300 --> 01:03:59.000 -And, Phil, did you have a follow-up? 1287 01:03:59.000 --> 01:04:00.868 -But let me say one thing about that 1288 01:04:00.868 --> 01:04:02.934 from a HST point of view. 1289 01:04:02.934 --> 01:04:04.667 The 16th and the 17th 1290 01:04:04.667 --> 01:04:08.167 are equivalent from HST's point of view. 1291 01:04:08.167 --> 01:04:10.033 You do four EVAs. 1292 01:04:10.033 --> 01:04:12.300 The mission is shortened by 1 day. 1293 01:04:12.300 --> 01:04:17.501 We had inserted in the time line a crew rest day, 1294 01:04:17.501 --> 01:04:20.868 and what we're doing by going to the 17th 1295 01:04:20.868 --> 01:04:23.200 is we would delete that crew rest day. 1296 01:04:23.200 --> 01:04:25.868 Now, obviously we don't do that without talking to the crew 1297 01:04:25.868 --> 01:04:28.033 and asking them how they feel about that, 1298 01:04:28.033 --> 01:04:30.634 and they felt perfectly comfortable with doing that, 1299 01:04:30.634 --> 01:04:33.334 and so did all their management. 1300 01:04:33.334 --> 01:04:35.968 And when you go up to the 18th, you have to take out 1301 01:04:35.968 --> 01:04:40.067 the crew rest day and one EVA to get to 8 days, 1302 01:04:40.067 --> 01:04:42.100 and then we're looking to see if there's any way to keep 1303 01:04:42.100 --> 01:04:44.400 that fourth EVA in there, and that's what -- 1304 01:04:44.400 --> 01:04:45.968 Dave is going to sharpen his pencil 1305 01:04:45.968 --> 01:04:47.467 and see if there's any way to do that, 1306 01:04:47.467 --> 01:04:51.667 but we'll worry about that when we have to launch on the 18th. 1307 01:04:53.901 --> 01:04:55.934 -Let me follow -- Again, on this minority. 1308 01:04:55.934 --> 01:04:59.133 Obviously, you can't prove that no one isn't concerned, 1309 01:04:59.133 --> 01:05:02.667 but has anybody come to either of you to, Ron or Dave, 1310 01:05:02.667 --> 01:05:06.734 and expressed any concerns, and what have you told them? 1311 01:05:06.734 --> 01:05:08.033 When we talked last week, 1312 01:05:08.033 --> 01:05:09.934 certainly I was less concerned afterwards 1313 01:05:09.934 --> 01:05:13.501 than before because you did explain what the situation was, 1314 01:05:13.501 --> 01:05:14.701 what with the barring and the two, 1315 01:05:14.701 --> 01:05:16.501 but have any workers come up to you 1316 01:05:16.501 --> 01:05:18.434 and expressed any of those concerns? 1317 01:05:18.434 --> 01:05:20.868 -I'll let Dave answer for what he knows down here, 1318 01:05:20.868 --> 01:05:26.767 but I asked our management team to hold meetings, 1319 01:05:26.767 --> 01:05:30.000 staff meetings, all-hands meetings, 1320 01:05:30.000 --> 01:05:32.534 get down on the floor and go talk to their people. 1321 01:05:32.534 --> 01:05:34.567 I explained to them our rationale, 1322 01:05:34.567 --> 01:05:36.267 a lot of what I've been explaining to you, 1323 01:05:36.267 --> 01:05:38.701 so that they understand what we're doing. 1324 01:05:38.701 --> 01:05:40.434 You know, much of what you hear in discontent 1325 01:05:40.434 --> 01:05:42.300 is generally not discontent as much as it 1326 01:05:42.300 --> 01:05:45.100 is a misunderstanding of what the objective is, 1327 01:05:45.100 --> 01:05:48.067 and so we've been trying to improve our communications, 1328 01:05:48.067 --> 01:05:51.067 from the bottom all the way to the top and down, 1329 01:05:51.067 --> 01:05:54.567 and we have been doing that for some weeks. 1330 01:05:54.567 --> 01:05:56.567 No one has come to me personally 1331 01:05:56.567 --> 01:05:58.834 and told me we should not launch. 1332 01:05:58.834 --> 01:06:00.834 No one has come to me personally and said, 1333 01:06:00.834 --> 01:06:04.701 "We're pressing it," from a workforce point of view. 1334 01:06:04.701 --> 01:06:06.767 I have had indications from managers 1335 01:06:06.767 --> 01:06:09.467 that they have this sense or have this feeling, 1336 01:06:09.467 --> 01:06:13.100 and I go follow up on that and try to understand it, 1337 01:06:13.100 --> 01:06:16.834 and I haven't found one yet that has real data 1338 01:06:16.834 --> 01:06:21.400 other than their sense, okay? 1339 01:06:21.400 --> 01:06:24.200 There's nothing that's pressing here other than their sense, 1340 01:06:24.200 --> 01:06:25.434 and the sense I get out of that 1341 01:06:25.434 --> 01:06:28.834 is that we're moving into the holidays. 1342 01:06:28.834 --> 01:06:31.968 We're working over Christmas, 1343 01:06:31.968 --> 01:06:34.334 and when people focus on those holidays, 1344 01:06:34.334 --> 01:06:39.234 that starts to get into what maybe plans they had made, 1345 01:06:39.234 --> 01:06:42.067 family plans, and so they start feeling that, 1346 01:06:42.067 --> 01:06:43.734 and we're getting some feedback on that. 1347 01:06:43.734 --> 01:06:45.868 That does not make us unsafe to fly. 1348 01:06:45.868 --> 01:06:47.400 That does not mean we cannot launch. 1349 01:06:47.400 --> 01:06:50.067 It just means we need to do a better job at communicating 1350 01:06:50.067 --> 01:06:54.167 so they understand why we are doing this. 1351 01:06:54.167 --> 01:06:56.567 -And my perspective on that: 1352 01:06:56.567 --> 01:06:59.067 We have been out talking to this workforce 1353 01:06:59.067 --> 01:07:02.367 quite extensively recently about those kinds of issues. 1354 01:07:02.367 --> 01:07:06.367 We've had lots of forums to give folks opportunities 1355 01:07:06.367 --> 01:07:09.601 to express concerns. 1356 01:07:09.601 --> 01:07:13.601 The only concerns I've heard is with folks 1357 01:07:13.601 --> 01:07:16.834 trying to support more than one vehicle at a time. 1358 01:07:16.834 --> 01:07:18.400 We heard that over the last couple of weeks 1359 01:07:18.400 --> 01:07:20.534 and have recently, you know, told them, 1360 01:07:20.534 --> 01:07:23.434 "Look. If you have a concern supporting both, 1361 01:07:23.434 --> 01:07:28.400 then we just won't process the other vehicle at this time." 1362 01:07:28.400 --> 01:07:30.300 And we've sent that message to the workforce, 1363 01:07:30.300 --> 01:07:32.601 and that's happening. 1364 01:07:32.601 --> 01:07:35.501 That's not to say that we are not going to go process 1365 01:07:35.501 --> 01:07:38.567 STS-99 to go fly because we want to go do that. 1366 01:07:38.567 --> 01:07:42.200 But where folks had concerns or might have concerns 1367 01:07:42.200 --> 01:07:44.200 about being able to support two, 1368 01:07:44.200 --> 01:07:47.234 we've given them instructions with, 1369 01:07:47.234 --> 01:07:51.701 after talking with Ron about that, to, if they need to, 1370 01:07:51.701 --> 01:07:54.501 back off on 99, to go support 103. 1371 01:07:54.501 --> 01:07:59.400 One oh three has the priority currently, 1372 01:07:59.400 --> 01:08:03.434 but I have not had anybody come to me telling me 1373 01:08:03.434 --> 01:08:06.701 that we have a safety issue here 1374 01:08:06.701 --> 01:08:10.200 or we have concerns of the nature you talked. 1375 01:08:10.200 --> 01:08:12.467 Every concern that has been brought to my attention, 1376 01:08:12.467 --> 01:08:15.067 we've gone and worked, and it's been, you know, 1377 01:08:15.067 --> 01:08:18.067 a way to try to get the work done, 1378 01:08:18.067 --> 01:08:20.868 and we addressed all those appropriately, I believe. 1379 01:08:20.868 --> 01:08:22.534 -You know, from a Christmas point of view, 1380 01:08:22.534 --> 01:08:24.734 we've worked two missions over Christmas. 1381 01:08:24.734 --> 01:08:26.634 All right? This would be the third, 1382 01:08:26.634 --> 01:08:29.834 and from a Space Station point of view, 1383 01:08:29.834 --> 01:08:31.033 we're going to do that every year. 1384 01:08:31.033 --> 01:08:32.467 In fact, last year, remember? 1385 01:08:32.467 --> 01:08:36.300 We launched 88 in a Christmas time frame, STS-88. 1386 01:08:36.300 --> 01:08:38.100 Although the shuttle landed, 1387 01:08:38.100 --> 01:08:40.334 we had a team of folks in the control center 1388 01:08:40.334 --> 01:08:46.300 looking after the FGB that was put in orbit, so it happens. 1389 01:08:46.300 --> 01:08:47.934 It's part of our job. We will go do it, 1390 01:08:47.934 --> 01:08:52.234 so it's not going to be uncommon in the future, 1391 01:08:52.234 --> 01:08:54.767 and so we better get used to that. 1392 01:08:54.767 --> 01:08:56.200 -We've got time for a few more questions. 1393 01:08:56.200 --> 01:08:57.567 Sue? 1394 01:08:57.567 --> 01:09:04.334 -An easy one for you: What is the latest current date 1395 01:09:04.334 --> 01:09:10.234 for launching Endeavour, and what -- 1396 01:09:10.234 --> 01:09:15.367 Suppose you have to switch that, and you can't for any reason 1397 01:09:15.367 --> 01:09:18.634 launch Discovery before Christmas. 1398 01:09:18.634 --> 01:09:21.901 What would be the launch date for Discovery 1399 01:09:21.901 --> 01:09:24.033 and then Endeavour? 1400 01:09:24.033 --> 01:09:27.667 And one more question I'd like to tack on: 1401 01:09:27.667 --> 01:09:31.234 Who really needs that radar Earth mission? 1402 01:09:31.234 --> 01:09:34.167 -Needs what? -That radar mission. 1403 01:09:34.167 --> 01:09:35.634 I mean, why is that so important? 1404 01:09:35.634 --> 01:09:37.567 -Save that one for January. 1405 01:09:39.868 --> 01:09:42.801 -Latest launch on the books for Endeavour 1406 01:09:42.801 --> 01:09:44.534 is January the 13th, 1407 01:09:44.534 --> 01:09:46.067 but it's going to move to the right 1408 01:09:46.067 --> 01:09:47.234 because we changed an engine 1409 01:09:47.234 --> 01:09:49.133 out in the Vertical Assembly Building, 1410 01:09:49.133 --> 01:09:52.834 and we know that's an impact on that schedule. 1411 01:09:52.834 --> 01:09:54.534 We've already moved our flight-readiness review 1412 01:09:54.534 --> 01:09:56.701 from the 6th of January to the 11th, 1413 01:09:56.701 --> 01:10:00.267 so we know that Endeavour is going to move to the right 1414 01:10:00.267 --> 01:10:02.634 to the latter part of January. 1415 01:10:02.634 --> 01:10:05.000 Okay? We know that. 1416 01:10:05.000 --> 01:10:08.567 Now, if Discovery did not launch in December, 1417 01:10:08.567 --> 01:10:12.601 we would schedule it for January 13th, 1418 01:10:12.601 --> 01:10:14.567 same slot that Endeavour was in. 1419 01:10:14.567 --> 01:10:15.767 That's the earliest we can launch 1420 01:10:15.767 --> 01:10:17.234 after the beginning of the year 1421 01:10:17.234 --> 01:10:19.968 just because of what we have to do by the nature of the work 1422 01:10:19.968 --> 01:10:22.434 to get ready to go do the launch. 1423 01:10:22.434 --> 01:10:24.968 So I think that answered two of your questions, 1424 01:10:24.968 --> 01:10:27.100 and that last one, I'd hope you'd save that one 1425 01:10:27.100 --> 01:10:29.968 for the SRTM folks when they come in January 1426 01:10:29.968 --> 01:10:33.367 and talk about their science payload. 1427 01:10:33.367 --> 01:10:35.501 -Okay, Todd Halverson. 1428 01:10:35.501 --> 01:10:39.234 -Yeah, Todd Halverson of space.com for Dave King. 1429 01:10:39.234 --> 01:10:42.968 It occurs to me that over the, well, past couple of weekends 1430 01:10:42.968 --> 01:10:44.734 as well as, I think, Thanksgiving, too, 1431 01:10:44.734 --> 01:10:47.834 you've had crews out there working, 1432 01:10:47.834 --> 01:10:51.033 and I was curious about what time of overtime percentage 1433 01:10:51.033 --> 01:10:54.300 you've been running in this particular launch flow, 1434 01:10:54.300 --> 01:10:58.000 how that might compare to a normal launch flow, 1435 01:10:58.000 --> 01:11:00.133 how many waivers you've been signing 1436 01:11:00.133 --> 01:11:04.334 and how that might compare to a typical flow. 1437 01:11:04.334 --> 01:11:05.701 -Let me tell you that the kind of work 1438 01:11:05.701 --> 01:11:07.534 we've been doing over the past few weekends 1439 01:11:07.534 --> 01:11:09.234 has been different most weekends 1440 01:11:09.234 --> 01:11:12.300 which means different sets of folks work different weekends. 1441 01:11:12.300 --> 01:11:13.501 We have had some folks 1442 01:11:13.501 --> 01:11:18.567 who have had to work consecutive weekends, 1443 01:11:18.567 --> 01:11:21.434 but we've worked very hard to give folks days off. 1444 01:11:21.434 --> 01:11:23.834 We have very few waivers associated with going 1445 01:11:23.834 --> 01:11:26.467 and flying Thursday night. 1446 01:11:26.467 --> 01:11:32.133 We do have some, but it's very small in number 1447 01:11:32.133 --> 01:11:35.367 and not of any concerns. 1448 01:11:35.367 --> 01:11:37.868 As you know, we review those on an individual basis 1449 01:11:37.868 --> 01:11:44.167 and feel comfortable that what we have is good to go, 1450 01:11:44.167 --> 01:11:47.334 and as I said, we work very hard to try to give folks at least 1451 01:11:47.334 --> 01:11:49.567 1 day off on the weekend to reset the clock 1452 01:11:49.567 --> 01:11:51.067 and to spend a little time with their family, 1453 01:11:51.067 --> 01:11:54.501 such that they can be ready to come out here 1454 01:11:54.501 --> 01:11:58.267 and do this job professionally as we ask them to do. 1455 01:11:58.267 --> 01:12:04.200 So although we have been working some weekends, 1456 01:12:04.200 --> 01:12:06.968 I think we've worked very hard at making sure 1457 01:12:06.968 --> 01:12:09.834 that folks have time off, such that we don't have folks 1458 01:12:09.834 --> 01:12:14.734 that have been working weekend after weekend after weekend. 1459 01:12:14.734 --> 01:12:17.167 -Bill Harwood. -Yeah, Bill Harwood again, CBS, 1460 01:12:17.167 --> 01:12:18.534 with just a quick nuts and bolts. 1461 01:12:18.534 --> 01:12:20.968 Back when it was a full 10-day mission with four EVAs. 1462 01:12:20.968 --> 01:12:22.200 like if you launched on the 16th, 1463 01:12:22.200 --> 01:12:23.467 they were telling us at the prelaunches a while 1464 01:12:23.467 --> 01:12:26.567 back you had at least one contingency Hubble EVA 1465 01:12:26.567 --> 01:12:29.968 as well as the usual contingency shuttle EVA in the back pocket. 1466 01:12:29.968 --> 01:12:31.601 If you go to the 17th or 18th, 1467 01:12:31.601 --> 01:12:34.067 what does that do to contingency EVAs? 1468 01:12:34.067 --> 01:12:36.567 I'm assuming you would be limited to just four, 1469 01:12:36.567 --> 01:12:38.200 just three no matter 1470 01:12:38.200 --> 01:12:39.868 what in order to get down on the 26th. 1471 01:12:39.868 --> 01:12:41.234 Is that right? -Well, what we start doing is, 1472 01:12:41.234 --> 01:12:45.434 we start taking that get-ahead activities on the EVAs, 1473 01:12:45.434 --> 01:12:50.200 and we start deleting them, and those third and fourth EVAs 1474 01:12:50.200 --> 01:12:53.167 which are largely comprised of get-ahead tasks, 1475 01:12:53.167 --> 01:12:54.834 they start becoming margin, 1476 01:12:54.834 --> 01:12:56.434 and if you had to delete the fourth EVA, 1477 01:12:56.434 --> 01:12:58.901 then the third EVA is still largely comprised 1478 01:12:58.901 --> 01:13:00.267 of get-ahead tasks. 1479 01:13:00.267 --> 01:13:01.767 It becomes margin. 1480 01:13:01.767 --> 01:13:06.601 So the first two EVAs are the real meat of the mission, 1481 01:13:06.601 --> 01:13:10.501 and then three and four provide the margin 1482 01:13:10.501 --> 01:13:12.334 for the real requirements. 1483 01:13:12.334 --> 01:13:14.667 If all goes well on the first couple of EVAs, 1484 01:13:14.667 --> 01:13:17.834 then we're going to do the get-ahead tasks, 1485 01:13:17.834 --> 01:13:19.200 but that's where the margin is: 1486 01:13:19.200 --> 01:13:20.601 to get the real requirements done. 1487 01:13:20.601 --> 01:13:23.100 -What if you slip into the [Indistinct] 1488 01:13:23.100 --> 01:13:24.400 become your contingency -- 1489 01:13:24.400 --> 01:13:29.033 -If we go to the 17th, we still do four EVAs, 1490 01:13:29.033 --> 01:13:30.567 but again, if we were pressed for time, 1491 01:13:30.567 --> 01:13:32.834 we'd start throwing away the get-ahead, 1492 01:13:32.834 --> 01:13:35.000 and on the 18th, right. 1493 01:13:35.000 --> 01:13:38.968 Three EVAs, and one of those is your margin. 1494 01:13:38.968 --> 01:13:40.000 -Okay. I think we have two 1495 01:13:40.000 --> 01:13:41.901 final questions on this side. 1496 01:13:41.901 --> 01:13:44.968 Marcia? 1497 01:13:44.968 --> 01:13:46.267 -Marcia Dunn, for Ron. 1498 01:13:46.267 --> 01:13:51.767 If you launch on the 16th, all four EVAs go great, 1499 01:13:51.767 --> 01:13:53.834 is there any talk being given if the crew wanted 1500 01:13:53.834 --> 01:13:57.167 to give up their day off and come back on Christmas day 1501 01:13:57.167 --> 01:13:58.868 to at least spend some time with their families 1502 01:13:58.868 --> 01:14:00.067 that they wouldn't have on a holiday? 1503 01:14:00.067 --> 01:14:01.234 Is there any talk about that, 1504 01:14:01.234 --> 01:14:02.934 or would you still fly the full 10-day mission? 1505 01:14:02.934 --> 01:14:04.701 -We would fly the full 10-day mission. 1506 01:14:04.701 --> 01:14:06.601 We would do it just the way we had planned, 1507 01:14:06.601 --> 01:14:08.434 and it would be the best Christmas present 1508 01:14:08.434 --> 01:14:10.567 I could have this year. 1509 01:14:10.567 --> 01:14:12.701 -And I believe, Franco Malerba, did you have your hand up? 1510 01:14:12.701 --> 01:14:14.400 You haven't had a chance yet. 1511 01:14:16.634 --> 01:14:21.234 -Franco Malerba, I'm supporting RAI TV in Italy. 1512 01:14:21.234 --> 01:14:23.200 About the EVAs, I wonder, 1513 01:14:23.200 --> 01:14:26.634 what is the level of certainty and confidence 1514 01:14:26.634 --> 01:14:30.501 you have about the status of the Hubble Space Telescope? 1515 01:14:30.501 --> 01:14:33.767 In other words, if there will be any, say, 1516 01:14:33.767 --> 01:14:37.200 unknown as to the operations that need to be carried, 1517 01:14:37.200 --> 01:14:39.400 and therefore whether there will be a need 1518 01:14:39.400 --> 01:14:44.367 for any extra activity on the EVA side. 1519 01:14:44.367 --> 01:14:46.033 -Well, all I can say is, you know, 1520 01:14:46.033 --> 01:14:48.267 they've given us the state of the spacecraft. 1521 01:14:48.267 --> 01:14:51.200 We know the status of the equipment that's not working. 1522 01:14:51.200 --> 01:14:54.667 We also know that even though some equipment may be working, 1523 01:14:54.667 --> 01:14:56.734 we plan to change it out, 1524 01:14:56.734 --> 01:15:00.868 very detailed and trained plans for the EVAs. 1525 01:15:00.868 --> 01:15:04.300 There is some margin contingency time 1526 01:15:04.300 --> 01:15:06.033 if something were to go wrong. 1527 01:15:06.033 --> 01:15:09.067 We're even carrying some extra hardware that, 1528 01:15:09.067 --> 01:15:11.501 if something were to go wrong, they find something, 1529 01:15:11.501 --> 01:15:13.901 we could replace a particular piece of equipment. 1530 01:15:13.901 --> 01:15:15.934 So there is that flexibility. 1531 01:15:15.934 --> 01:15:18.367 They've tried to think of everything they can think of 1532 01:15:18.367 --> 01:15:19.868 so that when you make this one trip, 1533 01:15:19.868 --> 01:15:21.501 and you don't get there very often, 1534 01:15:21.501 --> 01:15:24.234 that you take advantage of it. 1535 01:15:24.234 --> 01:15:25.901 -Okay. We have two briefings tomorrow: 1536 01:15:25.901 --> 01:15:27.934 the countdown-status briefing at 9 a.m. 1537 01:15:27.934 --> 01:15:29.834 and the Hubble science briefing at 10. 1538 01:15:29.834 --> 01:15:31.434 Thank you.