ETSO compliance support and TSO-to-ETSO mapping for suppliers

When this review is needed

• An article authorised under a TSO is being taken into the EASA system and the differences against the matching ETSO have to be mapped.
• A new article is pursuing an ETSO directly and the declaration of design and performance has to be built against CS-ETSO.
• The FAA and EASA standards invoked for the same article function diverge and the divergence has to be reconciled with evidence.
• A supplier wants an independent read of the ETSO evidence before the application reaches EASA.

The problem

An ETSO points to its own minimum performance standard under CS-ETSO, and assuming a TSO article transfers unchanged is where these programs slip. The invoked standards differ in revision or in specific clauses, the declaration of design and performance is treated as a formality rather than a substantiated claim, and the qualification evidence assembled for the FAA route is not re-examined against the EASA categories. An ETSO application that rests on an unreconciled TSO package collects findings that an early difference map would have avoided.

What gets reviewed

• The applicable ETSO under CS-ETSO and the standard it invokes
• Differences between the ETSO standard and any TSO basis the article already holds
• The declaration of design and performance and the claims it carries
• The article specification and marking against ETSO requirements
• Environmental qualification against the EASA-invoked categories
• Software and hardware lifecycle data against the assurance the ETSO expects

What gets validated

• The article maps to the correct ETSO and the standard revision it invokes
• Each difference from the TSO basis is identified and addressed with evidence
• The declaration of design and performance is backed by substantiating data
• Article specification and marking meet ETSO requirements
• Environmental qualification covers the EASA-invoked categories
• Software and hardware lifecycle data satisfy the assurance the ETSO expects
• Claims carried over from the FAA route are re-validated rather than assumed

Evidence normally required

• The applicable ETSO reference and the article it covers
• Any existing TSO authorisation data for the same article
• The article specification, drawings, and marking data
• Qualification, software, and hardware evidence already assembled
• Prior EASA correspondence if the application is in progress

Common discrepancies

• A TSO package assumed to transfer to the ETSO without a difference review
• An ETSO standard revision that differs from the TSO basis on specific clauses
• A declaration of design and performance with claims that lack substantiation
• Qualification categories that satisfy the FAA route but not the EASA invocation
• Marking data that meets TSO requirements but not the ETSO ones
• Software or hardware data not re-checked against the ETSO assurance expectations

What is at stake

An application that carries unreconciled differences between the standards stalls while EASA asks for the evidence the supplier assumed was already covered. The delay pushes the European market entry and ties up the team that should be on the next authorisation.

How the work runs

What the buyer receives

• A difference map between the ETSO standard and the article's TSO basis
• A gap assessment against the applicable ETSO under CS-ETSO
• A declaration of design and performance backed by traced evidence
• A prioritized list of the data needed to complete the ETSO application

Who uses the output

• Certification leads preparing the ETSO application for EASA
• Compliance and engineering teams closing the mapped differences
• Program management sequencing the European authorisation work

How the work fits into the transaction or program

The work supports the supplier's own ETSO application and any mapping from an existing TSO. It reconciles the two standards before submittal so the EASA review starts from a difference map rather than from an assumption that the FAA package transferred.

Regulatory limits

Endeavor Elements supports the applicant's ETSO evidence. It does not issue an ETSO authorisation, decide that a TSO article is accepted in the EASA system, or guarantee acceptance. An ETSO is a separate authorisation, not an automatic recognition of a TSO.

What this review does not cover

• Issuing an ETSO authorisation or any approval
• Determining that a TSO article is automatically accepted by EASA
• Performing the qualification testing itself

Specific to this review

• An ETSO invokes its own minimum performance standard under CS-ETSO, and that standard can differ in revision or clauses from the TSO an article already holds.
• A TSO authorisation is not automatically recognised in the EASA system; an ETSO is a distinct authorisation that requires its own declaration of design and performance.
• The declaration of design and performance is a substantiated claim under the EASA route, and treating it as a paperwork step is a frequent source of follow-up questions.
• Qualification evidence built for the FAA route can map to different EASA-invoked categories, so re-checking the categories rather than copying them is where the difference work pays off.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits