SUNSAT: learn by building a working satellite

SUNSAT was developed at Stellenbosch University and launched on 23 February 1999. Its work combined Earth imaging, amateur radio and student experiments. That combination matters: a small satellite can be a training program, a research platform and a public communications resource at the same time. Counting only the launch would miss most of the work that made those roles possible. The archive lists the spacecraft as Sunsat-OSCAR-35.

The university’s contemporary account describes a voice contact through SUNSAT on 14 March 1999. This was an engineering test as well as a memorable conversation. A relay receives a signal and sends it onward; success requires compatible radios, a usable path to the satellite and a ground team that knows when to listen. One successful contact establishes that particular link worked, not that every service is continuously available.

Imagine a classroom demonstration with a six-minute usable pass. Checking the station takes one minute, and closing the session safely takes another. That leaves four minutes for student messages. At thirty seconds per message, the team can schedule eight messages. These are invented teaching values, not SUNSAT operating specifications. Their purpose is to make the overhead visible before an enthusiastic group promises more airtime than it has.

The calculation is a capacity estimate with assumptions. It treats messages as non-overlapping and leaves no extra retry allowance. If reception becomes unreliable near the horizon, the teacher should reduce the schedule or add a reserve. Shortening every message might help, but eliminating the equipment check would trade a known preparation step for an uncertain result. A useful mission plan names both the task and the conditions needed to complete it.

Budget the usable pass

The final university report records last contact on 19 January 2001. It also documents earlier thermal and battery difficulties and several attempted recovery paths. The team discussed possible causes of the final loss, including external damage, without establishing a confirmed collision. A historical account should preserve that uncertainty instead of converting the most dramatic hypothesis into a fact.

To evaluate an educational satellite, keep several kinds of evidence together: working instruments, contacts with users, trained engineers and preserved measurements. A failed subsystem can end a service while leaving useful designs and skills for later projects. Conversely, valuable training does not prove that every payload met its goals. SUNSAT introduces a recurring idea in this course: the program’s contribution is broader than a single success label, and each claimed outcome needs its own evidence.