UK Counter UAS Technologies Grant (Innovate UK) 2026: Counter UAS Technologies

UK Counter UAS Technologies Grant (Innovate UK) 2026: Counter UAS Technologies

Key details

The official UKRI page for this opportunity shows the competition as open with a close date in early June 2026 and a total fund of £5 million.

What this opportunity is and why it matters

Counter UAS technologies refers to systems designed to protect people, infrastructure, and secure facilities from harmful or unlawful use of drones. This competition is explicitly framed as a dual-use innovation programme, so the same technical output is expected to have relevance across both civilian and defence/security or intelligence contexts.

The stated purpose is practical: build UK resilience against escalating UAS misuse around airports, prisons, critical national infrastructure, schools, and public events. The wording used on the official competition page is very explicit that funded proposals should address national security priorities, critical infrastructure protection, and wider UK protection goals.

This is not a generic technology grant. It is a targeted competition with technical and operational expectations that resemble real-world deployability:

• Solutions should demonstrate a credible path to deployment, not just a theoretical design.
• Candidates are expected to account for legal and regulatory constraints.
• Applications are screened against a portfolio approach and explicit “not funded” triggers.

In short: the competition is less about elegant writing and more about coherent demonstration of readiness and fit with UK operational needs.

Who this opportunity fits

The competition is best for teams that already have a technical option beyond concept-stage and can operate in a constrained 2026/2027 timeframe.

Best fit examples

• UK SME-led hardware, software, sensing, or detection teams that already have a TRL 4–5 concept and can move toward demonstration.
• Security-tech consortia combining engineering, integration, field-deployment, and compliance capability.
• Teams with direct pathway relationships to likely users (e.g., airports, local government infrastructure teams, secure estates) and evidence of user engagement.
• Collaborative partnerships where the lead is a UK-registered business or public sector entity and at least one UK SME is grant-funded.

Who should probably pass

• Researchers who only have a conceptual concept and no evidence of readiness for test, validation, or deployment planning.
• Proposals relying solely on existing commercial counter-UAS products with no real experimental development.
• Applicants unable to comply with UK legal/permissions constraints for flight trials or operational testing.
• Teams expecting to do most project work outside the UK without approved justification.

The program is for organisations with appetite for a relatively short cycle (8–12 months), where execution discipline matters more than broad long-term vision statements.

Eligibility: exact constraints that matter most

The competition page makes eligibility concrete, and this is where many applications fail. The following points are the high-risk filters:

1. Collaboration is mandatory

   • The lead applicant can be any-size UK business or a UK public sector body.
   • The consortium must include at least one UK SME that claims grant funding.

2. Only certain roles are eligible as lead and partners

   • Lead: UK-registered business or UK public sector org.
   • Partners can include businesses, charities, not-for-profits, research organisations, academic institutions, and public sector organisations.

3. Financial/project window is fixed

   • Total eligible grant request must be within £300k–£1.25M.
   • Project duration must be 8–12 months.

4. UK work is the rule, exceptions need approval

   • Default assumption: work in the UK.
   • Work outside the UK requires email-based justification and approval before submission.

5. Subcontractors and approvals are constrained

   • You can use overseas subcontractors only with evidence and justification.
   • Cheaper overseas costs alone are not sufficient to override UK sourcing requirements.

6. Exports and sanctions matter

   • Non-compliance on sanctions or export-control obligations can disqualify you.
   • Projects must provide enough clarity around TR&I and export-status risks.

7. Regulatory readiness for testing/demos

   • If your project needs regulatory approvals, they must either be already in place or realistically obtainable within your timeline.
   • The application asks for explicit demonstration of this.

Scope and what you can actually propose

The competition scope is strongly operational:

• Protective UAS solutions for defence/critical infrastructure/airports/schools/public events, with emphasis on cost-effective and scalable designs.
• Solutions aiming for deployment by around 2028 (in the protection-focused stream).
• A parallel stream for prison estate protection, where earlier TRL development is acceptable if targeted toward eventual deployment around 2030.

The competition explicitly excludes certain categories:

• Projects with no specific end user and no concrete use-case.
• Technologies already fully commercialised in counter-UAS at time of application.
• Off-the-shelf only proposals with no experimental development component.
• Solutions requiring unrealistic dependencies or impossible regulatory approvals by the project end.
• High-collateral kinetic approaches.

The practical implication: you need clear user-facing outcomes (e.g., demonstrator, prototype, field-validation route) and an evidence-led plan for legal compliance.

Application process and structure

If you are applying through the Innovation Funding Service, the process is structured into four sections:

1. Project details.
2. Application questions.
3. Finances.
4. Project impact.

Timeline to plan backwards from

• Competition opens: 5 May 2026.
• Closes: 3 June 2026, 11:00 AM UK time.
• Applicants notified: 8 July 2026.
• Project start date target: 1 September 2026.

This gives roughly one month for preparation and submission, then about a month to project setup after notification.

Application mechanics (officially important)

• You may reopen and resubmit before deadline.
• You must ensure the lead lead and all required partners submit complete sections and accept terms.
• Answers in scored sections require concise, decision-relevant writing.
• The system is strict on URLs in some answers; do not over-embed links.

Scored question strategy

From the official guidance, the scored application questions are the place to demonstrate depth:

• Need and challenge: define operational pain and why existing counter-UAS tools are insufficient.
• Approach and innovation: show technical route and product/system evolution.
• Team and resources: match expertise to tasks and milestones.
• Market awareness and route to market: prove there is demand beyond concept.
• Outcomes and route to commercialisation: explain exploitation and growth.
• Risks and mitigation: include technical, commercial, regulatory, and operational risks.
• Value for money and costs: justify requested grant in a realistic budget context.

Do not treat this as a pure research abstract. Every answer should be measurable, operationally grounded, and connected to the consortium structure.

Required materials and preparation checklist

A practical application prep list should include:

1. Regulatory pathway evidence

   • Confirm what approvals are needed for flight trials and demonstrations.
   • Include staged plan that shows how approvals fit in an 8–12 month schedule.

2. Site-level user evidence

   • Identify exact user categories: airport operations, prison estate, CNI, schools, event management.
   • Define the end-user pain-point each deliverable will address.

3. Technical proof and TRL argument

   • State where the project sits now.
   • Explain the move to field-representative testing within constraints.

4. Delivery package

   • Gantt/charts for work packages and dependencies.
   • Risk register aligned to milestones.

5. Financial model

   • Break grant by work package and partner.
   • Show counterpart/sustainability beyond grant support.

6. Partnership roles

   • Keep consortium size ≤ 5 funded partners (as stated in the competition eligibility).
   • Ensure each funded partner has a clear reason for existence.

7. Commercialisation pathway

   • Even for security-relevant technology, reviewers need an exploitation story.
   • Include who pays, who buys, and what licensing or production model follows.

Budget, funding intensity and financial interpretation

The competition has a competition-wide cap of £5 million and individual project grants in a constrained range. This matters because it shapes the project design:

• If your technical design is too large in scope, split and phase it.
• If your development cost is too low, explain why that is enough to meet deployment-readiness goals.

The page states funding percentages by R&D category and entity size under R&D streamlined routes (including industrial research and experimental development). In practice, this means you should budget with clear, defensible eligible costs and avoid inflated cost lines that do not map to outputs.

A key signal from the official text: projects with excessive reliance on speculative growth claims without concrete grant-claimable milestones tend to be weak. Reviewers repeatedly prioritise realism: clear outputs, compliance, and evidence of deployability.

Practical review expectations and how to avoid common failure modes

Common mistakes

• No real defined user context

  • Application states “UAS security is important” without specifying target sites, workflow, deployment constraints, or integration environment.

• Technology exists but no R&D leap

  • If the proposal is mainly repackaging existing commercial products, it risks rejection.

• Insufficient UK delivery plan

  • Failing to justify work outside the UK when proposed.
  • Weak subcontractor rationale.

• Regulation not solved

  • Overlooking required approvals and their timing.

• Grant requests over-designed

  • Asking amounts disconnected from 8–12 month, TRL-to-demonstration reality.

• Ignoring the collaboration structure

  • Not clearly using a lead+partner design with defined accountabilities.

Strong reviewer signals

• Precise definition of threat/use scenario and measurable outputs.
• Evidence of real integration fit with UK constraints (airspace management, communications, safety).
• Balanced risk register with owners and mitigation actions.
• Financial split that reflects actual funded work, not wishful spend categories.

FAQ: targeted questions before you start

Is this only for security companies?

Not exactly. The program is dual-use and explicitly covers civil, defence, security and intelligence domains, so applications should show where a technology can transition across these contexts, not a purely military-only pitch.

Can academic institutions lead?

The lead is restricted to UK-registered businesses or public sector organisations. Academic institutions cannot lead, but they can join as collaborators.

Is this funding only for TRL5+

Competition language distinguishes pathways:

• Protection-use stream expects higher maturity (around TRL5+ with aim to deploy by 2028).
• Prison-focused stream accepts earlier development work, often up to TRL4, with deployment later.

Is single-organisation submission allowed?

No. It is collaboration-only.

Can I use overseas partners?

Yes only in defined, justified cases. For funded and non-funded collaborators, clear rationale and approvals are required, with export-control considerations carefully documented.

What happens after award?

Successful applicants move into project setup on IFS, where mandatory checks and additional documentation are required before project start.

Decision quality checklist before submission

Use this as your pre-submit list:

• Collaboration includes one UK SME lead-claimant.
• Lead + partners are all invited and visible in IFS workflow.
• Project dates exactly fit the 8–12 month window.
• Grant requested is in the permitted range.
• Project start and end dates respect expected timeline from 1 Sep 2026 to 31 Aug 2027.
• Scope answers map to one of the two solution pathways and include a clear end-user problem.
• Regulatory approvals are identified with evidence and timing.
• No prohibited high-risk approaches (e.g., unjustified collateral-damaging methods).
• Risk register includes technical, regulatory, operational, and procurement risks.
• Financial table is complete with partner allocations and grant intensity assumptions.
• Every partner completes Project Impact section.

Official links

• UK opportunity landing page: https://www.ukri.org/opportunity/counter-uas-technologies/
• Innovation Funding Service competition overview: https://apply-for-innovation-funding.service.gov.uk/competition/2468/overview/6be7375d-717c-49b4-9411-f7709bb9e6ea
• UKRI good research/eligibility guidance from the competition page

Why this matters for your 2026/2027 cycle planning

This is one of the more operationally demanding UK government competitions in security tech because the review criteria force teams to show they can handle legal and systems constraints, not just research novelty. If your team has a near-term deployment track and a UK-ready execution structure, this can be a strong fit even if you are not a pure defence vendor. If your team is still pre-validation only, this competition is likely too advanced on commercial expectation but too early for market launch.

For 2026/2027, treat the close date as urgent. As of 18 May 2026, it is still active and visible from official sources, but with only about one month left from this point, late-stage collaboration and compliance work should begin immediately.