Maintenance program
Maintenance-program records review
A maintenance-program records review confirms that the operator's approved maintenance program is current, properly revised, and that its scheduled tasks trace back to the source documents they derive from. It is used before a purchase, a lease return, or an operator transition. It checks the program approval, the revision history, escalations and reductions, and the link from each recurring task to its source. You receive a program-to-source map, the tasks that cannot be traced, and the evidence needed to close each gap.
When this review is needed
- An aircraft will move to a new operator's program and the current program has to be understood first.
- A buyer wants the approved program and its revision basis confirmed before pricing the asset.
- A return references the maintenance program and the lessor needs its currency and approval verified.
- Escalations or task reductions have been applied and the basis for each needs confirming.
The problem
The maintenance program defines what gets done and when, but it is a living document layered with revisions, escalations, and operator-specific tasks. A task can sit in the program with no source behind it, a revision can lag the latest source-document issue, and an escalation can rest on a basis that is no longer in the records. A program that is current on its cover page can be out of step with the sources it should follow.
What gets reviewed
- The approved maintenance program, its approval, and its applicability to the aircraft
- The revision history and whether it tracks the relevant source-document issues
- Each recurring task and the source document or analysis it derives from
- Escalations and reductions and the basis recorded for each
- Operator-specific and special tasks added outside the source baseline
- Tasks the program carries that no current source supports
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 program is approved and applicable to the specific aircraft and configuration
- The revision level tracks the source-document issues the program should follow
- Each recurring task traces to a source document, modification, or analysis
- Escalations and reductions carry a recorded, retrievable basis
- No task lacks a source and no current source requirement is missing from the program
Evidence normally required
- The current approved maintenance program and its approval evidence
- The program revision history
- Source documents the program derives from and their issue status
- Escalation and reduction approvals and their supporting analysis
- The aircraft configuration the program is meant to cover
Common discrepancies
- A scheduled task with no source document or analysis behind it
- A program revision that lags the current issue of its source
- An escalation whose supporting basis is no longer in the records
- A source-added requirement that never reached the program
- Operator-specific tasks carried with no record of why they were added
What is at stake
A program that has drifted from its sources can carry tasks at the wrong interval or miss tasks a newer source added. On an operator transition, an unverified program is hard to map to the receiving program, and reconstructing the basis for each escalation after the move is slower than confirming it before.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Confirm approval and scope
Establish that the program is approved and applicable to the specific aircraft, configuration, and operating rule it is meant to cover.
Walk the revision history
Check that the revision level tracks the source-document issues the program follows and note where it lags.
Trace tasks to sources
Tie each recurring task to its source document, modification, or analysis, and confirm escalations carry a retrievable basis.
List untraceable items
Record tasks with no source and source requirements missing from the program, then recommend a basis to obtain or remove for each.
What the buyer receives
- A program-to-source map showing each task and its origin
- A list of untraceable tasks and missing source requirements
- A recommended closure path for each gap with the basis to obtain or remove
Who uses the output
- Continuing-airworthiness teams confirming the program is current and supported
- Transition teams mapping the program to a receiving operator
- Acquisition and asset teams judging program quality and currency
How the work fits into the transaction or program
The review supports a pre-purchase, a redelivery, or an operator transition by confirming the program is approved and traceable to its sources. It feeds the program-bridging effort and the planning that maps tasks to a receiving program.
Jurisdiction-specific considerations
An approved program reflects the authority and operating rule it was built under. Where the aircraft changes operators or authorities, the review identifies which escalations and tasks rest on an approval the receiving authority will need to re-establish.
Regulatory limits
The review confirms that the program records are complete, consistent, and traceable to their sources. It does not approve a program, grant an escalation, or make an airworthiness determination.
What this review does not cover
- Approval of the maintenance program or any escalation
- Building a receiving operator's program
- Any airworthiness determination on the aircraft
Specific to this review
- The program is a layered, living document, so the failure mode is drift between its current revision and the source-document issues it should follow.
- An escalation is only as defensible as the basis still in the records; a granted escalation with a missing basis is a finding, not a credit.
- Operator-specific tasks added outside the source baseline often outlive the reason they were created, and the records rarely explain them.
Sources
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.
International Civil Aviation Organization. International standards for aircraft operation, including maintenance program and recordkeeping expectations.
Frequently asked questions
Do you check whether the tasks were actually performed?
This review confirms the program itself is approved and traceable to its sources. Whether each due task was accomplished is a separate task-card and tracking question that builds on this baseline.
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.