Soyuz-2 (ST-A / ST-B) | |||||||||||||||||||||||||||||||||||||||||||||
Function: | Medium-lift launch vehicle | ||||||||||||||||||||||||||||||||||||||||||||
Manufacturer: | Progress Rocket Space Centre | ||||||||||||||||||||||||||||||||||||||||||||
Country-Origin: | Russia | ||||||||||||||||||||||||||||||||||||||||||||
Cpl: | [1] | ||||||||||||||||||||||||||||||||||||||||||||
Stages: | 3 or 4 | ||||||||||||||||||||||||||||||||||||||||||||
Capacities: |
| ||||||||||||||||||||||||||||||||||||||||||||
Family: | Soyuz-2 (R-7) | ||||||||||||||||||||||||||||||||||||||||||||
Status: | Suspended | ||||||||||||||||||||||||||||||||||||||||||||
Sites: | Guiana Space Centre, ELS | ||||||||||||||||||||||||||||||||||||||||||||
Launches: | 27 | ||||||||||||||||||||||||||||||||||||||||||||
Success: | 26 | ||||||||||||||||||||||||||||||||||||||||||||
Partial: | 1 | ||||||||||||||||||||||||||||||||||||||||||||
First: | 21 October 2011 [3] | ||||||||||||||||||||||||||||||||||||||||||||
Last: | 10 February 2022 | ||||||||||||||||||||||||||||||||||||||||||||
Stagedata: |
|
Soyuz at the Guiana Space Centre was a European Space Agency (ESA) programme that operated Soyuz-2 launch vehicles at the Guiana Space Centre (CSG). It provided Arianespace with a medium-lift launch vehicle alongside the light-lift Vega and heavy-lift Ariane 5.[4] The rocket was marketed by Starsem a joint venture of ArianeGroup, Arianespace, Progress Rocket Space Centre and Roscosmos.
Launched in 2002, the project involved collaboration with Russia in two key areas: building a launch site at the CSG for Soyuz and modifying the launch vehicle to handle the tropical climate. A formal agreement was signed in 2003, with funding and final approval granted in 2005. Construction of the Ensemble de Lancement Soyouz (ELS;) began in 2005 and was completed in early 2011.
In its standard configuration, Soyuz-2 is a three-stage launch vehicle designed for low Earth orbit missions. Notably, its stage numbering differs from some rockets. The boosters are considered its the first stage, while the central core is the second. For higher orbits, an optional Fregat upper stage could be added. A total of 27 Soyuz-2 vehicles were launched from the CSG between 2011 and February 2022, with 26 successes and one partial failure (Flight VS09). While most missions at the CSG used the ST-B variant of the Soyuz-2 with a more powerful third stage, nine used the ST-A variant.
Soyuz launches from the CSG were suspended indefinitely in 2022 following Russia's invasion of Ukraine. Additionally, with the introduction of the Vega C and Ariane 6 launchers, both offering medium-lift capabilities, the role previously filled by Soyuz has become largely redundant.
To accommodate the conditions and requirements of the CSG, Soyuz rockets underwent several key modifications. These adaptations ensure the vehicle's optimal performance and safety within the tropical environment.
Soyuz rockets arrive at the CSG by ship, where components are offloaded and stored for assembly. In preparation for launch, these components are transferred to the temperature-controlled Launch Vehicle Integration (LVI) Building. Here, in a horizontal orientation, the four strap-on boosters are attached to the core stage, followed by the third stage. Several days before launch, a dedicated transporter moves the assembled Soyuz stages from the LVI Building to the launchpad. At the pad, the launch vehicle is erected into a vertical position, and the mobile service tower is moved into place.
Concurrently, within the Payload Processing Facility (PPF) clean room, customer teams prepare their spacecraft. The day before leaving the PPF, the spacecraft is integrated with an adapter/dispenser. This assembly is then transferred to the S3B building, where the fueled Fregat upper stage awaits. Here, the spacecraft and Fregat are integrated and encapsulated within the payload fairing.
Everything comes together on the third day prior to launch when the mobile service tower lifts the encapsulated spacecraft and Fregat upper stage, positioning them atop the Soyuz launch vehicle. Finally, approximately one hour before launch commences, the mobile service tower is meticulously retracted, readying the Soyuz for its mission.[6] [7] [8] [9]
The first contract for the launch of Soyuz the CSG was signed at the 2009 Paris Air Show by the Director of the Galileo Programme and Navigation-related Activities René Oosterlinck and a CEO of Arianespace Jean-Yves Le Gall. This contract covered 2 launches of two Galileo satellites each.[10] The contract for the satellites themselves had already been signed by ESA and Galileo Industries in 2006.[11]
Launch vehicle components shipped from Saint Petersburg first arrived in French Guiana by ship in November 2009.[12] The Soyuz Launch Site acceptance review took place during the last week of March 2011, leading to the first simulated launch campaign between 29 April and 4 May 2011.[13] [14] The launch site was officially handed over from ESA to the Arianespace on 7 May 2011.[15]
Assembly of the Soyuz ST-B begun on 12 September 2011 in the Assembly and Testing building, while two Galileo satellites underwent final tests after their arrival from Thales Alenia Space facilities in Italy on 7 and 14 September 2011.[16] The launch was planned for 20 October 2011, however an anomaly was detected in the pneumatic system responsible for disconnecting the fuel lines from Soyuz third stage, forcing the mission to be postponed for 24 hours. On 21 October 2011, at 10:30 UTC, Soyuz ST-B took off for its inaugural, 3 hour 49 minute, flight,[17] making it the first time Soyuz was launched outside of the former Soviet Union territory.[18]
On 22 August 2014, Arianespace launched the first two Full Operational Capability satellites for the Galileo satellite navigation constellation into medium Earth orbit. The mission appeared to proceed normally and Arianespace reported the launch to be a success, however analysis of telemetry data provided by ESA and CNES tracking stations showed that the satellites were injected into an incorrect orbit.[19]
Orbit | Eccentricity | |||
---|---|---|---|---|
Targeted | 23,222 × 23,222 km | ° | 0.00 | |
Achieved | 25,900 × 13,713 km | ° | 0.23 |
The orbit was determined by the European Space Operations Centre within 3 hours after the separation from launcher, and the satellites were operating normally and under control.[20] Both satellites were switched to safe mode, pointing at the sun while both ESA/CNES and OHB teams investigated the failure and options for the satellites.[21]
On 25 August 2014, Arianespace announced the creation of an independent inquiry commission to investigate the anomaly.[22] On 28 August 2014, details emerged on the events that most likely led to a failure of the Fregat upper stage. At the end of the re-orientation phase the flight control system detected an incorrect angular speed and unsuccessfully attempted to use thrusters to correct the situation. The flight control system did not detect the thruster issue and continued the flight plan with the upper stage oriented in a wrong direction, leaving the satellites in an incorrect orbit.[23]
In late September 2014, the Roscosmos commission report, quoted by Izvestia, indicated that the Fregat failure was due to a design flaw leading to freezing in one of the hydrazine propellant lines, which was placed alongside a line carrying cold helium used for pressurization of the main propellant tanks. During the long first burn required for Galileo orbital insertion the propellant line was cooled to below the freezing point of hydrazine. Further investigations were focused on the software error and a means to prevent similar failures in future. Izvestia also reported that the failure of flight VS09 caused a serious reaction in Russian government. Oleg Ostapenko, head of Roscosmos, had a "difficult conversation in the (Moscow) White House".[24] [25]
On 7 October 2014, the Independent Inquiry Board announced the conclusions of its investigation, revealing that a proximity of helium and hydrazine feed lines resulted in a thermal bridge that caused an interruption of propellant supply to the thrusters. Ambiguities in the design documents allowing this to happen were a result of not taking into account thermal transfers in the thermal analyses of the stage system design. The Board recommended 3 corrective actions: Revamping thermal analysis, correcting design documents and modification of manufacture, assembly, integration and inspection procedures of the supply lines.[26]
In November 2014, ESA announced the satellites would perform a total of 15 orbital maneuvers to raise their perigee to 17,339 km. This would reduce the satellites' exposure to the Van Allen radiation belt, reduce the doppler effect, increase satellite visibility from the ground, and allow the satellites to keep their antennas pointed at Earth during perigee. These orbits would repeat the same ground track every 20 days, allowing synchronization with other Galileo satellites which repeat the same ground track every 10 days. Once in their new orbits the satellites could begin in-orbit testing.[27]
Recovery of the satellites concluded in March 2015, when Galileo-FOC FM2 entered a new orbit, mirrored to the orbit of Galileo-FOC FM1, which concluded its manoeuvres on the end of November 2014 and successfully passed testing. Currently satellites overfly the same location on the ground every 20 days, comparing to 10 days of standard Galileo satellites.[28]
Flight | Launch (UTC) | Payload | Payload mass | Orbit | Config. | Upper | Result | ||
---|---|---|---|---|---|---|---|---|---|
VS01 | 21 October 2011, 10:30:00 | Soyuz ST-B | Fregat-M | ||||||
VS02 | 17 December 2011, 02:03:08 | Soyuz ST-A | Fregat-M | [29] | |||||
VS03 | 12 October 2012, 18:15:01 | Soyuz ST-B | Fregat-MT | [30] | |||||
VS04 | 2 December 2012, 02:02:51 | Soyuz ST-A | Fregat | [31] | |||||
VS05 | 25 June 2013, 19:27:03 | O3b F1 | Soyuz ST-B | Fregat-MT | [32] | ||||
VS06 | 19 December 2013, 09:12:19 | Soyuz ST-B | Fregat-MT | [33] | |||||
VS07 | 3 April 2014, 21:02:26 | Soyuz ST-A | Fregat-M | [34] | |||||
VS08 | 10 July 2014, 18:55:56 | O3b F2 | Soyuz ST-B | Fregat-MT | [35] | ||||
VS09 | 22 August 2014, 12:27:11 | Soyuz ST-B | Fregat-MT | [36] [37] | |||||
VS10 | 18 December 2014, 18:37:00 | O3b F3 | Soyuz ST-B | Fregat-MT | [38] | ||||
VS11 | 27 March 2015, 21:46:18 | Soyuz ST-B | Fregat-MT | [39] | |||||
VS12 | 12 September 2015, 02:08:10 | Soyuz ST-B | Fregat-MT | [40] | |||||
VS13 | 17 December 2015, 11:51:56 | Soyuz ST-B | Fregat-MT | [41] | |||||
VS14 | 25 April 2016, 21:02:13 | Soyuz ST-A | Fregat-M | [42] [43] | |||||
VS15 | 24 May 2016, 08:48:43 | Soyuz ST-B | Fregat-MT | [44] | |||||
VS16 | 28 January 2017, 01:03:34 | Soyuz ST-B | Fregat-MT | ||||||
VS17 | 18 May 2017, 11:54:53 | Soyuz ST-A | Fregat-M | [45] | |||||
VS18 | 9 March 2018, 14:10:06 | O3b F4 | Soyuz ST-B | Fregat-MT | [46] | ||||
VS19 | 7 November 2018, 03:47:27 | MetOp-C | Soyuz ST-B | Fregat-M | [47] [48] | ||||
VS20 | 19 December 2018, 16:37:14 | CSO-1 | Soyuz ST-A | Fregat-M | [49] | ||||
VS21 | 27 February 2019, 21:37:00 | OneWeb F6 | Soyuz ST-B | Fregat-MT | [50] | ||||
VS22 | 4 April 2019, 17:03:37 | O3b F5 | Soyuz ST-B | Fregat-MT | |||||
VS23 | 18 December 2019, 08:54:20 | Soyuz ST-A | Fregat-MT | [51] | |||||
VS24 | 2 December 2020, 01:33:28 | FalconEye-2 | Soyuz ST-A | Fregat-M | [52] | ||||
VS25 | 29 December 2020, 16:42:07 | Soyuz ST-A | Fregat-M | [53] | |||||
VS26 | 5 December 2021, 00:19:20 | Soyuz ST-B | Fregat-MT | [54] | |||||
VS27 | 10 February 2022, 18:09:37 | OneWeb F13 | Soyuz ST-B | Fregat-MT | [55] |
Typically, operations 3 days before launch include countdown rehearsal for all stages as well as final preparations and verification of the Fregat upper stage. Two days before launch preparations for fueling begin. This is also the last day when pre-launch activity with the payload can occur.[56] The launch sequence is optimized for each mission, the sequence described here is based on flight VS07 which lifted the Sentinel-1A satellite:[57] [58]
Clock | Event | Altitude | |
---|---|---|---|
T− 06:30:00 | Mission control team B on a console, beginning of a network countdown | ||
T− 04:50:00 | State Commission meeting giving fueling authorization | ||
T− 04:00:00 | Beginning of fueling | ||
T− 03:00:00 | Payload switched to pre-launch mode | ||
T− 02:20:00 | Readiness report | ||
T− 01:45:00 | End of fueling | ||
T− 01:21:00 | GO / NO-GO roll-call | ||
T− 01:00:00 | Mobile gantry withdrawal | ||
T− 00:10:00 | Payload switches to onboard power supply | ||
T− 00:06:10 | Beginning of autosequence | ||
T− 00:05:00 | Fregat switches to onboard power supply | ||
T− 00:01:00 | Activation of automatic launch sequence | ||
T− 00:00:40 | Launcher switches to onboard power supply | ||
T− 00:00:20 | Lower stage umbilical mast withdrawal | ||
T− 00:00:17 | Main engine ignition | ||
T− 00:00:15 | Preliminary thrust level | ||
T− 00:00:03 | Maximum thrust level | ||
T+ 00:00:00 | Liftoff | ||
T+ 00:01:11 | Max Q | ||
T+ 00:01:58 | Boosters separation | ||
T+ 00:03:29 | Fairing separation | ||
T+ 00:04:47 | 2nd stage separation | ||
T+ 00:04:48 | 2nd stage ignition | ||
T+ 00:04:53 | Aft section separation (connects 1st with 2nd stage) | ||
T+ 00:08:46 | Fregat upper stage separation | ||
T+ 00:09:46 | Fregat ignition | ||
T+ 00:20:04 | Fregat shutdown | ||
T+ 00:23:29 | Payload separation |