Russian ground control and tracking network

At the dawn of Space Age, the Soviet Union has already had in place a network of ground control stations, allowing to communicate with the early spacecraft to send commands onboard and process the information received from orbit. As it was the case, with early space launchers, the Soviet command and control network owes its origin to the program of long-range ballistic missiles. The early ballistic missiles required radio commands to be sent onboard constantly to adjust their trajectories in flight.

Bookmark and Share

The origin of rocket and satellite tracking network

The development of the first intercontinental ballistic missile, the R-7, equipped with radio control, posed immediate challenge before its creators - the extensive network of "measurement stations" had to be deployed under the rocket path in order to determine the vehicle's speed and direction and send flight correction commands onboard.

In addition, a number of observation stations was required around the target range in Kamchatka Peninsula, where the missile's dummy warhead was expected to impact during test launches. As a result, two groups of command and control stations, known as IPs (from Russian "izmeritelny punkt" or measurement site), would be required. They would spread over a vast distance of more than 6,000 kilometers across the Soviet Union.

The construction of such a network became another unknown heroic feat for the Soviet military. Many installations of the network had to be built in the midst of virtually uninhabitable and hard-to-access wilderness, with no even basic accommodations. As it was typical for many Soviet military projects at the time, the government would spare no funds for the engineering infrastructure, but was slow to invest into residential housing.

The IP network for the R-7 program

A group of tracking stations responsible for the flight control of the R-7 missile was collectively know as the Taiga region. It included nine IP stations stretched downrange from the launch site in Tyuratam.

The second group of stations, known as the Kama region, were responsible for tracking of the warhead reentry over the target range in Kamchatka Peninsula. Both code-names of the regions -- Taiga (wild forests of Siberia) and Kama (a river in northern Russia) were designed to create a confusion about the actual location of the sites.

The original command and control station in the network, IP-1, was located at Site 18 of the NIIP-5 test range in Tyuratam (Kazakhstan) only about 1.5 kilometers behind the original launch pad for the R-7 rocket. The instruments of the IP-1 station were distributed over a distance of one kilometer along the ridge dominating the area.

Other IP stations were located symmetrically on both sides of the rocket's flight path, with even-numbered stations placed on the left side of the trajectory and odd-numbered stations deployed to the right from the path. Each pair of downrange stations in combination with the IP-1 was creating a giant triangle, and when including a flying rocket - a pyramid.

IP measurement station locations:

IP pair
Distance downrange Distance from flight path
IP-2, IP-3
25 - 35 kilometers
20 - 30 kilometers
IP-4, IP-5
104 - 120 kilometers
50 - 60 kilometers
IP-6, IP-7
500 kilometers
180 - 200 kilometers
IP-8, IP-9
730 - 800 kilometers
180 - 200 kilometers

In 1957, IP-4 and 5 stations had a staff around 13 officers and 25 soldiers. At the time, the IP-6 station was the biggest in the group, staffed by 38 officers and 139 soldiers.

At the same time, IP stations in the target area (Kama region) were located in two semicircles around projected impact point of the R-7 warhead. The original plans called for the construction of the station near the Pacific shore line, where their maintenance would be easier. However, when experiments showed the possibility of very poor signal during the warhead descent, the stations were planned closer to the target area.

The "internal semicircle" of the Kama Region included IP-15, 16 and 17 stations, which were located 36-57 kilometers from the target point. The "external semicircle" included IP-12, 13 and 14 stations, which were spread from 53 to 102 kilometers from the target.

NIP network

In 1956, the Soviet government approved the use of the R-7 missile for the launch of the artificial satellite. The special command and control infrastructure was now required to support the program. On May 8, 1957, the Soviet Ministry of Defense officially ordered to form a "Center on management and coordination of work of complex of means of measurements, communications and unified time service" and 13 detached Scientific Measurement Stations, or NIP. The purpose of the new organization was to control and communicate with the orbiting spacecraft.

The creation of the center was delegated to NII-4, the leading research institute of the Soviet Ministry of Defense. The center was conveniently located at NII-4 campus in the town of Bolshevo, just one train stop from the town of Podlipki, home of OKB-1, the R-7 developer. The center had a staff of 68 officers and 151 army employees.

The entire network was designated as Command and Measurement Complex, or KIK. Major General A. A. Vitruk became the first chief of the KIK network.

The original KIK network deployed by October 1957 included 13 NIP stations:

  • NIP-1 - Tyuratam, near already existing IP-1 in Area 18 (also known as IP-1D or v/ch 13986);
  • NIP-2 - Makat station (near the town of Guriev);
  • NIP-3 - Sary-Shagan 3 (also known as v/ch 14045) on the western coast of Lake Balkhash;
  • NIP-4 - Yeniseisk in Western Siberia;
  • NIP-5 - Iskhup;
  • NIP-6 - Yelizovo 6 (on Kamchatka Peninsula);
  • NIP-7 - Klyuchi (Barnaul);
  • NIP-8 - Bolshevo (northeast of Moscow);
  • NIP-9 - Krasnoe Selo 9 (near St. Petersburg);
  • NIP-10 - Simferopol (Crimean Peninsula);
  • NIP-11 - Cape Shartushalu near Tbilisi in Georgia;
  • NIP-12 - Novosibirsk (Kolpashevo) in Western Siberia;
  • NIP-13 - Ulan-Ude (east of Lake Baikal);

Tracking first Sputnik

All tracking of the rocket in flight had to be conducted passively by means of radar, without onboard response, and with the help of ground telescopes. Both optical and radar systems had a limited range and accuracy. Based on experience with the previous launch of the R-7 rocket, Binokl (binocular) tracking system was expected to see the rocket at the distance of up to 200 kilometers. The P-30 radar demonstrated an effective range of 500 kilometers, when tracking aircraft. Its effectiveness was further reduced by slow rotation of its antenna. Optical sensors KTh-41 and KT-50 available in Tyuratam had a range of 100-200 kilometers, also too short for effective tracking of a satellite. Two more powerful KST-80 instruments were available at IP-4 and IP-5 ground tracking stations. In the meantime, at the end of the powered flight, the rocket was expected to be 800 kilometers from the IP-1 station and 300 kilometers from the nearest tracking stations downrange from Tyuratam. When reaching orbit, the satellite would be 1,700 kilometers from the nearest tracking site.

Since ground-based tracking systems were limited, flight controllers had to rely on telemetry data from the Tral system in order to confirm the fact that the satellite reached orbit. If stabilization of the rocket would remain normal throughout powered flight and the command to cut off the engine would be issued within accepted time limits, launch officials could celebrate the success. Ultimately, the appearance of the radio signals from the satellite would confirm its release. While in orbit, telescopes of the Academy of Science and radio sensors would help to track the satellite.

To support first satellite launches, the Soviet government approved a number of upgrades to tracking facilities and to the hardware originally built for ballistic missile tests. As the original satellite development program was designated Object D, the index "D" was added to the names of systems supporting the mission. On the eve of the Sputnik launch only part of the tracking systems originally planned for the Object D project were ready for work. At the Tyuratam launch site, a special tracking station designated IP-1D was built next to the original IP-1 tracking site during July-August 1957. (70) It was equipped with P-30 and P-20 radar, the SON-2D angular coordinates guidance radar; radio range finder Binokl-D, which was serviced by the personnel from the nearby IP-1 tracking site under command of Lt. N. V. Sachko.

No satellite tracking stations, which were part of the KIK network at the time, were equipped with Tral systems, since originally scheduled for launch Object D was expected to carry a specialized RTS-8 system. Therefore all available technology was all but useless for tracking the first satellite. (51)

Tracking second Sputnik

To support the mission of the second satellite, two Tral telemetry trucks based at the IP-1 control station in Tyuratam along with power-generators, other support vehicles and their personnel were loaded on open railroad platforms and attached to passengers trains heading to the Soviet Far East. One unit led by Lt. Technician V. A. Solnyshkov was deployed in Ulan-Ude, another led by Lt. Technician V. A. Alekseev was stationed in Khabarovsk. In the meantime, back at IP-1, an experimental set of low-resolution Seliger TV receiver was installed in the hope of collecting moving images from the satellite. It was managed by Junior Lt. V. G. Borisov. (51)

Tracking Sputnik-3

The third Soviet satellite (Object D) would have a full complement of hardware for interaction with ground control. Its mission would be tracked by Tral stations in Tyuratam, and by field stations in Ulan-Ude (NIP-13) and from Khabarovsk. For the first time, a radar-based Binokl-D (binoculars) tracking and recording system and the MRV-2M mobile command radio-system (enabling sending commands to the satellite) were employed. Binokl's data would be fed into the Kvarts computer at five stations, which calculated the flight trajectory. (644)

During the testing of the MRV-2M command system in Tyuratam, its operators inadvertently sent commands to the satellite, while unsuspecting engineers were conducting tests on the spacecraft at the assembly building. To their surprise, the spacecraft suddenly started implementing commands. After realizing the source of the "external influence," the overly vigilant security personnel at the test range burst into the remote-control facility with allegations of sabotage! Fortunately, the incident was resolved without arrests. (537)

In order to automate the calculation of orbital parameters of Object-D in real time, in 1956, a department at Leningrad Polytechnic Institute, later known as OKB LPI, developed a system based on its Kvarts computer, which linked five tracking facilities in Tyuratam, Balkhash, Eniseisk, Makat and Kamchatka with a calculation center in Moscow. Each computer, fed with tracking data from its own Binokl-D radar, received information on range, angle and azimuth of the flying vehicle. The machine then processed data, averaging 128 different measurements taken by the radar and correlated it to the exact time. (51) A resulting data packet would then be transmitted to a calculation center, which could forecast the orbit in near-real time using the Strela-2 computer. All tracking data would be also recorded on magnetic media enabling its later retrieval in case of power interruption at field stations. (51)

Developments after Sputnik

In the following years, a number of additional ground control stations have been added into the network:

  • NIP-17 in Yakutsk in Eastern Siberia;
  • NIP-18 in Vorkuta in the Russian Far North to support space launches from Plesetsk, which both entered service in 1966;
  • NIP-19 in Dunaevtsu in Moldavia;
  • NIP-20 in Komsomolsk-na-Amure in the Russian Far East;
  • NIP-21 on the Mt. Maidanak in Uzbekistan;

In 1962, three additional NIP stations added into the network to support lunar program:

  • IP-14 in Shelkovo, east of Moscow; (later known as Medvezhi Ozera (Bear Lakes) complex). This particular site played especially crucial role in the post-Soviet Russia in controlling the Earth-orbiting and deep-space missions. In November 2012, a damaged cable near Shelkovskoe Shosse (Shelkovo highway) reportedly interrupted control over most Russian civilian satellites and the Russian segment of the ISS;
  • IP-41E on the southern slope of Koshka mountain near the town of Semeiz on Crimean Peninsula
  • IP-42E in Moscow

Also during 1962, deep space tracking facilities were introduced at IP-15 in Ussuriisk and IP-16 in Yevpatoria (Crimean Peninsula), while Saturn communication stations were added to IP-3, 4 and 14.

Saturn site upgrades

The Saturn tracking complex was also deployed at Site 23 in Tyuratam (later known as Baikonur Cosmodrome). The site, eventually designated IP-5, also received a 12-meter antenna for the Svyaznik (Communicator) complex designed to support Molniya communications satellites. In September 2011, on the eve of the Phobos-Grunt launch, the Svyaznik complex was upgraded to include the Spektr-Iks telemetry complex. Despite a relatively small size of the antenna, the latest highly sensitive hardware promised to enable the control of deep-space probes up to a distance of several million kilometers, according to Roskosmos.

Sea-based control stations

In 1960, as the Soviet space program was just taking off, a number of sea-based measurement stations were added to the NIP network. These stations were deployed onboard three oceangoing ships, named Krasnodar, Ilichevsk and Dolinsk. V.G. Bezborodov, the First Rank Captain, became the first chief of this command and control fleet.

During 1965 and 1966, Bezhitsa and Ristna command and control ships replaced older Krasnodar and Ilichevsk.

Five brand-new ships joined the command and control fleet in 1967:

  • Cosmonaut Vladimir Komarov
  • Kegostrov
  • Morzhovets
  • Nevel
  • Borovichi

Two more ships joined the fleet in 1970:

  • Academik Sergei Korolev
  • Cosmonaut Yuri Gagarin

Four ships entered service in 1975:

  • Cosmonaut Pavel Belyaev
  • Cosmonaut Vladimir Volkov
  • Cosmonaut Georgi Dobrovolskiy (The vessel was deactivated and sold at the auction on Dec. 6, 2005. Its duties transferred to Cosmonaut Viktor Patsaev)
  • Cosmonaut Viktor Patsaev

One command and control ship, Marshall Nedelin, joined the fleet in 1982 and Marshall Krylov in 1986.

Airborne stations

Four airborne measurement stations were also introduced in 1974. Three of them were deployed on Ilyushin-20RT planes, based on Il-18 four engine propeller passenger planes.

Galitsino-2 control center

From 1970s, the top-secret Galitsino-2 control center, located in the town of Krasnoznamensk northwest of Moscow, became a nerve center coordinating and managing the vast network of ground-, sea-based and airborne control facilities in Russia.

Satellite-watching stations

On Dec. 24, 1969, satellite-watching radar stations in Balkhash and Irkutsk were declared operational.

Kaliningrad OIP

During 2009, in the course of restructuring of Russian space forces, a new Detached Measurement Site, OIP, was formed in the Kaliningrad Region (Oblast), Oleg Ostapenko, the commander of space forces told the Russian press. A shift of flight controllers conducted their first communication session with the spacecraft on June 12, 2009, and from September 1 of the same year, the site had started experimental operations. (371) The establishment of the site apparently extended range of the Russian satellite tracking network to the West to the maximum extent possible from the Russian territory. The site probably compensated for the loss of tracking facilities in the former western republics of USSR in the wake of its dissolution.

As of 2009, the organizational structure of the Russian space forces included following space and satellite monitoring assets:

  • Titov Chief Center for Testing and Control of Space Assets, GITsIU KS;
  • Chief Center of Outer Space Monitoring, GTs KKP;
  • Chief Center for Early Warning of Rocket Attack, GTs PRN;
  • Anti-missile defense unit.

Laser network

As of 2012, Russia deployed a network of five laser stations intended for tracking and control of orbital vehicles.

TsKIP Zheleznogorsk

With the collapse of the USSR, Russian companies found themselves paying to the Ministry of Defense for the control of their non-military, commercial satellites. As a result, some of them decided to fund internal control facilities. NPO PM opened a control facility for Gals and Ekspress satellites on Jan. 20, 1994. Central Command and Measurement Point, TsKIP, code-named Zheleznogorsk, was located at the Paseka site in Eastern Siberia, probably within the campus of NPO PM (later ISS Reshetnev). In 2012, the center received a six-meter antenna of the Klen-A command and measurement complex, which was responsible for flight control of Elektro-L satellite, among several other facilities at the site. TsKIP Zheleznogorsk was a part of the Roskosmos' Unified State Automated Ground Complex for Control of Satellites or NAKU.


A map showing communications range of the Zheleznogorsk tracking station for the Kanopus-V satellite.

Miass site

In June 2013, GRTs Makeev, the developer of submarine-based ballistic missiles, announced a deployment of a 3.7-meter antenna for the KIP facility at the company's campus in Miass, as part of the Istochnik-M telemetry receiving and transmitting station. The facility would support mission of launch vehicles and civilian spacecraft for Roskosmos, including ISS, GRTs Makeev said. Beginning in the fourth quarter of 2013, the same facility would start deploying a nine-meter, S-band antenna for long-range communications, the announcement said.

A potential South-African site

In the wake of the summit between Russian and South-African presidents in September 2006, head of Federal Space Agency, Roskosmos, Anatoly Perminov, (who accompanied President Putin on the trip to South Africa) said that Russia had considered the construction of a ground control station on the South-African territory. On the eve of the Phobos-Grunt mission, the South Africa reportedly invited the spacecraft's developer -- NPO Lavochkin -- to take advantage of the existing site at Hartebeesthoek, however, the company reportedly insisted on the construction of brand-new stations in Namibia or Mozambique.

Hopes for opening a South-African site were rekindled in November 2012, when an intergovernmental committee on trade and economic cooperation prepared a ground work for an agreement to use the existing South-African ground station for communications with the Spektr-R observatory during a southern portion of its orbit around the Earth. The final document was promised to be signed during a summit of BRICS countries (Brazil, Russia, India, China and South Africa) then planned in March 2013.

A potential Australian site

During the 14th Australian International Aerospace Congress, held in Melbourne from Feb. 28 to March 3, 2011, Russian and Australian officials announced that two sides had discussed a possibility of deploying two ground stations in Australia:

  • A near-Earth object observation center was to conceived to detect and track large space debris and natural objects heading towards Earth;
  • A mission control center designed to support the International Space Station and unspecified future space operations.

Antarctic station

On Feb. 20, 2018, Moscow-based RKS Holdings announced a plan to build a receiving station in Antarctica, which would allow remote-sensing satellites in polar orbits to downlink their data to be transferred to the NTs OMZ center specialized in the distribution of information from the application spacecraft. For Russia, it would be the first ground station for the Integrated Remote Sensing Information Distribution Network, ETRIS DZZ, in the Southern Hemisphere. According to RKS Holdings, the new station will give satellites an extra opportunity to free their onboard memory, which should significantly increase the observable areas on Earth and accelerate the delivery of the remote-sensing data to the end users.

Scheduled for opening in February 2019, the new ground station will be situated on the hilltop near the Progress scientific station. The facility will include an antenna complex under a radio-transparent dome and the container with receiving and transmitting equipment. RKS Holdings said.

Page author: Anatoly Zak

Last update: February 20, 2018

All rights reserved


Several decades after it was used for tracking early launches, the Kama relay antenna stands as a monument at Site 18 in Baikonur. Copyright © 2001 Anatoly Zak

A theodolite used to track early R-7 launches from Site 18 in Baikonur. Copyright © 2001 Anatoly Zak

The main control building at IP-1 ground station at Site 18 in Baikonur. Copyright © 2001 Anatoly Zak


General view of Site 18 in Baikonur. Click to enlarge Copyright © 2000 Anatoly Zak

Click to enlarge

Like shadows of the world far away, the antennas of the Saturn ground control station dominate skyline over steppen village near Tyuratam. Antennas are part of the IP-5 tracking station located at Site 23. Copyright © 2001 Anatoly Zak

The Vega ground station at Site 21 in Baikonur is used for trajectory measurements. Click to enlarge Copyright © 2000 Anatoly Zak

The IP-1B ground control station, later renamed IP-2, was built on the right (eastern) flank of Baikonur cosmodrome. The facility was originally designed to support R-16 program. Copyright © 2000 Anatoly Zak

Ground control station in Shelkovo, east of Moscow. Copyright © 2001 Anatoly Zak


Romashka (Daisy) antenna, a component of the RTS-9 telemetry system at IP-1 site in Baikonur. Romashka was designed to receive telemetry from low-orbiting spacecraft, including Soyuz missions, flying as low as 200 kilometers overhead. Copyright © 2000 Anatoly Zak


A circa 2012 artist rendering of the laser tracking center in Altai mountains. Credit: Ipromashprom


A prototype of a space-based laser system developed for testing onboard Mir and ISS. Copyright © 2000 Anatoly Zak


A Soviet Iluyshin-18 aircraft configured to maintain communications with spacecraft.


A photo of the Russian military control center in Krasnoznamensk (Galitsino-2) accompanied an announcement about the successful launch of Kosmos-2513 (Garpun-12L) on December 13, 2015. Click to enlarge. Credit: Russian Ministry of Defense