A350 shop visit
Airbus A350 family engine shop-visit records review
This review works through the engine shop-visit package for an Airbus A350 and confirms the shop report, module build records, test-cell data, and release certificate tell one consistent story. It is run for a buyer, lessor, or CAMO that needs the last shop visit to hold before a transfer, a lease return, or the next removal. The work reconciles the workscope performed against the parts installed, the build records against the release, and the test-cell results against the return to service. You receive an exception list of inconsistencies across the package, a source map, and a closure plan for this engine.
When this review is needed
- An A350 is transferring and the last engine shop visit drives the engine's value and status.
- A lease return requires the shop-visit package to be confirmed before the return condition is met.
- A module build changed the engine's LLP content and the package has to reconcile to it.
- A shop-visit package was inherited and its internal consistency has never been checked.
The problem
An engine shop-visit package is a stack of documents produced by different parts of a shop, and they only prove the visit if they agree with each other. When the module build records show one LLP configuration and the release certificate another, or the test-cell data does not match the workscope claimed, the package looks thorough while the story inside it does not close. On an A350 the engine's high shop-visit rate means several of these packages stack up, and an inconsistency in an early one carries forward.
What gets reviewed
- The shop report and the workscope actually performed
- Module build records and the LLP configuration they establish
- Test-cell data and its agreement with the return to service
- The release certificate reconciled to the build and the workscope
- Parts installed at the visit against the certificates supporting them
- Consistency across the package documents for the same engine event
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
- The workscope in the shop report matches the parts installed and the module build records
- Module build records and the release certificate agree on the LLP configuration
- Test-cell data supports the return-to-service condition the release asserts
- Parts installed at the visit carry release certificates for the serial numbers fitted
- No two documents in the package assert contradicting status for the same item
Evidence normally required
- The engine shop-visit package for the visit under review
- The shop report and workscope documentation
- Module build records and the LLP status after the visit
- Test-cell data and the return-to-service release
- Release certificates for parts installed at the visit
Common discrepancies
- Module build records and the release certificate that disagree on LLP configuration
- A workscope claimed in the shop report that the parts installed do not reflect
- Test-cell data that does not support the return-to-service condition asserted
- A part installed at the visit with no release certificate for the serial fitted
What is at stake
A shop-visit package that does not reconcile leaves the engine's post-visit status unproven, which forces a conservative read at the next transaction or blocks a lease return that depends on the visit. An LLP configuration that the build records and the release disagree on undermines the trace built on top of it, and reconciling the package after the shop and its people have moved on is far harder than catching it now.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Set the event
Assemble the package for the visit and fix the workscope it claims to document.
Reconcile the build
Check the module build records and release agree on the LLP configuration.
Test to the return
Confirm the test-cell data supports the return-to-service condition asserted.
Flag and plan
List the inconsistencies and sequence the reconciliation for this engine.
What the buyer receives
- An exception list of inconsistencies across the shop-visit package
- A source map reconciling the shop report, build records, and release
- A closure plan to resolve the inconsistencies for this engine
Who uses the output
- Asset and acquisition teams pricing the engine status the visit supports
- CAMO and records teams confirming the visit before a return or removal
- Buyers requiring a reconciled shop-visit package before they accept the engine
How the work fits into the transaction or program
The review sits after a shop visit and before the package has to carry the engine's status into a transaction, a return, or the next removal. Its exception list drives the reconciliation while the shop can still be reached, and the source map becomes the confirmed post-visit baseline the LLP trace builds on.
Aircraft-specific considerations
The A350's engines run a high shop-visit rate, so several packages accumulate over the aircraft's life and an inconsistency in an early visit carries into every status built after it. The review reconciles the module build against the release for each package, because that is the junction where an A350 engine's post-visit LLP configuration most often stops agreeing with itself.
Jurisdiction-specific considerations
A shop-visit package released under one authority and an engine moving to an operator under another can call for release evidence in different forms, and the receiving operator may require the package re-evidenced. The review notes where the shop-visit records will need supplementing for the system the engine is heading into.
Regulatory limits
The review confirms the shop-visit package is internally consistent and supported. It does not approve the workscope, release the engine, or make an airworthiness determination on the engine or its modules.
What this review does not cover
- Performing or approving any engine workscope
- Physical inspection or test of the engine
- Any airworthiness determination on the engine
Specific to this review
- A shop-visit package proves the visit only if its documents agree, so the failure mode is internal contradiction, not a missing page.
- The module build against the release is where an A350 engine's post-visit LLP configuration most often stops agreeing with itself.
- An inconsistency in an early shop visit carries into every status built after it, so catching it early is worth more than catching it later.
- Test-cell data that does not support the return-to-service condition asserted is a subtle break, because both documents exist and only disagree on read.
- The A350 engine's high shop-visit rate stacks several packages over its life, so a reconciliation done once has to hold against every later event.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
The engine ran fine after the visit. Why does the package need reconciling?
The engine running does not prove the records agree. If the build records and the release disagree on LLP configuration, the post-visit status is unproven in the file, and that gap surfaces at the next transaction or return long after the shop is unreachable.
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.