Dual-use Aviation Systems and Autonomy 2026: Innovate UK Grant Competition for Collaborative Delivery

Dual-use Aviation Systems and Autonomy 2026: Innovate UK Grant Competition for Collaborative Delivery

Key details

This opportunity is a historical reference. The official UKRI and Innovation Funding Service pages mark the competition closed, and the official pages reviewed do not announce a next cycle. The IFS link should not be treated as an open application route.

What the opportunity is and why it exists

This UKRI/Innovate UK competition was designed to fund practical aerospace technology development with civilian and defence applications. Innovate UK allocated up to £10 million for dual-use aviation technologies and systems, with the competition opening on 5 May 2026 and closing on 3 June 2026. It did not target academic publication output, service-only activity, or pure software prototypes unrelated to operational outcomes. The brief focused on deployment readiness and on creating systems and pathways that could be adopted by UK operators.

The official summary is explicit: projects should support a stronger UK national security and defence ecosystem, while also driving innovation with commercial and export-ready potential. That dual objective is important because these calls are not about isolated technical experiments. Teams are expected to demonstrate how their work will move toward integration, operation, and user adoption in meaningful environments.

The competition is also very specific in scope. It covers dual-use aviation systems like unmanned aircraft systems (UAS), eVTOL and eCTOL platforms, autonomous or swarming systems, and related integration technology. The page text makes clear that “dual-use” is interpreted broadly as technology that can function in both civil and military contexts, including civilian products adapted for defence use or defence technologies adapted for civilian use. This matters because it broadens opportunities while preserving a hard focus on national relevance and practical commercialization.

Who was eligible to apply

This was a lead-organisation competition for teams that could show they were set up for delivery, not exploration. The strongest applicants were generally those with:

• A UK lead organisation with formal collaboration structure in place;
• Access to technical facilities and flight or systems integration testing routes;
• A clear user pathway to at least one UK operator or customer partner;
• A budget sized for concrete work and realistic 8–12 month delivery;
• Internal capability to manage cross-partner delivery and reporting obligations;
• An understanding of UK aerospace safety and operational constraints.

Because the programme asks for collaboration, single-company standalone submissions are not eligible. The application must be structured as a multi-organisation project, with one lead and at least one funded UK SME partner in the consortium.

Strongest fit profile

A good fit is often a technology startup, SME, or public-sector operator-led consortium where the project is past proof-of-concept and moving toward demonstrator-level integration. In practical terms, this means your team should already be in a place where engineering, software, sensing, autonomy stack, and systems-level integration decisions are converging.

Teams frequently fit well when they include:

• At least one company with direct engineering ownership of the core technology,
• One partner with domain access or operator insight,
• One partner supporting compliance, certification or integration,
• Optional academic/RTO input where the technical depth is high.

The call was not suitable for a university acting as principal applicant because the lead role was restricted to UK-registered businesses or public-sector organisations. Research institutions could collaborate, but could not lead.

Eligibility that changes everything

The eligibility conditions are easy to underestimate because they are presented across the official listing and IFS sections, so they need to be read as hard requirements.

Lead and consortium rules

• The lead must be a UK registered business of any size, or UK public sector organisation.
• The competition is collaboration-only. No solo lead without a partner setup.
• The consortium must include at least one UK registered SME claiming grant funding.
• Lead and at least one other funded partner must provide grant claims in the budget.
• The partnership must meet normal collaboration rules: invite all members in IFS, with accepted terms.

Project constraints and UK delivery

• Total eligible grant request must sit between £300,000 and £1.25 million.
• Project period must be between 8 and 12 months.
• Project start must be from 1 September 2026 and end by 31 August 2027.
• Project work is expected in the UK; any justified non-UK work needs prior approval.
• Maximum funded partners: 5.

For teams with overseas collaborators, this is usually manageable only if you provide clear justification and are prepared for stricter administrative and legal checks, including export control and legal obligations.

Non-negotiable commercial and legal constraints

The page includes explicit exclusions and compliance boundaries that should be handled early in proposal design:

• No reimbursement for projects that are purely academic or that cannot show a path to operational readiness.
• Projects must include a UK customer or operator partner.
• If a project needs flight tests, approvals must be either in place or realistically achievable within project timelines.
• Export controls and sanctions considerations are part of eligibility risk, not afterthought sections.
• The call is open to ambitious projects but does not fund those built on unrealistic assumptions of domestic market performance.

What kinds of projects were supported

The competition aimed at operationally meaningful dual-use development. The focus was not just technical novelty; it was technical relevance in scenarios where adoption and resilience matter. Strong applications generally aligned with these themes:

• Swarming systems with operational integration,
• Multi-platform operations for complex missions,
• Enabling capabilities that improve interoperability and operator visibility,
• Heavy-lift or vertical systems for logistics or critical-response use,
• Systems that align with broader UK public-interest and national missions.

The official guidance also lists example contexts such as search and rescue, aerial delivery, survey, medical support, resilience, and critical infrastructure inspection. Importantly, the competition expects projects to be positioned against one or more specific use cases, not broad aspiration statements.

What is excluded by design

The competition text identifies several categories that do not pass. If your proposal is in these, it is likely to fail screening before full assessment:

• Counter-UAS systems as a standalone focus,
• Pure sub-system development without integrated systems operation,
• Projects that only cover civil or defence use cases without a clear cross-domain transition,
• Alternative propulsion research where hydrogen or SAF development is the primary focus,
• Projects without a defined UK user partner,
• Projects dependent on approvals that cannot be obtained in the schedule.

If you have a valid technical concept that falls into one of these excluded categories, you may need to re-scope before applying.

Application process (official flow for the closed cycle)

The UKRI opportunity page linked directly to an IFS overview where the full process was handled. No new application can be started for this closed cycle. For archive and post-submission reference, the official application was split into four sections:

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

That structure mattered because the lead applicant had to provide complete responses in the relevant sections. Project details established baseline fit and context, while the scored questions evaluated depth, practicality, and delivery quality.

Official timeline for the closed cycle

• 5 May 2026: competition opened;
• 3 June 2026, 11:00 AM UK time: competition closed;
• 8 July 2026: applicants notified;
• 1 September 2026: project start from.

This was a short window for teams that were still building a consortium, so pre-application coordination was essential. A lead applicant also had to ensure that every section was complete, that partners had completed their assigned sections, and that partners had accepted the terms and conditions before resubmitting.

Submitting and revising

The portal allowed an applicant to reopen a submitted application up to the deadline. The lead applicant then had to resubmit it before the closing time; a partial submission was not a substitute for a complete application. Partners were responsible for entering their own project costs and completing their Project Impact questions after accepting the IFS invitation.

Support and contact

The competition page provided support via [email protected] and 0300 321 4357 for application questions and accessibility adjustments. The published phone hours were 9am to 12pm and 2pm to 5pm UK time, Monday to Friday, excluding bank holidays. Those details remain useful for interpreting the archived guidance, but they do not reopen the competition.

What applicants needed to prepare before opening the form

Applications with weak structure could lose points in both scoring and credibility even when the technical idea was strong. A practical preparation plan for this competition included:

1) Partnership architecture

Define the lead relationship, roles, and accountabilities first. Since collaboration is mandatory, every named partner should have

• A clear contribution tied to deliverables,
• A reason to be part of the consortium,
• Defined budget responsibility,
• A named governance path for internal decision-making.

2) User and operator evidence

The “UK customer or operator” requirement is explicit and must be named in scope. Include an operator interview, letters of interest, or clear usage assumptions.

3) Scope-to-outcome map

Map each technical package to operational outputs:

• What exactly you will build by month,
• How that output is tested,
• How output helps the operator,
• What commercial route follows.

This programme is highly sensitive to outcomes that remain theoretical.

4) TRL and maturity argument

The call requires development work at technology readiness level 5 and above at system level. Explain clearly:

• starting TRL,
• planned maturity step for each cycle,
• evidence needed at each milestone,
• how each milestone leads to integration.

5) Regulatory and approvals planning

If the project needs flight activity, you should already have an approval plan. The requirement is not that every permit is currently held, but that there is a credible, timed pathway. “We will apply later” without evidence is usually weaker than a realistic permit path with owners and contingency.

6) Cost structure and match-funding logic

Grant request caps are strict. Split costs by partner and workstream with enough detail for Innovate UK to see value for money. If a requested budget has no technical or delivery rationale, reviewers read it as risk.

7) Risk and dependencies

Most assessments fail on hidden assumptions. A strong risk section is not just a list; it must include mitigation actions, owners, and fallback plans if a dependency slips (for example, test approvals, supplier delays, or integration delays).

Finance and assessment signals

This competition gives a competition-level budget of £10 million and project-level grant requests from £300,000 to £1.25 million. Funding intensity varies by organisation type and project category under R&D streamlined rules. In plain terms, small organisations have different eligible-cost percentages than larger organisations, and academic and non-economic partners are treated differently.

How scoring often goes right or wrong

In this programme, two things matter more than polished text:

• Is the project clearly in scope and operationally relevant, and
• Is execution believable within 8–12 months with the stated budget.

A proposal can describe an excellent technology and still lose if it does not show pathway realism. Conversely, projects with modest novelty but strong evidence of fit and delivery often perform better.

The page indicates applications are assessed by independent reviewers and that, as with many UKRI innovation calls, portfolio constraints may limit award numbers even for high-scoring applications. So, even perfect scoring does not guarantee funding if the programme portfolio balance changes.

Common mistakes in this kind of dual-use call

“Innovation-first, evidence-later” proposals

Many teams begin with strong technical ideas but underdeliver on implementation detail. This competition expects concrete integration plans, especially for autonomous and aviation systems that must integrate hardware, software, and operations.

Overly broad scope

Projects attempting to cover too many use cases often appear weak because each case is underdeveloped. Select one or two high-impact paths and show deep execution quality.

Weak UK partner design

The UK customer/operator requirement is a screening point. If your UK operator connection is generic or implied, your project risks rejection before scoring. Name the operator type and role.

Ignoring funding intensity and max-funding concentration

Requests that appear unrealistic for one partner’s share can trigger risk flags. Keep a coherent split and avoid one partner carrying most costs without clear rationale.

Unresolved externalization

Overseas subcontracting is possible but must be justified. If UK alternatives exist, defaulting to overseas providers without evidence of attempts creates avoidable weakness.

Weak permit and compliance planning

If flight testing is essential to outcomes, a permit and compliance plan should be part of day one. Vague assumptions are often interpreted as planning gaps.

Historical application preparation sequence

A structured approach for a team preparing during the specific application window was:

Week 1 (immediately)

• Confirm lead eligibility and consortium list;
• Finalize UK operator/customer partner;
• Define one primary use case with measurable outputs.

Week 2 of preparation

• Draft scope, need/challenge, and approach/innovation responses;
• Finalise project timeline to meet 8–12 months and deliverable gates;
• Begin permit and compliance mapping.

Week 3 of preparation

• Build project impact and market sections,
• Produce cost model by work package,
• Prepare partner finance inputs.

Week 4, the closing week

• Final internal review by both technical and commercial owners;
• Upload required appendices (where needed, with size limits respected);
• Reopen and final submit in IFS before close.

This schedule assumed each partner was available. If a consortium was delayed, high-confidence sections needed to move earlier, leaving late edits for budget and compliance sections only. It is retained as historical planning guidance, not as an indication that submissions remain open.

FAQ

Can an academic institution lead this competition?

No. The lead must be a UK registered business of any size or UK public sector organisation. Academic institutions can participate as collaborators under the partner role.

Do I need to include a private investor in the consortium?

No. Investor participation is not mandatory for eligibility. The key requirement is a valid UK collaboration structure and required SME inclusion for funding.

Is flight testing required?

No, but projects that include flight activity must show it is permitted or realistically approvable within the timeline. The requirement is that any testing route be credible and time-bounded.

Can non-UK subcontractors be used?

Yes, with constraints and justification. You must demonstrate legitimate rationale, documented procurement effort, and (for any overseas component) prior approvals where relevant.

What happens after submission if shortlisted?

Successful applicants move to award and project setup steps in IFS. The opportunity text indicates the process continues with mandatory checks, setup information, and grant terms before funding flows.

How did partners submit their sections?

The lead invited each partner into IFS. Partners then accepted the invitation, entered their own project costs, completed their Project Impact questions, and accepted the terms and conditions. For an eligible collaboration, the lead and at least one other organisation had to claim funding, provide a collaboration rationale, and ensure no one partner accounted for more than 70% of the total eligible grant.

Reviewer mindset: what they are likely to reward

For this competition, high-scoring proposals usually show all of the following:

• A clear operational problem and a clear operator need;
• A concrete technical sequence from baseline to demonstration;
• Transparent risk management and mitigation;
• A budget that makes delivery believable;
• Compliance and legal awareness (permissions, export-control posture, sanctions checks); and
• Strong UK value beyond generic “national strategy alignment” claims.

Official links

• UKRI opportunity page: https://www.ukri.org/opportunity/dual-use-aviation-systems-and-autonomy/
• IFS competition overview: https://apply-for-innovation-funding.service.gov.uk/competition/2467/overview/3ac02a1d-68e5-460b-bddb-0ecacdabfb00

Final archive note

This was a concise but serious opportunity. The headline amount and short deadline rewarded teams that narrowed scope, tightened collaboration, and demonstrated operational readiness from day one. It was not a general innovation grant for exploratory ideas. It was a delivery-focused competition for dual-use aviation technology with clear UK user relevance and a realistic pathway to deployment and commercialisation. Since the official pages now mark the cycle closed and do not announce a successor, readers should use this entry to understand the closed call rather than treat it as an active funding opportunity.