Maintenance program records review when an MRO supports an operator transfer

When this review is needed

• A customer is inducting an aircraft it just took over and wants the MRO to plan a check from another operator's program data.
• The outgoing operator ran escalated intervals and the substantiation for those escalations has not been produced.
• Last-done next-due extracts arrive in a format the planning system cannot verify against source documents.
• The bridging analysis between the two programs was drafted quickly and the MRO will absorb the cost if it is wrong.

The problem

An MRO planning an induction check works from data it did not create: a program status export, a task-by-task history, a bridging table. Under 14 CFR 121.380, 135.439, or the EASA Part-M framework, the operator owns that data, but the MRO turns it into a workscope, a slot, materials, and manpower. If the last-done dates are soft or an escalation was never substantiated, the check grows on the hangar floor, and the schedule, the quote, and the customer relationship absorb the difference.

What gets reviewed

• Approved program revision history reconciled against the revisions actually applied in the task histories
• Escalations and interval changes traced to their approval and the reliability data behind them
• Last-done and next-due values sampled back to task cards, work orders, and check dossiers
• The bridging analysis tested for task-by-task coverage between outgoing and incoming programs
• Out-of-phase and one-time tasks located and confirmed against their source requirements
• ICA and supplemental requirements from STCs checked for inclusion in the program status

What gets validated

• Sampled last-done entries match the signed accomplishment record, at date, hours, and cycles level
• Every escalated interval carries an approval that was in force when the escalation was used
• Tasks introduced by mid-life modifications appear in the status with correct initial thresholds
• The bridging table leaves no outgoing-program task unmapped, undeferred, and unexplained
• Utilization figures driving next-due projections agree with the logbook totals at handover

Evidence normally required

• The outgoing operator's approved maintenance program and revision record
• Program status export with last-done and next-due for all tasks
• Check dossiers and work orders supporting recent accomplishments
• Escalation approvals and supporting reliability analyses
• The draft bridging analysis to the receiving operator's program

Common discrepancies

• Next-due projections computed on planned utilization that drifted far from actual utilization in the final lease year
• An escalation applied fleet-wide by the old operator that the receiving program does not carry, silently shortening intervals at induction
• One-time tasks from an SB or STC marked complete with no locatable accomplishment record
• A bridging table that maps task numbers but misses scope differences hidden inside renumbered tasks

What is at stake

Program data that fails during the check converts directly into unplanned findings, defect cards, and slot overruns. Tasks planned as not-yet-due that turn out overdue must be worked immediately, materials arrive late, and the MRO ends up arbitrating between the old operator's records and the new operator's expectations while the aircraft sits open.

How the work runs

What the buyer receives

• A validated program-status baseline the planning team can load with stated confidence levels
• A soft-data register listing tasks whose histories cannot support the planned interval treatment
• A query pack for the customer and outgoing operator, sequenced by workscope impact

Who uses the output

• MRO program managers freezing the induction workscope and quote
• Quality leadership deciding what the organization can accept as accomplished history
• The customer's CAMO, which must answer the queries and own the bridging decisions

How the work fits into the transaction or program

The review slots between records delivery and workscope freeze in the induction timeline. It protects the MRO's slot planning and quote from data risk it cannot price, and it hands the customer's CAMO a specific query list early enough that answers arrive before the aircraft does, rather than during the check.

Jurisdiction-specific considerations

Program requirements sit with the operator under 14 CFR 121.380 or 135.439 on the FAA side and under Regulation 1321/2014 for EASA operators, with ICAO Annex 6 framing the recordkeeping expectations across registries. A transfer that crosses these frameworks changes how escalations, tolerances, and program approvals carry over, which is exactly where a bridging analysis needs independent checking.

Regulatory limits

The review tests records against the programs and approvals provided. It does not approve a maintenance program or a bridging analysis, does not grant interval escalations or tolerances, and does not relieve the operator of its continuing-airworthiness responsibility; it equips the MRO and the CAMO to exercise their own.

What this review does not cover

• Authoring the bridging analysis or the receiving operator's program amendment
• Workscope development, material provisioning, or check planning itself
• Reliability analysis to justify new escalations

Specific to this review

• Interval escalations are operator-specific approvals; they evaporate at transfer unless the receiving program re-earns them, and status exports rarely flag which intervals were escalated.
• Renumbered tasks are the blind spot of bridging tables: two task codes can map cleanly while the inspection scope behind them differs.
• Utilization assumptions age badly in an aircraft's final months with an operator, when flying often drops, so next-due projections need recomputation at actual hours and cycles.
• The cheapest moment to challenge a soft last-done entry is before workscope freeze; the most expensive is after the access panels are open.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits