Wikipedia

List of submarine and submersible incidents since 2000

(Redirected from List of submarine incidents since 2000)

This article describes major accidents and incidents involving submarines and submersibles since 2000.

USS San Francisco in a dry dock, after hitting an underwater mountain 350 miles (560 km) south of Guam in 2005

2000s

edit

2000

edit

Kursk explosion

edit
Main article: Kursk submarine disaster

In August 2000, the Russian Oscar II-class submarine Kursk sank in the Barents Sea when a leak of high-test peroxide in the forward torpedo room led to the detonation of a torpedo warhead, which in turn triggered the explosion of around half a dozen other warheads about two minutes later. This second explosion was equivalent to about 3–7 tons of TNT[1] and was large enough to register on seismographs across Northern Europe.[2] The explosion and the flooding by high pressure seawater killed the majority of the submarine's 118 sailors. Twenty-three survived in the stern of the submarine, but despite an international rescue effort, they died several days later either from a flash fire or suffocation due to a lack of oxygen. The Russian Navy was severely criticised in its home country by family members of the deceased crew for failure to accept international help promptly.

2001

edit

Ehime Maru and USS Greeneville collision

edit
Main article: Ehime Maru and USS Greeneville collision
 
Greeneville in drydock at Pearl Harbor on 21 February 2001 after hitting and sinking Ehime Maru.

On 9 February 2001, the American submarine USS Greeneville accidentally struck and sank a Japanese high-school fisheries training ship, Ehime Maru, killing nine of the thirty-five people aboard, including four students, 10 miles (16 km) off the coast of Oahu. The collision occurred while members of the public were on board the submarine observing an emergency surface drill.

A naval inquiry found that the accident was the result of poorly executed sonar sweeps, an ineffective periscope search by the submarine's captain, Commander Scott Waddle, bad communication among the crew and distractions caused by the presence of the 16 civilian guests aboard the submarine.

The Navy and the command of Greeneville have been criticized for making no immediate attempt to help the Japanese on Ehime Maru that survived the initial collision. Weather conditions were producing 8-to-12-foot (2.4 to 3.7 m) waves and the submarine's partially surfaced condition prevented the opening of deck hatches. These were cited as reasons for the submarine captain's choosing to stand off and remain close by.[3] While the U.S. Coast Guard directly responded, survivors resorted to automatically deployed life rafts from Ehime Maru.

2002

edit

USS Dolphin major flooding and fire

edit

In May 2002, the U.S. Navy research submarine USS Dolphin experienced severe flooding and fires off the coast of San Diego, California. The ship was abandoned by the crew and Navy civilian personnel, who were rescued by nearby naval vessels. No one was seriously injured. Although severely damaged, the boat was towed back to San Diego for overhaul.

USS Oklahoma City collision with tanker

edit

On 13 November 2002, USS Oklahoma City collided with the Leif Hoegh liquefied natural gas tanker Norman Lady, east of the Strait of Gibraltar. No one on either vessel was hurt, and there were no leaks from fuel tanks and no threat to the environment, but the submarine sustained damage to her periscope and sail area, and put into La Maddalena, Sardinia, for repairs. Her commanding officer, Commander Richard Voter, was relieved of his command on 30 November. One other officer and two enlisted crew members were also disciplined for dereliction of duty.

HMS Trafalgar

edit

In November 2002, the Royal Navy's Trafalgar-class submarine, HMS Trafalgar, ran aground close to Skye, causing £5 million worth of damage to her hull and injuring three sailors. It was travelling 50 metres (160 ft) below the surface at more than 14 knots (26 km/h) when Lieutenant-Commander Tim Green, a student in the Submarine Command Course, ordered a course change that took her onto the rocks at Fladda-chùain, a small but well-charted islet.

A report issued in May 2008 stated that tracing paper (used to protect navigational charts) had obscured vital data during a training exercise. Furthermore, the officer in charge of the training exercise had not been tracking the submarine's position using all the available equipment. Commanders Robert Fancy and Ian McGhie were court martialled and reprimanded over the incident.[4]

2003

edit

HMAS Dechaineux flooding

edit

On 12 February 2003, HMAS Dechaineux, a Collins-class submarine of the Royal Australian Navy (RAN) was operating near her maximum safe diving depth off the coast of Western Australia when a seawater pipe burst.[5] The high-pressure seawater flooded the lower engine room before the hose was sealed off. It was estimated that if the inflow had continued for another twenty seconds, the weight of the water would have prevented Dechaineux from returning to the surface.[5] The Navy recalled all of the Collins-class submarines to the submarine base HMAS Stirling after this potentially catastrophic event, and after naval engineers were unable to find any flaws in the pipes that could have caused the burst, they commanded that the maximum safe depth of these submarines be reduced.[5]

Great Wall 361 accident

edit
See also: Chinese submarine 361

In May 2003, China announced that the entire ship's crew (70 people) had been killed aboard the Ming-class Great Wall submarine 361 due to a mechanical malfunction.[6] The accident took place off the coast of Liaoning province in northeast China. The vessel was recovered and towed to an unidentified port, where the cause of the accident was identified. When the battery was running low, the submarine surfaced with a vent opening for oxygen, which was consumed heavily by the charging diesel engines. At the same time, a sea wave surged, and seawater started to flow into the opening vent that automatically closed to prevent flooding. There was no single device on the submarine to detect low oxygen level and the crew suffocated due to the diesel engines consuming all the oxygen present within the submarine. As a consequence, the Commander and the Political Commissar of the People's Liberation Army Navy were dismissed from service, as well as the Commander, Political Commissar and Chief of Staff of the Northern Fleet.

K-159 sinking

edit

In August 2003, the Russian November-class submarine K-159 sank in the Barents Sea. This submarine had been decommissioned, and she was being towed away for scrapping. Of her skeleton crew of ten sailors, nine were killed.

USS Hartford grounding

edit
Main article: USS Hartford grounding

On 25 October 2003, the American Los Angeles-class submarine USS Hartford ran aground in the harbor of La Maddalena, Sardinia, in the Mediterranean Sea. This grounding caused about nine million dollars' worth of damage to Hartford.

2004

edit

HMCS Chicoutimi fire

edit

On 5 October 2004, the Canadian submarine HMCS Chicoutimi suffered from two fires after leaving Faslane harbour for Halifax harbour. One officer, Canadian Forces Lieutenant (Navy) Chris Saunders, died the following day while he was being flown via helicopter to a hospital in Ireland. Canadian Forces investigators concluded that poor insulation of some power cables caused the fires. The following board of inquiry found that the fire was caused by a series of events that caused electrical arcing at cable joints from seawater penetration at the joints.[7]

2005

edit

USS San Francisco collision with undersea terrain

edit

On 8 January 2005, the Los Angeles-class submarine USS San Francisco, while underway and submerged, collided with a seamount about 350 miles (560 km) south of Guam in the Marianas Islands. One of her sailors, Machinist mate 2nd Class (MM2(SS)) Joseph Allen Ashley, of Akron, Ohio, died from the injuries he suffered in the collision. This happened while San Francisco was on a high-speed voyage to visit Brisbane, Australia.

An additional 97 sailors were injured in this accident, including two with dislocated shoulders.[8] The collision with the seamount was so severe that San Francisco nearly sank. Accounts from the scene related a desperate struggle for positive buoyancy after her forward ballast tanks had been ruptured. Several news web sites stated that the boat had hit an "uncharted seamount" at a high speed. Commander Kevin Mooney was relieved of command of the San Francisco after an investigation revealed that he had been using inadequate methods of ocean voyage planning.

San Francisco underwent a rapid deceleration from more than 25 knots (46 km/h) to a standstill, causing a section of her bow to collapse (including her sonar system along with the forward ballast tanks) and everything not tied down to fly forward in the boat. San Francisco returned to her base at Guam, where emergency repairs were carried out. Next, she steamed to the Puget Sound Naval Shipyard for more permanent repairs. The bow section of San Francisco was replaced with that of a sister ship, USS Honolulu, which had already been removed from service because of years of wear and tear.[9][10] This replacement of the bow of San Francisco was successful, and the vessel returned to active service in the Pacific Fleet, based at San Diego.

AS-28 emergency

edit
Main article: AS-28

On 5 August 2005, the Russian Priz-class deep-submergence rescue vehicle AS-28, while operating off the coast of the Kamchatka Peninsula, became entangled in a fishing net, or possibly by cables belonging to an underwater antenna assembly, at a depth of 190 metres (620 feet). Unable to free itself, the submarine was stuck with a depleting air supply.

After a multi-national effort, a British Royal Navy team using a Scorpio ROV was able to free the submarine from the entanglement, allowing it to return to the surface. All seven crew members were rescued safely.

USS Philadelphia collision with MV Yasa Aysen

edit

On 5 September 2005, USS Philadelphia was in the Persian Gulf about 30 nautical miles (60 km) northeast of Bahrain when she collided with the Turkish merchant ship MV Yasa Aysen. No injuries were reported on either vessel. The damage to the submarine was described as "superficial." The Turkish ship suffered minor damage to its hull just above her waterline, but the United States Coast Guard inspected the ship and found her to be still seaworthy. The commanding officer of Philadelphia, Commander Steven M. Oxholm, was relieved of his command following this collision.

2006

edit

Daniil Moskovsky fire

edit

On 6 September 2006, the Russian Victor III-class submarine Daniil Moskovsky suffered a fire which resulted in the deaths of two crewmen (a warrant officer and a sailor). At the time of the incident the submarine was anchored off the Rybachiy peninsula, on Russia's north coast near the border with Norway. The fire was extinguished with no damage to the reactor (which had been scrammed as a precaution), and the submarine was towed to a base at Vidyayevo. The incident was reported as being caused by an electrical fire in the vessel's wiring.[11]

USS Minneapolis-Saint Paul incident

edit

Four crew members were washed overboard from USS Minneapolis-Saint Paul by heavy waves on 29 December 2006 in Plymouth Sound, England. This resulted in the deaths of Senior Chief Thomas Higgins (chief of the boat) and Sonar Technician 2nd Class Michael Holtz. After the preliminary investigation, Commander Edwin Ruff received a punitive letter of reprimand, stating that the accident was avoidable, and he was reassigned to a shore-based post in Norfolk, Virginia.

2007

edit

USS Newport News collision with Japanese tanker Mogamigawa

edit

On 8 January 2007, USS Newport News was transiting submerged in the Strait of Hormuz when she hit the Japanese tanker Mogamigawa.[12] She had been operating as part of Carrier Strike Group 8 (CSG-8), organised around the aircraft carrier USS Dwight D. Eisenhower[13] and dispatched to the Indian Ocean to help support operations in Somalia.

HMS Tireless

edit

On 21 March 2007, two crew members of the Royal Navy's Trafalgar-class submarine, HMS Tireless were killed in an explosion caused by air-purification equipment in the forward section of the submarine. The submarine was in service in the Arctic Ocean and had to make an emergency surface through the pack ice. A third crewmember who suffered "non-life-threatening" injuries was airlifted to a military hospital at Elmendorf Air Force Base near Anchorage, Alaska. According to the Royal Navy, the accident did not affect the ship's nuclear reactor, and the ship sustained only superficial damage.[14]

2008

edit

HMS Superb collision

edit

On 26 May 2008, the Royal Navy's Swiftsure-class submarine, HMS Superb hit an underwater rock pinnacle in the northern Red Sea, 80 miles (130 km) south of Suez, causing damage to sonar equipment. The submarine was decommissioned slightly earlier than planned as a result of the damage.[15][16]

Russian K-152 Nerpa gas leak

edit
Main article: 2008 Russian submarine accident

On 8 November 2008, at least 20 men died of asphyxiation from a gas leak on board the Russian nuclear submarine K-152 Nerpa, during trials in the Sea of Japan.[17] The submarine was leased to the Indian Navy in 2011 and was formally commissioned into service as INS Chakra in 2012.

2009

edit
 
USS Hartford in Bahrain a day after the collision

HMS Vanguard and Triomphant collision

edit
Main article: HMS Vanguard and Le Triomphant submarine collision

Two nuclear submarines, the Royal Navy's HMS Vanguard and the French Navy's Triomphant, collided in February 2009. They were operating in the Atlantic Ocean at the time. No injuries or radiation leaks were reported.[18]

USS Hartford and USS New Orleans collision

edit
Main article: USS Hartford and USS New Orleans collision

USS Hartford collided with USS New Orleans on 20 March 2009 in the Strait of Hormuz.[19]

2010s

edit

2010

edit

HMS Astute grounding

edit
 
Astute aground with the emergency tow vessel Anglian Prince

On 22 October 2010, HMS Astute ran aground on a sand bank off the coast of the Isle of Skye in Scotland.[20] Commanding officer Andy Coles was relieved of his post after an inquiry concluded a series of errors led to the incident. At least two other unnamed officers received disciplinary action.[21]

2011

edit

HMCS Corner Brook grounding

edit

HMCS Corner Brook ran aground in Nootka Sound off the coast of Vancouver Island on 4 June 2011, while conducting SOCT (Submarine Officer Training Course).[22] Minor injuries were sustained by two crew members and the submarine returned to CFB Esquimalt after the incident without escort or further incident.[22] A board of inquiry into the incident deemed commanding officer, Lieutenant-Commander Paul Sutherland, had responsibility for safe navigation of the submarine and was relieved of his command.

2012

edit

USS Miami arson

edit

On 23 May 2012, during a scheduled maintenance overhaul, USS Miami suffered extensive damage from a fire, which was later determined to have been part of a series of fires started deliberately by a civilian shipyard worker, Casey Fury, who was seeking time off from work. The Navy determined it would be uneconomical to repair the submarine and decided to decommission and scrap her instead.[23] Fury was sentenced to 17 years in jail.[24]

USS Montpelier collision with USS San Jacinto

edit

USS Montpelier and the Aegis cruiser USS San Jacinto collided off the coast of north-eastern Florida on 13 October 2012 during an exercise while the submarine was submerged at periscope depth. There were no injuries aboard either ship. The initial assessment of damage was that there was a complete depressurisation of the sonar dome aboard San Jacinto. The investigation revealed that the principal cause of the collision was human error, poor teamwork by Montpelier watch team, and the commanding officer's failure to follow established procedures for submarines operating at periscope depth. Additionally, the investigation revealed contributing factors threaded among the various command and control headquarters that provide training and operational oversight within Fleet Forces Command.[25]

2013

edit

INS Sindhurakshak explosion and sinking

edit

On 14 August 2013, the Indian Navy's INS Sindhurakshak Kilo-class Type 877EKM submarine sank after explosions caused by a fire took place 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. Due to damage from the explosions, the submarine sank at its berth with only a portion visible above the water surface.[26][27][28] Sailors on board reportedly jumped off to safety. The vessel was salvaged later and 18 dead bodies were recovered.[29]

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 Sindhuratna, also sustained minor damage when the fire on Sindhurakshak caused its torpedoes to explode.[27][30] An enquiry into the incident found the cause of the incident to be violation of Standard Operating Procedures during torpedo loading.[29] This resulted in the explosion of two torpedoes during the incident while the remaining 14 torpedoes disintegrated.[29]

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.[31][32][33] After a period of use for the training of marine commandos, the submarine was sunk in 3000 metres of water in the Arabian Sea during June 2017.[34][35]

Russian K-150 Tomsk fire

edit

On 16 September 2013, fifteen seamen were hospitalised after a fire on the Oscar-class submarine. The fire started during welding activity, as the sub was being repaired at the Zvezda shipyard near Vladivostok on the Sea of Japan. The fire was put out after five hours. A federal Investigative Committee said the fire had "caused damage to the health of 15 servicemen" and they remained in hospital. It gave no details about their condition.[36]

USS Jacksonville collision

edit

On 10 January 2013, USS Jacksonville struck a suspected fishing trawler in the Persian Gulf and bent one of its periscopes.[37] The ship's commanding and executive officers were relieved for cause following the incident.[38]

2015

edit

HMS Talent collision

edit

In early 2015, Trafalgar-class submarine HMS Talent entered Devonport Naval base in Plymouth with significant damage to its sail after striking ice.

2016

edit

Sinking of unknown North Korean submarine

edit

On 11 March 2016, CNN and the U.S. Naval Institute News reported that unnamed US officials believed a North Korean submarine had been lost at sea in the Sea of Japan. According to reports, the U.S. military had been observing the submarine when it "stopped" before the Korean People's Navy was observed searching the area by American satellites, aircraft and ships.[39][40]

HMS Ambush collision

edit

On 20 July 2016, while operating at periscope depth on a training exercise in the Strait of Gibraltar, HMS Ambush collided with a merchant ship, sustaining significant damage to the top of her conning tower. The merchant vessel did not sustain any damage. It was reported that no crew members were injured during the collision and that the submarine's nuclear reactor section remained completely undamaged.[41]

2017

edit

UC3 Nautilus sinking

edit

On 11 August 2017, the privately owned midget submarine UC3 Nautilus sank off the coast of Denmark. Danish authorities believe its owner Peter Madsen allegedly scuttled the submarine to hide evidence in the murder of journalist Kim Wall.[42][43][44] In October 2017, Madsen admitted to dismembering Wall during their submarine trip[45] and was later convicted of her murder.

ARA San Juan

edit

On the night of 16 November 2017, the Argentine Navy submarine ARA San Juan and her crew of 44 was reported missing in the San Jorge Gulf region.[46] Ships and long-range patrol aircraft from several nations, including Argentina, Brazil, Chile, Uruguay, Russia, the United Kingdom and the United States, were dispatched in a search and rescue mission. Rescue submersibles and parachute rescuers were deployed.[47][48] On 30 November, hopes of rescuing the crew alive were abandoned.[49]

On 16 November 2018, the company Ocean Infinity had located San Juan through a remote submersible. The wreck was 460 kilometres (290 miles) southeast of Comodoro Rivadavia at a depth of 907 metres (2,976 feet). The submarine's imploded wreckage was strewn up to 70 metres (230 feet) from the hull. All 44 crew members were lost with the submarine.

Alleged INS Arihant flood

edit

In January 2018, the Indian Navy nuclear submarine INS Arihant was alleged to have flooded alongside some time in 2017. Due to an aft hatch being left open by mistake, causing damage to its propulsion compartment. With claims of the submarine being out of action for 10 months while repairs to pipework was carried out. Some sources disputed this claim, alleging that the submarine did not have any aft hatches, as well as claims about the submarines doubled hulled design making this impossible. The Indian Ministry for Defence refused to deny the allegations, citing it would be a breach of national security to discuss the matter.[50][51][52][53][54][55]

2019

edit

Losharik fire

edit

On 1 July 2019, a fire on what it described as a Russian deep-water research submarine surveying the seabed near the Arctic killed 14 sailors. Russian officials faced accusations of trying to cover up the full details of the accident, and some Russian media criticised what they said was a lack of transparency, and drew parallels with the dearth of official information during the meltdown of a Soviet nuclear reactor in Chernobyl in 1986. One day later, the Russian government officially disclosed the incident on the submarine Losharik and acknowledged that the vessel had a nuclear reactor on board.[56]

2020s

edit

2020

edit

Hoegh London collision with South Korean Navy submarine

edit

On 15 July 2020, 05:00 UTC, Norwegian merchant ship Hoegh London (IMO 9342205) and South Korean Navy's Jang Bogo-class submarine collided near Gadeokdo island, Busan, South Korea.[57][58]

2021

edit

KRI Nanggala (402) sinking

edit
Main article: KRI Nanggala (402)

On 21 April 2021, Indonesian Navy spokesperson First Admiral Julius Widjojono announced that KRI Nanggala had failed to report for a post-maneuver brief following a torpedo live fire exercise in the Bali Sea off the coast of Surabaya, about 95 km (51 nautical miles) north of Bali, in an area where the water is 700 metres (2,300 ft) deep.[59][60] The submarine was declared sunk on 24 April, 18:00 (GMT+7) by Commander of the Indonesian National Armed Forces Hadi Tjahjanto at a depth of 700–800 metres below sea level.[61]

At a press conference held on 25 April, the 53 crew were confirmed lost after the submarine was found at a depth of 839 metres (2,753 feet) below sea level by Indonesian navy ship KRI Rigel, broken up into three parts.[62] The Singapore Navy RSSV ship MV Swift Rescue's ROV took the submarine's first image.[63][64]

USS Connecticut (SSN-22) collision with seamount

edit

On 2 October 2021, USS Connecticut (SSN-22) was severely damaged[65] by an collision with a seamount in the South China Sea.[66] About eleven sailors sustained injuries, though none were reported to be life-threatening. The submarine's propulsion system was said to be operating normally.[67] After an investigation the commanding officer, executive officer, and chief of the boat were relieved of duty.[68]

2023

edit

Titan implosion

edit
Main article: Titan submersible implosion

On 18 June 2023, Titan, a private submersible operated by OceanGate, went missing in international waters in the North Atlantic Ocean off the coast of Newfoundland, Canada. The submersible was on a tourist expedition to view the wreck of the Titanic with five people on board. Communication was lost with the submersible 1 hour and 45 minutes into its dive to the wreck site; authorities were notified when it did not resurface at its scheduled time later that day. On 22 June, following the discovery of a debris field containing parts of the Titan approximately 488 m (1,600 ft) from the bow of the Titanic by a remotely operated underwater vehicle (ROV), it was presumed that the pressure chamber had imploded during or after its descent, killing all onboard instantly.[69]

Russian B-237 "Rostov-na-Donu" missile attack

edit
Main article: Russian submarine B-237

On 13 September 2023, Russian Kilo-class submarine B-237 "Rostov-na-Donu" was hit by a missile during the ongoing Russo-Ukrainian War, while docked at Sevastopol Shipyard in Crimea. The missile is suspected to be either a Storm Shadow or SCALP. These are essentially identical air launched cruises missiles, and are expected to have been launched from a Ukrainian Sukhoi Su-24. Russia claimed that 10 missiles were fired, of which 3 managed to penetrate the dockyards defences, hitting both the Submarine and the landing ship Minsk.

On 20 September, photos emerged that showed two large holes in the pressure hull, expected to be an entry and exit hole. Ukraine and outside sources assessed that the two vessels were damaged beyond repair, while Russia's Defence Ministry claimed that both vessels would be repaired and returned to service. Casualties are unknown, although Ukrainian sources claimed 24 personnel were injured on the submarine and 62 killed aboard Minsk.[70][71][72][73]

2024

edit

Chinese Zhou-class nuclear submarine

edit

The first of a new series of nuclear submarines of the People's Liberation Army Navy (PLAN), called the Zhou-class, is believed to have sunk alongside a pier in Wuhan between March and June 2024. On 26 September 2024, US officials claimed that it had sunk. There has been no confirmation of the sinking from the PLAN or Chinese officials. The Chinese Embassy in Washington DC denied knowledge of the incident.[74][75] However, Wuhan is not a current known nuclear-powered submarine construction base, as it has previously only been used for diesel-electric/conventionally powered submarines.[76] This has cast doubts on the validity of the claim that it was a new, nuclear-powered 'Zhou' class submarine being built there.

Russian B-237 "Rostov-na-Donu" alleged sinking

edit
Main article: Russian submarine B-237

On 3 August 2024, Ukrainian officials claimed to have sunk the Russian Kilo-class submarine B-237 "Rostov-na-Donu" a day earlier. The submarine had been undergoing repairs at Sevastopol Shipyard in Crimea after being hit by a suspected Storm Shadow or SCALP missile in September 2023. There was no confirmation of the sinking from Russia, although an alleged decoy was seen on satellite imagery, with what is believed to be the genuine submarine sunk and partially under a tarp nearby. The British Ministry of Defence claimed that it was "highly likely" the submarine had been sunk.[77][78]

References

edit
  1. ^ "This Earthquake Hasn't Even Happened Yet, But It Has a Name". Archived from the original on 18 October 2006. Retrieved 20 November 2017.
  2. ^ "Archived copy" (PDF). www.eas.slu.edu. Archived from the original (PDF) on 25 April 2005. Retrieved 13 January 2022.{{cite web}}: CS1 maint: archived copy as title (link)
  3. ^ Marine Accident Brief MAB-05-01 (PDF). National Transportation Safety Board (Report). National Transportation Safety Board. 29 September 2005. pp. 27–28. Retrieved 23 November 2017.
  4. ^ Royal Navy is condemned over crash of nuclear submarine, P&J, 23 May 2008
  5. ^ a b c Australian Associated Press (23 July 2005). "Navy forced to reduce subs' diving depth". The Age. Retrieved 19 April 2009.
  6. ^ Becker, Jeffrey; Liebenberg, David; Mackenzie, Peter (December 2013). "Behind the Periscope: Leadership in China's Navy". Defense Technical Information Center. p. 81. Archived from the original on 20 November 2015.
  7. ^ "Board of Inquiry - HMCS Chicoutimi fires - Part II - Findings". Archived from the original on 18 May 2006. Retrieved 4 March 2006.
  8. ^ http://www.navy.mil/submit/display.asp?story_id=18257 Archived 11 December 2019 at the Wayback Machine, NNS050509-14 – USS San Francisco Investigation Completed
  9. ^ US Navy. USS Honolulu Holds Final Change of Command Ceremony Archived 13 September 2007 at the Wayback Machine. 14 December 2006.
  10. ^ Nose of USS Honolulu to go to USS San Francisco The Honolulu Advertiser
  11. ^ "Two killed in Russian sub blaze". BBC News. 7 September 2006. Retrieved 9 November 2008.
  12. ^ U.S. sub collides with Japan ship, CNN, 8 January 2007
  13. ^ Affairs, This story was written by Mass Communication Specialist 1st Class Carla Morton, USS Dwight D. Eisenhower Public. "Eisenhower Strike Group Completes JTFEX 06-2". Archived from the original on 25 February 2021. Retrieved 20 November 2017.{{cite web}}: CS1 maint: multiple names: authors list (link) CS1 maint: numeric names: authors list (link)
  14. ^ "Oxygen device sparked sub blast". BBC News. 22 March 2007. Retrieved 22 March 2007.
  15. ^ "UK submarine hits Red Sea rocks". BBC News. 27 May 2008. Retrieved 24 September 2017.
  16. ^ "Superb submarine's final service". BBC News. 26 September 2008. Retrieved 24 September 2017.
  17. ^ At least 20 die in accident on Russian nuclear sub Reuters.
  18. ^ "Nuclear subs collide in Atlantic". BBC News. BBC. 16 February 2009. Retrieved 16 February 2009.
  19. ^ "Ships collide in St of Hormuz". 5th fleet public affairs. 20 March 2009. Archived from the original on 23 March 2009. Retrieved 20 March 2009.
  20. ^ Couzens, Jo; Williams, Richard (23 October 2010). "Grounded Nuclear Submarine Is Towed Free". Sky News. Archived from the original on 10 January 2016. Retrieved 31 July 2015.
  21. ^ Hopkins, Nick (24 April 2012). "Navy submarine ran aground after series of errors, inquiry finds". The Guardian. ISSN 0261-3077. Retrieved 20 June 2023.
  22. ^ a b "Canadian submarine runs aground near Vancouver Island". AHN. 6 June 2011. Archived from the original on 13 June 2011.
  23. ^ "Fire-stricken submarine USS Miami is decommissioned". Retrieved 20 November 2017.
  24. ^ "Shipyard worker who set fire to nuclear submarine sentenced to 17 years in jail". The Guardian. 16 March 2013. ISSN 0261-3077. Retrieved 20 June 2023.
  25. ^ [1] ABC News, 13 October 2012
  26. ^ "Explosion Partly Sinks Indian Naval Submarine". The New York Times. 14 August 2013. Retrieved 14 August 2013.
  27. ^ a b "INS Sindhurakshak fire set off torpedoes causing minor damage to INS Sindhuratna; fate of 18 sailors on board uncertain". DNA India. 14 August 2013. Retrieved 14 August 2013.
  28. ^ "Fears for 18 as Indian navy submarine explodes and sinks in Mumbai". The Guardian. 14 August 2013. Retrieved 14 August 2013.
  29. ^ a b c "Blast in Submarine Sindhurakshak was Due to Lapses in Procedure: Says Navy". 25 September 2014. Retrieved 29 September 2015.
  30. ^ "INS Sindhurakshak: A Sindhughosh-class submarine with latest weapons". IBN Live. 14 August 2013. Archived from the original on 17 August 2013. Retrieved 14 August 2013.
  31. ^ Mumbai (4 December 2015). "Submarine Sindhurakshak to be disposed of soon: Vice Admiral". The Indian Express. Retrieved 9 March 2016.
  32. ^ "Indian Navy hopeful of using submarine that sank". Hindustan Times. 3 December 2013. Archived from the original on 4 December 2013. Retrieved 3 December 2013.
  33. ^ "Possible reuse of Sindhurakshak being explored". The Hindu. 3 December 2013. Retrieved 3 December 2013.
  34. ^ Singh, Rahul (10 July 2017). "Defunct submarine Sindhurakshak finally disposed of". Hindustan Times. New Delhi. Retrieved 11 September 2017.
  35. ^ Rajput, Rashmi (5 September 2017). "Navy sinks 'graveyard' INS Sindhurakshak". The Indian Express. Retrieved 11 September 2017.
  36. ^ "Fire on Russian sub injured 15: investigators". Reuters. Retrieved 17 September 2013.[dead link‍]
  37. ^ "Navy Sub Goes Bump in the Night and Loses Its Periscope". ABC. Retrieved 9 March 2015.
  38. ^ Commander Task Force 54 Public Affairs (10 February 2013). "USS Jacksonville Commanding Officer and Executive Officer Relieved of Duty". Navy News Service. US Navy. Archived from the original on 23 September 2015. Retrieved 10 January 2016.{{cite web}}: CS1 maint: numeric names: authors list (link)
  39. ^ "First on CNN: U.S. says North Korean submarine missing"
  40. ^ "U.S. Official: North Korean Submarine is Missing, Presumed Sunk"
  41. ^ "UK nuclear submarine collides with merchant vessel off Gibraltar". BBC News. 21 July 2016. Retrieved 21 July 2016.
  42. ^ "Inventor may have deliberately sunk submarine in missing journalist case, police say". Australian Broadcasting Corporation. 13 August 2017. Retrieved 20 November 2017.
  43. ^ Oltermann, Philip; agency (22 August 2017). "Woman's body found as Danish police search for missing journalist". The Guardian. Retrieved 20 November 2017 – via www.theguardian.com.
  44. ^ Orange, Richard (25 April 2018). "Peter Madsen sentenced to life for murdering journalist Kim Wall". The Guardian. Retrieved 29 April 2018.
  45. ^ Kennedy, Merrit (30 October 2017). "Police: Danish Inventor Admits To Dismembering Journalist Kim Wall". NPR.org. Retrieved 29 October 2020.
  46. ^ "Desapareció un submarino argentino y se desplegó un operativo de rescate". 17 November 2017. Archived from the original on 3 July 2018. Retrieved 20 November 2017.
  47. ^ "La Armada Argentina perdió contacto con el submarino ARA San Juan". Retrieved 20 November 2017.
  48. ^ Elite Royal Navy rescue team sent as possible calls detected from missing Argentine submarine, The Telegraph, 19 November 2017
  49. ^ "Submarino ARA San Juan: la Armada dio por finalizado el operativo de rescate y ya no busca sobrevivientes". La Nacion (in Spanish). 30 November 2017. Archived from the original on 30 November 2017. Retrieved 30 November 2017.
  50. ^ "India Learned One Way How to Sink a $3 Billion Dollar Submarine: Leave a Hatch Open". The National Interest. 22 August 2019. Retrieved 25 December 2020.
  51. ^ Peri, Dinakar; Joseph, Josy (8 January 2018). "INS Arihant left crippled after 'accident' 10 months ago". The Hindu. Archived from the original on 17 May 2019. Retrieved 29 January 2019.
  52. ^ Pubby, Manu (8 January 2018). "India's only nuclear-armed submarine is back in the water after contamination fears". The Print. Archived from the original on 6 March 2019. Retrieved 5 March 2019.
  53. ^ Suciu, Peter (28 June 2021). "The Dumbest Way Ever to Sink a Submarine? An Open Hatch (It Nearly Happened)". 19FortyFive. Retrieved 30 June 2021.
  54. ^ "Deep diving into the facts about INS Arihant 'accident'". The Economic Times. 12 January 2018.
  55. ^ "Is INS Arihant Damaged? Can't Divulge Information in National Interest, Says Government". News18. 21 March 2018.
  56. ^ Russia accused of cover-up over lethal submarine fire. Reuters. Retrieved 15 July 2019.
  57. ^ Norwegian car carrier collided with Korean submarine Maritime Bulletin. Mikhail Voytenko. July 17, 2020. Retrieved August 23, 2020.
  58. ^ 해군 잠수함-노르웨이 상선 충돌사고...'교신 오류'가 원인 (in Korean) Newsis. August 20, 2020. Retrieved August 23, 2020.
  59. ^ Rahmat, Ridzwan (21 April 2021). "Indonesian Navy submarine missing in Bali Sea". Janes. Retrieved 21 April 2021.
  60. ^ Pattisina, Edna C; Puttranto, Angger (21 April 2021). "Kapal Selam KRI Nanggala-402 Hilang di Utara Bali". kompas.id. Retrieved 21 April 2021.
  61. ^ Aditya, Nicholas (24 April 2021). "Daftar 6 Benda Milik KRI Nanggala-402 yang Ditemukan, Pelurus Tabung Torpedo hingga Alas Shalat". KOMPAS.com. Retrieved 25 April 2021.
  62. ^ Mahadzir, Dzirhan (24 April 2021). "UPDATED: Indonesian Navy Finds Missing Submarine Wreckage, All Aboard Dead". USNI News. Retrieved 20 June 2023.
  63. ^ Siregar, Kiki (25 April 2021). "Missing Indonesian submarine has sunk, objects recovered: Military chief". Channel News Asia. Archived from the original on 25 April 2021. Retrieved 26 April 2021.
  64. ^ "Photos show missing Indonesian navy submarine found broken up on seabed". The Guardian. Reuters. 26 April 2021. Archived from the original on 26 April 2021. Retrieved 26 April 2021.
  65. ^ Burns, Robert (1 November 2021). "Officials: Damaged US Navy Sub Struck Underwater Mountain". Military.com. Archived from the original on 8 August 2022. Retrieved 2 November 2021.
  66. ^ "US Nuclear Sub Damaged in Underwater Collision in South China Sea - October 7, 2021". Daily News Brief. 7 October 2021. Retrieved 7 October 2021.
  67. ^ Sam LaGrone (7 October 2021). "UPDATED: Attack Submarine USS Connecticut Suffers Underwater Collision in South China Sea". USNI News.
  68. ^ Geoff Ziezulewicz (4 November 2021). "USS Connecticut's leadership fired following undersea mountain collision". Navy Times.
  69. ^ "Titan sub implosion: What we know about catastrophic event". BBC News. 19 June 2023. Retrieved 23 June 2023.
  70. ^ "Russian Submarine Hit By Missile, Rostov-On-Don, Gone". Naval news. 20 September 2023. Retrieved 29 March 2024.
  71. ^ "Satellite images show damage to Russian naval vessels struck in Ukraine attack". Reuters. Retrieved 29 March 2024.
  72. ^ "RUSSIAN OFFENSIVE CAMPAIGN ASSESSMENT, SEPTEMBER 25, 2023". Understanding War. Retrieved 29 March 2024.
  73. ^ Amran, Rachel (13 September 2023). "UPDATE: Explosions reported at marine plant in occupied Sevastopol, 24 reported injured". The Kyiv Independent. Archived from the original on 25 December 2023. Retrieved 13 September 2023.
  74. ^ China’s newest nuclear-powered submarine sank earlier this year, US official says, CNN, 26 September 2024.
  75. ^ China’s Newest Nuclear Submarine Sank, Setting Back Its Military Modernization, Wall Street Journal, 26 September 2024.(subscription required)
  76. ^ https://digital-commons.usnwc.edu/cgi/viewcontent.cgi?article=1030&context=cmsi-maritime-reports
  77. ^ "Ukraine's military says it sunk Russian Black Sea Fleet submarine, damaged S-400 missile system in 'successful hit'". The Kyiv Independent. 3 August 2024. Retrieved 3 August 2024.
  78. ^ Reporter, Ryan Chan China News (16 August 2024). "Russia floats lifesize submarine decoy of sunken vessel in Crimea". Newsweek. Retrieved 19 August 2024.
edit
Retrieved from "https://en.wiki.x.io/w/index.php?title=List_of_submarine_and_submersible_incidents_since_2000&oldid=1260050091"