PROVES-Maia and PROVES-Taygeta launched toward the International Space Station aboard NASA’s SpaceX CRS-35 cargo mission on October 13, 2026. NASA described the student-built CubeSats as demonstrations of open-source spacecraft technology and amateur radio communications. Their launch begins the next stage of the projects, but it does not establish that their planned experiments have operated successfully in orbit.
The missions combine a shared spacecraft platform with different educational and experimental objectives. Texas State University assembled PROVES-Maia, using a platform developed by Cal Poly Pomona. PROVES-Taygeta brings together Cal Poly Pomona and Mt. San Antonio College. The practical question is whether shared designs can support useful flight experiments and transferable engineering experience without requiring each institution to design every spacecraft subsystem independently.
According to NASA’s mission description, Maia plans to relay amateur radio messages using UHF and S-band communications. Taygeta carries a camera and a radiation-sensing experiment. The broader project also plans intersatellite message-routing tests using Dynamic Relay for Intersatellite Fault Tolerance, or DRIFT. These are intended activities following deployment, rather than reported results.
The PROVES documentation provides the project’s underlying rationale. Its developers describe an education-focused CubeSat kit with design files and software available under open-source licenses. The documentation includes assembly instructions, hardware information, software material, and testing guidance. Publishing those resources makes the design inspectable and reusable, but access to the files does not by itself qualify another spacecraft for flight.
A satellite platform supplies functions needed by multiple missions, including electrical power, onboard computing, structural support, and communications interfaces. A payload performs the mission’s particular experiment. Separating those roles can allow student teams to concentrate on integration and their chosen investigation. It also requires understanding the platform’s limits so that a new payload does not exceed available power, data-handling capacity, or physical space.
Texas State’s PROVES-Maia project page identifies assembly of the shared bus and payload integration as its responsibilities. That work remains substantial even when a design already exists. Components must be installed correctly, electrical connections checked, and the assembled system evaluated. Reusing a platform reduces the number of original design decisions; it does not remove responsibility for the delivered hardware.
The developers’ design philosophy emphasizes simplicity, affordability, and accessibility. They describe reducing wiring complexity and making assembly easier to understand. These are useful design objectives because fewer ambiguous connections can simplify inspection and troubleshooting. They remain objectives that must be assessed against actual builds, rather than proof that every kit will operate correctly or meet the needs of every mission.
Hardware cost is only one part of an educational space project. Staff supervision, test equipment, facilities, documentation, integration, and operations also require resources. A low component bill does not establish a low total mission cost. The economic value of reuse depends partly on whether teams can reduce repeated work and preserve knowledge between successive groups of students.
A shared platform can help with that continuity. A documented interface gives a new team a defined starting point, and a recorded test procedure explains how an earlier team checked a function. Without those records, apparent reuse can become repeated investigation of the same uncertainties. Open documentation is most useful when it describes a specific version and remains consistent with the hardware being assembled.
The project’s FlatSat testing instructions illustrate this approach. A FlatSat connects spacecraft electronics in an accessible bench arrangement before final packaging. The instructions describe checking power regulation, connecting boards, running test software, and investigating unexpected results. The educational value includes learning how components interact, rather than merely confirming that a purchased board powers on.
Bench testing and flight demonstrations answer different questions. A bench can make connectors and measurements accessible, but it does not reproduce every vibration, temperature, radiation, or orbital condition. An operating spacecraft adds evidence about the integrated system in its actual environment. Even then, a successful result has a defined scope: it applies to the tested configuration and conditions, not every future derivative.
New Space Economy’s review of small-spacecraft technology readiness discusses this context dependence. A component with flight experience in one environment does not automatically have the same readiness for a different mission. For university teams, that means previous flight heritage is useful evidence, but changes in payloads, software, or operating conditions still require assessment.
The amateur radio objectives introduce another form of participation. The intended users of the communications experiments are outside the satellite development teams, making documentation and predictable interfaces part of the experiment’s usefulness. Message exchange requires compatible equipment and software at both ends. A spacecraft transmitting data and a ground participant successfully receiving usable information are related, but distinct, observations.
Intersatellite routing adds further conditions. Two spacecraft must have a suitable communications opportunity, compatible protocols, and sufficient resources to exchange messages. A planned protocol does not establish that those conditions have occurred or that data have been delivered. Meaningful results would identify the tested configuration, the circumstances of the exchange, and the observed behavior when communication was interrupted or unavailable.
For the imaging and radiation experiments, usable results will also depend on interpretation. An image requires associated information to explain what was captured and under which conditions. Radiation measurements require an understanding of the sensor’s response and limitations. An educational demonstration can produce useful engineering experience even when its data do not support the precision or scope of a dedicated scientific observatory.
The PROVES missions offer a specific test of shared spacecraft development: whether documented hardware and software can support independent teams through assembly, integration, and operations. The openly available design also makes negative results potentially useful, provided teams record the configuration, observations, and limits of any proposed explanation. Launch is an enabling event. The more informative outcomes will be successful deployment, verified communications, experiment results, and documentation that allows another team to understand what worked, what failed, and which changes are justified.
Useful Books Available on Amazon
