Equipment certification
Airborne electronic equipment certification data support
Airborne electronic equipment certification is the path a supplier follows to authorize an electronic article and substantiate its fitness for installation. It is used by avionics and equipment teams whose box carries digital function, processing, or a data interface that an authority will examine against an article authorization and the installed environment. The data support covers the certification basis, DO-160 environmental qualification, and software and hardware lifecycle evidence traced to the assigned assurance level. You receive a gap read against the applicable standards and a structured evidence set ready for review.
When this review is needed
- A new electronic box is heading toward an article authorization and the evidence has to be built from the certification basis up.
- An existing article gains a digital function or interface, and the software and hardware data has to be brought current with the change.
- A program needs an independent read of the package before the certification basis is locked with the authority.
- Findings against the qualification or lifecycle data have stalled the program and the evidence needs reconciling against the standards.
The problem
Electronic equipment certification is rarely held up by the circuit design. It is held up by the data that proves the box behaves across its environment and its function. Requirements drift as firmware iterates, the DO-160 test matrix lags the build, and the software and hardware lifecycle data is assembled late and at different assurance levels than the function actually carries. A package that reads cleanly in isolation falls apart once a reviewer traces a requirement to its evidence.
What gets reviewed
- The certification basis and the article authorization the electronic box is pursued under
- DO-160 environmental qualification scoped to the installed location and power source
- Software lifecycle data matched to the level the function's failure condition assigns
- Hardware lifecycle data for any complex programmable device the box contains
- Requirements and verification traceability from the box definition through test
- The interface and data-bus behavior the installation will depend on
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Identify what is missing against the means of compliance.
What gets validated
- Every box-level requirement maps to a means of compliance and substantiating evidence
- DO-160 categories cover the temperature, power, vibration, and emissions the install demands
- Software lifecycle data is consistent with the assigned software level and its objectives
- Hardware lifecycle data addresses the design assurance the device complexity warrants
- Derived requirements from the electronics are fed back into the safety assessment
Evidence normally required
- The draft or current certification basis and means-of-compliance plan
- The box requirements set and any traceability already in place
- DO-160 qualification test plans and reports assembled so far
- Software and hardware lifecycle data at its current state
- Open findings or prior authority correspondence if a program is in progress
Common discrepancies
- DO-160 qualification run against categories that do not match the installed environment
- Software level claimed below the function's failure-condition classification
- Hardware lifecycle data absent for a programmable device treated as if it were simple
- Box requirements with no traceable verification result behind a met status
- Derived electronic requirements that never returned to the safety assessment
What is at stake
An article whose qualification and lifecycle data do not trace cleanly draws findings that cycle for months. The cost lands on the development budget and the time to first installation, and each review cycle pulls engineering off the next box.
How the work runs
Fix the article basis
Confirm the certification basis, the article authorization, and the standards the electronic box is pursued under.
Scope the qualification
Tie the DO-160 categories to the installed location and power source so the environmental case matches the install.
Trace the lifecycle data
Map software and hardware evidence to the assurance level the function's failure condition assigns and find the gaps.
Package the evidence
Reconcile the matrix against current data and hand over a prioritized closure list for the submittal.
What the buyer receives
- A gap read against the applicable article authorization and standards
- A reconciled compliance matrix tied to the current qualification and lifecycle evidence
- A traceability view from box requirements through verification
- A prioritized list of the data needed to close the package
Who uses the output
- Certification leads sequencing the submittal for the electronic article
- Engineering teams closing the qualification and lifecycle gaps the read surfaces
- Program management timing the box against the platform it installs into
How the work fits into the transaction or program
The work strengthens the supplier's own electronic-article program before the basis is fixed with the authority. It sits ahead of qualification testing so the DO-160 categories are chosen as a design input, and it pairs with a focused matrix review when the entries alone need checking.
Start with a single asset
Confirm requirements map to substantiating evidence.
Aircraft-specific considerations
The environmental category an electronic box has to meet is set by where it mounts and what powers it, so a unit destined for a pressurized bay carries a different DO-160 profile than one bound for an unpressurized zone. The data support keeps the category selection tied to the intended installation rather than to a generic lab run.
Regulatory limits
Endeavor Elements supports the applicant's electronic-article data. It does not grant an article authorization, make compliance findings for the authority, or warrant that the box will be accepted. The applicant owns the submission and the authority owns the decision.
What this review does not cover
- Granting an article authorization or any design approval
- Acting as the authority or signing compliance findings
- Running the DO-160 qualification testing in a laboratory
Specific to this review
- The environmental qualification an electronic box needs is set by where it sits and what powers it, so the DO-160 category selection is a design input rather than a test afterthought.
- The software and hardware assurance levels follow the function's failure-condition classification, and a mismatch between the claimed level and the safety assessment is a frequent finding.
- Firmware iteration tends to outrun the qualification matrix, leaving test evidence tied to a build the box has already moved past.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
RTCA. Environmental qualification test categories and procedures referenced by TSO and equipment qualification.
RTCA. Objectives and lifecycle data for airborne software assurance, by design assurance level (DAL A-E).
RTCA. Design assurance objectives and lifecycle data for airborne electronic hardware (FPGA/ASIC/PLD).
Frequently asked questions
How do you decide the software and hardware assurance levels?
They follow from the function's failure-condition classification in the safety assessment, not from the box itself. The read checks that the lifecycle data matches the level the function carries and flags where a claimed level sits below the hazard.
Can you work from a partial DO-160 campaign?
Yes. A common engagement starts from a qualification campaign in progress, reconciles the categories already tested against the installed environment, and identifies the runs still owed before the basis is locked.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Walk through your situation with an engineer who has done this work.