2008 Russian submarine K-152 Nerpa accident

2008 Russian submarine K-152 Nerpa accident

An Akula-class submarine similar to K-152 Nerpa
Time 08:30 local time
Date 8 November 2008
Location Peter the Great Gulf, Sea of Japan, off the coast of Primorski Krai
Casualties
20 killed
41 injured
Accident occurred on board the Russian submarine K-152 Nerpa

The K-152 Nerpa accident was an incident that occurred aboard the Russian submarine K-152 Nerpa on 8 November 2008, which resulted in the deaths of 20 people and injuries to 41 more. The deaths and injuries were caused by an unsanctioned release of fire suppressant gas inside the submarine during a submerged test run during the vessel's sea trials in the Sea of Japan. The gas caused victims to die of asphyxiation or suffer frostbite in their lungs. The incident was the worst Russian submarine disaster since Kursk sank in 2000.[1] Three of the dead were military personnel and the rest were civilians from the Vostok, Zvezda, Era and Amur shipbuilding yards who were members of the acceptance team.[2]

Sequence of events

At the time of the accident, Nerpa was undergoing sea trials at the Russian Pacific Fleet's test range in Peter the Great Gulf, an inlet of the Sea of Japan adjoining the coast of Russia's Primorski Krai province. The vessel had not yet been accepted by the Russian Navy but was undergoing plant tests under the supervision of a team from the Amursky Ship Building Plant.[3] For this reason, it had a much larger than usual complement aboard, totalling 208 people, 81 military personnel and 127 civilian engineers from the shipyards responsible for building and outfitting the submarine.[4]

The accident occurred at 8:30 PM local time on 8 November 2008,[5] during the submarine's first underwater test run.[3] The submarine's fire extinguishing system was triggered, sealing two forward compartments and filling them with freon R-114B2 gas (Dibromotetrafluoroethane, known as khladon in Russian).[6] The gas, a hydrobromofluorocarbon refrigerant, is used in the Russian Navy's LOKh (lodochnaya obyemnaya khimischeskaya – "submarine volumetric chemical") fire suppressant system. Each compartment of a Russian submarine contains a LOKh station from which freon can be delivered into that or adjacent compartments.[7] Freon displaces oxygen, enabling it to extinguish fires rapidly in enclosed spaces. In high concentrations, it can cause narcosis, which progresses by stages into excitation, mental confusion, lethargy, and ultimately asphyxiation.[4]

Twenty people died of asphyxiation in the accident. The number of injured was initially put at 21[8] but was later revised to 41 by the Amurskiy Shipbuilding Company, a number of whose employees were among the injured. Many of the injured were reported to be suffering from frostbite caused by the chilling effect of the gas.[9]

Following the incident, the Udaloy-class destroyer Admiral Tributs and the rescue vessel Sayany were dispatched from Vladivostok to provide assistance to the stricken submarine. The injured survivors were transferred to the destroyer and sent to military hospitals for treatment, while the submarine returned under its own power to Primorsky Krai.[4] According to naval spokesman Igor Digaylo, the vessel was not damaged in the incident and radiation levels remained normal.[10]

Causes

Two principal explanations of the disaster have been advanced by naval experts and the media – that there was a failure of the equipment, or that the accident was caused by human error.

Equipment failure

The LOKh fire suppression system aboard Nerpa was reportedly of a new type that had not previously been used aboard any Russian submarine. Earlier versions of the LOKh system only operate under manual control from the duty shift console. The new system installed on Nerpa could also operate in automatic mode, responding to smoke and rises in compartment temperature and activating individually in each compartment. According to the testimony of an engineer from the Zvezda shipyard, this had malfunctioned before while the submarine was being readied for its sea trials. Some commentators speculated that the system could have been accidentally activated by cigarette smoke.[11]

Human error

On 10 November, a Russian Navy statement blamed the disaster on an "unsanctioned operation" of the fire suppression system aboard Nerpa.[4] Three days later, naval investigators announced that a crewman, named unofficially as Dmitry Grobov, had turned on the system "without permission or any particular grounds". According to reports in the Russian media, Grobov believed that a local control unit was not connected. Out of boredom he started playing with it. The submarine local control units are protected by five digit access numbers but during sea trials the access codes were penciled on the units. The seaman increased readings up from the original value of 30 °C to 78 °C, causing the control system to believe that there was a fire on board. The control unit requested permission to start the fire suppression system. Grobov granted permission, possibly without realizing what he was doing.[12][13] He was charged and would face up to seven years in prison if convicted.

Colleagues expressed skepticism, describing the accused crewman as an experienced and skilled specialist.[14] Several commentators suggested that the crewman was being treated as a scapegoat.[15] A number of retired naval officers told the business daily Kommersant that they doubted that Grobov was solely to blame, as it was impossible for one person to activate the system due to it requiring multiple levels of confirmation before it can be activated.[16]

Exacerbating factors

According to survivors, those affected by the gas release were caught off guard and may not have been alerted in time due to warning sirens sounding only after the gas had already begun pouring in. Some of the victims were reported to have been unable to don breathing kits before they suffocated.[17]

Igor Kurdin, a former Typhoon-class submarine commander and the current head of the St. Petersburg Submariners Club, attributed the high casualty count to the presence of a large number of civilian specialists on the submarine at the time of the accident. 17 of 20 people who perished in the accident were civilians. He noted that civilian observers would be untrained in the proper response to the release of the boat's firefighting gas, which would be preceded by a specific light and sound signal, after which all on board are supposed to put on oxygen masks to allow them to survive during the 30-minute period required to ventilate the compartments before they can be reopened. In addition, because the accident occurred at 8:30 PM many of the civilian specialists and crewmen would likely have been asleep, and unable to don their oxygen masks in time.[18] The accident was the country's worst since 2000, when a torpedo exploded and sank another Russian nuclear submarine, Kursk, killing 118 people.[19]

Mikhail Barabanov, editor-in-chief of Moscow Defense Brief, said that accidental discharge of the fire suppression system on submarines is common, but usually does not cause fatalities. However, Nerpa had a "crowd of civilians" on board and the boat was "overcrowded". His understanding was, "the fire alarm failed to work, so the passengers did not realize that the gas started to displace oxygen in the affected compartments."[20] Some suggested that there had not been enough breathing kits available for the larger than usual number of people aboard, or that the civilians had not been properly trained in their use.[2] Survivors stated that some breathing apparatuses had not worked or had failed after only a few minutes; some of the dead were reportedly found still wearing their breathing kits.[14]

Official reactions

Russia

Russian President Dmitry Medvedev ordered Defence Minister Anatoliy Serdyukov to undertake an immediate investigation into the causes of the accident.[4] Colonel General Aleksandr Kolmakov, the First Deputy Minister of Defenсe, and Admiral Vladimir Vysotskiy, the Navy Commander-in-Chief, were sent to the Far East region to oversee the investigation. The President also ordered Prosecutor General Yuriy Chayka to undertake a criminal investigation of the incident and a team of officers from the Main Military Procuracy were sent to investigate the case.[3] The Russian Navy and the governments of the Primorsky Krai and Khabarovsk Krai regions announced compensation packages to assist the families of those who lost their lives in the accident.[21]

India

Initially, there were reports in Russian and Indian media of a crew from the Indian Navy heading to Vladivostok later in November 2008, where they will start "trainings and preparations" aboard Nerpa.[22][23][24] These reports came amid speculations that Russia might lease a newly built nuclear submarine to India.[25] Reports later confirmed that the submarine which suffered the accident was indeed the one which was planned to be leased to India.[26][27]

Indian naval officials said, "Our officials are already in Russia monitoring the submarine project; both during its construction phase and now during the sea trial phase. We are keeping a close watch on the developments."

Opinions were divided among analysts about the effect that the accident would have on military relations with India. A Russian defense analyst remarked that it was unlikely that the incident "would scare India away."[28] On the other hand, Golts stated, "I think this is going to be another serious blow to cooperation with India. India will be even more concerned about the quality of Russian weapons." He also stated that India had desired secrecy, lest the United States apply pressure to scuttle the deal, but that with no other suppliers of such submarines, India would probably still accept the deal.[29] The planned lease of the submarine to India was in 2008 reported to be cancelled following the incident.[30] However, the submarine was officially inducted into the Indian Navy on 4 April 2012 as INS Chakra.[31][32]

References

  1. Syal, Rajeev (9 November 2008). "Twenty die in nuclear submarine accident". London: The Guardian. Retrieved 9 November 2008.
  2. 1 2 Ren TV, Moscow, 2030 GMT 10 November 2008
  3. 1 2 3 Poroskov, Nikolai (10 November 2008). "Accidents More Terrifying Than Fire". Vremya Novostei.
  4. 1 2 3 4 5 "Twenty Persons Perished Aboard a Submarine Due to a Defective Fire-Extinguishing System". Komsomolskaya Pravda. 9 November 2008.
  5. Loiko, Sergei L. (8 November 2008). "False fire alarm blamed in Russian sub deaths". The Columbus Dispatch. Retrieved 11 November 2008.
  6. "Fire on Board the Russian Navy Akula II Nuclear Submarine kills Twenty Russian Sailors". International Online Defense Magazine. 11 November 2008. Retrieved 17 November 2008.
  7. Romanov, D.A.; Moore, Kenneth J.; trans. Acus, Jonathan E. Fire at Sea: The Tragedy of the Soviet Submarine Komsomolets, p. 250. Brassey's, 2006. ISBN 1-57488-426-3
  8. "Twenty die on Russian submarine". BBC. 9 November 2008. Archived from the original on 9 November 2008. Retrieved 9 November 2008.
  9. ""Nerpa" Investigating Officers Debarred". Vostok Media. 19 November 2008. Archived from the original on 9 January 2009. Retrieved 28 November 2008.
  10. "Primorye flags at half-mast mourning over killed in sub accident". Information Telegraph Agency of Russia, 11 November 2008
  11. Zhurman, Olga; Gavrilov, Yuriy (11 November 2008). "Berth of Sadness: The Far East Is Saying Farewell to Deceased Sailors and Shipbuilders". Rossiyskaya Gazeta.
  12. Матрос запустил смертельный газ на глазах у своего командира? Komsomolskaya Pravda 15 November 2008 (Russian)
  13. Матрос включил систему пожаротушения на "Нерпе" от скуки Lenta.ru 15 November 2008
  14. 1 2 Halpin, Tony (13 November 2008). "Crew member blamed for Russian submarine disaster". London: The Times. Retrieved 27 November 2008.
  15. "Russia accused of cover-up over gassing of 20 sailors on nuclear submarine", Daily Mail, 13 November 2008
  16. "Crew member 'tampered with temperature sensor on Nerpa sub'". RIA Novosti. 17 November 2008. Retrieved 28 November 2008.
  17. "Russian sub survivors: Freon killed as crew slept". Associated Press. 11 November 2008. Retrieved 27 November 2008.
  18. Loiko, Sergei L. (10 November 2008). "False alarm blamed for Russian submarine deaths". Los Angeles Times. Archived from the original on 13 December 2008. Retrieved 11 November 2008.
  19. "Russian navy: sub accident kills at least 20". Associated Press. 9 November 2008. Retrieved 9 November 2008.
  20. "Tragedy Under The Sea". Newsweek. Archived from the original on 13 November 2008. Retrieved 11 November 2008.
  21. Centre TV, Moscow. 1130 GMT, 10 November 2008
  22. "Hindoos lease our submarine – Business – Vladivostok News". Vn.vladnews.ru. Retrieved 11 November 2008.
  23. "The Hindu News Update Service". Chennai, India: Hindu.com. 2 November 2008. Archived from the original on 8 December 2008. Retrieved 11 November 2008.
  24. Sandeep Unnithan. "India Today – India's most widely read magazine". Indiatoday.digitaltoday.in. Retrieved 11 November 2008.
  25. "domain-b.com : Speculation mounts about Indian lease of new Russian nuclear attack sub". Domain-b.com. Archived from the original on 3 November 2008. Retrieved 11 November 2008.
  26. "India was planning to lease Russian sub that suffered fatalities, reports say.". Kansascity.com. Retrieved 11 November 2008.
  27. Halpin, Tony (11 November 2008). "Russian nuclear death sub 'was due for delivery to India'". London: Timesonline. Archived from the original on 11 November 2008. Retrieved 11 November 2008.
  28. "Nuclear Submarine Accident Kills 20". Moscow Times. 10 November 2008. Archived from the original on 12 November 2008. Retrieved 11 November 2008.
  29. "Behind the Russian Sub Disaster.". Newsweek. Archived from the original on 13 November 2008. Retrieved 11 November 2008.
  30. "Nerpa nuclear submarine to join Russian Navy". Newstrack India. Retrieved 27 November 2008.
  31. "INS Chakra: Govt inducts Russian-origin Akula II class Nerpa into Navy". Economic Times. 4 April 2012. Retrieved 3 March 2015.
  32. "INS Chakra formally inducted into Indian Navy". India Today. 4 April 2012. Retrieved 3 March 2015.
This article is issued from Wikipedia - version of the 9/19/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.