3
$\begingroup$

In the future(2019-2020), if the American portion of the ISS had an unstable hull breach or worse a sick astronaut and 4 people took to earth. Are Russians qualified to handle the American portion of the ISS? Since they depend on the American power supply.

$\endgroup$
4
$\begingroup$

The international partners of the ISS look after the parts of the station they made. This is done from the mission control centers on the ground. All ISS systems are monitored on the ground and are adjusted from there, usually the crew is only involved when maintenance and repairs are needed, or new components are being installed.

So, if an extremely unlikely incident incapacitated everyone except the Russians and they all left, Houston would continue to run the US orbital segment just as they do now. This service shows some of the readouts from the consoles at the Johnson Space Center. If they needed the remaining crew to help them, they would talk them through it. Cosmonauts tend to have an engineering background and speak English, and would already be familiar with the US side. It wouldn't be a problem.

It is hard to imagine how the ISS could lose contact with the ground without all crew being evacuated. Houston would always be in touch with a crew in such a situation, and would continue to coordinate with Mission Control at Korolev, ESA, and JAXA.

If we imagine a fictional scenario like a natural disaster or a war, in which Houston can't communicate with the ISS, then the Backup Control Center takes over. That center used to be Korolev in Moscow, but has now been switched to Marshall Space Flight Center in Huntsville, Alabama. During Hurricane Rita in 2005, Korolev was used to control the ISS for a brief time, but they no longer have that capability. If the BCC also lost contact with the ISS it is unclear what would happen. Continuous contact with the station would be lost if it was not possible to use NASA's Tracking and Data Relay Satellite System, and would be restricted to when the station is in view of a ground station.

$\endgroup$
  • $\begingroup$ As this happening happen in 2019 at times of dragon capusle. Russian are only left onboard the Russian iss and american iss is unoccupied $\endgroup$ – user16223 Jul 14 '16 at 23:15
  • $\begingroup$ @Dlord2 -- Huh? 2019 hasn't happened yet, nor has the manned Dragon. $\endgroup$ – David Hammen Jul 15 '16 at 4:04
  • 1
    $\begingroup$ The info in that document is quite outdated. The backup MCC is not in Russia now. Here's info on the backup MCC ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20100020234.pdf Also, to be clear, the Russian systems can't command to the US part of the ISS and vice versa. When the BCC was in Moscow, it only used the Russia comm infrastructure, which was (and is) extremely limited due to the fact that they only have ground stations (no TDRSS equivalent any more). So this comment "it makes sense to have given Korolev the software" is quite misleading, that never happened and won't. $\endgroup$ – Organic Marble Jul 25 '16 at 12:29
  • 1
    $\begingroup$ @OrganicMarble Thanks for passing that along, i made an edit to correct. Though i wonder what happened during Hurricane Rita then, as the doc says 'After using Russian Ground Services for commanding during Hurricane Rita in September 2005, it was determined that the BCC should be relocated to the HOSC'. That seems to imply the control programs were running at Korolev. $\endgroup$ – kim holder Jul 25 '16 at 15:24
  • 1
    $\begingroup$ Well, sorta, there was a small US control center set up in the MCC-M facility. But it was US machines and software. It only used the Russian comm assets. So if by "Korolev" you mean the building, then OK, if you mean MCC-M the computers & software, no, that cannot command to the US side of the ISS. If for no other reason, the classified command encryption software & hardware is certainly not going to be incorporated into any foreign machines. $\endgroup$ – Organic Marble Jul 25 '16 at 15:57

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy