Ukraine can delay missile data without surrendering the public record

The security case needs a clearer explanation

There may be a legitimate military reason to limit immediate disclosure. A sequence of launch, interception and impact figures could help Russian planners compare their own assessments with Ukrainian reporting. Even incomplete data may assist battle-damage assessment or reveal changes in the performance and availability of Ukrainian interceptors. Ukraine does not owe the aggressor a convenient daily account of how its missile campaign is performing.

The public explanation, however, has mixed that security argument with concern about damaging headlines. Ihnat criticised reports built around figures such as “28/0” and acknowledged a shortage of Patriot interceptors. According to the Kyiv Independent’s account of the dispute, officials were also concerned that Russian media amplified pessimistic Ukrainian coverage. That problem is real, but an embarrassing number is not automatically an operational secret. If a restriction is based on military risk, the Air Force should explain the category of risk without disclosing the protected data.

The figures also carry unusual public weight because Russian long-range attacks are killing civilians far from the front. The UN Human Rights Monitoring Mission recorded 437 civilians killed and 2,610 injured in July. Long-range missiles and drones caused 38 per cent of those casualties, mostly in urban areas. Daily Air Force reports cannot independently prove every interception or impact, but they allow journalists, researchers and citizens to compare official claims across time against visible damage and other evidence.

“A delayed public record is not the same as no public record.”

Removing one set of numbers may prevent Russian outlets from exploiting a bleak daily ratio. It can also create a vacuum in which unsupported claims circulate more easily. Oksana Romaniuk, director of Ukraine’s Institute of Mass Information, warned that reduced disclosure could increase suspicion and rumours. Romaniuk’s warning arose from an open dispute among Ukrainian officials, journalists and civil-society figures about how a democracy at war should communicate. It is a demand for Ukrainian accountability, not a basis for equating Ukraine’s contested reporting with the aggressor’s propaganda.

Delay the detail, preserve the record

The workable answer is delayed disclosure under a published schedule. The Air Force can continue real-time alerts and daily identification of threat types while withholding sensitive ballistic-missile outcomes. It should then release weekly or monthly totals using stable categories for launches, interceptions, electronic suppression, missiles that failed to reach their targets and confirmed hits. Each release should state the period covered, explain later revisions and distinguish confirmed results from preliminary assessments.

That method would deny Russia immediate feedback while preserving evidence of the scale of its missile campaign and the pressure on Ukrainian defences. It would also keep the restriction narrow. A temporary delay tied to a specific operational risk is easier to defend than an open-ended suspension of the figures.

Ukraine can withhold operationally sensitive air-defence data without weakening public credibility if the figures are delayed and later published. Regular aggregate releases with fixed definitions and visible corrections would preserve the evidence needed to compare official claims over time. If no follow-up record appears, journalists and citizens will have less evidence with which to judge whether the restriction remains necessary.