Monday, November 12, 2007

Running My First Console Job

Last week I got to play Task Team Leader (TTL) for a console job. This meant I was in charge of coordinating with the Orbiter Test Conductor (OTC), Quality (QC), and the Technicians in the field. My role included talking on the net, monitoring the flow of the gaseous nitrogen (GN2) in the Ground Service Equipment (GSE) from the console computer, and commanding the solenoid valves.

During cart loading the week before we were having issues with one of the valves opening. It could have been a metering valve or a solenoid valve. The metering valve is person controlled right on the GSE where as the solenoid valve is controlled from the firing room through operator commands. These can be set to a sequencer to open and close at certain times which are more precise than what a human could do. Which is pretty important when you are dealing with hpypergolics. We were not sure which valve was having issues so we needed to route a flex hose from the metering valve to a gage on the other side of the solenoid. When we broke into the line at the metering valve and it was shown to be working we disconnected and tried using the solenoid. As it turns out it was working also. It must have just been a fluke in the system. There have not been too many problems with the solenoid valves so it is harder to figure out what the problem is. Could be that the magnetic pickups are gummed up. It will be something to look further into for the next loading.

Friday, November 9, 2007

Discovery Landing

On Wednesday 06 Nov. Discovery touched down at Kennedy Space Center at 13:01:18 (just as projected) from it's 15 day mission to the International Space Station. I was watching the live feed on NASA Tv all day up until landing eagerly waiting to see what would happen. I was absolutely astounded and couldn't help but laugh when I heard the controllers announce to the crew that they would begin to decelerate from Mach 22 to Mach 11. In less than an hour the orbiter screamed across North America from north-west Canada to central Florida.

At about 1250 I made my way outside (with almost everyone else in my building) to watch the bird land. For the first time ever, I got to hear the double sonic booms from re-entry. They were loud enough to set off car alarms in the parking lot.





I put in to get into the raffle to watch the landing from the runway but didn't win. So I was a little bitter that I would not be able to see Discovery in all her glory post landing. Much to my surprise on Thursday morning she was sitting outside Bay 3 waiting to get docked. Apparently there were some issues but I don't know the extent of them. I do know there were some issues later in the day when she was getting towed in. The system is measured by a laser. If the measurements are even a fraction of an inch off base the orbiter will be backed out of the bay and brought back in. NASA's misfortune made out for a great photo-op for me.



Tuesday, November 6, 2007

Launch Complex 31/32 and 34

I was bored over the weekend and found myself looking up urban myths about the shuttle program. One in particular caught my eye about Challenger and it got me thinking: Where is Challenger now? So I did some further research and found out that it is buried about 80 feet deep in an decommissioned minute-man missile silo at Cape Canaveral Air Force Station. Launch Complex 31/32 to be exact. So I decided to take a trip Cape side after work and see what I could find.

Unfortunately when I got to LC 31/32 there was no sign of anything related to Challenger. No buildings, no visible placards of any kind (I say visible because now that I know exactly where it is, I am going to go back to check it out), no fences or gates...nothing. It was just about what I expected an abandoned missile silo to be: abandoned. I would have expected there to be some kind of access to the orbiter or some kind of climate controlled structure. The area hadn't been used in decades and nature had begun taking the land back over. From the landscape I assumed I must have been in the wrong place. I was probably in the right area, maybe just looking in the wrong place. When I got back home I did some further research and found out that the first silo I stopped at was the silo which entombed Challenger (according to Google Earth). So now that I know where I am (presumably) supposed to go I will have to make another trip out there.

The trip was not a complete waste. I had been out to Launch Complex 34 before but did not have my camera with me. For those that do not know, Launch Complex 34 is where Apollo 1 burned up on the launch pad. The only other manned launch from the complex was Apollo 7. I do not want to say that it was eerie being there but it was. And it was extremely surreal. I do not have a whole lot to say about it other than it is a pretty peaceful place right next to the ocean. One of those places you can go to just think about life.

The launch pad and mobile flame trenches to the left:




Monday, November 5, 2007

Launch Countdown Simulation

Today we performed S0044 -- "Launch Countdown Simulation" for STS-122. During S0044 the launch team for each group sits on console and the countdown clock is started at T-20 minutes. The teams watch their simulated status and report any problems which occur and have to give a recommendation on holding the clock at the next milestone (usually T-9 minutes), scrub the launch if the problem cannot be resolved, or to decide if the problem will not inhibit launch or countdown.

For the APU team, there was a fuel pressure sensor which failed but a troubleshooting plan corrected the problem and there was no need to hold the countdown. For the SRB Hydraulics team, something similar happened but they would have had to scrub the launch because a technician would have had to enter the aft skirt of the SRB to assess the problem.

There are two sessions of S0044, one in the morning and one in the afternoon. The prime launch team comes in for the morning run where there is also a bonus round where they just dish out issues with your group but there is no troubleshooting. Just a decision on whether you would still be good for launch or not. The afternoon is used more for training for those that are not on the prime launch team (like myself!).