Commiserations to our Russian colleagues - this is too bad.Re the debris risk - low perigee but intermediate apogee, so debris could be around for a few years and passing through ISS and HST altitude regimes.... not as bad as the Arabsat/Briz debris cloud in GTO but not great.On the plus side, the low orbit means the debris will be trackable so we'll know the scope of the problem if any.
Quote from: input~2 on 08/07/2012 09:49 amSo from http://www.ria.ru/science/20120807/718040335.html the first and second Briz-M burns were nominal (as confirmed from TM data) while the third burn did not occur and the stack is orbiting in the intermediate orbit 268 x 5000km x 49.9°Is there the provision to try to command the burn again (perhaps on a ground override command)?
So from http://www.ria.ru/science/20120807/718040335.html the first and second Briz-M burns were nominal (as confirmed from TM data) while the third burn did not occur and the stack is orbiting in the intermediate orbit 268 x 5000km x 49.9°
Russian Federal Mission with TELKOM 3 and EXPRESS MD2 Satellites AnomalyInvestigation Underway; Russian State Commission Established On 7 August at 1:32 a.m. local time, a Proton Breeze M vehicle carrying the Express MD2 and Telkom 3 satellites launched from the Baikonur Cosmodrome in Kazakhstan. The Proton M launch vehicle performed nominally, however, the Orbital Unit (OU), comprised of the Breeze M upper stage and the two spacecraft, did not properly reach its transfer orbit and was placed into an off-nominal intermediate orbit. The Aerospace Defense and Roscosmos, are currently monitoring the OU and efforts are now underway to establish contact with the Express MD2 and Telkom 3 satellites.An investigation into the anomaly began immediately. A Russian State Commission of inquiry has been established and is in the process of determining the reasons for the anomaly. ILS will release details when data become available. While this was a Russian Federal mission, ILS will form its own Failure Review Oversight Board (FROB) in parallel with the Russian State Commission. The FROB will review the commission’s final report and corrective action plan, in accordance with U.S. and Russian government export control regulations.ILS remains committed to providing reliable, timely launch services for all its customers. To this end, ILS will work diligently with its partner Khrunichev to return Proton to flight as soon as possible.Further updates will be provided on the investigation as they become available.
Quote from: Chris Bergin on 08/06/2012 02:05 pmDo we have any good info pages in English on the two satellites?And is this a Briz-M five burn profile?Four burnshttp://coopi.khrunichev.ru/main.php?id=595http://forum.nasaspaceflight.com/index.php?topic=27791.msg935671#msg935671Edit by input~2: correct coopi.khrunichev. ru link:http://coopi.khrunichev.ru/main.php?id=606
Do we have any good info pages in English on the two satellites?And is this a Briz-M five burn profile?
Launch time is 19:31 UTC.Delay was related to problems with Briz-M upper stage.
Anatoli Zak sent me this screenshot which shows there should have been five burns, not four as the official scheme showed.
USSTRATCOM confirms 4 objects in similar orbit(epoch: August 7, 1543UTC)Object A (38744) in 266.5 x 5012.5km x 49.91°Object B (38745) in 266.3 x 5013.1km x 49.91°Object C (38746) in 266.8 x 5015.7km x 49.91°Object D (38747) in 266.7 x 5017.6km x 49.91°
One note: this launch was intended to inject the payloads directly into GEO, not GTO; that is the only way for 2 payloads to fly on one Proton to GEO, they are launched mostly without prop.
Quote from: Nicolas PILLET on 08/07/2012 04:16 pmAnatoli Zak sent me this screenshot which shows there should have been five burns, not four as the official scheme showed.СобытиеВремя от КП, сек.ВремяUTCКлюч на старт-30006.08.201219:26:00КП-120с-12006.08.201219:29:00Готовность РБ-11306.08.201219:29:07ОТП-506.08.201219:30:55Переход Земля - борт-206.08.201219:30:58Команда на запуск ДУ 1-ой ступени-206.08.201219:30:58Разрешение регулирования тяги двигателей-206.08.201219:30:58Прорыв мембраны окислителя ДУ 1-ой ступени-206.08.201219:30:58Команда выхода ДУ 1-ой ступени на главную ступень тяги006.08.201219:31:00Контакт подъема006.08.201219:31:00...
Quote from: Stan Black on 08/07/2012 06:20 pmQuote from: Nicolas PILLET on 08/07/2012 04:16 pmAnatoli Zak sent me this screenshot which shows there should have been five burns, not four as the official scheme showed.СобытиеВремя от КП, сек.ВремяUTCКлюч на старт-30006.08.201219:26:00КП-120с-12006.08.201219:29:00Готовность РБ-11306.08.201219:29:07ОТП-506.08.201219:30:55Переход Земля - борт-206.08.201219:30:58Команда на запуск ДУ 1-ой ступени-206.08.201219:30:58Разрешение регулирования тяги двигателей-206.08.201219:30:58Прорыв мембраны окислителя ДУ 1-ой ступени-206.08.201219:30:58Команда выхода ДУ 1-ой ступени на главную ступень тяги006.08.201219:31:00Контакт подъема006.08.201219:31:00...So that's the official scheme with 4 Briz burns.I am puzzled by Anatoli Zak's screenshot: what are the TM data in the 3rd column, showing time tags for events which didn't occur??