HomeCertification & DER Support

Certification / Compliance / Technical judgement

Certification
& DER support.

A clear compliance path.
Evidence that supports the finding.

We help aircraft developers and systems suppliers work through the certification questions that affect their design, evidence and programme. From the first compliance plan to the technical issues that need closing before approval.

Find an FAA designee

Hussein Khimji · FAA Consultant DER · Electrical Systems Engineering

Start with the decision

Where does your programme need clarity?

Certification support is most useful when it resolves a specific question and gives the engineering team a practical next step.

“We need to establish the certification approach.”
Define the proposed basis, means of compliance, responsibilities and authority discussions early enough to influence development.
“The design has changed. What evidence is affected?”
Assess the change against the approved baseline, affected requirements, safety assumptions and existing verification.
“We have the documents. Are they ready for review?”
Check whether the data supports the compliance claim, identifies the tested configuration and closes the relevant requirements.
“A technical issue is holding up the programme.”
Separate the unresolved question from the surrounding discussion, develop the technical position and identify the evidence needed to close it.

From planning to substantiation

Support that follows
the engineering work.

We connect certification planning with system safety, requirements and verification. The scope can be a focused technical question or an agreed part of the programme.

01Certification planningEstablish the proposed route and the evidence expected

Review the aircraft or system definition, intended operation and approval sought. Develop the proposed certification basis and compliance approach, including amendment levels, applicable guidance and matters requiring authority agreement.

For eVTOL and other novel designs, identify the questions that need specific treatment. Guidance from another aircraft category is assessed for applicability; it is not treated as an automatic certification basis.

Typical outputs: certification or compliance plans, compliance checklists, proposed means of compliance, responsibility assignments and a record of assumptions and agreements.

02Gap and readiness reviewsUnderstand what is complete, what is missing and what matters next

Review the planned submission against its purpose. Check coverage of applicable requirements, consistency between documents, configuration identification, open assumptions and the adequacy of supporting analysis or test results.

Comments explain the issue and the action needed. A document being present does not, by itself, mean the compliance objective has been met.

Typical outputs: a prioritised findings register, evidence gaps, closure actions, responsible owners and a submission readiness assessment.

03Technical substantiationBuild the evidence behind the compliance statement

Develop or review an agreed package of system descriptions, compliance analyses, safety assessments, verification plans, procedures and reports. Connect the requirements to the actual design and identify which analysis or test demonstrates each claim.

Where evidence is reused, assess its applicability to the current configuration, interfaces, operating conditions and assumptions. Record the additional work needed where those conditions have changed.

Typical outputs: technical reports, requirement-to-evidence traceability, test coverage reviews, change impact assessments and a controlled substantiation package.

Explore system safety support →
04FAA DER supportDefined authority, defined data and a clear finding

Provide technical review and, where authorised for the task, approval or recommendation for approval of engineering data. Confirm the relevant discipline, regulatory Parts, delegated functions and limitations against the current FAA authorisation and project arrangements.

Consulting scope and delegated authority are established separately. A DER finding on technical data is one part of the certification process; it is not an aircraft type certificate or a commitment that the programme will be approved.

Typical outputs: technical review comments, substantiated compliance findings and FAA Form 8110-3 where applicable and authorised.

The FAA’s description of the DER role →
05Authority coordination and issue resolutionMake the question, proposed position and closure evidence clear

Prepare technical positions, issue-paper inputs and responses to review findings. Support discussions with the applicant, suppliers, designees and the relevant authority, with a clear record of decisions and outstanding actions.

We identify where an issue concerns the design, the interpretation of a requirement, the proposed means of compliance or the sufficiency of evidence. Each needs a different resolution.

Typical outputs: issue papers or response inputs, meeting briefs, technical position notes, action registers and documented closure evidence.

An example of the approach

A flight-control change.
What needs revisiting?

A change can be small in the drawing set and significant to the compliance argument. Start by understanding what has actually changed and which conclusions relied on the previous design.

Illustrative engineering scenario

A new actuator controller changes the fault response.

The team proposes replacing a controller on a certificated aircraft. The control surface and intended function remain the same, but the monitoring logic, interfaces and time to isolate a fault change.

The question

Which existing findings remain supported, and what must be demonstrated again?

A fictional example, not a client programme. The applicable requirements and approval route must be established for the actual change.

01Define the change and its certification implications

Identify the original approved configuration, the proposed change and affected systems. Assess the certification basis and approval route, including the changed-product requirements where applicable. Do not assume the original basis applies unchanged.

Output: change definition, affected-requirements list and an agreed basis for the compliance plan.

02Revisit the assumptions behind the safety case

Check fault detection, isolation time, control authority, power and data dependencies, crew effects and interactions with other control functions. Identify which safety requirements and assurance allocations are affected by the revised architecture.

Output: updated safety assessment inputs, design constraints and a record of assumptions that remain valid or need substantiation.

03Decide what evidence can be retained

Review the applicability of earlier qualification, software or hardware assurance, integration and flight-test evidence. Define the new analysis and testing, including relevant failures, transition behaviour and representative configurations. A reused report needs a reasoned applicability assessment.

Output: evidence reuse rationale, revised verification coverage and identified conformity or witnessing needs.

04Close the compliance argument

Bring the reports, results, limitations and configuration records together. Resolve discrepancies and trace the evidence to the affected requirements. Confirm who will make each finding and what remains with the authority.

Output: a reviewable compliance package with clear findings and any remaining actions explicitly identified.

The practical result: the team can see what the change affects, why additional work is needed and which evidence supports the revised design.

Working through a similar change or an unresolved certification question?

Tangible outputs

A package your team
can use and maintain.

We agree the deliverables, inputs, responsibilities and review points at the start. Each output has a defined purpose in the programme.

01 / PLAN

The compliance roadmap

Certification basis inputs, compliance checklist, proposed means of compliance, planned evidence and responsibility assignments.

Used toAlign the engineering work with the approval objectives.

02 / SUBSTANTIATE

The technical evidence

Agreed analyses and reports, test coverage reviews, traceability, configuration references and justified evidence reuse.

Used toExplain how the actual design meets each requirement.

03 / CLOSE

The review and findings record

Technical positions, review comments, issue closure records and delegated findings where applicable and authorised.

Used toMake the status, conclusions and remaining actions clear.

The scope depends on the approval sought, the applicable basis, the maturity of the design and the existing evidence. FAA delegated activities remain subject to the current authorisation and project arrangements.

Working together

Start with the support
you need now.

A focused engagement can resolve a defined question. Ongoing support keeps the certification approach aligned with the design as it develops.

A defined question

Focused compliance review

For a design change, a submission approaching review or an issue that needs a clear technical position.

Starting point
The relevant requirements, design baseline and available evidence.
You receive
Prioritised findings, an assessment of the gaps and practical closure actions.

An agreed body of work

Compliance package development

For a defined system or set of requirements that needs a coherent substantiation package.

Starting point
Agreed scope, inputs, responsibilities and review milestones.
You receive
The planned technical deliverables, traceability and review support.

Alongside your team

Ongoing programme support

For teams needing continuity through architecture decisions, design changes, reviews and authority discussions.

Starting point
A programme review and an agreed set of priorities and responsibilities.
You receive
Regular technical input, maintained actions and support as issues arise.
Safety for your aircraft and certification basis.

Explore Part 23, Part 25, Part 27, eVTOL and new or novel designs, with the safety questions, evidence and guidance for each.

Explore the aircraft pathways →

Useful references

Official guidance and practical context for the work.

Powered-lift certification →System design & analysis →Changed-product guidance →

A practical tool for the industry

Find an FAA designee.
Understand what to check.

Search the consultant DER directory by name, discipline, location or regulatory Part. Compare listings and open the FAA authorisation letter to check the specific scope.

Explore the designee locator 965 public US consultant DER listings · Captured 17 November 2026

Let’s discuss the work

Tell us where the programme stands.

The aircraft or system, the approval sought, the stage of development and the question you need to resolve are enough to start a useful conversation.