Yamal: operate a commercial communications fleet

Yamal developed as a commercial communications system associated with Gascom, later Gazprom Space Systems. The operator dates the first Yamal-100 launch to September 6, 1999. Its history then records Yamal-201 and Yamal-202 launching on November 24, 2003, with service at different orbital positions. The Yamal-201 archive card identifies one of those spacecraft.

A fleet can serve different regions or requirements through different positions and payload allocations. The programme is more than a collection of launches: customers need capacity, ground terminals and an operator that maintains the service. Commercial financing adds another requirement, because construction and operations must be supported while customers are connected and retained.

A January 2009 operator announcement described a changed development approach after the earlier Yamal-301 and 302 plan. It introduced the Yamal-300K arrangement using a Reshetnev platform and discussed later 400-series work. The subsequent launch history records 300K and 402 in 2012 and 401 in 2014. Earlier schedules should remain dated forecasts, not be repeated as completed events.

The platform name Express-1000 in a manufacturing description does not make the spacecraft part of RSCC’s Express service fleet. A bus can support missions for different customers and programmes. When following a development history, keep the manufacturer, spacecraft platform, payload, owner and service operator separate. Shared hardware can connect programmes without making their identities interchangeable.

Keep the programme identities distinct

The operator records Yamal-401 launching in December 2014 and entering commercial service after in-orbit tests in January 2015. The interval illustrates a general distinction: reaching orbit is followed by checks before customers use the accepted service. A launch date and a commissioning — open definition date can both be correct while answering different questions.

Consider a hypothetical service contract covering ten remote facilities. Eight pass terminal and network tests; two still cannot complete the required connection. An honest acceptance report records eight ready facilities and two unresolved ones. It also identifies who will repair the remaining links. Yamal’s history makes the commercial lesson concrete: a programme succeeds for its users through working connections and continuing operations, not through a spacecraft count alone.