...
On Saturday, various Arabic media reported that a fierce battle took place between the Syrian army and IS forces that were trying to seize Jabal Turdah from the south. The coalition strike took place that same day, and although U.S. military accounts are unclear about whether the Syrian forces were regular army personnel or irregulars, the result was unmistakable: the regime contingent withdrew from the position after the strike, which allowed IS to seize it. To be sure, the victory was only temporary, since the army retook Jabal Turdah the next day thanks to huge reinforcements from Damascus and intense regime and Russian airstrikes. But the incident nevertheless highlighted the fragility of Assad's position in Deir al-Zour -- and of the recent U.S. "cessation of hostilities"
deal with Russia, which may be unraveling amid reports of renewed regime bombing in the Aleppo area.
According to the U.S. Central Command (CENTCOM) statement issued after the operation, "Coalition forces believed they were striking [an IS] fighting position that they had been tracking for a significant amount of time before the strike." But the statement raises several questions. For one, how did the coalition mistakenly bomb a fixed position of the Syrian army? Jabal Turdah has been continuously occupied by the army with the exception of January-March 2016, when IS briefly seized it. CENTCOM also stated that "the location of the strike is in an area the coalition has struck in the past," but its past statements make it difficult to confirm this. For some months -- including in recent weeks -- the coalition has officially announced a number of strikes "near Deir al-Zour," but exact locations have generally not been given; in at least one case where information was made available, the location was more than ten miles from the site struck Saturday. More important, the coalition has never intervened in the regime vs. IS battle for Deir al-Zour before, so why would it begin to do so this weekend?
...