Small spacecraft technology: prove capabilities within tight limits

NASA’s Small Spacecraft Technology program supported development and flight demonstrations that expanded what compact spacecraft could do. NASA’s 2026 technology review identifies the program as Small Spacecraft & Distributed Systems, or SSDS, formerly SST. These names describe a program lineage, not two unrelated missions. A technology portfolio can contain several spacecraft, research projects and partnerships.

CAPSTONE is one example: the small spacecraft tested operations in a lunar near-rectilinear halo orbit and navigation approaches. NASA records that its primary objectives were completed in 2023, followed by extensions. Starling provides a different example involving four small spacecraft and distributed operations experiments. Neither example means every small satellite belongs to this NASA program or uses the same design.

Reducing size does not remove the need for power, communications, navigation, thermal control and mission operations. A compact system has limited room and resources, so a change to one subsystem can affect others. A transmitter may fit physically yet demand more electrical power or heat rejection than the rest of the design can support. The interface between parts matters as much as the performance of each part in isolation.

Suppose a fictional spacecraft can continuously supply 10 watts, while its instruments need 6 watts and its transmitter needs 5 watts. Running both continuously requires 11 watts and exceeds the stated supply. Scheduling activities may help if batteries, energy balance and operational requirements permit, but simply calling the spacecraft small does not solve the deficit. Peak power and energy over time are related constraints that must both be checked.

A useful flight demonstration defines a capability, test conditions and evidence of performance. A navigation experiment might compare estimated position with an independent reference. A distributed-system experiment might test how spacecraft coordinate information when a link changes. Successful launch is necessary for many such tests, but it is not equivalent to completing the technology objective.

Imagine a demonstration that works only with frequent ground intervention. That result may still be useful, while falling short of a claim of fully autonomous operation. Reporting the conditions helps later designers decide what can be transferred to another mission and what needs further development. The program’s value is not merely producing smaller hardware; it is establishing credible capabilities and their limits for future science, exploration and services.