Article on the latest:http://www.nasaspaceflight.com/2011/05/sts-134-launch-slips-apu-troubleshooting-lca-fault/And I'll write another one tomorrow, lots of info coming in, but the above is what we need for now.
With 134 NET May 8, will this now affect 135 in June?
How is this problem not caught in all the testing that occurs during processing?
Quote from: TJL on 05/01/2011 04:18 pmWith 134 NET May 8, will this now affect 135 in June?They usually move the shuttle out to the pad a little over a month before launch. So if they get off the ground before on on the 10th there shouldn't be any delay for 135.
Hope you'll allow this question here?How do they decide where the count will pick up from?With recent scrubs they've continued from T-11 or T-6. I'm assuming it depends on the tasks which have had to be backed out from? (i.e. tank drained so it has to be at least T-6)?With the tasks undertaken this time (gained access to the aft of the orbiter) where might we pick up?
Quote from: Chris Bergin on 05/01/2011 01:20 pmArticle on the latest:http://www.nasaspaceflight.com/2011/05/sts-134-launch-slips-apu-troubleshooting-lca-fault/And I'll write another one tomorrow, lots of info coming in, but the above is what we need for now.Great write-up Chris - nailed it.