Reports of the overnight October 13–14, 2026, drone attacks include two headline figures: Moscow Mayor Sergei Sobyanin said 493 drones headed toward the Moscow region, while Russia’s Defense Ministry claimed its forces downed 902 drones across a wider area. Those figures describe overlapping geographic scopes, and the available reporting does not independently verify either total.
11
14
21
What was claimed about the drone numbers?
Sobyanin said the 493 drones were headed toward the Moscow region between 8:30 p.m. on October 13 and 7 a.m. on October 14. He said most were neutralized at distant approaches and 180 were destroyed as they neared Moscow. His reported statement did not give a separate exact count for the drones handled at distant approaches.
1
21
Separately, Russia’s Defense Ministry claimed that air defenses downed 902 Ukrainian drones overnight. TASS reported that the claim included areas across Russia and the waters of the Sea of Azov; Prensa Latina’s summary of the ministry’s statement also listed Crimea. RBC-Ukraine described the attack as spanning 20 Russian regions. These are separate reported descriptions of a broad attack, not figures that should be added to the Moscow-bound count.
4
6
11
14
The totals remain claims attributed to Russian officials. The sources available here do not provide independent verification. One report characterized the Moscow-region attack as among the largest in two years, but that comparison also relies on reported figures.
11
Moscow airports suspended operations
Restrictions affected all four airports serving Moscow: Vnukovo, Domodedovo, Zhukovsky and Sheremetyevo. TASS reported that operations resumed at 6:44 a.m. Moscow time on October 14.
11
Charter97 reported more than 500 delayed or canceled flights and said Vnukovo was closed for more than eight hours. NV reported that passengers were taken off planes at Vnukovo, citing independent monitoring channels. These reports describe disruption, but the available sources do not establish the full impact across every airport or confirm other specific flight claims.
9
20
Reported damage and casualties
In Balakovo, Saratov region, reports described damage to residential buildings. Meduza said the regional governor initially reported one death as preliminary information; that account should be understood as an official report, not an independently established casualty count.
21
23
A Sberbank data center in the region was also reported to have been targeted. TASS said Sber confirmed the attack on the data center and reported that the company’s systems and services were operating normally.
11
For Moscow itself, Meduza reported that no damage or casualties had been reported at the time. That is not the same as independently confirming that none occurred.
21
The Rostov-on-Don oil-terminal fire
A separate fire at an oil-loading terminal in Rostov-on-Don was reported after a drone strike on October 10. Militarnyi identified the site as the oil-loading terminal of the Novoshakhtinsk Oil Refinery.
33
On October 14, The Moscow Times reported that the fire was continuing for a fourth day and that another storage tank had exploded late on October 13. Citing monitoring channels and the outlet Astra, it reported that the blaze had spread to eight of the terminal’s 12 tanks.
30
The Moscow Times also described the terminal as formerly known as Yug Rusi. Later, Militarnyi reported on October 15 that the fire had been extinguished.
30
26
Taken together, the reporting supports a clear distinction: Sobyanin’s Moscow-bound total and the Defense Ministry’s nationwide figure were official claims; airport restrictions and the terminal fire were reported by multiple outlets; and some specific impact details remain uncertain or were reported only provisionally.