Release documents
Cessna Citation Longitude authorized release documentation records review
This review examines the authorized release documents behind the components on a Cessna Citation Longitude and confirms each one is valid, complete, and tied to an installation record. It is meant for a records team or buyer who must trust that every installed part arrived with a proper release. We check FAA Form 8130-3 and EASA Form 1 entries, test dual-release validity, and match each certificate to the part it installed. You receive an exception list, a source map, and a closure plan for the component release file on this tail.
When this review is needed
- A transaction requires proof that every installed component came with a valid release.
- A component was installed against a release whose dual-release status was never confirmed.
- The aircraft is transferring between FAA and EASA operators and the release forms must satisfy both.
- A release certificate is on file but no installation record shows where the part actually went.
The problem
A release certificate on file looks like proof, but a certificate only means something when it is valid, matches the part, and links to an installation. On a Citation Longitude, components change during warranty work and modifications, and a form can end up in the file with no record of which position it filled. A missing block on a Form 8130-3 or an unconfirmed dual release quietly undermines the very traceability the certificate was meant to provide.
What gets reviewed
- Validity of each FAA Form 8130-3 and EASA Form 1 against its required fields and signatures
- Dual-release status confirmed where the part must be acceptable to both authorities
- Each release certificate matched to the installation record for the part it covers
- Serial and part numbers on the certificate reconciled with the installed configuration
- Release documents for major components including the two HTF7700L engines and rotables
- Consistency of the component release file across warranty-era part changes
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
- Each release form carries the required blocks, signatures, and approval reference
- Dual release is stated on the certificate where both authorities must accept the part
- Every release certificate links to an installation record placing the part on the aircraft
- Serial and part numbers on the release match the part recorded as installed
- No installed component is missing a release certificate in the file
Evidence normally required
- The component release file with FAA Form 8130-3 and EASA Form 1 certificates
- Installation records and work orders placing each part on the aircraft
- The current configuration list for reconciliation of serial and part numbers
- Release documents for the two HTF7700L engines and major rotables
- Any warranty or modification records that changed installed components
Common discrepancies
- A release certificate on file with no installation record showing where the part went
- A Form 8130-3 missing a required block or signature that undermines its validity
- A part installed for a dual-authority operator with only a single-authority release
- A serial number on the release that does not match the part recorded as installed
What is at stake
An installed part whose release is invalid or cannot be tied to its installation is treated as undocumented, which can force removal and reinstallation with a proper certificate. In a transaction, a thin release file drives price concessions or holdbacks. If the aircraft moves between authorities, a release valid for one and not the other can block acceptance until each certificate is re-verified.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Inventory the release file
List every release certificate on file and the component it is meant to cover.
Test validity
Check each form for required fields, signatures, approval reference, and dual-release status where needed.
Match to installation
Link each certificate to the installation record and reconcile serial and part numbers with the configuration.
Report the gaps
Deliver the exception list, source map, and a closure plan for the component release file.
What the buyer receives
- An exception list of invalid, unmatched, or missing release documents with their components
- A source map linking each release certificate to the part and installation it covers
- A closure plan naming the release evidence needed to complete the component file
Who uses the output
- Records teams confirming that every installed part carries a valid release
- Buyers verifying component traceability before pricing the aircraft
- CAMO leads preparing the aircraft for acceptance onto a new register
How the work fits into the transaction or program
Release documents are the joints of component traceability, linking a part's pedigree to its place on the aircraft. This review tests those joints before a transaction or a register change relies on them. It supports the LLP-trace and repair-approval reviews, which each depend on the same release certificates holding up under inspection.
Aircraft-specific considerations
The Citation Longitude is a recent type, so many components are original or first-generation replacements, and warranty work can swap parts without the release always following into the file. With two HTF7700L engines and a G5000 avionics suite, the component release file mixes engine, airframe, and avionics certificates, and each family carries its own release conventions that have to be checked in place rather than assumed uniform.
Jurisdiction-specific considerations
An FAA operator relies on FAA Form 8130-3 while an EASA operator relies on EASA Form 1, and a part crossing between them needs a dual release or an accepted equivalent. A component release file built entirely under one authority can leave a cross-border transfer short of the release evidence the receiving authority requires.
Regulatory limits
This review reports on the validity and traceability of release documents. It does not issue or endorse any release certificate, approve a part for installation, determine airworthiness, or replace the operator's control of its component records.
What this review does not cover
- Issuing or reissuing any authorized release certificate
- Physical inspection or removal of installed components
- Approval of a part for continued service
Specific to this review
- A release certificate proves nothing on its own until it is tied to the installation record for the part it covers.
- Dual release is easy to overlook, and a single-authority release can block acceptance the moment the aircraft crosses registers.
- Warranty-era part swaps on a young Longitude frequently leave the release in the shop file rather than the aircraft file.
- A missing block or signature on a Form 8130-3 can invalidate the release even when the part itself is entirely serviceable.
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
Every component has a release certificate on file. What is left to check?
Having a certificate is only the first condition. It also has to be valid, match the part by serial and number, and connect to a record showing where the part was installed. This review tests those links so an invalid form or an unmatched certificate is caught before it stalls a transaction or a register change.
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.