ChrisO_wiki Profile picture
May 3, 2025 24 tweets 6 min read Read on X
1/ THE SINKING OF MOSKVA, PART 3: After being struck by Ukrainian missiles on 13 April, the Russian missile cruiser Moskva was abandoned and left to drift burning overnight. This thread tells the story of the ship's final hours, and what happened next. ⬇️ Image
2/ These threads are based on a newly published dossier compiled by Dmitry Shkrebets, the father of a conscript sailor who died in the attack on Moskva. 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/ On the morning of 14 April, the tugboat Shakhter arrived on the scene with Admiral Essen, Admiral Makarov and Epron already there. A helicopter survey of Moskva reported that the cruiser was still on fire, with explosions continuing within the ship's interior. Image
5/ A photograph of the sinking Moskva and the short video below were recorded on 14 April, with Shakhter visible in the background of the video. They both show how severely damaged Moskva was by this point.
6/ Flames are still visible coming out of the portholes in compartments 7 to 10. Soot stains above portholes near the stern show the extent of uncontrolled smoke, while a crack is visible near an aft torpedo tube. The deck above the S-300F missile room has sagged downwards. Image
7/ The missile room is one of the largest spaces in a Slava-class cruiser like Moskva and stretches across the ship's full width. It's occupied by several revolver-style S-300F missile tubes. It's marked in the diagram here as 'cellar no. 6', located above compartments 11 and 12. Image
Image
8/ The deck above the missile room had buckled across the entire width of the ship – a distance of 20.8 meters. This point was between the site of the two missile impacts, with the damage likely caused by the ship flexing after the explosions.
9/ A 2.5 meter crack is visible on the starboard side, extending from the main deck to below the waterline and running straight through a porthole. It would have allowed water to enter the ship – though probably not in sufficient quantities to cause the sinking by itself.
10/ The missile holes were underwater by this time. Further water ingress is likely to have come from open portholes. The crew members trapped in the central compartments after the attack had to open the portholes to escape, but could not have closed them afterwards.
11/ The ship is also visibly settling by the stern. Skhrebets writes that this was because the missile room was progressively flooding. He comments that water likely entered either from the engine room or from the missile hole at the junction of compartments 13 and 14.
12/ Despite the damage, it was decided that an attempt would be made to tow Moskva to Sevastopol, 210 km away. A tow line was attached but was abandoned late on 14 April after it was found that the tow could proceed no faster than 2 knots – a 57-hour voyage to Sevastopol.
13/ At 20:00, Shkrebets reports, "the cruiser Moskva lost stability... capsized on its left side and sank with a trim by the stern." There was no final explosion, as some erroneously suggested at the time. She may have been destabilised by the flooding of the S-300F missile room.
14/ Although many speculated at the time that the direct cause of the sinking was the explosion of ammunition aboard, according to Shkrebets the only ammunition that definitely exploded was the stockpile of 30 mm shells in a storage room on the upper deck.
15/ It's likely that the sinking was caused by water entering through holes caused by the missile impacts and fire-caused hull deformation. Shkrebets writes that using the bilge pumps to remove excess water failed, and the only large pump aboard broke down after 10 minutes.
16/ Shkrebets speculates that Moskva was deliberately sunk to spare the Russian Navy the embarassment of bringing it to shore in a burned-out condition. This seems unlikely, as having the ship sunk was undoubtedly far more embarassing.
17/ It also contradicts Shkrebets' own statement that "in Sevastopol they actually prepared the Northern Dock for it (located in Dock Bay, on the Northern Side)." If this was done, it was hardly consistent with an intention to deliberately sink the ship.
18/ Two days after the sinking, many of the surviving crew of Moskva were paraded in Sevastopol (excepting the badly wounded, of whom there appear to have been many). This caused a lot of discontent among the sailors, according to Shkrebets:
19/ "When the remaining crew of the cruiser Moskva was placed in the Kazachka (1472nd Naval Clinical Hospital in Sevastopol) they were forced to prepare dress uniforms for the arrival of the commander-in-chief.

The sailors began to express their dissatisfaction with this show.
20/ "They were pulled out of fire and water, many with burnt and frostbitten limbs — [and] were a hair's breadth from death (in the worst case scenario).

And they decided to arrange a military parade for them."
21/ The Russian Ministry of Defence subsequently attempted to carry out a years-long cover-up of who and how many had died in the sinking. Families of missing crew members who posted messages of mourning on social media were told to take them down.
22/ Even now, it's not clear how many died. Officially, one man died and and 27 were listed as missing, while 396 were rescued. 17 of the 27 were later declared dead by a court. A memorial listing 20 fatalities was unveilled in Sevastopol in April 2024.
23/ TO BE CONTINUED: lessons and reflections from the sinking of Moskva.

• • •

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!

:(