Published on: 2026-05-08
Source: Government of the Russian Federation
An important disclaimer is at the bottom of this article.
President of Russia Vladimir Putinheld an emergency meeting with the permanent members of the Security Council. At the meeting, Vice Prime Minister Vitaly Savelyev informed the President about the restoration of air traffic in the south of Russia after the attack by Ukrainian drones.
As reported, on the morning of May 8, 2026, strikes were carried out on the building of the regional air traffic control center of the Russian Federation in Rostov-on-Don.
“After the air traffic service strike procedures were carried out in accordance with the emergency and contingency action plan and were handed over to the aerodrome control centers. Thanks to the security services, the personnel were evacuated to the bomb shelter, there are no casualties. The extent of the damage and additional information are being clarified,” emphasized Vitaliy Savelyev.
The following 13 airfields in the Rostov zone were closed: Astrakhan, Volgograd, Vladikavkaz, Gelendzhik, Grozny, Krasnodar, Mayachkala, Magas, Mineralnye Vody, Nalchik, Sochi, Stavropol, Elista. Currently, work is being organized with reserve workplaces, and a safety assessment is being conducted.
Instructions have been given to airlines regarding the adjustment of flight schedules, the cancellation of flights, and the necessity of working with passengers. Instructions have also been given to airports and airlines on organizing bus and railway transportation as alternative means of evacuating citizens.
“Within literally two to three days, we will fully restore air traffic in the Rostov zone. From 13:00, communication has resumed with the 13 aerodromes listed above with a reduced flight frequency. All passengers have been notified, and work at the airport is conducted with passengers systematically,” noted Vitaliy Savelyev.
Please note; This information is raw content obtained directly from the information source. It represents an accurate report of what the source asserts and does not necessarily reflect the position of MIL-OSI or its clients.