Updated daily at 09:00 (EET) Index 5.1 = 0.0 elevated
Issue of October 11, 2026 · SundayNo. 131

Poland, evening: aircraft were up, the command closed the episode with no violation, and Lublin and Rzeszów airports paused

5.1/10 elevated = 0.0vs. previous issue
In this issue ▾
  1. Top stories of the day
  2. By area, in detail
  3. Contradictions and discrepancies
  4. Escalation risk assessment (0–10)
  5. Sources

Issue of 11 October 2026 — for the period 10–11 October 2026.

Note: On Saturday evening Poland's Operational Command had aircraft up because of strikes on western Ukraine and closed the episode with the line that no violation of Polish airspace was observed; Lublin and Rzeszów airports paused for that interval. On the night into Saturday and the night into Sunday the Government Centre for Security sent two alerts to the same two voivodeships and cancelled both with the line that there was no threat on Polish territory; no separate command sentence was found for those two nights. Russia's defence ministry lists of 560 drones overnight into Saturday and 78 during the day do not include the northwest. No full overnight list for Sunday morning had been found at compilation. (Previous issue — 10 October 2026, risk 5.1/10.)


Top stories of the day

  1. 10.10 — Poland, evening: aircraft were up, the command closed the episode with no violation, and Lublin and Rzeszów airports paused. TVN24 (10.10, 18:41, updated 19:44) writes that shortly after 18:30 the Government Centre for Security (RCB) sent an alert to Lublin and Podkarpackie voivodeships: "Russian air attack on the territory of Ukraine. The situation is being monitored. Polish aircraft are operating in Polish airspace." After 19:40 the centre sent the cancellation: the attack on Ukraine had ended and there was no threat on Polish territory. TVN24's lead says no violation of Polish airspace was recorded. The same text says the Operational Command reported that the actions tied to protecting the air during strikes on targets in Ukraine had ended; in an earlier command note aircraft were operating, the step was preventive and aimed at protecting Polish airspace, especially next to the threatened areas. The Polish Air Navigation Services Agency, per TVN24, said after 18:40 that Lublin and Rzeszów airports had temporarily stopped operations to give military aviation room, and later that they had resumed. RMF24 (published 18:55, updated 19:51) quotes the command's closing note: military aviation had stopped operating, ground air-defence and radar systems had returned to ordinary duty, and "no violation of the airspace of the Republic of Poland was observed." RMF24 places the RCB cancellation before 20:00 and also writes that the agency reported the airports stopping. Onet (10.10, 18:35) carries the command's earlier line: ground air-defence and radar systems were brought to readiness, and the actions were preventive. ⚠️ Discrepancy on the minute of the cancellation: TVN24 says after 19:40, RMF24 says before 20:00. It is one evening episode. The "no violation observed" sentence is in the command quotation at RMF24 and in TVN24's lead. TVN24 calls this the second alert of Saturday. No shot is described in these texts. Sources: TVN24 (10.10.2026, 18:41); RMF24 (10.10.2026, 19:51); Onet (10.10.2026, 18:35).

  2. 10–11.10 — Two other RCB alerts, with no separate command sentence; the 10 October issue did not see Saturday's midnight episode. Polsat News (10.10, item from 05:41, updated 07:00) writes that around midnight on the night from Friday to Saturday the RCB sent the same text about Polish aircraft operating to Lublin and Podkarpackie, and before 07:00 the cancellation "there is no threat on Polish territory." lublin112 (10.10, 07:58) gives the same two formulas and the same hours. The gov.pl page of 10.10 carries both formulas without clock times. Polsat's headline says the military scrambled fighters; the body quotes the RCB, not the Operational Command. TVN24's evening text calls the midnight alert the first of Saturday and says it was cancelled before 07:00. No separate command note with the sentence "no violation was observed" was found for that night in the pages read. The night into Sunday: Polskie Radio 24 (11.10, 05:56) writes that after midnight the same alert went to the same two voivodeships and was cancelled about 30 minutes later with the same formula. Polsat News (11.10, 05:48) writes "at midnight" and "a little over half an hour later." The gov.pl page of 11.10 carries both formulas without clock times. Polsat adds that this was the third warning in a few hours and that command communiques accompanied the evening attacks, without naming a separate Sunday command text. ⚠️ Discrepancy: "around midnight / after midnight" and "about 30 minutes / a little over half an hour." The RCB cancellation says there is no threat on Polish territory; it is not the command's verbatim formula. The 10 October issue wrote that no new alert dated 9 or 10 October had been found. The midnight episode was already at Polsat by 07:00 and at lublin112 by 07:58, and that issue cites Fontanka at 07:51. That is an omission. The evening episode appeared after the morning compilation and is not an error of that issue. Sources: Polsat News (10.10.2026, 07:00); lublin112 (10.10.2026, 07:58); gov.pl — alert of 10.10; Polskie Radio 24 (11.10.2026, 05:56); Polsat News (11.10.2026, 05:48); gov.pl — alert of 11.10.

  3. 10.10 — Overnight into Saturday: 560 drones; the daytime: 78; the northwest is on neither list. Interfax (10.10) carries the defence ministry: from 20:00 Friday to 08:00 Saturday, 560 Ukrainian UAVs were intercepted over Belgorod, Bryansk, Volgograd, Voronezh, Kaluga, Kursk, Lipetsk, Oryol, Penza, Rostov, Samara, Saratov, Smolensk, Tambov and Tula oblasts, the Moscow region, Crimea, and the Sea of Azov and the Black Sea. Kommersant (10.10, 12:13) repeats the same hours, the same number and the same list. Leningrad oblast, Pskov, Kaliningrad and St Petersburg are not on it. 560 is one ministry figure in two newsrooms, not two counts. It closes the overnight list that the 10 October issue did not yet have at its morning compilation: Kommersant appeared at 12:13. The day: Interfax (10.10) carries the ministry that from 08:00 to 20:00 Moscow time 78 UAVs were destroyed over Tver, Belgorod, Bryansk, Kursk, Kaluga, Tula, Oryol and Smolensk oblasts and the Moscow region. Fontanka (10.10, 21:21) gives the same list and writes that the daytime wounded were in Belgorod oblast (at least 11) and Kursk (two, including a man who opened a munition himself). 78 is one ministry figure. The northwest is absent. The wounded are named outside the Baltic northwest. RIA Novosti (ria.ru) — EU-sanctioned outlet, no direct link; the same daytime ministry text reached us through Interfax and Fontanka. Sources: Interfax — 560 (10.10.2026); Kommersant — 560 (10.10.2026, 12:13); Interfax — 78 (10.10.2026); Fontanka — 78 (10.10.2026, 21:21).

  4. 11.10 — Sunday morning: no full overnight list; the partial notes name Rostov, Sochi and Vladimir, not the northwest. No full defence-ministry text for the night from Saturday into Sunday had been found at compilation. Interfax (11.10) and Kommersant (11.10, 07:30) carry Rostov oblast governor Yuri Slyusar: about 50 UAVs were destroyed and suppressed overnight over Kamensk, Novoshakhtinsk and nine districts, nobody was hurt, and dry grass burned in Bokovsky district. Fontanka (11.10, 07:41) and Kommersant (11.10, 07:50), citing the Krasnodar krai operational headquarters, write that UAV fragments fell on the territory of Sochi airport, a fire in an administrative building was put out and nobody was hurt; debris also fell in a private-house area and at hotels. Interfax (11.10), citing Yandex's press service, writes that the data centre in Vladimir was stopped after an attack and that nobody was hurt. Fontanka (11.10, 06:52) carries the same company note and adds, citing governor Alexander Avdeev, a fire in the suburb, two substations cut and 5,000 residents without power, plus evacuation of the nearest houses; the same text says Yandex service failures are also being recorded in St Petersburg. Rostov, Sochi and Vladimir are not the Baltic northwest. About 50 is the governor's figure, not a ministry list. The 5,000 residents, the evacuation and the St Petersburg outage are one Fontanka text: that is not a strike on the city and not a drone over Leningrad oblast. The hours after Sunday morning are not closed. Sources: Interfax — Rostov (11.10.2026); Kommersant — Rostov (11.10.2026, 07:30); Fontanka — Sochi (11.10.2026, 07:41); Kommersant — Sochi (11.10.2026, 07:50); Interfax — the Vladimir data centre (11.10.2026); Fontanka — Vladimir (11.10.2026, 06:52).


By area, in detail

Construction of military sites and fortifications

  • No new kilometre of the Baltic Defence Line, of ditches, of dragon's teeth or of Tarcza Wschód sections, dated 10–11 October, was found.
  • No new report of a completed section after Kuldlabidakene ended on 9 October was found. That drill stays in the previous issue.

Deployment and movement of forces

  • The Kaliningrad border. No new primary text of 10–11 October naming duty posts or a new headcount beyond LRT's 9 October lead was found. The company in that wording stays in the previous issue. No Russian movement toward that border, dated 10–11 October, was found in non-registry sources.
  • Zemessardze, 10–11.10. No new report on the course of the 1st Riga Brigade drills in Ropaži, Ķekava and Bauska, beyond the National Armed Forces announcement of 9 October, was found. The figure of about 30 remains the municipal note of 9 October. This is not a move to a border.
  • Ādaži. No text of 10–11 October on the firing, beyond the Auseklis note of 9 October, was found. Confirmation on mil.lv is still absent. One source does not become a fact of this window.
  • Ämari, Spanish EF-18Ms. ERR (10.10, 11:25) writes that four EF-18Ms left Ämari on 9 October, after five weeks, and that Turkish aircraft remain at the base; the same piece gives about 110 people and more than 200 hours. That is one feature. ⚠️ Discrepancy on the end date: the EMAD staff on 1 October already wrote that the Ámbar detachment had completed the mission and that the aircraft were returning. The 1 October page is older than this window and does not confirm a departure on 9 October specifically. No second newsroom of 10–11 October with a 9 October departure date was found. It does not enter the score as an established withdrawal on 9 October.
  • The CSTO in Belarus. No text of 10–11 October on the contingent, beyond the press-centre note of 9 October, was found. The exercises are still announced for 12–16 October and, in the October text that was read, have not started. No topic page is opened.
  • Steadfast Duel 26 and Perkūno griausmas 2026 continue on the previously named dates through 15 October. No new dated episode for 10–11 October was found.
  • Zapad-2026 is not being held. Ussisõnad-2026 is not independently confirmed.

Agreements and spending

  • No newly signed interstate agreement and no new defence budget, dated 10–11 October, was found.

Military aid and air defence

  • Poland, three episodes (items 1 and 2). Saturday evening is closed by the command's sentence that there was no violation. The two nights are closed by RCB cancellations. No violation of the airspace of Lithuania, Latvia or Estonia for 10–11 October was found in the texts read.
  • 560 and 78 (item 3). The northwest is absent. Sunday morning's list is not closed (item 4).
  • Nyan, Tapa. ERR (10.10) retells Postimees: British Army spokesperson Melissa Terry said the Nyan drones were brought for this year's Spring Storm exercise and have already been used in Estonia. The English Postimees page is 9 October, 11:43. The range is "over 250 km", a single-use BAE Systems aircraft, with Estonian launchers Ely PL80 and Threod CATA BT. The Estonian Postimees original is dated 8 October, earlier than the day before yesterday, and is not a fresh source. ERR is a rewrite, not a second count. The text does not claim an arrival in the 10–11 October window. The range is one speaker. It does not enter the score as a new delivery this weekend.

Kaliningrad and Russia's border regions

  • The lists (items 3 and 4). The northwest is absent from the closed lists of 560 and 78. It is also absent from Sunday's partial morning texts. The Yandex outage "including in St Petersburg" is one newsroom and not an intercept over the city.
  • No Russian movement toward the Lithuanian border and no new note on Kaliningrad for 10–11 October was found. No new NATO reply to the earlier note was found in this window.
  • Belarus. No new incident on the Latvian or Lithuanian border, dated 10–11 October, was found. The CSTO exercises have not started in the text that was read.

Statements by officials

  • Polish Operational Command, evening of 10.10 (quotation at RMF24): operations have ended, systems have returned to ordinary duty, no violation of Polish airspace was observed. The earlier line at Onet and TVN24: the step was preventive.
  • RCB, 10.10 and 11.10: Polish aircraft are operating in Polish airspace; then, the attack on Ukraine has ended and there is no threat on Polish territory.
  • Y. Slyusar, 11.10: about 50 UAVs over Rostov oblast, nobody hurt. The region is outside the coverage.
  • Yandex press service, 11.10: the Vladimir data centre is stopped, nobody hurt.
  • A. Avdeev via Fontanka, 11.10: a fire, two substations, 5,000 residents, evacuation of the nearest houses. One text.
  • M. Terry via Postimees / ERR: Nyan was brought in the spring. One speaker.
  • ERR, 10.10: four EF-18Ms left on 9 October. One feature; the completion date differs from the EMAD page of 1 October.

⚠️ Contradictions and discrepancies

  • Omission in the 10 October issue. That issue wrote that no new scramble and no new RCB alert dated 9 or 10 October, apart from the Thursday evening episodes of 8 October, had been found. That was already incomplete at compilation: around midnight on 10 October the RCB sent an alert to Lublin and Podkarpackie, and before 07:00 cancelled it with "there is no threat on Polish territory" (Polsat News, updated 07:00; lublin112, 07:58; gov.pl of 10.10). The issue cites the morning Fontanka of 07:51, so the reading window already reached those pages. There is no separate Operational Command sentence "no violation was observed" for that night: Polsat's headline about fighters being scrambled is wider than the body, which quotes the RCB. The evening episode around 18:30 appeared after the morning compilation and is not an error of the 10 October issue. The 5.1 score for 10 October is not recalculated: the class of event (an alert with a cancellation, and no named violation) was already holding the reading all week. The entry is in corrections.json.
  • The minute of the evening cancellation. TVN24: alert shortly after 18:30, cancellation after 19:40. RMF24: cancellation before 20:00. Onet records the alert at about 18:30. It is one episode, not two.
  • The hours of Sunday night. Polskie Radio 24: after midnight, cancelled about 30 minutes later. Polsat: at midnight, a little over half an hour later. The RCB formulas match. Polsat attributes the command communiques to the evening attacks, not to Sunday morning.
  • 560 and 78. Each number is a defence-ministry text in two newsrooms, not two censuses. The northwest is on neither.
  • Ämari. ERR of 10 October dates the departure of four EF-18Ms to 9 October. EMAD on 1 October writes that the mission was already complete and the aircraft were returning. There is no second text of 10–11 October with the date 9 October. The 9 October withdrawal is not presented as established.
  • Nyan. ERR rewrites Postimees. The English page is 9 October, the Estonian original is 8 October. The arrival is placed in the spring, not this weekend. The range is one speaker.
  • Rostov, Sochi, Vladimir. About 50 and "nobody hurt" agree at Interfax and Kommersant via the governor; the region is outside the coverage. The 5,000 residents and the service outage in St Petersburg are only in Fontanka. That is not a strike on the Baltic northwest.
  • No other substantive error in previous issues, of the kind that has to be entered in corrections.json, was identified.

📊 Escalation risk assessment (0–10): 5.1 / 10

Score: 5.1 / 10. Unchanged from the 10 October issue. The nearest historical analogue is the tense late-Cold-War standoff (≈3–4), with a premium for the drone shoot-down over Lithuania on 15 September, for strikes close to the Polish border in earlier windows, and for the nuclear-coloured rhetoric around Kaliningrad in earlier issues. Clearly below Able Archer 1983 (≈7) and the eve of 2008/2014 (≈6–7): Saturday evening is closed by the command's sentence that no violation was observed; the other two nights are closed by RCB cancellations; the northwest is absent from the lists of 560 and 78; no declared mobilisation and no shot at a Baltic border were found in this window.

Drivers on the Russian side and its ally:

  • Strikes on western Ukraine on the evening of 10 October — the reason the Polish command itself gave for putting aircraft up. No separate count of the means of attack is in the Polish texts that were read.
  • The night into 10 October — 560 drones on the ministry list, the northwest absent.
  • The day of 10 October — 78 from the same ministry, the northwest absent. The wounded are named in Belgorod and Kursk oblasts.
  • Sunday morning, 11 October — the full list is not closed. Rostov, Sochi and Vladimir lie outside the Baltic northwest. The service outage in St Petersburg is one newsroom and not an intercept.
  • No new movement toward the Lithuanian border, no new note on Kaliningrad and no new text on the CSTO exercises for 10–11 October was found. The exercises are still ahead, 12–16 October.

Drivers on the NATO side and among individual members:

  • Saturday evening in Poland — preventive aircraft activity and readiness of ground systems, then a close with no observed violation. The pause at Lublin and Rzeszów airports was temporary: TVN24 writes that operations resumed.
  • Two RCB alerts — the night into Saturday and the night into Sunday, both with a "no threat" cancellation. There is no command sentence for those nights.
  • ERR on four EF-18Ms leaving on 9 October — one feature, and the date differs from the EMAD text of 1 October. It does not enter the score as a withdrawal.
  • Nyan — a spring delivery retold on 9–10 October, not a new unit this weekend.
  • No new decision to close the Gulf of Finland and no new headcount on the Lithuanian border was found in this window.

Mutual / structural factors:

  • The Russia–Ukraine war remains the background of the Polish alerts and of both lists.
  • No mobilisation announcement was found in a non-registry Russian source for 10–11 October.
  • No communication channel and no new agreement on one was announced in the window. No nuclear deployment and no new nuclear note on Kaliningrad was found.

Stabilisers (both sides):

  • The Polish command: no violation of airspace was observed in the evening episode.
  • The RCB: in both night episodes the cancellation says there is no threat on Polish territory.
  • The northwest is absent from the closed lists of 560 and 78 and from Sunday's partial morning notes.
  • No shot at the Baltic borders and no new airspace violation of Lithuania, Latvia or Estonia was found in the texts read.
  • The CSTO exercises have not started in the text read for this window.

Why this score: holding 5.1 follows from the window adding one more Polish episode closed without a violation, and two RCB cancellations, rather than a named violation of NATO airspace, the use of weapons at the Baltic borders, a strike on the Baltic northwest, or a declared mobilisation. The missed midnight alert in the previous issue is the same class and does not move the figure: the reading was already resting on a run of such cancellations.

Delta from the previous issue: = (0.0) — 5.1 (10 October) → 5.1 (11 October). Reason: the evening is closed by the command's sentence; the night alerts are closed by the centre's cancellation; the lists of 560 and 78 do not name the northwest; Sunday morning's list is not closed, but the partial notes do not name the northwest either.

Caveat: this is an analytical assessment from open sources, not a forecast.


Sources