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.⬇️
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.
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.
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.
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.
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.
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.
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."
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.
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
1/ Russian warbloggers are continuing to provide examples of how Telegram is used for frontline battlefield communications, to refute the claim of presidential spokesman Dmitri Peskov that such a thing is "not possible to imagine". ⬇️
2/ Platon Mamadov provides two detailed examples:
"Example number one:
Aerial reconnaissance of Unit N spotted a Ukrainian self-propelled gun in a shelter in the middle of town N."
3/ "Five minutes after the discovery, the target's coordinates and a detailed video were uploaded to a special secret chat group read by all drone operators, scouts, and artillerymen in that sector of the front.
1/ Russian soldiers overwhelmingly prefer to use Telegram for tactical communications despite the Russian army having its own dedicated military messengers. The reason isn't complex – the military's own alternatives are unreliable and difficult to use. ⬇️
2/ 'Vault No. 8' explains the problem:
"The Telegram slowdown is particularly nasty because Telegram is used for communication on the front lines.
Military messengers have been around since I wrote about this, but... Guess what you have to do to get a firmware-ready smartphone?
3/ "That's right! Buy it [with your own money] and send it in for a firmware update. On top of that, one of the military messengers periodically crashes like crazy, and the phone has to be sent in for a [periodic] firmware update, which takes at least a couple of weeks.
1/ Russian warbloggers are outraged at the Russian government's view that blocking Telegram is no big deal for frontline troops. They say it's a catastrophe heaped on the disaster of losing Starlink and that anyone who says Telegram isn't needed is talking "complete bullshit". ⬇️
2/ Dmitri Peskov, Vladimir Putin's spokesman, says: "I don't think it's possible to imagine frontline communications being provided via Telegram or some other messenger. It's difficult and impossible to imagine such a thing."
3/ However, it is very much a thing, as warbloggers have been pointing out furiously. 'Callsign Bruce' provides an example of how it is used to avoid friendly fire incidents:
"I'll give you a real-life example from one of the directions."
1/ Life after Starlink is proving to be difficult and frustrating for the Russian army. Russian warbloggers appear to be going through the stages of grief, expressing anger and alarm at the crisis and concern that Ukraine will exploit it. One anticipates "24/7 fucking". ⬇️
2/ Further instances of price-gouging are being reported, with the cost of US-made Ubiquiti WiFi bridges – illegally imported into Russia – doubling overnight. 'Strong Word' complains:
3/ "Elon is certainly a real jerk. But we have some real assholes in the rear who decided to ride the wave and make money off their own soldiers. Wi-Fi bridges instantly doubled in price. It's maddening, some are spilling blood, and others are making a living off of it."
1/ What can Russian soldiers do with thousands of useless Starlink terminals? One Russian warblogger has some humorous suggestions. ⬇️
2/ 'BKGB Casuar' writes:
"Here are 10 ways to use a broken terminal in the Special Military Operation zone:
3/ "1. Butt Kick.
The ground in the trench is cold and damp, and Elon Musk's plastic is warm and high-tech. Use it as an elite seat. Now you're not just a soldier in the mud, but a cyberpunk on a throne, whose butt is protected from moisture by American technology.
1/ Russian political officers are reportedly using the Epstein files to justify the 'Special Military Operation' (SVO) as a "war against global evil". However, as a frontline Russian warblogger points out, Russia and its soldiers are hardly innocent of crimes against children. ⬇️
2/ 'Vault No. 8', a serving soldier in the Russian army, writes:
"Over dinner, we were shown a report on the Epstein files: Satanism, cannibalism, paedophilia, child trafficking to EU countries in Ukraine, etc. The conclusion: "The SVO is the fight against global evil."
3/ "At the same time, during the SVO:
— I listened to the stories of several female specialists in men's health. One was raped by her grandfather, then later by her first husband. The second had a stepfather who was violent and raped her mother.