I also doubt the Orbcomm's have the fuel to take them to 775km once dtopped from the trunk
Quote from: docmordrid on 07/21/2011 01:07 amI also doubt the Orbcomm's have the fuel to take them to 775km once dtopped from the trunk Based on published info, they will/would barely have any prop left after circularizing that 775 km altitude.
and then uses the remaining performance margin to boost itself + Orbcomms (attached to the 2nd stage as already illustrated)
So does Nov 30th look solid enough to ask for the day off?
Quote from: ugordan on 07/21/2011 01:10 amQuote from: docmordrid on 07/21/2011 01:07 amI also doubt the Orbcomm's have the fuel to take them to 775km once dtopped from the trunk Based on published info, they will/would barely have any prop left after circularizing that 775 km altitude.Quote from: ugordan on 07/21/2011 12:39 amand then uses the remaining performance margin to boost itself + Orbcomms (attached to the 2nd stage as already illustrated) Maybe the 2nd stage does some of that work too.
Ok, it looks like the plan is for Spacex to go for a combined mission with a November 30th launch and a December 7th berthing date (hopefully a date that will not live in infamy for Spacex)
It just leaves his statements logically incomplete. He doesn't "have to" say anything, but he he states that they are still in the process of approving the combined flights, without defining the focus of that process. It makes it sound like NASA is fumbling around and just indecisive. This isn't to say that NASA is fumbling, just that Suffredini's statements lack a narative of how they will get to approval or disapproval.
Can the 2nd stage do some of that orbcomm circularizing work too?
Potentially stupid question: Assuming the demo flight Dragon berths safely, is there anything standing in the way of the ISS crew packing in some downmass for the trip back?
Can anyone explain the reasoning behind the Nov. 30 launch date that has been thrown around alot? Why then?
Bill Gerstenmaier: NASA technically agreed w/SpaceX to combine C2/C3 flights, but still working some details before formally approving it.
SpaceX is mucking up the COTS testing process by flying secondary payloads. If the secondary payloads are an issue, they get them off this flight. Those secondary payloads only make the flight software more difficult to develop and test anyway. Fly the Orbcomm satelites on their own launcher. Give the commerical community some confidence that you still remember how to launch their payloads. Perhaps a successful commerical launch might even bring in some additional business. In the meanwhile, trying to fly secondary payloads on the COTS missions is delaying the flights, and delaying the start of the CRS contract. All of these schedule delays mean delayed payments from NASA. Getting the last of the COTS milestone payments and starting the CRS payments earlier should help cover any additional costs of launching these secondary payloads on a separate launcher.
When it comes to security, you have to demonstrate that it doesn't (pose a danger).
As long as the second stage and the Orbcomms never intersect ISS's orbit, that should be good enough.
Quote from: Norm38 on 07/22/2011 06:33 pm As long as the second stage and the Orbcomms never intersect ISS's orbit, that should be good enough.That is the issue, it can