Program compliance at return
Maintenance-program records review for operators before lease return
Operators returning an aircraft must show the asset was maintained to the approved program for the whole lease. This review checks the maintenance program status against approved revisions, task escalations, and the bridging analysis the next operator will build on, before the lessor's inspectors do. It is performed for the operator's maintenance leadership in the run-up to redelivery. Each unsupported program entry is logged with the source document that would close it.
When this review is needed
- The lease return date is set and the redelivery conditions require demonstrating maintenance to the approved program.
- Tasks were escalated during the lease under the reliability program and the approvals need to be located and attached.
- The next operator has requested a bridging analysis and the program history it builds on has to be defensible.
- Program revisions accumulated over the lease and the status report no longer states which revision each task was performed against.
The problem
A maintenance program is a moving target across a lease: revisions land, intervals escalate, tasks are added by AD or dropped by amendment. The status report shows last-done and next-due, and the redelivery team must prove each figure was correct under the revision in force at the time. Digging out the approval letter for an escalation applied years ago, or the effectivity of a task added mid-lease, consumes exactly the weeks the return schedule does not have.
What gets reviewed
- The maintenance program status sampled against approved revisions in force across the lease
- Task escalations traced to their approval instrument, whether authority-approved or granted under an approved reliability program
- Last-done and next-due figures for sampled tasks verified against source records: task cards, work orders, and check packages
- Tasks introduced or removed by revision checked for correct adoption on this airframe
- The bridging position toward the next operator's program reviewed for source-document support
- Program-driven out-of-phase tasks confirmed tracked with their own compliance history
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 sampled task's last-done entry resolves to a signed source record, and the date and hours agree with the status report
- Escalated intervals carry an approval that covers this operator, this aircraft, and the period the escalation was used
- Revision adoption dates on the status report match the approved-revision record held by the operator's CAMO or equivalent
- No sampled task was accomplished against an interval from a revision not yet approved at the time
- Bridging statements cite documents that exist in the redelivery package rather than in the operator's live system alone
Evidence normally required
- The current maintenance program status report and the approved program with its revision history
- Escalation approvals and the reliability-program records behind them
- Task cards, work orders, and check packages for the sampled tasks
- The lease's redelivery conditions on program compliance
- Any draft bridging analysis prepared for the next operator
Common discrepancies
- Escalations applied fleet-wide whose approval documents never mention the returning serial number
- Status lines whose last-done date traces to a work order that covers a different task revision
- Program revisions adopted in the maintenance system months after their approval date, leaving a window of ambiguous intervals
- Out-of-phase tasks tracked on a side list that never made it into the redelivery status report
What is at stake
Program findings at redelivery are expensive because they cascade. One task shown overdue under the revision that applied at the time can reopen the sampling of the whole status report, extend the lessor's records review, and push the return past the lease expiry into holdover terms. The bridging analysis for the next operator inherits every unresolved question.
How the work runs
Map the revision history
Establish which program revision governed each period of the lease and which approvals modified it.
Sample against the record
Select tasks across checks, escalations, and revision changes, and pull their source records.
Close what can be closed
Route recoverable documents and correctable status lines to the operator's team with deadlines tied to the return date.
Package the evidence
Assemble the compliance pack and exception list for the redelivery review.
What the buyer receives
- A sampled compliance verdict on the program status report with every exception documented
- An evidence pack linking sampled status lines to their source records
- A prioritized fix list for items the operator can close before the lessor's team arrives
Who uses the output
- Directors of maintenance sequencing closure work against the return date
- CAMO or continuing-airworthiness staff defending the status report line by line
- Records leadership assembling the redelivery documentation package
How the work fits into the transaction or program
Program verification anchors the rest of redelivery preparation: AD status, component status, and check history all reference program tasks and intervals. Running it early gives the operator its own findings list before the lessor produces one, which changes the tone of the records review from adversarial sampling to confirmation.
Start with a single asset
Reconcile maintenance tracking against the underlying records.
Jurisdiction-specific considerations
Under EASA rules the program and its revisions run through the CAMO with defined approval routes, while FAA operators demonstrate compliance through their operations specifications and the applicable Part 121 or 135 recordkeeping rules. A lease return that crosses regimes has to present program history in terms the receiving side recognizes, and the review frames its evidence pack accordingly.
Regulatory limits
The review tests documentary support for program compliance. It does not approve programs, revisions, or escalations, does not perform bridging engineering for the next operator, and does not decide airworthiness or return-to-service questions reserved to certifying staff and authorities.
What this review does not cover
- Authoring or negotiating the bridging analysis with the incoming operator
- Reliability-program analysis or interval justification work
- Physical verification of task accomplishment on the aircraft
Specific to this review
- Compliance is judged against the revision in force when the task was done, so a status report that only shows the current revision hides the history that redelivery teams actually test.
- Escalation approvals are the most common single point of failure: the escalation is real, was used for years, and the approving document cannot be found.
- Bridging disputes at delivery of the next lease usually trace back to soft spots in the outgoing operator's program history rather than to the analysis itself.
- The lessor's records team samples where operators historically fail, so a self-review that samples the same way predicts most findings in advance.
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
Our maintenance system shows everything green. Why would the lessor find problems?
The system reports against the current program. Redelivery reviews reach backward: they test whether each accomplishment met the interval approved at the time, and whether the approvals for escalations and revisions can be produced on paper. Systems rarely store that second layer.
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.