NASA's Orbiting Carbon Observatory Mission Fails
jw3 writes "The NASA Orbiting Carbon Observatory scheduled for launch today has failed its mission: the payload fairing failed to separate and the launch managers declared a contingency. George Diller, NASA launch commentator, said, 'It either did not separate or did not separate in the way that it should, but at any rate we're still trying to evaluate exactly what the status of the spacecraft is at this point.'" Update: 02/24 14:17 GMT by T : Reader fadethepolice points out a Reuters report which says that the craft crashed into the ocean just short of Antarctica.
I know with the Mars rovers the cost of a second rover was small change compared to the development cost of the original. The launch vehicle is expensive, of course, but it was considered cheaper to launch two missions and hope one succeeded than launching one that could fail and mean all the money was wasted.
What sort of contingency do they have for sats like this? Do they just fabricate another one and try again in a year or two?
Kwisatz Haderach
Sell the spice to CHOAM
This Mahdi took Shaddam's Throne
Was the decision to use the Taurus to keep launch costs down? Launching from Vandenberg, I'm assuming they were aiming for a steep inclination. Just wondering if anyone knows why they didn't go with a Delta II....
the key satillite designed to monitor global warming and CO2 pollution and hence get scientific data that might affect global business and industrial nations has just nose dived into Antartica?
lets make sure nobody tells the conspiracy theorists, they could have a ball with this one.
Satellites are usually built in pairs just in case one of them fails during launch
Not usually...at least none of the NASA or AFRL projects I'm familiar with has a full-build spare. It's not entirely uncommon to have a second of some of the instruments, and it's pretty common to have enough spare parts to build another copy of an instrument. (Much easier to buy a couple of spares up front rather than wait around if someone screws something up.) Then testing and integration can go much more quickly and cheaply, having done it once before. It still can take awhile, though.
(Incidentally, the title and summary for this article suck...the OCO didn't fail, it was lost in a launch failure, and it didn't "fail its mission," it didn't get a chance to start. That's like saying your car broke down because someone ran a red light and T-boned it. No offense intended to the launch team.)