Managed-fleet records
Release-document reconciliation for aircraft management teams after digitization
Aircraft management teams inherit and digitize records more often than most custodians, and each pass risks scrambling the component release file. This reconciliation re-verifies, after a scanning project, a system change, or a handover from a previous manager, that every installation entry still pairs with the correct FAA Form 8130-3, EASA Form 1, or dual-release certificate. A records reviewer runs it once the new index is live, before an owner audit or the next maintenance event depends on it. The management team receives a verified pairing of installations to certificates, a misfile log, and a re-indexing correction set.
When this review is needed
- The management company took over an aircraft and the previous manager delivered records as loosely organized scans.
- A digitization project just converted years of paper certificates and the new electronic index has never been proof-checked.
- Records for several managed tails were processed in one batch and cross-filing between aircraft is suspected.
- An owner's auditor or insurer has asked for confidence that the electronic release file is complete and correctly linked.
The problem
Management transitions are hard on release paper. Certificates arrive from the previous manager sorted by year, by vendor, or by nothing at all, then a scanning batch flattens whatever structure remained. Because management companies handle several aircraft with overlapping component types, a certificate can be filed against the wrong tail and look perfectly plausible there. The manager is then custodian of a file it cannot vouch for, on behalf of an owner who assumes it can.
What gets reviewed
- Every installation entry in the aircraft's component history paired to a certificate in the rebuilt file
- Certificates screened for tail attribution where multiple managed aircraft were scanned or transferred together
- Serial-number agreement between certificate, installation entry, and the component tracking record
- Duplicate scans identified and collapsed so copies do not mask a missing original
- The handover inventory from the previous manager compared against what was actually received
- Unmatched certificates investigated as either orphans from another aircraft or evidence of undocumented changes
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 certificate in the index resolves to a legible document whose part and serial numbers match its catalog entry
- No certificate is attributed to this tail when its part or work scope belongs to a different managed aircraft's history
- Installation entries lacking any certificate are confirmed as true gaps rather than indexing failures, by searching the raw scan set
- Scanned images preserve all certificate blocks, including reverse sides where continuation entries exist
- The count and identity of certificates received at handover reconcile against the previous manager's transmittal list
Evidence normally required
- The rebuilt electronic release file and its index
- The raw scan set or paper archive it was built from
- Component removal and installation history for the aircraft
- The records transmittal or inventory from the previous manager, where one exists
- Fleet listing of other aircraft processed in the same batch
Common discrepancies
- Certificates from a sister managed aircraft filed against this tail after a combined scanning batch
- A release document indexed under the removed component rather than the installed one it accompanied
- Duplicate scans of one certificate creating a false impression of coverage across two installations
- Installation entries with no certificate anywhere in the raw scans, marking a gap that predates the handover
What is at stake
A release file the manager cannot stand behind converts every future maintenance event and ownership change into an archaeology project. Misfiled certificates surface as apparent gaps that alarm owners and their advisors, while genuine gaps hide behind plausible-looking neighbors. Owners hold the management company responsible for custody failures even when the damage predates the engagement, and the absence of a documented reconciliation makes that responsibility hard to rebut.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble both sides
Gather the rebuilt index and the raw scan or paper set, together with the component history to reconcile against.
Pair and attribute
Match each installation to its certificate and confirm tail, part, and serial attribution for every document.
Chase the unmatched
Resolve unmatched entries and orphan certificates against the raw scans and the handover inventory.
Correct and certify the file
Deliver index corrections, the gap log, and a written reconciliation record for the owner's file.
What the buyer receives
- A verified installation-to-certificate pairing for the aircraft's component history
- A misfile and gap log distinguishing indexing errors from documents genuinely absent at handover
- A correction set for the electronic index, plus a documented record of the reconciliation for the owner's file
Who uses the output
- Maintenance control staff who rely on the release file when planning and certifying component work
- The owner representative reporting custody status to the owner and its advisors
- Future transaction teams, who inherit a release file with a documented verification behind it
How the work fits into the transaction or program
For a management company, this reconciliation is the quality gate on records custody. It closes out the handover or digitization project with evidence, separates inherited gaps from anything that happened on the current manager's watch, and leaves the release file in a state where a later sale or audit starts from verified ground instead of raw scans.
Jurisdiction-specific considerations
Managed fleets commonly mix FAA-registered and EASA-registered aircraft, which multiplies filing hazards: an EASA Form 1 misfiled onto an FAA tail can sit unnoticed because both forms circulate through the same shops and suppliers. The reconciliation checks form type against each aircraft's registry history so cross-regime misfiles are caught alongside cross-tail ones.
Regulatory limits
The reconciliation validates filing and linkage, without judging the underlying maintenance. It confers no approval on any component, makes no airworthiness determination, and does not transfer or diminish the record-keeping responsibilities of the owner and operator under their applicable regulations.
What this review does not cover
- Recovering certificates that were never delivered by prior custodians, which is remediation work
- Assessing whether the certified work itself was properly performed or approved
- Records for aircraft outside the agreed tail, even when found mixed into the scan set
Specific to this review
- Cross-tail misfiling is a hazard specific to multi-aircraft custodians; a certificate for a common part number looks equally at home in either aircraft's file.
- A reconciliation performed at handover cleanly divides responsibility between managers, which matters when a gap is discovered years into the engagement.
- Duplicate scans are worse than they sound, because deduplication by filename alone can delete the only copy that captured a certificate's reverse side.
- Orphan certificates in a scan set are diagnostic: each one either belongs to another aircraft or points to a component change missing from this aircraft's history.
Sources
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union Aviation Safety Agency. EASA authorised release certificate for components, equivalent in function to FAA Form 8130-3.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
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.
Frequently asked questions
We just paid for professional scanning. Would the file really be wrong?
Scanning quality and indexing accuracy are different things. Imaging vendors capture documents faithfully, but attributing a certificate to the right tail, component, and installation requires aviation-records context the scanning workflow does not carry. Errors concentrate exactly where automation is weakest: lookalike certificates, shared part numbers across a managed fleet, and documents whose meaning depends on the removal they accompanied.
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.