HORIZON-CL4-2026-03: Boosting Space through EU non-dependence for critical space technologies

HORIZON-CL4-2026-03: Boosting Space through EU non-dependence for critical space technologies

Horizon Europe Cluster 4 launched a dedicated 2026 Space package focused on strategic autonomy and resilient supply chains for critical components and subsystems used in European space systems. The call is published as HORIZON-CL4-2026-03 and is currently listed as Open by HaDEA. It is a single-stage deadline call with opening date 10 March 2026 and submission deadline 3 September 2026 at 17:00 (CEST).

This page is written for applicants who want to target this call in a realistic way. It is not just a rewrite of the official announcement; it is a practical guide grounded in the call metadata, topic descriptions, and funding table details published in the official 2026–2027 Horizon Europe Work Programme.

Key details at a glance

What this call covers and why it is strategically distinct

Most of the 2026–2027 Horizon calls are broad. This one is narrower by design. It is explicitly focused on critical space components and equipment and on the conditions that can lock European missions into dependence on third-country technology.

The topics sit in a mission-relevant section of Horizon Europe Cluster 4 (Destination: open strategic autonomy in developing and deploying space infrastructures, services and applications). They are not about open-ended science-only space research; instead, they target technologies with clear industrial and security implications:

• R&D for replacement or resilient versions of components where non-EU supply is fragile
• Qualification and industrialization pathways (where practical)
• Hardware, interfaces, and facilities that improve mission self-sufficiency in Europe

This makes the call useful for organizations that can propose a technology-to-industry path, not only a prototype paper exercise.

Because the call pages repeatedly frame outcomes around “access to space missions” and “strategic autonomy,” you should treat these topics like mission-enabling industrial innovation calls: technical quality and implementation governance carry almost equal weight.

Call portfolio map: 81, 82, 85, and 86

The current open Space call includes four named topics:

• HORIZON-CL4-2026-SPACE-03-81: Space critical EEE components for EU non-dependence – Radiation Hard FPGA on 7nm. This is a RIA with topic-level budget up to €12.74M.
• HORIZON-CL4-2026-SPACE-03-82: Space critical EEE components for EU non-dependence – GaN MMICs mm-Wave Foundations (Phase A): Development and Industrialization of Semi-insulating SiC Substrate Capabilities. This is a RIA with topic-level budget up to €6.86M.
• HORIZON-CL4-2026-SPACE-03-85: Critical Facilities Serving Space EEE components for EU non-dependence – High and Very High Energy Irradiation Test Facility Market Deployment. This is an IA with topic-level budget up to €3.92M.
• HORIZON-CL4-2026-SPACE-03-86: Space critical Equipment for EU non-dependence – Space Refuelling Interface. This is a RIA with topic-level budget up to €2.94M.

These titles are not interchangeable. You should only choose the topic that matches your technical portfolio and execution capacity. Proposing the wrong subtopic is one of the most common “reject before review” causes in specialized technical calls.

Who is best suited for this opportunity

This call is designed for technical teams with enough depth to handle supply-chain redesign, compliance, and integration constraints.

Best fit profiles

• Industrial SMEs with proven relationships to space, semiconductor, or high-reliability electronics supply chains.
• Research organisations that can partner with manufacturing/qualification organisations.
• Consortia combining component developers, qualification/qualification-adjacent entities, and mission-facing application users.
• Institutions already active in space hardware, trust-chain compliance, export-control-aware design, and long-cycle qualification.

Profiles to avoid applying alone

• Single academic labs with only a conceptual concept and no scale path.
• Teams that cannot secure EU-manufacturing or supply-chain capability support.
• Proposers treating this as a near-term small grant with no strategic autonomy link.

A strong proposal needs a coherent chain from science/engineering through hardware readiness and eventual mission insertion.

Eligibility and mandatory constraints (what is explicitly confirmed)

The HaDEA summary provides the official call skeleton and topic IDs. Topic 03-81’s detail text is explicit about expected deliverables and risk controls. Important confirmed constraints include:

• The call is single-stage and open as one package.
• The opportunity covers four topics under one call identifier.
• Proposal outcomes are tied directly to strengthening EU independence in critical space components.
• The 03-81 topic text requires that proposals explain the technology and supply chain at a high level, including whether parts are affected by export controls outside EU frameworks.
• It also requires addressing chain vulnerability and demonstrating that outputs are usable in European contexts without restrictive external controls.

The 03-81 page also sets a technical quality expectation: by project end, TRL improvement to 6 is expected, and deliverables around standards and qualification documentation are specifically required when a project follows space qualification routes.

Other topics are linked from HaDEA as official EC pages. Their action type and budget figures are available from the Horizon Europe call overview. For exact eligibility wording beyond what is guaranteed on each topic page, always open each topic page again before submission; call systems often add eligibility clarifications without changing the high-level call metadata.

Funding profile and expected scope of effort

The funding table indicates the maximum EU contribution per project for each topic, with one or more projects likely per topic. It is not a pooled amount across all four topics; each topic has its own ceiling and action type.

From the official listing used in this guide:

• Topic 03-81: up to approximately €12.74M
• Topic 03-82: up to approximately €6.86M
• Topic 03-85: up to approximately €3.92M
• Topic 03-86: up to approximately €2.94M

Given these levels, these projects are typically large collaborative efforts, often with industry and non-industry components.

In practice, the funding profile creates a practical filter:

1. Scope and ambition must be realistic for the topic budget and action type.
2. Cost realism matters, because EU grants in this category are expected to fund R&D-to-industrialization bridge work, not only proof-of-concept.
3. Intellectual property and ownership control are likely to be negotiated carefully, especially when non-EU influence must be minimized.

How to prepare a strong application package (practical view)

Below is a workflow that reflects how technical evaluation teams usually assess these calls. The checklist is tuned to the actual text available on the official pages.

1) Pick the topic before writing the concept note

Do not draft a generic “space components” proposal first. In this call, each topic is narrow and reviewers will evaluate fit quickly. If your proposed technology has a mission dependency but not a direct match to one of the four topic titles, you may still build a stronger proposal by selecting the adjacent topic that maps most directly to your path.

A useful internal test:

• Does your solution directly support space mission hardware resilience and autonomy?
• Can it be justified as reducing dependence on non-EU components or non-EU supply controls?
• Do you already have a route to at least TRL-6 level outputs where relevant?

If you answer all three positively, the project likely fits.

2) Build a supply-chain-first work breakdown

For this call, the phrase “strategic autonomy” is not decorative; it is a decision boundary. In your technical plan include:

• Source chain mapping by component family
• Risk map for non-EU restrictions and dependency concentration
• Mitigation steps with milestones (design qualification, pilot manufacturing, delivery and integration path)

Reviewers need evidence that the chain can be made less vulnerable and that Europe can benefit operationally, not only in publications.

3) Align milestones to the call’s final timeline

The single deadline is fixed. Build backward from acceptance of the final submission:

• Full draft technical section two weeks before internal final
• Internal security and compliance review before final sign-off
• Submission QA pass (administrative, formatting, budget coherence)

For topics with strict component qualification expectations, teams should front-load risky technical work packages. Reviewers dislike vague milestone trees for hardware projects.

4) Keep your implementation narrative consistent with evaluation logic

A good evaluation-ready narrative links four things in one chain:

• Why this component/topic is critical now.
• Why existing alternatives are insufficient.
• Why the project approach lowers vulnerability while keeping industrial viability.
• Why the consortium can deliver under realistic timelines.

The best proposals are coherent across technical, industrial, and governance layers.

Application process and official submission path

The call status and dates are published on the HaDEA call page. The page explicitly links each topic to EC topic entries and is the accepted starting point for the open call metadata.

At a minimum, your pre-submission tasks should include:

1. Confirm your chosen topic ID and call status on official pages.
2. Verify that your organization profile and partner composition match Horizon Europe and country eligibility rules for this call.
3. Prepare the full proposal package in the official portal workflow.
4. Keep all export-control and supply-chain assumptions explicit in a dedicated section.
5. Ensure confidentiality-sensitive design artifacts are handled per any project governance requirements.

Do not rely only on mirrors for procedural details. Use the portal and official PDF/annex material as the source of truth for templates, forms, and eligibility annexes.

Common mistakes that regularly weaken applications

1) Weakly tied topic selection

Choosing a technology stack that sounds adjacent but does not match the listed 03-81/82/85/86 intent creates a fast rejection risk.

2) Underestimating security and compliance sections

The 03-81 text explicitly references legal export controls and trustable supply chains. Teams that mention these only superficially are often ranked below more mature proposals with explicit compliance architecture.

3) Mismatched expectations for action type

RIA and IA are not interchangeable. Your project architecture should be action-appropriate:

• RIA should reflect research and innovation activity with technical maturation.
• IA should reflect more demonstration/deployment-like execution.

4) No implementation chain from TRL to mission context

These are mission-influencing calls. A proposal that does not connect development, qualification route, and mission insertion loses competitiveness.

5) Vague ownership and follow-through model

Because outputs are often strategic and potentially sensitive, reviewers expect clear plans for commercialization, availability conditions, and long-term stewardship after project end.

6) Ignoring the post-2026 continuity

Applicants should indicate whether the topic outcome enables follow-up activity in later Horizon calls or commercial scaling pathways, especially with call cycles that continue into 2027 in related strategic autonomy themes.

FAQ

Is this call still open now?

As of the checked metadata date, the call is marked open and has an announced close date of 3 September 2026. Check the HaDEA page for status updates immediately before submission.

Is this a single-stage call or two-stage?

The HaDEA metadata indicates single-stage submission.

Can a consortium mix topic-relevant outcomes?

The safest path is to apply to one topic only, with tightly aligned objectives. Mixed-topic scope creep is a known risk in technical evaluation panels.

Does this target only one country?

No single-country framing is in the call title itself; the call is a Horizon Europe open competitive framework. Eligible participant logic is governed by Horizon rules and country participation, so verify the country eligibility matrix in the latest official annexes.

What should the proposal emphasize if we are a hardware startup?

Emphasize qualification maturity path, manufacturing feasibility, and risk-managed supply-chain transition rather than only novelty. Hardware calls favor demonstrated execution and industrial relevance.

Is TRL 6 required?

The detailed 03-81 topic text specifically references TRL 6 as an expected end-point target. For other topics, verify topic wording directly before submission.

Official links and monitoring points

Use these links as your baseline set:

• Official call landing: https://hadea.ec.europa.eu/calls-proposals/boosting-space-through-eu-nondependence-critical-space-technologies-horizon-europe-space-2026-calls_en
• Topic hub listing (French mirror of call pages; useful for budget/action-type snapshots): https://www.horizon-europe.gouv.fr/appels/espace
• Topic 03-81 detail (official mirrored page with scope and expected outcomes): https://www.horizon-europe.gouv.fr/space-critical-eee-components-eu-non-dependence-radiation-hard-fpga-7nm-42306
• Horizon Europe 2026-2027 Work Programme PDF entries for this cluster and topics: https://www.horizon-europe.gouv.fr/sites/default/files/2026-02/work-programme-7-digital-industry-and-space-horizon-2026-2027-en-pdf-12315.pdf
• EC EC Funding and Tenders entries (topic IDs):
  • https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/topic-details/HORIZON-CL4-2026-SPACE-03-81
  • https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/topic-details/HORIZON-CL4-2026-SPACE-03-82
  • https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/topic-details/HORIZON-CL4-2026-SPACE-03-85
  • https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/topic-details/HORIZON-CL4-2026-SPACE-03-86

Practical next steps before you submit

1. Open the call page and confirm the current deadline status.
2. Confirm your final topic choice and action type.
3. Set a strict internal timeline that includes compliance review.
4. Build a supply-chain risk appendix and attach it as a named technical deliverable.
5. Validate financial and partner declarations against the latest Horizon templates.
6. Finalize a publication and dissemination plan that protects sensitive technology while supporting deployment.

This call is unusual in that the opportunity language and the funding terms are clear, but the technical evaluation bar is high and very implementation-oriented. Strong applications are not the loudest ones; they are the most specific ones.