Owner handover
How to prepare an owner-handover records package
An owner-handover records package is the ordered set of maintenance and compliance records that moves with an aircraft when ownership changes. You build it by listing the record sets the buyer's review will index, reconciling each status report against its source documents, and arranging the files so a reviewer can trace any claim to its evidence. The package covers AD and SB status, life-limited part history, component release certificates, and the logbooks behind them. It is prepared by the seller's records team and read by the incoming owner's technical reviewer.
When this review is needed
- An aircraft has been sold and the records have to move to the new owner in a form the buyer's review will accept.
- A handover date is fixed and the seller wants the package built before the buyer's technical reviewer arrives.
- A previous handover was assembled in a hurry and later returned with a long discrepancy list to close.
- An owner is consolidating records from several maintenance providers into one package ahead of a sale.
The problem
The seller holds the source documents, but they sit in different systems, formats, and locations after years of operation. The buyer's reviewer indexes status reports and expects each line to resolve to evidence, while the seller's team is used to running the aircraft rather than presenting its history. A package assembled by document type instead of by what the review asks for forces the reviewer to reconstruct the trace themselves, and every line they cannot resolve becomes a question back to the seller.
What gets reviewed
- The record sets the buyer's diligence will index, listed before files are gathered
- AD and Service Bulletin status with the accomplishment evidence behind each closure
- Life-limited part history arranged so each part's status traces to release documents
- Component release certificates for parts installed across the period of ownership
- Airframe, engine, and APU logbooks or their digital equivalents
- Repair and modification records with the approval basis behind each
- A file index that maps every status claim to the document that supports it
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 status report in the package reconciles with the source documents it summarizes
- Every AD shown as complete carries accomplishment evidence with the method of compliance visible
- Life-limited part entries trace to release paperwork and a consistent time and cycle history
- Installed components have a valid release certificate appropriate to the registration
- Repairs and modifications carry the approval reference the records claim
- The file index resolves to real documents with no dead references
Evidence normally required
- Current AD and SB status reports from the maintenance-tracking system
- Life-limited part status list with part and serial numbers
- Release certificates for components installed during ownership
- Airframe, engine, and APU logbooks or digital records
- Repair and modification dossiers with their approval references
- Any prior handover binder or data-room index to reuse
Common discrepancies
- Status reports that summarize life remaining the source documents do not support
- An AD marked complete with no accomplishment record attached
- Release certificates missing for components fitted late in the ownership period
- A file index that points to documents not actually present in the package
- Time and cycle figures that disagree between logbooks and the status list
- A repair recorded without the approval data the records reference
What is at stake
A package that does not let the reviewer trace claims to evidence stalls the handover and shifts the burden of proof onto the seller after the sale price is set. Items raised late are closed under time pressure, and the documents needed to answer them are hardest to retrieve once the maintenance providers have moved on.
How the work runs
List what the review indexes
Map the record sets and status reports the buyer's diligence will work from before any files are pulled together.
Reconcile status to source
Tie each AD, SB, LLP, and component status line back to the accomplishment and release evidence behind it.
Order and index
Arrange the files to the review structure and build an index where every status claim resolves to a present document.
Record residual gaps
List any item that could not be evidenced so it is disclosed and scheduled rather than discovered by the buyer.
What the buyer receives
- An ordered handover package indexed to the buyer's likely review structure
- A reconciliation note linking each status claim to its supporting document
- A gap list for any item that could not be evidenced before handover
- A handover index the new owner can carry into its own records system
Who uses the output
- The seller's records team assembling and defending the package
- The incoming owner's technical reviewer working through diligence
- Asset and transaction stakeholders confirming the records support the price
How the work fits into the transaction or program
Package preparation runs ahead of the buyer's diligence so the seller controls the trace while the source documents and the people who created them are still reachable. It feeds the data room and becomes the records baseline the new owner inherits.
Aircraft-specific considerations
How records were kept varies with how the aircraft was operated and maintained. A type maintained on a phased program leaves a different paper trail than one on block checks, and modification-heavy aircraft carry approval dossiers that the index has to surface rather than bury. The package is arranged for the actual maintenance history rather than a generic template.
Regulatory limits
A handover package shows that the records are complete, consistent, and traceable. It does not transfer airworthiness, issue any approval, or stand in for the receiving authority's acceptance of the aircraft onto its register.
What this review does not cover
- Physical survey of the aircraft or its components
- Negotiation of the sale terms or transfer price
- Any airworthiness determination or registry transfer filing
Specific to this review
- The buyer's review indexes status reports first, so a package built around those reports is faster to clear than one organized by document type alone.
- Components fitted in the final months before handover are the most common source of missing release paperwork because they postdate the last full records sweep.
- Assembling the package before the buyer's reviewer arrives keeps closure with the seller, where the source documents and the people who created them are.
- A file index that resolves cleanly to real documents is itself a finding-avoidance tool, because dead references read to a reviewer as missing evidence.
Sources
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.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Does a complete handover package make the aircraft airworthy?
No. The package shows that the records are complete, consistent, and traceable. Airworthiness determinations rest with the operator and the authority, and a clean package does not by itself transfer or confirm airworthiness.
Should the package be organized by document type or by status report?
By the structure the buyer's review uses, which indexes status reports and traces each line to evidence. A package ordered only by document type makes the reviewer reconstruct the trace and tends to generate more questions back to the seller.
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.
Adapt the checklist to your asset, event, and jurisdiction.