Moldova’s airspace closure confirmed a Russian drone hazard. A near collision remains unproven.

A real incursion with physical evidence

Moldovan police recovered fragments with a propulsion system and features resembling Russia’s Geran family of attack drones. Investigators also found a crater and continued examining the wreckage to determine whether it carried an explosive payload. Those findings support the attribution of the intrusion to weapons used by Russia in its war against Ukraine. They do not depend on statements about Zelenskyy’s itinerary.

A later Romanian response shows how similar uncertainty shapes operational decisions in the region. On 10 September, Romanian radar detected a group of aerial targets near Snake Island, prompting a public alert and the launch of two Spanish F-18s and a Romanian helicopter. This later event does not prove what happened around Zelenskyy’s plane. It shows that aerial activity near the Ukraine–Romania border can require operational decisions before an object’s route and identity are fully known.

Where the near-hit account outruns the evidence

On 9 September, Norwegian Prime Minister Jonas Gahr Støre said Zelenskyy’s plane was “almost hit” by a drone. Reuters reported that Støre did not explain how close the drone came to the aircraft. The published account included no radar plot, minimum separation, altitude comparison or precise sequence linking the drone to the presidential flight.

Moldova’s own public account supports a delay caused by a precautionary closure. It does not publicly confirm a near collision. The Associated Press reported that the crashed drone was found about 160 kilometres from Chișinău airport. That distance cannot exclude danger at an earlier point on the drone’s route. It does show why the claim requires synchronized tracks rather than inference from the crash site or the fact that Zelenskyy was due to depart.

Moldova had enough evidence of danger to stop flights, but the public record contains no distance or track data showing a near collision. The distinction matters because “airspace closed during a Russian incursion” and “a drone nearly hit the president’s plane” describe different levels of evidence. Treating them as interchangeable makes later corrections look like denials of the incursion itself.

“Moldova had enough evidence of danger to stop flights, but the public record contains no distance or track data showing a near collision.”

What would settle the claim

The missing evidence is specific. Authorities would need to publish synchronized radar tracks for the drones and Zelenskyy’s aircraft, their altitudes, the minimum horizontal and vertical separation, and the time at which the presidential flight began taxiing or took off. Air-traffic-control logs could show whether the plane was still on the ground when the closest approach occurred. Evidence of targeting would require more, such as a route change toward the aircraft, recovered guidance data or intelligence connecting the drone’s mission to Zelenskyy.

Russia’s responsibility for creating the danger does not depend on proving that stronger claim. The incursion occurred during Russia’s ongoing aggression against Ukraine, and a separate Russian drone attack on 9 September killed two people at the Starokozache crossing on the Ukraine–Moldova border. Kremlin spokesman Dmitry Peskov later denied any danger to Zelenskyy’s aircraft and alleged a Ukrainian provocation. He offered no evidence, while Moldova had wreckage and multiple operational confirmations of the incursion.

The 8 September closure establishes a credible Russian-drone hazard to civilian aviation and shows that Moldova had reason to suspend flights as a precaution. The evidence released so far cannot support claims of a near collision or deliberate targeting. Synchronized radar and flight records showing minimum separation would justify the first judgment, while technical or intelligence evidence of deliberate guidance toward the aircraft would justify the second.