Program compliance
Closing a maintenance program mismatch in operator records
Operator maintenance program mismatch remediation closes the gap between what a tracking system says is due and what the approved maintenance program actually requires. It is run for operators, usually by the records or continuing-airworthiness team with outside support, once a mismatch has surfaced in an audit, a bridging exercise, or a task-card review. The work traces each disputed task back to the program revision, the bridging analysis, and the sign-off history to establish which intervals were actually flown. You get a substantiated finding register, a corrective-action file for the tracking system, and closure evidence that stands up when a regulator or lessor asks how the mismatch happened.
When this review is needed
- An internal or authority audit found tasks being controlled at intervals that differ from the approved program revision.
- A fleet moved onto a new program and the bridging analysis was never fully loaded into the tracking system.
- Task cards reference a superseded program revision and nobody can say when the drift started.
- A lease return or program approval renewal is approaching and the mismatch has to be explained with evidence rather than memory.
The problem
A program mismatch is rarely one bad entry. It usually starts with a program revision, an escalation approval, or a bridging analysis that was applied to some tasks and not others, and then compounds quietly through months of flying. By the time it surfaces, the tracking system, the task cards, and the approved document each tell a slightly different story, and the team that made the original change may be gone.
What gets reviewed
- Comparison of tracked intervals and thresholds against the approved program revision in force for each period
- Reconciliation of escalations, short-term extensions, and bridging analyses against their approvals
- Task-by-task review of where the mismatch changed what was done or when
- Sign-off and task-card sampling to confirm which requirement the work was performed against
- Separation of clerical loading errors from tasks flown past a valid limit
- A closure position for each affected task, with the evidence that supports it
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 tracked interval traces to a specific approved program revision or documented escalation
- Bridging analyses cover every task that changed when the program changed, with approval references
- Accomplished task cards cite the requirement revision that was actually in force at sign-off
- Next-due calculations use the utilization figures recorded in the technical log rather than backfilled estimates
- Corrective entries in the tracking system carry an audit trail instead of silent overwrites
Evidence normally required
- The approved maintenance program, including superseded revisions covering the mismatch period
- Tracking-system task history and current forecast export
- Bridging analyses, escalation approvals, and any short-term extension records
- Completed task cards and work orders for the sampled tasks
- Technical log utilization data for the affected period
Common discrepancies
- Program revisions loaded selectively, leaving a subset of tasks controlled at superseded intervals
- Escalations applied in the tracking system before, or without, the supporting approval
- Bridging analyses that stop at the check level and never address out-of-phase tasks
- Task cards signed against requirement wording that no longer matches the current program
What is at stake
Left open, every task touched by the mismatch becomes arguable. An authority can treat work controlled at the wrong interval as overdue maintenance, a lessor can hold redelivery until the history is reconstructed, and the operator ends up defending its whole compliance system instead of one finding.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Bound the mismatch
Establish which tasks, which program revisions, and which date range the discrepancy actually covers.
Rebuild the requirement history
Lay the approved revisions, escalations, and bridging analyses on a timeline against the tracked intervals.
Test what was flown
Sample task cards and utilization data to separate loading errors from tasks performed late or against the wrong requirement.
Close with evidence
Document each task's position, correct the tracking entries with an audit trail, and assemble the closure file.
What the buyer receives
- A finding register that states, for each task, what the program required and what the records show
- A document and data request list aimed at the approvals and task cards still missing
- A closure file with corrective tracking entries and the evidence behind each one
- A short narrative the operator can hand to an auditor or lessor explaining cause and containment
Who uses the output
- Directors of maintenance answering an audit finding on program compliance
- CAMO and records staff correcting the tracking system without erasing its history
- Lessor-facing teams preparing for a redelivery where the mismatch will be probed
How the work fits into the transaction or program
This remediation sits between the audit that found the mismatch and the routine program compliance the operator wants to return to. It draws on the same sources a lease-return records audit would test, and its closure file becomes part of the evidence set at the next transition or authority review.
Jurisdiction-specific considerations
Under FAA rules the mismatch is judged against the program the operator is obligated to follow, with recordkeeping duties under 14 CFR 91.417, 121.380, or 135.439 depending on the operation. Under EASA, Part-M and Part-CAMO treat the approved aircraft maintenance programme as the controlling document, so a tracking system that drifts from it is a finding against the CAMO's own system and the closure evidence should be framed accordingly.
Regulatory limits
The work establishes what the records support and where they conflict with the approved program. It does not approve escalations, amend the program, make an airworthiness determination, or decide on behalf of any authority whether a task flown past its interval requires further action.
What this review does not cover
- Writing or revising the maintenance program itself
- Negotiating escalation or extension approvals with the authority
- Performing or certifying any maintenance arising from the findings
Specific to this review
- Mismatches concentrate at program revision boundaries; a task loaded correctly today can still have been controlled at the wrong interval for the two years before the revision.
- Out-of-phase tasks are the usual blind spot in bridging: the check content bridges cleanly while stand-alone tasks keep their old due points.
- Silent corrections in the tracking system are worse than the original error, because they destroy the audit trail an authority will ask for first.
- Whether a task was flown past a valid limit often turns on utilization data quality, so the technical log is checked before any overdue conclusion is drawn.
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.
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 a program mismatch automatically mean the aircraft was operated with overdue maintenance?
No. Many mismatches turn out to be loading or transcription errors where the work was performed on time against the correct requirement. The remediation exists to separate those from tasks genuinely controlled past a valid limit, because the two carry very different consequences and the difference has to be shown from task cards and utilization records.
Can we simply correct the intervals in the tracking system and move on?
Correcting forward without documenting the history leaves the operator unable to explain the period the mismatch covers. Authorities and lessors both read edit histories, so each correction should carry a reference to the finding it closes.
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.