NSPA's Counter-UAS Framework: Tested at Baltic Trust 26, Not Yet Ordered

Europe now has the money, the suppliers and a working demonstration for shooting down drones. What it does not yet have is a signed order — and that missing signature, not any technical shortfall, is where the counter-drone gap now sits.

Three things fell into place in the summer of 2026. Allied governments publicly committed more than USD 40 billion to counter-drone capability over five years. The NATO Support and Procurement Agency (NSPA) brought five suppliers of deployable counter-UAS systems under a single framework contract, built on a shared command-and-control backbone. And at Baltic Trust 26 (BATT26), the two-week exercise the Latvian National Armed Forces ran with the NATO Communications and Information Agency (NCIA) at Sēlija in Latvia from 3 to 14 August, mixed-vendor sensors, command links and effectors were made to behave as one layered chain rather than a shelf of separate boxes.

So the budget was announced, a purchasing lane existed, and a configuration had been shown to work. The fourth piece — the one that turns an exercise into a capability someone actually owns — is a firm order: a contract that binds a specific tested configuration to a delivery schedule, a sustainment tail and an accountable buyer. On the evidence assembled here, that order had not been placed. NATO's own Rapid Adoption Action Plan, endorsed on 25 June 2026, describes how the Alliance means to move faster from a decision to fielded equipment; it sets out a process, not a signed contract.

This is why the distinction between the instruments matters. A framework is permission to buy, not a purchase. NSPA's five suppliers are eligible to be ordered from; they have not been ordered from. There is in fact more than one lane: alongside NSPA's contracts sits NCIA's own counter-UAS framework, run through Invitation for Bids CO-42530191-CUAS, and both lean on the SAPIENT interface — the open counter-UAS control standard whose documentation the UK Ministry of Defence and the British Standards Institution publish. Two of the five NSPA suppliers already sit inside the BATT26 industrial universe: Axon, which owns Dedrone, and DefSecIntel Solutions. Corporate control runs through the exercise too — Blue Bear Systems Research, a participant, is listed on the Companies House register as controlled by Saab UK Limited.

None of that is revenue. A supplier on the framework has eligibility; an integrator whose kit passed the hand-off test at BATT26 has a reference. The declared USD 40 billion is a budget line, not a fielded system, and it should not be read as a framework ceiling or a market forecast. For an investor or a competitor, the gap between "declared forty billion" and "signed order for configuration X" is the gap between a market that exists on paper and revenue that exists in fact — and the interval between the two is exactly where positioning, qualification and framework access are decided.

This analysis works through that interval deliberately, and leaves the reader with the questions that actually move money:

• Which layer of the counter-UAS chain — sensing, command-and-control, or the effector — is the real bottleneck once integration, not the individual box, is the test?
• What must a supplier already on the NSPA or NCIA framework still do before a declared budget becomes an order it can book?
• How much of the announced USD 40 billion is reachable by European industry, and how much routes to configurations and vendors already inside the BATT26 universe?
• On a buyer's timeline, what turns an exercise like Baltic Trust 26 into a programme of record — and how long does that step realistically take?