Follow Malindi from launch base to ground network

The San Marco Launch Complex off Kenya’s coast belongs to a history of launches, while the land-based Luigi Broglio Space Centre supports communication with spacecraft. Italy’s embassy in Nairobi records nine orbital launches and eighteen suborbital launches between 1967 and 1988. It separately describes the centre’s satellite operations, data reception and training work. Ending one activity does not imply that every facility at the site stopped working.

That distinction also separates geography from responsibility. A spacecraft can launch from one country, use another country’s ground service and be operated by a third organisation. Kenya and Italy’s cooperation provides the setting for Malindi; particular missions and instruments have their own responsibilities and interfaces.

Separate the activities at Malindi

ESA’s 2015 account describes MAL-X, a two-metre X-band terminal added at Malindi for LISA Pathfinder support. The need was a particular communications opportunity near the equator, complementing the station at Kourou. A terminal is selected against a mission’s path, radio interface and operating task; its dish diameter alone does not identify every mission it can support.

A ground system also needs power, cooling, signal processing, timing, network connections and trained operators. An impressive dish with an incompatible receiver cannot supply the required service. Treat the antenna as one part of the working chain, rather than a complete description of the station.

A 2015 photograph documents a configuration seen then. It is not a current inventory or proof that every later mission uses the same hardware. Likewise, the embassy’s account of a newer cooperation agreement does not make older equipment lists current. Use dated evidence for the claim it actually supports.

For an invented service request, begin with the mission’s required frequency, compatible signal handling, contact window, delivery deadline and responsible team. Ask for evidence against each requirement. A historic success can explain experience, but a changed interface still needs an appropriate compatibility check.