Site Map Facebook Twitter Youtube Instagram VKontakte Odnoklassniki
Home  < Mission in Syria  < More

Tu-95MS bombers fired cruise missiles at terrorists’ objects in Syria

Today, at 12:06 a.m., Tu-95MS bombers fired cruise missiles at objects of international terrorist groupings in Syria.

The aircraft scrambled from the Engels airfield and flew over territories of Iran and Iraq.

In the Syria airspace, the strategic bombers fired Kh-101 cruise missiles at the most important ISIS and Jabhat al-Nusra objects located in the provinces of Deir ez-Zor and Idlib.

The unexpected strikes eliminated terrorists’ command posts, hardware and manpower concentration areas as well as ammunition depots.

The objective monitoring data has confirmed elimination of all assigned targets.

Su-30 and Su-35 fighters were covering the Tu-95MS bombers.

The strategic bombers successfully flew about 7,000 kilometers. They were in-flight refueled by Il-78 tanker aircraft.

The missile strikes were carried out against the ISIS objects in order to support offensive of the Syrian Arab Army to eliminate the last terrorists’ bridgehead.

It is to be stressed that all the targets were located out of settlements and in a safe distance from strongholds of the US SOF and Syrian Democratic Forces in the ISIS-controlled territories.

Latest air photos of Deir ez-Zor area demonstrate these objects.

In order to ensure security of the American troops and Kurdish formations, the Russian party will not specify locations of these strongholds.

Though, it is to be stressed that the images clearly show that there are no engagements at the former ISIS strongholds occupied by the US SOF units.

There are no bomb carters neither of artillery nor aircraft strikes. Moreover, as it can be seen, no elementary security is organized, even more defence.

Considering the two-year experience that Russian special forces received when operating behind the terrorists’ lines, one can question with whom and against whom the US SOF has been fighting in Syria.

So far there has been no substantiated explanations regarding the issue.

ServerCode=node2 isCompatibilityMode=false