Moldova: NATO airspace breached, two jets up, nothing stopped
On the afternoon of 8 September a Russian long-range attack drone crossed out of Ukraine, flew through Moldovan airspace, entered Romanian - and therefore NATO - airspace south-east of Iasi, and was tracked across five Romanian counties. Two Spanish Air Force F-18s on NATO air-policing duty were launched within two minutes. The drone was not intercepted. It went back into Moldova and exploded on the ground.
Moldova closed its airspace and the aircraft carrying President Zelenskyy, which was at Chisinau airport, took off late. Norway's prime minister later said the aircraft had been almost hit. The Moldovan government's own account puts the crash about 160 kilometres from the airport, and has the aircraft leaving 55 minutes after Romanian radar last held the drone.
↓ Download one-page brief (PDF)About 16:20 - Moldova detects it
Moldovan military radar picks up an unidentified uncrewed aircraft in Moldovan airspace. Moldova closes its airspace after about 16:30. Three departures and four arrivals are delayed.
16:33 to 16:37 - into NATO airspace
Romanian radar holds the target west of Chisinau at 16:33. At 16:37 it enters Romanian airspace south-east of Iasi. RO-Alert warnings go to Iasi and northern Vaslui, then Neamt at 16:44, Suceava at 16:53 and Botosani at 16:56.
16:39 - two F-18s launch
Two Spanish Air Force F-18s lift from 57th Air Base Mihail Kogalniceanu under NATO enhanced Air Policing. No engagement follows.
16:48 to 17:02 - across Romania and out
The target is tracked 18 km north of Roman at 16:48. Romanian radar loses contact at 17:02 on the Iasi-Botosani boundary. It is reacquired over Moldova at about 17:08 and the Romanian alert is lifted at 17:33.
After 17:20 - it explodes on the ground
The drone comes down and detonates near Mihailenii Vechi in Riscani district, northern Moldova. Moldova lifts its flight restrictions. Confirmation is published about 18:30.
17:57 - the presidential aircraft departs
Zelenskyy's aircraft leaves Chisinau for Norway, delayed by about an hour. Two days later the Norwegian prime minister tells NRK the aircraft was almost hit by a drone as it was about to take off.
Poland
Nineteen drones crossed into Polish airspace in a single night and NATO aircraft engaged. Reported by Scorpius.
Estonia and Romania
Airspace violations and a device recovered in a Romanian field by a resident. Reported by Scorpius as the Estonia and Romania spillover.
Tulcea
A drone that Romanian radar did not see, reported by a resident. Reported by Scorpius.
Moldova and Romania
A Geran-4 crosses two states, is pursued by two F-18s, and is not engaged.
The pattern in this file is not that incursions happen - they have happened for three years and will keep happening. It is that the published record now contains several cases in which the alliance knew, launched, and still did not stop the object. That is a statement about the match between the threat and the equipment held against it, and it does not improve because the intent behind any individual flight is disputed.
The airspace violation is established; the near-miss is not
A NATO member's airspace was entered by a Russian munition, and the Romanian defence ministry has published the times. The near-miss claim came from a third country's prime minister two days later. Moldova's own government confirmed a delayed departure, not a danger, put the crash about 160 km from the airport, and Romanian radar had lost the drone 55 minutes before the aircraft left the ground. A Ukrainian source told AFP the danger had been exaggerated. On the published timings the aircraft and the drone were not close in time or in space, and reporting that treats "almost hit" as an established fact is repeating one statement rather than the record.
Being disputed is not the same as being harmless
Nothing above reduces what happened. A hostile munition capable of carrying 50 to 90 kilogrammes of explosive flew through the airspace of an alliance member, over a populated region, and was not brought down. The correction is to the drama, not to the seriousness.
Deliberate targeting is open, and the evidence for it is thin so far
It is a realistic possibility that the flight was routed to coincide with the presidential movement, on the strength of the timing, Ambassador Kulminski's point that jet-powered drones do not casually wander into Moldova, and the difficulty of accepting the coincidence at face value. It is no higher than that on the public record: nothing published shows a track towards the airport, and the Moldovan government has not made that claim.
The interception problem is now demonstrated, not theorised
It is almost certain that fast, cheap, jet-powered one-way attack drones will keep penetrating this airspace, given the volume in use against Ukraine and the geography of the border. It is likely that fighter-based air policing continues to fail to engage them, because an F-18 is an expensive and poorly matched answer to a 450 kg airframe. The counter is ground-based, layered and cheap per engagement, and it is not presently in place along this frontier.
Where this goes
It is highly likely that further incursions into Romanian and Moldovan airspace occur within weeks. It is a realistic possibility that a head-of-state or senior movement in the region coincides with one again, because the movements are frequent and predictable and the munitions are numerous. It is unlikely that the intent behind this particular flight is ever established publicly.
Romania confirmed the airspace violation, the times and the scramble. Moldova confirmed the airspace closure, the delayed departures and the crash site 160 km from the airport. Norway's prime minister said the aircraft was almost hit. The Kremlin said there was no threat. A Ukrainian source said the danger had been exaggerated. Only the first two are accounts by the states that held the radar picture, and only those two should carry weight in a brief.
- Separate the airspace fact from the aircraft story before you brief either. One is on the record with timings from a defence ministry. The other is a claim by a third party that the two governments involved have not made.
- Plan aviation movements in this region around closure, not interception. The realistic effect on a flight is an hour on the ground and a closed corridor. Build the delay into itineraries and have a hold plan for principals at regional airports.
- Do not assume a scramble means a solution. Fighters launched in two minutes here and achieved nothing. If your contingency assumes air policing removes the threat, it assumes something the published record does not support.
- Treat public alerting as part of the impact. RO-Alert reached five counties. Anyone running sites, staff or events in that footprint needs a standing answer to what people should do when the phone alarm goes off, because it will go off again.
- Predictable movements are the exposure. Whatever this particular flight was aimed at, senior travel through this corridor is announced, routine and geographically constrained. That is a planning problem for protection teams irrespective of attribution.
- https://www.euronews.com/my-europe/2026/09/10/timeline-how-a-russian-drone-nearly-hit-zelenskyys-plane-in-moldova
- https://www.euronews.ro/articole/o-drona-s-ar-indrepta-spre-iasi-dupa-ce-ar-fi-survolat-chisinaul-mesaj-ro-alert-i
- https://hotnews.ro/ce-spune-chisinaul-despre-avionul-lui-zelenski-care-aproape-a-fost-lovit-de-o-drona-2346009
- https://www.digi24.ro/stiri/externe/moldova/chisinaul-confirma-ca-avionul-lui-volodimir-zelenski-risca-sa-fie-lovit-de-o-drona-rusa-in-republica-moldova-3942195
- https://ziare.com/zelenski/vizat-drona-romania-moldova-2034678
Compiled from open-source reporting for professional security discussion. This is a protective-security lessons-learned assessment, not an operational account. The airspace violation, the scramble and the crash are confirmed by the Romanian defence ministry and the Moldovan government. Whether the drone was directed at or near the presidential aircraft is disputed and unresolved: the near-miss account is the Norwegian prime minister's, given to NRK two days later; the Moldovan government confirmed a delayed departure rather than a danger; a Ukrainian source told AFP the danger had been exaggerated; and the Kremlin said no threat existed. The type identification as a Geran-4 and its performance figures are from Ukrainian open-source monitoring reported by Euronews, not from an official technical assessment. Dates differ across sources - the incident is dated 8 September here on the Romanian defence ministry and Moldovan government accounts, while some reporting gives 9 or 10 September, the days of disclosure. The crash village is absent from the mapping data and is not plotted; the four plotted points are the radar track as published, not the flight path.