HomeExperience & Approach

Experience & approach

Technical depth.
Practical judgement.

Safety, systems engineering and certification, considered together.

We help aircraft developers and systems suppliers work through the decisions that affect their design, their safety case and the evidence needed for certification.

Explore our work

Grounded in aircraft development

Experience on both sides
of the technical discussion.

Understanding the design matters. So does knowing how to explain it, test it and support the compliance argument when it is reviewed.

2018 onwards

Aerospace Consulting

Certification, system safety & systems engineering

Supporting aircraft developers and suppliers through requirements, architecture, safety assessments, design reviews and verification. Coordinating technical work with delegates and certification authorities.

Aircraft systems

Flight controls & integration

Systems engineering & technical substantiation

Flight controls and fly by wire, aircraft door systems, integration and testing. Experience spanning development, design changes, flight readiness and in service support.

Development & verification

Aircraft development

Systems engineering & aircraft development

Flight control work packages, technical requirements and ground test planning, alongside production liaison, configuration management and mass properties.

Engineering experience of Hussein Khimji.

Representative work

The questions behind
the deliverables.

Anonymised summaries drawn from our technical work. Each shows the engineering question, the contribution and the kind of output involved.

01

Advanced aircraft · Actuation

Does the architecture support the safety requirement?

Developing a preliminary safety argument as the system design evolves.

Our contribution & work products

Relate failure conditions to the proposed architecture, examine the assumptions behind fault tolerance and monitoring, and trace the allocated safety requirements into the supplier design.

Work products
PSSA development, fault tree review, safety requirements and a clear record of assumptions and open issues.
What the work makes visible
Where the architecture supports the safety case and where further design work or evidence is still needed.
Explore system safety →
02

Rotorcraft · Fly by wire

Does the verification actually cover the requirement?

Reviewing evidence for a complex flight control system.

Our contribution & work products

Follow the requirement into the test approach, identify what is physically tested and what is simulated, and check that the tested configuration matches the design baseline being claimed.

Work products
Technical review comments, requirement coverage questions, configuration checks and actions to close evidence gaps.
What the work makes visible
Partial coverage, unsupported assumptions and the additional analysis or testing needed before closure.
Explore systems engineering →
03

Conventional aircraft · Design changes

What changes in the compliance argument?

Working through the technical implications of an aircraft system change.

Our contribution & work products

Define the change, identify affected interfaces and safety assumptions, and establish how existing evidence can be used and what additional substantiation is required.

Work products
Requirements and safety assessment contributions, design review material, verification planning and technical substantiation.
What the work makes visible
A defensible connection between the changed configuration, affected requirements and supporting evidence.
Explore certification support →
04

Aircraft & system suppliers · Interfaces

Who owns the requirement, assumption and evidence?

Bringing aircraft and supplier responsibilities into a consistent development approach.

Our contribution & work products

Work across the aircraft and system boundary to clarify allocated functions, interface assumptions, development assurance responsibilities and the evidence each team must provide.

Work products
Requirements and interface reviews, agreed technical actions, assurance planning contributions and coordinated review material.
What the work makes visible
Gaps between teams that might otherwise remain hidden until integration or certification review.
Explore development assurance →

These summaries describe technical contributions. They do not imply that a particular aircraft or programme has received certification.

How we work

Start with the engineering.
Keep the evidence connected.

Clear reasoning, direct communication and an agreed next step. The work should help your team make a decision and move the programme forward.

  1. 01

    Establish the real question

    Understand the system, intended operation, design baseline and decision that needs to be made. Agree the scope and what a useful output looks like.

  2. 02

    Test the assumptions

    Examine the failure effects, interfaces, independence, monitoring and operating assumptions that carry the safety or compliance argument.

  3. 03

    Develop the evidence

    Connect requirements, analyses and verification to the actual configuration. Make limitations and unresolved items visible.

  4. 04

    Work the issue to closure

    Review the response, assess changes and follow actions through to the supporting evidence. Keep the technical position clear for the team and the reviewer.

Our technical foundation

Safety and development assurance are part of the same programme.

Our methods draw on ARP4761A for safety assessment and ARP4754B for aircraft and systems development. The applicable standards, revisions and authority acceptance are established for each project.

Safety approach →Development approach →Technical references →

Background & authorisation

Specific credentials.
Clear responsibilities.

Consulting support and delegated findings have different roles. We establish the required specialist coverage and approval responsibilities at the start of an engagement.

FAA Consultant DER

Hussein is listed in the FAA’s public directory under Electrical Systems Engineering for Parts 23, 25 and 27.

Any delegated finding is subject to the current authorisation, its limitations and the applicable project arrangements. DMS remains the official record.

Previous Transport Canada delegation

Former Design Approval Designee, including aircraft door mechanical systems.

Aerospace engineering education

Bachelor of Applied Science, Engineering Science, aerospace engineering, University of Toronto.

Working together

The right involvement
for your programme.

Work directly with Hussein, with specialist associates brought in where the agreed scope calls for additional expertise or delegated authority.

A defined question

Focused technical review

An assessment, architecture, compliance position or verification package that needs a clear technical review.

An agreed deliverable

Defined work package

Development or review of a safety, systems or certification package with agreed inputs, outputs and responsibilities.

Continuity as the design evolves

Ongoing programme support

Regular technical involvement alongside your team, with a retainer and priorities agreed around the programme’s needs.

Start with a conversation

Tell us what you are building.
And where you need clarity.

The aircraft or system, its development stage, your next milestone and the technical question in front of you.