Drone Strikes Zelenskyy Plane Amid Takeoff

A drone incursion in Moldova shut the sky and delayed President Volodymyr Zelenskyy’s flight—then Norway’s prime minister said the plane was almost hit.

Story Snapshot

Norway’s prime minister said Zelenskyy’s aircraft nearly got hit by a drone.
Moldova closed its airspace due to a drone threat, delaying Zelenskyy’s takeoff.
Moldovan police reported a Russian drone crashed in-country the same day.
A Ukrainian presidency source called the near-hit claim exaggerated.

What Officials Said And What Actually Happened

Norwegian Prime Minister Jonas Gahr Støre told a public broadcaster that Zelenskyy’s plane “was almost hit by a drone” during takeoff from Moldova. Major outlets relayed his on-the-record claim the same day. Moldovan authorities, meanwhile, closed national airspace due to a drone alert and delayed several departures, including Zelenskyy’s. They reopened after the threat cleared. Those facts establish a drone hazard and a delay. They do not, by themselves, prove a measured near-collision distance.

The drone that temporarily closed airspace in Moldova and caused the delay of a flight carrying President Zelenskyy has been identified as a Shahed. This information was provided by the Ministry of Defense of Moldova to Suspilne. – REPORTS

— CGTN Europe (@CGTNEurope) September 10, 2026

Police in Moldova reported that a Russian drone crashed in a sunflower field in Riscani district that day, sparking fires and prompting restrictions. That detail links a real object to the alert timeline. It also explains why airspace managers hit pause. From an aviation-safety view, closing airspace when an uncooperative drone is near flight paths is standard risk control. Pilots cannot see every drone. Controllers cannot predict every track. You shut the door first; you sort the details after.

The Dispute Over “Almost Hit”

Ukraine’s presidency pushed back through a sourced comment to reporters, calling the danger claim exaggerated and framing the event as an air alert rather than a near-strike on the presidential jet. Another secondary report surfaced a conflicting Ukrainian-source account that said the drone nearly hit the plane. That leaves a split: a Norwegian leader describes a close call; a Ukrainian source downplays it; a separate Ukrainian source echoes the close-call idea. None of these public accounts release radar plots, cockpit logs, or tower tapes.

Common sense says weigh claims against hard anchors. The anchors here are the airspace closure, the delayed departure, and the confirmed drone crash inside Moldova. Those prove a real safety event. The exact separation between drone and aircraft remains unverified in open sources. Calling that gap “almost hit” needs data. American conservative values prize clear evidence and accountability. Officials should publish declassified logs to settle the distance question and shut down spin—from any side.

Why This Matters For European Air Safety

Moldova has faced repeated Russian drone intrusions that threaten civil aviation, according to prior reporting on cross-border strikes and airspace violations. These episodes create chaotic, fast-moving windows where a single error can turn deadly. Heads of state draw special risk because their routes and timing can be predictable. When national managers close airspace, flights stack up, costs rise, and confidence drops. That is not theater; it is the rational price of keeping jets and people alive.

Policy should now chase three fixes. First, radar, air traffic, and airport operations logs for that departure window should be reviewed and, as security allows, released. Second, Moldova and neighbors need layered drone defense tied directly to civil aviation procedures, not just military alerts. Third, communications discipline must improve. One leader’s vivid line can race ahead of data and hand opponents an easy wedge. Facts beat slogans. Show the tracks, mark the time stamps, and let the numbers speak.