Gorizont: connect a broadcast network

The Gorizont family emerged in the late 1970s as the Soviet Union prepared for international television and radio transmission from the 1980 Moscow Olympics. Reshetnev’s history describes this requirement, while RSCC records the creation of the Dubna satellite communications centre for the event. The spacecraft and the teleport — open definition were complementary parts of the broadcast system.

The family’s work extended beyond that event. NASA’s November 1993 bulletin records Gorizont 28 launching on October 28 for telephone and television service to Siberia and the Far East. Its archive card is titled Gorizont — S22880. This dated example establishes continued development across the Soviet-to-Russian transition; it does not claim that a 1993 satellite participated in a 1980 broadcast.

Imagine a camera at a sporting venue. Its programme feed must reach a transmitting facility, travel up to a satellite, return to a receiving station and continue through a distribution network. Each stage has equipment and an operating team. The satellite is a relay in this chain; it is not the camera, the editor or the viewer’s television.

In a hypothetical capacity exercise, a venue can supply 50 units of data per second, an uplink accepts 40, the satellite allocation permits 30 and the receiving network handles 45. The complete path carries at most 30 units per second under these assumptions. Upgrading the venue feed to 100 does not remove the 30-unit bottleneck. The numbers are teaching values, not Gorizont technical specifications.

Find the limiting stage

Reliability also depends on the arrangement of the ground network. Two satellite paths using the same failed terrestrial cable do not provide independent end-to-end service. A useful backup must address the particular failure being considered. Engineers examine common equipment, power, routing and operating procedures rather than simply counting the number of spacecraft available.

A historical source may describe a satellite’s intended service immediately after launch. That is evidence of its assigned role, but full acceptance and actual performance need additional operational records. Keeping purpose, launch and service separate makes the chronology easier to understand. Gorizont’s example connects a public event to the less visible systems that turn an orbital relay into a dependable communications network.