Summary：India Mourns Lost Satellite and Server After PSLV Failure **Introduction** India’s space community

India Mourns Lost Satellite and Server After PSLV Failure

**Introduction**
India’s space community is grappling with a sobering setback after the Polar Satellite Launch Vehicle (PSLV)‑C55 mission failed to place its payload into orbit. The rocket, which lifted off from Sriharikota on a clear morning, suffered an anomaly during the second‑stage burn, resulting in the loss of both a communications satellite and a ground‑based data server that was to be hosted on the spacecraft. Officials from the Indian Space Research Organisation (ISRO) confirmed the mishap within hours, prompting a nationwide wave of disappointment and a renewed focus on what went wrong.

**Key Developments**
Telemetry indicated a sudden drop in thrust from the Vikas engine shortly after stage separation, triggering an automatic safety shutdown. The vehicle deviated from its planned trajectory and ultimately disintegrated over the Bay of Bengal. The primary payload, GSAT‑32, was intended to augment broadband services in remote regions, while the secondary server—part of a pilot project for on‑orbit data processing—was meant to test edge‑computing capabilities for future deep‑space missions. ISRO chairman S. Somanath addressed the press, stating that a failure analysis committee has been convened and that preliminary findings point to a possible fuel‑line obstruction. No casualties were reported, but the financial impact is estimated at several hundred million dollars, factoring in satellite construction, launch services, and the lost server hardware.

**Industry Analysis**
The incident underscores the inherent risks associated with relying on a workhorse launcher like the PSLV for increasingly complex payloads. Industry analysts note that while the PSLV boasts a success rate above 95%, the recent failure highlights the need for stricter quality‑control protocols, especially as ISRO pushes toward heavier payloads and reusable technologies. Comparisons are being drawn to the 2017 PSLV‑C39 anomaly, which also involved a second‑stage issue, suggesting a pattern that warrants a comprehensive review of the Vikas engine’s manufacturing and inspection processes.