Airbus A220 family maintenance program records review

When this review is needed

• A tail is transferring between operators and the incoming program has to bridge from the outgoing one.
• The program in use has drifted from the approved revisions and the difference has never been reconciled.
• A task escalation was applied but the analysis and approval behind it were never captured in the file.
• A buyer needs the program the aircraft is flown to reconciled against what the records actually approve.

The problem

A maintenance program is a living document, and the version the aircraft is actually flown to can drift from the approved revisions in the file. A task interval may reflect an escalation whose supporting analysis was never captured, or a bridging analysis from a prior transition may not carry into the current program. The status list keeps the tail flying against intervals, but whether those intervals trace to an approved revision is a separate question that goes unasked until a transition or a buyer forces it.

What gets reviewed

• Approved program revisions reconciled to the revision the aircraft is flown to
• Task escalations matched to the analysis and approval that support them
• Bridging analyses from prior transitions carried into the current program
• Task intervals in the status list traced to an approved program source
• Program source references confirmed present and current for the tail
• Deviations between the program in use and the approved basis identified

What gets validated

• The revision the aircraft is flown to matches an approved revision on file
• Each task escalation traces to a supporting analysis and its approval
• A prior bridging analysis is reflected in the current program the tail runs
• Every interval in the status list maps to an approved program source
• Program source references are the current issue rather than a superseded one

Evidence normally required

• The approved maintenance program revisions on file for the tail
• The program status list and the intervals the aircraft is tracked to
• Task escalation analyses and their approvals
• Bridging analyses from any prior operator transitions
• The source references the program cites for its tasks and intervals

Common discrepancies

• The aircraft flown to a program revision that does not match the approved issue on file
• A task escalation applied without the analysis that would support it
• A bridging analysis from a prior transition that never carried into the current program
• An interval in the status list that maps to no approved program source

What is at stake

A program whose approved basis cannot be shown puts every interval built on it in question, and a task flown to an unsupported escalation may have to revert to the base interval, pulling work forward. At a transition, a bridging gap between the outgoing and incoming programs surfaces at the first check under the new operator, and reconstructing an escalation basis after the fact is far harder than confirming it when the revision was approved.

How the work runs

What the buyer receives

• A supported exception list where the program in use and the approved basis diverge
• A source map from each interval and escalation to its approved program source
• A closure plan to recover the missing analyses and reconcile the revisions

Who uses the output

• Records teams reconciling the program before a transition or a sale
• Continuing-airworthiness staff confirming intervals rest on an approved basis
• Asset and buyer teams reading program integrity into the value of the tail

How the work fits into the transaction or program

The program review anchors the intervals that task cards, non-routine work, and status tracking all run against. It reconciles the program in use to its approved basis before a transition or a valuation depends on it, so the receiving operator bridges from a documented program and a buyer prices intervals that trace to an approved source.

Aircraft-specific considerations

A220 programs derive from a maintenance review board structure that individual operators tailor, so a tail carries both the baseline program and the operator-specific escalations layered on it. Because the fleet is young, most tails have passed through few program revisions, which makes any bridging analysis from an operator transition a concentrated point of risk rather than one of many. The review traces the escalations and bridges specific to this tail rather than assuming a generic program.

Jurisdiction-specific considerations

An A220 program approved under an FAA operator's oversight differs from one accepted under an EASA continuing-airworthiness structure, and a transition between the two is where the program has to be bridged rather than copied. The review notes where the approved basis for the current program will need rework or fresh acceptance for the receiving system.

Regulatory limits

The review reconciles the program records to their approved basis. It does not approve a maintenance program, authorize a task escalation, or accept the program on any authority's behalf. Confirming an escalation's analysis exists is not the same as approving the escalation.

What this review does not cover

• Authoring, revising, or approving the maintenance program
• Approving task escalations or bridging analyses
• Any airworthiness or program-acceptance decision

Specific to this review

• The program the aircraft is flown to can differ from the approved revision on file, and only reconciling the two surfaces it.
• A task escalation without its supporting analysis may have to revert to the base interval, pulling work forward.
• On a young A220, a single transition's bridging analysis is a concentrated risk because the tail has few program revisions behind it.
• An operator's tailored escalations sit on top of the review-board baseline, so the tail-specific layer is where the program most often diverges.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits