Coordinates: 56°30′0″N 31°43′15″E / 56.50000°N 31.72083°E / 56.50000; 31.72083

Toropets depot explosions

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
2024 Toropets depot explosions
Part of the Ukrainian attacks in Russia during the Russian invasion of Ukraine
NASA FIRMS imagery of the Toropets depot fires from 2024-09-17 to 2024-09-21 with first detection at 2024-09-17 23:58:00 (UTC)
Lua error in Module:Infobox_mapframe at line 197: attempt to index field 'wikibase' (a nil value).
DateSeptember 17–18, 2024 (2024-09-17 – 2024-09-18)
Time3:56 (UTC+03:00)
VenueToropets weapon depot
LocationToropets, Tver Oblast, Russia
CoordinatesLua error in Module:Coordinates at line 489: attempt to index field 'wikibase' (a nil value).
TypeWeapons storage explosion
CauseUkrainian drone attack[1]
PerpetratorSecurity Service of Ukraine
Deaths0 (per Russia)[3]
Non-fatal injuries13 (per Russia)[2]

On the night of 17–18 September 2024, during the Russo-Ukrainian War, Ukraine launched a drone attack on the 107th Arsenal, Main Missile and Artillery Directorate (GRAU), an ammunition depot of the Russian Armed Forces in Toropets, Tver Oblast. The attack causing a massive series of explosions and fires and shattering windows across nearby towns.[4][5] The primary explosion caused a 82 m wide crater[6] and a seismic wave of magnitude 2.5~2.8 on 18 September, 3:56 am, local time.[1][7]

Context

[edit | edit source]

Following more than two years of war, Ukraine moved the conflict into Russian territories. On 6 August 2024, Ukraine launched an incursion into Kursk Oblast. Ukraine claimed responsibility for the attack[1] stating it was led with domestically-manufactured airborne drones with a goal of normalizing such in-depth attacks in order to ease allies' stances.[8] Ukrainian representatives stated that more attacks of this kind are expected in order to “methodically” reduce Russia’s missile potential.[1]

Target

[edit | edit source]

In 2012, a program was launched to develop a comprehensive system for safeguarding ammunition in order to reduce the risk of accidental detonations. Funding for this program amounted to 90 billion rubles. The Minister of Defense Sergei Shoigu stated that under this program, in 2015 it was planned to produce 454 units in 13 arsenals.[9] The 107th Arsenal was modernized within the framework of this programme. 3.5 billion rubles were allocated for the construction of shelters in this territory. A modern arsenal was to appear, in compliance with environmental requirements.[10]

The facility was substantially expanded after 2010, reaching its current state by 2018, as seen in Google Earth history: numerous new buildings and hardened bunkers were added on the southeastern end, perhaps doubling the storage capacity.

Euronews reported that the military ammunition depot had been renovated in 2018, and that the Russian deputy defense minister claimed that "the site met the 'highest international standards" and could defend against weapons such as missiles and "even a small nuclear attack".[11] Euronews also reported that approximately 30,000 tonnes of military munitions were stored at the facility, including "fuel tanks, as well as .. Iskander and Tochka-U missile systems, guided aerial bombs and assorted artillery ammunition... Russia had also started to store North Korean munitions in Toropets."[12] NBC reported that KAB missiles were also stored at the facility.[11]

Depot contents

[edit | edit source]

CIA involvement

[edit | edit source]

Intelligence about the depot's munitions, its vulnerabilities, and nearby Russian defensive systems was provided to Ukraine by the Central Intelligence Agency. CIA officers were also responsible for calculating how many drones would be necessary, and for planning the drones' flight paths.[14]

Attack

[edit | edit source]

Ukrainska Pravda cited Ukraine's Security Service, Defence Intelligence and Special Operations Force as the author of the nighttime attack.[8] According to Russian Defense Ministry, all of the 54 Ukrainian drones aimed at western Russian regions were successfully intercepted.[8] According to Igor Rudenya, governor of Tver Oblast, debris of a successfully downed Ukrainian drone caused the fire, igniting the ammunition depot and the series of explosions.[8][5][15][16][17]

On 22 September 2024, media reported that Ukrainian drones had struck a second ammunition depot located south of Toropets, again causing a large fire.[18]

Explosions

[edit | edit source]
NASA FIRMS imagery from 21 September 2024 showing the newer, extensive fire south of Toropets with first detections at 00:18:00 (UTC) and the still ongoing fire from the first attack east of Toropets

The attack resulted in multiple secondary explosions, the largest being an earthquake-magnitude blast.[19] The blast wave spread up to 300 km (200 mi) and was estimated to have a TNT equivalent of either 200 to 240 tons or 1.3 to 1.8 kilotons of high-explosives.[3][19][11] Resulting fires were detected from NASA's fire monitoring systems as covering an area of approximately 13 km2 (5 sq mi).[19]

Consequences

[edit | edit source]

Igor Rudenya, governor of Tver Oblast, announced a partial evacuation of the town but that there were no serious injuries nor fatalities.[5][15][16][17] Russian officials later reported that 13 people had been injured.[2]

However, according to pro–Russian milblogger Anastasia Kashevarova, hundreds of Russians may have been killed in the strike, with the facility's utility block alone accommodating 200 people.[20]

On 20 September, Colonel Kiviselg, head of the Estonian Defense Forces Intelligence Center, estimated that the strike had caused 30,000 tonnes of munitions to explode, the size of which he equated to 750,000 shells, adding that the strike destroyed two to three months of Russia's ammunition supply. The depot reportedly stored not only artillery shells, but also Iskander missiles, Tochka-U ballistic missiles and glide bombs and it is unclear if his bomb damage assessment includes both missiles and artillery ammunition.[21][22]

See also

[edit | edit source]

References

[edit | edit source]
  1. ^ a b c d e f g h Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  2. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  3. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  4. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  5. ^ a b c Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  6. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  7. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  8. ^ a b c d e f Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  9. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  10. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  11. ^ a b c d Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  12. ^ a b c d e f g Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  13. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  14. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  15. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  16. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  17. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  18. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  19. ^ a b c Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  20. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  21. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  22. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).