ChrisO_wiki Profile picture
May 4, 2025 36 tweets 8 min read Read on X
1/ THE SINKING OF MOSKVA, PART 4: The Russian Black Sea flagship Moskva sank on 14 April 2022 after being hit by two Ukrainian missiles the day before, inflicting the Russian Navy's biggest loss in 80 years. This thread looks at possible lessons learned from the sinking. ⬇️ Image
2/ For part 1, describing events leading up to the missile strikes, see the thread below.
3/ Part 2 describes how the crew tried to save the ship after two Ukrainian Neptune missiles struck it at 14:20 on 13 April:
4/ Part 3 covers the ship's final hours on 14 April, and the immediate aftermath:
5/ Dmitry Shkrebets, the author of the account on which these threads are based, is understandably very angry with the long list of failings that led to the loss of Moskva and 28 of her crew. The casualties included his son Yegor, who was only a week from his 20th birthday. Image
6/ Among the failures that Shkrebets lists are:

🔺 Moskva sailed unescorted into Ukrainian missile range with faulty radars and weapons systems and without combat preparations;
🔺 The conscripts aboard her were sent illegally to a war zone outside of Russian territory;
7/ 🔺 The Russian Navy appears to have ignored the threat of Ukrainian cruise missile attacks in its mission planning;
🔺 Poorly maintained structures within the ship, such as ladders and gangways, disintegrated and blocked escape;
8/ 🔺 Fire suppression systems and pumps did not work properly;
🔺 Toxic smoke spread uncontrolled throughout the ship;
🔺 Gas masks did not work because they were decades old and components were long since life-expired;
9/ 🔺 Breathing apparatuses were unusable because they had been packaged without masks;
🔺 There was insufficient fire-fighting equipment on board.

(There were likely many other flaws, particularly compared to best practice in NATO navies.)
10/ As Shkrebets points out, these were the result of complacency, mismanagement and decades of lack of maintenance on the ship. If those problems could be so severe on Moskva, the flagship of the Black Sea Fleet, he asks, how much worse is it elsewhere? Image
11/ The Ukrainians were admittedly extremely lucky. The first missile to hit caused critical damage and knocked out the ship's damage control facilities. It appears to have set fire to the ship's fuel supply almost immediately, filling Moskva with choking smoke.
12/ Skhrebets' account indicates that the second strike on the stern caused far less damage and the fire there was quickly extinguished. Had this been the only strike on Moskva, the ship was unlikely to have been lost.
13/ The Russians were somewhat lucky too, despite the loss of the ship. The 30 mm shells that exploded in the fire were probably the least destructive type of ammunition on Moskva. Each of the 16 huge Vulkan missiles contained 1.5 tons of kerosene and 490 kg of high explosive. Image
14/ As Shkrebets points out, "It was believed that just three P-1000 Vulkan missiles would be capable of sinking an aircraft carrier... [In the event of] detonation of the first four P-1000 Vulkan missiles [aboard Moskva], the front end of the ship would be torn off."
15/ Had either of the missiles struck a few meters away from their impact sites, they could have detonated multiple heavy weapons systems – P-1000s, S-300Fs (shown here in their launcher room, near the site of the second missile impact), or heavy torpedoes. Image
16/ According to Shkrebets, most of the crew would have died in the mess hall in the first missile impact if a scheduled meeting there had not been delayed by the mess hall staff failing to finish their lunch washing up on time.
17/ Assessing the reliability of Shkrebets' account is made more difficult by the lack of other sources. The Russian authorities very firmly suppressed any relatives or survivors who tried to give their version of events.
18/ However, his extremely detailed dossier indicates that he obtained a good deal of information directly from Moskva sailors and eyewitnesses, including some original documentation. He has been extraordinarily brave in defying the authorities to expose failures.
19/ His description of what happened on board is partly corroborated by the single photo and brief video that emerged from the sinking. The damage visible to Moskva matches what he says about the fire and other physical damage caused by the attack. Image
20/ Bearing these caveats in mind, it's worth reviewing was said by the Russians, Ukrainians and others at the time to assess its consistency with Shkrebets' version of events.
21/ The first Ukrainian account, which appeared on Facebook at 20:42, was mostly accurate: "The cruiser Moskva has just been hit by 2 Neptune missiles. It is standing [not sunk], burning. And there is a storm at sea. Tactical flooding is required, apparently."
22/ This was likely sourced from intercepted Russian radio signals, perhaps the call below, which was published by the Ukrainian military's Operational Command South on 15 May 2022.
23/ The Russian MOD said early on 14 April that a fire had caused ammunition to explode and that the ship had been seriously damaged. This was also mostly accurate, likely referring to the detonation of 30 mm ammunition, though they didn't say anything about then the cause.
24/ Later Russian statements said that the missile systems of the cruiser were undamaged, the fire was contained by sailors, and that efforts were underway to tow the ship to port. This was only partly true (in fact, the fire was never fully contained, according to Shkrebets.)
25/ The ship's sinking was said by the Russian MOD to have happened in "stormy seas", which Shkrebets says was untrue. At the time of the missile impacts and sinking, he says that wind speeds were between 4 and 10 knots, which would have only created small wavelets.
26/ There were also claims from foreign sources that survivors had been evacuated by Turkish or Romanian ships in the vicinity. These were clearly untrue; nothing has emerged to verify this, and Shkrebets is clear that only Russian ships were involved.
27/ Casualty reports from foreign sources were clearly heavily exaggerated. Shkrebets does not contradict the official Russian figures, which were far lower than those given by others. Initial claims of hundreds of fatalities were never corroborated.
28/ An eyewitness report at the time claimed that around 200 men, or nearly half the crew, were in hospitals in Sevastopol, most likely suffering from smoke inhalation. This is consistent with about only 100-140 men appearing in the 16 April 2022 parade in Sevastopol.
29/ The remaining men missing from the parade were likely among the fatalities. Moskva's captain Anton Kuprin survived the attack, as did all of the senior officers. The most senior officer known to have died was a captain-lieutenant (equivalent to a US Navy lieutenant). Image
30/ The Moskva memorial in Sevastopol records that the publicly disclosed fatalities were aged between 18 and 61 years old. Three-quarters were under 24 years of age, which suggests that conscripts were disproportionately represented among the dead. Image
31/ The following lists all of the names recorded on the Moskva memorial. Two are recorded as having died in June 2022, presumably as a result of lingering injuries:

- Captain-Lieutenant Vyacheslav Mikhailovich Geplock

- Lieutenant Maxim Alexandrovich Naumkin
32/ - Senior Michman [=chief petty officer] Dmitry Alexandrovich Cheremiskin

- Senior Michman Ivan Leonidovich Vakhrushev

- Fuel Foreman Takhir Zamirovich Afashagov
33/ Privates

- Vladislav Alexandrovich Dorokhin [died 21/06/2022]
- Akim Aleksandrovich Kozyr
- Sergei Sergeevich Pozdnyakov
- Artem Sergeevich Pustovet
- Leonid Viktorovich Savin
- Yegor Dmitrievich Shkrebets
- Georgy Khayyamovich Shakuro
34/ Senior sailors

- Vitaly Vladimirovich Begersky
- Anton Konstantinovich Fedotov [died 25/06/2022]
- Danil Mikhailovich Gerok
- Daniil Eduardovich Kitaev
- Vladimir Alekseevich Kovalev
35/ Sailors

- Pavel Alekseevich Efimov
- Ivan Vladimirovich Frantin
- Ilya Alekseevich Shcherbina
- Viktor Yurievich Shirinkin
36/ TO BE CONTINUED: The capture of Snake Island and Moskva's Black Sea missions before the sinking.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with ChrisO_wiki

ChrisO_wiki Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @ChrisO_wiki

Jun 23
1/ Russian warbloggers have steadily become bolder in calling for Russia's leadership to be replaced to overcome the current stalemate in Ukraine. Calling the current situation "hopeless", 'Verum Regnum' calls for new leadership in Russia so that it can win the war. ⬇️ Image
2/ While well aware that open criticism of Vladimir Putin is still too dangerous a step, many warbloggers are willing to criticise "the system" in general terms or call out specific officials regarded as failing, such as Chief of General Staff Valery Gerasimov
3/ This kind of approach, which could be summed up as "the Tsar should replace his boyars", is clearly visible in what 'Verum Regnum' writes on Telegram:

"Do you know what a "hopeless situation" is? It's a situation where we don't like the simple, obvious way out."
Read 16 tweets
Jun 23
1/ Russia's air defence teams are manned by "homeless people, alcoholics, deserters, disabled people, idiots", complains a Russian warblogger. In the face of continued failures to stop Ukrainian drone attacks, urgent investment in robotic defence systems is advocated. ⬇️ Image
2/ 'Military Chronicle' argues that "recent incidents involving the use of attack drones against targets in Moscow and Voronezh demonstrate that the human factor is becoming the most critical vulnerability in modern air defence systems."
3/ 'Dead Heads' explains that Russia's mobile fire teams are attracting the wrong kind of recruits: "We're forming Mobile Task Forces (MOGs) and assembling them by units: homeless people, alcoholics, 500s, disabled people, idiots – why aren't they shooting down anything?"
Read 20 tweets
Jun 22
1/ The Russian warblogger 'Fighterbomber', a retired Russian air force pilot, is taking heavy flak from other warbloggers for disclosing a fuel delivery to Crimea that the Ukrainians promptly blew up. "Go fuck yourself. Preferably holding hands," he responds. ⬇️ Image
2/ On 17 June, in an apparent attempt to refute widespread accounts of fuel shortages in Crimea, 'Fighterbomber' wrote on his Telegram channel: "The audience is saying that fuel has arrived in Crimea. Lots of it. There's more coming. 😍"
3/ Three days later, Ukrainian forces struck the Kerch oil terminal's fuel depot, causing a major fire. An official Ukrainian Telegram channel trolled Fighterbomber by crediting the warblogger for the strike (it's unlikely that he had any influence on it).
Read 23 tweets
Jun 22
1/ Dozens of specialist workers were likely killed or wounded in today's Ukrainian strike in Voronezh. Russian warbloggers are dismayed, complain that the Russian government is ignoring it, and call for London to be nuked in retaliation. ⬇️
2/ Heavy missiles (it's not yet clear what type; the Russian warbloggers assume a UK/French Storm Shadow or SCALP/ER) have caused heavy damage and raging fires at the Voronezh Semiconductor Devices Plant, a vital element of Russia's missile production chain.
3/ The regional governor says that five people are known to have died, with dozens more injured. He says that while most were able to take shelter and survived, many ignored the alert and were caught up in the attack.
Read 24 tweets
Jun 22
1/ Russian warbloggers complain that their readers are insufficiently enthusiastic about the disastrous war in Ukraine, following an outpouring of negative sentiment after the drone strikes on Moscow. "Social media has been a living hell since yesterday," one gripes. ⬇️ Image
2/ Warblogger Andrey Antonov urges his readers not to believe what they're reading:

"Be vigilant! Social media has been a living hell since yesterday.

A coordinated campaign against our peace of mind is underway.

I saw the same thing in 2022, during Crocus, Kursk, and so on."
3/ "Your feed is flooded with nonsense, both from new accounts you never followed and from tried-and-true opposition faggots you never followed, but bots are amplifying the popularity of these posts, and they're popping up everywhere.
Read 27 tweets
Jun 22
1/ The occupied Donetsk region is being isolated from Russia through drone-dropped remote mining, according to reports from the area. The forced closure of border checkpoints highlights the region's vulnerability to Ukraine's anti-logistics campaign. ⬇️ Image
2/ Despite occupied regions of Ukraine having been formally annexed, Russia still maintains full border controls with its 'new territories'. This is generally believed to be to meant prevent the smuggling of weapons and drugs, and to stop military deserters returning to Russia.
3/ However, the retention of border controls has also created chokepoints which Ukraine can block. Recent reports have indicated that air-dropped mines are being deployed around the checkpoints from Ukrainian drones, many kilometres from the front line.
Read 11 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(