A Kh-101 exposed Poland’s firing gap

At 03:40 on July 30, Polish radar operators spotted an unidentified object moving west through their airspace. An F-16 scrambled. By 03:46, the object had vanished from screens (TVN24, RMF24). It had already hit the ground near Tarnawa-Kolonia in the Lublin region. Prosecutors later identified the debris as a Russian-made Kh-101 cruise missile (Rzeczpospolita).

No one was hurt. But those six minutes have become the sharpest test yet of a problem running the length of NATO's eastern flank: allied systems can spot incoming threats, but turning detection into a lawful, tactically safe firing decision fast enough to stop them remains unsolved.

The order to fire depended on where the missile was heading

Poland was already on high alert. During Russia's overnight barrage against Ukraine, the Operational Command had activated fighters, ground-based defences, radar and early-warning aircraft (MON). Earlier that night, around 03:29, a separate object had approached within five kilometres of the border before veering east (Radio PiK). The system was already watching. The breach still happened.

Defence minister Władysław Kosiniak-Kamysz told parliament that the general who commands Polish military operations, Ireneusz Nowak, had authority to order a shootdown — if the trajectory threatened populated areas (MON). Prime Minister Tusk held the same line: the missile would have been destroyed if it had kept flying toward cities (France 24). It crashed in open terrain. No shot was fired.

The decision window may have been even tighter than those six minutes suggest. According to deputy defence minister Cezary Tomczyk, cited by Polish media, a Ukrainian pilot chased the missile but turned back about 20 seconds before the Polish border. The pilot pulled away because crossing into NATO airspace while armed risked triggering Polish defences (Interia). No separate statement from Warsaw, NATO or Kyiv confirmed this account. If accurate, it means the last chance to destroy the missile before it entered Poland collapsed seconds before the border.

Romania changed the law. Its pilots started shooting down intruders.

The gap is not unique to Poland. Romania spent months collecting Russian drone fragments from border fields before its military began firing at intruders. The shift came after a February 2025 law explicitly authorized the armed forces to destroy drones illegally entering Romanian airspace (Adevărul). Since then, Romanian F-16s have intercepted targets near the Black Sea coast and inland (AP, Ziarul Financiar). Even then, Romania's army chief acknowledged one case where pilots visually identified a Shahed drone but could not engage. The army did not explain which conditions failed (Bursa).

The Baltics are drawing the same conclusion. NATO's Baltic Air Policing mission, where rotating allied jets scramble to identify unknown aircraft over Estonia, Latvia and Lithuania, is being upgraded into a full air defence mission with broader rules of engagement (the standing instructions that tell pilots when they may fire) (ERR, LRT). Estonian defence minister Hanno Pevkur said pre-authorisations would reduce the need to call capitals before pulling the trigger (ERR).

German analyst Nico Lange told ZDFheute that roughly 95 kilometres of penetration without interception exposed the limits of eastern-flank air defence (ZDFheute). NATO secretary general Mark Rutte called the breach a reckless consequence of Russia's war, and the alliance activated air and ground defences in coordination with Warsaw (Al Jazeera, Deutschlandfunk). That coordination came after the missile hit the ground.

Poland's internal review will determine whether the firing rule — shoot only if the trajectory threatens cities — protected civilians or left Poland dependent on where the missile happened to fall. Romania answered a version of that question for drones by rewriting the law. The Baltics are rewriting their rules now. Poland owes its allies the same clarity about what happens in the next six minutes.