INS Sindhurakshak (S63)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
INS Sindhurakshak (S63).jpg
INS Sindhurakshak
History
India
Name: INS Sindhurakshak
Builder: Admiralty Shipyard, Saint Petersburg
Laid down: 16 February 1995
Launched: 26 June 1997
Commissioned: 24 December 1997
Identification: Pennant number: S63
Fate: Sank at Mumbai's naval dockyards on 14 August 2013 due to on board explosions, but possibility of salvage remains.[1][2]
Status: Inactive
Badge: INS Sindhurakshak
General characteristics
Class & type: Sindhughosh-class submarine
Displacement:
  • 2325 tons surfaced
  • 3076 tons submerged
Length: 72.6 m (238 ft)
Beam: 9.9 m (32 ft)
Draught: 6.6 m (22 ft)
Propulsion:
  • 2 × 3650 hp diesel-electric motors
  • 1 × 5900 hp motor
  • 2 × 204 hp auxiliary motors
  • 1 × 130 hp economic speed motor
Speed:
  • Surfaced: 10 knots (19 km/h)
  • Snorkel Mode: 9 knots (17 km/h)
  • Submerged: 17 knots (31 km/h)
Range:
  • Snorkel Mode: 6,000 mi (9,700 km) at 7 kn (13 km/h)
  • Submerged: 400 miles (640 km) at 3 knots (5.6 km/h)
Endurance: Up to 45 days with a crew of 52
Test depth:
  • Operational depth: 240 m (790 ft)
  • Maximum depth: 300 m (980 ft)
Complement: Seven officers and 61 ratings[3]
Armament:
  • 9M36 Strela-3 (SA-N-8) surface-to-air missile
  • 3M-54 Klub-S anti-ship and land-attack missiles
  • Type 53-65 passive wake-homing torpedo
  • TEST 71/76 anti-submarine active-passive homing torpedo
  • 24 × DM-1 mines in lieu of torpedo tube

INS Sindhurakshak (Sanskrit, for Protector of the Seas)[4] was a Russian-made Kilo-class 877EKM[5][6][7] (Sindhughosh-class) diesel-electric submarine of the Indian Navy.[8] Commissioned on 24 December 1997, it was the ninth of the ten Kilo-class submarines in the Indian Navy.[9] On 4 June 2010, the Indian Defence Ministry and Zvezdochka shipyard signed a contract worth US$80 million to upgrade and overhaul the submarine. After the overhaul, it returned to India from Russia between May and June 2013.[10]

The submarine suffered a minor fire incident in 2010 and a major one on 14 August 2013, which resulted in its sinking at Mumbai's naval dockyard.[11][12] At the time of its sinking, there were reportedly 18 crew members on board and all of them are either dead or presumed so.[13][14]

Construction

Sindhurakshak was constructed at the Admiralty Shipyard in Saint Petersburg, Russia. Construction of the submarine began in 1995. It was launched in June 1997 and delivered to India in December 1997.[9][15]

Service history

Kargil war (1999)

Sindhurakshak was deployed very close to Karachi, Pakistan during the Kargil War in 1999.[16][17]

President Kalam (2006)

File:President on-board INS Sindhurakshak.jpg
President APJ Abdul Kalam on-board Sindhurakshak

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.[18][19]

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.[20][21]

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.[22] 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.[20][23] 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.[9] The submarine was handed back to the Indian Navy on 27 January 2013,[15] after which it sailed back to India, under Commander Rajesh Ramkumar. This was the first time an Indian submarine had navigated under ice.[24][25][26]

File:INS Sindhurakshak (S63)-8edited.jpg
Sindhurakshak at Portsmouth, UK, where it was berthed on its way to India after the mid-life overhaul

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.[23][27] 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.[28][29]

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. The fire was put out within two hours. It is unclear exactly what caused the fire. 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.[30][31][23][32][33] 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. Defence Minister A. K. Antony confirmed that there were fatalities.[13] Other sources state that a small explosion occurred around midnight which then triggered the two larger explosions.[23]

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, however the navy has not released any details of the extent of damage.[30][34] Sindhurakshak's double hull was credited with preventing further damage to surrounding vessels.[35][32][36] Official sources said it was "highly unlikely" the submarine could be returned to service. The navy plans to begin salvage operations after the rescue operation is completed.[37][38] By 19 August, seven bodies had been recovered, with 11 still missing.[39][40][41] A Board of Inquiry, set up by the navy, was expected to present a report on the cause of the disaster by mid-September.[42] On 31 August, six of the eleven recovered bodies had been identified and sent home for last rites with military honours.[43]

The preliminary report indicated that "an accident or inadvertent mishandling of ammunition" was the cause of the explosions.[44][45] The complete incident report would only be submitted after the submarine is brought up from the harbor bed.[46] The salvage job was awarded to Resolve India, a subsidiary of the US-based Resolve Marine Group, on 31 January 2014 and will be completed by the end of June 2014.[47] The Chief of Naval Staff Admiral D.K. Joshi said that the navy was hopeful of using Sindhurakshak after it is salvaged, which would depend upon the hull survey to be done after the boat is re-floated.[1][2] The submarine was brought to the surface on 6 June 2014.[48]

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.” [49]

See also

References

<templatestyles src="Reflist/styles.css" />

Cite error: Invalid <references> tag; parameter "group" is allowed only.

Use <references />, or <references group="..." />

External links

Images

  1. ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ 9.0 9.1 9.2 Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ 15.0 15.1 Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ 20.0 20.1 Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ 23.0 23.1 23.2 23.3 Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ 30.0 30.1 Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ 32.0 32.1 Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ Lua error in package.lua at line 80: module 'strict' not found.
Retrieved from "https://infogalactic.com/w/index.php?title=INS_Sindhurakshak_(S63)&oldid=3091331"