Program status
Maintenance program records read against the engine-module file
This source review tests whether the maintenance program status claimed for an engine and its modules is supported by the records underneath it. A CAMO, operator, or lessor commissions it when the engine changes program, changes hands, or returns from a shop visit with a reset due list. The task list, intervals, and due calculations are checked against the approved program basis, the build and test records from the last visit, and the utilization history since. It closes with a list of program lines whose status cannot be reproduced from source.
When this review is needed
- An engine is moving between operators and the receiving CAMO must bridge its status onto a different approved program.
- A shop visit reset task accomplishments and the post-visit due list needs proving before the engine flies out.
- The program basis was revised and nobody has confirmed the due list picked up the new intervals.
- A lease transfer requires a program status the counterparty can audit line by line.
The problem
Engine program status is a computed artifact. It depends on the right program revision, the right accomplishment dates, and the right utilization figures, and an error in any input produces a due list that looks precise while being wrong. Teams inherit status exports from a prior operator's system with no practical way to know which lines were computed from evidence and which were carried on trust.
What gets reviewed
- The task list compared against the current approved program basis and its revision status
- Accomplishment dates and utilization at accomplishment traced to visit records, task cards, and logbook entries
- Interval and threshold values checked against the program document rather than the tracking-system export
- Utilization inputs since last accomplishment reconciled with the installation and removal history
- Bridging assumptions from any prior program identified and tested
- Module-level tasks matched by serial to the module actually installed
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
- Each due time on the list recomputes correctly from its accomplishment point, interval, and utilization since
- Accomplishment entries cite evidence that exists in the file, at the claimed date and utilization
- No task references an interval from a superseded revision of the program
- Tasks tied to module serials follow the module, and swaps in the installation history are reflected in the status
- Items added or escalated by AD or SB action appear on the program with the correct control
Evidence normally required
- The current program status export with due list and accomplishment history
- The approved maintenance program or relevant sections, at its current revision
- Shop-visit and task-card evidence for the accomplishments claimed
- Utilization statements and the installation history for the engine and modules
- Any bridging documentation from a previous operator's program
Common discrepancies
- Due times computed from an interval that the current program revision no longer contains
- An accomplishment date entered from a planning record rather than the signed evidence, off by one visit
- Module tasks that stayed with the engine position after the module itself was exchanged
- Utilization gaps between removal and reinstallation that the status quietly interpolates
What is at stake
A due list built on a superseded interval or a wrong accomplishment date either burns margin the engine actually has or, worse, lets a task run past its approved limit. Findings of that kind surface during authority audits and lease redeliveries, and unwinding them means reconstructing years of utilization instead of correcting one line at transfer.
How the work runs
Fix the program basis
Confirm the approved program revision in force and pull the interval set the status should be using.
Trace accomplishments
Follow each claimed accomplishment to signed evidence in the visit packages, task cards, and logbooks.
Recompute the due list
Rebuild due times from verified accomplishment points and reconciled utilization, then compare against the export.
Register the exceptions
Document every line that fails to reproduce, with the evidence gap that explains it.
What the buyer receives
- A line-by-line verification of the due list with each unsupported status flagged
- A register of program exceptions for the engine trace support file
- Corrected accomplishment references where the file contains better evidence than the system cites
Who uses the output
- CAMO and program engineers accepting the engine onto their program
- Lessor technical teams auditing status at transfer or redelivery
- MRO planners scoping the next visit from a due list they can defend
How the work fits into the transaction or program
Program status sits downstream of everything else in the engine-module file: it is only as good as the visit records, logbooks, and utilization data feeding it. This review typically follows the shop-visit package review and runs before bridging onto a new program, so exceptions are settled while the delivering party is still obligated to answer.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
FAA operators carry program recordkeeping obligations under 14 CFR 121.380 or 135.439 and their operations specifications, while EASA engines sit with a Part-CAMO organization under an approved maintenance program per Regulation 1321/2014. Cross-registry transfers are where interval bases most often diverge, because the same task can carry different thresholds under the two approvals, and ICAO Annex 6 retention expectations apply on top for international operations.
Regulatory limits
The review verifies that status is reproducible from records. It does not approve a maintenance program, grant escalations or bridging, or determine airworthiness; program approval remains with the operator's authority, and continued-airworthiness decisions remain with the responsible CAMO or operator.
What this review does not cover
- Writing or revising the maintenance program itself
- Reliability analysis or interval escalation studies
- Entering corrections into the operator's tracking system
Specific to this review
- A status export inherits the assumptions of every system migration before it, and migration defaults are a recurring source of invented accomplishment dates.
- Interval mismatches cluster around tasks amended in the last two program revisions, since older lines have usually been challenged already.
- Bridging is where conservative assumptions get made and then forgotten; a task bridged conservatively in one transfer can be bridged again a lease later, compounding the penalty.
- Module exchanges are the sharpest test of a program status, because task history must split between the departing and arriving serials on one date.
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
Our tracking system already flags overdue tasks. What does this add?
The system computes from the data it holds and flags what that data says. This review tests the data itself: whether accomplishment dates, intervals, and utilization match the signed records. A system will not flag a due list built on a wrong input, because to the system that input is the truth.
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.