Acquired records, verified
Engine shop-visit record reconciliation for acquisition teams after a records migration
Acquisition teams inherit engine shop-visit records from sellers, servicers, and prior custodians, then consolidate them into their own repository. This reconciliation verifies, after that migration or re-indexing, that each shop-visit package in the new repository is complete, correctly attributed to its engine and visit, and faithful to the source documents received. A records specialist runs it before the portfolio's first audit, valuation refresh, or asset handover leans on the consolidated archive. The team receives a package-by-package integrity assessment, an attribution and completeness log, and a repair-index correction set.
When this review is needed
- A closed acquisition delivered engine records from several custodians and they were loaded into the acquirer's repository in bulk.
- Portfolio engines have multi-visit histories and the migration flattened folder structures that marked visit boundaries.
- An asset-management platform re-indexed the archive and shop-visit documents were classified by automated rules.
- A lender's audit, an insurance review, or the first post-closing disposal is approaching and will sample the consolidated records.
The problem
Every custodian organizes shop-visit records differently, and consolidation grinds those structures into one indexing scheme built by people who never saw the originals in context. Visit boundaries blur on engines with several overhauls, pages from different visits interleave under one label, and a folder named for a package can contain placeholders, duplicates, or another engine's scans. The repository looks orderly at exactly the moment its contents stop being trustworthy.
What gets reviewed
- Each indexed shop-visit package opened and verified against its manifest: every listed document present, legible, and the right one
- Engine and visit attribution confirmed, with ESN checks on test-cell data, build records, and release certificates
- Visit boundaries reconstructed on multi-visit engines where the migration flattened the original structure
- Duplicate folders and files resolved to a single authoritative copy per document
- Cross-custodian coverage assessed: whether each engine's known visit history is represented by a package at all
- The repository's index corrected so search returns the true contents rather than the labels
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
- ESNs inside sampled documents match the engine the package is filed under, checked on test-cell sheets, build records, and releases
- Dates and workscopes within one package belong to a single visit rather than an interleaved pair
- Placeholder files, blank scans, and cover sheets are not counted as the documents their filenames claim
- Where duplicate folders exist for one visit, their contents are compared rather than assumed identical
- The set of packages per engine accounts for every visit named in diligence materials and utilization history
Evidence normally required
- The consolidated repository and its index
- Source deliveries as received from each custodian, ideally unaltered
- Engine list with known visit histories from diligence
- Migration and classification rules used in the consolidation
- Diligence reports referencing specific shop-visit documents
Common discrepancies
- Test-cell data filed under one ESN while its header shows another engine from the same seller's fleet
- Interleaved pages from two visits to the same engine presented as a single package
- Two folders for one visit whose contents differ, each missing pages the other holds
- An index entry counting a transmittal cover sheet as the module build record it announced
What is at stake
An acquirer that discovers archive defects during a disposal has recreated the seller's problem at its own expense: value assumptions built on shop-visit histories come under challenge just when leverage is lowest. Lender audits that find attribution errors expand their sampling, and reconstructing which document belonged to which visit gets harder each year as the people who packed the original boxes disappear from reach.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Map holdings to history
List each engine's known visits from diligence and match a package in the repository to every one.
Open and attribute
Verify sampled contents against manifests, checking ESN, dates, and visit coherence inside each package.
Resolve conflicts
Arbitrate duplicates, split interleaved visits, and re-home documents filed under the wrong engine.
Correct and baseline
Apply index corrections and issue the integrity assessment as the portfolio's records baseline.
What the buyer receives
- A package-by-package integrity assessment across the portfolio's engines
- An attribution and completeness log identifying misfiled, mixed, duplicate, and absent material
- An index correction set and a statement of the reconciliation method for lender and auditor use
Who uses the output
- The investment team relying on shop-visit histories for maintenance-reserve and valuation models
- Technical due-diligence staff answering lender and insurer sampling
- Asset managers preparing individual engines for lease placement or disposal
How the work fits into the transaction or program
This reconciliation converts a pile of inherited deliveries into an archive the acquirer can cite. It runs after consolidation and before reliance, and its integrity assessment feeds valuation models, audit responses, and the records baseline each engine carries into its next transaction. Gaps it identifies route into remediation while seller cooperation obligations still have force.
Jurisdiction-specific considerations
Portfolios assembled across sellers mix FAA-oriented and EASA-oriented documentation conventions, and the same visit can be evidenced by an 8130-3 in one custodian's copy and a dual release in another's. The reconciliation records which regime's documents evidence each visit, since the answer determines what a future counterparty on either registry will accept without supplement.
Regulatory limits
The work verifies documentary integrity and attribution within the acquirer's repository. It does not certify any overhaul, assign or confirm airworthiness status, or convert incomplete visit evidence into acceptable evidence; it establishes what the acquirer actually holds.
What this review does not cover
- Back-to-birth LLP trace construction, which builds on this work but is scoped separately
- Chasing documents the custodians never delivered, which is a remediation engagement
- Technical evaluation of workscopes, findings, or test results within the packages
Specific to this review
- A shop-visit package is only as reliable as its weakest module record, and consolidation defects concentrate in module-level documents because they look alike across visits.
- ESN errors cluster within a seller's fleet: engines that lived together in one custodian's archive are the ones whose documents swap during scanning and loading.
- Post-closing seller cooperation clauses expire, so the window for resolving attribution questions against the source custodian is measured in months, never years.
- Automated document classification labels by layout and title, which is exactly why a cover sheet gets indexed as the build record it merely announced.
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
Diligence already reviewed these records before we closed. Why review them again?
Diligence read the records in the seller's structure to inform price; this reconciliation proves the records survived the move into yours. The consolidation itself is a new failure opportunity that diligence never examined, and defects introduced by loading and re-indexing are invisible to any pre-closing review. The two exercises answer different questions on either side of the same closing.
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.