Docking and berthing of spacecraft

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
200px
The free-flying Progress in the process of docking to the ISS
Dragon prior to being berthed to the ISS by the Canadarm2

Docking and berthing of spacecraft is the joining of two space vehicles. This connection can be temporary, or semipermanent such as for space station modules.

Docking specifically refers to joining of two separate free-flying space vehicles.[1][2][3][4] Berthing refers to mating operations where an inactive module/vehicle is placed into the mating interface of another space vehicle by using a robotic arm.[1][3][4] Because the modern process of un-berthing is manually laborious, berthing operations are seen as unsuited for rapid crew evacuations in the event of an emergency.[5]

Docking states

A docking/berthing connection is referred to as either "soft" or "hard". Typically, a spacecraft first initiates a soft dock by making contact and latching its docking connector with that of the target vehicle. Once the soft connection is secured, if both spacecraft are pressurized, they may proceed to a hard dock where the docking mechanisms airtightly seal together, enabling interior hatches to be safely opened so that crew and cargo can be transferred.

Docking of manned spacecraft

History

Lua error in package.lua at line 80: module 'strict' not found.

The first spacecraft docking was performed between Gemini 8 and an unmanned Agena Target Vehicle on March 16, 1966.

Spacecraft docking capability depends on space rendezvous, the ability of two spacecraft to find each other and station-keep in the same orbit. This was first developed by the United States for Project Gemini. It was planned for the crew of Gemini 6 to rendezvous and manually dock under the command of Wally Schirra, with an unmanned Agena Target Vehicle in October 1965, but the Agena vehicle exploded during launch. On the revised mission Gemini 6A, Schirra successfully performed a rendezvous in December 1965 with the manned Gemini 7, but there was no docking capability. The first docking with an Agena was successfully performed under the command of Neil Armstrong on Gemini 8 on March 16, 1966. Manual dockings were performed on three subsequent Gemini missions in 1966.

The Apollo program depended on lunar orbit rendezvous to achieve its objective of landing men on the Moon. This required first a transposition, docking, and extraction maneuver between the Apollo Command/Service Module (CSM) mother spacecraft and the Lunar Module (LM) landing spacecraft, shortly after both craft were sent out of Earth orbit on a path to the Moon. Then after completing the lunar landing mission, two astronauts in the LM had to rendezvous and dock with the CSM in lunar orbit, in order to be able to return to Earth. The spacecraft were designed to permit intra-vehicular crew transfer through a tunnel between the nose of the Command Module and the roof of the Lunar Module. These maneuvers were first demonstrated in low Earth orbit on March 7, 1969, on Apollo 9, then in lunar orbit in May 1969 on Apollo 10, then in six lunar landing missions.

The Soviet Union first achieved rendezvous of Soyuz 3 with the unmanned Soyuz 2 craft on October 25, 1968; docking was unsuccessfully attempted. The first Soviet docking was achieved on January 16, 1969, between the manned Soyuz 4 and manned Soyuz 5. This early version of the Soyuz spacecraft had no internal transfer tunnel, but two cosmonauts performed an extravehicular transfer from Soyuz 5 to Soyuz 4.

In the 1970s, the Soviets upgraded the Soyuz spacecraft to add an internal transfer tunnel and used it for their Salyut space station program. The United States docked its Apollo spacecraft to its Skylab space station. In July 1975, both nations docked an Apollo spacecraft with a Soyuz in the Apollo-Soyuz Test Project, using a specially designed docking module to accommodate the different docking systems and spacecraft atmospheres.

In the 1990s, the Russians demonstrated automated docking capability to allow unmanned cargo ships to ferry supplies to their Mir space station and the International Space Station.

Hardware

Androgyny

Docking/berthing systems may be either androgynous (ungendered) or non-androgynous (gendered), indicating which parts of the system may mate together.

Early systems for conjoining spacecraft were all non-androgynous docking system designs. Non-androgynous designs are a form of "gender mating"[2] where each spacecraft to be joined has a unique design ("male" or "female") and a specific role to play in the docking process. The roles cannot be reversed. Furthermore, two spacecraft of the same gender cannot be joined at all.

Androgynous docking (and later androgynous berthing) by contrast has an identical interface on both spacecraft. In an androgynous interface, there is a single design which can connect to a duplicate of itself. This allows system-level redundancy (role reversing) as well as rescue and collaboration between any two spacecraft. It also provides more flexible mission design and reduces unique mission analysis and training.[2]

List of mechanisms/systems

Image Name Method Internal crew transfer Notes Type
Gemini Docking Mechanism diagram view2.png Gemini Docking System Docking No Allowed the Gemini Spacecraft (active) to dock to the Agena target vehicle (passive). Non-Androgynous
65px65px Apollo Docking System Docking Yes Allowed the Command/Service Module (active) to dock to the Apollo Lunar Module[6] (passive) and the Skylab space station (passive). Was used to dock to the Docking Module adapter (passive) during the Apollo–Soyuz Test Project (ASTP), which enabled the crew to dock with a Soviet Soyuz 7K-TM spacecraft. It had a circular pass through diameter of 810 mm (32 in).[7][8] Non-Androgynous
Soyuz 7K-OK docking system drawing.png Original Russian probe and drogue docking system Docking No The original Soyuz "probe and drogue" docking system was used with the first generation Soyuz 7K-OK spacecraft from 1966 until 1970, in order to gather engineering data as a preparation for the Soviet space station program. The gathered data were subsequently used for the conversion of the Soyuz spacecraft – which was initially developed for the Soviet manned lunar program – into a space station transport craft.[1]

A first docking with two unmanned Soyuz spacecraft – the first fully automated space docking in the history of space flight – was made with the Kosmos 186 and Kosmos 188 missions on October 30, 1967.

 Non-Androgynous
Kontakt docking system.png Kontakt docking system Docking No Intended to be used in the Soviet manned lunar program to allow the Soyuz 7K-LOK ("Lunar Orbital Craft", active) to dock to the LK lunar lander (passive).[9] Non-Androgynous
Russian drogue.jpgRussian probe extended.jpg SSVP-G4000 Docking Yes SSVP-G4000 is also known more vaguely as the Russian "probe and drogue" or simply the "Russian Docking System" (RDS).[1][10] In Russian, SSVP stands for Sistema Stykovki i Vnutrennego Perekhoda, literally "System for docking and internal transfer".[11]

It was used for the first docking to a space station in the history of space flight, with the Soyuz 10 and Soyuz 11 missions that docked to the Soviet space station Salyut 1 in 1971.[1][10] The docking system was upgraded in the mid-1980s to allow the docking of 20 ton modules to the Mir space station.[11] It has a circular transfer passage that has a diameter of 800 mm (31 in) and is manufactured by RKK Energiya.[3][4][11]

The "probe and drogue" system allows visiting spacecraft using the "probe" docking interface, such as Soyuz, Progress and ATV spacecraft, to dock to space stations that offer a port with a "drogue" interface, like the former Salyut and Mir or the current ISS space station. There are in total four such docking ports are available for visiting spacecraft on the ISS; These are located on the Zvezda, Rassvet, Pirs and Poisk modules.[11] Furthermore, the "probe and drogue" system was used on the ISS to dock Rassvet semipermanently to Zarya.[1]

 Non-Androgynous
APAS-75 image cropped and rotated.jpg
 APAS-75 Docking Yes Used on the Apollo-Soyuz Test Project Docking Module and Soyuz 7K-TM. There were variations in design between the American and Soviet version but they were still mechanically compatible. Androgynous
APAS-89 forward docking mechanism on Kristall.jpgAPAS-89 active - drawing.png APAS-89 Docking Yes Used on Mir (Kristall,[9][12] Mir Docking Module), Soyuz TM-16,[9][12] Buran (was planned).[12] It had a circular transfer passage with a diameter of 800 mm (31 in).[1][3][4] Androgynous (Soyuz TM-16), Non-Androgynous (Kristall,[13] Mir Docking Module[14])
APAS-95 passive side.jpgAPAS-95 active side.jpg APAS-95 Docking Yes Used by Space Shuttle,[12] ISS (Zarya, Pressurized Mating Adapters). It has a circular transfer passage with a diameter of 800 mm (31 in).[1][3][4] It was manufactured by RKK Energiya and has been described as being "essentially the same as" APAS-89.[12] The androgynous variant had a mass of 286 kg.[15] Androgynous (Shuttle and PMA-1[1]), Non-Androgynous (PMA-2 and PMA-3)[1]
Passive hybrid docking system - from another angle.jpgISS S01 Pirs airlock cropped.jpg SSVP-M8000 (Hybrid Docking System) Docking Yes SSVP-M8000 or more commonly known as "hybrid", is a combination of a "probe and drogue" soft-dock mechanism with an APAS-95 hard-dock collar.[11] It began to be manufactured in 1996.[11] It is manufactured by RKK Energiya.[11]

Used on ISS (Connects Zvezda to Zarya, Pirs & Poisk)[1]

 Non-Androgynous
COTS2Dragon CBM.jpgCommon Berthing Mechanism with micrometeorite layer.jpg Common Berthing Mechanism Berthing Yes Used on ISS (USOS), MPLMs, HTV, Dragon Cargo,[16] Cygnus. The standard CBM has a pass through in the shape of a square with rounded edges and has a width of 1,300 mm (50 in).[4] The smaller hatch that Cygnus uses results in a transfer passage of the same shape but has a width of 940 mm (37 in).[17] Non-Androgynous
Chinese Docking Mechanism.jpg Chinese Docking Mechanism Docking Yes Used by Shenzhou spacecraft, beginning with Shenzhou 8, to dock to Chinese space stations. The Chinese docking mechanism is based on the Russian APAS-89/APAS-95 system, some have called it a "clone".[1] There have been contradicting reports by the Chinese on its compatibility with APAS-89/95.[18] It has a circular transfer passage that has a diameter of 800 mm (31 in).[19][20] The androgynous variant has a mass of 310 kg and the non-androgynous variant has a mass of 200 kg.[21]

Used for the first time on Tiangong 1 space station and will be used on future Chinese space stations and with future Chinese cargo resupply vehicles.

 Androgynous (Shenzhou)
Non-Androgynous (Tiangong-1)
NDS docking tests.jpg NASA Docking System Docking or Berthing Yes Used on the International Docking Adapter and on future US vehicles. Compliant with the International Docking System Standard. It has a circular transfer passage that has a diameter of 800 mm (31 in).[22] Androgynous (Commercial Crew Vehicle, Orion)
Non-Androgynous (IDA)
IBDM passive active.jpg International Berthing and Docking Mechanism Docking or Berthing Yes The European mating system is planned to be capable of docking and berthing large and small spacecraft.

The IBDM is designed to be compliant with the International Docking System Standard[22] (IDSS) and is hence compatible with the future ISS International Docking Adapter (IDA) on the US side of the ISS.[23] It has a circular transfer passage that has a diameter of 800 mm (31 in).[22]

The American company Sierra Nevada Corporation (SNC) is developing the Dream Chaser, which is a small reusable spacecraft that is a candidate to transport astronauts and/or crew to the ISS. The European Space Agency has started a cooperation with SNC to potentially provide the IBDM for attaching this new vehicle to the ISS in the future.[24]

 Androgynous

Adapters

A docking or berthing adapter is a mechanical or electromechanical device that facilitates the connection of one type of docking or berthing interface to a different interface. While such interfaces may theoretically be docking/docking, docking/berthing, or berthing/berthing, only the first two types have been deployed in space to date. Previously launched and planned to be launched adapters are listed below:

  • ASTP Docking Module

  • Pressurized Mating Adapter

  • International Docking Adapter

Docking of unmanned spacecraft

The Soft-Capture Mechanism (SCM) added in 2009 to the Hubble Space Telescope. The SCM allows both manned and unmanned spacecraft that utilize the NASA Docking System (NDS) to dock with Hubble.

For the first fifty years of spaceflight, the main objective of most docking and berthing missions was to transfer crew, construct or resupply a space station, or to test for such a mission (e.g. the docking between Kosmos 186 and Kosmos 188). Therefore, commonly at least one of the participating spacecraft was "manned", with a pressurized habitable volume (e.g. a space station or a lunar lander) being the target – the exceptions were a few fully unmanned Soviet docking missions (e.g. the dockings of Kosmos 1443 and Progress 23 to an unmanned Salyut 7 or Progress M1-5 to an unmanned Mir). Another exception were a few missions of the manned US Space Shuttles, like berthings of the Hubble Space Telescope (HST) during the five HST servicing missions.

This is changing, as a number of economically driven commercial dockings of unmanned spacecraft are planned starting as soon as 2015. In early 2011, two commercial spacecraft providers have announced plans to provide new autonomous/teleoperated unmanned resupply spacecraft for servicing other unmanned spacecraft. Notably, both of these servicing spacecraft will be intending to dock with satellites that were designed neither for docking, nor for in-space servicing.

The early business model for these services is primarily in near-geosynchronous orbit, although large delta-v orbital maneuvering services are also envisioned.[29]

Building off of the 2007 Orbital Express mission — a U.S. government-sponsored mission to test in-space satellite servicing with two vehicles designed from the ground up for on-orbit refueling and subsystem replacement — two companies have announced new commercial satellite servicing missions that will require docking of two unmanned vehicles.

The SIS and MEV vehicles will each use a different docking technique. SIS will utilize a ring attachment around the kick motor[33] while the Mission Extension Vehicle will use a somewhat more standard insert-a-probe-into-the-nozzle-of-the-kick-motor approach.[29]

A prominent spacecraft that received a mechanism for unmanned dockings is the Hubble Space Telescope (HST). In 2009 the STS-125 shuttle mission added the Soft-Capture Mechanism (SCM) at the aft bulkhead of the space telescope. The SCM is meant for unpressurized dockings and will be used at the end of Hubble's service lifetime to dock an unmanned spacecraft to de-orbit Hubble. The SCM used was designed to be compatible to the NASA Docking System (NDS) interface to reserve the possibility of a Multi-Purpose Crew Vehicle docked mission.[34] The SCM will, compared to the system used during the five HST Servicing Missions to capture and berth the HST to the Space Shuttle,[citation needed] significantly reduce the rendezvous and capture design complexities associated with such missions. The NDS bears some resemblance to the APAS-95 mechanism, but is not compatible with it.[35]

Non-cooperative docking

Docking with a spacecraft (or other man made space object) that does not have an operable attitude control system might sometimes be desirable, either in order to salvage it, or to initiate a controlled de-orbit. Some theoretical techniques for docking with non-cooperative spacecraft have been proposed so far.[36] Yet, with the sole exception of the Soyuz T-13 mission to salvage the crippled Salyut 7 space station, as of 2006, all spacecraft dockings in the first fifty years of spaceflight had been accomplished with vehicles where both spacecraft involved were under either piloted, autonomous or telerobotic attitude control.[36] In 2007, however, a demonstration mission was flown that included an initial test of a non-cooperative spacecraft captured by a controlled spacecraft with the use of a robotic arm.[37] Research and modeling work continues to support additional autonomous noncooperative capture missions in the coming years.[38][39]

Salyut 7 space station salvage mission

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Soyuz T-13
Commander Vladimir Dzhanibekov (left) with Oleg Grigoryevich Makarov (right) on a 1978 Soviet postage stamp
Doctor of technical sciences Viktor Savinykh with Vladimir Kovalyonok pictured on a Soviet postage stamp commemorating a Salyut 6 mission

Salyut 7, the tenth space station of any kind launched, and Soyuz T-13 were docked in what author David S. F. Portree describes as "one of the most impressive feats of in-space repairs in history".[9] Solar tracking failed and due to a telemetry fault the station did not report the failure to mission control while flying autonomously. Once the station ran out of electrical energy reserves it ceased communication abruptly in February 1985. Crew scheduling was interrupted to allow Russian military commander Vladimir Dzhanibekov[40] and technical science flight engineer Viktor Savinykh[41] to make emergency repairs.

All Soviet and Russian space stations were equipped with automatic rendezvous and docking systems, from the first space station Salyut 1 using the IGLA system, to the Russian Orbital Segment of the International Space Station using the Kurs system. The soyuz crew found the station was not broadcasting radar or telemetry for rendezvous, and after arrival and external inspection of the tumbling station, the crew judged proximity using handheld laser rangefinders.

Dzhanibekov piloted his ship to intercept the forward port of Salyut 7, matched the station's rotation and achieved soft dock with the station. After achieving hard dock they confirmed that the station's electrical system was dead. Prior to opening the hatch, Dzhanibekov and Savinykh sampled the condition of the station's atmosphere and found it satisfactory. Attired in winter fur-lined clothing, they entered the cold station to conduct repairs. Within a week sufficient systems were brought back online to allow robot cargo ships to dock with the station. Nearly two months went by before atmospheric conditions on the space station were normalized.[9]

Uncrewed dockings of non-cooperative space objects

Orbital Express: ASTRO (left) and NEXTSat (right), 2007.

Non-cooperative rendezvous and capture techniques have been theorized, and one mission has successfully been performed with uncrewed spacecraft in orbit.[37]

A typical approach for solving this problem involves two phases. First, attitude and orbital changes are made to the "chaser" spacecraft until it has zero relative motion with the "target" spacecraft. Second, docking maneuvers commence that are similar to traditional cooperative spacecraft docking. A standardized docking interface on each spacecraft is assumed.[42]

NASA has identified automated and autonomous rendezvous and docking — the ability of two spacecraft to rendezvous and dock "operating independently from human controllers and without other back-up, [and which requires technology] advances in sensors, software, and realtime on-orbit positioning and flight control, among other challenges" — as a critical technology to the "ultimate success of capabilities such as in-orbit propellant storage and refueling," and also for complex operations in assembling mission components for interplanetary destinations.[43]

The Automated/Autonomous Rendezvous & Docking Vehicle (ARDV) is a proposed NASA Flagship Technology Demonstration (FTD) mission, for flight as early as 2014/2015. An important NASA objective on the proposed mission is to advance the technology and demonstrate automated rendezvous and docking. One mission element defined in the 2010 analysis was the development of a laser proximity operations sensor that could be used for non-cooperative vehicles at distances between 1 metre (3 ft 3 in) and Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value).. Non-cooperative docking mechanisms were identified as critical mission elements to the success of such autonomous missions.[43]

Grappling and connecting to non-cooperative space objects was identified as a top technical challenge in the 2010 NASA Robotics, tele-robotics and autonomous systems roadmap.[44]

See also

References

  1. ↑ 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 2.2 Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ 3.0 3.1 3.2 3.3 3.4 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ 4.0 4.1 4.2 4.3 4.4 4.5 Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ http://www.nasaspaceflight.com/2015/02/astronauts-spacewalk-re-wire-iss-commercial-crew/
  6. ↑ History of U.S. Docking Systems (10/05/2010)
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ 9.0 9.1 9.2 9.3 9.4 Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ 11.0 11.1 11.2 11.3 11.4 11.5 11.6 Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ 12.0 12.1 12.2 12.3 12.4 Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Tests of new Dragon systems to begin minutes after launch, Stephen Clark, Spaceflight Now, 2012-05-21, accessed 2012-050-22.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ 22.0 22.1 22.2 Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ 25.0 25.1 25.2 Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ 27.0 27.1 Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ 29.0 29.1 29.2 29.3 Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ 36.0 36.1 Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ 37.0 37.1 Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ 43.0 43.1 Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
Retrieved from "https://infogalactic.com/w/index.php?title=Docking_and_berthing_of_spacecraft&oldid=722724040"