ChrisO_wiki Profile picture
May 2 31 tweets 8 min read Read on X
1/ A detailed inside account of the sinking of the Russian missile cruiser Moskva has been published. It describes how the ship was overwhelmed with fire and smoke, safety systems failed, interior structures collapsed and crewmen jumped out through portholes to save themselves.⬇️ Image
2/ On the afternoon of 13 April 2022, Moskva was struck and set on fire by two Ukrainian Neptune missiles. A day later, the ship sank. Russian authorities said that 396 crew members had been evacuated, with one sailor killed and 27 missing. Image
3/ Dmitry Shkrebets, the father of one of the missing sailors, has compiled an extremely detailed dossier of the events that led up to the sinking and how the sinking itself took place. It includes survivors' first-hand accounts. The ship was in a very poor condition at the time.
4/ As previously reported, a February 2022 report by its captain found numerous technical deficiencies in many of the ship's systems due to an apparent lack of maintenance. These were compounded by crewing issues on the ship.
5/ Shkrebets' dossier reports that about 100 experienced contract sailors were removed from the cruiser Moskva just before the war and transferred to other duty stations. Their places were taken by 83 conscripts, like Shkrebets' son Yegor, who were formally regarded as trainees. Image
6/ As well as being inexperienced and new to the ship, the conscripts were not supposed to be sent to a war zone. Despite this, Moskva repeatedly spent extended periods in Ukraine's territorial waters, most famously during the capture of Snake Island on the invasion's first day. Image
7/ The ship's logbook records numerous combat alerts caused by the detection of Ukrainian aircraft and incoming rocket artillery. Black Sea Fleet ships were ordered not to come within 30 km of the coast, but the threat of cruise missile attacks seems to have been ignored.
8/ At the time, as the captain's technical report recorded, the ship's radar and anti-missile systems had malfunctions which reduced effectiveness. On 7 March 2022, an Osa-MA2 air defence missile system on the starboard side had detected a probable UAV when it was only 7 km away. Image
9/ Moskva left Sevastopol for her last mission on 10 April 2022. On 12 April, the ship was ordered to "guard and defend" the Odessa gas field, 140 km from Odessa city and about 93 km from the nearest coastline in the Odessa region. This was well within Ukrainian missile range. Image
10/ By midnight on the same day, Moskva had reached a point within 5 km of the gas field. Despite the missile threat, it was not accompanied by any other ships, but the rescue vessel Epron was nearby. During the morning of 13 April the crew undertook exercises on board. Image
11/ According to Shkrebets, at 14:20 on 13 April, the ship detected incoming missiles only 4 km away. This was too close for the crew to react in time, and the missiles struck Moskva at a height of 3.5 m to 4 m above the waterline a few seconds later, just below the upper deck.
12/ Shkrebets provides a diagram of where the missiles hit. He writes that the first missile had the most destructive effect, hitting "the central part of the cruiser (compartment 8), with the galley and crew mess rooms at the epicenter of the explosion." Image
13/ The entire ship's crew had been scheduled to assemble in the mess room at 14:00 to be told about the outcome of the exercises, but this was delayed due to the mess crew not having washed the dishes and cleaned up in time. If they had, most of the crew would likely have died.
14/ The first missile strike also badly affected the engine room and the ship's damage control post, which controlled the ship's power systems and emergency response. It exploded a short distance below and behind a Vulkan P-1000 anti-ship missile system on the upper deck. Image
15/ The second missile hit the stern at the junction of compartments 12 and 13, below an AK-630 anti-aircraft gun, next to a torpedo tube and very close to the launcher for an S-300F Fort anti-aircraft missile system.
16/ As a result of the missile strikes, Shkrebets writes, "there was destruction, blocking and deformation of bulkheads, hatches and doors. Formation of cracks in the ship's hull structures and decks, collapse of ladders and platforms."
17/ "For example: in the officers' corridor they couldn't seal the door because it was simply torn off its hinges.

Which critically complicated orientation (due to the lack of electric lighting), visibility and the ability to breathe fully."
18/ The ship's main corridor was blocked by debris, preventing anyone from using it to exit the galley or mess, and "the ladders in the engine room were torn off (all the way to the starboard side)."
19/ The explosions rocked the ship, but the men on the upper deck and superstructure only perceived "two strong and dull bangs, indicating the detonation of missiles deep inside the ship's hull."
20/ Those near the impact points experienced a fiery blast. One man who was in the galley and mess hall at the time of the impact described it as "a barrage of fire rushing in, I didn't even hear the explosion."
21/ Very fortunately for the crew, none of the ammunition in the weapons systems near the impact points detonated at that time. If it had, the ship would undoubtedly have sunk very quickly and taken most of the crew with it.
22/ Although the initial fire in the stern caused by the second missile was soon extinguished, the fire in the mess hall burned through most of the ship, up to compartment 3 in the bow, and most of the way to the stern (as far as compartment 14).
23/ Shkrebets writes: "Due to the large-scale destruction, collapses and deformation of the ship's structures, thick and dense smoke penetrated almost everywhere without hindrance." The decks were "riddled with through cracks and fractures" which let the smoke spread.
24/ Project 1164 Atlant-class ships like Moskva have continous corridors along the entire lengths of their upper and lower (residential) decks. This contributed to the rapid spread of the fire and smoke. The bulkheads could not be sealed due to buckling caused by the explosions.
25/ Even on the upper deck, "the smoke itself was very thick and heavy (relative to the air), looked black, with large 'flakes' of soot, so there was essentially no air 'cushion' below (for breathing)." It was so thick that the men could not even see the life rafts on the deck.
26/ A number of men near the site of the explosions died immediately. Others perished "while trying to climb to the upper deck, through collapses and a wall of toxic smoke, in conditions of almost zero visibility." Some fell into the sea and died of hypothermia or drowing.
27/ TO BE CONTINUED: how Moskva's surviving crew fought to save the ship.
@ShipWrektPod As for the rear FRPP team being more effective, I think this could be accounted for by less severe damage and smoke at the aft. Shkrebets describes immediate severe fire and smoke forward and centre. The radio call I posted in part 2 likely came from the rear command post.
@ShipWrektPod I think what happened was that the rear command post was able to organise more quickly due to being less disrupted than the bridge, and was able to extinguish the second fire quickly because there was less local damage and fire. It also had the ship's only accessible fire suits.

• • •

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

Jul 31
1/ Even as Russian troops struggle for lack of vehicles, forcing them to rely on donations and home-made contraptions, Russia's vehicle manufacturers have cut back production due to economic difficulties. Russian warbloggers can't understand why they're not helping the army. ⬇️ Image
2/ AvtoVAZ, the makers of the iconic Lada and its military variants, has announced that it will cut salaries by at least 20% and will switch employees to a four-day week starting in September. Russia's slumping economy has led to a sharp decline in demand and sales. Image
3/ In February 2025 alone, AvtoVAZ had about 100,000 unsold cars, with the norm being 60,000, according to company president Maxim Sokolov. Truck manufacturers GAZ and KAMAZ are likewise switching to a four-day week.
Read 19 tweets
Jul 30
1/ Russian units are sustaining losses of 70-95% – with only the command staff being left alive in the latter case – before being declared combat ineffective, according to a Russian source. This is a far higher level of accepted casualties than in World War II. ⬇️
2/ The author of the 'Vault No. 8' Telegram channel discusses the level of losses at which a unit is considered to have lost combat readiness and requires withdrawal for replenishment, according to US Army doctrine (though misattributed here to Clausewitz):
3/ "If I remember correctly, then when 30% of personnel losses are reached, the same assault company must be withdrawn for replenishment in order to preserve the experienced core of the unit ...
Read 14 tweets
Jul 30
1/ Aeroflot has come in for ridicule after it was reported that pro-Ukrainian hackers found its CEO had not changed his password for three years. However, it's been reported that password management was the responsibility of a specialist FSB unit, which is now being blamed. ⬇️ Image
2/ The VChK-OGPU Telegram channel reports that sources say there is "panic in the ranks of the FSB's Department T in connection with the hacker attack on Aeroflot."
3/ "The special service employees who supervise transport infrastructure once again found themselves on the front line and were unable to ensure the security of yet another strategic facility.
Read 11 tweets
Jul 28
1/ Chechen leader Ramzan Kadyrov's recent near-drowning in Bodrum is reportedly suspected to have been a suicide attempt. He is said to have slipped away from his bodyguards and entered the sea in a presumed one-way trip, but was saved by beach lifeguards. ⬇️
2/ The VChK-OGPU Telegram channel reports on rumours around the incident which took place on 24 July at the Turkish resort of Bodrum, according to local media. According to the channel, Kadyrov was alone on the beach at the time.
3/ "The guards on the beach helped him, called an ambulance, and Kadyrov was taken to a private hospital. One of the TV channels showed Kadyrov's motorcade with an ambulance leaving the hospital grounds.
Read 8 tweets
Jul 26
1/ Russian warblogger Andrey Filatov has narrowly survived an FPV drone strike. He says he inadvertently got ahead of the protection of a vehicle.l equipped with electronic warfare equipment. ⬇️
2/ "Almost got caught, but the [Ukrainians] couldn't [manage it].

Situation.

Situation.

We had a jamming post of Chistyuli-Ornithologists, which covered the direction and the road of life/death. There were no serious problems there for almost a month.
3/ "Then the post position was changed and ... the guys made a mistake. They began to see further, and the road ended up in the radio shadow.
Read 7 tweets
Jul 25
1/ A Russian artilleryman has written a highly critical commentary on the way that the Russian army manages small units, which he says discourages independent thought and empowers "scoundrels". ⬇️ Image
2/ The 'Ghost of Novorossiya' Telegram channel posts the thoughts of an artilleryman with the callsign 'Lame', about the controls of small units at the platoon-company/battery level:
3/ "1. The old army maxim does not work: "Until you have risen to the rank of colonel, you do not need to think. Just follow orders." In general, it is a bad habit not to think, and in a modern war it is fraught with death.
Read 13 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!

:(