Flight-deck equipment certification evidence for TSO authorization

When this review is needed

• A flight-deck control or display unit is heading for TSO authorization and its data package has not been mapped to the minimum performance standard.
• Environmental qualification exists but has not been tied to the DO-160G categories the standard calls out.
• The article's software data has to be shown at the assurance level the flight-deck function requires.
• A TSO application needs a compliance matrix that points each requirement to a specific test or analysis.

The problem

A flight-deck equipment package often holds qualification reports, software artifacts, and a design description, but not a matrix that ties each line of the minimum performance standard to the evidence that meets it. Human interface behavior is easy to describe and hard to prove, and a package that asserts the crew interface works without test evidence behind each claim leaves the assessor to reconstruct the compliance argument. The gap between having the data and having it mapped is where TSO applications stall.

What gets reviewed

• The applicable minimum performance standard identified and turned into a compliance matrix
• Human interface and control behavior tied to the requirements they satisfy with test evidence
• Display response and annunciation reconciled with the article's functional requirements
• DO-160G environmental qualification mapped to the categories the standard and installation demand
• DO-178C software lifecycle data matched to the design assurance level the function requires
• The article's configuration and part number reconciled with the qualified test specimens

What gets validated

• Every line of the minimum performance standard maps to a specific test, analysis, or inspection in the matrix
• Human interface claims are supported by test evidence rather than a design description alone
• The DO-160G categories qualified to cover the environment the standard specifies for the article
• The DO-178C assurance level matches the criticality of the flight-deck function the equipment performs
• The configuration of the qualified specimens matches the article the TSO application covers

Evidence normally required

• The applicable minimum performance standard for the flight-deck article
• DO-160G environmental qualification reports for the equipment
• DO-178C software lifecycle data and the plan for software aspects of certification
• The human interface description and any test data for control and display behavior
• The article's design data, configuration, and part number definition

Common discrepancies

• A minimum performance standard requirement with no matrix entry pointing to evidence
• Human interface behavior described but not backed by a test result
• Environmental qualification run to a category the standard does not accept for the article
• A qualified specimen configuration that does not match the article being submitted

What is at stake

A TSO application submitted without a clean compliance matrix invites questions that reopen the whole package, and each round costs weeks. If the software assurance level or an environmental category turns out to be wrong for the article, the correction can mean re-verification or re-test, which pushes the authorization past the window the installation program was counting on.

How the work runs

What the buyer receives

• An article-specific evidence gap list against the minimum performance standard
• A trace map linking each requirement to the test or analysis that meets it
• A closure sequence for the open items ahead of the TSO application

Who uses the output

• Certification engineers assembling the TSO data package
• Suppliers deciding which qualification or software evidence still has to be produced
• Program leads sequencing closure against the TSO application date

How the work fits into the transaction or program

The support sits ahead of the TSO application, converting the supplier's qualification and software data into a mapped compliance matrix the assessor can follow. The gap list it produces drives the remaining test and analysis, and the matrix carries forward into any installation approval that later cites the TSO article.

Jurisdiction-specific considerations

FAA TSO authorization and the EASA ETSO route rest on largely aligned standards but diverge in application detail and in which deviations each accepts. The mapping notes where a package built for one route needs added substantiation for the other so a supplier pursuing both does not assume a single matrix covers each.

Regulatory limits

The support prepares and maps the evidence for a TSO application. It does not grant the TSO authorization, approve the article, or make an airworthiness determination, and a TSO article still requires separate installation approval on any given aircraft. Those decisions rest with the authority.

What this review does not cover

• Running the environmental, software, or human interface testing
• Developing the article's design or its software
• Issuing the TSO authorization or any installation approval

Specific to this review

• A TSO authorization covers the article against its minimum performance standard, not its installation, so a clean TSO package still leaves the installation approval to be earned separately on each aircraft.
• Human interface requirements are the most common place a flight-deck package is described but not tested, because the behavior is easy to write down and easy to leave unverified.
• A specimen configuration that drifts from the submitted article quietly invalidates otherwise good qualification data, so the matrix ties test results to the exact part number.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits