Redelivery handover
AD status review at redelivery for aircraft management teams
At redelivery, the AD status list is the first document the receiving operator's reviewers take apart. This review pressure-tests that list before the handover: applicability calls, accomplishment evidence, AMOC references, and recurring-item projections all get checked against source records. Aircraft management teams run it while the aircraft is still under their control and corrections are still cheap. It produces a defensible AD status, a findings log with closure actions, and the evidence set to hand across at acceptance.
When this review is needed
- A management term is ending and the aircraft returns to the owner or moves to a receiving operator with its own reviewers.
- The AD status has been maintained in the manager's system for years and never externally tested.
- Redelivery conditions require demonstrable compliance, with evidence, at the handover date.
- Earlier operators contributed entries to the status that the current team adopted without source documents.
The problem
On the outgoing side of a handover, the manager defends a status list built partly from its own records and partly from what it inherited when the aircraft arrived. The receiving side reads that list adversarially, entry by entry, and any item the manager cannot evidence becomes a delivery-table dispute with the aircraft's departure date attached. Preparing the defense after the receiving team has started asking questions means every gap is discovered publicly.
What gets reviewed
- The full AD status list reviewed as a receiving inspector would read it
- Accomplishment evidence located and attached for each complied-with entry
- Applicability and not-applicable justifications restated with their supporting configuration data
- AMOC approvals, terminating actions, and repetitive-inspection statuses documented
- Entries inherited from prior operators traced to source or flagged for recovery
- Next-due projections for recurring items confirmed through the handover date
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 entry can be handed to a skeptical reviewer with its evidence in the same folder
- Recurring items show margin beyond the redelivery date, or the shortfall is declared and planned
- Inherited entries either trace to source documents or appear on the recovery list with a named holder
- Method-of-compliance citations match the accomplishment records they claim to describe
- The list is current against the latest directive issuances for airframe, engines, and appliances
Evidence normally required
- The AD status list as maintained through the management term
- Accomplishment records, logbook entries, and release documents across the term
- The induction file from when the manager received the aircraft, including inherited evidence
- Redelivery conditions from the management agreement or lease
- Configuration and modification records supporting applicability positions
Common discrepancies
- Entries the manager's system carried forward from induction that were never evidenced then either
- Recurring inspections that fall due within days of the planned handover
- Accomplishment evidence that exists but is filed under work-order numbers no index connects to the AD
- Applicability justifications written for internal use that a receiving reviewer would reject as bare assertion
What is at stake
Disputed AD items at redelivery hold the handover open while evidence is chased, and each held day has a cost the owner sees. Items that cannot be evidenced at all get resolved commercially, through holdbacks or concessions, or physically, through re-accomplishment the outgoing side pays for. A status tested privately beforehand converts most of these into items closed quietly on the manager's schedule.
How the work runs
Adopt the adversarial read
Review the status list to the standard the receiving side will apply, not the standard that maintained it.
Assemble evidence per entry
Attach accomplishment records, approvals, and justifications so each entry stands alone.
Close the weak entries
Recover inherited documents, re-index misfiled evidence, and schedule any physical work while access is easy.
Package for handover
Deliver the organized evidence set and a status the delivery team can defend line by line.
What the buyer receives
- A redelivery-ready AD status with evidence assembled per entry
- A findings log of weak entries, each with a closure action and owner
- A handover evidence set organized the way receiving reviewers work
Who uses the output
- Owner representatives managing the handover and its commercial exposure
- Maintenance-control staff closing findings while the aircraft is still accessible
- The receiving operator's reviewers, who get an evidence set instead of a spreadsheet
How the work fits into the transaction or program
This review runs weeks ahead of the redelivery event, far enough out that findings can still be fixed with records requests or scheduled maintenance rather than delivery-table concessions. Its output plugs into the wider redelivery records package, alongside LLP, program, and repair documentation prepared to the same standard.
Start with a single asset
Reconcile maintenance tracking against source records.
Jurisdiction-specific considerations
If the receiving operator sits under a different authority, the handover crosses directive regimes: an aircraft managed under FAA oversight moving to EASA registration will be reviewed against EASA directives its status list may never have tracked. The review runs the list against the receiving side's index when the destination is known, and against both major indexes when it is not.
Regulatory limits
The review prepares and tests documentation. It does not accomplish directives, approve compliance methods, negotiate redelivery conditions, or determine the aircraft's airworthiness at handover; those determinations belong to the operators and authorities involved.
What this review does not cover
- Performing maintenance to close open directives
- Commercial negotiation of disputed redelivery items
- Records domains other than AD compliance, which are covered by parallel redelivery workstreams
Specific to this review
- Redelivery AD disputes concentrate in entries inherited at induction, because that is where the current team's institutional knowledge is thinnest.
- Recurring items due shortly after handover are a classic friction point: compliant on the date, unacceptable to a receiving operator that inherits an immediate grounding item.
- Evidence usually exists somewhere in the term's work orders; the failure is indexing, and rebuilding the index is faster than re-accomplishing the work.
- The outgoing side chooses when the review happens, and that timing choice, more than the state of the records, decides whether findings close quietly or publicly.
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
How far before redelivery should this start?
Three to six months, for a typical management handover. Records recovery from prior operators sets the pace, and any finding that turns into physical maintenance needs to land in a scheduled downtime rather than force one.
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.