Category Energiya-Buran

Early Return

“Early Return” was a scenario giving the crew 3 to 24 hours to prepare for deorbit, with a much better chance of reaching one of the three runways. This would have required the same type of action on the part of the crew as “Immediate Return”, but only at a more relaxed pace. The most probable event leading to such a situation would have been a dangerous loss of redundancy in critical on-board systems such as the computers, the GSP gyro platforms, the fuel cells, etc. Even depressurization of the crew cabin was ranked as an anomaly that would give the crew several hours or more to prepare for deorbit, assuming that the loss of pressure was slow enough for the crew to have a chance to don their Strizh pressure suits and hook them up to the Personal Life Support System (the minimum time required for this was five minutes). Cabin systems were designed to operate in a vacuum and the suit’s life support systems could sustain the crew for 12 hours.

Orbiter Assembly and Test Facility (MIK OK/MIK 254)

The MIK OK (also designated 11P592) was the biggest facility that had to be built from scratch in support of the Energiya-Buran project. Early plans to use reinforced concrete were abandoned in favor of lighter materials to speed up construction. Sources differ on the exact size of the building, with the width given between 112 and 132 m, length between 222 and 254 m, and height between 30 and 37 m. The actual processing area was surrounded on three sides by a multi-storey prefabricated concrete structure containing 4,800 m of laboratory and office space.

Whereas NASA’s Orbiters are processed in stationary mode in three separate, virtually identical Orbiter Processing Facilities, all Soviet vehicles were processed in one single building, progressively moving from one bay to another to undergo specific processing tasks. The MIK OK housed five bays:

– Transfer bay: this is where Buran arrived first after entering the building through large rolling doors. Having been transported to the MIK OK, the vehicle was transferred here to an internal transportation device, allowing it to be moved from one bay to the other. It was also possible to move the orbiters from one bay to another with the help of a bridge crane.

– Thermal protection system bay (“bay 102’’): a bay specifically equipped to further outfit Buran with tiles after arriving from the factory or to service the thermal protection system in between flights.

– Assembly bay (“bay 103’’): here Buran was fitted with parts that could not be installed in the factory either for technical reasons or because of weight

Orbiter Assembly and Test Facility (B. Vis).

constraints imposed by the VM-T carrier aircraft. Among other things, the engines, the power supply system, additional life support systems, and various cables were installed here. This bay was also to be used for repair work in between flights, leak checks, and autonomous tests of various systems.

– Control and test bay (“bay 104”): this was used for electrical tests of individual systems and integrated electrical tests, some additional assembly work that could not be performed in the assembly bay, and also for final close-out work.

– Anechoic chamber (“bay 105”): this bay (measuring 60 x 40 x 30 m) was used for individual and integrated tests of the orbiter’s radio systems to make sure that they would not interfere with one another in flight.

The MIK OK would have been capable of supporting a launch rate of up to six missions per year [9].

CREWING FOR BURAN’S FIRST MANNED MISSIONS

Soviet planners envisaged an extensive orbital test flight program for Buran, which at one point included as many as 10 missions, both unmanned and manned. By comparison, the US Space Shuttle flew just four (manned) test flights in 1981— 1982 before being declared operational.

For safety reasons, crews for the initial Buran test flights would have been restricted to just two cosmonauts. First, it was not practical to install ejection seats for more than two crew members and, second, if a life-threatening emergency arose in orbit, a Soyuz would have to be able to come to the rescue. Since that Soyuz needed a “rescue commander”, only two seats would be left in the vehicle for the stranded Buran crew.

Throughout the 1980s, there was disagreement on the composition of the initial Buran crews. LII in Zhukovskiy, backed by the Air Force, argued that both seats should be occupied by its experienced test pilots. However, NPO Energiya, intent on not being sidelined, pushed to fly one of its engineers in the co-pilot seat rather than an LII test pilot. Therefore, two types of crews were considered for most of the duration of the program: crews consisting of two LII pilots, on the one hand, and crews composed of one LII pilot and one NPO Energiya flight engineer, on the other hand.

It should be stressed that as Buran never came anywhere close to flying a manned mission, none of the crews mentioned below was ever officially assigned. The flight plan for the first manned mission remained vague until the end of the program and none of these crews performed any dedicated mission training.

LII crews

From the very beginning LII had the following crews in mind for the first flight:

Prime crew Back-up crew

Igor Volk Anatoliy Levchenko

Rimantas Stankyavichus Aleksandr Shchukin

The preference for Volk-Stankyavichus and Levchenko-Shchukin was reflected in the fact that the two crews flew the bulk of the atmospheric Horizontal Flight Tests with the BTS-002 Buran analog. A total of 24 such flights were performed between November 1985 and April 1988. Volk and Stankyavichus were paired for 11 of the missions and Levchenko and Shchukin jointly flew 4 missions (see Chapter 6).

The original crewing plan was completely disrupted in August 1988, when in a bizarre twist of fate Buran lost its entire back-up crew with the deaths of both Levchenko and Shchukin. As a result, Volk and Stankyavichus were split up and both got new co-pilots from the LII ranks [41]. Volk has claimed that GKNII pilots Ivan Bachurin and Aleksey Boroday, veterans of six BTS-002 flights, were also considered as the back-up crew [42]. The new crews were:

Prime crew Back-up crew

Igor Volk Rimantas Stankyavichus

Magomed Tolboyev Viktor Zabolotskiy

Internal LII documents show that another option considered was to retain the Volk- Stankyavichus team, with Zabolotskiy and Tolboyev acting as back-ups. This plan assumed that Zabolotskiy would first fly a Soyuz mission to give him the necessary spaceflight experience to command Buran if the need arose [43].

When Stankyavichus was killed in a plane crash in September 1990, LII was forced once again to change the composition of the back-up crew [44]. The new crews were:

Prime crew Back-up crew

Igor Volk Viktor Zabolotskiy

Magomed Tolboyev Ural Sultanov

These are the last crews known to have been considered by LII for the first piloted Buran mission.

First roll-outs

As early as 1979 crude full-scale mock-ups of the core stage and one of the strap-ons (“EUK-13”) were built in situ at Baykonur just to get a feel of things to come [5]. During that same year the Progress factory in Kuybyshev manufactured a core stage called 4M that was to be used for a variety of pad tests at Baykonur. However, the beginning of those pad tests hinged on the completion of the UKSS test stand as well as the availability of the VM-T Atlant carrier aircraft to fly elements of the core stage from Kuybyshev to the cosmodrome. After completing its test flights at Zhukovskiy, the VM-T delivered the 4M core stage to Baykonur in two ferry flights on 8 April and 11 June 1982. At about the same time KB Yuzhnoye shipped four mock-up modular sections of strap-on boosters to the launch site.

By the autumn of 1982 the Interdepartmental Coordinating Council (MVKS) set the goal of assembling the first Energiya rocket before the end of the year, which was expected to be a major morale-booster for cosmodrome personnel. This was easier said than done, because much of the equipment needed for this at the Energiya assembly building was not yet in place and NPO Energiya’s ZEM factory was running late in supplying the nose and tail sections for the mock-up boosters. In order to meet the deadline, tail sections for the mock-up boosters were quickly manufactured by the Atommash factory in Volgodonsk, which produced large-scale components for the Soviet Union’s nuclear power program. Mustering all their improvisation skills, workers managed to complete the assembly of the first so-called “packet’’ in the final days of 1982, using a specially ordered crane to mount the final two boosters on the stack.

A first demonstration roll-out took place in the late winter, but the exact date is unknown and it is not clear if the vehicle was actually placed on the UKSS. US reconnaissance satellites observed the rocket outside the assembly building in March 1983 [6]. The next step would have been to conduct fueling tests of the 4M’s LOX and LH2 tanks, but much of the 4M core stage’s internal plumbing had not yet been supplied by the Progress plant and the UKSS had not been completely finished either. However, engineers came up with an alternative plan to use the 4M stack for dynamic tests that would normally be done much later at the Dynamic Test Stand, the construction of which was running many years behind schedule. The purpose was to learn more about the effects of longitudinal and transverse vibrations on the core stage, the boosters, and the mechanical systems joining them. Another objective was to study the effects of an emergency shutdown of two RD-0120 engines. For the tests

Energiya 4M-D roll-out in May 1983 (source: www. buran. ru).

the stack was equipped with a wide array of sensors capable of monitoring 85 different parameters.

For the longitudinal vibration tests, a cable would be suspended between the top and bottom sections of the core stage, where one of the engine nozzles was removed. Pyrotechnic bolts would then be fired to release the cable either at the bottom end or top end of the core stage, thereby creating longitudinal vibrations. Dubbed 4M-D (D for “dynamic”), the stack was rolled out to the UKSS for these tests on 7 May 1983. Dynamic tests were later continued with the same stack in horizontal position in the Energiya assembly building. Several months later the UKSS was finally ready for fit checks, and launch pad chief designer Vladimir Barmin insisted on doing another roll-out. In October 1983 the 4M stack once again slowly made its way to the UKSS and all its systems were hooked up to the pad, which had not been the case in the earlier tests [7].

Snooping on Buran

Although the Energiya-Buran program remained shrouded in secrecy for much of the 1980s, US intelligence specialists had a fairly good idea of the system’s character­istics and capabilities, mainly thanks to detailed American reconnaissance satellite images of both Baykonur and the Flight Research Institute (LII) in Zhukovskiy. The latter was identified in the intelligence literature as Ramenskoye, which is the name of LII’s airfield in Zhukovskiy and (confusingly) also of a neighboring town and railway station.

The first clear evidence for the existence of a large shuttle came in the late 1970s, when construction of the runway and launch pads at Baykonur got underway. The Energiya-Buran pads were identified as “Complex J’’ (the same code name given to the N-1 pads) and the UKSS pad as “Complex W’’. By 1982 spy satellites had even spotted the construction of the back-up runway in the Soviet Far East. [14].

The first public assessment of the system’s capabilities was given in Soviet Military Power 1983, published in early 1983. Since the first test models of Energiya were yet to be rolled out to the pad, analysts still had a poor understanding of the system’s configuration and capabilities. Drawings showed the Soviet shuttle mounted on an external tank with two rocket boosters, with the main engines apparently on the orbiter itself. The lift-off weight of the system was estimated to be just 1,500 tons compared with the NASA Shuttle lift-off weight of 2,220 tons. Combined with an estimated lift-off thrust of between 1,800 and 2,700 tons (compared with roughly 3,000 tons for the Shuttle), this translated into a staggering payload capacity of 60 tons, twice that of the Space Shuttle Orbiter. The Soviet shuttle was believed to have a substantially different wing design with an 80-degree sweep. The heavy-lift launch vehicle (HLLV) was depicted as a 95 m high core vehicle with three 35 m high liquid propellant boosters and a top-mounted payload with a maximum mass of between 130 and 150 tons [15].

Assessment of Soviet heavy-lift launch vehicle capabilities in Soviet Military Power 1983 {source: US Department of Defense).

By the middle of 1983 several events led to a much better understanding of the Soviet shuttle system. Spy satellites had acquired detailed images of a test orbiter sitting atop a VM-T carrier aircraft during tests earlier in the year and had also spotted an incident in which the pair accidentally skidded off the runway in March 1983. Moreover, the first test versions of Energiya had been rolled out of the assembly building in the first half of the year. A CIA National Intelligence Estimate in July 1983 now correctly concluded that the orbiter had a configuration very similar to that of the US Space Shuttle Orbiter and that the main engines were on the core rather than on the orbiter. The report was wrong in stating that the rocket had only two strap-on boosters and that the core was outfitted with “at least two and probably three engines”. This may have been related to the fact that the Energiya rolled out in May 1983 had only three nozzles installed on the core stage {see Chapter 6). The report referred to the spherical sections above the core stage nozzles as “pod-like

US Defense Department representation of Soviet shuttle on the pad. Illustration from Soviet Military Power 1986 (source: US Department of Defense).

objects” that were erroneously interpreted as part of a recovery system for the LOX/LH2 engines [16]. In Soviet Military Power 1984 lift-off weight and thrust were now estimated at 2,000 tons and 3,000 tons, respectively, resulting in an orbiter payload capacity of 30 tons. The HLLV was still expected to be a nearly 100 m high rocket with six or more strap-on boosters and a payload capacity of 150 tons, a configuration that was actually more reminiscent of the Vulkan rocket.

It was not until the 1986 edition that Soviet Military Power published a drawing of a 100-ton capacity HLLV where the orbiter was replaced by a side-mounted cargo pod. This was also the first edition that got the dimensions of the rocket/orbiter stack more or less right, although the first Energiya-Buran combination did not make its appearance on the Baykonur launch pads until summer/autumn of 1986, after the report had been published. The following year potential payloads for the cargo version of the rocket were said to be modules for large space stations, components for a manned or unmanned interplanetary mission, and even directed-energy ASAT and ballistic missile defense weapons.

Reconnaissance satellite images of Baykonur also gave some idea of how the testing proceeded. In 1984 and early 1985 the SL-X-16 (“Zenit”) medium-lift booster had been observed being alternately removed from and erected on the pad, suggesting Soviet dissatisfaction with the ground test results. This in turn had implications for

US Defense Department representation of Soviet shuttle atop the VM-T aircraft. Illustration from Soviet Military Power 1985 (source: US Department of Defense).

the HLLV/shuttle program, which used common engines. Apparently, the belief at this time was that the SL-X-16 was powered by liquid hydrogen/liquid oxygen engines and that these same engines were used both in the strap-ons and the core stage of the HLLV. The fact that no Energiya had yet been seen with an orbiter strapped to the side was also seen as an indication that the program was suffering delays [17]. When a test orbiter did finally undergo the first pad tests in August – October 1986, the news was reported only weeks later [18]. US reconnaissance assets apparently also picked up signs of the Energiya core stage test firings in the first half of 1986, but these were not openly reported until a year later [19].

Buran-related test activities were not always correctly interpreted, especially when the Soviet approach to testing was different than NASA’s. Just weeks before the first ground run of the BTS-002 atmospheric test bed at LII in late December 1984, Aviation Week correctly reported that approach and landing tests of the shuttle were imminent, but wrongly concluded that the vehicle would be dropped from the VM-T carrier aircraft in similar fashion to the test flights of Enterprise in 1977 [20]. In April 1986, by which time BTS-002 had performed numerous ground runs and two

landing tests, Aviation Week referred to reconnaissance photography showing jet engines mounted on either side of the tail, but still believed the vehicle was being dropped from the VM-T. The jet engines were thought to be on board only to test their ability to correct an orbiter’s flight path when returning from space and might or might not be lit prior to separation from the aircraft depending on test objectives [21].

Of course, the information that leaked out via Aviation Week did not necessarily reflect what the US intelligence community really knew. Other observers, taking into account the known capabilities of the VM-T, correctly concluded that it could hardly carry a full-size, full-weight orbiter to sufficient altitude for a safe free flight [22]. Aviation Week did not report the correct flight profile of the BTS-002 until late 1987 after having been informed by Soviet space officials at an international space congress in Moscow. The only mistake remaining was that the tests were said to take place at Baykonur [23].

Western observers had more to go on than just the intelligence community’s interpretation of reconnaissance satellite imagery. Pictures taken of Baykonur by civilian remote-sensing satellites such as the US Landsat and the French SPOT had sufficient resolution to show the construction work going on in support of the Energiya-Buran program. Unlike the spy satellite pictures, these were openly available to the public.

It is not clear how much information on the program leaked to the West through breaches in the Soviet censorship and security apparatus or via human intelligence. One piece of information that did slip through was that the name of the Soviet shuttle was Buran. The name first appeared in a 1983 CIA National Intelligence Estimate and also surfaced in several open Western publications the following years, well before the Russians officially announced it [24]. This information could not possibly have been gleaned from spy satellite photography, because the name was not on any of the test models and was not painted on the first flight vehicle until 1988. Actually, before 1988 Buran was not the name of a specific orbiter, but a generic name used by the Russians to refer to the combination of rocket and orbiter (see Chapter 2).

Defense Council meeting

On 6 May 1989 the Energiya-Buran program was again on the agenda of the Defense Council, chaired by Gorbachov. Appearing before the Council, leaders of the Energiya-Buran program outlined future plans for the system, including the GK-199 mission, the creation of fully reusable versions of the Energiya rocket, and the development of derived launch vehicles such as Energiya-M, Groza, and Vulkan. While acknowledging the success of Buran’s mission and praising the work of the people involved, the Council expressed dissatisfaction with the progress made on devising payloads and missions for the Soviet shuttle. The Council also made some cost-cutting moves, ordering the number of operational shuttle vehicles to be reduced from five (as planned since 1977) to three and curtail Buran’s test flight program to just five missions by combining some of the objectives of the earlier planned missions. At the same time it called for speeding up work on Buran payloads and Energiya – derived launch vehicles.

The plan was now to fly Energiya 2L with the GK-199 payload in 1990, giving the team an extra opportunity to man-rate the rocket for future Buran missions. The second unmanned orbiter mission was now delayed to the first quarter of 1991 and apart from a docking with Mir would feature a link-up with a manned Soyuz “rescue vehicle’’ (see Chapter 5). This mission, designated 2K1 (the first flight of orbiter 2K) had already been approved by the Military Industrial Commission on 22 February 1989. The first manned Buran flight was now scheduled for the first half of 1992. LII internal planning documents drawn up around this time show the unmanned mission was scheduled for April/May 1991 and the manned flight for May 1992, with crew training to begin in December 1990. The decisions of the Council were consolidated by a government decree in June 1989, which laid out plans for the use of Buran until the year 2000 [5].

Cargo Transport Container

For cargo missions the orbiter would have been replaced by a so-called Cargo Transport Container (GTK or 14S70) that could house a variety of payloads. This configuration was known as Buran-T (T standing for “transport”) before the name Energiya was adopted in 1987. The interfaces between the rocket and the payload would have been virtually identical to those on Energiya-Buran. Two diameters were considered for the GTK—namely, 5.5 m and 6.7 m—with the final choice falling on the latter, which turned out to be the most favorable in terms of aerodynamic and other characteristics. The container was 42 m long and had an internal volume of about 1,000 m3. The two main sections of the container were to be jettisoned after the rocket passed through the thickest layers of the atmosphere. The GTK was not used on the maiden flight of Energiya with the Skif-DM/Polyus payload, which flew the launch profile unprotected, except for a shroud on the upper FSB section. Strictly speaking, this was not a standard Buran-T configuration [56].

MIK RN/MIK 112

The Energiya assembly building is now run by the Samara-based TsSKB/Progress organization. As mentioned earlier, the three high bays were rendered useless by the roof collapse in May 2002, which among other hardware destroyed the only flown Buran orbiter. In 2004 the Russian Space Agency earmarked funds to refurbish high Bay 3 for processing future satellites built by TsSKB/Progress, but there are no signs that any work is being done. No plans have been announced for repairing the other two high bays and these may be demolished. By the end of 2006 the debris from the roof collapse had reportedly still not been cleared.

Soyuz rocket assembly in low bay 1 (source: RKK Energiya).

Low bay 1 now houses the processing area for Soyuz launch vehicles flying from pad 5 (the “Gagarin pad”) on Site 1, which is now used for Soyuz and Progress launches to the International Space Station and also for occasional launches of civilian satellites built by TsSKB/Progress (Foton, Resurs). Soyuz rockets destined for the Gagarin pad used to be assembled in the old MIK-2B building in the center of the cosmodrome. Although the new assembly hall is much roomier than MIK-2B, it is much farther away from the Gagarin pad, making the roll-out procedure more cumbersome. The roll-out now takes about 2 hours, compared with 30 minutes in the old days. The first vehicle to be rolled out from the modified low bay 1 was Progress M1-10 in June 2003.

Low bay 2 was modified in the late 1990s to process payloads for Starsem, a Russian/European company founded in 1996 by Arianespace, EADS SPACE, TsSKB/Progress, and the Russian Space Agency to commercially market the Soyuz launch vehicle. There are three Starsem clean rooms here: a 286 m2 Payload Processing Facility (PPF) with two independent control rooms to permit parallel operations, a 285 m2 Hazardous Processing Facility (HPF) to fill satellites with toxic hypergolic propellants, and a 587 m2 Upper Composite Integration Facility (UCIF) for integration with the Fregat upper stage and upper fairing encapsulation. Mating of the upper composite with the first three stages of the Soyuz launch vehicle takes place in the Soyuz assembly building on Site 31 on the “right flank” of the cosmo­drome. Starsem exclusively flies from pad 6, situated on Site 31 [79].

The Soviet response to NASP

Research on aerospace planes in the Soviet Union got a fresh impetus in the mid-1980s, presumably in response to similar work started in the US in 1982 at the Defense Advanced Research Projects Agency (DARPA) under the name Copper Canyon and then transferred to NASA and the Air Force as the National Aerospace Plane (NASP) in 1986. President Ronald Reagan mentioned the project in his State of the Union speech on 4 February 1986, calling it:

“a new Orient Express that could, by the end of the next decade, take off from Dulles Airport, accelerate up to 15 times the speed of sound, attaining low Earth orbit or flying to Tokyo within two hours.’’

Although touted by the Reagan Administration for its civilian commercial applica­tions and as a possible follow-on to the Space Shuttle for NASA, the 80-20 split of funding between the Air Force and NASA clearly indicates NASP was first and foremost a military program. The objective of the program was to develop a proto­type SSTO vehicle taking off with turbojets, then switching to hydrogen-fueled scramjets at subsonic and hypersonic speeds, with a LOX/LH2 rocket engine performing orbit insertion.

The go-ahead for the Soviet response came in two government decrees on 27 January and 19 July 1986, followed by the release of technical specifications by

The Tu-2000.

the Ministry of Defense on 1 September 1986. Three organizations were tasked to come up with proposals: NPO Energiya, the Yakovlev bureau, and the Tupolev bureau. While nothing is known about the Yakovlev concept, NPO Energiya’s aero­space plane was a 71 m long vehicle with a wingspan of 42 m and a maximum height of 10 m. With a take-off mass of approximately 700 tons (dry mass 140 tons), the vehicle would use a combination of turbojets, scramjets, and rocket engines to reach orbit. It was designed for the deployment of payloads into low orbits (at least 25 tons into a 200 km, 51° orbit), servicing of orbital complexes, intercontinental passenger transport and also for military operations “in and from orbit’’. The project was headed by veteran designer Pavel Tsybin [20].

The project eventually selected for further development was the Tupolev bureau’s Tu-2000. Actually, the bureau was no newcomer to SSTO vehicles, having already performed low-priority studies of horizontal take-off and landing space – planes with a take-off mass of up to 300 tons in 1968-1971. Overall Tu-2000 was very similar in design to NASP, relying on the same combination of engines to go into orbit. It had a vertical stabilizer and small delta wings, with much of the lift provided by the flat-shaped underside of the fuselage. A huge hydrogen tank occupied most of the mid and aft fuselage and would feed both the scramjet and rocket engines. The oxygen tank for the rocket engine was located in the tail section.

The Tupolev bureau proposed to carry out the project in two stages. First, it would develop a 55-60 m long two-man suborbital demonstrator (Tu-2000A) to reach a maximum velocity of Mach 5/6 and an altitude of up to 30 km. With a take-off mass between 70 and 90 tons, the vehicle would be equipped with four turbojet engines, two scramjets, and two liquid-fuel rocket engines. Then the project would move on to an experimental 71 m long two-man orbital version with a take-off mass between 210 and 280 tons and six rather than four turbojet engines. Payload capacity was 6-10 tons to low orbits between 200 and 400 km. Unconfirmed reports suggest the Tupolev bureau also planned a long-range bomber (Tu-2000B) and a hypersonic passenger plane based on the Tu-2000 design.

By the early 1990s the Tupolev bureau had reportedly built a wing torque box made of a nickel alloy, elements of the fuselage, cryogenic fuel tanks, and composite fuel lines. Estimates made in 1995 showed that Tu-2000 related R&D would cost at least $5.29 billion, a high price-tag even if Russia had a healthy economy. Budget realities had also forced NASA and the Air Force to cancel NASP in 1993. Although low-level research on the Tu-2000 may have continued for several more years, this project obviously stands no chance of being realized any time soon [21].

PRELIMINARY STUDIES

Meanwhile, six Soviet military and civilian research institutes were tasked with performing a study of the Soviet Union’s future space transportation needs to help determine the need for a response to the Space Shuttle. These were TsNIIMash and NIITP (the Scientific Research Institute for Thermal Processes, the current Keldysh Research Centre) under MOM, TsAGI (the Central Aerohydrodynamics Institute) under MAP, TsNII-30 and TsNII-50 under the Ministry of Defense, and IKI (the Institute of Space Studies) under the Academy of Sciences. TsNIIMash was given the lead role.

Actually, the studies centered not solely on shuttles, but on a wide array of expendable and reusable launch vehicles that would provide the most economical access to space in the future. They also extended to various reusable space tugs and expendable upper stages with either liquid or nuclear rocket engines for interorbital maneuvers and deep-space missions. Four future directions were considered for the Soviet Union’s space transportation program:

• the continued use of expendable launch vehicles and spacecraft until the year 2000;

• the continued use of expendable launch vehicles, but with standardized satellites;

• the use of a reusable space transportation system capable of returning spacecraft back to Earth for servicing and subsequent reuse;

image37

Reusable space transportation systems studied at Soviet research institutes in the early 1970s (source: Ts. Solovyov).

• the use of a reusable space transportation system capable of servicing and

repairing satellites in orbit.

As for reusable systems, the institutes explored two vehicle sizes, one able to accom­modate payloads of 30-40 tons (like the Space Shuttle) and another for payloads weighing 3-5 tons. Furthermore, two ways were studied of recovering the first stage, one involving the use of standard recovery techniques, the other requiring the use of reusable flyback boosters.

The six institutes presented their joint findings in June 1974. They concluded that the development of a reusable launch vehicle was only economically justified if the launch rate was very high, more particularly if the annual amount of cargo delivered to orbit would exceed 10,000 tons. However, it was stressed that much also depended on the vehicle’s capability of servicing satellites in orbit or returning them to Earth for repairs. The size of the spaceplane in itself would not determine its effectiveness and would have to depend on the mass and size of the payloads that needed to be launched or returned. Finally, it was recommended to perfect future reusable systems by developing first stages with air-breathing engines and eventually to introduce high-thrust nuclear engines for single-stage-to-orbit spaceplanes.

Basically, the conclusion was that a Space Shuttle type transportation system would not provide any major cost savings even if a relatively high launch rate was achieved and should be seen as nothing more than a first step towards developing more efficient transportation systems. However, the consensus was that if a reusable system were developed, preference should be given to a big shuttle akin to the American one [4].

On 27 December 1973, without awaiting the results of the studies, the VPK ordered three design bureaus to formulate so-called “technical proposals” for a reusable space transportation system. This is one of the first stages in a Soviet space project, in which various preliminary designs are worked out and compared in terms of their technical and economic feasibility. While the VPK order was significant in being the first official government-level decision on a Space Shuttle response, it was far from a commitment to build such a system, but merely an attempt to explore various vehicle configurations that might eventually lead to to a final decision later on. The three bureaus were MMZ Zenit (headed by Rostislav Belyakov after Mikoyan’s death in 1971), Chelomey’s TsKBM, and Mishin’s TsKBEM. They came up with two basically different concepts that reflected the conflict between a small vs. a large shuttle.

MMZ Zenit was best prepared to respond to this order, having worked since 1966 on its Spiral air-launched spaceplane and benefiting from actual suborbital flight experience with the BOR-1, 2, and 3 scale models. Strictly speaking, the space branch that had been set up in Dubna in 1967 to work on Spiral was no longer subordinate to MMZ Zenit, having merged in 1972 with MKB Raduga (another former branch of Mikoyan’s bureau) to form DPKO Raduga. The VPK order must have been a major morale booster for Lozino-Lozinskiy’s Spiral team, which because of a lack of government and military support had been forced to do its work on an almost semi-legal basis. It did require the team to divert its attention from the small air – launched Spiral, which had been primarily designed for reconnaissance, inspection, and combat missions. With the focus now shifting to transportation tasks, a larger version of Spiral with a higher payload capacity was needed. Although the details are sketchy, Lozino-Lozinskiy’s team seems to have studied an enlarged 20-ton version of the Spiral spaceplane launched by the Proton rocket.

TsKBM also set its sights on a 20-ton spaceplane to be orbited by the Proton, which itself was a product of Chelomey’s bureau. However, the spaceplane project seems to have been low on Chelomey’s list of priorities at this stage. Indications are that the bulk of spaceplane research at TsKBM was done in the late 1970s, by which time Buran had already been approved (see Chapter 9) [5].

TsKBEM was to focus on a Space Shuttle sized vehicle to be orbited by the N-1 rocket, but it appears that little, if any, work was done on this. The research was to be done by a small team headed by Valeriy Burdakov, but as Burdakov later recalled, the team’s work was limited to studying the possibility of reusing the first stage of the N-1 and keeping track of foreign literature on reusable space systems [6]. However, big changes were ahead at TsKBEM that would turn these plans upside down.