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.
Certification / Compliance / Technical judgement
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.
Hussein Khimji · FAA Consultant DER · Electrical Systems Engineering
Start with the decision
Certification support is most useful when it resolves a specific question and gives the engineering team a practical next step.
From planning to substantiation
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.
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.
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.
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 →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 →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 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.
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.
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.
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.
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.
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.
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.
Tangible outputs
We agree the deliverables, inputs, responsibilities and review points at the start. Each output has a defined purpose in the programme.
Certification basis inputs, compliance checklist, proposed means of compliance, planned evidence and responsibility assignments.
Used toAlign the engineering work with the approval objectives.
Agreed analyses and reports, test coverage reviews, traceability, configuration references and justified evidence reuse.
Used toExplain how the actual design meets each requirement.
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
A focused engagement can resolve a defined question. Ongoing support keeps the certification approach aligned with the design as it develops.
A defined question
For a design change, a submission approaching review or an issue that needs a clear technical position.
An agreed body of work
For a defined system or set of requirements that needs a coherent substantiation package.
Alongside your team
For teams needing continuity through architecture decisions, design changes, reviews and authority discussions.
Explore Part 23, Part 25, Part 27, eVTOL and new or novel designs, with the safety questions, evidence and guidance for each.
Useful references
Official guidance and practical context for the work.
A practical tool for the industry
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 2026Let’s discuss the work
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.
Conventional Aircraft
Safety and certification support for fixed wing aircraft and the systems that make them work.
Proposed sector introduction for review.
Rotorcraft
Connect rotorcraft safety, system architecture and certification evidence.
Proposed sector introduction for review.
eVTOL & advanced air mobility
Bring safety and certification thinking into emerging aircraft programmes from the outset.
Proposed sector introduction for review.
Certification & DER support
Tell us about the aircraft or system, the approval sought, its stage of development and the question you need to resolve.
aero@aerospace.consultingA focused review, an agreed compliance package or ongoing support alongside your team.
This opens your email application.
System safety support
Tell us about the aircraft or system, its stage of development and the safety question you need help answering.
aero@aerospace.consultingA focused review, an agreed assessment package or ongoing support alongside your team. We can agree the relevant inputs and scope in the initial conversation.
This opens your email application.
Start a conversation
Tell us about your programme, the system you are developing and the support you need.
aero@aerospace.consultingCertification planning, a system safety review, or ongoing technical support for your team.
This opens your email application.
Experience & approach
Tell us about the aircraft or system, its development stage, your next milestone and the technical question you need to resolve.
aero@aerospace.consultingWe can then agree whether a focused review, a defined work package or ongoing support is the right starting point.
This opens your email application.
AI/ML assurance & certification readiness
Tell us what the AI will do, who will rely on its output, the aircraft or engineering process involved, and the next decision you need to make.
aero@aerospace.consultingWe can agree a focused use-case review, a defined evidence package or ongoing programme support.
This opens your email application.
Specialist aerospace expertise
Aerospace Consulting is led by Hussein Khimji, an FAA Designated Engineering Representative in systems and equipment, with a focus on system safety, flight controls and avionics.
We work with aircraft developers and systems suppliers to connect technical decisions, safety assessments and certification evidence.
This is the proposed introduction. The full About page will add your approved biography and associate expertise.
Systems engineering & development assurance
Tell us about the aircraft or system, its intended function, stage of development and the support you need.
aero@aerospace.consultingA focused engineering review or ongoing support with requirements, architecture and development assurance.
This opens your email application.
A technical conversation
Tell us about your aircraft or system, the reference you are using and the decision your team needs to make.
aero@aerospace.consultingWe can help connect the guidance to your safety, systems engineering or certification work.
This opens your email application.