On 15 May 1987, Energia made its first flight carrying Polyus, the Soviet spacecraft also known as Skif-DM. The launcher succeeded; the payload failed to reach orbit. Those outcomes can coexist because separation from a rocket is sometimes a handover, with propulsion and control tasks still to come.

Polyus makes that handover unusually revealing. Its connection to a proposed space-laser weapon has often overshadowed the simpler engineering question: what did the spacecraft still have to do after Energia released it?

What did Energia finish, and what remained?#

Energia supplied the launch, but Polyus had to provide the final boost to orbital velocity. Boris Chertok's memoir celebrates the first Energia flight, while an editorial footnote explicitly records the payload's control-system malfunction and failure to reach orbit. This distinction matters more than calling the whole flight either a success or a failure.

The machines were physically joined side by side. Polyus was the long payload alongside Energia, rather than a satellite perched above the rocket. After separation, its service module supplied propulsion and control. The launcher could therefore deliver the spacecraft to the intended handover conditions without delivering a completed orbital mission.

Think of two acceptance questions. Did the launcher perform its assigned flight? Did the separated spacecraft then establish its intended orbit? An affirmative answer to the first cannot substitute for the second.

Sources: [1][2]

Why was reaching space insufficient?#

Height alone does not keep an object aloft. Gravity still acts above the atmosphere. An orbiting spacecraft falls toward Earth while moving sideways fast enough for its path to keep missing the surface.

Position and velocity together determine that path. Velocity includes direction as well as speed. A spacecraft can be above the atmosphere yet still be on a trajectory that intersects the atmosphere again. This is what makes a suborbital flight different from a completed orbital insertion.

A useful idealization is to imagine Earth without air. A freely moving object's calculated path might pass through the planet; the real surface would interrupt it. Restoring the atmosphere makes the distinction stricter: even a path that misses solid ground can dip deeply enough into air to end the flight. Polyus needed propulsion to change its trajectory before that return.

Sources: [3][4][1]

Why did the spacecraft need to turn?#

Polyus's engines were pointed in the launch direction while it rode Energia. NASA's 1995 Mir Hardware Heritage, drawing on designer Yuri Kornilov's account, explains that the separated spacecraft had to reorient before using those engines for insertion. Its launch attitude was unsuitable for that task.

Turning changes where a spacecraft points; an engine burn changes how it moves. These are distinct operations. A vehicle can point one way while continuing to travel another way, because rotating its body does not automatically rotate its velocity.

The direction of thrust then determines the change in velocity. A push along the direction of travel increases speed; a push against it reduces speed; a sideways push redirects motion. Burning propellant is therefore insufficient by itself. The force must act in the direction the trajectory requires. The same broad distinction between rotation and travel also helps explain the control emergency aboard Gemini 8.

Two conceptual spacecraft share rightward velocity; forward thrust increases speed while backward thrust reduces it.
Conceptual force-direction examples explain why pointing matters. Neither panel reconstructs the exact Polyus engine sequence or attitude. Original diagram by Draw to Know

Sources: [2][4]

What can we say about the failure?#

The defensible common account is a spacecraft control failure during the post-separation insertion sequence. Mir Hardware Heritage describes lost attitude control and a tumble that prevented the propulsion system from completing insertion. Polyus reentered over the Pacific.

That NASA account is a historical reconstruction based on a named designer's report, rather than a published telemetry record. The later January 2010 Air & Space account gives a more detailed rotation and software narrative. Those added details should not be mistaken for independently inspected flight data.

The diagrams here explain the required handover and the importance of thrust direction. They do not reproduce measured trajectories, exact rotations, command timing or the full engine sequence. The evidence supports failure to attain orbit; it does not establish sabotage or political intent behind a malfunction.

Sources: [1][2][5]

Was a working laser weapon aboard?#

Skif was a proposed space-based laser weapon program. Skif-DM was an early demonstration model intended to test supporting systems. The 2010 Air & Space reconstruction distinguishes it from later laser-equipped vehicles that were planned. It did not carry an operational combat laser.

This was a real military development effort, so calling the payload merely an inert weight would also mislead. Testing propulsion, control and other supporting equipment can advance a weapons program without demonstrating the weapon's destructive capability. No combat-laser firing occurred on this flight.

The failure left that distinction unresolved by experiment: a successful insertion could have tested a spacecraft demonstrator, but it would still not have proved an operational orbital laser. What the flight did show was the dependency between two machines. Energia's achievement ended at a handover that Polyus could not finish.

Sources: [5][1]

Keep exploring

Sources & further reading

Follow the original research, records, and explanations behind this story.

  1. Rockets and People, Volume IV: The Moon Race NASA / Boris E. Chertok

    Printed p.576 and editorial footnote 73: first Energia flight, payload control failure and required final boost. Memoir and editorial annotation are distinguished.

  2. Mir Hardware Heritage NASA / David S. F. Portree

    Section 3.8.2, printed pp.168–169: side mounting, service module, orientation and failed insertion; attributed to Kornilov.

  3. Chapter 3: Gravity & Mechanics NASA

    Page One, Gravitation and Ellipses: gravity persists with distance and orbital paths.

  4. Chapter 3: Gravity & Mechanics NASA

    Page Two, Newton’s Principles of Mechanics, Acceleration and The Rocket: force direction, inertia and thrust. Unrelated dated statements are not used.

  5. Soviet Star Wars Air & Space Magazine / Smithsonian

    Dwayne A. Day and Robert G. Kennedy III, January 2010: distinction between proposed weapon program and Skif-DM demonstrator. Secondary historical reconstruction, not telemetry.

Follow the thread