R&D tax credit for aerospace: development yes, qualification no

Developing new aircraft components, space systems or manufacturing processes? Germany’s research allowance can support your development work where novelty, technical risk and a systematic approach can be demonstrated. Explore eligible activities and the boundaries with routine work below.

  • Funding rate up to 35%
  • OEM & Tier suppliers eligible
  • Retroactive for open years
Example: satellite mechanics

Aerospace: test systems through cycles

Aerospace: test systems through cycles

New approachTest solar wing, hinge and temperature together

Open questionHow does the joint behave across a thermal cycle?

ExperimentCombine deployment and temperature changes

In aerospace the scope of the project decides, not the certification programme.

The certification office does not assess how strict CS-25 or DO-178C are, but whether a technical question was open beforehand and answered systematically. A supplier rarely loses an application on the technology; usually it is lost because certification evidence and development sit in the same project.

Rates, costs and limits

The essentials on the research allowance in aerospace

  • Funding rate
    25% of the assessment basis, 35% for SMEs. For projects started after 31 December 2025, a 20% flat rate increases the assessment basis (Section 3 (3b) FZulG); the EUR 12 million cap still applies (Section 3 (5) FZulG).
  • Eligible
    Novel propulsion, structural and avionics concepts, qualification trials and test articles. What counts is not the certification programme but whether novelty, technical risk and systematic approach can be demonstrated.
  • What counts
    The employer gross salary of structural, propulsion and avionics engineers for the hours spent on the project. Since 2024 also the depreciation of movable assets used exclusively for the project, such as a test rig or test article. Material for the test article itself is not eligible.
  • Ceiling
    Assessment base of EUR 12 million per financial year, maximum research allowance EUR 4.2 million.
  • Contract research
    70% of the cost of commissioned development work is eligible (Section 3 (4) FZulG): wind tunnel testing, testing institutes, DLR collaborations, external certification labs.
  • Retroactive
    Applications for closed financial years from 2022 are possible as long as the assessment period of the respective year is still open; for 2020 and 2021 it has expired (§ 12 FZulG in conjunction with § 169 AO). Projects started before 1 January 2026 do not receive the overhead allowance.
  • Which activities in aerospace are eligible?

    The industry does not decide eligibility. The certification office checks every project against three criteria: novelty, technical risk, systematic approach. If one fails, the application fails. Below are the activities we encounter most often at aerospace companies and their suppliers, with the verdict we expect.

    Boundary case: eligibility depends on the specific project.

    Structures & lightweight design

    • Novel composite structure with unknown damage tolerance and fatigue behaviourEligible

      Eligible. Novelty: No laminate or sandwich concept available on the market achieves the required ratio of weight, stiffness and residual strength for your load case. Technical risk: Whether delamination growth, residual strength after impact and fatigue behaviour land in the target range is not known before simulation and test article. Systematic approach: Layup design, FEA, test article, fatigue testing, iteration, documented by calculation reports and test protocols.

    • Weight optimisation of an existing structure through thickness reductionBorderline

      Borderline. Routine as long as the design rules transfer. It becomes eligible when residual strength or damage tolerance at the new wall thickness demonstrably falls outside known substantiation methods and has to be re-derived.

    • Replacing a metal part with a composite part in a known geometryBorderline

      Borderline. Eligible is the part for which no validated design exists, such as new load introduction points or joint details. Not eligible is pure material substitution using library values.

    • Manufacturing drawing and lay-up plan to specification for a known partNot eligible

      Not eligible. Interfaces, layup, cure cycle: the result is known before the start, the procedure is documented. Effort is not a criterion of the FZulG.

    Propulsion & engines

    • New combustion or cooling concept for hot engine componentsEligible

      Eligible. Anyone who designs a cooling concept because standard solutions do not reach the required component temperature or life must explain why. That names the state of the art. Keep the rejected concepts and their measurements; that is the decisive evidence later.

    • Hybrid or electric propulsion with unknown system behaviour under flight conditionsEligible

      Eligible. Whether power density, thermal balance and failure behaviour of the powertrain land in the target range under real flight profiles is open beforehand. Test rig series showing these variables over iterations are systematic approach and technical risk in one.

    • Adapting an existing engine to a new aircraft typeBorderline

      Borderline. Eligible if the interaction of engine, intake and airframe is structurally or thermally unresolved and worked out in testing. Routine if the interface control document and the engine's type certificate prescribe the way.

    • Series integration of a certified engine to manufacturer specificationNot eligible

      Not eligible. Intended installation per instructions for continued airworthiness and installation manual. Only when the interaction demonstrably deviates from the documented case does an open technical question exist.

    Avionics, sensors & control

    • Own control strategy for active gust load alleviation or flight controlEligible

      Eligible. Anyone who designs a controller because standard controllers do not achieve the required load reduction or path accuracy must explain why. Keep the rejected controller structures and their measurement series; that is the decisive evidence later.

    • Sensor fusion for a new structural health monitoring conceptEligible

      Eligible. Whether distributed fibre sensing or acceleration signals support the required statement about structural condition at all is open beforehand. Measurement series showing signal quality and model accuracy over iterations are systematic approach and technical risk in one.

    • Porting existing avionics software to new hardwareBorderline

      Borderline. Eligible if the real-time behaviour on the new platform is unresolved beforehand and worked out in testing. Routine if compiler, time slices and interfaces are ported to manufacturer specification.

    • Parameterising certified flight control software to specificationNot eligible

      Not eligible. Intended use of the approved platform. Only when the platform demonstrably cannot map the requirement and a separate method is developed alongside it does an open technical question exist.

    Testing, qualification & certification

    • Qualification trial to resolve a technical question open before certificationEligible

      Eligible. A trial that shows whether a part reaches a required limit load, temperature or life at all is a gain of knowledge. With a measurement plan and abort criteria documented in advance, this is the clearest case in this group.

    • Wind tunnel or ground vibration test to substantiate an edge caseBorderline

      Borderline. Eligible is the share in which behaviour at the edge of the operating envelope was not known beforehand. Pure confirmation trials within already substantiated limits are evidence gathering, not a gain of knowledge.

    • EASA certification documentation and substantiation under CS-25 without an open technical questionNot eligible

      Not eligible. Pure compliance evidence for the certification authority where the technical result is already settled. The test protocols created along the way can, however, serve as evidence for an eligible project if they show iterations and not pure confirmation.

    • Repeat testing under an established test plan for batch releaseNot eligible

      Not eligible. Even elaborate series testing remains quality assurance. The way is documented, the result predictable.

    Suppliers, space & digitalisation

    • Physics-based condition model or digital twin of an aircraft or satellite systemEligible

      Eligible. Whether a reduced model predicts the dynamic or thermal behaviour of the system with sufficient accuracy is open beforehand. Comparing model and measurement over several iterations is the evidence.

    • Tier-1 or tier-2 development of a component for an OEM or a space programmeBorderline

      Borderline. Eligible if the supplier itself bears the technical risk and part of the development was open beforehand. Pure manufacturing to an OEM drawing, where the development risk sits with the client, is not.

    • Integrating standard PLM or MES software into manufacturingNot eligible

      Not eligible. Even demanding integration work remains integration. The tools are built for exactly this purpose, the way is documented, the result predictable.

    What is regularly rejected

    • Contract manufacturing and supply without own development riskNot eligible

      Not eligible. Whoever manufactures to someone else's drawing bears no technical risk. The case is different when the supplier develops the component itself and is accountable for its behaviour.

    • Maintenance, repair and overhaul under approved procedures (MRO)Not eligible

      Not eligible. Work under an approved maintenance manual is maintenance, not development. The result is settled beforehand, the procedure is approved.

    • Spare-part and modification upkeep for already certified assembliesNot eligible

      Not eligible. The result is fixed beforehand: the same functional scope in an approved form. Occasionally submitted by advisers along with everything else, and then it drags the whole project into scrutiny.

    Your project is not listed or sits between two lines? That is the normal case; eligibility is decided on the specific facts, not on the heading. Describe the project to us and we will tell you where it stands.

    How does your documentation become an application?

    Your test field and your qualification documentation already document everything the certification office wants to see, just in a different language. Here is the same set of facts in four registers, from the test rig protocol to the application sentence.

    In the test field — What gets written anyway
    Wing TF-19, gust load test series 2
    Load reduction 8% at full flutter margin
      // target −15%, controller too cautious
    
    - FBG fibres, spar ..... 3 segments
    - trailing edge actuator rev. B
    - series 3 ............. 17% / flutter ok
    In conversation — What the team says about it
    "The controller was too aggressive on the first pass, we lost the flutter margin. Then we pulled the gain back but only got to eight percent. Only with the third controller version and the strain fibres in the spar did we reach seventeen percent, and the margin still held."

    Technically complete and worthless as application text. There is no reference to the state of the art or to the measured variable.

    At the BSFZ — What is actually examined
    • Novelty
    • Technical risk
    • Systematic approach

    For each of the three criteria the application must contain a verifiable statement. What is described is the knowledge gained on the way to the finished wing.

    In the application — What we formulate from it

    "For a load-adaptive trailing edge with fibre-optic structural monitoring no control concept existed that reduces gust loads on the wing by at least 15% without falling below the required flutter margin. Whether a stable actuator command could be derived from the strain signals of the sensor fibres could not be determined in advance. The project established this in three measurement series in the wind tunnel and on the ground vibration test against a defined target."

    This is the work. The same facts, four formulations, and only one of them is an application. This translation is our actual service: building, from what your test field produces anyway, the statement the certification office can examine. Not writing more beautifully. Writing differently.

    Why do applications fail in aerospace?

    Rejected projects from aerospace rarely fail on their technology. They fail on five recurring patterns, and we see them in self-submitted applications just as in externally assisted ones.

    The state of the art is missing

    The application describes what was built, not why it could not be done with what was available. Without named competitor solutions, standards or qualified parts the certification office cannot establish novelty. This is the most common reason in our own mandates.

    How we do it. We specifically name the concepts, materials and processes that were examined and rejected, each with the technical property on which they fail.
    Certification evidence is submitted as development

    An application describing "the EASA certification" as the project forces the certification office to assess compliance evidence and development together. The pure documentation work drags the whole project down, even if part of it contains real qualification trials.

    How we do it. We scope the project to the qualification trials that resolve a question open beforehand, and cleanly separate compliance documentation and type certification.
    Project risk instead of technical risk

    Delivery dates, programme cost and supplier availability are not technical risks. Anyone arguing this way describes a management problem and gets it decided as such.

    How we do it. We phrase the risk as an open technical question: which property of the system was not predictable before the start, and exactly where the project would have failed.
    The test article is described as a product

    The application reads like a data sheet: thrust, weight, range. The certification office is looking for the way there, the trials that did not work and the measurement that proves the difference.

    How we do it. We derive the systematic approach from your own artefacts: layout in the calculation report, trial in the test protocol, decision in the change request.
    Cost side and facts do not match

    The BSFZ certifies the project, the tax office checks the costs. Anyone who claims personnel costs already reimbursed through an ESA or EU funding programme, or hours that contradict the project description, loses in the second step, after the certificate has already been issued.

    How we do it. We run project description, time recording and research allowance application (ELSTER) against the same scope from the start, including a check for double funding on international programmes.

    If you already have a rejection, the first step is analysing the decision: which of the five points carries it. That determines whether objection or new application is the right way.

    Which other industries use the research allowance?

    The sector never decides eligibility — Section 2 FZulG does. These pages show the same three criteria against the activities of each field.

    Send us a test protocol, not a questionnaire

    In the first consultation we talk about your project, not about your certification programme. After thirty minutes you know which part of your development is eligible, in what order of magnitude, and whether a retroactive application is worthwhile. The first consultation is free; 30 % of the fee falls due with the BSFZ decision, 70 % only after the allowance has been paid out.

    Book a first consultation
    Max Nodes

    Max Nodes

    Founder and Managing Director of NOVARIS Consulting. Specialised in the German R&D tax credit (FZulG) since 2021; 25 of 25 accompanied BSFZ applications approved (as of 09/2026). Max Nodes