Program transition
Maintenance-program transition mapping between programs
Maintenance-program transition mapping aligns each maintenance task from an aircraft's outgoing program to the incoming program task by task, so no requirement is dropped and every interval and due point carries over correctly. It is built for lessors, airlines, and acquisition teams moving an aircraft between maintenance programs. It covers task equivalence, interval and threshold reconciliation, escalation and bridging of intervals, and the items the new program adds or the old program no longer covers. You receive a task-level mapping, a list of orphaned and added tasks, and the recalculated due points the incoming program will run.
When this review is needed
- An aircraft is moving from one approved maintenance program to another and every task must carry across without a gap.
- The incoming program uses different intervals or thresholds and the existing due points must be recalculated onto it.
- Tasks tracked under the outgoing program have no direct equivalent and have to be reconciled rather than dropped.
- An interval was escalated or bridged under the outgoing program and the basis must be carried into the incoming one.
The problem
A change of maintenance program is where requirements quietly disappear. The outgoing program and the incoming program describe the same airframe with different task structures, different intervals, and different thresholds, and a one-to-one match rarely exists. A task on the old program can map to part of a task on the new one, an interval can shorten so that an item is suddenly overdue, and an escalation granted under the old program may not carry without its basis. When the mapping is done loosely, a requirement is lost or a due point is miscalculated, and the error is not visible until the task should have come due.
What gets reviewed
- Each task in the outgoing program against its equivalent, partial equivalent, or absence in the incoming program
- Intervals and thresholds reconciled where the incoming program defines them differently
- Last-accomplishment status carried forward so due points recalculate correctly onto the incoming program
- Escalations, bridging, and interval extensions granted under the outgoing program and their basis
- Tasks the incoming program adds that the outgoing program did not require
- Requirements the outgoing program covered that the incoming program no longer carries, and how each is met
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 outgoing task is mapped to an incoming equivalent, a partial equivalent, or an explicit reconciliation
- Intervals and thresholds are reconciled where the two programs define them differently
- Due points recalculate correctly from the last accomplishment onto the incoming interval
- An interval that shortens does not leave a task already overdue once mapped, or the overrun is flagged
- An escalation or bridging granted under the outgoing program carries with the basis that supports it
- Added tasks have a first due point established, and dropped tasks have their requirement accounted for
Evidence normally required
- The outgoing approved maintenance program and its task list with intervals
- The incoming approved maintenance program and its task list with intervals
- Last-accomplishment status and current due points for every task
- Escalation, bridging, and interval-extension approvals under the outgoing program
- The maintenance-tracking baseline the due points are carried in
Common discrepancies
- An outgoing task with no direct equivalent that was about to be dropped in the transition
- An interval that shortens on the incoming program and renders an item overdue once mapped
- A due point miscalculated because the last-accomplishment basis did not carry across
- An escalation granted under the outgoing program that would have been lost without its basis
- A task the incoming program adds that had no first due point established
What is at stake
A task that fails to carry across leaves a requirement uncovered until it is noticed, which is a continuing-airworthiness exposure rather than a scheduling slip. An interval miscalculated onto the incoming program can show an item as not yet due when it has in fact run past its limit, or pull work forward and waste life. At a transition under time pressure, an unmapped escalation or a dropped task is the kind of gap that surfaces only when the incoming program is already in force.
How the work runs
Lay the programs side by side
Capture every task, interval, and threshold from the outgoing and incoming programs for the specific type.
Map task to task
Match each outgoing task to its incoming equivalent, partial equivalent, or an explicit reconciliation where none exists.
Reconcile intervals and due points
Recalculate due points from the last accomplishment onto the incoming intervals and flag any item the change renders overdue.
Account for orphans and additions
Record dropped tasks with how their requirement is met, set first due points for added tasks, and carry escalations with their basis.
What the buyer receives
- A task-level mapping from the outgoing program to the incoming program with the equivalence stated
- A list of orphaned tasks, added tasks, and items whose interval changes the due point
- The recalculated due points the incoming program will run, with any overrun flagged
Who uses the output
- Continuing-airworthiness teams adopting the incoming program with the due points in place
- Fleet planners scheduling the first events under the incoming program
- Records teams confirming no requirement was lost in the program change
How the work fits into the transaction or program
The mapping underpins an operator or program change by turning two task lists into one reconciled schedule, so the incoming program runs from correct due points. It feeds the AOC transfer review, since the program differences drive most of the onboarding gaps, and it gives the tracking system a baseline that reflects the new program rather than the old one.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Aircraft-specific considerations
Program structure differs by aircraft type and the source document behind it. A type whose program derives from a maintenance review board report carries a task structure that maps differently from one built on a manufacturer's planning document, so the mapping is done against the specific type's program rather than applied as a generic crosswalk.
Jurisdiction-specific considerations
An approved maintenance program is approved under the operator's authority, so a transition that crosses authorities may also cross program structures. A task escalation accepted under one authority's program does not automatically carry under another, so the basis for any extension is mapped explicitly rather than assumed to transfer with the task.
Regulatory limits
The mapping reconciles the two programs at task level and recalculates the due points that follow. It does not approve a maintenance program, grant an escalation or interval extension, make an airworthiness determination, or set the incoming program's due points on the operator's behalf.
What this review does not cover
- Approval or amendment of either maintenance program
- Granting any escalation, bridging, or interval extension
- Physical accomplishment of any task or return-to-service action
Specific to this review
- A one-to-one match between two programs is rare, so a task often maps to part of another, and a loose mapping is where a requirement is silently lost.
- An interval that shortens on the incoming program can render an item overdue the moment it is mapped, so a shorter interval is checked against the last accomplishment before the program goes live.
- An escalation carries only with its basis, so an interval extension granted under the outgoing program is mapped with the approval that supports it rather than as a bare number.
- Tasks the incoming program adds need a first due point set from scratch, because there is no last-accomplishment history for a requirement the aircraft never tracked.
Sources
Federal Aviation Administration. FAA acceptance criteria for electronic recordkeeping systems and electronic signatures.
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). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Transport Canada. Canadian airworthiness, maintenance records (CAR 605/571), and Airworthiness Directive requirements (CAR 593).
Frequently asked questions
What happens to a task that has no equivalent in the new program?
It is not simply dropped. The mapping records the orphaned task and how its requirement is met under the incoming program, whether by another task, a different interval, or an item that has to be added, so the requirement is accounted for rather than lost.
Does an interval escalation carry over automatically?
No. An escalation carries only with the basis that supports it. The mapping carries the extension together with its approval rather than as a number, so the incoming program does not inherit an interval it has no basis to run.
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.
Walk through your situation with an engineer who has done this work.