Skip to content

Component release evidence

Authorized release certificates in an owner-managed aircraft file

An owner-managed release-document source review tests the paperwork behind every serialized component installed on a managed aircraft. It compares the component release file against what actually exists in owner folders, the management company's receiving records, and the installing shops' job files. The review is run for the owner representative ahead of a sale or a change of management provider. It returns a component-level exception list naming each install that rests on an invoice, a mismatched certificate, or no release document at all.

When this review is needed

  • A sale is in view and the buyer's records team will sample release certificates for installed components.
  • The management contract is ending and the incoming provider wants component evidence, source documents included, before accepting the aircraft.
  • Parts were purchased and fitted through the management company for years and the owner never held the certificates.
  • A pre-buy inspection already found one install without a release document and the owner needs to know how far the problem extends.

The problem

Management companies source and install parts on the owner's behalf, and what reaches the owner's folder is usually the invoice. The FAA Form 8130-3 or EASA Form 1 that released the part stays in the provider's receiving file or in the installing shop's job records. By the time sale preparation starts, the component release file shows parts flying on the aircraft with nothing in hand to show where they came from.

What gets reviewed

  • Inventory of serialized installed components built from the tracking export and logbook install entries
  • Match of each FAA Form 8130-3 or EASA Form 1 on file to part number, serial number, and the install it supports
  • Release status (new, overhauled, repaired, inspected) checked against how the part was used
  • Installs supported only by an invoice traced toward the shop or supplier that can produce the certificate
  • Dual-release needs assessed where the aircraft has moved, or may move, between FAA and EASA environments
  • Component-level exceptions recorded with the specific source that fails

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 serialized component shown installed in tracking has a release certificate whose part and serial numbers match
  • The work performed on the certificate agrees with the logbook description at installation
  • Certificate issue dates precede the install dates they are claimed to support
  • The certifying regime on each release suits the regulatory context the part was received into
  • No certificate has been attached to two different installations of the same part number

Evidence normally required

  • Component status export from the management provider's tracking system
  • Owner folders and any closing binders from earlier transactions on the aircraft
  • Receiving records and purchase orders held by the management company
  • Work orders and invoices from installing shops
  • Prior audit or pre-buy reports that touched component documentation

Common discrepancies

  • An invoice on file with no certificate, where the installing shop still holds a recoverable copy
  • A Form 1 present in the folder that carries a different part number than tracking shows installed
  • A release issued for a repair while the logbook entry claims an overhaul
  • A certificate scan cut off or illegible exactly where the approval reference and signature should be

What is at stake

Certificates that cannot be produced become the buyer's leverage. Serialized components without releases get priced as unsupported, life-limited or safety-significant parts can trigger replacement demands, and closing can stall while certificates are chased through shops that have no open relationship with the aircraft. Access to the management provider's receiving files usually ends with the contract, so waiting makes recovery harder.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Build the installed-component picture

Assemble the serialized component population from the tracking export, logbook install entries, and the current component release file.

02

Pull certificates from every source

Collect release documents from owner folders, the provider's receiving records, and installing-shop job files, and index them by component.

03

Test each certificate

Check part and serial match, work performed, date order, and receiving regime for every install, and log the specific failure where one exists.

04

Issue the exception list

Deliver component-level exceptions with recovery routes and flag the items that matter most for the handover baseline.

What the buyer receives

  • A component-level exception list stating which document fails and why
  • A recoverability note for each exception naming the shop or provider most likely to hold the missing certificate
  • A reconciled release-document index ready for the handover file

Who uses the output

  • The owner representative negotiating what the sale price should absorb
  • The incoming management provider or maintenance control accepting the aircraft onto its system
  • Buyer-side reviewers who receive a mapped file instead of a box of scans

How the work fits into the transaction or program

Release documents are one slice of the wider source review run across an owner-managed file before handover. Findings here feed the owner handover baseline directly and often open questions for the repair and modification reviews, since an undocumented part frequently arrived during an undocumented job.

Jurisdiction-specific considerations

Under FAA practice, plenty of domestic installs on privately operated aircraft were lawfully made without an 8130-3, which makes a missing certificate a commercial exposure more than a regulatory one. EASA-facing transactions are stricter: a component entering an EASA environment is expected to carry an EASA Form 1 or an acceptable dual release, so the direction of the likely sale decides how hard each gap bites.

Regulatory limits

The review reports the state of release documentation. It does not approve any part for installation, issue or correct a certificate, or determine airworthiness. Whether a given part may remain in service is a question for certificating personnel and the responsible authority, and nothing in the exception list substitutes for that judgment.

What this review does not cover

  • Physical inspection or removal of installed components
  • Sourcing replacement parts or certificates on the owner's behalf
  • Suspected unapproved parts investigation, which follows the authority's own process

Specific to this review

  • Many domestic installs on Part 91 aircraft never required an 8130-3 at the time, yet buyer checklists expect one now; the review separates regulatory shortfalls from market expectations so each is negotiated correctly.
  • The management provider's receiving file is the single best recovery source, and contractual access to it usually lapses at termination, which argues for running this review before switching providers.
  • Certificates for life-limited parts draw scrutiny no other component paperwork gets, so exceptions on LLPs are worked first.
  • A release dated after the install it supposedly covers supports nothing; simple date-order checks close or open more exceptions than any other single test.
  • An invoice proves payment and identifies the seller, and buyers will accept it as a lead to the certificate, never as its substitute.

Sources

Frequently asked questions

The aircraft has only ever operated under Part 91 and some parts never came with an 8130-3. Is that a finding?

It can be lawful and still cost money. The review records it as an exception with its regulatory context stated plainly, so the owner representative can present it as a market-expectation gap rather than concede it as a compliance defect. Where the shop or distributor can still produce a certificate, the exception carries that recovery route.

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.