Russian submarine Ekaterinburg (K-84)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
File:K-84 Ekaterinburg in 2014.jpg
K-84 Ekaterinburg at Zvezdochka, summer 2014
History
Soviet Union, Russia
Name: K-84 Ekaterinburg
Namesake: City of Yekaterinburg
Builder: Northern Machinebuilding Enterprise (Sevmash)
Laid down: 17 February 1982
Commissioned: 30 December 1985
Status: in active service, as of 2024[1]
General characteristics
Class & type: Delta IV-class submarine
Displacement:
  • 11,740 tons (surface)
  • 18,200 tons (submerged)[2]
Length: 167.4 metres (549 ft)[2]
Beam: 11.7 metres (38 ft)[2]
Draft: 8.8 metres (29 ft)[2]
Propulsion: Two VM4-SG nuclear reactors[2]
Speed:
  • 14 knots (26 km/h; 16 mph) (surface)
  • 24 knots (44 km/h; 28 mph) (submerged)[2]
Endurance: 90 days[2]
Complement: 140 officers and men[2]
Armament:

K-84 Ekaterinburg (Russian: К-84 Екатеринбург) is a Project 667BDRM Delfin class (NATO reporting name: Delta IV) nuclear-powered ballistic missile submarine. The submarine was laid down on 17 February 1982 at the Russian Northern Machine-Building Enterprise (Sevmash).[2] She was commissioned into the Soviet Navy on 30 December 1985.[2] After the collapse of the Soviet Union, the submarine continued to serve in the Russian Navy. Initially known only by her hull number, in February 1999 she was renamed after the city of Yekaterinburg.[2][3]

Construction

Construction of the nuclear submarine Ekaterinburg (K-84) began at the Northern Machinebuilding Enterprise (Sevmash) in Severodvinsk on 17 February 1982, before being commissioned into the Soviet Navy on 30 December 1985.[2] She was the second of the seven-boat Project 667BDRM Delfin class, which was developed at the Rubin Design Bureau in September 1975.[4] A ballistic missile submarine, she was designed primarily to carry up to 16 R-29RM Shtil (NATO designation: SS-N-23 Skiff) SLBM for use against military and industrial facilities in the case of a nuclear war.[2][4] Each Shtil missile carries ten 100 kt multiple independently targeted reentry vehicles, and has a circular error probable of 500 metres (1,600 ft).[5] She is also equipped with RPK-7 Veter (NATO designation: SS-N-16 Stallion) anti-ship missiles for use against large surface vessels, and self-defense torpedoes.[5]

Operational history

After commissioning, Ekaterinburg was deployed to the base at Olenya Bay, and during the second half of 1986 underwent acoustic trials.[2] In August 1989, Ekaterinburg conducted a failed launch of all its missile under Operation Behemoth. Four months later, in December 1989, she was the first submarine to attempt to launch all her missiles while underwater; the first launch was successful, though the second was not.[2] In 1993, she was transferred to the base at Sayda-Guba.[2] On 3 December 1996, Ekaterinburg entered the Zvezdochka shipyard in Severodvinsk for an overhaul, though work did not begin until March 1998.[2] She re-entered service in 2003, based in Yagelnaya Bay.[2] She test-fired R-29RMU Sineva missiles in December 2003 and June 2004, and during Northern Fleet exercises in August 2005 fired missiles at the Kamchatka range.[2] Also in 2005, Ekaterinburg was awarded the Navy Commander's Prize for her missile launches.[2] In 2006, she successfully fired missiles at the Chizha Range from the North Pole.[2] On 20 May 2011, the boat fired the first R-29RMU2 Liner SLBM, aimed at the Kura Test Range.[6]

Fire incident and near nuclear catastrophe

On 29 December 2011 around 1220 UTC, Ekaterinburg caught fire while in drydock in Murmansk, and after several hours of firefighting efforts, she was partially sunk in an effort to control the fire.[7] Initial statements from Russian authorities indicate there were no injuries or radiation leakage, and that the vessel was not carrying any weapons as she was drydocked for repairs. The fire apparently began when sparks from welding being done on the boat's hull ignited wooden scaffolding around the ship, then spread to the flammable rubber coating covering the hull.[8] Russian President Dmitry Medvedev ordered the repair of the submarine and a thorough investigation of the incident on 30 December 2011.[9] The boat's hydro acoustic system was disabled in the fire.[9] Some sources speculate that the submarine's pressure hull suffered possible structural damage due to the intense heat; the temperature inside the torpedo room allegedly rose to 60-70 °C.[10]

A commission was to study the damage to the submarine and determine whether it was economical to repair it.[3] A Zvezdochka shipyard spokesperson said that the repairs would take more than a year.[11]

On 12 January 2012 ITAR-TASS reported that the repair of the submarine would take three to four years.[12] The repair would be combined with a scheduled refit that was to start in 2013. As it would be some months before the submarine can be transferred to the shipyard due to winter sea ice, the repairs would begin in May–June, 2012, so the submarine would not be expected to return to service before 2015.

On 14 February 2012, Vlast reported that the submarine had been carrying 16 R-29RM Shtil (NATO designation SS-N-23 Skiff) SLBMs, armed with four nuclear warheads in each missile, at the time of the fire, though officials had said at the time of the fire that no nuclear weapons were on board, as they had been unloaded before the fire broke out.[13] According to Vlast, the presence of nuclear weapons on the burning vessel would have meant that "Russia, for a day, was on the brink of the biggest catastrophe since the time of Chernobyl."[13]

Viktor Litovkin, editor-in-chief of Nezavisimoye Voyennoye Obozreniye, seriously doubted that a nuclear submarine could undergo maintenance with missiles and torpedoes on board because an off-duty submarine cannot have any weapons on board due to the Russian-American Prague agreement on nuclear arms. Litovkin explains that "when such a submarine is in dock, all missile pits are opened so that the Americans could check from surveillance satellites that there are no missiles in them... Moscow and Washington notify each other when nuclear missile carriers are going off duty for maintenance and Russia does the same surveillance of American subs."[14]

References

  1. http://flot.com/2014/181145/
  2. 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 2.10 2.11 2.12 2.13 2.14 2.15 2.16 2.17 2.18 2.19 2.20 2.21 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 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 Lua error in package.lua at line 80: module 'strict' not found.
  10. http://www.novayagazeta.ru/inquests/50842.html
  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.

External links