Qualification testing
Qualification-test-report review for avionics and equipment suppliers
A qualification-test-report review checks whether a supplier's environmental test reports actually substantiate the qualification claimed. It is for avionics and equipment teams whose DO-160 test reports have to hold up against the test plan and the installation environment before submittal. The review covers the test categories run against the categories the environment requires, the report content against the plan, and the test-article configuration against the certified build. You receive an assessment of qualification coverage and a list of categories, results, or report records that are missing, out of tolerance, or run against the wrong configuration.
When this review is needed
- Qualification testing is complete and the reports have to be confirmed against the categories the installation environment demands.
- The article changed after testing and no one has checked whether the reports still describe the built configuration.
- Tests were run by more than one lab and the reports differ in format, tolerance, or category coverage.
- A reviewer is asking which environmental categories were tested and where the results sit against the limits.
The problem
Environmental qualification is expensive to run and easy to misrepresent on paper. A category gets tested to a lower level than the installation needs, a result sits at the edge of tolerance without being flagged, or the unit on the shaker table is an earlier build than the one the data package describes. The reports look complete because they are bound and signed, but coverage against the actual environment and traceability to the actual article are separate questions that a glance at the cover page does not answer.
What gets reviewed
- The environmental categories tested against the categories the installation requires
- Test levels and durations run against the levels the environment defines
- Report content against the test plan and the procedures it called for
- Results against the pass criteria, including margins and flagged anomalies
- The test-article configuration against the build the data package describes
- Consistency across reports where more than one lab or campaign was involved
What gets validated
- Every environmental category the installation requires has a test report behind it
- Test levels and durations match what the environment and plan specify
- Each report follows the test plan and the procedures it referenced
- Results meet the pass criteria, with margins and anomalies recorded
- The test-article configuration matches the certified build the data describes
- Re-tests after a failure are traced and the qualifying run is identified
- Reports from different labs are consistent in category coverage and tolerance
Evidence normally required
- The environmental qualification test reports for the article
- The qualification test plan and the environmental categories it defines
- The installation environment the article is qualified for
- The test-article configuration records for each test run
- Any failure and re-test history during the qualification campaign
Common discrepancies
- An environmental category the installation requires with no test report behind it
- Test levels run below what the installation environment demands
- Results sitting outside tolerance without being flagged as a failure
- A test article in an earlier configuration than the certified build
- Re-tests after a failure with no clear identification of the qualifying run
- Reports from separate labs that disagree on category coverage or pass criteria
What is at stake
A qualification gap found in review is a gap that can only be closed by re-testing, which means lab time, schedule, and a re-opened data package. A report tied to the wrong configuration is worse: it can invalidate qualification the program believed it already held, putting the test campaign back on the critical path late in the program.
Move from findings to resolution
Identify gaps against the means of compliance.
How the work runs
Define the environment
Confirm the environmental categories the installation requires from the certification basis and the article's intended location.
Map the coverage
Match each required category to a test report and flag categories with no report or with levels run too low.
Read the results
Check report content against the plan, confirm results against pass criteria, and trace any failure to its qualifying re-test.
Tie to the build
Confirm each report's test-article configuration matches the certified build and deliver a prioritized closure list.
What the buyer receives
- An assessment of qualification coverage against the required environmental categories
- A list of categories, results, or reports that are missing or out of tolerance
- A configuration check tying each report to the article build it tested
- A prioritized closure list separating re-test needs from documentation gaps
Who uses the output
- Certification leads confirming qualification before submittal
- Hardware and test engineering teams closing the coverage gaps
- Program management deciding which gaps require re-test
How the work fits into the transaction or program
The review checks the qualification layer that the hardware and equipment evidence rests on. It pairs with a configuration-management evidence review when the question is which build was tested, and with a tool-qualification evidence review when the test setup or data reduction relied on qualified tools.
Start with a single asset
Confirm requirements trace through verification.
Aircraft-specific considerations
The environmental categories an article must meet follow its installation: a unit in an unpressurized, high-vibration zone faces different temperature, altitude, and vibration categories than one in a controlled bay. The review checks the tested categories against the environment the installation actually presents, so the qualification coverage is judged against where the article goes rather than a generic profile.
Jurisdiction-specific considerations
FAA and EASA reference the same RTCA and EUROCAE environmental standard, so the test categories and procedures align closely. What can differ is how the qualification evidence is folded into the wider submittal, so the review checks coverage and traceability against the environment the basis defines regardless of which authority the package is bound for.
Regulatory limits
Endeavor Elements checks the applicant's qualification test reports for completeness, consistency, and traceability. It does not perform the testing, make compliance findings, or issue any approval. The applicant and the authority keep their roles.
What this review does not cover
- Performing the environmental qualification testing
- Making official compliance findings or issuing any approval
- Operating the test lab or reducing the supplier's test data
Specific to this review
- Qualification coverage and qualification traceability are separate failures: a report can cover the right category and still describe the wrong test article.
- A result at the edge of tolerance that is not flagged reads as a pass to a casual look and as a finding to a reviewer who checks the margins.
- A configuration mismatch can invalidate qualification the program thought it held, because the data no longer describes the article that was built.
- When categories are split across labs, the coverage gap usually hides in the seam between two reports rather than inside either one.
Sources
RTCA. Environmental qualification test categories and procedures referenced by TSO and equipment qualification.
RTCA. Design assurance objectives and lifecycle data for airborne electronic hardware (FPGA/ASIC/PLD).
SAE International. Development assurance process at aircraft and system level, including requirements capture and validation.
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Frequently asked questions
Do you run the qualification testing?
No. The review checks the reports from testing already performed: whether they cover the required categories, meet the pass criteria, and describe the right article. The testing itself stays with the supplier and its lab.
What if a report turns out to describe an earlier configuration?
That is one of the more serious findings, because it can invalidate qualification the program believed it held. The review flags it, traces what the report actually tested, and identifies whether a re-test is needed or the configuration question can be resolved on paper.
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.