Launch News (FAILURE) Zenit-3SL with Intelsat 27, February 1, 2013

Well, there is no way that 6 knots winds have caused this. I've been sailing a bit and this is hardly enough to power a small sailboat. And usually, winds gusts peak at 50% of the wind speed, so that would make 9 knots. I call this a gentle sea breeze.

Exactly. Just 6 knots can't explain this - and it also can't explain what we can see in the video during the final minute before launch and during lift-off.
 
Well, I guess we have to wait the inquiry results :shrug:

Another bad blow for SeaLaunch.
 
The engine's manufacturer says the engine is not at blame:

http://www.militarynews.ru/fcl_l/news.asp?id=305282

Vladimir Solntsev, CEO of Energomash, says:

"The engine was working absolutely normally. We had okay launch sequence, 20 seonds of nominal work, after which time an emergency shutdown program was initiated by the rocket's guidance system. We see no abnormality in our system".
 
Looks like the probable end of SeaLaunch, this was their last firm contract and they barely survived the last SeaLaunch failure.
 
This is the weather report at the launch site before launch:

IS27_Weather_Conditions.jpg

Same weather conditions as the Eutelsat 70B launch.... Looks that the weather is not the cause of the failure.

I think personally that there can 4 things what can cause this failure:

1. defect on there gimble('s)

2. Autopilot error

3. Rocket Power Level is less then 80% after a few seconds (What is unlikely)

4. Shutdown of the engine after 10-25 seconds of launch, caused by a error in the system of the Zenit-3SL rocket.
 
Last edited:
Typical Roscosmos.....

Oh this Roscosmos press release is classic! :lol:

A quick analysis of telemetry data received leads to a preliminary conclusion that the first-stage propulsion system and control system of the launch vehicle were operating normally.

Document review conducted during this day at the factory power plant (NGO "Energomash") and management systems (SPC AP) showed that there were no abnormalities in their production.

So what caused the rocket to pitch over? Tornadoes? Or the rocket made up its own mind to commit suicide? :rofl: :facepalm:
 
4. Shutdown of the 4 engines after 10-25 seconds of launch, caused by a error in the system of the Zenit-3SL rocket.

No no no :nono:, the RD-171 has 4 combustion chambers and 4 nozzles but is only 1 engine. Like on the R-7/Soyuz rocket.
 
No no no :nono:, the RD-171 has 4 combustion chambers and 4 nozzles but is only 1 engine. Like on the R-7/Soyuz rocket.

How the cow...how can I miss that, I must shame for my human mistakes :facepalm:

Thanks for the info BTW!
 
I work for BSSI's astrodynamics group and I can tell you that this came as a bit of a blow to my colleagues who spent many hours planning and rehearsing for this mission. RIP, IS-27. :(
 
Three Failures and one "launch anomaly" out of 35.
 
I can't read russian, what happened? Could someone please summerize the failure in english? Please!

1. This thing failed:
79ea8372e28ae0203be86200ac57c6975f49a7142474230.jpg

2. Nozzles could not gimbal due to loss of hydro pressure..
3. The guidance fell back to emergency withdrawal & shutdown mode after mandatory 20 seconds of thrusting necessary to clear the pad.
 
Thanks for the info. That's actually better than I thought. And those were actual launcher failures not separate satellite kick stage failures?


Bob Clark

January 30, 2007 NSS-8 launch failure

The launch anomaly "Telstar 18 was launched in June 2004 by Sea Launch. The upper stage of the rocket underperformed, but the satellite used its significant stationkeeping fuel margin to achieve its operational geostationary orbit. It has enough on-board fuel remaining to allow it to exceed its specified 13-year design life."

I cant find details on the other one at the moment.
 
Last edited:
Hydraulic problem makes sense, it explains why the rocket had a strong pitch seconds after takeoff.
 
I still think the Zenit will make my "favored" list of GWS launch vehicles. It has proven to be a good launch platform for light payloads.
 
Looks like it's indeed an engine gimballing problem per information from Sea Launch:

As a followup to the February 1st launch failure, Sea Launch can confirm the following information:

The Zenit-3SL successfully completed all pre-launch processing activities, with all systems and environments within requirements up to the on time liftoff at 6:54:59 UTC.
At approximately 11.4 seconds into flight, the Zenit flight control system detected an exceedance of a pre-programmed roll limit and responded appropriately with activation of the on-board thrust termination sequence, which is designed to ensure a safe outcome in the event of vehicle loss of control.
In accordance with the flight termination logic, RD-171M main engine thrust was terminated 20 seconds into flight, resulting in impact of the Zenit-3SL with the IS-27 spacecraft with the Pacific Ocean surface approximately 4 km from the Odyssey Launch Platform.

Nobody was injured and the Sea Launch vessels were not damaged in the incident. A search effort conducted this morning from the Sea Launch Commander-based helicopter identified no recoverable debris.



Based on preliminary information received from the launch vehicle designer, the investigation will focus on Zenit-3SL systems associated with thrust-vector control of the first stage engine. As per the Sea Launch Failure Review and Investigation Plan, each associate contractor will first perform an independent investigation of their respective systems, processes and procedures to identify any and all potential contributors to the failure.

Energia Logistics Ltd. (ELUS) will form a Failure Review Oversight Board (FROB) to review the contractor findings and agree on root cause and appropriate corrective actions to prevent recurrence. The FROB will be led by ELUS Chief Operating Officer Kirk Pysher, along with co-chairman Dr. Valery Aliev, ELUS Executive Vice President and Mission Director, and Rick Pudil, ELUS Chief Systems Engineer. The first meeting of the FROB is tentatively planned for late February to early March time frame.
 
Back
Top