TSO finding closure
Closing certification claims that no document substantiates in a TSO program
This supports equipment suppliers whose certification evidence package makes compliance claims that no document actually substantiates. A specialist reads each assertion in the package and follows it to the document meant to support it, separating claims backed by current evidence from claims backed by nothing, by a superseded report, or by a document that says something narrower than the claim. The work runs during the program, before a reviewer finds a claim and asks for the paper behind it. You receive a closure brief listing every unsupported or over-stated claim, an evidence request list for the documents needed to back them, and a disposition package that either ties each claim to current evidence or restates it honestly as open.
When this review is needed
- A reviewer picks a compliance statement and asks for the document that supports it, and none is on file.
- The evidence package was assembled from summaries that assert results without citing the underlying report.
- A claim cites a report that was later superseded, and the claim was never updated.
- A statement claims more than its supporting document actually demonstrates.
The problem
A certification evidence package is a chain of assertions, each of which is only worth the document that stands behind it. Under schedule pressure, packages get written as narratives that assert compliance ahead of the evidence catching up, or that cite a report by title without anyone confirming the report still says what the claim needs. The claims read confidently, the package looks finished, and the weakness is invisible until someone pulls on a single thread and finds the document missing, superseded, or narrower than the sentence that cited it.
What gets reviewed
- Every compliance claim in the evidence package identified and traced to its intended supporting document
- Claims separated into supported, unsupported, or supported by superseded or narrower evidence
- Each cited document checked for currency and for whether it demonstrates what the claim states
- Over-stated claims narrowed to what the evidence actually shows
- Unsupportable claims restated as open items with an evidence path rather than left asserting compliance
- A reconciled package where every claim either cites current evidence or is honestly marked open
What gets validated
- Every compliance claim cites a document that exists and is current
- Each cited document demonstrates at least what its claim asserts, not something narrower
- Claims resting on superseded reports are re-tied to the current revision or reopened
- Over-stated claims are narrowed to the demonstrated result
- Claims with no supporting evidence are restated as open, not left reading as compliant
Evidence normally required
- The certification evidence package or compliance report as drafted
- The underlying reports, analyses, and test results the claims rely on
- The document revision history needed to check currency
- The certification basis and requirements the claims are made against
- Any reviewer comments questioning a specific claim
Common discrepancies
- A claim asserting compliance with no document on file that supports it
- A claim citing a report that was superseded after the claim was written
- A statement claiming a broader result than its cited evidence demonstrates
- A summary that asserts a test outcome without pointing to the test report
What is at stake
An unsupported claim is the finding that damages trust fastest, because once a reviewer finds one claim with nothing behind it, every other claim in the package is suspect and the review turns adversarial. Restoring that trust is slower than closing the original gap, and each unsupported claim either needs a real document produced or has to be walked back, which is uncomfortable to do in front of the authority. A package that reaches service on unsupported claims leaves the supplier asserting compliance it cannot demonstrate if anyone ever asks again.
Move from findings to resolution
Identify the missing data behind the finding.
How the work runs
Trace each claim
Follow every compliance assertion in the package to the document meant to support it.
Test the support
Check each cited document for existence, currency, and whether it demonstrates what the claim states.
Resolve the weak ones
Narrow over-stated claims, re-tie superseded ones, and restate unsupportable claims as open.
Reconcile the package
Deliver a package where every claim cites current evidence or is honestly open, with a disposition package.
What the buyer receives
- A closure brief listing every unsupported, superseded, or over-stated claim
- An evidence request list for the documents needed to substantiate the salvageable claims
- A disposition package that ties each claim to current evidence or restates it as open
Who uses the output
- Certification leadership deciding which claims to substantiate and which to reopen
- Engineering leads producing or retrieving the documents the claims require
- Program management judging schedule exposure before the package meets a reviewer
How the work fits into the transaction or program
This audits the evidence package against its own supporting documents before it faces a reviewer, sitting just ahead of the compliance submittal. It turns a narrative of assertions into a package where every claim is either backed by current evidence or honestly open, so the reviewer never finds a thread that unravels the rest.
Start with a single asset
Confirm each requirement maps to substantiating evidence.
Jurisdiction-specific considerations
FAA and EASA both require that a compliance statement rest on substantiating data, and both treat an unsupported claim as a finding regardless of how the package reads. The claim-to-evidence check is authority-neutral, though the two authorities may hold the same claim to different supporting documents where their bases diverge.
Regulatory limits
The work checks whether claims are supported by current evidence and restates the ones that are not. It does not produce the missing evidence, does not determine airworthiness, and does not accept any claim on behalf of an authority; whether a substantiated claim is sufficient stays with the authority.
What this review does not cover
- Producing or retrieving the substantiating reports and test results
- Rewriting the certification basis to make a claim defensible
- Design or test work to make an unsupportable claim true
Specific to this review
- One unsupported claim discovered by a reviewer taints the whole package, because it converts every other claim from trusted to unverified.
- Over-stated claims are more common than absent ones: the document exists but shows less than the sentence that cites it.
- Superseded evidence is a silent failure, since the claim looked supported the day it was written and quietly detached when the report was revised.
- Restating a claim as open is cheaper and safer than defending it, but it has to happen before the reviewer finds it, not after.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Federal Aviation Administration. FAA type certification process, certification basis establishment, and compliance findings.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
Frequently asked questions
The claim cites a report by title. Is that not enough support?
A citation only holds if the report still exists, is the current revision, and demonstrates what the claim asserts. A title reference can point to a report that was later superseded, or to one that shows a narrower result than the sentence citing it. Support means the document behind the claim actually backs it today, not that a title appears next to the statement.
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.