MDASat: test a constellation beyond launch

MDASat is South Africa’s Maritime Domain Awareness satellite initiative. Its first three spacecraft, MDASat-1a, MDASat-1b and MDASat-1c, launched in January 2022. Built through Cape Peninsula University of Technology, they extended the country’s work on compact satellites and maritime radio reception. Their purpose was to contribute information about vessels, not simply to increase the number of objects bearing a national flag in orbit.

The preserved Transporter-3 launch photograph shows their shared launch event. The satellites are enclosed inside the rocket’s fairing, so none can be individually identified in the picture. A launch photo can establish context when the mission identity is documented, but it cannot reveal the payloads’ later performance. This distinction becomes particularly important for rideshares, where many unrelated spacecraft travel on the same rocket.

A spacecraft may transmit a basic beacon while a more complicated payload remains unverified. The platform’s command link, onboard data connections, instrument output and ground processing each need tests. SANSA’s 2023/24 annual report records a communications-bus problem and incomplete commissioning — open definition of the MDASat payloads. That dated assessment qualifies the early launch milestone; it is not a claim about the constellation — open definition’s condition on every later date.

Consider an invented acceptance exercise with four required checks on each of three satellites. There are twelve satellite-check results to document. If ten pass and two remain unresolved, the program has ten passing results, not three fully accepted satellites. Both unresolved checks might belong to one spacecraft, or they might be split across two. Without that mapping, even the number of fully accepted spacecraft cannot be calculated. A total alone hides the structure of the evidence.

Track acceptance by spacecraft

More satellites can create more opportunities to receive messages, but their usefulness depends on orbital geometry, receiver behavior, communications access and ground processing. Three spacecraft passing over a region at similar times do not automatically provide continuous coverage. Planners should describe the longest relevant gaps and the age of delivered information, rather than assuming that a constellation label guarantees an uninterrupted service.

This connects back to all three earlier lessons. SUNSAT shows why operations and learning outcomes both matter. SumbandilaSat demonstrates the distinction between useful observations and complete knowledge. ZACUBE introduces message age and missing reports. MDASat brings those ideas together at constellation scale: a credible program summary should identify what was built, what flew, which functions were demonstrated and what the dated evidence still leaves unresolved. Those distinctions help explain setbacks without erasing the engineering work or overstating its results.