Program basis at transition
Maintenance program records review inside the lease-transition file
The maintenance program status delivered at transition is only as good as the approved program behind it, and this review establishes whether the two still agree. A specialist compares the task due list against the program basis, its revision record, and any escalations or bridging decisions the transition folders contain, then checks that the utilization statements support the due calculations. Intervals that trace to an unapproved revision, an undocumented escalation, or a bridging exercise with no paperwork are raised as exceptions. The transition lead receives that exception list plus the evidence map for every interval that holds.
When this review is needed
- The incoming operator is building its bridging analysis and keeps finding due-list intervals with no visible program source.
- The program was escalated during the lease and the approval trail for the escalation has not been located.
- A mid-term operator change re-based the program and the transition file holds both versions without a reconciliation.
- Redelivery conditions reference the approved program and the due list in the file predates its last revision.
The problem
The approved program and the task due list are maintained by different people on different rhythms: the program changes by formal revision, the due list changes nightly with utilization feeds and planning edits. Over a lease term the two accumulate quiet divergences that no daily process surfaces. A transition forces them back into one frame, usually at the exact moment an incoming CAMO starts asking which revision authorized which interval.
What gets reviewed
- The task due list sampled against the approved program document at its controlling revision
- Escalations and interval changes during the lease traced to their approval records
- Utilization figures behind due calculations verified against the delivered statements
- One-time and out-of-phase tasks checked for the accomplishment records that reset them
- Program-driven requirements arising from repairs, modifications, and ADs cross-checked into the list
- Revision control on the program itself, establishing which revision governed which period of 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
- Every sampled interval on the due list appears in the approved program at the governing revision
- Escalated intervals carry the analysis and approval the escalation process required
- Last-done values on sampled tasks trace to signed accomplishment records in the folders
- Due calculations use utilization figures the delivered statements can reproduce
- Tasks added by AD, SB, repair, or modification action are present with the correct threshold
Evidence normally required
- The maintenance program document with its revision history
- The current task due list as exported for the transition
- Escalation approvals and reliability data referenced by interval changes
- Utilization statements for the lease term
- Acceptance correspondence raising program or bridging questions
Common discrepancies
- A due list built on utilization figures that run ahead of what the delivered statements support
- Intervals still reflecting an escalation the authority approved for the previous operator only
- An out-of-phase task whose last-done value is a system entry with no signed card behind it
- Repair-driven inspections recorded in the repair files that never entered the program
What is at stake
Every interval that cannot be traced to an approved source gets bridged conservatively, and conservative bridging pulls tasks forward into maintenance inputs the plan never budgeted. Escalations lacking their approval trail simply vanish at handover, taking their interval relief with them. The receiving side prices uncertainty in inspections and buffer, and the delivering side pays that price in acceptance friction.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the revisions
Build the timeline of program revisions and interval changes across the lease term.
Sample the list
Test due-list intervals against the governing revision and the escalation approvals.
Verify the resets
Check last-done records and utilization sources behind the sampled due calculations.
Package for bridging
Deliver the exception list and evidence index in the form the receiving side's bridging work consumes.
What the buyer receives
- An exception list mapping each unsupported interval to what is missing: approval, accomplishment record, or utilization source
- A revision timeline showing which program version governed each period of the lease
- An evidence index for supportable intervals, formatted for the receiving side's bridging work
Who uses the output
- Receiving CAMO teams building the bridging analysis on verified rather than assumed intervals
- Transition leads answering program queries with documents instead of assurances
- Planning staff correcting due-list entries before they drive premature or late inputs
How the work fits into the transaction or program
The program strand hands its output directly to the receiving side's bridging exercise, which is the next thing that happens to these records. Verified intervals shrink the bridging workload, and the revision timeline answers the governing-revision questions that otherwise bounce between the parties for weeks.
Jurisdiction-specific considerations
Program approval mechanics differ across regimes: FAA operators carry their program through operations specifications and the recordkeeping rules of 14 CFR 121.380 or 135.439, while EASA operators hold an approved aircraft maintenance program managed by the CAMO under Regulation (EU) 1321/2014, with ICAO Annex 6 behind both. Escalations approved in one system rarely transfer with the aircraft, so a cross-regime transition typically resets interval relief to the baseline program.
Regulatory limits
Nothing in this review approves a program, an escalation, or a bridging outcome, and nothing in it constitutes an airworthiness determination. Program approval and interval relief remain matters between the operator, its CAMO, and the authority.
What this review does not cover
- Authoring the receiving operator's bridging analysis
- Reliability analysis for or against interval escalations
- Amending the program document or the due list
Specific to this review
- Escalation approvals are operator-specific in most regimes, so an interval that was legitimate for the outgoing operator can be unusable to the incoming one.
- Due lists fail quietly: a wrong utilization feed produces plausible dates that no one questions until a transition forces recomputation.
- The governing-revision question matters because a task accomplished correctly under revision twelve can look overdue under revision fourteen.
- Bridging teams reward clean evidence with narrower conservatism; every verified interval trims the buffer they would otherwise add.
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
Does this produce the bridging analysis itself?
No. Bridging belongs to the receiving operator and its CAMO, since it commits their program. What this review produces is the verified input bridging depends on: which intervals are approved, which accomplishments are evidenced, and which figures the utilization record actually supports.
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.