Recommended Posts

If I were one of their program managers I'd pulling my hair out by the roots, if they have any left.

http://www.spaceflightnow.com/proton/yamal402/failure.html

Russian satellite launch fails to reach proper orbit

The Russian space industry suffered another malfunction Saturday when the upper stage of the heavy-lift Proton rocket failed to perform the full duration of its final boost-burn, leaving a domestic telecommunications satellite in a lower-than-planned orbit at the end of a 9-hour flight from the Baikonur Cosmodrome.

Launch of the Yamal 402 spacecraft occurred at the precise moment of 1313:43 GMT (8:13:43 a.m. EST) atop the Proton M/Breeze M vehicle combination en route to geosynchronous transfer orbit.

The launch came just after sunset in temperatures just above the freezing mark, but the rocket rapidly disappeared into a low cloud deck within a few seconds of flight.

It was supposed to take 9 hours and 15 minutes to reach the ascent's completion, releasing the 9,839-pound satellite into an highly elliptical orbit expected to range from 4,642 miles at perigee to 22,181 miles at apogee and inclined 9 degrees to the equator.

Getting there began with the six main engines of the 191-foot-tall rocket blasting at liftoff to send the four-stage vehicle in the skies of Kazakhstan.

The lower three stages that comprised the Proton core vehicle sequentially fired through the initial 10 minutes of flight, leaving the Breeze M upper stage to step through four burns over the next several hours to achieve a preliminary parking orbit before heading into intermediate orbits to hit the geosynchronous transfer orbit.

Overseeing the mission was International Launch Services, the commercial marketer of Proton flights. ILS reported that the first three burns by the upper stage and jettison of the donut-shaped auxiliary fuel tank on the Breeze M had been performed, presumably putting the vehicle into a 317-mile by 22,147-mile orbit inclined 48 degrees to the equator within four hours of liftoff.

The rocket would then coast away from Earth for nearly five hours until the Breeze M would re-start its engine for a fourth and final burn of the day, raising the orbit's low point from 317 miles to 4,642 miles and bringing the inclination down from 48 degrees to 9 degrees relative to the equator where it ultimately would be stationed.

But instead of delivering nearly 9 minutes of propulsion as planned, the burn lasted several minutes short of that, leaving the satellite in the "off-nominal" orbit, according to a statement released by Proton rocket-builder Khrunichev.

International Launch Services did not issue a statement by press time. A company spokesperson did not respond to questions Saturday night.

Yamal 402 was supposed to maneuver itself into a circular geosynchronous orbit 22,300 miles up and lowering inclination where it can match Earth's rotation and appear parked over the equator at 55 degrees East longitude to begin a 15-year service life.

Whether the spacecraft has enough fuel to overcome the rocket problem and still have a sufficient reserve for its 15-year mission life was not immediately known Saturday.

>

>

Link to comment
https://www.neowin.net/forum/topic/1124582-another-russian-rocket-fail/
Share on other sites

Well, we came close ourselves recently when a Centaur 2nd stage had a failure that almost caused a satellite loss due to a significant reduction in thrust and a guidance problem. The investigation grounded both the Atlas-Centaur and Delta-Centaur launches and just concluded.

Result: there was a partial burn-through of the engine near the throat of the RL10 engines combustion chamber. This took out one of its surrounding fuel lines which leaked into the chamber, causing both a reduction in thrust and a thrust asymmetry that required constant course correction.

Centaur's guidance pulled it off, and the engine fortunately didn't totally blow.

Then there was the failure of a Merlin 1C engines fuel dome on the last Falcon 9 flight. Fortunatel F9 has 9 engines and each is surrounded by armor plates & blast blankets so the remaining 8 engines and the tanks were protected & survived. The multi-redundant flight computer corrected the course, lengthened the 1st stage burn, and the Dragon spacecraft got to the ISS 30 minutes early. Go figure.

Merlin 1C only has 1 more flight before it's replaced by the totally new Merlin 1D in a new & larger version of F9, so its risk factor is very reduced.

  • 2 months later...

Cause found, and once again it appears quality control related: a bearing failed in the oxidizer turbo-pump.

http://www.spaceflightnow.com/proton/yamal402/130212frob/

Commercial Proton flights cleared to resume in March

An anomaly during a December Proton rocket launch of a Russian communications satellite was caused by the failure of a bearing inside the launcher's Breeze M upper stage, ultimately causing the launcher to release its commercial payload in the wrong orbit, International Launch Services announced Tuesday.

Experts found the most probable root cause of the mishap was a "combination of adverse conditions" leading to the failure of a bearing inside the main engine of the launcher's Breeze M upper stage.

The Dec. 8 launch carried the Yamal 402 communications satellite for Gazprom Space Systems, a division of Russian oil and gas producer Gazprom.

After lifting off from the Baikonur Cosmodrome in Kazakhstan, the three-stage Proton rocket boosted a Breeze M upper stage and the Yamal 402 satellite on an arcing suborbital trajectory. The Breeze M engine was supposed to fire four times to place the payload in an elliptical transfer orbit.

But the Breeze M's fourth burn, which was scheduled to last nine minutes, ended about four minutes early when a bearing failed on the oxidizer side of the main engine's turbopump, according to engineers who examined data from the mission.

The "adverse conditions" affected the Breeze M during the start of the upper stage's third burn, but the engine bearing did not fail until the fourth burn about five hours later.

The upper stage deployed Yamal 402 in the wrong orbit, and the satellite used its own propulsion system to reach its operational position 22,300 miles over the equator. But the satellite used more fuel than originally planned, shortening its projected lifetime from 15 years to 11 years, according to industry sources.

A Russian board of inquiry finished its investigation into the mishap in January, and U.S.-based International Launch Services, which manages commercial Proton/Breeze M missions, convened an oversight committee to review the results.

The ILS oversight board agreed with the Russian commission and approved plans to resume commercial Proton/Breeze M launches in March.

The Dec. 8 launch mishap marked the third problematic Proton/Breeze M launch since August 2011.

>

  • 3 months later...

http://www.sea-launch.com/missions-q11349-Failure_Review_Oversight_Board.aspx

Failure Review Oversight Board

Following the unsuccessful launch of the SL-48 mission on January 31, 2013, Sea Launch and Energia Logistics Ltd. (ELUS) formed 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 is 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.

ELUS has secured the participation of various technical consultants to support the FROB review, who encompass broad knowledge and extensive experience with launch vehicle technical and program matters (including prior Sea Launch experience), as well as subject matter expertise. In addition, customer participants from three global satellite operators participated in the FROB review.

On April 25, 2013, the FROB completed its review of investigations into the failed launch attempt. The investigations into the cause of the failure covered the entire Sea Launch complex to ensure all contributors to the failure were properly identified.

The investigations isolated the failure to the Zenit-3SL first stage hydraulic power supply unit (BIM) used to pressurize the RD-171M main engine gimbal actuators. No additional contributors to the failure were found. The BIM failed approximately 3.9 seconds into the flight due to the abnormal performance of the pump that?s function is to pressurize the hydraulic oil supplied to the RD-171M main engine gimbal actuators. The pump failure was the result of contributing factors associated with a pump manufacturing process that proved difficult to control.

The FROB confirms that the investigation has properly identified the cause of the failure and that the identified corrective actions will eliminate the possibility of recurrence going forward. Pending implementation of the identified corrective actions, the Sea Launch Zenit 3SL is ready to return to flight.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
    • Tor Browser 15.0.17 by Razvan Serea Protect your privacy. Defend yourself against network surveillance and traffic analysis. Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. The Tor software protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody from watching your Internet connection and learning what sites you visit, it prevents the sites you visit from learning your physical location, and it lets you access sites which are blocked. The Tor Browser Bundle lets you use Tor on Windows, Mac OS X, or Linux without needing to install any software. It can run off a USB flash drive, comes with a pre-configured web browser to protect your anonymity, and is self-contained. Tor Browser 15.0.17 changelog: All Platforms Updated Tor to 0.4.9.11 Updated NoScript to 13.6.25.1984 Build System / All Platforms Bug tor-browser-build#41821: Update gpg subkeys for boklm Bug tor-browser-build#41827: Update morgan's keychain with renewed key Download: Tor Browser (64-bit) | Tor Browser (32-bit) | 109.0 MB (Open Source) View: Tor Browser Website | Other Operating Systems Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!