Lessor acquisitions
Maintenance program records review for lessors buying an aircraft
Lessors buying an aircraft inherit its maintenance program history along with the metal. This review reads the approved program revisions, escalation approvals, and bridging analyses in the data room and tests whether the reported program status is supported by accomplishment records. It runs during pre-purchase diligence, before price and delivery conditions close. The asset manager receives a finding log ranked by transition cost, a seller request list, and a route to close each item.
When this review is needed
- A purchase with lease attached is in diligence and the seller's program compliance is priced into the transaction.
- The operator has escalated task intervals and the approvals behind those escalations are not in the data room.
- The aircraft has moved between programs before, and the earlier bridging analyses are the only link in its compliance chain.
- Redelivery conditions in the attached lease reference the maintenance program, and the lessor needs to know what it is actually acquiring.
The problem
Program compliance is reported as a percentage and a next-due list, and both depend on which program revision each task was accomplished against. An operator that escalated intervals, adopted revisions late, or bridged from a previous program leaves a compliance status that only holds if the approvals and analyses behind those steps exist. In a data room, those documents are the ones most often missing, because they live in the operator's engineering files rather than the records archive.
What gets reviewed
- The approved maintenance program revision history for the period under review
- Task escalations and the approvals or reliability data supporting them
- Bridging analyses from any prior program, with regulator or CAMO acceptance
- Sampled task accomplishments checked against the revision in force at the time
- Program status reporting reconciled with the underlying compliance records
- ICA and mandatory requirements incorporated at the correct revisions
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 escalation applied in the compliance data has an approval or a documented reliability basis
- Bridging analyses account for all applicable tasks, without silent deletions between programs
- Sampled accomplishments reference the correct task, interval, and program revision
- The reported next-due list is reproducible from the compliance records rather than asserted
- Program revisions were adopted within the approval framework of the responsible authority
Evidence normally required
- The approved maintenance program and its revision history
- Escalation approvals, reliability reports, and CAMO or authority correspondence
- Bridging analyses from prior program transitions
- The operator's compliance status export and next-due report
- A sample of task cards or work orders for accomplishment verification
Common discrepancies
- Escalations applied in the tracking system with no approval on file
- A bridging analysis that skips tasks introduced by a later program revision
- Compliance percentages computed against a superseded revision
- Task accomplishments signed against the wrong interval after a revision change
What is at stake
A lessor that buys against an unsupported program status inherits the burden at the next transition. Tasks accomplished against unapproved escalations may need to be repeated, bridging gaps can force conservative re-baselining of intervals, and the cost lands during redelivery negotiations, where the lessor is the party with the least room to move.
How the work runs
Fix the program timeline
Establish which program revision was in force across the review period and when each revision was adopted.
Trace escalations and bridges
Pull every escalation and bridging analysis and confirm the approval or acceptance behind it.
Sample accomplishments
Check a structured sample of task accomplishments against the correct revision, task, and interval.
Report exposure
Deliver findings ranked by what they would cost at the next transition, with a route to close each one.
What the buyer receives
- A finding log ranked by transition-cost exposure
- A reconciled view of program status against the evidence that supports it
- A seller request list targeting the missing approvals and analyses
Who uses the output
- Asset managers pricing the transaction and its redelivery risk
- Lessor technical-records leads planning the post-closing baseline
- Transaction managers drafting conditions that reference program compliance
How the work fits into the transaction or program
Program findings shape both the purchase terms and the lease that survives closing. Anything the review flags becomes either a price point, a closing condition, or a tracked item in the lessor's asset file, and the verified program status feeds transition planning for the next placement or redelivery.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Jurisdiction-specific considerations
FAA operators under 14 CFR 121.380 or 135.439 and EASA operators under Part-CAMO document program control differently: escalations, reliability programs, and revision approvals sit with different parties in each system. The review reads the records against the framework the aircraft actually operated under, then flags what a counterpart authority would expect to see at transfer.
Regulatory limits
This is a records verification, and its findings describe documentary support only. It does not approve a maintenance program or an escalation, does not perform a bridging analysis, and does not make any determination that the aircraft is airworthy or that its program satisfies a specific authority.
What this review does not cover
- Building or approving a bridging analysis for the buyer's future program
- Reliability engineering or interval-setting work
- Review of unrelated records domains such as AD status or LLP trace, which run as separate workstreams
Specific to this review
- Escalation approvals are the single most frequently missing document class in maintenance-program diligence, because operators file them with engineering correspondence rather than aircraft records.
- A compliance percentage can be technically accurate and still misleading if it is calculated against a superseded program revision.
- Lease redelivery conditions often require compliance with the delivery-time program, which makes the revision history at acquisition a contract-relevant document years later.
- Bridging gaps compound: each program transition inherits the unverified assumptions of the previous one, so an aircraft on its third operator can carry silent deletions from its first.
Sources
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
U.S. Government (eCFR). Maintenance recordkeeping and retention requirements for Part 135 operators.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
International Civil Aviation Organization. International standards for aircraft operation, including maintenance program and recordkeeping expectations.
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 aircraft comes with a lease attached. Does that change the review?
It sharpens it. The attached lease's redelivery conditions define what program compliance will mean at the end of the term, so the review reads the records against those conditions as well as the regulatory framework, and flags where the two diverge.
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.