|
m Changing "Soyuz TMA-M" into the currently "Soyuz MS". The recently MS-10 mission give us some base for the claim about the currently model.
|
|
||
| Line 12: | Line 12: | ||
The SAS can be used to separate the Soyuz capsule from the launch vehicle up to about two and half minutes into powered flight. The launch escape system can be triggered by onboard computers or by radio communication from ground crews. The onboard computers use instruments to detect several possible failures including premature separation of stages, loss of pressure in combustion chambers, and loss of control of the launch vehicle.<ref name = zak/> Once triggered, struts are deployed to secure the descent module to the orbital module until after the escape motors are burnt out and jettisoned. After this, the descent module is separated, its heat shield is jettisoned, and its parachutes are deployed.<ref name = 'spaceflight 101'/> |
The SAS can be used to separate the Soyuz capsule from the launch vehicle up to about two and half minutes into powered flight. The launch escape system can be triggered by onboard computers or by radio communication from ground crews. The onboard computers use instruments to detect several possible failures including premature separation of stages, loss of pressure in combustion chambers, and loss of control of the launch vehicle.<ref name = zak/> Once triggered, struts are deployed to secure the descent module to the orbital module until after the escape motors are burnt out and jettisoned. After this, the descent module is separated, its heat shield is jettisoned, and its parachutes are deployed.<ref name = 'spaceflight 101'/> |
||
|
Beginning with the [[Apollo-Soyuz Test Project]], the Soyuz spacecraft also has a secondary set of four rocket motors at the top of the fairing that can propel the escape head section away from the rocket during the period between the jettisoning of the SAS at T+115s until fairing deployment at T+157s. In contrast to the SAS these rockets only move the escape head section a small distance away from the rocket, as at these altitudes there is enough time for the landing system to deploy.<ref name="hall & shayler"/> |
||
===Other abort procedures=== |
===Other abort procedures=== |
||
In the event of catastrophic failure, the Soyuz spacecraft has a series of automated and semi-automated abort modes to rescue the crew. The abort systems have been refined since the first manned flights and all abort scenarios for the Soyuz MS are expected to be survivable for the crew.[1]
The Soyuz abort systems are especially complicated because of the modular design of the vehicle; only the middle descent module is designed to survive reentry, so in an emergency the orbital module and the descent module must be separated together (sometimes with the service module also attached) before the descent can be separated and orient itself for reentry. Other Soviet spacecraft, like the TKS, attempted similar modular designs with a hatch through the heat shield to resolve this issue.[2] The modular design also means that the Soyuz capsule is contained within a payload fairing for much of the flight and removing the fairing without collision in an emergency was another difficult issue that needed to be addressed.[3]
The primary abort system for use early in the flight is the Jettisonable Emergency Escape Head Section, known by its Russian abbreviation OGB SAS or just SAS. It is a launch escape system designed by a team from OKB-1 under Sergei Korolev's leadership.[3] The main SAS is a single solid rocket booster with several nozzles to control attitude, placed on top of the Soyuz capsule.[4]
The SAS can be used to separate the Soyuz capsule from the launch vehicle up to about two and half minutes into powered flight. The launch escape system can be triggered by onboard computers or by radio communication from ground crews. The onboard computers use instruments to detect several possible failures including premature separation of stages, loss of pressure in combustion chambers, and loss of control of the launch vehicle.[3] Once triggered, struts are deployed to secure the descent module to the orbital module until after the escape motors are burnt out and jettisoned. After this, the descent module is separated, its heat shield is jettisoned, and its parachutes are deployed.[1]
Beginning with the Apollo-Soyuz Test Project, the Soyuz spacecraft also has a secondary set of four rocket motors at the top of the fairing that can propel the escape head section away from the rocket during the period between the jettisoning of the SAS at T+115s until fairing deployment at T+157s. In contrast to the SAS these rockets only move the escape head section a small distance away from the rocket, as at these altitudes there is enough time for the landing system to deploy.[4]
In early Soyuz models there were two abort modes in the time ranging from the ejection of the launch escape system until orbit. One called for separation of only the upper two modules and a controlled descent and could be initiated before about T+522s, the other separated all three and underwent a ballistic descent after T+522.[4]
Unlike the space shuttle, Soyuz cannot abort-to-orbit because its third stage has only a single engine and does not carry the reserve fuel necessary to achieve orbit with reduced thrust at a lower stage.[4]
An analysis of the overall reliability of the Soyuz capsule was published in the years leading up to the retirement of the Space Shuttle in 2010 by individuals from NASA JSC and the ARES Corporation. The report concluded that the current manned Soyuz capsule has not been on enough flights to reliably measure the probability of a loss of mission, but that the overall history of the program shows that it performed roughly as reliably as other contemporary systems and that, while the number could be improved, significant improvement of reliability was not feasible with current technology.[5]
Following a malfunction in the central thrust chamber of the launch escape system when it was routinely jettisoned during the 2009 Soyuz TMA-15 launch, concerns were raised by officials with NASA and Russian organizations (including the Machine Building Central Research Institute) about the quality control and reliability of Soyuz emergency systems.[6]
Soyuz has experienced three launch aborts and one in-orbit abort. All crew members survived the aborts.
| Launch date | Mission | Cause of failure |
|---|---|---|
| 5 April 1975 | Soyuz 18a | Second stage separation failed prior to third stage ignition. The flight control computer detected a trajectory deviation and triggered an automated abort. Since the escape tower had already been jettisoned, the service module engines were used for the abort.[7] |
| 26 September 1983 | Soyuz T-10-1 | The rocket caught fire on the pad. The launch escape system was fired, pulling the spacecraft free two seconds before the rocket exploded. This is, to date, the only successful manned pad abort.[8] |
| 11 October 2018 | Soyuz MS-10 | An anomaly occurred around booster separation, affecting the first and second stages. Immediately following staging an abort was triggered, followed by capsule separation, ballistic reentry, and normal landing.[9] |
| Launch date | Mission | Cause of failure |
|---|---|---|
| 10 April 1979 | Soyuz 33 | The Igla docking system suffered an engine failure. After consideration by ground crews, the mission was aborted by firing the back up engines and initiating a ballistic reentry.[10] |
{{cite journal}}: Cite journal requires |journal= (help)
|
| |||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||
| Main topics |
|
| |||||||||||||||||||||||||
| Past missions (by spacecraft type) |
| ||||||||||||||||||||||||||
| Current missions |
| ||||||||||||||||||||||||||
| Future missions |
| ||||||||||||||||||||||||||
Uncrewed missions are designated as Kosmos instead of Soyuz; exceptions are noted "(uncrewed)". | |||||||||||||||||||||||||||
