Skip to content

Release documentation

Authorized release document review for operators returning a leased aircraft

This review confirms that every component subject to the lease's documentation standard has an acceptable authorized release certificate on file before redelivery. It pairs FAA Form 8130-3 and EASA Form 1 certificates with installation records, checks dual-release coverage where the aircraft will change registry, and rebuilds the component release file into the order a lessor inspection expects. Operators typically commission it once the return workscope is defined. Maintenance leadership receives a component-level exception list, source requests for missing certificates, and a release file structured for handover.

When this review is needed

  • The return workscope is set and the component release file has grown by accretion over several years of operation.
  • Rotables were sourced from multiple pools and stockrooms during the lease, each with its own paperwork habits.
  • The aircraft will move to a different registry at return and dual-release coverage was never systematically checked.
  • A pre-return self-audit found certificates filed by purchase order with no link to what is actually installed.

The problem

Release certificates arrive with parts and get filed where receiving puts them, while installation happens on the hangar floor against a work order. Years later the connection between a certificate in a folder and a unit on the aircraft exists mostly in people's memory. A lessor's inspector will pull an installed component's serial number and ask for its release, and the operator has days, not months, to produce it.

What gets reviewed

  • The component release file inventoried and indexed against installed serial numbers
  • FAA Form 8130-3 and EASA Form 1 certificates checked for completeness, block by block, on sampled and critical items
  • Dual-release status established for components on an aircraft changing registry
  • Installation records tied to each certificate through work orders and log entries
  • Certificates for on-condition and hard-time components verified against the lease's documentation standard
  • Loose or orphaned certificates matched to parts or flagged for disposition

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

  • The serial number on each certificate matches the installed unit, and the certificate's issue date precedes installation
  • Work descriptions and status blocks on each certificate are consistent with the part's documented history
  • Dual-release wording actually satisfies both authorities rather than one authority plus a courtesy note
  • The signing organization held the relevant approval on the certificate's issue date
  • Every installation entry in the logbook trail resolves to a certificate in the file, and unresolved entries are logged

Evidence normally required

  • The component release file as it stands, in whatever order it is kept
  • Installed-component listings from the maintenance system
  • Work orders and logbook entries covering component changes during the lease
  • The lease's records and documentation return standard
  • Stores and receiving records for parts fitted from the operator's own inventory

Common discrepancies

  • Certificates filed under the purchase order of a part that was later moved to a different aircraft
  • Single-authority releases on components that need dual coverage for the receiving registry
  • Photocopied or partial certificates where the lease requires originals or certified true copies
  • Installed units traced to a stockroom issue with no release paperwork attached at all

What is at stake

A component without an acceptable release at redelivery gets treated as unapproved by the receiving side, and the usual remedies are replacement, re-certification through a shop, or a financial adjustment. Each is slower and costlier than recovering paperwork would have been. Enough of these findings and the lessor extends the inspection, which pushes the return date and keeps rent running.

How the work runs

01

Build the installed baseline

Extract current installed serial numbers and the component-change history for the lease period.

02

Index the file

Match every certificate to an installed unit or a historical fitment, and log what is left over on both sides.

03

Chase the gaps

Issue certificate requests by source, starting with items the lease standard treats as acceptance blockers.

04

Assemble for handover

Deliver the reindexed file, the exception list, and the filing standard that keeps it current to the return date.

What the buyer receives

  • A component-level exception list keyed to installed serial numbers
  • Certificate requests routed to the shops, suppliers, and pools that can reissue or supply copies
  • A reindexed release file ordered the way a lessor's inspection will consume it
  • A short standard for filing future certificates so the file stays inspection-ready

Who uses the output

  • The director of maintenance who signs up to the return condition
  • Records staff producing certificates on demand during the lessor's on-site review
  • The operator's counsel where unresolvable items head toward a settlement discussion

How the work fits into the transaction or program

Release paperwork is the connective tissue between the aircraft's physical configuration and its records story. This review usually runs alongside the LLP trace work, shares its installation-history digging, and its exception list flows into the same return-condition negotiation the AD and repair reviews feed.

Start with a single asset

Reconcile maintenance tracking against the underlying records.

Jurisdiction-specific considerations

What counts as an acceptable release depends on where the aircraft is going. An EASA Form 1 from a Part-145 organization, an FAA Form 8130-3 with the right approval basis, or a dual release each cover different receiving situations, and bilateral agreements shift the answer over time. The review applies the standard of the registry the aircraft will actually land on, plus the lease's own wording, which is sometimes stricter than either authority.

Regulatory limits

The review evaluates documents against the lease standard and general authority expectations. It does not approve parts for installation, issue or amend any release certificate, or decide airworthiness.

What this review does not cover

  • Physical removal of components to verify data-plate details
  • Issuing replacement 8130-3 or Form 1 certificates
  • Vendor management of the shops asked to supply missing paperwork

Specific to this review

  • Most release-file gaps trace to routine component swaps done under time pressure, so the exception rate correlates with dispatch-critical systems like wheels, brakes, and generators rather than with expensive parts.
  • Reissued certificates from shops carry the reissue date, and some lessor teams question any certificate dated after installation, so recovered paperwork needs its explanation attached before it goes in the file.
  • An indexed release file shortens a lessor's on-site review by days, and the inspection tone set in the first morning tends to persist.
  • Dual-release gaps are cheap to fix while the shop relationship is live and nearly unfixable once the part's last shop has passed its records retention window.

Sources

Frequently asked questions

Do we need releases for every part on the aircraft?

No. The lease's documentation standard defines the population, usually components with maintenance significance or a control category, and the review scopes to that standard. Chasing paperwork for items outside it spends the window on findings nobody will price.

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.