Program-control gap
Missing maintenance-program revision history
Missing maintenance-program revision history means the records cannot show which revision of the maintenance program governed the aircraft at each point in its life, so the intervals that scheduled tasks were flown to have no documented basis. It is a problem for lessors, airlines, and MROs at induction, redelivery, or a program transfer. The check reads program revision logs, effectivity dates, task escalations, and the inspection records that should map to a stated revision. You receive the periods with no controlling revision, the tasks whose due points cannot be justified, and the path to reconstruct the trail.
When this review is needed
- An aircraft is moving onto a new operator's program and the incoming team has to confirm what controlled it before, so the bridge from the old program to the new one holds.
- A redelivery requires the maintenance program and its revision history, and the binder names a current revision with no trail showing how the aircraft arrived at it.
- An escalation was applied to an interval and the records cannot show the approved revision that authorized the longer period.
- A registry or program change happened mid-life and the controlling document on either side of the change is not in the file.
The problem
Scheduled tasks are flown to intervals set by a maintenance program that is itself revised over the years as the type matures and escalations are approved. The accomplishment record shows a task was done, but it rarely names the program revision that set the interval, and the revision log that would tie the two together is one of the first documents to drop out at an operator change. Without it, every due point in the status list rests on an interval no one can trace to an approved source.
What gets reviewed
- The maintenance program of record and the full sequence of revisions issued over the aircraft's life
- Effectivity dates tying each revision to the period it governed
- Task escalations and the approval that authorized each longer interval
- Inspection records mapped to the revision in force when each scheduled task was flown
- Bridging documentation across any operator, registry, or program change
- Reliability program output that supports an escalation claimed in the records
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 period of the aircraft's life maps to a single identifiable controlling revision
- Each escalated interval traces to the revision and approval that authorized it
- Each scheduled task accomplishment falls within the interval the governing revision set
- Revision effectivity dates are continuous with no unaccounted gap between revisions
- A program or operator change shows a documented bridge rather than an undocumented jump
Evidence normally required
- Maintenance program of record with its revision log
- Approved escalation records and supporting reliability data
- Scheduled inspection accomplishment records across the period in question
- Bridging or transfer documentation from prior operators
- Status list showing current due points and the intervals behind them
Common discrepancies
- A multi-year period with no identifiable controlling revision on file
- An escalated interval flown with no approved revision authorizing the longer period
- A revision log that skips one or more issues, leaving a gap in effectivity
- Scheduled tasks accomplished at intervals that do not match any revision the records can produce
- A program change at an operator transfer with no bridging document connecting the two baselines
What is at stake
If the controlling revision for a period cannot be shown, the intervals flown in that period cannot be justified, and the receiving operator may have to revert tasks to the most conservative published interval or re-establish the baseline from scratch. That can pull a block of inspections forward into the first check after transfer and turn a clean induction into an unplanned shop input.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Build the revision timeline
Assemble every program revision with its effectivity dates and lay them against the aircraft's life to find periods with no controlling document.
Test the intervals
Map scheduled task accomplishments to the revision in force when each was flown and flag intervals that match no producible revision.
Trace escalations
For each escalated interval, locate the approved revision and supporting reliability data, and register any that cannot be supported.
Reconstruct the baseline
Identify where each missing revision likely sits, recover what can be recovered, and deliver a defensible current baseline.
What the buyer receives
- A revision timeline showing the controlling document for each period and where it is missing
- A list of tasks whose due points cannot be justified against an approved revision
- A reconstruction path naming the source most likely to hold each missing revision
- A reconciled baseline tying current due points to a defensible interval
Who uses the output
- Continuing-airworthiness staff bridging the aircraft onto a new program
- Records teams assembling the program section of a redelivery binder
- Reliability and programs staff defending an escalated interval
How the work fits into the transaction or program
The review isolates the program-control trail within a broader induction or redelivery audit, so interval problems rooted in a missing revision are separated from problems with the accomplishment records themselves. It feeds the bridging analysis and gives the incoming operator a defensible starting baseline.
Jurisdiction-specific considerations
Program approval and escalation authority differ between the FAA and EASA systems, so a revision approved under one operator's oversight is not automatically the controlling document under another. Where the aircraft crosses authorities, the trail has to show acceptance of the prior program on the receiving side, not just its existence.
Regulatory limits
The review reconstructs and reconciles the program revision trail from the records. It does not approve a maintenance program, authorize an escalation, set an interval on the operator's behalf, or determine that the aircraft is airworthy.
What this review does not cover
- Drafting or approval of a maintenance program or its revisions
- Approval of any interval escalation
- Any airworthiness determination or regulatory acceptance
Specific to this review
- An accomplishment record proves a task was done but rarely names the program revision that set its interval, so the revision log is the only document that joins the two.
- An escalation is only defensible when the approved revision that authorized the longer interval can be produced, not when the longer interval merely appears in the status list.
- When the controlling revision for a period is lost, the safe fallback is the most conservative published interval, which can pull a block of tasks forward at transfer.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Why does the controlling revision matter if the task was done?
The accomplishment shows the work happened, but the interval it was flown to is only defensible if the program revision that set that interval can be produced. Without the revision, the due point has no documented basis.
What happens if a revision cannot be recovered?
The aircraft can usually be bridged onto the new program by reverting affected tasks to the most conservative published interval, then re-establishing the baseline. The review identifies which tasks that affects so the cost is known before transfer.
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.