SSLV: evaluate a small launcher through its development flights

The Small Satellite Launch Vehicle program developed an Indian launcher intended for small payloads and more responsive launch operations. Its architecture combines three solid-propellant stages with a liquid-propulsion Velocity Trimming — open definition Module for the final delivery adjustments. A small launcher may offer scheduling and mission flexibility, but “small” does not mean the guidance or separation sequence is unimportant.

ISRO designed the system with industrial production and a simpler operating model in mind. Those are program objectives rather than proof that every future customer can launch immediately or that a universal price applies. A specific mission still needs a suitable orbit, payload interface, readiness assessment and range operations. The vehicle and its service arrangements should be evaluated with their actual dated records.

SSLV-D1 flew on August 7, 2022, but its payloads did not reach a sustainable orbit. ISRO’s investigation traced a short, unexpectedly strong vibration disturbance during second-stage separation to saturation of navigation accelerometers. Fault-detection logic treated their differing readings as a failure and switched the vehicle to a programmed salvage mode. The sensors subsequently recovered, but their data were no longer used in that mode.

The resulting guidance and propulsion sequence left a velocity shortfall and an orbit intersecting the atmosphere. A high point above Earth did not rescue the payloads from the very low perigee. This was a system interaction involving hardware dynamics, measurement limits and software decisions; saying only that “the sensors broke” would misrepresent the published investigation.

ISRO changed separation hardware, structural response and fault-detection logic, and revised how navigation information and the trimming module could be used in fallback operation. SSLV-D2 successfully launched in February 2023. SSLV-D3 delivered EOS-08 in August 2024, and ISRO declared the development project complete. These later flights provide dated verification evidence rather than a guarantee that all future flights will succeed.

For a fictional fault-response test, inject a brief sensor saturation — open definition event and ask whether the system can distinguish it from a persistent fault. Verify the fallback mode’s final orbit as well as whether the software followed its programmed steps. A procedure can execute exactly as written yet fail to achieve the mission’s intended outcome. SSLV’s development makes that distinction concrete.