NATO Eastern Flank developments — 4 October 2026
A week in which the flank's response changed more than its record of entries. Russian drones struck three times in September beside the Yahodyn–Dorohusk crossing, the last on 28 September — close to NATO territory but, by Poland's own account, never inside it. Polish fighters flew, two airports closed and an air-attack alert went to Lublin province. The same day Poland's deputy defence minister announced that pilots and commanders would no longer need to see a target before engaging it: radar, other sensors and data from Ukraine would be enough. The change was reported to apply from 1 October as a military procedure, with no published order and no change in law. Romania confirmed one drone entry, on 27 September, and found an explosive drone on its soil near Brăila with no entry on its radar, which this module holds rather than counts. Estonia attributed August's arson at a defence-robotics firm to Russian special services and summoned Russia's chargé d'affaires. The United States rotations announced for Lithuania and Estonia had not arrived by the end of the window.
The developments
Poland announced it would stop requiring visual identification before engaging aerial objects, after Russian drones struck beside the Dorohusk crossing without entering Polish airspace
On the evening of 28 September a Russian jet-powered drone struck on the Ukrainian side of the Yahodyn–Dorohusk border crossing. Poland's Operational Command said a Russian drone had again come down near the crossing. Poland's defence minister said it hit about two kilometres from the crossing, inside Ukraine, and that there was no violation of Polish airspace. Ukrainian regional authorities said the blast damaged a checkpoint building at the terminal entrance; Ukraine's border guard said the crossing itself was undamaged. Polish fighters flew in Polish airspace, ground-based air defence was brought to readiness, Lublin and Rzeszów airports suspended operations, and an air-attack alert for Lublin province was issued and withdrawn. Drones had also struck near the same crossing, on Ukrainian territory, on 13 and 17 September. Also on 28 September, Deputy Defence Minister Cezary Tomczyk announced that the peacetime requirement to identify a target visually before engaging it would be replaced by positive identification from radar and other sensors, flight parameters, the absence of a friend-or-foe reply and data provided by Ukraine. The decision rests with the pilot or the Operational Commander. The defence minister was reported on 30 September and 1 October as saying the procedures were ready and would apply from 1 October. They are set at military level; no order has been published and no law was changed.
Why it matters. Of everything near the flank this week, this is the only change to a standing response, and it is national, not NATO's. It changes how quickly a Polish decision to engage can be taken, not what Poland may engage, and it adds to rather than alters the alliance air defence mission that replaced Baltic Air Policing in August. The strikes are recorded as what they were: Russian action close to NATO territory. None was an entry into NATO airspace, and none enters this module's airspace series. What the change does not establish is any engagement under the new rule. A published instrument, or a first engagement under the rule, is the evidence that would show how it works in practice.
- Poland to ease rules for shooting down drones, missiles entering from Russia
- Poland changes rules of engagement for firing on foreign aircraft amid growing Russia threat
- Poland implements new response rules for air defence amid Russian attacks on Ukraine from 1 October
- Russian drone strikes near Yahodyn border crossing with Poland
- Alert RCB na Lubelszczyźnie. DORSZ: dron rozbił się niedaleko polskiej granicy, po stronie Ukrainy
- Poland sounds air attack alert over Russian drone
Romania confirmed a drone entry on 27 September and found an explosive drone near Brăila two days later with no entry on its radar
Romania's defence ministry stated that on the evening of 27 September an aerial target entered Romanian airspace through the Ceatalchioi area, moved along the border and was lost from radar after about ten minutes near Somova, in Tulcea county. Two F-16s took off and an RO-Alert went to the county. On 29 September the ministry reported that an object had fallen in the night on farmland near Gropeni, in Brăila county. Its team found a crater and fragments of a drone whose explosive charge had detonated on impact. The ministry also stated that its radar had reported no unauthorised entry that night. On the night of 29–30 September Spanish fighters on enhanced air policing took off for a target east of Izmail that did not enter Romanian airspace. On 2 October a possible drone fell at Plauru, in Tulcea, and again no entry was detected.
Why it matters. The 27 September case continues the most frequent pattern in the uncrewed series, at the Danube frontier. Gropeni is the harder case: a drone on Romanian soil that the state's own radar did not see enter. No record in this series rests on debris alone against a stated radar negative, so it is held and named rather than counted. The series now holds twenty records, eleven of them Romanian. What these cases do not establish is origin or intent. No release states either, and none brought an Article 4 request.
Estonia attributed August's arson at a defence-robotics firm to Russian special services and summoned Russia's chargé d'affaires
On 29 September Estonia's foreign minister, Margus Tsahkna, said it could be concluded with certainty that the fire at a Milrem Robotics building in Tallinn on the night of 14–15 August was sabotage ordered by the special services of the Russian Federation. The ministry summoned Russia's chargé d'affaires. Three Latvian citizens detained in Latvia in August were handed to Estonia and are in custody. No charge has been published. The Kremlin rejected the accusation.
Why it matters. This module measures hybrid pressure by how far each case climbs toward an established finding, and how long it takes. Most of its cases took many months to reach an official attribution, if they reached one at all. This one reached a government attribution about six weeks after the fire, before any charge. A government's attribution is its stated position, not a court's finding, and it is national, not collective. Whether a court reaches the same conclusion is what would establish it at the highest rung.
Where this fits
This is one conflict's dated review for the week. The cross-conflict edition for the same week carries the most consequential findings from every conflict Vigil covers. The standing picture this review updates is the NATO Eastern Flank coverage. How Vigil grades, dates and sources its claims is set out in the methodology, and anything later found wrong is recorded in the corrections log.
By email Get Vigil’s Weekly Briefs and new Analytical Notes by email. What Vigil Dispatch sends
← Previous NATO Eastern Flank brief — 2026-09-27Every NATO Eastern Flank review All weekly briefs