Reported Ukrainian 493-Drone Raid Disrupts Four Moscow Airports, Vnukovo Over Eight Hours

A reported wave of 493 Ukrainian drones disrupted all four major Moscow airports overnight on October 13-14, with Vnukovo reportedly closed for more than eight hours. Russian media outlet Astra said passengers there were required to leave their aircraft as restrictions also affected Sheremetyevo, Domodedovo and Zhukovsky.

The scale comes from Moscow Mayor Sergei Sobyanin and has not been independently verified. Sobyanin said 493 uncrewed aircraft flew toward the Moscow region between 8:30 p.m. and 7 a.m., while most were neutralized on distant approaches and another 180 were destroyed while approaching Moscow. It is not clear how the figure of 180 relates to the broader total. Earlier updates from the mayor had reported interceptions of 20 drones and then 30 more.

Whatever the final aircraft count, the confirmed public-facing issue is broader than the fate of individual drones: a warning spanning the metropolitan area removed landing and departure capacity from an entire four-airport network. That is a significant civil-aviation consequence even under the Russian account that most of the aircraft were stopped before reaching the city.

Why an interception claim does not prevent airport disruption

Airport restrictions are precautionary measures, not a scorecard of how many drones reach a destination. Civil operators need sufficiently predictable airspace for departures, approaches and missed-approach options. During an extended warning, uncertainty about where and when aircraft may be operating can be enough to suspend movements, regardless of later claims about interception success.

The four affected airports also function as a network rather than isolated runways. When several hubs become unavailable together, controllers and airlines have fewer nearby options for absorbing traffic. Aircraft may remain at their departure points, hold only when operationally appropriate, or use alternate airports. The supplied account does not establish what happened to each flight, but Vnukovo’s reported passenger disembarkations show that the restrictions reached aircraft already in the boarding or departure process.

Reopening airspace does not instantly rebuild a schedule. Aircraft and crews may no longer be where an airline planned to use them, while accumulated departures must compete for available slots. Refueling, passenger handling and crew-duty limits can prolong disruption after restrictions end, although none of those constraints has been specifically documented for the October 13-14 event.

Repeated closures turn readiness into a scheduling problem

The latest interruption was not an isolated operational pattern. Russian airports temporarily closed 993 times during August, averaging 32 closures per day, according to aviation-security data reported by Euronews. Across the summer, 2,182 closures were recorded, already exceeding the total for all of 2025.

Moscow’s four airports had also imposed temporary restrictions during a separate drone warning on October 9. Vnukovo was then the most affected airport, with more than 40% of its flights delayed and another 10% canceled, according to reporting based on regulator and flight-tracking information. Those earlier figures should not be applied to the latest event, but they illustrate how recurring warnings can consume airport capacity even without a documented impact on airport infrastructure.

This repetition changes the readiness burden. Airports and airlines must manage not only a single closure but also the possibility that aircraft positioning, crew availability and passenger processing will be disturbed again. For airspace authorities, the task combines civil traffic management with military air-defense activity over a densely served region. The safe operating response can therefore impose costs even when defensive systems perform as officials claim.

The numbers remain less certain than the airport consequence

A wave measured in hundreds would indicate substantial drone production and deployment capacity, but Sobyanin’s 493-aircraft figure remains an attributed Russian claim. TASS described the operation as among the largest attacks on Moscow and its surrounding region in two years, yet the lack of independent confirmation and the unclear relationship between the 493 and 180 figures—limits conclusions about the raid’s exact scale or interception rate.

The airport impact is more concrete: all four major Moscow hubs temporarily restricted operations, and Vnukovo reportedly remained unavailable for more than eight hours. That gap between claimed defensive success and prolonged civil disruption is the event’s central systems consequence. Air defense may reduce physical damage, but it cannot by itself preserve normal airline operations while the airspace threat remains unresolved.

By Stephen Wallace — Editor for AMI’s aerospace integration and unmanned mobility coverage, focused on drone manufacturing, VTOL systems, autonomous networks, and air-ground mobility links.