Airbus A220 family engine shop-visit records review

When this review is needed

• An engine has come back from shop and its package has to support the value the visit added.
• A buyer is pricing the tail on shop-visit history and needs each build reconciled to its parts.
• The engine will feed a future module build and the current LLP and part status must be proven from the package.
• A shop visit was accepted at redelivery with open items in the package that were never reconciled.

The problem

A shop-visit package is a stack of documents from different stations in the shop, and value depends on whether they tell one consistent story. The workscope, the module build records, the parts installed, the test-cell run, and the release certificate each come from a different point in the visit, and a break between any two of them, a part in the build sheet that never appears on a release, or LLP data that does not carry into the module record, means the package does not fully close. The stack looks thick, but thickness is not reconciliation.

What gets reviewed

• Workscope reconciled to the module build records that carried it out
• Parts installed in the build matched to their release certificates
• Module build records reconciled to the LLP and life-limited data they carry
• Test-cell data confirmed present and consistent with the completed workscope
• The final release certificate reconciled to the parts and work in the package
• Open or deferred items from the visit identified and their status resolved

What gets validated

• The workscope matches the work the module build records show was performed
• Each part installed in the build has a release certificate supporting it
• LLP data in the module records agrees with the parts and cycles in the build
• Test-cell results are present and consistent with the completed workscope
• The final release reconciles to every part and task the package documents

Evidence normally required

• The full engine shop-visit package for the visit under review
• The workscope or induction document that opened the visit
• Module build records and the installed-parts list
• Release certificates for the parts and the engine
• Test-cell data and any deferred-item list from the visit

Common discrepancies

• A part on the build sheet that never appears on a release certificate in the package
• LLP data in the module record that does not agree with the installed parts
• Test-cell data missing for a workscope that should have required it
• A deferred item accepted at redelivery and never reconciled in the package

What is at stake

A shop visit whose package does not reconcile cannot be relied on for the value it supposedly added, so a buyer discounts it or a valuation ignores it. A part installed in the build but unsupported by a release becomes a trace break the next build inherits, and reconciling a package after the shop has closed the visit is far harder than catching the gap while the paperwork is fresh.

How the work runs

What the buyer receives

• A supported exception list where the shop-visit package does not reconcile
• A source map tracing workscope, build, test, and release through the visit
• A closure plan to recover the missing package elements for this tail

Who uses the output

• Records teams confirming a shop visit supports the value it claims
• Engine planners proving the LLP and part status the next build will inherit
• Asset managers pricing the tail on shop-visit history that actually reconciles

How the work fits into the transaction or program

The shop-visit review closes the engine record that LLP trace and the maintenance program both draw on. It reconciles the package before a valuation or a future build relies on it, so the parts, life data, and release the visit produced carry forward as a consistent record rather than a stack that has never been checked end to end.

Aircraft-specific considerations

A220 engines run a modular architecture, so a shop-visit package has to reconcile at the module boundary where parts and life data move between builds. The fleet is young enough that most engines have a short shop history, which makes a single visit's package proportionally more important to value than on an engine with many visits behind it. The review reconciles each build record to the LLP data it carries because that boundary is where the package most often fails to close.

Jurisdiction-specific considerations

Engine and part releases in an A220 shop-visit package may sit on an FAA Form 8130-3 or an EASA Form 1 depending on the shop, and a dual-release covers both. The review confirms the release paperwork in the package supports the tail's register and flags parts that would need a further release before a move between systems.

Regulatory limits

The review reconciles the shop-visit package to the records within it. It does not certify the engine, approve the workscope, or return the engine to service. Confirming that a release exists in the package is an evidence check, not an endorsement of the maintenance the release covers.

What this review does not cover

• Any engine inspection, test, or disposition
• Approval of the workscope or the maintenance performed
• Any airworthiness or return-to-service decision on the engine

Specific to this review

• A thick shop-visit package is not a reconciled one: the test is whether workscope, build, test, and release tell one story.
• The module boundary is where the package most often breaks, because parts and life data move between builds there.
• A part in the build with no release becomes a trace break the next module build inherits.
• On a young engine, a single visit's package carries a larger share of the engine's documented value than on a high-time engine.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits