Crossing registries
Engine shop-visit records in an import and export package
This review tests whether the engine shop-visit package will hold up when an importing authority reads it. A records specialist works through the last shop-visit reports, module build records, test-cell data, and release certificates, comparing each against the export application, registry-change file, and status summaries the transaction team has assembled. It runs during import, export, or registry-change preparation, before the package goes to the authority. The output is an exception list naming every shop-visit item the source evidence cannot yet support.
When this review is needed
- An export certificate of airworthiness application is being prepared and the engines had shop visits under a previous operator.
- The importing authority has asked for the last shop-visit report and release documentation for each engine.
- A registry change moves the aircraft between FAA and EASA oversight and engine release coverage must match the destination.
- Status summaries quote engine times and cycles that nobody has traced back to the shop-visit paperwork.
The problem
Engine shop-visit paperwork arrives from repair stations in inconsistent shapes: some visits produce a bound report with build sheets and test-cell data, others a folder of scans with pages missing. The transaction team quotes times, cycles, and LLP status from summaries while the underlying visit records sit unread. Importing authorities do read them, and they read them late in the timeline, when a missing test run or a single-authority release is hardest to fix.
What gets reviewed
- Final shop-visit reports for each installed engine, read against the workscope that opened the visit
- Module build records and the serial numbers they document, compared with the configuration the status summary claims
- Test-cell acceptance data and the performance margins recorded at release
- Release certificates for each engine and module, checked for the coverage the destination registry requires
- LLP records generated at the visit, reconciled with the current LLP status list
- Times and cycles at visit induction and release, tied into the aircraft utilization record
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 engine serial number matches the engine the most recent shop-visit report was written for
- Module serial numbers in the build records agree with the released configuration and with the current status summary
- Release documentation carries the authority coverage the importing registry will require, including dual release where the destination demands it
- Cycle counts at visit induction reconcile with the utilization record, so LLP arithmetic downstream of the visit holds
- Disk sheets and LLP records raised at the visit agree with the remaining-life figures quoted in the export package
Evidence normally required
- Final shop-visit reports with build records and test-cell data for each installed engine
- Release certificates for engines and modules, FAA Form 8130-3 or EASA Form 1 as applicable
- The current engine status summary and LLP status list
- The draft export application, registry-change file, and any importing-authority questionnaire
- Aircraft utilization records covering the period since each visit
Common discrepancies
- An engine released under a single authority heading for a destination registry that expects dual release
- A module exchanged during the visit whose incoming cycle history never joined the build records
- Test-cell acceptance sheets absent from the report, leaving the performance basis of the release unsupported
- LLP figures on the status list that disagree with the disk sheets produced at the visit
What is at stake
A shop-visit defect found by the authority instead of the exporting team stalls the whole registry change. Questions about one engine hold the export certificate, storage and insurance costs run while answers are chased from a repair station that closed the visit years earlier, and a dual-release gap discovered at that stage can add weeks of certificate reissue work.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Index the visit records
Catalog every shop-visit report, build record, test-cell sheet, and release certificate delivered for each installed engine.
Read against the destination
Check release coverage, data content, and format against what the importing authority and destination registry require.
Reconcile configuration and life
Tie module serials and LLP figures from the visit paperwork to the current status summary and utilization record.
Issue the exception list
Deliver findings ranked by fix difficulty, each pointing to the exact document and the party who can supply it.
What the buyer receives
- An exception list for each engine, tied to the specific shop-visit document that fails to support the claim
- A reconciliation of module configuration between build records, releases, and the status summary
- A gap-closure plan naming which repair station, operator, or file holds each missing item
Who uses the output
- Transition leads assembling the authority-facing export or import file
- CAMO and continuing-airworthiness staff who must stand behind the engine status after transfer
- Lessor technical managers deciding what to chase before the registry date is committed
How the work fits into the transaction or program
Engine shop-visit evidence is one layer of the wider import and export package review. It sits alongside the maintenance program, logbook continuity, and modification status checks, and it feeds the same exception register the transition lead uses to sequence fixes before the application is filed.
Jurisdiction-specific considerations
Release coverage is where FAA and EASA expectations diverge most for engines. An engine destined for an EASA registry needs release documentation acceptable under EU Regulation 1321/2014, while an FAA import leans on 14 CFR Part 43 records and Order 8130.21 conventions for the 8130-3. The review checks the paper against the destination, whichever direction the transfer runs.
Regulatory limits
The review reports what the shop-visit evidence does and does not support. It does not certify an engine as airworthy, does not issue or amend any release document, and does not decide whether an importing authority will accept the package. Those determinations stay with the certificate holders and the authorities involved.
What this review does not cover
- Borescope inspections, test runs, or any physical assessment of the engines
- Negotiation with repair stations over reissued or corrected release certificates
- Commercial valuation of engine condition or maintenance reserves
Specific to this review
- Importing authorities usually sample the most recent shop visit first, so the newest report needs to be the cleanest one in the package.
- Dual-release coverage is the most common engine-related blocker in FAA-to-EASA transfers, and it cannot be fixed by the transition team alone.
- Cycle figures recorded at visit induction anchor the arithmetic for every LLP in the engine; an error there propagates through the whole remaining-life calculation.
- Module exchanges inside a shop visit are where cycle traces break, because the incoming module's history was documented by a different owner and often a different repair station.
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 engines had shop visits under a previous operator. Does that change the review?
It usually raises the stakes. Records from a prior operator's visit passed through at least one handover already, and pages drop out at each transfer. Older visits therefore get extra attention on completeness, because the party who could replace a missing page may no longer have any obligation to help.
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.