Kargil war (1999)

Sindhurakshak was deployed very close to Karachi, Pakistan during the Kargil War in 1999.^[13][14]

President Kalam (2006)

On 13 February 2006, during the submarine's deployment in Vishakhapatnam under the Eastern Naval Command, the then President of India A. P. J. Abdul Kalam became the first Indian head of state to sail in a submarine. He was given a demonstrative excursion, during which the submarine dived and sailed in the Bay of Bengal for a few hours. He was accompanied by the Chief of Naval Staff Arun Prakash. The submarine was commanded by Commander P S Bisht.^[15][16]

Accident (2010)

A fire broke out aboard Sindhurakshak while the vessel was in Visakhapatnam in February 2010. One sailor was killed and two others were injured. Navy officials reported that the fire had been caused by an explosion in the submarine's battery compartment, which occurred due to a faulty battery valve that leaked hydrogen gas.^[17][18]

Upgrades

After the fire damage in 2010, Sindhurakshak was transported to Russia on board a heavy lift ship from Visakhapatnam in June 2010 for refit, overhaul and upgrade which lasted two and a half years.^[19] In August 2010, Sindhurakshak arrived at the Zvezdochka shipyard in Russia. The submarine was modernised, repaired and retrofitted under Project 08773, and after the upgrade, the sea trials started in October 2012. The upgrades included improved electronic warfare systems, an integrated weapon control system and a new cooling system, and were expected to extend the service life of the submarine by ten years.^[17][20] The Club-S (3M54E1 anti-ship and 3M14E land attack) missiles, USHUS sonar, СCS-MK-2 radio communication systems and Porpoise radio-locating radar, and other safety-enhancing features were incorporated.^[7] The submarine was handed back to the Indian Navy on 27 January 2013,^[12] after which it sailed back to India, under Commander Rajesh Ramkumar. This was the first time an Indian submarine had navigated under ice.^[21][22]

Incident in the Mediterranean

In March 2013, while returning from the refit, Sindhurakshak encountered severe storms in the Mediterranean Sea when it was travelling near Alexandria. This was part of the submarine's extensive three-month-long deployment, where it traveled 10,000 miles.^[20][23] The severity of the storms prevented the Alexandria port authorities from sending a tugboat, and the shallow waters prevented the submarine from diving. An emergency call was placed via the Indian Ministry of External Affairs to the Egyptian Navy, which sent its latest tugboats and towed the submarine to Port Said.^[24][25]

Explosion and sinking (2013)

On 14 August 2013, the Sindhurakshak sank after explosions caused by a fire on board when the submarine was berthed at Mumbai. The fire, followed by a series of ordnance blasts on the armed submarine, occurred shortly after midnight. Though the fire was put out within two hours, due to damage from the explosions, the submarine sank and was partially submerged in 15 metres deep water at its berth, with only a portion of the sail visible above the water surface.^[26][27][28] Three sailors on board reportedly jumped off to safety. Navy divers were also brought in as there was a possibility that 18 personnel were trapped inside and Defence Minister A. K. Antony confirmed that there were fatalities.^[29] Other sources stated that a small explosion occurred around midnight which then triggered the two larger explosions.^[20]

Due to the explosion, the front section of the submarine was twisted, bent and crumpled, and water had entered the forward compartment. Another submarine, INS Sindhughosh was berthed very close to Sindhurakshak in the congested Mumbai naval dockyard; and sustained minor fire damage, though the navy did not release details of the extent of damage.^[26][30] Sindhurakshak's double hull was credited with preventing further damage to surrounding vessels.^[31][28][32] Official sources at the time said it was "highly unlikely" the submarine could be returned to service. The navy planned to begin salvage operations after the rescue operation was completed.^[33][34] By 19 August, seven bodies had been recovered, with 11 still missing.^[35][36][37] On 31 August, six of the eleven recovered bodies had been identified and sent home for last rites with military honours.^[38]

The Navy's preliminary report indicated that "an accident or inadvertent mishandling of ammunition" was the cause of the explosions; the full incident report would only be completed after the submarine was raised.^[39][40][41] The salvage contract was awarded on 31 January 2014 to Resolve India, a subsidiary of the US-based Resolve Marine Group.^[42] The submarine was brought to the surface on 6 June 2014.^[43] In December 2014, a naval court of inquiry arrived at the preliminary conclusion that human error as a result of crew fatigue caused the disaster. A senior officer stated that "the crew was working beyond their prescribed hours. Fatigue and exhaustion may have triggered human error that led to the accident. Standard operating procedures were violated at several levels".^[44] A 2017 report by the Comptroller and Auditor General of India quoted the Navy's Board of Inquiry stating that "Submarine authorities concerned didn’t properly assess the crew fatigue, besides, the submarine was holding ammunition nearing life expiry".^[45]

Initially, the navy was hopeful of using Sindhurakshak after it was salvaged, but on Navy Day 2015, Vice Admiral Cheema confirmed the Sindhurakshak would be disposed of.^[46][47][48] After a period of use for the training of marine commandos, the submarine was sunk in 3000 metres of water in the Arabian Sea in June 2017.^[49][50]