The launch is planned at 03:34 UTC on May 14th.
Quote from: anik on 03/30/2011 05:47 pmThe launch is planned at 03:34 UTC on May 14th.Anyone have any data on the 2.1A launcher for this launch? Has it been delivered yet?Thanks,PCSTEL
Rumor circulating that the May 14th launch is now delayed?
I was told that the problem is linked to the inertial wheels.
I was told that satellites will be returned to Baikonur on May 22nd and the launch is planned on July 3rd.
Live video feed http://www.videocorner.tv/index.htm
Hoping Chris won't ban me for this... Nice music too...
Well, that's a downer. No actual webcast.
Well, that's a downer. No live video footage due to equipment failures...
Heh, scrub with seconds to go
Be carefull if you post here, Chris might ban you for not paying enough attention to the shuttle!
Thanks Ian. Can any confirm if they've not updated that page, or if they have postponded today/tonight's attempt?
Quote from: Chris Bergin on 07/11/2011 11:53 pmThanks Ian. Can any confirm if they've not updated that page, or if they have postponded today/tonight's attempt?EDIT: A friend said it was counting down again after the scrub.
I tell you what, if you click the webcast player you get one of the most epic promos ever. What a wonderful advert for Arianespace. "Human Connection" - the launch segment is absolutely beautiful.
Found it on youtube, with only 700 views. Will give it a thread of it's own. Super impressive.
Else, the launcher will have to go back to MIK for reprocessing (AFAIU it cannot remain more than 3 days on pad once it has been filled).
Quote from: Space Lizard on 07/12/2011 04:10 amElse, the launcher will have to go back to MIK for reprocessing (AFAIU it cannot remain more than 3 days on pad once it has been filled).Is the Soyuz fueled during all of this? Or were you talking about something besides the main fuel tanks that were "filled"?
So shall we try again with one?
Streams online here: mms://wms.190E.edgecastcdn.net/20190E/AE_VA_IP203Just a counting clock for now.
Quote from: Mapperuo on 07/12/2011 11:39 pmStreams online here: mms://wms.190E.edgecastcdn.net/20190E/AE_VA_IP203Just a counting clock for now.And for those wondering, it's at t- 1hr5min and counting, so no need to open yet
Hope they've fixed their video equipment this time...
Quote from: Jason1701 on 07/12/2011 02:40 pmQuote from: Space Lizard on 07/12/2011 04:10 amElse, the launcher will have to go back to MIK for reprocessing (AFAIU it cannot remain more than 3 days on pad once it has been filled).Is the Soyuz fueled during all of this? Or were you talking about something besides the main fuel tanks that were "filled"?Yes, I think the kerosene is left on board in the event of a delay.
Webcast going on hold for now until spacecraft separation.
Webcast ending.
Seven objects are currently being tracked in the 900 km orbit, 2011-33A to 33F or 37739 to 37745. It was expected that only the 6 payloads would be in this orbit, and the Fregat stage would have been deorbited by now. It's possible that the Fregat deorbit burn failed, or that one of the objects in the catalog is a tracking error - I am suspicious of the element sets attributed to 37744. Should become more clear in a few days.
Quote from: jcm on 07/15/2011 02:16 amSeven objects are currently being tracked in the 900 km orbit, 2011-33A to 33F or 37739 to 37745. It was expected that only the 6 payloads would be in this orbit, and the Fregat stage would have been deorbited by now. It's possible that the Fregat deorbit burn failed, or that one of the objects in the catalog is a tracking error - I am suspicious of the element sets attributed to 37744. Should become more clear in a few days.Indeed, 37744 hasn't had any recent element sets and I suspect it is a mistake.Does anyone know the Fregat serial for this launch? (Andrey? Stan? hello? :-))
Quote from: jcm on 07/15/2011 02:16 amSeven objects are currently being tracked in the 900 km orbit, 2011-33A to 33F or 37739 to 37745. It was expected that only the 6 payloads would be in this orbit, and the Fregat stage would have been deorbited by now. It's possible that the Fregat deorbit burn failed, or that one of the objects in the catalog is a tracking error - I am suspicious of the element sets attributed to 37744. Should become more clear in a few days.Indeed, 37744 hasn't had any recent element sets and I suspect it is a mistake.
Quote from: jcm on 07/16/2011 07:16 pmQuote from: jcm on 07/15/2011 02:16 amSeven objects are currently being tracked in the 900 km orbit, 2011-33A to 33F or 37739 to 37745. It was expected that only the 6 payloads would be in this orbit, and the Fregat stage would have been deorbited by now. It's possible that the Fregat deorbit burn failed, or that one of the objects in the catalog is a tracking error - I am suspicious of the element sets attributed to 37744. Should become more clear in a few days.Indeed, 37744 hasn't had any recent element sets and I suspect it is a mistake.An alternate explanation is that 37744 de-orbited after 14 or so orbits.
Quote from: PCSTEL on 04/01/2011 05:13 pmQuote from: anik on 03/30/2011 05:47 pmThe launch is planned at 03:34 UTC on May 14th.Anyone have any data on the 2.1A launcher for this launch? Has it been delivered yet?Thanks,PCSTELThis message implies the answer is yes:http://forum.nasaspaceflight.com/index.php?topic=17286.msg708688#msg708688
Quote from: Danderman on 07/16/2011 10:04 pmQuote from: jcm on 07/16/2011 07:16 pmQuote from: jcm on 07/15/2011 02:16 amSeven objects are currently being tracked in the 900 km orbit, 2011-33A to 33F or 37739 to 37745. It was expected that only the 6 payloads would be in this orbit, and the Fregat stage would have been deorbited by now. It's possible that the Fregat deorbit burn failed, or that one of the objects in the catalog is a tracking error - I am suspicious of the element sets attributed to 37744. Should become more clear in a few days.Indeed, 37744 hasn't had any recent element sets and I suspect it is a mistake.An alternate explanation is that 37744 de-orbited after 14 or so orbits.True - although I think at least the third elset is actually a ghost of 37745Fregat was expected to deorbit much sooner than that, based on the previous flight. Thanks for pointing out Rui's scoop on the Fregat number!