Hubbry Logo
search
logo
Battle of Khasham avatar
Battle of Khasham
Battle of Khasham
current hub
196812

Battle of Khasham

logo
Community Hub0 Subscribers
Read side by side
Battle of Khasham
View on Wikipedia
from Wikipedia

Battle of Conoco Fields (Battle of Khasham)
Part of the 2017–2019 Deir ez-Zor campaign of the Syrian civil war

Hatched box shows location of clashes
Territorial control in February 2018:
  Syrian Arab Republic
  Syrian Democratic Forces
Date7–8 February 2018 (1 day)
Location
near Khasham, Deir ez-Zor Governorate, Syria
35°20′10″N 40°18′34″E / 35.33611°N 40.30944°E / 35.33611; 40.30944
Result United States and SDF victory
Belligerents
Commanders and leaders
 Unknown
Units involved

Syria Syrian government forces

Wagner Group[10][3]

Strength

  • 40 American troops[6]

US aircraft and artillery

500 Syrian and Russian troops

27 total vehicles,[12][13] including T-72 tanks[14]
Casualties and losses
  • United States None
  • 1 SDF fighter wounded[15]
Map

The Battle of Khasham, also known as the Battle of Conoco Fields, was a military engagement of the Syrian civil war fought on 7 February 2018 near the towns of Khasham and Al Tabiyeh in the Deir ez-Zor Governorate, Syria. The Operation Inherent Resolve coalition delivered air and artillery strikes on Syrian Armed Forces and pro-government militias after they reportedly engaged a U.S. military and Syrian Democratic Forces (SDF) position in the region.

The US Central Command alleged that pro-government forces had "initiated an unprovoked attack against well-established Syrian Democratic Forces headquarters" in the area, while coalition service members were "co-located with SDF partners during the attack 8 kilometers (5 mi) east of the agreed-upon Euphrates River de-confliction line".[22][23][24] The Russian Ministry of Defence's statement, released on 8 February 2018, referred to the incident at the village of Salihiyah (located south of the SDF-held town of Abu Hamam in the Abu Kamal District) and said that it was caused by reconnaissance actions of Syrian militias that had not been cleared with the Russian operations command; the statement stressed that there were no Russian service members in the "designated district of the Deir ez-Zor province of Syria".[25][26]

The number of pro-Syrian government troops—particularly the number of Russian mercenaries—has been the subject of debate.[20]: 49  Shortly after the fighting, the American officials estimated that around 100 Syrian troops had been killed in the fighting, with some reports of Russian mercenaries among the dead.[13] As unconfirmed accounts of casualties among Russian Wagner Group mercenaries in the strike emerged, the incident was billed by media as "the first deadly clash between citizens of Russia and the United States since the Cold War".[27]

Reporting by Der Spiegel and the official Russian position hold that U.S. troops repelling a Syrian attack "happened to kill 20–30 Russians", while the Syrian Observatory for Human Rights (SOHR) believed there were some Russian casualties caused by a nearby booby-trap unrelated to the assault. However, other news organizations and American official estimates ranged up to a "couple of hundred" Russians killed. The Ukrainian Security Service of Ukraine identified 65 Russians as killed through open-source intelligence, though this appraisal has the potential for forgery. A report published by the University of Southern Denmark in 2019 which referred to claims made by Der Spiegel's report, official Russian and American statements, and other sources estimated "that 65–200 Russians (of which a few may have been Russian special operators assisting or leading the Wagnerites) died as a result of the fighting, some in the field, and some in hospital beds in Syria and Russia".[20]: 49–54 

Background

[edit]
See also: American-led intervention in the Syrian civil war, List of United States attacks on Syria during the Syrian civil war, and Al-Tanf (U.S. military base)

In September 2014, the United States began to undertake efforts to establish a global coalition with the declared aim of countering the Islamic State of Iraq and the Levant.[28] Since September 2014, the U.S. had conducted military operations in Syria, primarily against ISIL forces as part of Operation Inherent Resolve. The primary U.S.-backed force in the northeastern part of Syria is the Syrian Democratic Forces, a group composed predominantly of Kurdish and Arab militiamen. In 2017, backed by U.S. forces, the SDF captured Raqqa from the Islamic State and then advanced to the Euphrates River, where a deconfliction line was established by the governments of the United States and Russia.[29]

On several occasions, U.S. forces struck Syrian pro-government units operating in the area.[30][31][32] In November 2017, the U.S. government made it known that they were expanding their goals in Syria beyond routing ISIL forces, to pressure the Syrian government to make concessions at the Geneva talks.[33] This intent was, in mid-January 2018, clearly broadcast by Secretary of State Rex Tillerson, who said the Trump administration would maintain an open-ended military presence in Syria to counter Iranian influence and ensure the departure of Syrian President Bashar al-Assad.[34][35]

Russia had been conducting air military operations in Syria in support of the Syrian government since 30 September 2015. Furthermore, Russian private military contractors ("volunteers"), notably those associated with the Wagner Group, had been engaged in ground operations throughout that time, although their presence was never officially confirmed by the Russian government.[36]

In February 2018, Lt. Gen. Jeffrey L. Harrigian, Commander of U.S. Air Forces Central Command, talked about the circumstances before the attack: "The coalition observed a slow buildup of personnel and equipment the previous week, and we reminded Russian officials of the SDF and coalition presence via the telephone deconfliction line. This was well in advance of the enemy forces' attack. I know you're going to ask, so I'm going to be clear that I will not speculate on the composition of this force or whose control they were under."[7] Harrigian presented the U.S. strike as demonstration of the coalition's readiness "to prevent a resurgence of ISIS".[7]

On 22 February 2018, The Washington Post cited unnamed sources in U.S. intelligence as alleging that the communications intercepted days before and after the incident between Russian businessman Yevgeny Prigozhin, who was believed to finance Wagner, and senior Syrian officials, such as Mansour Fadlallah Azzam, as well as Kremlin officials, suggested that Prigozhin had "secured permission" from an unspecified Russian minister to go ahead with a "fast and strong" move in early February and was awaiting approval from the Syrian government.[27][37]

A few days before, Prigozhin had been indicted by the grand jury for the District of Columbia on charges related to the investigation into Russian interference in the 2016 U.S. elections.[38] A publication by the Ukraine-based anti-Kremlin InformNapalm alleged the operation had been cleared with the Russian military command by Sergey Kim, the chief of Wagner's operations department and a former Russian Naval Infantry officer.[39][40][41]

Incident and casualties

[edit]

U.S. version

[edit]

According to the U.S. military's official statement, around 10 p.m. local time on the night of 7 February 2018, a force of 500 pro-government fighters consisting of local militiamen, Syrian Army regulars, Shia militants from Liwa Fatemiyoun and Liwa Zainebiyoun, and reportedly Russian private military contractors, launched an assault on an SDF headquarters near Khasham.[22][13] Supported by T-72 and T-55 tanks, the pro-government troops first shelled the SDF base with artillery, mortars, "coordinated attack". Around 20–30 shells landed within 500 meters (1,600 ft) of the headquarters.[6][15][7]

According to the U.S. military, the presence of U.S. special operations personnel in the targeted base elicited a response by coalition aircraft, including AC-130 gunships, F-22 Raptor and F-15E Strike Eagle fighter jets, MQ-9 Reaper unmanned combat aerial vehicles, AH-64 Apache attack helicopters, and B-52 bombers.[6][15][7] Nearby American artillery batteries, including an M142 HIMARS, shelled Syrian forces as well.[15] According to sources in Wagner, cited by news media as well as the Department of Defense, U.S. forces were in constant contact with the official Russian liaison officer posted in Deir ez-Zor throughout the engagement, and only opened fire after they had received assurances that no regular Russian troops were in action or at risk.[42]

The clashes lasted four hours and saw more than 100 Syrian pro-government fighters killed, with one SDF fighter injured, according to the coalition. No U.S. troops were reported killed or wounded.[15]

According to two unnamed U.S. defense officials cited by CNN on 8 February, the U.S. military had assessed that Russian contractors had been involved, with one saying some of the contractors had been killed in the airstrikes.[15] A Kurdish militia commander and an ex-Russian officer also claimed Russian contractors were present and suffered casualties during the strikes.[43] During the two weeks following the incident, U.S. Secretary of Defense James Mattis and other U.S. military officials repeatedly stated that American military commanders were in contact with their official Russian counterparts prior to, during, and after the clash, and that the U.S military was told by their Russian counterparts that there were no Russians in the paramilitary formation.[44][45]

On 13 February 2018, unclassified footage depicting the coalition's targeted airstrikes on a pro-government T-72 tank position and a reported Russian contractor artillery position in the Khasham area was released by the Department of Defense.[46][failed verification]

Syrian government version

[edit]

In an official statement that was released by the "ISIS Hunters" unit of the Syrian Armed Forces, they had received intelligence that ISIL forces were moving towards Khasham and government forces decided to move from the Euphrates so to cut off ISIL's line of attack. At this point, armed groups were spotted east of Khasham, in SDF-held territory, which then attacked the government's troops. The groups were quickly pushed back. The military claimed that, according to intercepted radio traffic, the groups were partly ISIL and partly Kurds, and retreated towards the Conoco factory. At this point, pro-government units were hit by airstrikes. According to Syrian military sources, some 55 pro-government fighters were killed, including around 10 Russian fighters.[16]

Der Spiegel and SOHR version

[edit]

Der Spiegel version

[edit]

Three weeks after the incident, Germany's Der Spiegel published their own investigative report based on evidence gleaned from multiple first-hand sources (participants and witnesses) in the area. According to this report, pro-Syrian government forces spent a week prior to the event gathering in the Deir ez-Zor Airport, which is located to the west of the Euphrates[2] and south of Deir ez-Zor, the capital city of Deir ez-Zor Governorate.

In the vicinity of this city, the Euphrates river runs roughly from the northwest to the southeast, flowing into neighboring Iraq, and splits the city in two. The Syrian government controlled all areas west of the river, including the great majority of Deir ez-Zor, and a salient on the river's east bank across from the city. The SDF controlled almost all other territory east of the river, excluding the salient and the islands in the river.

The Iranian-backed forces that had gathered consisted of members of the Syrian Army's elite 4th Armoured Division, members of the militias of the local Bekara and Albo Hamad Arab tribes, and members of the Iranian-controlled Fatemiyoun and Zainebiyoun brigades.[2] Contrary to what was widely reported at the time, Der Spiegel later reported that according to witnesses, no Russian mercenaries were part of this formation.[2] At the time, Russia and the United States had an agreement that no more than 400 pro-Syrian government fighters could be in the Syrian-government controlled salient on the river's east bank.[2]

As with the deconfliction line, the Syrian government itself never officially agreed to this limit but due to its dependence on Russia, the Syrian Army had nevertheless been, by and large de facto adhering to both; the Iranian government also never joined either of these two bilateral U.S.–Russian agreements. Compared to its influence over the Syrian government, the Russian government had significantly less influence over Iran's government, military, and proxies in Syria, which constituted a large portion of pro-Syrian government ground forces in both Deir ez-Zor and throughout Syria.[47]

The Syrian government's dependence on these ground forces for territorial control, a consequence of severe manpower shortages in the Syrian military,[47] gave Iran significant influence over it, to the extent that Russia and Iran had to increasingly compete for control and influence over the Syria government.[48][49] Der Spiegel's report did not indicate whether this formation was under Iranian or Syrian command or what attempt, if any, Russia made to force the Syrian and Iranian governments to comply with these U.S.–Russian agreements.

At around 5 a.m. on 7 February 2018, around 250 of these fighters attempted to cross the Euphrates over a military pontoon bridge located to the southeast of both the Deir ez-Zor Airport and the SDF base near Khasham. Warning shots fired by U.S. military forces in the area stopped this morning advance, and the fighters withdrew back to the west of the Euphrates; these warning shots did not result in any injuries.[2] According to Der Spiegel, witnesses said that no Russian mercenaries were part of this group.[2]

Later that same day, under the cover of darkness, about twice as many pro-Syrian government fighters successfully crossed a different bridge located northeast of Deir ez-Zor Airport. They arrived at the village of Marrot, which is northwest of both Khasham and the nearby SDF base.[2] At around 10 p.m. that night, these fighters began to advance southeast toward Khasham. Concurrently, another group of Syrian tribal militia and Shia fighters began to advance north toward Khasham from Tabiyet Jazira, a Syrian government-controlled town east of the Euphrates that is significantly closer to Khasham (and the nearby the SDF base) than Marrot.[2]

U.S. military forces once again opened fire, but this time with the intention of inflicting casualties.[2] According to Der Spiegel's report, no Russians were in either formation, though there was a small contingent of Russian private military contractors (PMCs) stationed in Tabiyeh who were not participating in the fighting. Notwithstanding that, between 10 and 20 of the Russians were killed in the U.S. strikes, while most of the formations' deaths were reportedly among the servicemen of the 4th Armoured Division of the Syrian Army. Further strikes were carried out on the mornings of 8 and 9 February on tribal militia members that had come to retrieve dead bodies.[2]

SOHR version

[edit]

Similarly, the UK-based Syrian Observatory for Human Rights reported that 68 pro-government fighters were killed during the day in the area,[18] including 45 who died in the coalition airstrikes,[50] with most being Syrians.[18] The remaining 23 pro-government personnel, including 15 Russians PMCs, were not killed in the airstrikes, but instead caught in a booby-trapped explosion at an arms depot at Tabiyet Jazira. The PMCs were accompanying government forces as they advanced towards the SDF-held oil and gas fields.[51]

Unofficial Russian sources version

[edit]

Shortly after the strikes, various Russian unofficial sources began to publicize information that a number of Russian "volunteers" (PMCs) had been killed in the strikes,[3][52] with some posts on Russian social media making claims of over 200 Russian PMCs being killed, although the veracity of this information was questioned[53] and could not be confirmed.[54] Yevgeny Shabayev, a known critic of the company that hired the contractors, also claimed 218 PMCs were killed and that the families were still waiting for their remains.[55] Additionally, a Russian military doctor, a leader of a PMC-linked paramilitary Cossack organization, and a source with ties to Wagner claimed 80–100 PMCs were killed and 200 wounded.[19]

Contrary to the claims of hundreds of deaths among the PMCs, a Russian investigative group, the Conflict Intelligence Team (CIT), confirmed 10 contractor deaths[56] and estimated a total of between 20 and 30 had died.[57] A Russian journalist also believed between 20 and 25 PMCs died in the strikes.[53] On 17 February,[58] a Wagner leader, Andrei Troshev, was quoted as saying 14 "volunteers" died in the battle.[36] Three other Wagner commanders also stated the claim of 200 dead was an exaggeration and that 15 PMCs were killed at the most.[59]

Russian newspaper Kommersant, citing Russian military and contractor sources, reported pro-government forces were attempting to capture the Conoco (locally called Al Tabiyeh) gas field from the SDF.[60][61]

Official reaction

[edit]
  •  Russia – Russian member of parliament Frants Klintsevich called U.S. strikes illegal and an act of aggression.[62] Russia has accused the U.S. of being motivated by the presence of oil in the area.[13] Vasily Nebenzya, Russia's ambassador to the United Nations, called the strikes "regrettable" and promised to raise it to the Security Council.[63] On 8 February 2018, the Russian foreign ministry spokesperson, without referring to the U.S. strike, spoke of "the U.S. military presence in Syria present[ing] a serious challenge to the peace process and thwart[ing] the protection of the country's territorial integrity."[64]
  •  Syria – The Syrian foreign ministry wrote to the United Nations calling for the international community to condemn U.S. actions and labeled them a war crime, a "brutal massacre", and a crime against humanity. The Syrian government also accused American forces of aiding terrorism and violating Syria's sovereignty.[13]
  •  Iran – Ali Khamenei strongly condemned the confrontation and stated "Today, the U.S. government is the cruelest and most merciless system in the world, which is even worse than the savage ISIS members."[65]

Political ramifications in Russia and abroad

[edit]

In the wake of the incident, in the absence of any official comments in response to allegations about Russian fatalities, details about Russian citizens' involvement and casualties in the U.S. strike began to be made public through social and mass media, provoking resentment and outrage from sections of the Russian public.[66][67] The issue gained additional sensitivity in Russia in view of the upcoming presidential election in March 2018.[56] Prominent among those figures who early on made public information about presumably high numbers of Russian casualties in the U.S. strike was Igor Strelkov,[42][68] who in late February 2018 was registered as an authorized representative of Sergey Baburin, leader of the nationalist Russian All-People's Union and candidate for the 2018 Russian presidential election.[69]

Bloomberg, as well as other commentators, opined that both the Russian government and Trump administration, in their official statements, appeared to try obfuscating any Russian government role in the incident.[56][70] Irek Murtazin of Novaya Gazeta and analyst Yury Barmin speculated that the Russian Ministry of Defence may have wittingly let the Wagner unit find itself in harm's way.[27][71]

On 12 February 2018, Grigory Yavlinsky called on President Vladimir Putin to present an account of whether any Russian military forces had been involved in the battle.[72][73][74] Meanwhile, Russia's government-run news agency TASS acknowledged, with reference to a Cossack organisation, the death in a battle near Deir ez-Zor of a Russian "volunteer", sotnik Vladimir Loginov, a resident of the Kaliningrad Region.[75]

The news media also named four more Russians killed during the strike, including Kirill Ananiev, a veteran member of the banned National Bolshevik Party.[76][77] News outlets also noted that Vladimir Putin abruptly cancelled most of his previously announced engagements scheduled for 12 and 13 February, his press service citing ill health, and instead had a secret conference with his top military chiefs;[78][79] he also had a telephone conversation with U.S. president Donald Trump on 12 February, with no details revealed.[80][81]

Russian politician Viktor Alksnis, authorised representative of Communist Party presidential election candidate Pavel Grudinin, voiced an opinion on Radio Liberty that the U.S. strike was designed as a demonstration of the U.S.'s military superiority and dominance in the region, and that it might have serious geopolitical consequences for Russia.[82]

On 14 February, presidential spokesperson Dmitry Peskov admitted the possibility that some Russian citizens who were not part of Russia's armed forces were in Syria, but dismissed reports of mass casualties as false.[83] The following day, the Russian foreign ministry's spokesperson Maria Zakharova conceded that five Russian citizens might have been killed in the U.S. attack; she emphasized that they were not members of the Russian Armed Forces.[84][85]

State Duma Defense Committee Chairman Vladimir Shamanov, citing reported casualties of Russian PMCs, said the Russian parliament was working on a bill that would regulate activities of private military contractors, which he said was necessary.[86][87]

On 16 February, Viktor Alksnis said that the preliminary figure of Russian fatalities in the strike, based on information from the relatives and friends, stood at 334, mainly the personnel of the 5th storm squadron; he also said that, according to his information, personnel of Russia's Special Operations Forces were also involved in "the raid" on 7 February. This was in contrast to CIT's earlier confirmation by name of no more than eight dead.[88] On the same day, Russian Foreign Minister Sergey Lavrov in a Euronews channel interview said, "[The United States] seem to be seeking to isolate a vast part of the Syrian territory from the rest of the country in violation of Syria's sovereignty and territorial integrity."[89][90] According to an insider source quoted on 19 February by Vedomosti, there were 50 citizens of Russia and Ukraine dead as a result of the U.S. strike.[91][92]

On 20 February 2018, the Russian foreign ministry released a statement which, while admitting that there had been citizens of Russia and "countries of the CIS" killed and wounded in the course of the "recent clash" in Syria, claimed that no Russian service members or their materiel had been involved in any way.[93][94] Following the statement, the foreign ministries of Belarus and Kazakhstan were reported to be checking if there were casualties among their countries' citizens, but stated they had no information to confirm that Belarusians or Kazakhstanis had been killed or wounded.[95]

In late February 2018, CNN quoted multiple Russian sources claiming that those seeking to publicise information about the casualties in the 7 February strike were being harassed and silenced, presumably by people loyal to Yevgeny Prigozhin.[96]

Several Russian online news outlets, citing Syria's media and ex-KGB officer Igor Panarin, published unconfirmed reports that the Su-57 fighters, deployed to Syria since February 2017, had taken part in strikes against rebel targets in Eastern Ghouta, killing about ten U.S. personnel (military instructors) as well as other Western countries' instructors stationed in the rebel stronghold, despite the lack of known U.S. military presence in the region; the strikes were presented as retaliation for the U.S. attack at Khasham.[97][98][99] A short-term deployment of two Su-57s to Syria was officially confirmed by the Russian defence minister Sergey Shoygu on 1 March 2018.[100][101] Earlier, Komsomolskaya Pravda military correspondent Viktor Baranets [ru] was cited as saying that according to his information, the Su-57s had done "excellent" work carrying out their mission in Eastern Ghouta.[102]

On 12 April 2018, outgoing U.S. Central Intelligence Agency director Mike Pompeo, during his Senate hearing for the position of the United States Secretary of State, commented, "This administration announced a nuclear posture review that has put Russia on notice that we are going to recapitalize our deterrent force. In Syria, now, a handful of weeks ago the Russians met their match. A couple hundred Russians were killed."[103]

The death of the Russian investigative journalist Maksim Borodin, who wrote about the deaths of mercenaries in Syria in mid-April 2018, was linked by the media to his publications about Wagner's casualties in the clash at Khasham.[104]

Further incidents in the area

[edit]
See also: Deir ez-Zor Governorate clashes

On 10 February 2018, a U.S. MQ-9 Reaper drone destroyed a T-72 tank of pro-government forces in an airstrike near the Al Tabiyeh gas field. The tank itself was not firing on the SDF and the coalition, but other elements in the formation were.[105][106]

On 2 March 2018, at least two pro-government fighters were reportedly killed by coalition air raids near Khasham.[107][108]

On 27 March 2018, U.S. officials, including U.S. Secretary of Defense James Mattis, said a contingent of pro-Syrian government forces and Russian "mercenaries" had again similarly amassed near coalition forces in Deir ez-Zor the week prior, but the potential confrontation was defused after the U.S. military contacted Russian officers. Mattis believed the forces were under Russian control, as the pro-government troops pulled back after U.S. forces spoke with their Russian counterparts.[109]

On 29 April 2018, pro-government forces launched an assault against four SDF villages on the Euphrates, initially capturing them. However, the SDF later retook the villages, with local sources claiming coalition aircraft bombed pro-government positions in response.[citation needed]

On 11 May 2018, the coalition stated that SDF units responded to artillery fire from an unknown source on the outskirts of Deir ez-Zor; the SDF returned fire, leading to the destruction of one enemy artillery piece. No casualties were reported on either side of the engagement.[110] The coalition discussed the development with Russian counterparts via the established deconfliction line.[111]

See also

[edit]

References

[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Battle of Khasham

View on Grokipedia
from Grokipedia
The Battle of Khasham, also known as the Battle of Conoco Fields, was a four-hour military clash on 7 February 2018 in eastern Syria's Deir ez-Zor Governorate, where a force of roughly 500 pro-Syrian government combatants—including Russian Wagner Group contractors, Syrian Army elements, and Iranian-backed militias—attempted to overrun U.S. special operations personnel and Syrian Democratic Forces (SDF) holding the Conoco natural gas processing facility near the town of Khasham.[1][2] The attackers advanced with armored vehicles, artillery, and infantry under cover of night, ignoring prior U.S. warnings communicated through established deconfliction channels with Russian military liaisons.[1][3] Approximately 40 U.S. troops, embedded as advisors with SDF partners to counter ISIS remnants and secure oil infrastructure, responded with coordinated defensive fires, including 155mm howitzer barrages from attached artillery units, AC-130 gunship strafing runs, AH-64 Apache helicopter engagements, and precision airstrikes from F-22 Raptors and other platforms, systematically neutralizing over 100 advancing vehicles and the bulk of the assault force.[1][2][3] U.S. and SDF casualties were limited to non-fatal wounds, while attacker losses were severe, with U.S. assessments estimating 100 to 300 killed and the near-total destruction of their mechanized elements, though Russian and Syrian reports claimed far lower figures around 50-60 total deaths to downplay the rout.[1][3][4] The battle underscored the tactical effectiveness of U.S. joint fires in asymmetric defense against numerically superior but poorly coordinated foes, while exposing the vulnerabilities of deniable proxy forces like Wagner in challenging professionally integrated Western operations; Moscow officially disavowed the mercenaries, attributing the probe to "local" actors despite evidence of Russian command involvement, thereby avoiding escalation but revealing limits in hybrid warfare deniability.[5][6] It remains the deadliest U.S.-Russia proxy confrontation since the Cold War, influencing subsequent Russian restraint in Syria and highlighting risks of miscalculation in multi-actor conflicts over resource-rich zones.[1][2]

Historical and Geopolitical Context

Syrian Civil War and ISIS Defeat

The Syrian Civil War began in March 2011 amid widespread protests against President Bashar al-Assad's regime, which responded with military force, escalating demonstrations into full-scale armed conflict involving opposition groups, jihadist factions, and foreign powers.[7] By 2013, the Islamic State of Iraq and Syria (ISIS), evolving from al-Qaeda in Iraq, exploited the chaos to seize territory in eastern Syria, including parts of Deir ez-Zor province, and declared a caliphate in June 2014 across Syria and Iraq, controlling an area roughly the size of Britain with an estimated 10 million people under its influence at its peak.[8] ISIS imposed brutal governance, funding operations through oil sales and extortion, while conducting global terrorist attacks.[9] In response to ISIS's expansion, the United States formed a coalition in 2014, launching airstrikes and partnering with the Syrian Democratic Forces (SDF), a Kurdish-led alliance including Arab militias, to conduct ground operations without committing large U.S. troop deployments.[10] Russia intervened militarily on September 30, 2015, deploying air forces to support Assad's regime, which primarily targeted non-ISIS rebels rather than the jihadist group, enabling Syrian government advances in western Syria but contributing minimally to ISIS's territorial losses.[11] By 2017, coalition efforts yielded significant gains, with the SDF launching an offensive against ISIS's de facto capital of Raqqa in June, encircling the city amid intense urban fighting supported by U.S. special operations advisors and artillery; Raqqa fell to the SDF on October 17, 2017, after four months of combat that displaced over 300,000 civilians and caused high casualties on both sides.[12][13] Concurrently, Syrian government forces, backed by Russian airstrikes and Iranian-backed militias, lifted ISIS's three-year siege of Deir ez-Zor city in September 2017, capturing the urban core by November and pushing eastward along the Euphrates River, though ISIS retained pockets in the surrounding desert.[14][15] The SDF then advanced into Deir ez-Zor from the northeast, clashing with ISIS remnants and securing oil-rich areas by late 2017, as part of broader coalition operations that reduced ISIS-held territory in Syria by over 95% from its 2014 peak.[10][8] The U.S.-led coalition's partner forces, rather than Russian or Syrian efforts, accounted for the majority of ISIS's territorial defeats in Syria, with the group confined to rural enclaves by early 2018 and fully losing its last Syrian strongholds, such as Baghuz, in March 2019.[16] This collapse shifted post-ISIS dynamics toward competition between the SDF and pro-government forces for control of eastern Syria's resources, amid deconfliction protocols to avoid direct clashes.

U.S. and SDF Operations Against ISIS

The United States partnered with the Syrian Democratic Forces (SDF), a Kurdish-led coalition incorporating Arab fighters, to conduct ground offensives against the Islamic State of Iraq and Syria (ISIS) in eastern Syria as part of Operation Inherent Resolve. This cooperation intensified after the SDF's capture of Raqqa, ISIS's de facto capital, in October 2017, shifting focus to Deir ez-Zor province to dismantle remaining ISIS pockets east of the Euphrates River. U.S. support included embedded special operations advisors, close air support from coalition aircraft, and artillery fire from positions such as those near the Conoco gas plant, enabling SDF advances against ISIS-held terrain rich in oil and gas resources.[17][18] In September 2017, the SDF initiated the al-Jazeera Storm campaign, advancing southward from Hasakah province to seize key ISIS-controlled sites in Deir ez-Zor. On September 23, SDF fighters captured the Conoco gas field—Syria's largest natural gas facility, located near Khasham village—from ISIS after intense clashes, with U.S. coalition forces providing airstrikes and intelligence to neutralize militant defenses. This operation disrupted ISIS revenue streams from resource extraction and secured a strategic foothold, allowing further SDF pushes toward towns like Gharanij and Shadadi. By late 2017, these efforts had cleared significant ISIS territory, though militants retained pockets along the eastern bank, prompting continued U.S.-enabled raids and patrols.[19][20][21] U.S. forces maintained a presence of approximately 2,000 troops in Syria by early 2018, including advisors co-located with SDF units at forward operating bases east of the Euphrates to advise on tactics, provide real-time targeting data, and deter ISIS counterattacks. This embedded model proved effective in prior phases, such as the Raqqa campaign, where U.S. firepower inflicted heavy casualties on ISIS, but in Deir ez-Zor, operations adapted to rural, riverine terrain favoring guerrilla tactics by retreating jihadists. SDF ground assaults, bolstered by U.S. precision strikes, aimed to prevent ISIS reconstitution by securing resource sites and border areas near Iraq, though challenges persisted from ISIS improvised explosive devices and sleeper cells.[22][23] By February 2018, preceding the Khasham clash, U.S.-SDF operations had reduced ISIS territorial control in the region to isolated enclaves, with joint raids capturing or killing dozens of fighters weekly. However, the partnership prioritized ISIS defeat over permanent territorial gains, leading to de facto SDF administration of captured areas, including oil fields that funded local governance amid ongoing threats from ISIS remnants. This phase underscored U.S. reliance on local proxies for sustained presence while minimizing American ground combat exposure.[24][25]

Russian Intervention and Pro-Government Advances

Russia initiated its military intervention in the Syrian Civil War on September 30, 2015, deploying air forces from bases in Latakia and conducting airstrikes to bolster Syrian government positions against ISIS and rebel groups.[26] In the Deir ez-Zor region, Russian aviation provided critical close air support starting in early 2017, enabling Syrian Arab Army advances against ISIS encirclement of the city, which had persisted since July 2014.[27] By August 2017, intensified Russian airstrikes targeted ISIS supply lines and fortifications around Deir ez-Zor, facilitating ground offensives by Syrian forces and allied militias from the west and south.[28] On September 5, 2017, these operations culminated in the lifting of the three-year ISIS siege, with Syrian troops linking up across government-held corridors and securing the city's airport and surrounding districts.[27] Russian strategic bombers, including Tu-22M3s, were employed to destroy ISIS command centers and armor, contributing to the recapture of over 100 square kilometers in the vicinity.[29] Post-siege, pro-government forces pressed southward and eastward along the Euphrates Valley in September-October 2017, supported by ongoing Russian air cover, to eliminate ISIS pockets and consolidate control west of the river.[28] These advances overlapped with SDF operations east of the Euphrates, prompting incidents such as a Russian airstrike on September 18, 2017, near U.S. advisory positions in Deir ez-Zor, which highlighted frictions despite U.S.-Russian deconfliction channels.[30] By November 2017, Syrian and allied units, backed by Russian and Iranian elements, captured Al-Bukamal on the Iraqi border, further extending government reach but straining relations with U.S.-protected zones holding key oil infrastructure. This momentum set the stage for subsequent pro-government probes into SDF-held territories east of the Euphrates in early 2018.[31]

Prelude to the Clash

Control of Deir ez-Zor Oil Fields

The Syrian Democratic Forces (SDF), backed by U.S. coalition airpower and special operations, captured key oil fields in Deir ez-Zor province from the Islamic State (ISIS) during their offensive in late 2017. On October 22, 2017, the SDF seized the Al-Omar oil field, Syria's largest and estimated to produce up to 30,000 barrels per day prior to the war, along with surrounding facilities east of the Euphrates River. This followed earlier gains, such as the Conoco gas plant and associated fields near Khasham, secured amid the broader push to dismantle ISIS's territorial caliphate, which had controlled these resources since 2014 to fund its operations.[32][33][34] These fields, concentrated in the eastern Deir ez-Zor region bordering Iraq, represented a substantial portion of Syria's pre-war oil output, with the province holding reserves estimated at around 70% of the country's total hydrocarbon resources. Control allowed the SDF to generate revenue through local sales and smuggling, estimated at tens of millions of dollars annually, which supported their governance in Kurdish-majority areas and anti-ISIS efforts, though exact figures varied due to opaque operations and sanctions. U.S. forces established bases at sites like the Conoco facility to secure these assets, prevent their recapture by ISIS remnants or the Assad regime, and deny economic leverage to Iranian-backed militias advancing from the west.[35][36] By early 2018, the Euphrates River served as a de facto dividing line: SDF and U.S. coalition elements held the eastern bank, including the lucrative Al-Omar, Tanak, and Jafra fields, while Syrian government forces, supported by Russia and Iran, consolidated the west after lifting the ISIS siege of Deir ez-Zor city in September 2017. Pro-government advances aimed to cross the river and reclaim these resources for the Assad regime, which viewed SDF control as a direct threat to sovereignty and economic recovery, prompting tensions despite U.S.-Russian deconfliction channels. This standoff over the oil fields escalated into direct confrontations, as regime-aligned militias sought to exploit ISIS's collapse to unify territorial control.[19][37]

Pro-Government Force Movements

In late 2017, following the Syrian government's recapture of Deir ez-Zor city from ISIS in September, pro-government forces—including the Syrian Arab Army (SAA), Russian Wagner Group contractors embedded with local militias like the 5th Assault Corps and ISIS Hunters, and Iranian-backed units such as Liwa Fatemiyoun—initiated eastward advances across the Euphrates River to contest SDF control of oil and gas infrastructure.[5] These movements disregarded a U.S.-Russia deconfliction protocol established in 2015, which implicitly divided operations with SAA allies remaining west of the river while SDF forces operated east, ostensibly to avoid direct clashes during anti-ISIS campaigns.[38] The primary aim was to seize facilities like the Conoco gas plant—Syria's largest, capable of producing 5.6 billion cubic meters of gas annually—controlled by SDF since 2017, thereby denying economic assets to U.S.-backed groups and bolstering Assad regime revenues estimated at millions in lost production.[14][1] By early February 2018, these forces had massed artillery and armor west of the river before probing crossings via makeshift bridges and ferries, capturing villages in the Euphrates Valley to establish bridgeheads.[5] Wagner operatives, reportedly numbering in the hundreds and coordinated with Syrian 4th Armored Division elements, provided training, equipment, and direct assault support to paramilitary units tasked with the push, motivated partly by interests tied to Yevgeny Prigozhin's Evro Polis company, which held concessions for the Conoco fields.[5] On February 7, pro-government columns began concentrating near Khasham around 3:00 p.m. local time, assembling over 500 fighters with 27 vehicles including T-72 tanks, BMP infantry fighting vehicles, and artillery pieces from positions west of the Conoco refinery.[1] By early evening, three T-72 tanks had maneuvered to within one mile of the SDF-held site, supported by artillery fire rehearsals targeting defensive positions.[1] At approximately 10:00 p.m., the assault force advanced from an adjacent neighborhood in a coordinated mechanized push, employing suppressive fire to overrun the refinery headquarters.[1] This operation represented a second attempted breach of the deconfliction line that night, escalating tensions amid prior U.S. warnings via Russian channels.[5]

U.S.-Russian Deconfliction Communications

The U.S. and Russia established deconfliction protocols in Syria as early as 2015 to mitigate risks of direct military confrontation, evolving into a dedicated hotline between U.S. Central Command and Russian forces by 2017. This mechanism delineated operational zones, with the Euphrates River formalized as the boundary after U.S.-backed Syrian Democratic Forces secured the eastern bank, reserving it for anti-ISIS operations while ceding the west to Syrian government advances supported by Russia.[39][40] In early February 2018, as pro-Syrian government militias—including Russian private military contractors—massed and probed eastward toward the Conoco gas processing facility near Khasham, U.S. military officials repeatedly alerted their Russian counterparts via the deconfliction line about the buildup of over 500 fighters, dozens of vehicles, tanks, and artillery pieces violating the Euphrates demarcation.[41][40] These warnings explicitly flagged the risk of a U.S. defensive response if the incursion proceeded, emphasizing the presence of American advisors embedded with Syrian Democratic Forces at the site.[40] Russian officers responded that Moscow exercised no authority over the irregular units involved, distancing the Russian Ministry of Defense from the advancing proxies despite evidence of Russian-supplied equipment and personnel.[41][40] This attribution of non-control enabled plausible deniability for operations conducted by semi-autonomous groups like the Wagner organization, which operated outside formal Russian chains of command but aligned with broader Syrian regime objectives in Deir ez-Zor.[40] The failure of these preemptive communications to deter the offensive—despite U.S. indications of resolve—underscored limitations in the deconfliction framework when proxies evaded official oversight, culminating in the unheeded assault on February 7.[41][40]

Course of the Battle

Initial Assault on February 7, 2018

On the evening of February 7, 2018, approximately 500 pro-Syrian government fighters, including Russian Wagner Group contractors, Syrian Arab Army elements from the 5th Assault Corps, and Iranian-backed militias such as Liwa Fatemiyoun, launched a coordinated assault against Syrian Democratic Forces (SDF) positions at the Conoco gas plant near Khasham, Deir ez-Zor province.[41][1] The attack commenced around 22:00 local time with initial artillery and mortar barrages targeting the outpost, followed by an advance of roughly 20-30 armored vehicles, including T-72 tanks and BMP infantry fighting vehicles, supported by dismounted infantry aiming to overrun the defenses.[42][43] The pro-government force sought to capture the strategically vital oil infrastructure held by the SDF, with U.S. military advisors—numbering about 40 special operations personnel—embedded to provide training and support.[1][44] U.S. surveillance detected the buildup hours earlier, prompting repeated warnings through established U.S.-Russian deconfliction channels to halt the advance, but the assault proceeded without acknowledged response from Russian military liaisons.[41][45] Initial ground probes met resistance from SDF fighters, who held elevated positions around the plant, while U.S. forces prepared defensive measures including anti-tank weapons and called for air support; the attackers' vehicles closed to within several hundred meters, attempting to breach perimeter lines under cover of darkness and suppressive fire.[1][42] Wagner Group accounts later described their column moving under the assumption of minimal opposition, only encountering incoming fire upon nearing the target, highlighting a tactical underestimation of U.S. commitment to the site.[45]

U.S. Defensive Tactics and Firepower

U.S. forces, consisting of approximately 40 special operations personnel embedded with Syrian Democratic Forces (SDF) at the Conoco gas plant, adopted defensive positions in foxholes and behind dirt berms to withstand the initial artillery barrage and ground assault launched around 9:45 p.m. on February 7, 2018.[41] These troops returned fire using machine guns and anti-tank missiles, targeting advancing enemy vehicles including T-72 tanks and armored personnel carriers.[41] The defensive setup leveraged the plant's infrastructure and surrounding terrain for cover, allowing the small contingent to hold against an estimated 500 attackers equipped with heavy armor.[2] As the assault intensified, U.S. combat controllers coordinated rapid reinforcement and firepower escalation, directing Marine artillery units—likely including M777 howitzers and M142 HIMARS systems positioned nearby—to deliver counter-battery fire and precision strikes on enemy concentrations.[46] [47] This artillery response suppressed incoming mortar and rocket fire, inflicting significant casualties on the pro-government forces.[41] Concurrently, an MQ-9 Reaper drone provided real-time intelligence and initial strikes with Hellfire missiles, marking the transition to integrated joint fires.[2] Air superiority proved decisive, with U.S. forces summoning a cascade of close air support assets despite the risks of operating in contested airspace. An AC-130 gunship, dubbed "Spooky," engaged with its 105mm howitzer and 30mm cannons, delivering devastating area suppression on infantry and light vehicles.[44] AH-64 Apache helicopters fired additional Hellfires and rockets at armored threats, while F-15E Strike Eagles conducted precision bomb drops.[44] F-22 Raptors provided stealthy overwatch to deter potential Russian air intervention, and B-52 bombers loitered for potential heavy ordnance delivery, though not confirmed used in direct strikes.[44] This multi-layered firepower, guided by ground controllers under intense fire—one of whom earned the Air Force Cross for sustained direction of strikes—overwhelmed the attackers, forcing their withdrawal after four hours with minimal U.S. casualties.[48] [41]

Withdrawal and Cessation of Hostilities

The pro-government forces' advance halted short of overrunning the U.S.-SDF positions at the Conoco gas plant after sustaining intense defensive fire from U.S. artillery, including High Mobility Artillery Rocket Systems, and initial helicopter strikes that destroyed multiple armored vehicles advancing to within 300 meters of the outpost.[1] Over the subsequent 45 minutes, escalating U.S. air support from AH-64 Apache helicopters, AC-130 gunships, F-15E Strike Eagles, and other fixed-wing assets targeted the remaining assault elements, dismantling the bulk of the attacking columns comprising tanks, infantry fighting vehicles, and dismounted troops.[2] This phase of the engagement, commencing around 10:00 p.m. local time on February 7, 2018, inflicted disproportionate losses, with intercepted communications from Wagner Group participants later describing the outcome as a humiliating rout.[2] Surviving attackers initiated withdrawal approximately one hour following the peak of U.S. aerial operations, retreating eastward toward Syrian government-held territory while abandoning damaged equipment and suffering further attrition from ongoing strikes.[1] Concurrently, U.S. officials in Washington engaged Russian counterparts through established deconfliction channels, securing the temporary shutdown of a Russian-operated surface-to-air missile battery that had threatened incoming American aircraft, thereby enabling unrestricted close air support.[1] These communications underscored the deniability of the assault, as Moscow publicly disavowed control over the proxy forces involved, attributing the operation to Syrian regulars and unattributable mercenaries.[2] Hostilities ceased formally via a negotiated cease-fire between U.S. and Russian military representatives, with the pro-government withdrawal completing by roughly two hours before dawn on February 8, 2018, after approximately four hours of combat.[1] Remnants of the force subsequently reapproached the battlefield under darkness to recover casualties and salvage wrecks, confirming the offensive's total repulse without recapture of the contested oil and gas infrastructure.[2] No further incursions occurred in the immediate vicinity, preserving U.S.-SDF control over the Khasham area.[1]

Casualties, Forces Involved, and Conflicting Accounts

U.S. and SDF Estimates

The United States military estimated that the pro-regime attacking force numbered more than 500 fighters, including Syrian government troops, Iranian-backed militias, and Russian private military contractors, advancing with approximately 100 vehicles such as armored personnel carriers, tanks, and artillery pieces.[41] U.S. Central Command reported destroying over 100 enemy vehicles and killing between 200 and 300 combatants during the four-hour engagement on February 7, 2018, attributing the high toll to coordinated airstrikes, artillery barrages, and defensive fire from approximately 40 U.S. special operations personnel embedded with Syrian Democratic Forces (SDF) positions.[41] [1] No U.S. personnel were killed or wounded, reflecting the effectiveness of layered defenses including Apache helicopters, AC-130 gunships, and F-15 strikes that neutralized the assault waves.[2] SDF commanders aligned their assessments with U.S. figures, reporting over 100 pro-regime fatalities in initial statements, with their own forces suffering minimal losses—specifically one fighter wounded amid the defense of the Conoco gas plant near Khasham.[44] The SDF emphasized the attackers' use of human waves and vehicle-borne assaults, claiming the coalition response prevented any territorial gains and inflicted disproportionate casualties, estimated at around 200 enemy dead based on battlefield observations and intercepted communications.[49] These estimates, derived from drone footage, signals intelligence, and post-battle reconnaissance, contrasted sharply with lower figures from Syrian and Russian sources but were corroborated by U.S. after-action reviews highlighting the destruction of nearly the entire mechanized element of the assault.[1]

Russian Official and Wagner Perspectives

The Russian Ministry of Defense maintained that no regular Russian troops participated in the February 7, 2018, assault near Khasham, describing the attacking force as Syrian government-aligned militias conducting an uncoordinated reconnaissance operation.[50] The ministry estimated the involved pro-government contingent at around 500 personnel, primarily Syrian regulars and local irregulars, with no acknowledgment of private military contractors.[51] It reported only 25 Syrian militia casualties, attributing higher claims to unverified reports and emphasizing that Russian forces were not engaged.[50] Russia's Foreign Ministry later conceded that "several dozen" Russian nationals sustained injuries from U.S. strikes, with an unspecified number fatalities among volunteers or contractors, while denying operational control over the assailants.[52] [53] This figure represented a minimal official tally, contrasting with independent estimates and aimed at distancing the state from private actors, whose activities were then illegal under Russian law.[54] Wagner Group-affiliated Telegram channels, such as Grey Zone, portrayed the engagement as a deliberate advance by several hundred Russian contractors against U.S.-SDF positions, resulting in catastrophic losses from sustained American artillery and air bombardment.[45] These accounts detailed the near-total destruction of an armored column, with fighter communications indicating up to 200-300 killed or wounded, including incinerated T-72 tanks and BMP vehicles.[45] [55] Yevgeny Prigozhin, the group's backer, subsequently blamed Russian military leadership for withholding air support despite foreknowledge, framing the outcome as abandonment that exacerbated the disproportionate casualties.[56]

Syrian Government Claims

The Syrian government portrayed the February 7, 2018, advance toward Khasham as a legitimate operation by "popular forces" targeting ISIS remnants and U.S.-backed militants in Deir ez-Zor province.[57] State media, including the Syrian Arab News Agency (SANA), described these forces as local tribesmen and allied militias loyal to President Bashar al-Assad, engaged in counter-terrorism efforts east of the Euphrates River.[58] Officials denied any unprovoked assault on U.S. or SDF positions, framing the movement as defensive against terrorist threats rather than an offensive to seize oil fields.[57] In response to U.S. defensive strikes, the Syrian Foreign Ministry and state outlets condemned the coalition's actions as "new aggression" and an "attempt to support terrorism," accusing the U.S. of committing war crimes by bombing Syrian troops.[59][60] SANA reports emphasized that the strikes violated Syrian sovereignty and aided SDF forces, which Damascus labeled as terrorist affiliates, without acknowledging coordination failures with Russian allies or the involvement of foreign contractors.[58] The regime rejected U.S. claims of an unprovoked attack, insisting the engagement stemmed from ongoing anti-ISIS operations.[57] Syrian state media reported casualties from the U.S. strikes as "dozens of dead and wounded" among government-aligned fighters, with Al-Ikhbariyah TV specifying heavy losses but avoiding precise tallies initially.[57] Later attributions to official sources cited approximately 50 to 55 Syrian Arab Army soldiers killed, downplaying foreign elements like Afghan Shia militias or Russian nationals and omitting equipment losses such as tanks and artillery.[60] These figures contrasted sharply with higher estimates from other observers, but Damascus maintained them to portray resilience against foreign intervention.[54] No admissions of tactical errors or proxy force composition appeared in official narratives.

Independent Verifications and Media Investigations

Media investigations into the Battle of Khasham primarily relied on declassified U.S. military documents, interviews with American participants, and intercepted communications to reconstruct events. A New York Times report detailed a four-hour engagement on February 7, 2018, involving roughly 500 pro-Syrian government fighters assaulting a U.S.-SDF outpost defended by about 40 American personnel, resulting in 200 to 300 attacker casualties from coordinated U.S. artillery and airstrikes, with no U.S. deaths.[41] The investigation highlighted warnings issued via U.S.-Russian deconfliction channels, which Russian officers allegedly dismissed, and confirmed the attackers' advance under cover of night with tanks and armored vehicles.[41] Open-source intelligence analyses have verified material losses through photographic and video evidence of destroyed equipment. Oryx, a defense blog specializing in visual confirmations, documented the destruction of at least 11 T-72 tanks, 5 BMP-1 infantry fighting vehicles, 2 BRDM-2 scout cars, and additional artillery pieces and trucks belonging to pro-government forces, corroborating the intensity of U.S. firepower and the failure of the assault.[61] These losses, geolocated to the Khasham area, align with post-battle imagery showing burned-out hulks but underscore challenges in fully accounting for unphotographed or salvaged items. Casualty estimates from independent monitors diverge from U.S. claims. The Syrian Observatory for Human Rights (SOHR), a UK-based group tracking Syrian conflict deaths via local networks, reported 68 pro-government fatalities, including 10 to 12 Russians, significantly lower than Pentagon figures and suggesting potential underreporting due to limited access in regime-controlled areas.[62] SOHR's data, while empirically derived from informant reports, has faced scrutiny for opposition leanings, though it often cross-verifies with multiple sources. Other investigations, including participant interviews in outlets like The War Horse, reinforced U.S. accounts of heavy enemy losses without independent body counts.[1] No comprehensive satellite imagery analyses have publicly confirmed precise casualty numbers, but equipment wreckage patterns support a lopsided outcome favoring defenders.

Immediate Aftermath

Battlefield Cleanup and Assessments

U.S. and Syrian Democratic Forces (SDF) personnel secured the Conoco gas processing plant following the withdrawal of pro-regime attackers on the night of February 7, 2018, conducting initial battle damage assessments (BDA) via overhead drones and ground reconnaissance to confirm the neutralization of the assault. These assessments documented extensive destruction among the attacking force's equipment, with no significant damage reported to the plant's infrastructure itself, which remained operational under SDF control.[1][2] Independent open-source intelligence verification, relying on geolocated imagery of vehicle wrecks, confirmed the loss of at least 11 pro-regime vehicles in the engagement: three T-72 tanks (two destroyed by airstrikes and one by ground fire), two armored fighting vehicles (BMP-1 variants), one gun-mounted truck (likely a 2S1 Gvozdika self-propelled howitzer adapted), one towed artillery piece (MT-LB with 122mm howitzer), and four technicals (pickup trucks with mounted weapons). These losses were attributed to combined U.S. airstrikes, artillery, and machine-gun fire, with remnants left scattered across the battlefield due to the rapidity of the retreat and ongoing SDF presence.[61] Cleanup efforts were limited and contested; surviving pro-regime fighters, including Wagner Group elements, returned to the site in subsequent days under cover of darkness to retrieve bodies, amid U.S. estimates of 200 to 300 fatalities among the attackers, though Russian state media downplayed losses and claimed successful evacuations. SDF forces handled on-site disposal of unrecovered remains and unexploded ordnance to restore access routes, while denying regime access to salvage equipment, which remained in contested territory until later regime advances elsewhere in Deir ez-Zor. No formal international oversight or humanitarian cleanup was reported, reflecting the area's status as a active conflict zone.[41][1]

Diplomatic Exchanges Post-Engagement

U.S. military officials utilized the pre-existing deconfliction hotline with Russian counterparts immediately after the February 7, 2018, engagement to report the defensive strikes and affirm that coalition forces had repelled an unprovoked assault on established positions near Khasham.[40] These post-battle communications, which extended the channel's use from before and during the clash, elicited repeated denials from Russian officers that the advancing forces included regular military personnel, with Moscow attributing the attack to Syrian allied militias operating independently.[45] The Russian Foreign Ministry publicly acknowledged on February 15, 2018, that "five Russians may have died" in the incident, revising this estimate on February 20 to "several dozen" Russian and Russian-speaking individuals killed or wounded, while maintaining that none were serving under official Russian command.[63] U.S. Defense Secretary Jim Mattis referenced these assurances in April 2018 congressional testimony, stating that "the Russian high command in Syria assured us it was not their people," underscoring the Kremlin's disavowal as a means to avert escalation.[41] No formal bilateral diplomatic summits or protests ensued directly from the Khasham clash, as both sides prioritized de-escalation through the existing military-to-military framework amid broader U.S.-Russia tensions in Syria.[39] This approach reflected a pattern of proxy-mediated deniability, with Russia leveraging private contractors to probe U.S. "red lines" without triggering direct state-on-state confrontation.[63]

Official Reactions and Statements

United States and Coalition Responses

The United States Central Command (CENTCOM) released an official statement on February 8, 2018, asserting that Syrian pro-regime forces had initiated an unprovoked attack on February 7 against a well-established Syrian Democratic Forces (SDF) headquarters in the Deir ez-Zor region, where coalition advisors were embedded in an advisory capacity.[64] The statement emphasized that the coalition's response consisted of defensive strikes using air and artillery assets to repel the assault, estimating approximately 100 pro-regime fighters killed, with no coalition personnel or SDF losses reported.[64] [65] Prior to lethal engagement, U.S. military officials contacted their Russian counterparts via established deconfliction channels multiple times during the initial phases of the attack, urging them to withdraw the advancing forces; these warnings were issued for approximately 15 minutes before defensive fires were authorized when the threat persisted.[41] [66] Pentagon spokespersons framed the coalition's actions as strictly self-defensive, supporting SDF partners against an unprovoked incursion, and clarified that the strikes targeted pro-regime elements rather than official Russian military units.[65] [67] Coalition leadership, including CENTCOM commander General Joseph Votel, later underscored in congressional testimony that the engagement demonstrated effective deterrence against threats to U.S. and partner forces, while avoiding broader escalation with Russian state actors by distinguishing mercenaries from regular troops.[68] No high-level public statements from President Trump or the State Department directly addressed the incident in the immediate aftermath, with focus remaining on ongoing operations against ISIS.[69] The response reinforced U.S. policy of protecting embedded advisors and SDF holdings in eastern Syria without altering the overall mission parameters.[57]

Russian Government Denials and Justifications

The Russian government initially denied any involvement of its military or citizens in the February 7, 2018, assault near Khasham, asserting that the operation involved only Syrian government forces advancing against U.S.-backed positions.[5] Officials emphasized that Russia had coordinated the Syrian troop movements through established deconfliction channels with the U.S. military, notifying them of an impending advance by pro-regime units, though U.S. accounts disputed the adequacy or specificity of these warnings.[41] Following reports of heavy casualties among Russian nationals, the Kremlin shifted to acknowledging the presence of "citizens of the Russian Federation" in the fighting but framed them as private volunteers or contractors operating independently, without direction from the Russian Ministry of Defense.[63] On February 20, 2018, the Russian Foreign Ministry stated that "several dozen" Russian nationals had been wounded and an unspecified number killed in the clashes, while explicitly ruling out participation by regular Russian troops and attributing the incident to a broader Syrian offensive against terrorist-held areas.[70][71] The ministry reported knowledge of only five confirmed Russian deaths at that stage, contrasting sharply with higher estimates from other sources, and warned the U.S. against escalating tensions by "playing with fire" in Syria.[72][52] Justifications centered on the legitimacy of supporting Syrian regime operations to combat ISIS remnants and reclaim territory, with any Russian casualties portrayed as incidental to private initiatives rather than state policy.[73] Russian spokespeople, including Foreign Ministry representative Maria Zakharova, downplayed the event as an isolated armed clash amid complex ground operations, insisting it did not alter Russia's non-confrontational stance toward U.S. forces and that Moscow had no prior knowledge of mercenary plans to seize the Conoco facility.[74] This position allowed the government to distance itself from the Wagner Group's actions, maintaining plausible deniability while avoiding direct confrontation with the U.S.[1]

Syrian and Allied Regime Positions

The Syrian government, through its state-run Syrian Arab News Agency (SANA), described the U.S.-led coalition strikes on February 7-8, 2018, as a "barbaric aggression" targeting units of the Syrian Arab Army and allied "popular forces" engaged in anti-terrorism operations against ISIS remnants in the Deir ez-Zor countryside near the Conoco gas fields.[75] SANA reports emphasized that the attacked forces were advancing to secure areas from Daesh (ISIS) holdouts, framing the clash as an unprovoked assault by coalition forces supporting "terrorist" elements, rather than a defensive response to an offensive probe.[76] The regime reported dozens of casualties among Syrian military personnel and pro-government militias but avoided detailing the composition of the assaulting force, which independent accounts later identified as including irregular proxies.[77] In a formal letter to the United Nations, the Syrian Foreign Ministry condemned the incident as a "war crime" and "crime against humanity," attributing responsibility to U.S.-backed Syrian Democratic Forces (SDF) for initiating hostilities while accusing the United States of direct sponsorship of terrorism through its occupation of eastern Syrian territories.[78] The statement demanded international condemnation and the withdrawal of foreign forces, portraying the strikes as evidence of Washington's intent to undermine Syrian sovereignty and perpetuate division along the Euphrates River.[79] These claims, disseminated via regime-controlled outlets like SANA, consistently downplayed any provocative advance by Syrian-aligned units and aligned with broader narratives of U.S. imperialism, though they conflicted with coalition evidence of coordinated armored assaults on established SDF positions.[80] Allied regimes, particularly Iran, reinforced the Syrian portrayal through state-affiliated channels, viewing the engagement as an escalation of American efforts to entrench separatist control in resource-rich eastern Syria at the expense of Damascus's authority. Iranian-backed militias, including Afghan Fatemiyoun and Pakistani Zainebiyoun brigades, participated in the pro-regime advance, and Tehran implicitly endorsed the anti-terrorism rationale while decrying U.S. airstrikes as violations of international law.[81] Iranian officials did not issue standalone condemnations specific to Khasham but integrated the incident into critiques of coalition operations as proxy warfare against the "Axis of Resistance," consistent with Tehran's strategic investment in bolstering Assad's control over Deir ez-Zor.[82] This alignment underscored shared regime interests in narrative control, prioritizing sovereignty claims over admissions of proxy miscalculations that risked direct superpower confrontation.

Strategic and Political Ramifications

Implications for Russian Proxy Warfare

The Battle of Khasham on February 7, 2018, underscored the inherent risks of Russia's proxy warfare model, where private military security contractors (PMSCs) like the Wagner Group enable deniability but expose Moscow to uncontrolled escalations when proxies overreach against superior adversaries. Approximately 200-300 pro-regime fighters, including significant numbers of Russian Wagner personnel, were killed in the failed assault on U.S.-held positions near the Conoco gas plant, highlighting the tactical vulnerability of proxy forces lacking air support and advanced intelligence against U.S. combined arms operations involving artillery, airstrikes, and special forces.[83] Russia maintained plausible deniability by disavowing the attackers as non-state actors, avoiding admission of casualties to prevent domestic political fallout akin to the Soviet experience in Afghanistan, yet intercepted communications and survivor accounts linked the operation to Wagner's command structure tied to Kremlin-linked oligarch Yevgeny Prigozhin.[84] This engagement compelled Russia to recalibrate proxy deployments in Syria, shifting Wagner from aggressive frontal assaults to securing resource extraction sites like oil fields, where they could operate with reduced exposure to direct U.S. interdiction. The lopsided outcome—zero U.S. fatalities versus massive proxy losses—demonstrated the limits of deniable offensives against NATO-backed forces, fostering a doctrinal caution against conventional clashes that experts describe as "suicidal" for PMSCs, prompting a pivot toward hybrid tactics such as cross-border raids and information operations in subsequent theaters.[4] However, Khasham did not dismantle Russia's proxy paradigm; instead, it served as a learning curve, enabling Wagner to expand operations across Africa and Ukraine, where they exploited local asymmetries rather than challenging peer adversaries head-on.[85] Broader strategic ramifications included heightened Kremlin sensitivity to proxy miscalculations, fueling later nuclear saber-rattling in Ukraine as a hedge against conventional defeats reminiscent of Khasham, while reinforcing the utility of PMSCs for resource-driven interventions without triggering full-spectrum retaliation. Despite the battle's exposure of proxy fragility—through digital leaks eroding covertness—Russia intensified disinformation to obscure losses and sustain operational tempo, adapting rather than abandoning the model to pursue influence in legally ambiguous spaces.[84][83]

Effects on U.S. Deterrence in Syria

The Battle of Khasham on February 7, 2018, exemplified U.S. commitment to defending positions held by American-backed Syrian Democratic Forces (SDF) in eastern Syria, where approximately 40 U.S. special operations personnel, supported by air and artillery assets, repelled an assault by 200–500 pro-regime fighters, including Russian Wagner Group contractors, resulting in 200–300 enemy casualties and no U.S. fatalities.[41] This disproportionate outcome underscored the efficacy of integrated U.S. combined-arms tactics, particularly close air support from AC-130 gunships, Apache helicopters, and precision strikes, which overwhelmed numerically superior ground forces advancing on the Conoco gas plant near Khasham.[41] The engagement reinforced deterrence by imposing severe costs on challengers, signaling that violations of deconfliction lines—intended to separate U.S.-SDF areas east of the Euphrates from regime-held territory west of the river—would provoke overwhelming retaliation. In the aftermath, pro-regime advances toward SDF oil and gas fields in Deir ez-Zor province halted, with no comparable large-scale assaults on U.S. positions occurring for years, as Moscow and Damascus recalibrated proxy operations to avoid direct escalation.[86] Analysts attribute this to the battle's demonstration of U.S. resolve, which deterred Russian-backed militias from testing red lines again through deniable forces, thereby preserving American freedom of maneuver in counter-ISIS operations and resource-rich areas.[6] Russian official denials of Wagner's involvement, coupled with the group's heavy losses (estimated at dozens killed), highlighted the limits of proxy warfare against U.S. air dominance, prompting a shift toward indirect pressure tactics like artillery harassment rather than ground offensives.[6] Over the subsequent two years, the risk of direct U.S.-Russian clashes in northeastern Syria diminished, as evidenced by stabilized deconfliction protocols and reduced regime probing of eastern Euphrates boundaries, allowing sustained U.S. advisory roles with the SDF without major disruptions.[86] However, deterrence was not absolute; intermittent small-scale incidents, such as unclaimed shelling, persisted, indicating that while Khasham checked ambitions for territorial conquest, it did not eliminate hybrid threats from Iranian- or Russian-aligned irregulars.[86] The event ultimately bolstered U.S. credibility in enforcing no-encroachment zones, contributing to the maintenance of a partitioned status quo in eastern Syria amid broader regime offensives elsewhere.[6]

Internal Repercussions in Russia and Wagner Group

The Battle of Khasham inflicted severe casualties on the Wagner Group, with at least 200 fighters killed and dozens injured during the February 7, 2018, engagement, an event later termed the "Red February Massacre" within Russian circles associated with the PMC.[37] These losses strained Wagner's manpower and operational tempo in Syria, as the group relied on recruited contractors rather than regular forces, prompting internal reassessments of uncoordinated advances against U.S.-protected positions.[5] Yevgeny Prigozhin, Wagner's financier and de facto leader, publicly and privately accused the Russian Ministry of Defense (MoD) of betrayal, claiming officials had assured air cover via Russian Su-25 jets and S-300 systems but failed to intervene after U.S. warnings about the assault were relayed to Moscow through deconfliction channels.[37][56] The MoD's subsequent denial of any Russian involvement—attributing the attack to Syrian proxies—reinforced this perception of abandonment, exposing frictions rooted in the MoD's jealousy over Wagner's battlefield successes and resource control in Syria, such as oil fields.[56] Prigozhin highlighted the lack of honors or support for Wagner's role in prior victories, like Palmyra, further fueling grievances that Wagner leadership viewed as deliberate sabotage.[37] Within Russia, the government's insistence on plausible deniability preserved strategic ambiguity toward the U.S. but isolated Wagner domestically, as official silence minimized public acknowledgment of the deaths and complicated compensation payouts to families, which standard Wagner policy set at up to 5 million rubles per casualty.[37][87] This episode crystallized the PMC's expendable status under Kremlin oversight, curtailing autonomous operations without MoD alignment and laying groundwork for escalating tensions that persisted into Wagner's later activities.[56]

International Perceptions and Media Coverage

Western media extensively covered the Battle of Khasham as a rare direct confrontation between U.S. forces and Russian proxies, emphasizing American technological superiority and resolve in defending positions against an assault by approximately 500 Wagner Group mercenaries on February 7, 2018. Outlets like The New York Times described a four-hour battle involving U.S. special operations troops, artillery, and airstrikes from AC-130 gunships, Apache helicopters, and F-22 fighters, which inflicted heavy casualties—estimated at 200 to 300 killed—on the attackers while suffering no U.S. fatalities.[41] The Guardian reported similar figures, framing the strikes as a response to pro-regime advances violating U.S.-Russia deconfliction agreements, with sources alleging up to 100 Russian nationals among the dead.[88] Such coverage often highlighted the event's novelty as the bloodiest U.S.-Russia clash since the Korean War, underscoring the effectiveness of integrated U.S. firepower in hybrid scenarios.[89] Russian state media minimized the incident, with official narratives denying direct involvement of regular forces and attributing losses to Syrian or allied militias rather than Wagner contractors. The Russian Ministry of Defense claimed no knowledge of the assault and portrayed U.S. actions as excessive, while suppressing casualty figures to avoid domestic backlash.[51] Independent Russian outlets and social media, however, circulated leaked audio recordings of fighters expressing shock and humiliation amid the bombardment, corroborating high death tolls and fueling perceptions of betrayal by Moscow, as Wagner leader Yevgeny Prigozhin later accused the military of abandoning his men.[51] This discrepancy reflected broader Kremlin control over information, where state-aligned sources prioritized narrative control over empirical reporting of proxy failures. Globally, the battle shaped views of Russian private military companies as high-risk tools for deniable operations, with analysts perceiving it as evidence of limits to proxy adventurism against U.S.-backed forces equipped with superior intelligence and air dominance. European and Middle Eastern observers noted implications for escalation risks in Syria, viewing the U.S. response as a deterrent signal against further encroachments east of the Euphrates.[37] Retrospective coverage, including in outlets like Newsweek, linked Khasham to Wagner's evolving role, suggesting the "massacre" deterred direct provocations against NATO while exposing internal Russian frictions that presaged later mutinies.[4] Perceptions varied by alignment, with pro-Western sources lauding U.S. interoperability and pro-Russian ones questioning casualty exaggerations, but consensus emerged on the clash's role in highlighting vulnerabilities in asymmetric engagements.[5]

Long-Term Significance

Lessons on Hybrid Conflicts and PMCs

The Battle of Khasham demonstrated the utility and limitations of private military companies (PMCs) in hybrid conflicts, where state actors employ non-regular forces to pursue objectives while preserving deniability. On February 7, 2018, approximately 500 pro-regime fighters, including Wagner Group contractors, advanced on U.S.-supported Syrian Democratic Forces positions near the Conoco gas plant, probing deconflicted boundaries in Deir ez-Zor. This proxy assault allowed Russia to test U.S. red lines without committing conventional troops, blending irregular ground tactics with regime militias to mask direct involvement. However, U.S. forces responded with integrated firepower, including F-15E strikes, AH-64 Apache helicopters, and MQ-9 drones, destroying nearly all enemy armor and artillery while inflicting 100-300 casualties, predominantly among Wagner personnel, with no U.S. losses.[1][5] A core lesson emerged on PMC vulnerabilities in confronting air-dominant adversaries: Wagner's ground-centric force, lacking effective surface-to-air defenses or real-time state air cover, suffered catastrophic attrition from precision strikes, exposing the fragility of deniable assets absent robust integration. Russian deconfliction channels had warned against the advance, yet the operation proceeded, suggesting either autonomous PMC decision-making or deliberate escalation, which undermined Moscow's narrative control as satellite imagery and survivor accounts confirmed heavy Russian involvement. This highlighted coordination breakdowns inherent to hybrid proxy models, where PMCs operate with semi-independence, prioritizing operational tempo over strategic restraint.[90][56][1] Strategically, the clash underscored that hybrid warfare's proxy layer does not shield sponsors from retaliation, as U.S. doctrine treated PMC-led threats equivalently to state-directed ones, enforcing deterrence through overwhelming response. For PMCs, the engagement revealed dependency on sponsoring states for escalation dominance; Wagner's asymmetric successes in prior Syrian operations faltered against peer-level opposition, prompting no immediate doctrinal shifts but illustrating risks of overreliance on obfuscation in digitized battlefields where exposures via media and intelligence erode deniability. Broader implications include the need for proxies to incorporate anti-access capabilities or tighter command chains to avoid such routs, while affirming airpower's role in resolving ground asymmetries in multipolar conflicts.[5][90][56]

Impact on Subsequent Operations in Eastern Syria

The Battle of Khasham on February 7, 2018, where U.S. and Syrian Democratic Forces (SDF) repelled an assault by roughly 500 pro-Syrian government fighters including Russian contractors, established a strong deterrent against major cross-Euphrates incursions in eastern Syria.[2] Subsequent pro-regime probes were confined to localized clashes and artillery duels rather than coordinated offensives, as the heavy U.S. response—inflicting 200–300 casualties via air and artillery strikes—signaled severe risks for violators of the informal deconfliction line along the Euphrates River.[41][6] This restraint enabled the SDF, backed by U.S. Coalition forces, to prioritize anti-ISIS operations east of the river, including the clearance of the Hajin pocket in December 2018, securing key terrain and resource areas like the Conoco gas plant near Khasham.[5] Pro-regime forces, including Iranian-backed militias and Syrian army units, attempted limited advances, such as seizing two villages near the Iraq border in late April 2018, but U.S. diplomatic and deconfliction efforts quickly halted escalation without direct engagement.[91] Wagner Group's post-Khasham activities in Syria shifted away from direct challenges to U.S. positions, hampered by the battle's exposure of vulnerabilities and ensuing frictions with Russian military command, which had withheld support during the assault.[37][56] Smaller-scale tribal and militia skirmishes persisted in Deir ez-Zor through 2019, often involving local pro-Assad elements testing SDF control, but these lacked the scale or Wagner-led coordination of the February attack, reflecting Moscow's recalibration to avoid broader confrontation.[92] The outcome thus stabilized U.S.-SDF dominance over eastern Syria's hydrocarbon infrastructure, sustaining operations against ISIS remnants amid reduced proxy threats until U.S. troop posture adjustments in 2019.[2]

Broader Geopolitical Shifts

The Battle of Khasham on February 7, 2018, exposed the limitations of Russia's proxy warfare model, as U.S. forces decisively repelled an assault by Wagner Group contractors and Syrian proxies near the Conoco gas plant, resulting in 200-300 attacker casualties without direct Russian military intervention. This incident pierced the Kremlin's plausible deniability, marking the first significant post-Cold War clash between U.S. and Russian-affiliated combatants and straining de-confliction channels between Washington and Moscow.[93][5] The defeat reinforced the Euphrates River as a de facto boundary in Syria, halting pro-regime expansion eastward and securing U.S.-SDF control over key oil and gas fields, which denied economic resources to the Assad regime and its allies. Russian strategy adapted by confining operations primarily west of the river, avoiding repeats of direct tests against U.S. positions equipped with superior air and artillery capabilities.[94] Globally, Khasham highlighted Russian conventional weaknesses against U.S. technological dominance, amplifying Moscow's aversion to symmetric engagements and contributing to an emphasis on nuclear deterrence to offset these disparities, a pattern observed in subsequent crises like Ukraine. The battle's outcome signaled to Iran and other actors the high costs of challenging entrenched U.S. footholds, subtly shifting regional power dynamics toward sustained American leverage in countering hybrid threats from the Russia-Iran-Syria axis.[6]

Related Incidents

Clashes in Deir ez-Zor Province Post-2018

Following the Battle of Khasham, the de facto front line in Deir ez-Zor province between U.S.-backed Syrian Democratic Forces (SDF) east of the Euphrates River and Syrian government-held territory to the west experienced relative stabilization through deconfliction channels, yet low-intensity clashes persisted involving pro-government militias, often Iranian-backed tribal elements probing SDF positions over resource disputes and local control.[95][96] In 2023, SDF forces confronted an insurgency from Arab tribal fighters in Deir ez-Zor, triggered by the arrest of Deir ez-Zor Military Council commander Ahmed al-Khubayl, resulting in weeks of fighting that killed dozens and strained U.S.-SDF relations amid accusations of heavy-handed tactics.[97][98] These tribal groups received support from Syrian government and Iranian proxies, escalating hybrid threats similar to pre-2018 patterns.[96] Tensions intensified in 2025 amid reports of regime advances and failed integration pacts, leading to direct engagements. On August 4, armed groups allied with government forces clashed with SDF units, coinciding with ISIS attacks that killed five SDF fighters at a Deir ez-Zor checkpoint.[99] By August 14, Syrian government troops and unidentified gunmen initiated assaults in areas like Gharanij, sparking intense exchanges with machine guns and mortars; one SDF fighter was killed, three attackers injured, and six SDF members abducted (two later released).[100][101][102] Subsequent incidents included limited machine-gun clashes on September 14 at the Al-Asharah crossing amid heightened tensions.[103] On October 9, government forces conducted a covert incursion in Mazloum Town, prompting intermittent SDF-government firefights.[104] These events, monitored by groups like the Syrian Observatory for Human Rights, underscore fragile ceasefires and persistent proxy dynamics, with casualty figures varying by source due to restricted access but consistently reporting small-unit actions rather than large-scale assaults.[104][103]

Evolving U.S.-Russia Tensions in the Region

The Battle of Khasham exposed vulnerabilities in the U.S.-Russia deconfliction mechanisms established in Syria since 2015, as pro-regime forces, including Russian-linked contractors, advanced across the Euphrates River deconfliction line despite prior warnings through the hotline. U.S. officials notified Russian counterparts via the deconfliction channel during the assault on February 7, 2018, but the attack proceeded, resulting in heavy losses among the assailants from U.S. airstrikes and artillery. Russia officially denied directing the operation, attributing it to autonomous mercenaries, which allowed Moscow to avoid direct accountability while highlighting the risks of proxy forces operating outside state control.[2] In the aftermath, U.S. Central Command reinforced its stance, declaring that any threats to American or partnered forces east of the Euphrates would face overwhelming response, effectively deterring large-scale repeats of the incursion. Russian military overflights into U.S.-controlled airspace persisted at rates of six to eight per day immediately following the battle, but ground probes diminished as Moscow curtailed the autonomy of groups like Wagner to prevent uncontrolled escalations. This incident prompted internal Russian adjustments, including greater oversight of private military contractors, amid broader U.S.-Russia rivalry, yet both sides sustained the deconfliction framework to avert direct superpower confrontation.[2][86] Subsequent years saw episodic frictions, such as Russian patrols approaching U.S. positions in Deir ez-Zor and occasional airspace violations, but no engagements approached Khasham's scale, reflecting a tacit mutual restraint informed by the battle's lopsided outcome. The 2022 Russian invasion of Ukraine intensified geopolitical strains, indirectly affecting Syria by diverting Moscow's resources, yet U.S. troop levels stabilized around 900 in northeastern Syria to counter ISIS remnants and secure oil fields, sustaining pressure on Russian-backed forces west of the river. Deconfliction dialogues evolved modestly, emphasizing collision avoidance over cooperation, as evidenced by ongoing military-to-military channels that prevented miscalculations despite diplomatic freezes.[39][86]

References

  1. American Special Forces Versus Russian Mercenaries in Syria
  2. How US Special Forces took on Wagner Group mercenaries in an ...
  3. Opinion: Inside The Battle Of Khasham In Syria - Aviation Week
  4. How Wagner's Khasham 'Massacre' Hints at Group's Future Role
  5. The Battle of Khasham: Under Cover of Night in Deir Ezzor
  6. How the Battle of Khasham Fueled Russia's Nuclear War Threats in ...
  7. Syria Timeline: Since the Uprising Against Assad
  8. Timeline: the Rise, Spread, and Fall of the Islamic State
  9. Iraq, ISIS and the Syrian War | Regions and Countries - CSIS
  10. US-led coalition forces make decisive gains against ISIS in 2017
  11. Putin's true victory in Syria isn't over ISIS - Brookings Institution
  12. Raqqa: IS 'capital' falls to US-backed Syrian forces - BBC
  13. SDF Begins Raqqa Offensive, Progress Continues in Mosul - War.gov
  14. Mapping the Battle Against ISIS in Deir Ezzor - News Deeply
  15. [PDF] Weekly Conflict Summary November 2-8, 2017 Syrian government ...
  16. Who 'Defeated' ISIS? An Analysis of US and Russian Contributions
  17. Conflict in Syria | Global Conflict Tracker
  18. US-backed SDF says it took Syria's largest gas field from ISIS
  19. U.S.-backed forces capture big gas field in Syria's Deir al-Zor - Reuters
  20. Syria: SDF says it took Conoco gas field from ISIL | News - Al Jazeera
  21. SDF captures Syria's largest gas field | Rudaw.net
  22. https://www.wsj.com/articles/u-s-backed-forces-seize-conoco-gas-plant-from-islamic-state-1506290098
  23. A dangerous escalation in Syria's Deir ez-Zor - Middle East Institute
  24. [PDF] Weekly Conflict Summary – October 12-18, 2017 | The Carter Center
  25. US-backed SDF Says it Took Syria's Largest gas Field From IS - VOA
  26. [PDF] The Russian Air Campaign in Syria, 2015 to 2018 - RAND
  27. Syrian army claims it has broken years-long Isis siege on Deir ez-Zor
  28. Battle of Deir ez-Zor & Raqqah September & October 2017
  29. Russia's Battlefield Success in Syria: Will It Be a Pyrrhic Victory?
  30. Russia bombed location where US troops were present | CNN Politics
  31. A Hollow Victory over the Islamic State in Syria? The High Risk of ...
  32. SDF take control of Syria's largest oil field - Rudaw
  33. Syria's largest oil field captured by US-backed forces - CNN
  34. U.S.-allied force captures Syria's largest oil field from ISIS - CBS News
  35. ? What is the Strategic Importance of Deir ez-Zor and Could It Cause ...
  36. Who Benefits from a U.S. Oil Deal in Northeast Syria?
  37. Syria is where the conflict between Wagner and the Russian ...
  38. Details Of U.S. Engagement With Russian Mercenaries In Syria ...
  39. Collision Avoidance: The Lessons of U.S. and Russian Operations ...
  40. The Puzzle of Russian Behavior in Deir al-Zour - War on the Rocks
  41. How a 4-Hour Battle Between Russian Mercenaries and U.S. ...
  42. Battle of Khasham (Feb 7, 2018): US and Russian Forces (Wagner ...
  43. The Battle Of Khasham: How Outnumbered US Forces Defeated ...
  44. 'The Battle of Khasham' saw US troops rout Russian mercenaries in ...
  45. Wagner recounts US air strikes during Battle of Khasham - AeroTime
  46. That Time US Forces Tore Hundreds of Russian Wagner Group ...
  47. The Battle of Khasham: When Russians Fought Americans and Lost ...
  48. Combat Controller got secret Air Force Cross for 2018 Syria battle
  49. https://www.newsbreak.com/war-history-online-1745274/4299464664928-about-200-enemy-casualties-were-reported-from-the-first-deadly-clash-between-the-u-s-and-russia-since-the-cold-war
  50. US massacre of Syrian troops threatens to unleash wider war - WSWS
  51. Report: Leaked Audio of Russians on Humiliating Defeat by US Forces
  52. 'Dozens' of Russians injured in US airstrikes in Syria, ministry ... - CNN
  53. Russia admits 'several dozen' of its citizens killed in Syria fighting
  54. It All Started at Khasham - Elections Daily
  55. 'A Total F***up': Russian Mercenaries in Syria Lament U.S. Strike ...
  56. How the Wagner Group Lost Syria | Royal United Services Institute
  57. Syria war: US bombs government forces after Deir al-Zour attack - BBC
  58. https://sana.sy/en/?p=126670
  59. US-led air raids in Syria 'kill 100 pro-Assad fighters' - Al Jazeera
  60. Syria Condemns U.S. Airstrike as Tensions Rise
  61. Documenting Equipment Losses During The Battle Of Conoco Fields
  62. Was the battle in Khasham, Syria in February 2018 where the US ...
  63. Russia's Mercenary Debacle in Syria | Foreign Affairs
  64. Unprovoked attack by Syrian pro-regime forces prompts Coalition ...
  65. Pentagon Official Describes Response to Attack by Pro-Regime ...
  66. How That Massive Battle Between US Troops And Russian ...
  67. U.S. Troops With Syrian Rebels Come Under Attack, But No ... - NPR
  68. Pro-Assad fighters attack US-backed forces, coalition advisers
  69. US-led coalition strikes kill pro-regime forces in Syria | CNN Politics
  70. Russia admits dozens of Russian casualties in Syria battle - BBC
  71. Russia Admits to 'Dozens' of Casualties in Syria Clashes
  72. Russia Warns U.S. Not to 'Play With Fire' in Syrian Conflict
  73. Russia Says 'Several Dozen' Wounded In Clash With U.S.-Led ...
  74. Zakharova Downplays Armed Clash with Americans in Syria ... - VOA
  75. The international coalition aggression on Deir Ezzor affirms US low ...
  76. US-led coalition launches aggression against popular forces fighting ...
  77. U.S. troops may be at risk of 'mission creep' after a deadly battle in ...
  78. TSC IntelBrief: The U.S. Hits Back in Syria - The Soufan Center
  79. Syria: US supporting terrorism after airstrikes | World | postguam.com
  80. Klintsevich: Targeting popular forces fighting Daesh in Deir Ezzor ...
  81. Battle of Khasham | Military Wiki - Fandom
  82. US military says strikes in Syria targeted 'Iranian backed groups'
  83. Wagner Operations in Syria: A Legacy of Profit, Power, and Decline
  84. Decoding the Wagner Group: Analyzing the Role of Private Military Security Contractors in Russian Proxy Warfare
  85. Five Years After a Disastrous Syria Battle, Wagner Is More ...
  86. US-Russia standoffs in northeast Syria: Just getting started
  87. Families of Dead Wagner Mercenaries Paid $60,000, Creating Cash ...
  88. Scores of Russian mercenaries reportedly killed by US airstrikes in ...
  89. The battle in Syria that looms behind Wagner's rebellion
  90. [PDF] Superpower Hybrid Warfare in Syria - DTIC
  91. Pro-Regime Syrian Forces Take Control Of At Least Two Villages ...
  92. Non-international armed conflicts in Syria - Rulac
  93. The Risks of Russia's Proxy Warfare Strategy - New America
  94. The Battle of Khasham
  95. The SDF's Insurgency Challenge in Deir ez-Zor
  96. Eastern Syria After Assad
  97. Deir ez-Zor torn between Arab tribes' struggle for independence and ...
  98. Clashes between Arab tribes, SDF forces in Syria pose challenge to ...
  99. Violence Resurges in Syria After Armed Groups, Kurdish-Led SDF ...
  100. Clashes break out in Deir az-Zour between Syria govt troops, SDF
  101. Deadly Clashes and Abductions in Deir ez-Zor as Tensions Escalate ...
  102. Clashes Between Syrian Ministry of Defense Forces and the SDF in ...
  103. Tension grows at Al-Asharah crossing | Limited clashes erupt ...
  104. Clashes erupted between SDF and military formations of Syrian ...
User Avatar
No comments yet.