Quote from: edkyle99 on 06/08/2012 01:56 pmFlightGlobal offers a balanced assessment, suggesting that the cause of the problem is more uncertain given the stuck arrays on Proton flights too.http://www.flightglobal.com/blogs/hyperbola/2012/06/speculation-that-intelsat-19-s.htmlIf the payload separation issue turns out to be a Sea Launch, or even a Proton, problem, I would have to reassess the "success/fail" calls on several launches. - Ed Kyle"explosion" might be the key word no?
FlightGlobal offers a balanced assessment, suggesting that the cause of the problem is more uncertain given the stuck arrays on Proton flights too.http://www.flightglobal.com/blogs/hyperbola/2012/06/speculation-that-intelsat-19-s.htmlIf the payload separation issue turns out to be a Sea Launch, or even a Proton, problem, I would have to reassess the "success/fail" calls on several launches. - Ed Kyle
Quote from: edkyle99 on 06/08/2012 03:45 amThe payload fairing is Boeing hardware, correct?Yes.It was really new for me: "But Celli said U.S. Air Force images of the satellite [Telstar 14] in orbit showed massive damage to the affected array, confirming that an explosion — which was picked up by Sea Launch sensors — had occurred"I wonder what does Mr. Celli think about SES-4 issues? Explosion under Proton-M fairing? Or something else?
The payload fairing is Boeing hardware, correct?
There seems to be growing suspicion that the Intelsat 19 solar array was somehow damaged by the Sea Launch payload fairing separation event.
FlightGlobal offers a balanced assessment
Wrong guess by Space News, it seems.
How about the fact that 75 LS 1300s have been launched to date but this has only happened on the two Sea Launch missions (of ten)? On the other hand, two of 32 SL launches had this issue. From a purely statistical standpoint, it seems more likely to be a rocket/fairing issue than a spacecraft.
Quote from: SIM city on 06/11/2012 01:09 pmHow about the fact that 75 LS 1300s have been launched to date but this has only happened on the two Sea Launch missions (of ten)? On the other hand, two of 32 SL launches had this issue. From a purely statistical standpoint, it seems more likely to be a rocket/fairing issue than a spacecraft.Telstar 14R had the same problem, and it flew on a Proton
Report for Thursday June 14http://www.intelsat.com/network/satellite/intelsat19/is19-mission-updates.aspThe south solar array panel on IS-19 was deployed on 12 June 2012, following four apogee maneuver firings on 11 June 2012. Currently, we are conducting tests to establish the performance, power level, structural integrity and operability of the south array panel. The Ku-band deflector deployment is scheduled for 18 July.
Deployed but damaged.
Space Systems/Loral said that, for its part, it noticed that the outer solar panel on the satellite, which was exposed to the sun after the fairing was jettisoned during the rocket’s in-orbit coast phase, was registering less power than expected even before the spacecraft was released by the rocket’s upper stage.
From the space news article...QuoteSpace Systems/Loral said that, for its part, it noticed that the outer solar panel on the satellite, which was exposed to the sun after the fairing was jettisoned during the rocket’s in-orbit coast phase, was registering less power than expected even before the spacecraft was released by the rocket’s upper stage.Sounds like physical damage to the panel(s) during the launch...
So what could cause an "explosive" pressure spike? A hole developing in the fairing at Max-Q? A sudden delamination of part of the fairing from trapped air? What on the satellite could cause this while only harming the solar arrays?
Quote from: LouScheffer on 06/19/2012 11:22 pmSo what could cause an "explosive" pressure spike? trapped air in the spacecraft
So what could cause an "explosive" pressure spike?