Redelivery preparation
Aircraft redelivery records review
An aircraft redelivery records review prepares and tests the redelivery package from the outgoing party's side before an aircraft is handed back. It serves operators returning a leased aircraft, lessors managing a transition between lessees, and management companies redelivering a client asset. The trigger is an approaching redelivery where the return conditions set a records standard the package has to meet. It assembles the AD, LLP, release, and shop evidence the conditions call for, tests it the way a receiving auditor will, and closes findings while the outgoing side still controls the records. You receive a redelivery-ready package, a self-audit findings list, and the evidence map tying each return condition to its document.
When this review is needed
- A redelivery date is set and the package has to meet the return conditions before handover.
- The outgoing side wants to find and fix records gaps before a receiving auditor does.
- An aircraft is moving directly between lessees and the package must satisfy the next operator.
- Records were maintained across several systems and now have to be assembled into one defensible package.
The problem
The records were kept to run the aircraft, not to be handed back. When redelivery arrives, the package has to satisfy someone else's auditor working from the return conditions, and gaps that never mattered in service suddenly hold up acceptance. Fixing them is easiest while the outgoing side still holds the records and the relationships to close them, which is exactly the window that closes at handover.
What gets reviewed
- The return conditions and the records standard the package must meet
- AD and SB status assembled with accomplishment evidence attached
- Life-limited part trace built back to the required origin
- Engine, APU, and landing-gear shop-visit packages
- Authorized release certificates for components changed during the lease
- An evidence map linking each return condition to its supporting document
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 return condition has a document assembled and attached to satisfy it
- AD accomplishment evidence is present and matches the stated method for this aircraft
- LLP trace reaches the required origin without an unexplained break
- Components changed during the lease carry valid release certificates
- Shop-visit packages reconcile to recorded part and serial numbers
- The package reads as a receiving auditor will read it, not only as the outgoing team knows it
Evidence normally required
Common discrepancies
- A return condition with no document yet assembled to meet it
- AD accomplishment evidence that is missing or does not match the method recorded
- An LLP trace that stops short of the required origin
- A component changed in service without a release certificate on hand
- A shop-visit package that does not reconcile to the recorded serial number
- A package that the outgoing team can follow but an outside auditor cannot
What is at stake
A package that fails the receiving audit stalls the redelivery, extends technical responsibility, and can trigger holdbacks or rework charges. Once the aircraft has gone, closing a missing release or an unsupported AD from the losing side is slow and weak, and the cost usually lands on the outgoing party anyway.
How the work runs
Translate the conditions
Turn the return conditions into the exact document set the package must contain for this aircraft.
Assemble the package
Gather AD, LLP, release, and shop evidence and attach each item to the condition it satisfies.
Self-audit
Test the assembled package as an outside auditor would and record every gap it leaves.
Close before handover
Resolve findings while the outgoing side still controls the records and confirm each closure.
What the buyer receives
- A redelivery-ready records package mapped to the return conditions
- A self-audit findings list with each gap and its closure status
- An evidence map tying every return condition to its supporting document
Who uses the output
- Continuing-airworthiness and records teams handing the aircraft back
- Asset managers coordinating the redelivery with the receiving side
- Transaction stakeholders managing holdbacks and closure terms
How the work fits into the transaction or program
The review is the outgoing-side counterpart to a receiving audit. It readies the package while the losing party still controls the records, so the handover meets the return conditions with findings already closed rather than discovered at the gate.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Aircraft-specific considerations
Shop-visit evidence for engines and landing gear often decides a redelivery, so the package work concentrates on traceability and LLP origin for the specific type, where the largest holdbacks tend to arise.
Jurisdiction-specific considerations
If the aircraft is going to a different register, the package has to anticipate the receiving authority's expectations. A release acceptable where the aircraft operated may need supplementary evidence before the receiving authority will work with it.
Regulatory limits
The review assembles and tests the records for completeness, consistency, and traceability against the return conditions. It does not perform the receiving party's acceptance, make an airworthiness determination, or guarantee the redelivery will be accepted.
What this review does not cover
- Physical preparation, inspection, or shop work on the aircraft
- Negotiation of the return conditions or any holdback amount
- Any airworthiness determination or regulatory approval
Specific to this review
- This review reads the package the way the receiving auditor will, which is the opposite vantage point from the team that maintained the aircraft in service.
- The leverage to close a redelivery gap is greatest before handover, while the outgoing side still holds the records and the shop relationships.
- Shop-visit traceability for engines and landing gear is treated as a priority because it is where the largest redelivery holdbacks typically originate.
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.
U.S. Government (eCFR). Export airworthiness approval requirements and special requirements of an importing authority.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
How is this different from a lease-return audit run by the receiving side?
A receiving audit checks the package on the way in. This is the outgoing side preparing and self-testing that package on the way out, so gaps are closed before handover rather than raised against it.
Do you negotiate the return conditions?
No. The conditions are taken as given. The review assembles and tests the records evidence needed to meet them and closes findings before the aircraft is handed back.
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.
Walk through your situation with an engineer who has done this work.