At 03:40 GMT on Thursday, Polish radar picked up an incoming cruise missile over Lublin province. Within minutes an F‑16 fighter was launched to visualise the target, reaching the vicinity of the impact site at 03:46 GMT.

The missile, later identified as a Russian Kh‑101, struck a field near the village of Tarnawa‑Kolonia, about 90 km from the Ukrainian border. The impact created a crater but caused no injuries; the warhead landed roughly two kilometres from the nearest dwellings.

Identification and official reaction

Prime Minister Donald Tusk said fragments recovered from the crater matched the profile of a Kh‑101, a long‑range, low‑observable cruise missile used by the Russian Air Force. He told reporters: "All indications point to a Russian Kh‑101," while noting that the defence ministry had not yet disclosed whether the missile had been launched from Russian‑occupied Ukrainian territory or from Russia itself.

The F‑16 pilot reported being prepared to engage the threat. The commander of the aircraft later recounted that he was "ready to give the order to fire" but held fire because the missile’s trajectory steered it away from populated areas.

Six‑minute decision window

The episode illustrates the narrow time‑frame commanders face: detection at 03:40, scramble within minutes, and impact at 03:46. In that six‑minute interval the operational commander had to assess the missile’s path, weigh the risk of collateral damage from an interceptor, and decide whether to fire.

Polish officials framed the outcome as a correct judgement – the missile landed on empty farmland, sparing civilian lives – but also highlighted a gap between detection capability and the time required for threat assessment and authorisation.

Broader NATO context

The incident follows a series of Russian aerial incursions on NATO’s eastern flank, including a Geran‑2 drone strike on an apartment block in Galaţi, Romania, earlier this year. Romania responded by expelling the Russian consul‑general in Constanţa, whereas Poland’s response centred on technical attribution before moving to accountability.

Tusk warned that Moscow would likely try to distance itself from responsibility, echoing alliance concerns after the Romanian episode, where online narratives attempted to portray the drone attack as a staged provocation.

Analysts argue that European air‑defence systems need a cheaper, low‑cost layer to deal with inexpensive threats such as drones and cruise missiles, reserving expensive interceptors for high‑value targets. The EU’s SAFE loan programme, which recently funded Romanian air‑defence contracts, is part of a wider effort to modernise the continent’s shield against asymmetric aerial attacks.

Poland’s experience also underlines the importance of tighter de‑confliction with Ukrainian forces operating near the border, to avoid mis‑identification or delayed communication that could increase the risk of friendly fire or missed interceptions.

Looking ahead

In the coming weeks the Polish government is expected to publish a detailed report on the incident, outlining procedural gaps and recommending reforms. The findings will feed into NATO’s ongoing assessment of eastern‑flank readiness as Russia continues to test response times with low‑observable, high‑speed weapons.

While the ability to quickly name a weapon type has improved, the six‑minute window in which a commander must decide to fire remains a critical vulnerability. Enhancing real‑time data sharing, automating parts of the threat‑assessment process and expanding low‑cost air‑defence assets could narrow that gap. For now, the Tarnawa‑Kolonia incident serves as a reminder that detection alone does not guarantee protection.