ChrisO_wiki Profile picture
May 5, 2025 29 tweets 7 min read Read on X
1/ THE SINKING OF MOSKVA, PART 5: In this penultimate thread on the sinking of the Russian missile cruiser Moskva on 13-14 April 2022, we'll look at how Moskva was nearly decommissioned because of her poor condition before being reactivated in time for the invasion of Ukraine. ⬇️ 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 describes the ship's final hours on 14 April, and the immediate aftermath:
5/ Part 4, evaluating lessons and conclusions from the sinking, is here:
6/ Prior to the war in Ukraine, Moskva had faced an uncertain future. She had been designed as a Cold War carrier-killer, armed with 16 huge Vulkan P-1000 anti-ship missiles, but her secondary role was to provide air defence with her S-300F Fort anti-aircraft missiles. Image
Image
7/ In September 2015, Moskva sailed through the Bosphorus Strait to take up station in the eastern Mediterranean, where she provided air defence cover for the Russian Air Force's Khmeimim air base in Syria until January 2016. Image
8/ On returning to Russia, Moskva was due for a refit and upgrade but due to lack of funds her future became uncertain. She remained at anchor in Sevastopol for most of the following four years with a skeleton crew of 64 men on board (rather than the usual 500+).
9/ According to a dossier compiled by Dmitry Skrebets, the father of a conscript sailor who died in the April 2022 sinking, the ship was used as a floating barracks under the command of a Guard Captain (equivalent to between a NATO lieutenant or major).
10/ As Skhrebets puts it, "Conscripts were housed there, they lived in quarters, marched around the parade ground, learned to stand watch, and did cleaning." It looked likely that the ship, which was already 37 years old at that time and in a poor condition, would be scrapped.
11/ However, Shkrebets says, Moskva was reactivated for political reasons. As the Russian Navy's only ship of the first line in the Black Sea, it was the only ship there that could qualify as a flagship. Without a flagship, the Black Sea Fleet would be downgraded to a flotilla.
12/ By then, Moskva's condition had deteriorated severely. "At that time, the decks on the cruiser Moskva had rotted so much in some places that the dough mixing apparatus (250 liters) fell through the deck onto the generator (this fact was passed on from call to call)."
13/ "And some transformers (approximately 700 kg each) were practically hanging on power cables. They were propped up with improvised means so that when the sea was rough they would not be torn off and injure anyone."
14/ On 5 June 2019, Moskva left the port of Sevastopol in the Black Sea to test her combat systems and main propulsion. A year later, on 9 June 2020, Captain 1st Rank Anton Valerievich Kuprin was appointed as the ship's captain to oversea the ship's restoration. Image
15/ Money had been found to fix the essentials, like the screws, shaft lines, gears and generator, but not to fully repair or upgrade the weapons systems or radars. These remained in a fragile state even as late as February 2022.
16/ Shkrebets writes: "For example: the OSA air defence missile systems on the left and right sides were undergoing modernisation, but the contract for modernisation was not completed in full. They were only partially operational."
17/ "One of the two radar stations had been suspended with cables since 2006 to prevent it from wobbling and [was] welded in place ... On the other – of the two channels, one was semi-working, without gyrostabilisation, with major limitations."
18/ This state of disrepair was very likely a factor in Moskva only detecting the incoming Ukrainian Neptune missiles when they were just 4 km, and a few seconds' flying time, away from the ship.
19/ Moskva was formally reinstated as a ship of the first line on 1 October 2021, by order of the commander of the 11th Anti-Submarine Ship Brigade. The ship was part of this unit, which had been formed on 1 June 1970, consisting of a command, brigade headquarters and six ships.
20/ By this time, preparations for the full-scale invasion of Ukraine were well underway. Russian forces had begun massing in Belarus and on the Russian border from the start of October, so Moskva's hasty reinstatement was almost certainly linked to this effort.
21/ Between 1 December 2021 and 10 February 2022, Moskva was put through K-1 and K-2 exercises intended to develop crew readiness. K-1 exercises are conducted within the naval base, K-2 exercises are performed at sea. However, the K-2 exercises were cut short by the invasion.
22/ Likely to support preparations on other ships, around 100 professional sailors were taken from Moskva's crew (possibly in January 2022 – Shkrebets does not specify) and were replaced with 86 conscript sailors taken from the patrol ships Ladny and Pytlivy.
23/ These men were, of course, untrained in Moskva's systems and emergency drills. The official list of those who died in the April 2022 missile attack indicates that most of the dead were conscripts. Their lack of training likely contributed to their deaths. Image
24/ A final exercise was carried out off Feodosia on 8 February 2022 before being terminated only two days later on 10 February. Shkrebets says they were overseen by the fleet's division commander, who was also the combat group commander at the time.
25/ At the premature end of the exercise, Captain Kuprin wrote a "Reference Report on the Status of the Guided Missile Cruiser 'Moskva'" which concluded that Moskva still had many very serious defects. Despite this, her condition was rated 'satisfactory'.
26/ This was clearly a politically motivated judgement by the Black Sea Fleet command rather than reflecting the alarming contents of Kuprin's report. On 20 February, Moskva set sail on what was to be her first wartime cruise.
27/ TO BE CONTINUED: Moskva goes to war: how Snake Island was captured, and subsequent Black Sea patrols.
@1Truthkeeper Actually on second thoughts, having re-listened to it I wonder if it might be some kind of status code - like the police using "10-4" to mean "message received". "690" could be the Russian Navy code for "we're fucked", perhaps.

• • •

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/ 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
Jun 21
1/ Ukraine's attacks against bridges, ferries, and logistics in Crimea have virtually cut off the peninsula. Russian warbloggers are reacting with anger and dismay. "Crimea has become an island," one admits. "Are we tolerating it?", demands another. ⬇️
2/ 'Intelligence Diary' sums up the situation following a Ukrainian attack using hundreds of UAVs, with Russia claiming to have shot down 239 but many more getting through:

"Crimea has become an island.

No ferry
No gasoline
No Chongar Bridge
No buses
No trains"
3/ He reports gloomily that "Crimea is in a complete fuel lockdown and there's a gasoline panic.

People are close to hysteria. The peninsula is descending into chaos."

He notes that Ukraine's data-enabled attack planning is fundamentally changing the situation for Russia:
Read 17 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!

:(