Sinking of the Moskva

Moskva

Company type	Guided missile cruiser
Industry	Naval military vessel
Founded	1983 (1983)
Fate	Sunk on 14 April 2022
Headquarters	Sevastopol , Russia
Area served	Black Sea
Products	Naval warship

Template:Infobox event Template:Campaignbox Russian invasion of Ukraine

The Russian cruiser Moskva, serving as the flagship of the Russian Navy's Black Sea Fleet, was attacked and ultimately sunk by Ukrainian forces on 14 April 2022 amid the ongoing Russo-Ukrainian war (2022–present). Ukrainian authorities declared that their military had successfully struck the vessel with two R-360 Neptune anti-ship missiles, which led to a fire onboard. This was later corroborated by the United States Department of Defense. According to Russian reports, the ship sank during turbulent seas after the fire ignited ammunition stores, causing explosions.

This cruiser represents the largest Russian naval vessel lost in combat since World War II, and marks the first time a Russian flagship has sunk since Knyaz Suvorov was lost in 1905 during the Russo-Japanese War.

Russia stated that 396 crew members were evacuated, with one fatality and 27 personnel unaccounted for, although there are unconfirmed reports suggesting higher casualties. Subsequently, a court in Sevastopol declared at least 17 of those missing as deceased.

Background

In February 2022, the Moskva departed from the Port of Sevastopol to engage in operations related to the Russian invasion of Ukraine. The vessel was subsequently involved in combat against Ukrainian forces during the assault on Snake Island, alongside the Russian patrol boat Vasily Bykov. During this engagement, Moskva communicated with the island’s defenders over radio, demanding their surrender; they famously responded with "Russian warship, go fuck yourself". Contact with the Ukrainian garrison on Snake Island was lost afterward, and eventually, the thirteen Ukrainian soldiers stationed there surrendered. The cruiser remained active in Black Sea operations until it was sunk in April 2022.

Sinking

Template:Maplink

Ukrainian account

The earliest documented indication of a missile strike on the vessel surfaced at 20:42 on 13 April 2022, Ukrainian time (EEST, UTC+03:00), via a Facebook post from a Ukrainian volunteer associated with the military: The message stated: "The cruiser Moskva has just been struck by two Neptune missiles. It remains afloat but is burning amid stormy sea conditions. Tactical flooding appears necessary." Later that night, presidential adviser Oleksiy Arestovych indicated that Moskva was ablaze amid turbulent seas, and Odesa governor Maksym Marchenko officially acknowledged that Ukrainian forces had struck the ship with two R-360 Neptune anti-ship missiles, inflicting "severe damage." At 12:43 on 14 April EEST, the Ukrainian Southern Command shared a video on Facebook reporting that the cruiser sustained damage consistent with hits from Neptune anti-ship missiles and was engulfed in flames. The footage further claimed that other vessels in Moskva’s formation attempted assistance; however, adverse weather and a massive ammunition explosion caused the cruiser to capsize and begin sinking.

Russian account

Shortly after Marchenko's assertion, the Russian Ministry of Defense announced that a fire had triggered the detonation of ammunition, resulting in significant damage to the vessel. The statement did not mention any cause or suggest a Ukrainian attack. On 14 April, the ministry confirmed that the cruiser's missile systems remained intact, the crew had managed to control the blaze, and operations were ongoing to tow the ship back to port. Later that day, Russian officials reported that Moskva sank while being towed amid rough weather conditions. The following day, Russian media briefly covered the sinking, attributing it to "stormy seas".

Additional initial insights

On 14 April, a spokesperson for the United States Department of Defense, John Kirby, indicated that there was insufficient data to definitively verify a missile strike but did not exclude the possibility. Analysis of available imagery revealed the vessel had endured a significant blast, though the exact origin of the explosion remained uncertain. The ship seemed to be moving independently, likely en route to Sevastopol for maintenance. Subsequently, a defense official clarified that it was not confirmed whether the cruiser was self-propelled or being towed. An anonymous senior Defense Department representative noted that the ship was "combating an onboard fire," with damage described as "substantial" and "extensive," though the full extent was unknown.

A satellite image utilizing cloud-penetrating synthetic aperture radar (SAR) captured Moskva at 18:52 local time (UTC+03:00) on 13 April 2022, positioned at 45°10′43.39″N 30°55′30.54″E, roughly 80 nautical miles (150 km) south of Odesa, eastward from Snake Island and approximately 50 nmi (90 km) off the Ukrainian shoreline. Analysts suggested this image was taken shortly after the damage occurred that ultimately led to the ship’s sinking. The cruiser is seen in proximity to other vessels in this photograph.

At 02:59 on 14 April 2022 [EEST], the Telegram channel Reverse Side of the Medal, linked to the Russian paramilitary Wagner Group, posted: "According to unverified reports, the Black Sea Fleet's flagship, the cruiser Moskva, has sunk." They further indicated that preliminary information suggested an attack by Neptune anti-ship missiles launched from the coast between Odesa and Nikolaev. The post stated that the ship's crew had been distracted by efforts to counter a Bayraktar TB-2 UAV when a missile struck the port side, causing a severe list. Due to concerns over ammunition detonation, approximately 500 crew members were evacuated.

Later, at 10:59 on 14 April 2022 [EEST], Lithuanian Defense Minister Arvydas Anušauskas shared on Facebook that an SOS signal was transmitted at 01:05, followed by the cruiser capsizing at 01:14 and power loss about thirty minutes afterward. He reported that beginning at 2 a.m., a Turkish vessel evacuated 54 sailors from the cruiser, and by around 3 a.m., both Turkey and Romania confirmed the ship had fully sunk. However, according to Politiko, an Albanian news outlet, a Turkish official denied to BBC News any involvement in rescuing Russian personnel.

In the afternoon of 14 April, US Defense Department spokesman Kirby affirmed that Moskva had sunk but stated they could not conclusively determine the cause behind it, although Ukraine’s version was "certainly plausible." Regarding potential causes for the explosion, he remarked: "It could have resulted from external damage such as a missile strike, torpedo hit or similar attack... but equally it might have originated internally—perhaps an engineering malfunction or fuel fire. The exact cause remains unknown."

Missile strike

An R-360 Neptune launcher near Kyiv in 2019

On 15 April, a high-ranking US Defense official reported that the Moskva had been struck by two Neptune missiles. The official noted that the cruiser was positioned approximately 65 nmi (120 km) south of Odesa at the time of impact and that it managed to proceed under its own power before eventually sinking on 14 April. Intelligence assessments suggested casualties occurred during the attack, though the exact number remained unknown. The missiles were reportedly launched from a terrestrial platform near Odesa while Moskva was situated about 60–65 nautical miles (110–120 kilometres) offshore.

On 5 May, a US official disclosed that the United States provided "a range of intelligence" to aid in the sinking of Moskva. Nevertheless, the decision to execute the strike was entirely made by Ukraine. Prior to the sinking, a US Navy P-8A Poseidon maritime patrol aircraft was operating in the vicinity. This P-8A, based in Italy, was conducting surveillance within its radar coverage over the Black Sea, and US authorities confirmed identifying the vessel as Moskva as part of intelligence sharing efforts intended to support Ukraine’s defense against Russian naval threats. The US Department of Defense spokesperson John Kirby stated explicitly: "There was no provision of targeting information by any United States Navy P-8 flying in these air policing missions."

The cruiser Moskva possessed a layered air defense system capable of offering a reasonable chance to intercept incoming Neptune missiles, with radar detection providing approximately three to four minutes of advance warning. However, there is no evidence indicating that these defensive measures were activated during the attack. Systems such as the S-300F, 9K33 Osa surface-to-air missiles, chaff or decoy countermeasures, electronic jamming, or even last-resort AK-630 close-in weapon systems appear not to have been employed. Defense analyst Tayfun Ozberk from Defense News suggested that either the ship’s radars failed to detect the incoming Neptune missiles or that its defenses were not prepared to respond effectively, possibly reflecting inadequate crew training for emergency engagements.

The destruction of Moskva may have involved at least one Bayraktar TB2 unmanned combat aerial vehicle (UCAV), which is believed to have monitored the event and potentially contributed in other capacities. According to a Telegram message from the Wagner Group, along with statements from Ukrainian officials, this drone allegedly distracted or diverted the ship’s crew. However, technology journalist David Hambling writing for Forbes considered this explanation unlikely because anti-drone and anti-missile defenses on board were managed by separate systems: long-range SA-N-6 Grumble (S-300F) missiles targeting drones and AK-630 cannons defending against Neptune missiles.

Multiple sources corroborate the presence of Bayraktar drones in proximity to Moskva. Defense industry expert Arda Mevlutoglu reported observing a Bayraktar TB2 ground control station in Odesa on 10 April. On 12 April, Russian military footage showed a missile launch from the frigate Admiral Essen claiming to have destroyed a Bayraktar drone near Crimea’s coast. A Ukrainian video purportedly filmed using a night vision scope depicted Moskva engulfed in flames from a distance, possibly recorded by a Bayraktar drone operating nearby.

Experts suggest that Bayraktar drones might have also played a role in providing targeting data. Can Kasapoglu, director of security and defense studies at Turkey’s Center for Economics and Foreign Policy Studies (EDAM), remarked: "Reports indicating Turkish TB2 drones participated either by distracting Moskva or serving as spotters are both plausible." Mevlutoglu further noted that Rear Admiral Oleksiy Neizhpapa, commander of Ukraine’s naval forces, had previously indicated plans to deploy TB2 drones alongside Neptune missile launchers for reconnaissance purposes. Additionally, Mevlutoglu highlighted that Moskva’s main radar system was outdated and primarily designed for detecting aircraft and cruise missiles; thus, smaller UAVs like TB2s with reduced radar signatures and slower speeds could evade detection.

Aviation journalist Valius Venckunas cited Russian military correspondent Arkady Babchenko—an outspoken Putin critic—who claimed that a Ukrainian Bayraktar disabled Moskva’s radar system, preventing it from detecting and countering incoming missiles. However, Babchenko did not disclose his sources for this information.

Danish defense analyst Anders Puck Nielsen proposed operator fatigue as a critical factor affecting performance: Russian vessels operate with relatively dated systems requiring vigilant and responsive personnel. With active defensive measures engaged, it would be anticipated that Moskva could withstand multiple Neptune missile strikes due to its substantial displacement and armor. One combat simulation model estimates that an attack involving at least eleven Neptune missiles fired simultaneously would be necessary; under this scenario, Moskva could neutralize six missiles while five penetrated defenses causing sufficient hull damage to sink her. This scenario presumes effective damage control preventing catastrophic detonation of onboard munitions; factors such as reliance on conscripted personnel rather than experienced professionals and inadequate compartmentalization within the ship have been cited as contributors to her loss.

Visuals and footage of the sinking vessel

By 18 April 2022, social media platforms were circulating two photographs and a brief 3-second video clip depicting Moskva prior to its sinking following the outbreak of fire. These visuals capture the ship leaning to port side during daylight under calm sea conditions, revealing extensive fire damage concentrated around the central superstructure, visible breaches at the waterline, and a noticeable absence of most life rafts, suggesting partial crew evacuation. According to CNN, "a sizable Russian rescue tug is observed spraying water on the far starboard side of the warship."

• Moskva before and after the incident: a comparative view
• 
  Moskva docked in Sevastopol Bay in 2012
• A large warship listing significantly to port with smoke rising from its bridge, viewed from the rail of another vessel; an arm from someone aboard that vessel is visible in the foreground.
  An image purportedly showing Moskva aflame and heavily listing post-incident. This photograph serves as one of the few tangible verifications of the damage sustained by the ship and is a principal source for open-source internet analyses, including those by H. I. Sutton

The origin or creator of these images and video remains unidentified. The Telegraph reported that these visuals initially appeared online through the Telegram messaging app on a channel reportedly associated with Russian security forces. Independent analysts consulted by The Guardian and CNN verified that the footage likely shows Moskva. Yörük Işık, a journalist and expert in ship identification quoted by The Guardian, stated: "I am convinced the video is authentic. The shape and size correspond precisely. It is indeed the Moskva." Additionally, The Guardian noted that Işık believed at least one photograph was captured from a Project 22870 rescue tug, of which Russia reportedly operates two in the Black Sea.

A senior official from US defense remarked that while independent verification of the images was not possible, "the visuals align with our assessments regarding the damage inflicted upon the vessel." Carl Schuster, formerly director of operations at the US Pacific Command's Joint Intelligence Operations Center, commented: "Provided the photo has not been altered or manipulated, it appears missile strikes hit forward sections, which aligns with typical anti-ship cruise missile behavior targeting the radar signature's center—usually situated at the front part of the superstructure." Former rear admiral Chris Parry wrote to The Guardian: "It appears one or two missiles penetrated just beneath the aft pair of Vulcan anti-ship missiles... This would have caused extensive internal destruction and likely ruptured these missiles, releasing propellant fuel that exacerbated onboard fires by spreading laterally along decks and through compromised bulkheads." Naval specialists interviewed by the BBC agreed that observed damage matches missile strike effects but differed on other possible explanations. Notably, no indications of stormy conditions mentioned in Russian accounts are visible in the footage.

Casualties

On 14 April, Lithuania's defense minister Arvydas Anušauskas reported that a distress call had been issued from the Moskva earlier that day. A Turkish vessel responded by evacuating 54 crew members from the cruiser at approximately 2 am, shortly before the ship sank at 3 am. The total crew numbered 485, including 66 officers, though the number of survivors remained unclear.

On 15 April, Ukrainian sources stated that several crew members of Moskva had died, including the ship’s commanding officer, First Rank Captain Anton Kuprin (aged 43). A senior U.S. official later confirmed on the same day that U.S. intelligence also suggested casualties had occurred. During a U.S. Department of Defense briefing on 18 April, a senior defense representative mentioned sightings of lifeboats carrying sailors but could not provide an exact figure. The independent Russian publication Novaya Gazeta Europe reported approximately 40 fatalities resulting from the sinking. An eyewitness account indicated that around 200 injured sailors were hospitalized in Crimea out of an estimated total crew of roughly 500, with many others still unaccounted for.

Following the sinking, the Russian Ministry of Defense declared that all crew members had been evacuated, initially reporting no casualties. Nonetheless, some relatives were informed that their family members were "missing". On the following day, Russia released footage purportedly showing a gathering in Sevastopol with approximately 100 Moskva sailors present alongside Navy Commander-in-Chief Admiral Nikolay Yevmenov, who affirmed that these sailors would continue their naval service.

According to the independent Russian online outlet The Insider, the video features roughly one hundred sailors including Captain Anton Kuprin. Naval News indicated that this footage suggested around half of the crew—approximately 240 individuals—survived. However, the Ukrainian branch of Radio Liberty noted that verifying this video’s authenticity was not possible.

On 22 April, an official statement from the Russian Defense Ministry confirmed one fatality among Moskva’s crew and reported that twenty-seven sailors were missing while four hundred ninety-six were rescued. Families of those who served aboard have claimed that the number missing might be greater and expressed frustration over a lack of official updates concerning their relatives’ status. Subsequently, a court in Sevastopol officially declared at least seventeen missing sailors deceased.

Contrastingly, on the same date—22 April—Oleksiy Danilov, secretary of Ukraine’s National Security and Defense Council, asserted that only fifty-eight out of an estimated five hundred ten crew members had been rescued. The last comparable loss was when German air raids sank the Soviet battleship Marat during that conflict, marking also the first time a Russian flagship was lost in combat since the battleship Knyaz Suvorov sank at the Battle of Tsushima during the Russo-Japanese War in 1905. The last sinking of a warship of similar scale occurred during the 1982 Falklands War, when the Argentine Navy cruiser ARA General Belgrano was destroyed by the British submarine HMS Conqueror. Should Ukrainian assertions be accurate, Moskva might hold the record as the largest warship ever disabled or destroyed by missile strike, according to Carl Schuster, a retired US Navy captain and former operations director at the US Indo-Pacific Command’s Joint Intelligence Center.

The sinking of Moskva is viewed as a major and embarrassing setback for Russian President Vladimir Putin; however, Mykola Bielieskov from Ukraine’s National Institute for Strategic Studies emphasized its impact as more psychological than material. He noted that while it would not fully end Russia’s naval blockade of Ukraine, it demonstrated Ukraine’s capability to effectively utilize advanced weapon systems. Similarly, the Institute for the Study of War concluded that this loss could compel Russia to either bolster its Black Sea fleet with additional air and point-defense assets or retreat vessels from positions close to Ukraine’s coastline. Following this event, Russia repositioned five other warships further away from Ukraine’s shores.

As the sole vessel in Russia’s Black Sea Fleet equipped with the S-300F long-range air defense missiles, Moskva did not launch missiles against Ukrainian land targets but provided critical anti-air coverage to other ships engaged in such strikes; its destruction forced Russian naval units to operate farther offshore due to diminished protection. Retired US Rear Admiral Samuel J. Cox, head of the Naval History and Heritage Command, remarked to The New York Times that without Moskva, any amphibious operations against Ukraine would become significantly riskier for Russia, exposing landing and amphibious vessels to greater vulnerability.

In June 2022, images surfaced showing Russian Project 22160 patrol ships of the Vasily Bykov class outfitted with ground-based Tor-M1/M2 surface-to-air missile systems mounted on deck; analysts interpreted this modification as an attempt to compensate for lost seaborne air defense capabilities after Moskva's sinking. Additionally, several Russian offshore gas platforms situated roughly midway between Crimea and occupied Snake Island experienced attacks attributed to reduced area defense. By August, Russia’s naval dominance over the Black Sea had weakened significantly as Odesa was no longer under threat from maritime approaches; however, Russia retained sufficient naval capacity to secure its export routes across the sea.

While two sister ships of Moskva were stationed in the Eastern Mediterranean as of February 2022, Turkey invoked provisions of the Montreux Convention by closing the Turkish Straits to belligerent warships without Black Sea home ports for the duration of hostilities; this prevents Russia from redeploying vessels from other fleets to replace Moskva without breaching Turkish sovereignty.

In early 2020, a fragment believed to be from the True Cross, a rare Christian relic revered as part of the cross upon which Jesus was crucified, was placed within Moskvas chapel by the archpriest of Sevastopol District of the Russian Orthodox Church. Following Moskvas sinking, speculation arose that this sacred relic may have been lost with her.

Aftermath

Ukrainian postage stamp illustrating a Ukrainian serviceman making an obscene gesture towards the Russian cruiser Moskva, issued two days prior to its sinking

Russian salvage vessel Kommuna

United States National Security Advisor Jake Sullivan described the loss of Moskva as a significant setback for Russia, noting Moscow’s conflicting explanations between claims of mishandling and allegations of an attack. Sasaki Takahiro, a guest professor specializing in Russian security policy at Hiroshima University, compared the sinking of Moskva to the historic loss of Imperial Japan’s battleship Yamato, emphasizing its strategic impact. According to John Kirby, spokesperson for the US Department of Defense, Moskva primarily provided air defense for Russian forces in the Black Sea, and her destruction will notably diminish this capability in the short term.

An assessment from Forbes Ukraine estimated the replacement cost of Moskva at approximately US$750 million, marking it as the most expensive single military asset lost by Russia during the conflict up to that point. Although Russia did not officially acknowledge Ukrainian missile strikes as the cause, Reuters reported that on the morning of 15 April, Russia conducted a retaliatory missile attack on the Luch Design Bureau missile factory in Kyiv, where Neptune missiles—suspected to have been used against Moskva—were developed and produced.

The cruiser’s sinking occurred shortly after Ukrposhta issued one million copies of the "Russian warship, go fuck yourself" postage stamps featuring a soldier giving an offensive gesture toward Moskva. This event significantly increased demand for the stamp within Ukraine; with some buyers waiting over two hours to obtain it. The loss is widely believed to have boosted Ukrainian morale while negatively affecting Russian spirits. Following this event, Oleksiy Neizhpapa, commander of Ukraine’s naval forces, received a promotion.

Russian state media gave limited coverage to the incident; reports mentioned outdated fire suppression systems and downplayed any operational consequences. However, film director and former State Duma deputy Vladimir Bortko, appearing on a talk show, called for total war retaliation, declaring the fate of Moskva as justification for an all-out conflict. On 18 April, Russia-1 host Vladimir Solovyov publicly criticized the Russian navy regarding the sinking. Kremlin loyalist commentator Sergei Markov told BBC Radio 4's The World at One that missiles originating from Norway had struck the cruiser and that US forces had compromised its electronic defenses. The Russian tabloid Komsomolskaya Pravda speculated that a Norwegian AGM-119 Penguin missile was responsible for damaging the ship.

A Ukraine-based publication, along with two defense experts, suggested that Moskva was capable of carrying nuclear warheads and may have had two onboard when it sank. They urged neighboring countries to investigate potential nuclear hazards. While there is a remote possibility that nuclear warheads were present for its P-500/P-1000 anti-ship missiles, no evidence supports this claim. A senior U.S. defense official confirmed that no nuclear weapons were aboard at the time of sinking.

Ukraine designated the wreck site of Moskva as "underwater cultural heritage." Located approximately 130 km off Odesa’s coast in waters about 45–50 metres deep, it has been promoted as a diving attraction accessible without extensive diving experience.

Reports indicated that the Russian navy dispatched the salvage vessel Kommuna—commissioned in 1915 and recognized as the world’s oldest active naval ship—accompanied by the AS-28 submersible to investigate the wreck. This deployment was part of an eight-ship convoy. Given Moskva’’’s large size and intact sinking, raising her is considered unfeasible; recovery efforts likely focus on retrieving encryption devices, armaments, remains, and other sensitive materials potentially valuable to foreign intelligence. Based with Russia’s Black Sea Fleet in Sevastopol, Kommuna’’’s presence near the wreck exposes it to potential Ukrainian attacks. On 24 May, Ukrainian sources reported that over two weeks Russian forces had been extracting bodies and classified equipment from the sunken cruiser with involvement from five to seven vessels.

On 30 June, Russian troops withdrew from Snake Island, which had previously been targeted by Moskva alongside Vasily Bykov. Subsequently, on 4 July, Ukrainian forces landed on Snake Island and raised their national flag.

On 4 November, a court in Sevastopol officially declared 17 sailors missing from Moskva as deceased.

See also

• Black Sea Fleet
• Spasatel Vasily Bekh – Tugboat of the Russian Navy destroyed by Ukrainian forces during the 2022 conflict
• List of ship losses during the Russo-Ukrainian War
• Battle of the Denmark Strait (destruction of the British battlecruiser HMS Hood)
• Operation Ten-Go (sinking of the Japanese battleship Yamato)
• Last battle of Bismarck (loss of the German battleship Bismarck)