Program compliance
Maintenance program records review in the shop-visit source file
The maintenance program status that leaves a shop visit sets every due date the operator plans against next. This review checks that status against two references: the approved program basis in force and the tasks the source file shows were actually accomplished. It is run for CAMO, quality, or lessor teams as the package closes. The outcome is a task-level exception listing showing where the outgoing status diverges from either the program or the evidence.
When this review is needed
- The visit accomplished program tasks and the next-due projections must be rebuilt from evidence.
- The approved program was revised during or shortly before the visit and the status may straddle two baselines.
- The asset is bridging between maintenance programs as part of an operator change.
- A due-list anomaly surfaced after a previous visit and confidence in the status data is low.
The problem
Program status is a computed artifact: intervals from the approved program applied to accomplishment dates from the shop floor. Errors enter from both sides at once. The visit signs off tasks against one revision of the program while the planning system carries another, or a card closes a task at a different level than the program defines, and the recomputed due list silently inherits the mismatch. Planners then schedule real aircraft against numbers nobody has re-derived from source.
What gets reviewed
- Program tasks signed off in the visit reconciled to their cards and sign-off records
- Intervals in the outgoing status compared against the approved program revision in force
- Accomplishment dates and utilization at accomplishment verified from the source file
- Next-due calculations spot-recomputed across calendar, hours, and cycles controls
- Bridging decisions and one-time adjustments checked for their approval trail
- Tasks escalated, de-escalated, or deleted since the last visit traced to a program amendment
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 accomplished task in the status maps to a signed card describing work at the task's defined level
- The interval shown per task equals the interval in the approved program document, not a legacy value
- Utilization figures used for next-due arithmetic match the airframe and engine records at the event
- Sampling and threshold tasks show the fleet or serial applicability the program assigns them
- No task disappears between the incoming and outgoing status without a documented reason
Evidence normally required
- Outgoing maintenance program status or task due list
- The approved maintenance program at the applicable revision, with any bridging documents
- Signed task cards and the visit's accomplishment summary
- Incoming status as loaded at induction
- Utilization records covering the visit period
Common discrepancies
- Intervals in the planning system left at a prior program revision after an amendment tightened them
- A task recorded accomplished at check level while the program defines it at zonal or item level
- Next-due dates computed from estimated rather than actual utilization at accomplishment
- A bridging adjustment applied at operator change with no approval reference in the file
What is at stake
A wrong interval or unsupported accomplishment date propagates into every projection until it is found, and it is usually found by an auditor asking why a task ran past due. Overruns discovered retrospectively can require an airworthiness review, unscheduled downtime, and disclosure in the next transaction. Under-running tasks is quieter but burns maintenance cost on intervals the program never required.
How the work runs
Fix the program basis
Identify the approved program revision and any bridging documents governing the visit.
Verify accomplishments
Tie each status entry claiming accomplishment to its signed card and utilization point.
Recompute forward
Re-derive next-due values on a sampled or full basis and compare with the outgoing list.
Hand over exceptions
Report divergences with the program clause and source document behind each one.
What the buyer receives
- A task-level exception listing against both the program basis and the accomplishment evidence
- A corrected next-due projection for the tasks the file supports
- A note of program-control weaknesses observed, for the CAMO's own follow-up
Who uses the output
- CAMO planners rebuilding the due list after the visit
- Quality auditors evidencing program compliance to the authority
- Lessor teams confirming the asset's program position ahead of remarketing
How the work fits into the transaction or program
Program verification connects the shop event to the operator's planning horizon: task-card review proves individual accomplishments, and this review proves the recomputed future built on them. It also protects the bridging record, which becomes the reference point every later operator transition reaches back to.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
US operators under 14 CFR 121.380 or 135.439 and EU operators under Part-CAMO carry differently structured program-record obligations, and ICAO Annex 6 frames the expectations many other registries apply. An asset moving between systems rarely maps task for task, which is why the review treats the bridging documentation as part of the status, never as background.
Regulatory limits
The review measures conformity between records, program, and evidence. It does not approve maintenance programs or amendments, grant escalations or variations, perform airworthiness reviews, or authorize any deviation from the approved intervals; those decisions sit with the operator, the CAMO, and the competent authority.
What this review does not cover
- Authoring or revising the maintenance program itself
- Reliability analysis or optimization of task intervals
- Loading corrected data into the operator's planning system
Specific to this review
- Planning systems seldom flag when a program amendment changes an interval; the old value persists until a human reconciles the revision, and visits are where the drift surfaces.
- The gap between task accomplished and task recorded at the right level is the most common defect, and it is invisible on the due list itself.
- Estimated utilization keyed at closeout, meant to be corrected later, hardens into the permanent record more often than anyone intends.
- Bridging files are read years after they are written, usually by people who were not there; a missing approval reference converts a routine transition into a reconstruction project.
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 planning system recalculates due dates automatically. What can be wrong?
The arithmetic is rarely the problem; the inputs are. Systems compute faithfully on whatever interval and accomplishment data they hold, and the review tests those inputs against the approved program and the signed cards, which is where the mismatches live.
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.