Archives

ARCHIVES

The BCFA Archive dates back to February 2022. Our archives allow members to study information preceding the most recent reports in order to gain full understanding regardless of their current familiarity with the topic of interest.

Institute for the Study of War: Mercenary leader Prigozhin reported killed in Russian missile strike on his private plane

Wagner Group financier Yevgeny Prigozhin and founder Dmitry Utkin reportedly died after Russian forces shot down an aircraft transporting senior Wagner commanders over Tver Oblast. The Russian Federal Aviation Agency (Rosaviatsiya) reported on August 23 that all the passengers – Yevgeny Prigozhin, Dmitry Utkin, Sergei Propustin, Yevgeny Makaryan, Alexander Totmin, Valery

Read More »

Ukrainian General Staff:  480 Russian casualties in 24 hours of fighting

The total combat losses of the enemy from 24.02.22 to 23.08.23 were approximately: personnel ‒ about 258820 (+480) persons,  tanks ‒ 4373 (+11), APV ‒ 8488 (+12) од,  artillery systems – 5318 (+23),  MLRS – 722 (+1),  Anti-aircraft warfare systems ‒ 491, aircraft – 315,  helicopters – 316,  UAV operational-tactical

Read More »

Russian Ministry of Defense: up to 595 Ukrainian casualties in 24 hours

The Armed Forces of the Russian Federation continue the special military operation. In the Kupyansk direction, the assault detachments of the Zapad Group of Forces carried out offensive actions in the assigned areas of responsibility and improved the tactical situation. With the support of aviation, artillery fire, and heavy flamethrowers,

Read More »

August 23, 2023

Institute for the Study of War: Mercenary leader Prigozhin reported killed in Russian missile strike on his private plane

Institute for the Study of War

Wagner Group financier Yevgeny Prigozhin and founder Dmitry Utkin reportedly died after Russian forces shot down an aircraft transporting senior Wagner commanders over Tver Oblast. The Russian Federal Aviation Agency (Rosaviatsiya) reported on August 23 that all the passengers – Yevgeny Prigozhin, Dmitry Utkin, Sergei Propustin, Yevgeny Makaryan, Alexander Totmin, Valery Chekalov, Nikolai Matyuseev – died in the crash along with all three crew members.[1] Russian opposition outlet Dossier reported that Chekalov, who is under US sanctions for transferring munitions to Russia and has acted on behalf of Prigozhin, oversaw Wagner transport logistics and “civilian” projects abroad.[2] A Russian insider source claimed that Chekalov also served as head of Wagner’s security services, though another source refuted this claim.[3] Dossier also reported that several other passengers joined Wagner between 2015 and 2017 and fought in Syria, although their current positions are unclear.[4] Russian sources amplified footage apparently showing a Russian missile striking an aircraft carrying Prigozhin, Utkin, and other Wagner commanders and the wreckage of the aircraft.[5] An insider source claimed that two S-300 missiles shot down the aircraft.[6] Flight tracking data for an Embraer Legacy 600 jet (registration number RA-02795) registered to the Wagner Group stopped after 6:11pm Moscow time while over Tver Oblast.[7] Russian sources claimed that a second Wagner Group-owned Embraer jet (registration number RA-02748) departed Moscow but turned around and landed at Ostafyevo airport in Moscow around the time of the strike.[8] Flight tracking data showed that this second aircraft arrived in St Petersburg at 6:27pm and flew back to Moscow 20 minutes later arriving at 8:02pm, however.[9]

The Russian Ministry of Defense (MoD) and the Kremlin have been destroying the Wagner private military company (PMC) and weakening Prigozhin’s authority since the rebellion – and the assassination of Wagner’s top leadership was likely the final step to eliminate Wagner as an independent organization. Wagner and Russian insider sources reported that the Russian MoD recently began forming new PMCs to replace Wagner in Africa and the Middle East and started recruiting Wagner personnel.[10] Wagner commanders indicated that two high-ranking Wagner officials joined the Russian MoD, and insider sources claimed that some Wagner personnel began to leave Belarus after Belarusian President Alexander Lukashenko refused to finance Wagner when he discovered that Russia would not pay Wagner’s costs.[11] Prigozhin’s online persona has been largely silenced since the rebellion – possibly as part of the deal between Lukashenko, Russian President Vladimir Putin, and Prigozhin – which may have negatively impacted Wagner’s ability to recruit new personnel amidst the Kremlin’s defamation campaign against Prigozhin. The Russian MoD and the Kremlin had effectively created conditions in which Prigozhin could no longer adequately support the Wagner contingent unless he was able to secure new funding and missions for Wagner personnel in the immediate term. Such conditions could have eventually led Wagner to slowly lose fighters and cause Prigozhin to lose his relevancy and influence.

Prigozhin was likely attempting to counter the Russian MoD’s and the Kremlin’s destruction of Wagner. A Russian insider source with reported ties to Russian security services claimed that Prigozhin’s “hasty” departure to and from Africa was in response to the Main Directorate of the Russian General Staff’s (GRU) plans and measures to undermine Wagner’s presence in Africa.[12] The source claimed that GRU Deputy Head (Head of the Special Activities Service) Colonel General Andrei Averyanov led the effort to completely block Wagner from operating in Africa and that there were plans to create and train an army corps of more than 20,000 people as Wagner replacements. The source added that Prigozhin was deeply opposed to these efforts and “made every effort to prevent them.” ISW observed that Prigozhin and Wagner’s representatives intensified their efforts to reestablish Wagner in Africa and the Middle East in mid-August, and Prigozhin even published a video of himself in an unspecified African country on August 21 – one of the few published videos of Prigozhin since the rebellion.[13] This video appeared to have heavy recruitment undertones, and it is possible that Prigozhin had traveled to Africa in hopes of securing further missions for Wagner personnel independent of the Russian MoD and the Kremlin.[14] Averyanov has reportedly participated in other high-profile assassination attempts such as the poisoning of Sergei and Yuliya Skripal, and it is possible that Russian officials capitalized on Prigozhin’s panic and impulsivity to eliminate Wagner’s top-most leadership.

Wagner PMC’s future without a leader remains uncertain. A Russian news aggregator claimed that the Wagner council of commanders is currently meeting at the time of this publication to prepare a joint statement and announce what will happen to Wagner in the near future.[15] The aggregator, citing an unnamed source, also claimed that Wagner had long developed a mechanism to mitigate the aftermath of Prigozhin’s and Utkin’s deaths.[16] The source, however, refused to disclose what such mitigations entail but noted that “in any scenario, [these mitigations] will be bad news.”[17] Wagner-affiliated channels urged Russian media to refrain from speculations about Prigozhin, Wagner’s fate, and the council of commanders.[18] A prominent Russian milblogger with reported connections to the Russian State Duma claimed that Wagner personnel are still “at their posts” in Belarus and Africa and denied the claims that Wagner personnel are being evacuated.[19] Prigozhin and Utkin were undeniably the faces of Wagner, and their assassinations will have dramatic impacts on Wagner’s command structure and the Wagner brand. Wagner commanders and fighters may begin to fear for their lives or become demoralized. The Russian MoD’s and Kremlin’s inroads into Wagner’s operations and the absence of Prigozhin – who would fight for new opportunities for Wagner personnel – may further lead to the degradation of the Wagner grouping.

Putin almost certainly ordered the Russian military command to shoot down Prigozhin’s plane. Elements of the Russian military, especially Russian Defense Minister Sergei Shoigu and Chief of the General Staff Army General Valery Gerasimov, would be extremely unlikely to execute Prigozhin without Putin’s order. The entirety of the Russian political and security sphere likely viewed Prigozhin’s continued survival following Wagner’s rebellion as at Putin’s discretion. ISW will make further assessments based on the assumption that Putin ordered Prigozhin’s assassination unless evidence to the contrary emerges. ISW’s previous standing assessment that Putin was unlikely to kill Prigozhin for fear of angering Wagner personnel has thus been invalidated.[20]

Putin may have concluded that he had sufficiently separated Prigozhin from Wagner and could kill him without turning Prigozhin into a martyr for the remaining Wagner personnel. Some Wagner commanders recently appeared to betray Wagner for the Russian MoD-affiliated Redut PMC, suggesting that the Kremlin’s and Russian MoD’s efforts to separate Wagner elements from those loyal to Prigozhin were partially succeeding.[21] Increasing reports of Wagner’s financial issues and corresponding reports of Wagner personnel leaving the group due to decreased payments and opportunities to deploy may have resulted in Prigozhin losing favor among the Wagner rank-in-file.[22] The Russian MoD has been setting conditions to replace the Wagner Group with MoD-affiliated PMCs, and Russian sources have claimed that these PMCs are attempting to recruit current and former Wagner personnel.[23] Putin may have decided that Wagner personnel had reached a point where they were sufficiently more interested in payments and deployments with these new PMCS than their continued loyalty to Prigozhin and that he could safely kill Prigozhin.

Alternatively, Putin may have decided that Prigozhin had crossed a pre-established redline with his efforts to retain Wagner’s access to operations in Africa. Putin, Prigozhin, and Lukashenko may have included an agreement in the deal that ended Wagner’s rebellion that required Prigozhin to limit his and Wagner’s media presence and/or curtail Wagner’s operations in Africa. Prigozhin’s August 21 video claiming that Wagner is expanding its presence in Africa and subsequent uptick in Wagner recruitment advertisements may have crossed a pre-established redline if Prigozhin had agreed to silence himself.[24] Prigozhin’s alleged repeated attempts to prevent the Russian MoD from completely replacing the Wagner contingent in Africa may have also crossed a pre-established redline restricting Wagner’s African operations. Putin may have decided that Prigozhin had violated enough aspects or all of the pre-established deal.

It is possible that Putin has intended to execute Prigozhin for some time and that the downing of Prigozhin’s plane on August 23 was coincidental timing, although this is unlikely. Kremlin newswire RIA Novosti reported on August 23 that Putin formally dismissed Wagner-affiliated Army General Sergei Surovikin as commander of Russian Aerospace Forces (VKS) and replaced him with Colonel General Viktor Afzalov.[25] The official confirmation of Surovikin’s dismissal in Russian state media on the same day as Prigozhin’s assassination is likely no coincidence. The Kremlin likely intends for both publicized punishments to send a clear message that those who were involved in the June 24 rebellion have been dealt with and that Wagner’s challenge to the Russian leadership is a settled affair.

Putin’s almost certain order for the Russian MoD to shoot down Prigozhin’s plane is likely a public attempt to reassert his dominance and exact vengeance for the humiliation that the Wagner Group’s armed rebellion on June 24 caused Putin and the Russian MoD. Putin notably attended a publicly televised concert in honor of the 80th anniversary of the Battle of Kursk around the time that Russian air defenses downed Prigozhin’s plane. Putin’s attendance at the televised concert echoed the memory of Soviet state television showing Swan Lake on television in August 1991 as the Soviet Union collapsed.[26] Russian sources noted that it has been exactly two months since the beginning of Wagner’s armed rebellion during which Wagner forces shot down several Russian helicopters and killed at least 13 Russian servicemen.[27] The decision to have Russian air defenses be the method for Prigozhin’s assassination allowed the Russian MoD to directly avenge what was one the deadliest days for Russian aviation since the start of the full-scale invasion. Putin had suffered significant humiliation for failing to stop Wagner’s rebellion, relying on Lukashenko to stop Prigozhin’s march, and failing to punish Wagner servicemen who were responsible for shooting down Russian aircraft on June 24.[28] Putin’s behavior during the rebellion reportedly concerned his inner circle about his ability to sustain his regime, and CIA Director William Burns reiterated similar observations about Putin’s judgments and detachment from events.[29] Burns also noted that “Putin is the ultimate apostle of payback,” and it is likely that Putin was waiting to set proper conditions to finally avenge himself on Prigozhin without appearing impulsive or overreacting.[30] Putin needed to exact ostentatious revenge against Prigozhin not only to prove that he is not a weak leader, but also to support his military – which in the eyes of many Russians did not see justice carried out for the events of June 24.

Specific individuals who may have planned to oppose Putin, the Kremlin, or the MoD have likely taken note of Prigozhin’s ultimate fate and other recent measures to reassert the Kremlin’s backing for the senior Russian military leadership. Putin notably sidelined Tula Oblast Governor Alexey Dyumin at the recent Army-2023 forum, publicly posturing him as subordinate to Shoigu following suggestions that Dyumin might replace Shoigu.[31] Putin and Gerasimov visited the Southern Military District (SMD) headquarters in Rostov-on-Don, which Wagner forces occupied during the rebellion, likely to publicly demonstrate the Kremlin’s backing of Gerasimov.[32] Prigozhin’s fate is also likely meant to serve as a deterrent to elements of the Russian military who may try to follow an existing precedent of insubordination that Prigozhin helped establish.[33] Lukashenko notably embarrassed Putin by directly negotiating with Prigozhin to end the rebellion, and Prigozhin’s assassination may signal to Lukashenko both a dramatic reduction of his negotiating space with the Kremlin and an implicit threat against his continued attempts to resist Union State integration efforts.[34]

The Kremlin appears to be setting conditions to deflect overt responsibility for Prigozhin’s assassination away from Putin and the Russian military. Rosaviatsiya created a special commission to investigate the technical condition of the crashed aircraft, the meteorological conditions on the flight route, and the dispatch services and ground radio equipment.[35] The Russian Investigative Committee has initiated a criminal case on the charge of violating the rules of traffic safety and operation of air transport.[36] A Kremlin-affiliated milblogger noted that the Investigative Committee may choose the “erroneous” launch of air defense systems as the main version of the event given the claimed Ukrainian drone strikes on Moscow.[37] A Russian insider source claimed that the crash will likely be framed as a terrorist act that occurred onboard, and Russian State Duma Deputy Yevgeniy Popov already echoed this narrative in the Russian information space.[38] A Wagner-affiliated channel criticized Russian state TV channels for failing to mention the crash during the evening news cycle.[39]

The wider Russian information space refrained from commenting on the reasons behind the crash, with only a few sources tying the incident to the Kremlin and/or the Russian MoD. Many sources observed that the crash occurred exactly two months after the start of Prigozhin’s rebellion.[40] Several insider sources claimed that the incident indicated that Putin “has something to be afraid of” and speculated that Putin’s system (likely referring to his regime) is undergoing a new wave of changes.[41] Some milbloggers claimed that Prigozhin’s assassination will have “catastrophic consequences” and that this incident is a lesson that one must always continue going until the end – implying that Prigozhin should have continued his march on Moscow.[42] Most milbloggers refused to comment on Prigozhin’s death, citing a lack of available official information.[43] ISW will resume its coverage of milblogger reactions on August 24.

Russian milbloggers will likely focus most of their coverage in the coming days on Prigozhin’s assassination and may report less on the Ukrainian counteroffensive. Russian milbloggers similarly shifted much of their reporting to cover Wagner’s rebellion on June 24 to developments within Russia and it took several days for them to return to their normal reporting on the frontlines in Ukraine.[44] The Kremlin may have decided to ostentatiously kill Prigozhin at this time in part to shift focus in the Russian information space away from the frontlines in Ukraine amidst notable Ukrainian advances. ISW’s coverage of kinetic activity on the frontlines in the coming days may be constrained if Russian reporting is limited.

Further tactically significant Ukrainian gains in and around Robotyne in western Zaporizhia Oblast are widening the Ukrainian breach of Russian defensive lines in the area and threatening Russian secondary lines of defense. Geolocated footage published on August 22 and 23 indicates that Ukrainian forces have advanced further in Robotyne (10km south of Orikhiv) and control most of the settlement and have made further gains west of Verbove (18km southeast of Orikhiv).[45] The Ukrainian General Staff reported that Ukrainian forces achieved unspecified success in the direction of Novopokropivka (13km south of Orikhiv) and Novodanylivka (5km south of Orikhiv).[46] Russian forces had likely hoped to use their positions in and around Robotyne as a launching point for counterattacks against the western flank of the Ukrainian advance east of the settlement, where Ukrainian forces appear to be widening their penetration through Russian first lines of defense. The Ukrainian advance through Robotyne itself and the potential liberation of the settlement will deprive Russian forces of positions near the western flank of the Ukrainian breach and therefore give Ukrainian forces more maneuver space to launch offensive operations against the Russian secondary line of defense that runs south of Robotyne to the western outskirts of Verbove. A successful deep penetration of Russian defensive lines likely requires a widening of the initial penetration to prevent Russian forces from cutting off a too-narrow thrust.

Ukrainian advances have now brought Ukrainian forces within roughly two kilometers of the secondary lines of Russian defense, a relatively more continuous set of field fortifications consisting of anti-tank ditches and dragon’s teeth anti-tank obstacles. The extent of minefields in the area is unclear, although areas in front of these secondary lines of defense may be less heavily mined to give Russian forces north of the lines the ability to retreat. ISW previously assessed that these secondary lines of defense may be relatively weaker than the first Russian defensive lines in the area due to a lack of uncommitted Russian forces in the area and further lateral deployments from other sectors of the front.[47]

Ukrainian forces likely struck a Russian S-400 air defense system in Crimea on August 23. The Ukrainian Main Military Intelligence Directorate (GUR) announced and posted footage of a strike on a Russian S-400 long and medium-range anti-aircraft missile system near Olenivka, Crimea (116km northwest of Sevastopol and about 140km south of Kherson City).[48] GUR reported that the strike destroyed an air defense installation, an unspecified number of missiles, and killed nearby Russian military personnel, though the footage only shows part of the installation exploding.[49] A Kremlin-affiliated Russian milblogger suggested that Ukrainian forces likely used a Harpoon, Neptune, or Brimstone II missile to strike the air defense system.[50] Russian milbloggers expressed concern that Ukrainian forces were able to operate a drone and record footage of the strike roughly 120km behind the current frontline.[51] A Ukrainian strike on a Russian air defense installation deep within the Russian rear indicates a number of Russian tactical failures, particularly that Russian forces were seemingly unprepared to intercept the missiles with the air defense system or operate electronic warfare jamming to prevent Ukrainian forces from operating a drone in the area. These tactical failures, though surprising and serious, may not be indicative of wider systemic issues within Russian air defenses, however.

US National Security Advisor Jake Sullivan and Pentagon Spokesperson General Patrick Ryder notably pushed back on an alleged US intelligence assessment that the Ukrainian counteroffensive will fail to meet its objectives. Sullivan stated on August 22 that the United States does not assess that the war in Ukraine “is a stalemate.”[52] Sullivan stated that the United States continues to support Ukraine in its counteroffensive efforts and noted that Ukrainian forces continue to take territory.[53] Sullivan noted that the United States will continue to support Ukrainian forces as they operate according to their tactics and timetable and proceed according to the strategic and operational decisions of their commanders and leadership.[54] Ryder stated on August 23 that it is “inappropriate” to draw any conclusions about the Ukrainian counteroffensive while fighting continues across the frontline and that Ukrainian forces continue to advance.[55] Sullivan’s and Ryder’s statements are a notable response to the Washington Post’s August 18 report that the US intelligence community has assessed that Ukraine’s counteroffensive will fail to reach Melitopol in western Zaporizhia Oblast and will not achieve its principal objective of severing the Russian land bridge to Crimea.[56]

Russian forces conducted a series of drone and missile strikes across Ukraine on the night of August 22 to 23 and destroyed grain infrastructure at the port in Izmail, Odesa Oblast. Ukrainian officials reported that Russian forces launched nine missiles and up to 20 Shahed-131/136 drones and that Ukrainian forces destroyed 11 drones, including nine over Odesa Oblast.[57] Ukrainian Minister for Communities, Territories, and Infrastructure Development Oleksandr Kubrakov reported on August 23 that the Russian drone strike on the port of Izmail destroyed over 13,000 tons of grain intended for Egypt and Romania.[58] Kubrakov reported that Russian strikes have destroyed 270,000 tons of grain since Russia’s withdrawal from the Black Sea Grain Initiative on July 17.[59] The Russian destruction of additional Ukrainian grain infrastructure comes less than a day after Putin attempted to mitigate dissatisfaction from African countries at Russia’s withdrawal from the grain deal during the BRICS Business Forum in South Africa.[60]

Key Takeaways:

  • Wagner Group financier Yevgeny Prigozhin and founder Dmitry Utkin reportedly died after Russian forces shot down an aircraft transporting senior Wagner commanders over Tver Oblast.
  • The Russian Ministry of Defense (MoD) and the Kremlin have been destroying the Wagner private military company (PMC) and weakening Prigozhin’s authority since the rebellion – and the assassination of Wagner’s top leadership was likely the final step to eliminate Wagner as an independent organization.
  • Prigozhin was likely attempting to counter the Russian MoD’s and the Kremlin’s destruction of Wagner and Wagner’s future remains uncertain.
  • Putin almost certainly ordered the Russian military command to shoot down Prigozhin’s plane.
  • Putin’s almost certain order for the Russian MoD to shoot down Prigozhin’s plane is likely a public attempt to reassert his dominance and exact vengeance for the humiliation that the Wagner Group’s armed rebellion on June 24 caused Putin and the Russian MoD.
  • Specific individuals who may have planned to oppose Putin, the Kremlin, or the MoD have likely taken note of Prigozhin’s ultimate fate and other recent measures to reassert the Kremlin’s backing for the senior Russian military leadership.
  • The Kremlin appears to be setting conditions to deflect overt responsibility for Prigozhin’s assassination away from Putin and the Russian military.
  • Further tactically significant Ukrainian gains in and around Robotyne in western Zaporizhia Oblast are widening the Ukrainian breach of Russian defensive lines in the area and threatening Russian secondary lines of defense.
  • Ukrainian forces likely struck a Russian S-400 air defense system in Crimea on August 23.
  • Russian forces conducted offensive operations along the Kupyansk-Svatove-Kreminna line, in the Bakhmut area, along the Avdiivka-Donetsk City line on August 23 and did not make any confirmed advances.
Share the Post:

Wilson Center

Forced displacement represents one of the most pressing humanitarian issues of our time. Individuals and families, torn from the fabric of their communities, find themselves navigating a world of uncertainty, often without basic necessities or a clear path to safety. There are currently some 110 million forced displaced, and this number is growing by 10 million each year!

At the heart of this crisis are the political triggers. Armed conflicts, ethnic or religious persecutions, and systemic human rights abuses force millions to flee their homes in terror. Many are displaced within their own national boundaries, while others seek asylum abroad. If these factors change as a result of political shifts at home or the pressures from abroad, they can return to their homes. Forced displacement is thus different from environmentally driven displacement, as victims of climate change may never be able to return to their homes.

The ramifications of any sort of displacement are profound, not just for those directly affected, but also for host communities and countries. Overburdened infrastructures, socio-economic strains, and cultural tensions can arise, necessitating comprehensive strategies to foster harmony and integration. Yet the root causes of forced displacement can be remedied with a concerted focus by local players and international diplomacy.

Organizations like Refugees International play a crucial role in this arena, advocating for the rights and needs of the displaced, conducting on-the-ground assessments, and influencing policymakers to take informed actions. Their relentless work underscores the gravity of the situation and the urgency ofinternational cooperation. But they, too, are overwhelmed by the rapid expansion of the crisis.

International Humanitarian Law (IHL), with its core principles centered on the protection of civilians during conflicts, plays a pivotal role in this discourse. Yet, despite clear legal frameworks, compliance remains
inconsistent. This initiative emphasizes the importance of upholding and reinforcing these international standards.

It’s not just about recognizing the problem; it’s about active engagement. We urge governments, organizations, and individuals to prioritize the rights and needs of the forced displaced. Through collective efforts, informed policies, and sustained advocacy, we can shift the narrative from passive acknowledgment to proactive intervention.