Acquisition records support
Authorized release certificate review for aircraft-management teams during an acquisition
When an aircraft-management team represents a buyer, this review audits the seller's component release documentation before the purchase conditions close. It maps FAA Form 8130-3 and EASA Form 1 certificates to the installed configuration, tests dual-release coverage against the aircraft's intended registry, and traces installation records for the components the purchase standard covers. The work happens inside the data-room window, while the seller must still respond. The owner representative receives an exception schedule for the negotiation, targeted certificate requests, and a release file organized for the owner's long-term archive.
When this review is needed
- A data room has opened on a purchase candidate and the release file is a scanned folder with no index.
- The buyer intends a registry change and nobody has established which installed components carry dual releases.
- The candidate spent time in storage or with a distressed operator, periods when component paperwork discipline typically slips.
- Closing conditions reference a documentation standard and someone has to measure the file against it before signatures.
The problem
A management team stands between a buyer who wants the aircraft and a data room that shows certificates without showing whether they belong to the parts on the wing. Sellers assemble release files from what survived, and survival is uneven: certificates for a landing-gear overhaul filed perfectly, the avionics units behind it undocumented. Testing the file part by part is slow, the window is fixed, and every unchecked component is a risk the owner carries after the wire transfer.
What gets reviewed
- The release file indexed against the installed configuration from the maintenance system and survey data where available
- Certificate completeness checked on a risk-weighted sample: controlled components fully, general rotables sampled
- Dual-release coverage assessed against the registry the buyer intends
- Installation records tied to certificates through the seller's work orders and logbook entries
- Storage and preservation periods examined for component changes with thin paperwork
- The purchase agreement's documentation standard applied as the pass mark throughout
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
- Certificate part and serial numbers resolve to installed units, with mismatches logged rather than rationalized
- Issue dates precede installation dates on every matched pair
- The issuing organization's approval covered the work described, at the date it was signed
- Components changed during storage or ferry operations carry the same standard of release as line changes
- Copies, reissues, and certified-true duplicates are distinguished from originals wherever the purchase standard cares
Evidence normally required
- The data-room release file and any index the seller provides
- Installed configuration and component listings from the seller's maintenance system
- Work orders, logbooks, and component-change history for the ownership period in scope
- The purchase agreement's records and documentation conditions
- Storage entry and return-to-service records, where the aircraft was parked
Common discrepancies
- Installed units whose certificates match the part number and miss on serial number, pointing to an undocumented swap
- Single-authority releases across a component population that the intended registry needs dual-released
- Certificates dated during a storage period with no corresponding work order anywhere in the room
- An immaculate file for the most recent operator sitting on top of a near-empty one for the operator before
What is at stake
Release gaps that close as findings before purchase close as costs after it. A missing certificate discovered at the owner's first component change, or at a later lease placement, forces re-certification or replacement at the owner's expense, and it colors how the next counterparty reads the whole records set. Owners hire management teams precisely to prevent inherited paperwork liabilities, so undetected gaps land on the relationship as well as the budget.
How the work runs
Fix the standard and the population
Read the purchase agreement's documentation conditions and extract the installed-component baseline they apply to.
Match certificates to metal
Index the release file against installed serial numbers, logging matches, mismatches, and absences.
Press the seller
Issue component-specific requests while the deal gives the seller a reason to dig.
Report and archive
Deliver the exception schedule for closing and the indexed file for the ownership that follows.
What the buyer receives
- An exception schedule tied to the purchase agreement's documentation standard, ready for the negotiation table
- Certificate requests directed at the seller, shops, and suppliers with realistic closure estimates
- An indexed release file structured for the owner's archive and the next transaction
- A gap-risk note for components accepted without full paperwork, stating the owner's residual exposure
Who uses the output
- The owner representative negotiating conditions, holdbacks, or repairs to the file before closing
- Maintenance control, which inherits the component baseline on day one of management
- The owner's advisors weighing documentation risk in the final purchase decision
How the work fits into the transaction or program
Release-document diligence runs beside the AD, LLP, and repair reviews in a purchase, and it is usually the volume leader: hundreds of certificates against dozens of directives. Its exception schedule feeds the closing negotiation, and the indexed file it leaves behind becomes the management team's working baseline for the ownership period.
Start with a single asset
Reconcile maintenance tracking against source records.
Jurisdiction-specific considerations
Acceptability of a release turns on the receiving registry, the bilateral agreements in force when the part was installed, and what the purchase agreement itself demands, which is often stricter. A buyer moving the aircraft from FAA to EASA oversight, or the reverse, inherits a component population whose paperwork was assembled for the old world, and the review measures it against the new one.
Regulatory limits
This is documentary diligence. The review does not issue or validate release certificates, approve components for installation, or make any airworthiness determination on the aircraft or its parts.
What this review does not cover
- Physical inspection of components or data plates
- Post-closing management of the seller's outstanding obligations, unless separately engaged
- Valuation opinions on the aircraft or its components
Specific to this review
- Storage periods deserve disproportionate attention: components migrate off parked aircraft, and the replacement paperwork, when it exists, was rarely filed with a future sale in mind.
- Serial-number mismatches are more informative than missing certificates, since a mismatch proves an undocumented event happened, while an absence may only prove poor filing.
- The purchase agreement's documentation clause is the review's real standard, and a vague clause discovered mid-diligence is itself a finding worth escalating to counsel while it can still be tightened.
- Sellers respond to specific requests, this certificate, this serial, this date range, at several times the rate they respond to general completeness demands, so the request list is built at component level from the start.
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 seller's broker says the file was reviewed at the last transaction. Does that reduce the scope?
It changes the starting expectation, and none of the risk transfer. The prior review served a different buyer against a different standard, and components have changed since. A file with good history usually verifies faster, which shows up in the effort rather than in the scope.
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.