Four Moscow airports restricted flights. Reopening did not settle the disruption.

Four airports: every main civilian gateway to Moscow restricted flights on October 23, 2026, amid a reported drone raid. The disruption reached aircraft arriving in the Russian capital and those waiting to leave. At Sheremetyevo, passengers were told to take shelter. Restrictions were subsequently reported lifted, but that did not establish that journeys—or airport schedules—were back to normal. ^{47 48}

The affected airports were Sheremetyevo, Domodedovo, Vnukovo and Zhukovsky. Reports described substantial delays and cancellations, although the available counts cannot be assembled into a reliable final total. By the morning of October 24, there was still no clear airport-by-airport account of how long restrictions lasted or whether the backlog had cleared. ^{1 5 7 48}

That distinction is the practical heart of this episode. Permission to resume flying is one milestone; getting stranded passengers moving and restoring a timetable is another. The reopening reports establish the former, not the latter.

Russia’s civil aviation authority, Rosaviatsiya, announced restrictions on arrivals and departures at 2:05 p.m. Moscow time, according to The Kyiv Independent. That is an announcement time, not a verified simultaneous start at all four airports. TASS and aviation outlet AeroTime also reported restrictions across the capital’s airport network on October 23. ^{1 47 4}

At Sheremetyevo, Moscow’s largest airport, an air alert brought instructions for waiting passengers to shelter. The reported 5 p.m. all-clear concerned that alert. It cannot safely be used as the end of the flight restrictions, much less as the time of the first subsequent landing or departure. ¹

Subsequent accounts described Sheremetyevo and Zhukovsky returning to normal operations, with check-in resuming at Sheremetyevo. Vedomosti reported that restrictions had been lifted across all four airports, while also saying Vnukovo and Domodedovo were accepting and dispatching flights by agreement with the relevant authorities. Those qualifications matter: authorized aircraft movements are not the same as an unrestricted timetable. ^{46 48}

The exact lifting times and first resumed-flight times remain unestablished. Nor was there a fresh, dated October 24 operating bulletin in the available record to show whether the previous day’s disruption had worked its way out of the system. A report of reopening should not be stretched into an assurance that every airport had recovered. ^{46 48}

One daytime snapshot reported 150 delayed flights across the four airports: 75 at Vnukovo, 35 at Sheremetyevo, 31 at Domodedovo and nine at Zhukovsky. MiraNews put Vnukovo’s count at 75 by 3:30 p.m., after an earlier update had listed 29. These were successive snapshots, not separate batches to add together. ⁵

A later 360.ru report described more than 340 delays across Moscow’s airports. Without an established precise counting window or airport breakdown, that figure indicates broader disruption but does not supply a final accounting. It also cannot simply be added to the earlier 150. ⁷

Sheremetyevo’s cancellation figures need particular care. The Kyiv Independent reported 85 cancellations and 229 delays over the day, attributing the numbers to Flightradar24. But the dated underlying tracker archive, exact snapshot time and counting definitions were not established. The numbers are reported daily disruption figures, not a verified tally of flights affected solely by this restriction period. ¹

NGS, in an October 23 report timestamped 22:12, listed 55 cancelled arrivals and 60 cancelled departures at Sheremetyevo—115 cancellations combined—as current figures. That differs from The Kyiv Independent’s 85. The two accounts have not been reconciled and may cover different snapshots or counting scopes; the later publication is not enough to establish a like-for-like revision. ^{3 1}

The responsible conclusion is substantial travel disruption, not one definitive number. There is no comparable verified full-day cancellation-and-delay total for each of the other three airports, and no basis for turning these flight counts into an invented passenger toll or financial loss.

The military account is less settled than the operational one. Moscow Mayor Sergey Sobyanin was reported as saying air defenses had shot down 17 drones heading toward the city. CGTN and Moskovsky Komsomolets carried that claim on October 23. It remains an official interception claim, not an independently verified tally. ^{13 15}

A separate report on Moscow’s official city website, displayed at 2:45 p.m. Moscow time, gave 19. Yet the later-published MK and CGTN accounts still carried a two-hour total of 17. The original message sequence was not established, so these accounts cannot safely be turned into a clean progression from 17 to 19. Publication lag or different counting windows could explain the difference; the available record does not settle it. ^{14 15 13}

The city report also said emergency personnel were working where debris fell. It did not identify those locations as Sheremetyevo. Photographs circulated online alleging drone debris on the airport’s tarmac, but The Kyiv Independent said it could not independently verify them. An illustrative airport photograph dated July 28, 2025, likewise cannot document this October 23 incident. ^{14 1}

No independently verified airport impact, physical damage or casualties were established. That is not proof that none occurred. It is a limit on what can be claimed: shelter instructions and flight restrictions demonstrate a response to a perceived threat, not that a drone successfully struck an airport. ^{1 47}

Russian officials described the drones as Ukrainian. Ukraine had not commented when the initial account was published, and no acknowledgement of this specific episode was located through 7:38 a.m. UTC on October 24. Responsibility therefore remained independently unresolved, even as the flight disruption was plainly documented. ¹

The wider aviation risk had already been raised on September 1, when Ukrainian President Volodymyr Zelensky warned airlines, insurers and governments that “Russian skies are becoming completely dangerous.” He also said Ukraine did not threaten civil aviation, while urging carriers serving Moscow, St. Petersburg and other major hubs to factor in drone risks. That warning provides context, not an admission of responsibility for October 23 or authentication of the alleged debris photographs. ¹