Off-registry preparation
Maintenance-program records review for lessors preparing an aircraft export
Lessors use this review when an aircraft is coming off its current registry and the maintenance-program records must carry the asset cleanly to its next operator. It verifies the approved program revision behind the status, the escalations in effect, the bridging support prepared for the receiving program, and the source documents underneath the compiled status. Records specialists run it during export preparation, usually alongside redelivery activity. Asset management receives a bridging-readiness statement, a discrepancy schedule, and closure assignments split between the outgoing operator and the lessor's own team.
When this review is needed
- A lease is ending, the aircraft is leaving the registry, and program records must function under the next operator's authority.
- The outgoing operator's escalations underpin the status and their expiry at transfer has not been quantified.
- Bridging materials exist in draft and nobody has tested their coverage against the receiving program.
- Redelivery negotiations are consuming the technical team in the same weeks the export package must come together.
The problem
The program records a lessor exports with an aircraft were built for the outgoing operator's authority and utilization, and every element that is operator-specific stops working at transfer. Redelivery consumes the technical team's attention in the same window the export package is due, and program discrepancies found late land after the lessor's contractual leverage over the operator has expired.
What gets reviewed
- The approved program revision and amendment history behind the compiled status
- Escalations in effect and which of them expire at operator transfer
- Bridging support prepared for the receiving operator's program and authority
- Source-document sampling from the status into task cards and check packages
- Tasks approaching limits within the transition and early next-lease window
- Program treatment of ICA from modifications embodied during the lease
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
- The compiled status names its program revision, and that revision matches what the authority approved
- Intervals shown as escalated are flagged for reversion wherever the escalation will not follow the aircraft
- Sampled status lines resolve to signed task cards in the operator's check packages
- The bridging file addresses component and structural tasks as well as the airframe check cycle
- Nothing in the status contradicts the redelivery condition report for the same items
Evidence normally required
- The operator's compiled program status with revision and compile date
- The approved maintenance program and its amendment record
- Escalation approvals granted during the lease
- The bridging materials prepared for the next operator, in whatever state they exist
- Condition documents from redelivery covering overlapping items
Common discrepancies
- Escalated intervals presented without reversion flags, understating near-term task load for the next operator
- A status compiled against an amendment the authority record does not show as approved
- A bridging file that covers the airframe check cycle but skips component hard times
- Status entries contradicted by the redelivery survey on the same tasks
What is at stake
Program records that do not bridge cleanly delay the next delivery, and delay on a transitioning asset is direct revenue loss. Status defects that pass unnoticed at export resurface during the next operator's induction, where the lessor pays to fix them without recourse to the operator who created them.
How the work runs
Verify the reference
Confirm the approved revision, amendment history, and escalation set behind the operator's status.
Sample the status
Trace status lines into task cards and check packages, weighting recent and escalated tasks.
Test the bridge
Check bridging coverage against the receiving program across every task family.
Assign closure
Issue the discrepancy schedule with each item assigned while lease obligations still apply.
What the buyer receives
- A bridging-readiness statement for the receiving operator and authority
- A discrepancy schedule tied to specific status lines and documents
- Closure assignments allocating each item to the operator under the lease or to the lessor's team
Who uses the output
- Asset managers holding the operator to lease-return records obligations
- Transition managers planning the next delivery timeline
- The next operator's continuing-airworthiness team receiving the bridge
How the work fits into the transaction or program
The review runs in the seam between redelivery and export, using the last period in which the outgoing operator is contractually bound to fix its own records. Its output feeds three places at once: the redelivery closeout, the export package, and the induction file for the next operator.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Jurisdiction-specific considerations
Program approval mechanics are authority-specific: an EASA operator's program is managed within its CAMO under Regulation 1321/2014, US operators follow their certificate's program rules with retention duties such as 14 CFR 91.417, and ICAO Annex 6 sets the frame the next registry implements in its own way. The readiness statement is written against the receiving system, since that is where the records must function next.
Regulatory limits
The review verifies program records and bridging support. It does not approve programs or escalations for any operator, author the bridging submission, or determine airworthiness for the export certificate.
What this review does not cover
- Physical inspection and condition survey at redelivery
- Drafting the next operator's maintenance program
- Lease enforcement or commercial dispute handling
Specific to this review
- Every escalation on the status is a question with a deadline: it either transfers, reverts, or must be re-earned by the next operator, and the answer changes near-term maintenance cost.
- The redelivery survey and the program status describe the same aircraft through different documents, and their disagreements are the fastest route to real findings.
- Lessor leverage over records defects expires with the lease, so the discrepancy schedule is sequenced to use that leverage before it lapses.
- A bridge that omits component hard times looks complete at export and fails at induction, which is the most expensive place for it to fail.
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
Is this the same work as the redelivery records review?
They overlap in inputs and differ in purpose. Redelivery review enforces the lease's return conditions; this review makes the program records function under the next authority and operator. An item can pass redelivery language and still break the bridge, which is why the program pass runs on its own terms.
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.