http://www.al.com/news/huntsvilletimes/index.ssf?/base/news/1219915016317820.xml&coll=1
This is instead of 2010 -- still preliminary though.......hmmmmm....
This is a near impossible subject to discuss without mentioning the politics....but forum rules are rules.
Leaving politics and funding issues aside, I think it's worth discussing the safety aspect of any decision to extend the Shuttle fleet's operational lifetime past 2010.
The 2010 date was not set for political or even budgetary reasons. It was one of those very strong recommendations-cum-orders that came out of the Columbia Accident Investigation Board (CAIB) report.
The CAIB set the bar very, very high in terms of safety -- essentially, to reduce the possibility of another loss of crew and vehicle (LOCV) accident to such a remote level that one could confidently predict that we would never lose another Shuttle crew. In this regard, they studied not only the sequence of events leading up to the loss of Columbia, they also studied the engineering history of the orbiter fleet.
The general trend of the observations was that the fleet was flying fewer total flights per vehicle than it was designed for, but over a longer period of time. So while the process of refurbishing between flights was doing a decent job of catching and fixing flight damage, there were far fewer processes in place to catch and fix issues of senescence -- of aging components and wiring that could be developing fatal flaws.
This was reinforced by the late 1999 launch of the first Shuttle flight commanded by Eileen Collins, during which deteriorating wiring harnesses throughout the orbiter caused several short circuits which brought the Shuttle stack one electrical failure away from losing from one to all three SSMEs during the first few seconds of climb-out.
The CAIB studied this and other incidents, looked at all of the (at least partially) applicable data from the aircraft industry, and concluded that one of two things needed to happen:
1) The entire fleet needed to be completely rebuilt, checking and replacing every wiring harness, avionics box, and even high-stress portions of the airframe, if it was to be safe to fly beyond the end of the decade, or
2) The entire fleet needed to be retired by 2010.
Since option 2 is one heck of a lot less expensive than option 1, NASA decided to retire the fleet and redirect post-2010 Shuttle operational funding into CEV development.
Now, you can easily debate the political and funding issues surrounding a decision to abandon the 2010 retirement date. But I find it very difficult to ignore the original driving force behind that date -- the aging condition of the orbiter fleet.
I do understand that we have a corps of astronauts who will take the risk of flying a vehicle that may not be 100% safe. But, solely from a safety standpoint, do we *really* want that to be our national policy?
-the other Doug
Great points from Doug and Wayne Hale's blog...I love his self-description as a "shuttle hugger". I'm admittedly torn on many accounts, have a not-so-closet emotional attachment to this vehicle from childhood, and would love to see it keep flying for a spell...but the safety, component, and technical considerations seem insurmountable for more than a few extra missions beyond the 2010 date. The AMS should fly on the proposed 134 mission if the right parts are available, but beyond that...
As a side note, I hope this often flawed but beautiful partnership can continue irrespective of the current difficulties. The plotline of "2010" suddenly seems prescient again.
Sorry to break with PDP8E's excellent suggestion to keep this potential powder keg limited to real news, but I've watched this development with ears perked up, and was excited to find this thread here.
I propose the remaining orbiters be converted to pedicabs. Thirty bicycles on each side of the fuselage should be enough to get one up the hills of Seattle or san Francisco. They can be amphibious like the tourist "Ducks" to meet Greg's suggestion in the middle.
Is there a definition somewhere of how we are operationally defining "politics" vis-a-vis this forum? I'm having difficulty distinguishing between why it's appropriate to bash ESA but inappropriate to discuss support for funding for a space project in the US. Not trying to be difficult here, but having had my hand slapped before, I am hesitant to participate in a discussion without having the rules defined clearly.
ESA isn't politics (how can you draw an analogy about that?). Talking about politicians or political parties is, however. Given the nature of who has asked for the Shuttle to be retired in 2010 - who is asking for an extension to be investigated - and what's happening in November - it's hard to discuss this without politics getting involved.
However - the Politics rule is here for a reason - and it will never be up for debate.
Basically - if you need a definition of politics - look in a dictionary.
It's impossible to write down forum rules. I've tried - but it's essentially impossible because at any decision process, it's a judgement call. This, however, is a very clear, unambiguous one.
If you aren't sure, it's probably best to avoid it.
Speaking absolutely apolitically, there seem to be a number of vehicles under development from many sources that could support ISS logistics to varying degrees. Jules Verne is still docked, for example, and IIRC Japan is developing something similar. I've also heard that private companies like SpaceX are interested in entering the market if & when Falcon 9 becomes a reliable reality.
Supply chains, like anything else, are horribly vulnerable to single-point (in this case, single-channel) failures unless enough redundancy is built in to the system. It would be interesting to know if these emerging alternatives are being considered as part of the Shuttle retirement decision.
Last word on the subject, I promise, but I found the perfect illustration of the Apollo X crew "assuming the position" for political discourse.
Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)