Maintenance program records validated against a scanned archive

When this review is needed

• The approved program has been revised repeatedly and no one has confirmed the due list tracks the current revision.
• Escalations granted years ago still drive intervals and their approval letters have not been sighted since scanning.
• An operator change or bridging exercise is coming and the program history must be demonstrable.
• Sampled last-done dates in the tracking system disagree with the check packages in the archive.

The problem

A maintenance program lives in three places that drift apart: the approved document, the tracking system's due list, and the accomplishment records. Revisions change intervals, escalations and de-escalations layer approvals on top, and each migration re-keys the data. The scanned archive holds the proof of all of it, dispersed through approval letters, revision transmittals, and check packages, while the due list quietly runs on whatever numbers survived the last system change.

What gets reviewed

• The current due list mapped task by task to the approved program revision in force
• Interval escalations and permitted variations traced to their approval documents in the archive
• Program revision history reconstructed from transmittals and acceptance correspondence
• Sampled last-done and next-due values verified against scanned check and task-card evidence
• Out-of-phase and bridged tasks examined for the analysis that justified their positions

What gets validated

• Every sampled task's tracked interval equals the interval in the approved revision or a documented variation
• Escalation approvals in the archive cover the tasks and durations the due list applies them to
• Revision transmittals form an unbroken sequence up to the revision the operator claims
• Last-done dates driving projections match the signed accomplishment evidence
• No task disappeared from the due list without a deletion supported by the program basis

Evidence normally required

• The current task due list export with intervals and last-done data
• The approved maintenance program document at its claimed current revision
• Scanned archive access covering approval letters, transmittals, and check packages
• Escalation and reliability documentation as scanned
• Any bridging analyses from previous operator or program transitions

Common discrepancies

• Intervals still reflecting a superseded revision because a program update never reached the tracking system
• An escalation applied fleet-wide when its approval letter covered specific serial numbers
• Revision transmittals missing from the archive mid-sequence, leaving the current basis unprovable
• Due-list tasks whose last-done evidence sits in the archive under a check number the index never linked

What is at stake

A task tracked at an interval the approved basis does not support is an overdue-maintenance exposure hiding in plain sight, and authorities treat it that way when found. Program findings at audit scale badly, because one unsupported interval implies the whole due list needs verification. At transition, a program history that cannot be evidenced forces conservative bridging, repeating checks the aircraft had legitimately completed.

How the work runs

What the buyer receives

• A task-level basis reconciliation showing where the due list and approved program diverge
• The corrected digital index linking approvals, transmittals, and evidence to the tasks they govern
• A findings package for the CAMO with divergent tasks graded by compliance exposure

Who uses the output

• CAMO leads correcting the due list and dispositioning divergent tasks
• Records teams substantiating program history at audits and transitions
• Maintenance planners rebuilding confidence in projected due dates

How the work fits into the transaction or program

Program validation is usually the last review run on a corrected archive index, because it consumes the check packages, task cards, and approvals the earlier reviews located. Its findings hand off directly to the CAMO's compliance process, and its reconciliation becomes the backbone of any future bridging or operator-transition exercise.

Jurisdiction-specific considerations

Air carrier programs under 14 CFR 121.380 and 135.439 carry explicit recordkeeping duties, and 91.417 covers the broader retention baseline, while EASA operators hold the program and its records through the CAMO under Regulation 1321/2014, with ICAO Annex 6 setting the international frame. Escalation practice differs notably between regimes, so the review reads each variation against the approval mechanism its regime actually offers.

Regulatory limits

The review reconciles records with the approved basis. It does not approve programs, intervals, or escalations, does not declare tasks compliant or overdue in a regulatory sense, and does not substitute for the CAMO's or the authority's determinations. It gives those parties an evidenced starting point.

What this review does not cover

• Development or revision of the maintenance program itself
• Reliability analysis supporting new escalations
• Execution of any maintenance the reconciliation shows as due

Specific to this review

• Interval errors introduced during a tracking-system migration are systematic rather than random: one mis-mapped field can shift a whole ATA chapter's intervals at once.
• Escalation approvals age poorly in archives because they arrive as correspondence rather than maintenance records, and scanning projects often route correspondence to a separate, less-indexed batch.
• A due list can be arithmetically perfect and still unsupported, when every projection is correct against a basis document the operator can no longer produce.
• Bridging at transition rewards operators who can evidence program history; the difference between evidenced and asserted history is often measured in repeated heavy-check content.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits