-
#20
by
Mike_1179
on 16 Dec, 2014 17:04
-
Is that an octo-web I see?
edit- nope, top of the TE
-
#21
by
Mike_1179
on 16 Dec, 2014 17:05
-
-
#22
by
Mike_1179
on 16 Dec, 2014 17:09
-
-
#23
by
pericynthion
on 16 Dec, 2014 17:10
-
SpX-5 Payloads
Two Planet Labs cubesats onboard also, equipped with replacements for the experimental new hardware that we lost on ORB-3.
-
#24
by
Mike_1179
on 16 Dec, 2014 17:13
-
Now time to watch for signs of venting, TE retraction, venting suddenly stopping and then hot-fire over these next few hours.
-
#25
by
sghill
on 16 Dec, 2014 18:36
-
-
#26
by
mheney
on 16 Dec, 2014 19:01
-
-
#27
by
saliva_sweet
on 16 Dec, 2014 19:03
-
-
#28
by
mheney
on 16 Dec, 2014 19:39
-
Feed just went to color bars (with a You Shall Not Pass" wizard wandering around from frame to frame ...)
-
#29
by
saliva_sweet
on 16 Dec, 2014 20:15
-
Excellent video made from the static fire feed by reddit user DevinWatson
edit: clarification per MTom's suggestion: Video ends when the feed was cut and (almost certainly) does not cover the actual static fire. Although interestingly the strongback was retracted at one point.
-
#30
by
WHAP
on 16 Dec, 2014 20:46
-
Did the static fire happen in there? Doesn't seem to be enough venting to indicate the LOX tank was filled, but hard to tell since I don't know the refresh rate.
-
#31
by
MTom
on 16 Dec, 2014 21:02
-
Excellent video made from the static fire feed by reddit user DevinWatson
I suggest to add a comment to your post: this is only a video about the preparation for the static fire.
@WHAP:
The feed has been cut before static fire occured. No further infos (here) yet.
-
#32
by
Chris Bergin
on 16 Dec, 2014 23:04
-
No static fire completed yet. She's being somewhat naughty on the pad. Waiting to hear if they can still get an attempt in today.
(Update: Clearly not. We're asking if they will attempt again tomorrow).
-
#33
by
aleponcin
on 17 Dec, 2014 01:30
-
SPACEPORT MAGAZINE tweeted the following earlier this evening.
@Spaceport_Mag
The @SpaceX CRS-5 static fire was successful at 6:45 PM. This was an important step leading toward plan to launch at 1:22:13 pm ET Friday.
-
#34
by
Chris Bergin
on 17 Dec, 2014 01:33
-
SPACEPORT MAGAZINE tweeted the following earlier this evening.
@Spaceport_Mag
The @SpaceX CRS-5 static fire was successful at 6:45 PM. This was an important step leading toward plan to launch at 1:22:13 pm ET Friday.
SpaceX isn't saying that and it's their rocket.
-
#35
by
Carl G
on 17 Dec, 2014 02:46
-
Remember to use the correct threads. The ASDS coverage is in SpaceX reusable section.
-
#36
by
Chris Bergin
on 17 Dec, 2014 11:35
-
Here's where we are on this.
Static Fire scheduled for yesterday, but wasn't confirmed until we saw the vehicle on the pad.
Webcam feed was cut (as per usual), guarded by Gandalf (humorous), by the time they entered tanking.
Window was four hours, but we knew they could extend if required.
We know they had at least one good countdown but didn't get to ignition, OR didn't complete the static fire requirement. Now that times in with the above tweet about completing the static fire, so either that account heard the countdown, saw a puff, or classed that as complete - but I was getting notes it wasn't, per the Static Fire requirements. I *think* it's the only account classing it as a complete.
I was asking SpaceX for updates and they moved to a stance of saying they would let me know as soon as they had the Static Fire confirmation - which is usual and fine. SpaceX is very helpful towards us, but at the same time they are a commercial company and don't give running commentaries about their flows.
I asked again after we heard the Static Fire attempt didn't work out, and I was told they can't comment yet, but would when they would be able to.
Experience over previous Static Fires is they always say it's complete, when it's complete, within the hour. Usually a one liner, saying engines fired, initial data looks good, then they go into the LRR. That's all we need, so that's great. That didn't happen yesterday, with the final note saying they would let us know when they had more info.
So right now, until I'm officially told different, they didn't complete the Static Fire, and they will need to try again today if they are to protect the Friday launch attempt, I assume.
Personally I'd love it if someone turned around and provided official confirmation of a Static Fire, allowing us all to look forward to a Friday launch and a sporty core stage return, but I've covered enough of their Static Fires to know this one doesn't feel like it has been completed.
There's your update. If you want to discuss it, please use the discussion threads and I'll update this update thread when I know more.
-
#37
by
Kabloona
on 17 Dec, 2014 15:12
-
Update on the support vessel Go Quest:
After zigzagging at low speed all night just offshore of Jacksonville, Go Quest set a northeast course at 9 knots this morning at 7:00 am Eastern. The course appeared to be towards the designated landing zone. AIS contact was lost at 7:40, about 10 nm offshore. The crew may have turned off their AIS transponder to prevent tracking while at sea.
AIS contact with the ASDS tugboat Elsbeth III was also lost yesterday as she headed out of the port of Jacksonville.
-
#38
by
Chris Bergin
on 17 Dec, 2014 16:47
-
-
#39
by
chamann
on 17 Dec, 2014 18:06
-