SpaceX COTS Demo 1 Updates

[renclod]

I would really love to know how they manage to make the supports for the capsule to penetrate the heat shield without causing a burn-through.

I asked that back here
http://forum.nasaspaceflight.com/index.php?topic=22769.msg644750#msg644750
Ben the space brit ansswered..

They aren't holes, they are geometric shapes in the PICA material into which the trunk attachment pads will fit.  the raised sides will stop the Dragon rotating atop the trunk during high-vibration flight modes.

jb

The compression pads are different material than the heatshield.
Ex: heatshield is PICA, or Avcoat. Fragile stuff.
Compression pads are [like] carbon-phenolic. Not sure what exactly that is, but think Shuttle RCC or rocket engine carbon composite nozzle material (RS-68, RSRM). Strong, heat-resistant material.
The compression pads are reacting loads between the CM and service module. The heatshield proper (ablative material) , does not.
The tension ties are forcing the CM and SM together.
Think steel cable, or threaded rods.
At CM-SM separation, the tension ties are severed (cut) on the outside of the heatshield/pads, so there is no hole. After separation, there is a small piece of the tension tie protruding, in the wake.
Each tension tie is going either right through the compression pad (Orion, Dragon), or through the heatshield but in close proximity of the compression pad (Apollo).
In the SpaceX updates (months old) there is a photo of heatshield assembly pathfinder operations - can't miss the compression pad (blue-ish colour in the pic), surrounded by large PICA tiles; or the tension tie position.

[Comga]

If you look at the video of the Dragon - Trunk separation test at http://www.spacex.com/multimedia/videos.php?id=49 it looks like there are six pads, three of which have tension ties near their centers.  ("Orion style")  As renclod says, after separation there is a small bit of the tensioner protruding through the pad that should be more or less flush with the PICA-X heat shield.  Here is a frame from the video where those protrusions are barely visible.

[Antares]

The Delta-IVH launch with the NROL-32 recon-sat keeps on slipping; I note that it seems to have reached 11/5 now.  What is the latest it can happen before SpaceX have to give up their 11/8 launch slot?

Hard to say.  There aren't hard, fast requirements on this.  Commercial launches are supposed to have precedence once on a long-term launch slot, but the government can always claim national interest or ISS crew at risk to bump them.

The same thing applies on short-term range scheduling, but IME once a range date is confirmed it is REALLY unusual for anyone to get bumped.

[aquarius]

NROL-32 launch slipped to November 16, so right now it can't impact the launch of F9/Dragon.

[robertross]

NROL-32 launch slipped to November 16, so right now it can't impact the launch of F9/Dragon.

Sucks for them, but great for Space-X (and ISS)  :)Thanks

[mr. mark]

COTS-1 is still on for November 8th about 3 weeks away due to the slippage of Delta IV to November 16th. That means that both Falcon 9 and the Shuttle will be on their pads at the same time. Sound like a great photo op. Also, Spacex still needs to engine test about 1 week before launch. Can they perform that while the shuttle is awaiting launch or will they narrrow their window and perform the test just after the shuttle launch? Does that also mean that the shuttle, Delta IV and Falcon 9 will all be on their pads at once. Wow! has that ever happened before?

[ugordan]

That means that both Falcon 9 and the Shuttle will be on their pads at the same time.

People never learn when it comes to new vehicles/spacecraft, do they?

Both Falcon 9 and the Shuttle may be on their pads at the same time. COTS-1 may slip just as NROL-32 has.

[Jim]

The F9 is no longer on its erector.

[mr. mark]

The F9 is no longer on its erector.

Does that imply something? Of course it's not on it's erectror. It's undergoing testing and vehicle integration as shown in this update picture on Spacex's website.

[Ben the Space Brit]

Besides, this is the Cape we're talking about.  It isn't the nicest of work environments when it comes to weather, bugs and beasties.  Would you voluntarily leave something outside of its sealed and air-conditioned hanger longer than absolutely necessary?

[ChefPat]

The F9 is no longer on its erector.

Thank you for the update (despite the negative comments about having done so), it is appreciated.

[ugordan]

Of course it's not on it's erectror. It's undergoing testing and vehicle integration as shown in this update picture on Spacex's website.

Well, duh, that image was taken before the vehicle was rolled out to the pad and WDR performed.

[Jim]

The F9 is no longer on its erector.

Thank you for the update (despite the negative comments about having done so), it is appreciated.

The erector is at the pad and vertical.

[StuffOfInterest]

Is the erector normally stored vertical?  I saw a photo recently of it horizontal and parked outside of the integration hangar which leads me to think it is not normally kept hooked up at the pad.  Leaves one to wonder if something new has been added and is now being tested.

[ugordan]

I guess it's only logical the stack had to be demated from the T/E in order to also demate Dragon. Curious why they tend to prefer keeping the T/E vertical at the pad, though.

[ChefPat]

I guess it's only logical the stack had to be demated from the T/E in order to also demate Dragon. Curious why they tend to prefer keeping the T/E vertical at the pad, though.

Once F9 is picked up by the cradle, wouldn't the erector be in the way?

[butters]

I guess it's only logical the stack had to be demated from the T/E in order to also demate Dragon. Curious why they tend to prefer keeping the T/E vertical at the pad, though.

Why would they demate Dragon before the static fire test?  I assume they're doing some prep work for the static fire (ignition fluid loading?), after which they will roll back to demate Dragon for hypergolic loading and remate for launch.

I predict static fire will be sometime around Oct 25-28, safely before Shuttle takes the range and leaving plenty of time for Dragon hyper loading and final preps.  Could even be late next week at the earliest.

[spacetraveler]

I predict static fire will be sometime around Oct 25-28, safely before Shuttle takes the range and leaving plenty of time for Dragon hyper loading and final preps.  Could even be late next week at the earliest.

Why would range availability affect a static fire test? They aren't launching anything.

[alexw]

I predict static fire will be sometime around Oct 25-28, safely before Shuttle takes the range and leaving plenty of time for Dragon hyper loading and final preps.  Could even be late next week at the earliest.

Why would range availability affect a static fire test? They aren't launching anything.

   In case of thermal curtain failure?      {Running and ducking...!}
    -Alex

[Ben the Space Brit]

I predict static fire will be sometime around Oct 25-28, safely before Shuttle takes the range and leaving plenty of time for Dragon hyper loading and final preps.  Could even be late next week at the earliest.

Why would range availability affect a static fire test? They aren't launching anything.

A static fire requires that the range be fully ready for a flight.  I don't know why, it just does.