Counterparty review
Counterparty-audit records preparation for a counterparty review
Counterparty-audit records preparation gets an aircraft's records ready for review by a commercial counterparty rather than a regulator: a potential lessee, a buyer, a charter or wet-lease reviewer, or a contract partner whose agreement sets a records standard. It is run by or for a lessor, airline, operator, or aircraft management provider that has to satisfy a counterparty's own records requirements before the asset is accepted. It covers the records the contract or scope calls for, their format and transferability, the status lists the counterparty will sample, and the evidence behind each. You receive a records package mapped to the counterparty's requirements, a register of gaps measured against their standard, and a path to close each before their audit.
When this review is needed
- A potential lessee is auditing the asset's records against the standard in the draft lease before accepting it.
- A buyer's technical team is reviewing the records as a condition of a sale and the bar is theirs, not a regulator's.
- A charter or wet-lease counterparty requires evidence of the asset's records before placing it into their operation.
- A contract partner sets a records format and completeness standard the asset has to meet on delivery.
- A counterparty's audit checklist has arrived and the records need aligning to it before they sample the asset.
The problem
A counterparty audits to its own standard, which is set by a contract or a checklist rather than a regulation, and that standard is often stricter or simply different from how the records are kept. The counterparty expects specific record types, in a particular format, traceable and transferable to them, and they sample status lists expecting the evidence behind each line. Records that satisfy the operator's own system can still fail a counterparty's checklist on format, completeness, or a clause the operator never mapped, and the gap surfaces in front of the counterparty.
What gets reviewed
- The records the contract or audit scope requires and their completeness standard
- Format and transferability of each record to the counterparty
- AD and SB status lists the counterparty will sample with supporting evidence
- Component and life-limited part status against release and trace documents
- The configuration and modification status against the contractual baseline
- Mapping of each counterparty checklist item to the record that answers it
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 record the contract requires is present and meets the agreed completeness standard
- Every record is in the format the agreement specifies and is transferable to the counterparty
- Status lists the counterparty samples reconcile with the underlying source documents
- Component and life-limited part status traces to valid release and accumulation evidence
- The configuration and modification status matches the baseline the contract references
- Each item on the counterparty's audit checklist maps to a specific record that answers it
- No required record is held in a form the counterparty's standard will reject
Evidence normally required
- The contract records standard or the counterparty's audit checklist
- AD and SB status lists with accomplishment references
- Component and life-limited part status with release certificates
- The configuration and modification status against the contractual baseline
- The agreed delivery format and transfer requirements
- Logbooks and source documents for the lines the counterparty will sample
Common discrepancies
- A record the operator holds that does not meet the contract's completeness standard
- A record in a format the counterparty's checklist will not accept on transfer
- A status list the counterparty samples that disagrees with the source documents behind it
- A life-limited part trace that satisfies the operator but not the contract's standard
- A configuration status that differs from the baseline the agreement references
- A checklist item with no record mapped to answer it
- A record that cannot be transferred to the counterparty in the form the contract requires
What is at stake
A failed counterparty audit delays acceptance, weakens the owner's position in the deal, and can reopen commercial terms while the counterparty holds the leverage. Records that are not transferable in the form the contract requires can block the asset from moving to the counterparty at all, and findings raised during their audit are closed under their timeline rather than the owner's.
How the work runs
Read the counterparty standard
Take the contract records standard or audit checklist as the measure and map each requirement to a record set.
Align format and transfer
Confirm each required record is in the agreed format and can be transferred to the counterparty as the contract specifies.
Reconcile sampled status
Tie the status lists the counterparty will sample back to their source documents so each line is supported.
Close gaps before the audit
Register each gap against the counterparty's standard and resolve it while the owner still holds the timeline.
What the buyer receives
- A records package mapped item by item to the counterparty's requirements
- A gap register measured against the contract standard or audit checklist
- A reconciled status view tying the sampled lists to their source documents
- A closure path for each gap with the record or format change needed before the audit
Who uses the output
- Asset and transaction teams presenting the records to the counterparty
- Technical-records staff aligning the package to the counterparty's checklist
- Commercial leads protecting the deal position during the counterparty's review
How the work fits into the transaction or program
Preparation runs before the counterparty's audit so the records meet their standard while the owner still controls the timeline and the deal terms. It feeds the acceptance package and, on a lease or sale, the records baseline the counterparty carries forward.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Jurisdiction-specific considerations
A counterparty often operates the asset under a different authority than the current operator, so the records have to satisfy both the contract and the form the receiving system expects. A release or trace document acceptable to the current operator is not automatically acceptable to a counterparty taking the asset onto another authority, and the preparation addresses that before the audit.
Regulatory limits
Preparation aligns and checks records against a counterparty's contractual standard and identifies gaps measured against it. It does not negotiate the contract, make an airworthiness determination, or guarantee the counterparty will accept the asset.
What this review does not cover
- Negotiation of the contract or the records standard it sets
- Acceptance of the asset on the counterparty's behalf
- Any airworthiness determination or regulatory approval
Specific to this review
- The bar in a counterparty audit is set by a contract or checklist, not a regulation, so records that pass the operator's own system can still fail on format or a clause never mapped.
- Transferability matters as much as content, because a record the counterparty cannot receive in the agreed form can block the asset even when the maintenance is sound.
- Each counterparty checklist item is mapped to a specific record before the audit, since an unmapped item reads as a gap regardless of whether the evidence exists somewhere.
Sources
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.
U.S. Government (eCFR). Requirement to transfer maintenance records with an aircraft on sale or transfer of ownership.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
How is a counterparty audit different from a regulator's?
A regulator tests compliance with its rules. A counterparty tests the records against the contract it set and its own checklist, which can demand specific formats, completeness, and transferability that go beyond what a regulator asks for.
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.
Walk through your situation with an engineer who has done this work.