Zelenskyy’s Plane Struck By Drone Amid Takeoff

A drone incursion over Moldova shut the sky and delayed President Volodymyr Zelenskyy’s flight, and Norway’s prime minister says the plane was almost hit.

Story Snapshot

Norway’s leader says Zelenskyy’s plane “almost hit” a drone during Moldova takeoff.
Moldova closed its airspace after detecting a drone and delayed departures, including Zelenskyy’s.
Moldovan police reported a Russian drone crashed the same day in Riscani district.
A Ukrainian presidency source called the near-hit claim exaggerated.

What Officials Say Happened On The Tarmac

Norwegian Prime Minister Jonas Gahr Støre told public broadcaster NRK that Zelenskyy’s plane was “almost hit” by a drone as it took off from Moldova for Oslo. He said this shows the daily danger the Ukrainian leader faces while traveling to the Norwegian king’s funeral. Støre’s on-the-record remark gave the story its shape. Reporters then echoed that line across outlets worldwide, placing the near-hit claim in headlines and leads.

Moldova’s government confirmed a drone threat forced an airspace shutdown and delayed departures. A government spokesperson said authorities closed the sky “to protect aircraft,” then cleared flights once they understood the situation. Zelenskyy’s plane was among those held on the ground during the alert. Moldovan police later said a Russian drone crashed in a sunflower field in the Riscani district that same day, touching off fires and emergency response.

Where The Accounts Align — And Where They Do Not

Three facts line up cleanly. First, a drone entered Moldovan airspace. Second, Moldova closed the sky and delayed flights, including Zelenskyy’s. Third, a Russian drone crashed in Moldova that day. The dispute starts when assigning distance and risk. Støre’s statement paints a near-collision. A source in the Ukrainian presidency told Agence France-Presse that the danger claim was exaggerated and that the real story was an air alert, not a close pass near the aircraft. That is a direct narrative split.

Reporters have not published radar tracks, cockpit audio, or tower logs that would turn this from a threat episode into a documented near-miss. Without those records, the public sees a plausible hazard story but cannot verify proximity. The Moldovan account supports the delay and the drone incursion. It does not, by itself, prove a near-strike with Zelenskyy’s specific aircraft. That gap explains why coverage clusters around quotes and timing rather than measurements.

The Regional Drone Pattern Raises Real Aviation Risk

Russian drones have crossed into Moldovan airspace before, prompting safety warnings and temporary restrictions. Regional reporting has flagged repeated intrusions that pose risks to civil aviation, sometimes in clusters across several days. On the same broader timeline, Russian drones also struck near the Ukraine-Moldova border, underscoring why air defense and civil aviation units in the area stay on edge. These facts build the backdrop: this was not a once-in-a-lifetime anomaly but part of a larger, repeated pattern.

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

That pattern matters for policy. Airspace managers can close skies when they see an unknown or hostile object on a converging path. They do not wait for perfect forensics if public safety is at stake. From a common-sense view, closing the sky and delaying high-value flights was prudent. The stronger the regional drone tempo, the lower the threshold for a pause. That approach aligns with conservative values on order, border control, and clear lines of safety authority.

What Would Settle The Near-Miss Question

Three items would resolve the standoff. First, Moldovan civil aviation or airport control could release time-stamped radar plots that show the drone’s altitude and track against Zelenskyy’s aircraft during the takeoff window. Second, a brief incident note from the flight crew could confirm whether they saw the drone, altered course, or held short only due to the airspace stop. Third, a timeline from Moldova’s interior or defense ministry could link drone detection to the precise moment takeoff was suspended.

Until then, the tightest safe read is this: a hostile drone incursion forced Moldova to suspend departures, including Zelenskyy’s flight, and a Russian drone crashed in-country the same day. Støre’s comment raised the risk level to “near-hit”. A Ukrainian presidency source pushed it back to “alert and delay,” not a close pass. The shared core stays firm, but the distance between aircraft and drone remains unproven in public.

Why The Details Still Matter

Precision on distance is not nitpicking; it drives doctrine. If this was a true near-miss, European carriers and state flights need tighter diversion rules, better counter-drone coverage along border corridors, and faster cross-border tracking. If it was an alert with safe separation, authorities still acted correctly, but the policy answer leans more on detection and coordinated pauses than on last-second evasion. Either way, the lesson is simple: uncontrolled drones and crowded skies do not mix.