A320 family engines
Airbus A320 family engine shop-visit records review
This review verifies that the engine shop-visit package for an Airbus A320 family aircraft supports the life-limited part status and workscope the records assert. It is run for a lessor, operator, or manager evaluating or transferring an A320 family asset with recent engine work. The work checks shop reports, module build records, test-cell data, and release certificates, then follows each disk and spool through the build so the trace holds. You receive a supported exception list, a source map for the shop visit, and a closure plan for the specific engine serial numbers on the tail.
When this review is needed
- An engine came off the wing for a shop visit and the package has to be reconciled before the asset trades.
- A buyer is pricing green-time and LLP life and needs the shop report to support the claimed status.
- Modules were swapped at the shop and the build records must trace each disk to its origin.
- A lease return turns on the engine condition and the release certificates have to hold up.
The problem
An A320 family engine shop visit generates a thick package where the value hides in a few pages: the module build sheet, the disk sheets, and the release certificate. Modules move between engines during a visit, so a disk that looks accounted for on the summary can trace to a build the paperwork never fully documents. When the package is incomplete, the green-time and LLP life it is meant to prove rest on the shop's word rather than the records.
What gets reviewed
- Shop report and workscope reconciled to the engine serial number on the tail
- The module build records traced through each disk and spool installed at the visit
- Life-limited part life confirmed against disk sheets rather than the summary alone
- Acceptance run data from the test cell checked against the closing workscope
- Release certificate matched to the parts actually built into the engine
- Piece-part trace followed where modules were exchanged during the visit
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
- Each installed LLP traces to a disk sheet showing cycles used and remaining life
- The module build record reconciles with the parts listed on the release certificate
- Test-cell acceptance data is present and consistent with the workscope performed
- Disks introduced from another engine carry their own trace across the swap
- The engine serial number on the package matches the one recorded on the airframe
Evidence normally required
- The full engine shop-visit package for each serial number on the tail
- Build records and disk sheets for the parts installed at the visit
- The test-cell acceptance run report for the visit
- The release certificate closing the visit
- The engine LLP status list carried on the aircraft records
Common discrepancies
- An LLP whose remaining life rests on the status summary with no disk sheet behind it
- A module build that swapped a disk in without carrying its trace across the exchange
- A release certificate listing parts that do not match the build record
- Test-cell data missing for a shop visit the status treats as complete
What is at stake
A shop-visit package that cannot substantiate LLP life forces a conservative assumption that discounts the engine, and a broken trace at a module build can strand a high-value disk on resale. If the release certificate does not match the parts installed, the engine's return-to-service basis is open to challenge exactly when the asset is under scrutiny.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Frame the visit
Confirm the engine serial number and workscope, then pull the package for that shop visit.
Follow the build
Trace each installed disk and spool through the module build and its disk sheet.
Match the release
Reconcile the release certificate and test-cell data against the parts built into the engine.
List the exceptions
Flag figures the package cannot substantiate and plan recovery of the missing documents.
What the buyer receives
- A supported exception list naming each part or figure the package cannot substantiate
- A source map linking LLP life and workscope to the shop-visit evidence
- A closure plan to recover the missing build or release documents per engine serial
Who uses the output
- Asset managers valuing green-time and LLP life on the specific engines
- Records teams assembling the shop-visit evidence a buyer will require
- Continuing-airworthiness teams confirming the engine return-to-service basis holds
How the work fits into the transaction or program
The shop-visit review supports the LLP traceability position and the engine value that a transaction or lease return depends on. Its exception list drives recovery of the missing disk sheets and release documents from the shop while the visit is recent, and the source map feeds the engine section of the data room.
Aircraft-specific considerations
A320 family engines run in short-sector, high-cycle service, so shop visits are frequent and disks accumulate cycles fast, which puts LLP life at the center of the package. Module exchanges are common on these engines, and the swap is where a disk most often loses its trace, so the review follows piece-part history through each build rather than trusting the closing summary.
Jurisdiction-specific considerations
A shop visit released on an FAA Form 8130-3 or an EASA Form 1 has to be acceptable to the register the aircraft flies under, so the review checks that the release certificate carries the dual-release or the acceptance the receiving system needs rather than assuming one form satisfies both.
Regulatory limits
The review confirms the shop-visit package supports the recorded status and trace. It does not certify the engine, set LLP life on an authority's behalf, or determine that the engine is airworthy.
What this review does not cover
- Physical inspection, borescope, or test of the engine
- Re-certification or re-life of any life-limited part
- Setting a value or price for the engine
Specific to this review
- The disk sheet, not the status summary, is the document that actually proves an LLP's remaining life at resale.
- Module swaps during a shop visit are the most common point where a high-value disk loses its trace.
- A release certificate that lists parts inconsistent with the build record puts the whole visit's return-to-service basis in question.
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
Why is a status summary not enough to prove LLP life?
A summary is a rollup that a buyer or auditor will trace to source. The disk sheet from the shop visit is the document that shows cycles used and remaining life for the actual part installed, so the review confirms the summary matches those sheets rather than relying on it alone.
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.