Certification evidence
ETSO and TSO evidence reuse review for easa validation of a tso article
certification liaison, Certification engineer, Product manager use this page when EASA validation of a TSO article depends on records that have moved across revisions, suppliers, or workstreams. EE checks FAA TSO data index, ETSO requirement comparison, deviation list, test reports against the applicable basis, plan language, and source records. Findings are written as evidence gaps, not approval decisions. The deliverable is a ranked discrepancy log with the evidence trail needed for closure.
When this review is needed
- EASA validation of a TSO article has created a gate where document titles are no longer enough.
- Program leaders need a ranked list of etso and tso evidence reuse review blockers rather than another unfiltered file dump.
- The review notes that evidence was copied from earlier work and its applicability must be tested.
- Authority, DER, ODA, or internal reviewers are expected to sample the record trail.
The problem
Teams usually know the files exist, but they do not always know whether FAA TSO data index still agrees with test reports. That uncertainty burns review time when a sampled citation fails.
What gets reviewed
- Inventory FAA TSO data index and record its source, owner, and controlled revision.
- Match ETSO requirement comparison against the current baseline and the applicable plan language.
- Follow deviation list through downstream reports, summaries, and closure notes.
- Flag test reports when it refers to a superseded configuration or unresolved deviation.
- List missing source records needed before reviewers can rely on the package.
What gets validated
- A cited record passes only if its identifier, title, and revision match the controlled index.
- Configuration alignment is tested between FAA TSO data index and test reports; conflicting serials, drawings, or baselines fail.
- The review notes that evidence type is checked against the claim, so analysis cannot silently replace a promised test or inspection.
- Open exceptions fail the gate when they have no owner, due path, or technical disposition.
- Downstream documents are sampled for references that still point to superseded material.
Evidence normally required
Common discrepancies
- Failure modes: assuming full reuse when the ETSO references a different standard revision.
- missing deviations that block acceptance.
- a DDP that does not reflect the reused evidence.
What is at stake
Late discovery turns a records problem into a program problem. Reviewers may pause sampling, ask for a corrected baseline, or require new evidence before the package can move forward.
Move from findings to resolution
Identify gaps against the means of compliance.
How the work runs
Frame ETSO TSO
Confirm the exact event, affected file set, buyer role, and decision standard before any faa tso data index is treated as sufficient.
Trace Reuse Review
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Validation Article
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package FAA Data
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
- Gap log for etso and tso evidence reuse review
- Cross reference table
- Document retrieval list
- Disposition worksheet
- Submittal readiness note
Who uses the output
- certification liaison decides which exceptions block the next gate.
- Certification engineer updates the plan, matrix, or report index.
- Product manager tracks owner responses through closure.
How the work fits into the transaction or program
How much of an existing FAA TSO evidence package can be reused for an EASA ETSO authorization, because bilateral acceptance and the CS-ETSO index determine what transfers directly, what needs a Declaration of Design and Performance, and what needs a deviation. The evidence set centers on the mapping of FAA TSO data to the CS-ETSO index and its referenced standard, the bilateral/TIP acceptance basis, the DDP and any deviation requests, and the gaps requiring additional data. The likely weak points are assuming full reuse when the ETSO references a different standard revision, missing deviations that block acceptance, and a DDP that does not reflect the reused evidence; Pairs with the etso-deviation product page: that page frames the path, this reviews the reuse evidence. The output gives the certification liaison a cleanup register for ETSO and TSO evidence reuse review for easa validation of a tso article before EASA validation of a TSO article.
Start with a single asset
Confirm requirements trace through verification.
Regulatory limits
The review is an evidence and consistency check only. EE does not approve data, accept certification credit, make airworthiness determinations, or act for FAA, EASA, a DER, a DAR, or an ODA unit member.
What this review does not cover
- Design approval
- Regulatory acceptance decisions
- Laboratory testing or retesting
- Acting as DER, DAR, ODA unit member, or authority
Specific to this review
- test reports is often where stale evidence surfaces first, because reports preserve old titles long after plans change.
- A complete index is weaker than a resolved index; the review asks whether each citation can actually be used.
- Supplier or lab records need the same baseline discipline as internal certification data.
- A discrepancy should name the blocked decision, not merely the document where the problem was found.
- The scope uses the ETSO TSO Evidence Reuse question as the control point, so the review stays tied to EASA validation of a TSO article and the buyer decision behind it.
- The evidence starts with FAA TSO data index and follows Review EASA Validation Article references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for certification liaison: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Certification FAA Data Actually questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Gap log for etso and tso evidence reuse review; it gives the next reviewer a precise map instead of another broad request for a better file.
Sources
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
European Union Aviation Safety Agency. EASA authorised release certificate for components, equivalent in function to FAA Form 8130-3.
Frequently asked questions
What makes this evidence review different from a general file audit?
The scope is tied to etso tso evidence reuse and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block easa validation of a tso article or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is faa tso data index, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives certification liaison a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
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.
Talk through the aircraft, records, evidence, deadline, and next useful step.