Program handback
Maintenance-program status review within the redelivery binder
Before an aircraft changes hands, someone has to prove that its maintenance program status is real. This review takes the program status in the redelivery binder, the task due list with its last-done and next-due values, and audits it against the approved program revision, the accomplishment records behind each task, and the utilization figures the intervals are counted in. It is commissioned by lessors or returning operators once binder assembly starts. The outcome is a task-level defect list showing where the status cannot be reproduced from source.
When this review is needed
- The lease requires return in compliance with the manufacturer's planning document baseline while the operator flew an escalated program for years.
- Program revisions during the lease were approved by the operator's authority but the revision trail was never consolidated in one place.
- The due list comes straight from a maintenance-information system whose interval parameters have not been audited against the approved program.
- A bridging exercise to the next operator's program is imminent and its planners need a status they can trust as the starting point.
The problem
A program status looks authoritative because software produced it, yet everything in it is only as good as the parameters someone configured and the accomplishment data someone entered. Over a long lease, programs get revised, intervals get escalated, tasks get merged or split, and fleet utilization assumptions drift away from how this airframe actually flew. The binder then presents a due list computed on today's settings against history recorded under yesterday's, and no single document in it explains the difference.
What gets reviewed
- Verification that the program revision cited in the binder is the one the operator's authority actually approved, with the approval trail enclosed
- Sampled recomputation of last-done and next-due values from task cards and utilization records
- Comparison of applied intervals against the approved program, isolating escalations, and against the return-condition baseline where the lease sets one
- Review of utilization statements feeding the status, reconciled to logbook hours and cycles
- Check that program-change bridging during the lease was documented, including task mapping between revisions
- Confirmation that out-of-phase and short-interval items appear on the due list rather than only in operator work-planning tools
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
- Sampled tasks show accomplishment evidence dated and referenced consistently with the last-done values on the status
- Interval and threshold values in the due list match the approved program revision effective at redelivery
- Hours and cycles used to compute next-due figures agree with the logbook and utilization records in the binder
- Every escalation applied during the lease has its approval attached and is either permitted by the return conditions or flagged
- Tasks added, split, or renumbered across program revisions are traceable through a documented mapping
Evidence normally required
- The maintenance program status and task due list as offered in the binder
- The approved maintenance program with its revision history and authority approvals
- Task accomplishment records for the sampled population, typically work packs and certification statements
- Utilization reports and logbook totals for the airframe, engines, and APU
- Lease return conditions defining the program baseline for redelivery
Common discrepancies
- Due-list intervals reflecting operator escalations that the return conditions expressly exclude
- Last-done dates keyed into the system weeks after the work, so next-due projections disagree with the physical records
- A program revision applied to the status with no enclosed approval from the operator's authority
- Utilization in the status trailing the logbooks by several hundred hours because the export predates the final flights
What is at stake
If the program status collapses under audit, the fallback position is ugly: tasks whose accomplishment cannot be tied to a valid interval may be treated as overdue, forcing repeat inspections before the next operator's authority will accept the aircraft. Bridging work stalls, the return slips, and each slipped week accrues cost on both sides of the lease while engineers argue over interval genealogy.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Pin the program basis
Identify the approved revision in force, the return-condition baseline, and every escalation or change between them.
Draw the task sample
Select tasks weighted toward escalated intervals, renumbered items, and high-consequence inspections.
Recompute against source
Rebuild last-done and next-due for the sample from work packs and reconciled utilization.
Deliver the defect list
Report by defect type with the supportable program basis stated for the bridging teams.
What the buyer receives
- A task-level defect list separating interval errors, evidence gaps, and utilization mismatches
- A statement of the program basis actually supportable from the enclosed approvals
- A corrected status extract for the sampled population, suitable as a bridging input
Who uses the output
- CAMO and planning engineers building the bridge to the next operator's program
- Lessor technical managers testing return-condition compliance on the program clause
- The returning operator's records office, which must cure the defects before acceptance closes
How the work fits into the transaction or program
Program status is the spine that the task-card, non-routine, and logbook reviews hang off, since each of those record classes exists to evidence what the status claims. Running this review early tells the whole binder effort which tasks to sample hardest, and its corrected status extract becomes the entry point for the incoming operator's bridging analysis.
Jurisdiction-specific considerations
An FAA operator's program authority flows through 14 CFR 121.380-style recordkeeping and operations specifications, while an EASA operator's AMP sits under Part-CAMO and Regulation (EU) 1321/2014, with ICAO Annex 6 shaping states that follow neither directly. Escalation philosophy differs across these regimes, which is why a status that satisfied the outgoing authority can still miss the return-condition baseline written into the lease.
Regulatory limits
The review measures documentary support, no more. It does not approve maintenance programs or escalations, does not declare tasks airworthy or overdue in any regulatory sense, and does not perform the bridging analysis itself; those decisions rest with the operators and their authorities.
What this review does not cover
- Authoring or revising the maintenance program
- Full recomputation of the entire due list rather than a structured sample
- Reliability analysis supporting or opposing interval escalations
Specific to this review
- Return conditions usually anchor to the manufacturer's planning-document intervals, so an operator can be fully compliant with its own authority and simultaneously out of compliance with the lease.
- Task renumbering across program revisions is the quietest way a due list loses items; a task that was split into two can show one half accomplished and the other simply absent.
- Status exports age fast in the final weeks of a lease because ferry flights and return checks keep adding hours after the export date, and acceptance teams routinely catch the stale figure.
- A defensible status needs the approval trail for every revision applied during the lease, and operators changing CAMO providers mid-lease often lose exactly that trail.
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
Why sample tasks instead of auditing the full due list?
A due list can run to thousands of lines, and defects cluster by cause rather than scattering randomly. A sample weighted toward escalations, revision boundaries, and recent accomplishments finds the systematic problems, and the defect pattern then tells both parties whether a full recomputation is worth commissioning for specific task groups.
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.