Release documentation
Authorized release certificate review in the modification baseline file
Every component a modification installs should arrive with an authorized release certificate, and the certificate should still make sense in the context where the part was fitted. This review pairs the component release file with the modification-baseline sources, reading SB records, STC files, equipment lists, and embodiment evidence to confirm that each installed part has release paper matching its identity, condition status, and the regulatory system receiving it. Configuration and asset teams run it when declaring a baseline or preparing for counterparty scrutiny. It produces an exception list of installations whose release documentation is missing, incomplete, or wrong for the context.
When this review is needed
- A modification campaign installed dozens of components and the release file was assembled from kit paperwork nobody has audited.
- Parts were fitted under an STC sourced from another regulatory system and the dual-release question was never settled.
- The equipment list changed during embodiment and it is unclear which installed serial numbers the release file actually covers.
- An upcoming transaction or authority audit will sample release paper against the installed configuration.
The problem
Modification kits arrive as boxes with paperwork packs, and the paperwork gets filed by whoever unpacked the box. When embodiment stretches over months, parts get substituted, serials get swapped between aircraft, and the release file ends up describing the kit as shipped rather than the configuration as installed. STC hardware adds another layer: a certificate acceptable in the exporting system may need specific dual-release blocks to be acceptable in the receiving one, and that detail surfaces only when a trained reader looks.
What gets reviewed
- Each component the embodiment evidence shows installed matched to a release certificate in the file
- Certificate content checked against the part actually fitted: part number, serial, condition status, and quantity
- Dual-release adequacy assessed for parts crossing between FAA and EASA systems under the modification
- Substitutions and serial swaps during embodiment traced so the file reflects as-installed, as opposed to as-shipped
- Equipment-list entries reconciled with the release file so listed hardware has paper and papered hardware is listed
- Certificates examined for completeness: signatures, approval references, and status blocks appropriate to the release
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Send a representative, redacted record set and we will scope the review.
What gets validated
- Every serial number in the embodiment evidence appears on exactly one release certificate consistent with its installation date
- Certificate part numbers match the installed identity, including any re-identification the modification performed
- Parts from the other regulatory system carry the release statements the receiving system requires
- No certificate in the file is orphaned, covering a part the configuration records show was never installed or was later removed
- The condition status on each certificate, new or overhauled or repaired, is coherent with the modification's requirements
Evidence normally required
- The component release file for the modification baseline
- Embodiment evidence and work packages showing what was actually installed
- SB and STC documentation defining required hardware and any re-identifications
- Current and pre-modification equipment lists
- Configuration-control logs covering substitutions during the campaign
Common discrepancies
- Kit paperwork filed as the release record while the installed part is a substituted serial with no certificate on file
- A single-system release for STC hardware that needed dual-release statements in the receiving context
- Certificates present for parts that were returned or superseded during embodiment, masking the absence of paper for what actually flew
- Release documents whose condition status contradicts the modification instruction, such as repaired parts where the SB required new
What is at stake
A part installed without matching release paper is a part whose provenance is open to challenge, and challenges arrive at the worst moments: mid-transaction, during an authority audit, or after an unrelated event puts the aircraft's history under review. Resolution means chasing the certificate from the supplier or installer years after the fact, or removing serviceable hardware because its paper cannot be reconstructed. Either path costs more than the review that would have caught it at filing time.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Build the installed list
Derive what was actually fitted from embodiment evidence and configuration logs, independent of the kit manifests.
Pair parts to paper
Match each installed serial to a certificate and grade the match on identity, status, and context.
Apply acceptance rules
Test cross-system certificates against the receiving authority's release requirements.
Deliver the register
Issue the reconciled register, the exception list, and the sourcing plan for recovery.
What the buyer receives
- An installation-by-installation exception list separating missing, incomplete, and context-inappropriate certificates
- A reconciled register linking each installed serial to its certificate and file location
- A sourcing plan naming, for each exception, the supplier, installer, or authority route likeliest to produce the paper
Who uses the output
- Configuration managers closing the release-paper dimension of the baseline
- Purchasing and warranty staff pursuing certificates from suppliers while records duties still apply
- Transaction teams who would rather present a reconciled register than defend a box of kit paperwork
How the work fits into the transaction or program
Release documentation is where the modification baseline touches the parts market: certificates come from outside the operator and can only be corrected by going back outside. This review therefore runs early in a baseline effort, because its exceptions have the longest recovery lead times, and it exchanges findings with the LLP trace review whenever a certificate anchors a life-limited part's identity.
Jurisdiction-specific considerations
The FAA Form 8130-3 under Order 8130-21 and the EASA Form 1 under Regulation 1321/2014 are parallel instruments with non-identical acceptance rules, and 14 CFR Part 43 governs who may return parts to service on the FAA side. Bilateral arrangements make many certificates acceptable across systems, but only when specific blocks and statements are completed, and modification kits assembled for a global customer base routinely ship with paper optimized for neither system in particular. The review applies the acceptance rules of the system the aircraft actually answers to.
Regulatory limits
The review assesses documentation against the applicable acceptance rules. It does not issue or amend release certificates, does not approve parts for installation, does not perform maintenance releases, and does not decide whether hardware may remain fitted. Those determinations belong to the operator, its maintenance organizations, and the authority.
What this review does not cover
- Physical identification or inspection of installed hardware
- Procurement of replacement certificates or parts
- Judgments on suspected unapproved parts beyond flagging the documentary inconsistency
Specific to this review
- The as-shipped versus as-installed gap is the defining failure mode for modification release files, and it grows with campaign length as substitutions accumulate.
- Orphaned certificates are as diagnostic as missing ones: paper for a part that never flew usually means the paper for the flying part went somewhere else.
- Suppliers retain release records for finite periods, so the practical window for recovering a missing certificate closes years before anyone typically looks.
- Dual-release defects hide in completed-looking forms, because the certificate is genuine and correctly filled for its home system, just insufficient for the receiving one.
Sources
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union Aviation Safety Agency. EASA authorised release certificate for components, equivalent in function to FAA Form 8130-3.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Frequently asked questions
The modification was done by an approved organization. Does that not guarantee the release paper?
The installer's own release covers the work performed, but the component certificates come from upstream suppliers, and file quality depends on how the kit paperwork was checked at receiving. Approved organizations vary widely on this, and the exceptions this review finds are usually receiving-inspection escapes that nobody has looked at since.
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.