Sale-and-leaseback closing
Source evidence review for sale leaseback records audit
For airlines, lessors, and Asset managers, this review is used when sale-and-leaseback closing puts records evidence under review. EE compares full status and source spot checks to populate the..., LLP and shop-visit positions that set reserve rates,..., Sale Leaseback Records Audit source file with source records and event criteria. Discrepancies are unsupported status, missing release or trace evidence, conflicting serial or time data, or open items without disposition. Deliverables are a discrepancy register, evidence map, request list, and decision brief. The review does not approve maintenance or determine airworthiness.
When this review is needed
- Before sale-and-leaseback closing fixes the commercial or operational position.
- When a summary status must be defended with records a third party can inspect.
- After prior findings, custody changes, or late evidence requests reveal file risk.
The problem
Brief focus: In a sale-leaseback the seller keeps flying the aircraft, so the records audit sets the delivery-condition baseline that the same airline will be measured against at redelivery years later: the decision is which discrepancies to fix, disclose, or accept into the lease annexes now. The review notes that evidence reviewed: full status and source spot checks to populate the delivery-condition annexes, LLP and shop-visit positions that set reserve rates, open discrepancies to be scheduled or carved out in the lease, and records custody and format agreements for the lease term. Failure modes: a delivery annex signed off from tracking-system data that source records later contradict, gaps discovered at redelivery that were present at closing but never carved out, and reserve rates set against an unverified maintenance status. Serves both chairs of the same event: the seller-airline testing which delivery conditions its records can demonstrate before signing, and the buying lessor verifying in the bid window - both converge on the same annex baseline.
What gets reviewed
- Establish the event baseline and the records population to be reviewed.
- Read full status and source spot checks to populate the delivery-condition annexes for dates, references, serials, and completeness.
- Tie LLP and shop-visit positions that set reserve rates, open discrepancies to be. to source evidence rather than exported status alone.
- Test Sale Leaseback Records Audit source file against the acceptance criteria in the brief.
- Log custody, access, and retrieval gaps that could block later review.
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
- Source match: every claimed status line must point to a record that supports it.
- Continuity test: times, cycles, serials, dates, and configuration must reconcile across systems.
- Release check: approval or return-to-service evidence must fit the item and event.
- Disposition check: each exception needs owner, request, due path, or commercial reserve.
Evidence normally required
- full status and source spot checks to populate the delivery-condition annexes
- LLP and shop-visit positions that set reserve rates, open discrepancies to be.
- Sale Leaseback Records Audit source file
- current maintenance or compliance status list
- release certificates and logbook entries
Common discrepancies
- Delivery annex signed off from tracking-system data that source records later contradict, gaps discovered at redelivery that were present at closing.
- Buying lessor verifying in the bid window - both converge on the same annex baseline.
- Status line unsupported by the source record
- Release or trace document absent from the reviewed file
What is at stake
Practical exposure is specific to this event: Grep for leaseback returned zero pages. Checked aircraft-sale-preparation-records-review (sale prep, seller exits) and delivery-acceptance-records-review (buyer accepting delivery): neither covers the seller-stays-operator active where the closing baseline becomes the seller's own future redelivery standard. Challenge merge absorbed: ai-sale-leaseback-records-review, airline-sale-leaseback-records-readiness. If the evidence fails, the team may face delayed acceptance, repricing, added reserve, audit escalation, repeated inspection, or a disputed handover.
How the work runs
Frame Sale Leaseback
Confirm the exact event, affected file set, buyer role, and decision standard before any full status and source spot checks to populate the delivery-condition annexes is treated as sufficient.
Trace Audit Source
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Review Closing
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Gaps Become
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
- discrepancy register keyed to slb-delivery-annex-baseline
- The review notes that evidence map linking claimed status to source records
- closure request list with owners and acceptance evidence
- decision brief for Fleet transactions lead and Lessor technical manager
Who uses the output
- Fleet transactions lead uses the exception list to direct closure work.
- Lessor technical manager uses the evidence map for counterparties, auditors, or internal approval.
- Treasury or finance lead uses the residual-risk view for timing, price, covenant, or acceptance decisions.
How the work fits into the transaction or program
In a sale-leaseback the seller keeps flying the aircraft, so the records audit sets the delivery-condition baseline that the same airline will be measured against at redelivery years later: the decision is which discrepancies to fix, disclose, or accept into the lease annexes now. The evidence set centers on full status and source spot checks to populate the delivery-condition annexes, LLP and shop-visit positions that set reserve rates, open discrepancies to be scheduled or carved out in the lease, and records custody and. The likely weak points are a delivery annex signed off from tracking-system data that source records later contradict, gaps discovered at redelivery that were present at closing but never carved out, and reserve rates set against an unverified maintenance status; Serves both chairs of the same event: the seller-airline testing which delivery conditions its records can demonstrate before signing, and the buying lessor verifying in the bid window - both converge on the same annex baseline. Handoff: fleet transactions lead, sale-and-leaseback closing, Source.
Start with a single asset
Prove the review on a single tail, then scale across the fleet.
Regulatory limits
EE reviews records and evidence only. The work does not approve maintenance, certify an aircraft or component, determine airworthiness, or bind FAA, EASA, TCCA, ICAO, an approved organization, or an authorized person.
Specific to this review
- This page is scoped around slb-delivery-annex-baseline, not a general records health check.
- The brief's evidence set controls sampling: full status and source spot checks to populate the delivery-condition annexes; LLP and shop-visit positions that set reserve rates, open discrepancies to be.; Sale Leaseback Records Audit source file; current maintenance or compliance status list; release certificates and logbook entries.
- The main failure pattern is page-specific: Delivery annex signed off from tracking-system data that source records later contradict, gaps discovered at redelivery that were present at closing.; Buying lessor verifying in the bid window - both converge on the same annex baseline.; Status line unsupported by the source record; Release or trace document absent from the reviewed file.
- Records made before sale-and-leaseback closing carry more weight than summaries produced after the issue is commercial or adversarial.
- The scope uses the Sale Leaseback Records Audit question as the control point, so the review stays tied to Sale-and-leaseback closing and the buyer decision behind it.
- The evidence starts with full status and source spot checks to populate the delivery-condition annexes and follows Source Evidence Review Closing references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for Fleet transactions lead: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Today Gaps Become Redelivery questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from discrepancy register keyed to slb-delivery-annex-baseline; it gives the next reviewer a precise map instead of another broad request for a better file.
Sources
U.S. Government (eCFR). Requirement to transfer maintenance records with an aircraft on sale or transfer of ownership.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
What makes this workflows review different from a general file audit?
The scope is tied to sale leaseback records audit and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block sale-and-leaseback closing or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is full status and source spot checks to populate the delivery-condition annexes, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives fleet transactions lead a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
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.