Lessor AD gaps
Lessor-side cure plan for unsupported AD closures
This page is for lessors, Asset managers, Aircraft records teams dealing with Redelivery exception log with unsupported AD closures. The review starts with the disputed or high-risk status claim, then checks it against redelivery AD exception log, lease return conditions, current AD status file, source records recovered from lessee. Findings identify absent source pages, wrong-asset evidence, timing conflicts, and limits that should be disclosed rather than hidden. The buyer receives lessee AD cure matrix, prior-custodian evidence chase list, remarketing AD risk summary so closure work can be assigned and tracked.
When this review is needed
- A counterparty has challenged the records position or asked for deeper evidence.
- The internal team can see a gap but has not defined the cure route.
- Several record families point to the same unresolved source document or status conflict.
- Commercial or program timing requires a defensible position before every document is recovered.
The problem
The difficult part is deciding what the records actually prove before the deadline or transaction pressure takes over. Current lessee can cure some AD lines but older lines trace to a prior operator. The lessor loses leverage by accepting the aircraft before evidence requests are closed.
What gets reviewed
- Classify each unsupported AD closure by lessee cure obligation, prior-custodian gap, or lessor residual item.
- Use lease leverage while the aircraft is still in redelivery to obtain evidence or reservation language.
- Chase older evidence from prior operators, MROs, and archives after handback where needed.
- Update remarketing readiness based on which AD gaps remain open.
- Preserve accepted exceptions for the next delivery file.
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
- Pass when each gap has a responsible party and evidence path before return acceptance.
- Fail when the aircraft is accepted with an open log and no reservation position.
- Pass when prior-operator gaps are separated from current-lessee obligations.
- Fail when remarketing proceeds on unsupported AD status.
Evidence normally required
Common discrepancies
- Current lessee can cure some AD lines but older lines trace to a prior operator.
- The lessor loses leverage by accepting the aircraft before evidence requests are closed.
- Recovered records support compliance but are not reflected in the remarketing status file.
- A redelivery exception becomes the next buyer question because no closure narrative was retained.
What is at stake
A weak response can turn a curable records defect into a holdback, delivery condition, audit repeat, or grounded planning assumption. The practical risk is carrying forward an unsupported position because nobody separated evidence gaps from administrative cleanup.
How the work runs
Frame Lessor Evidence
Confirm the exact event, affected file set, buyer role, and decision standard before any redelivery exception log is treated as sufficient.
Trace Remediation Side
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Plan Unsupported
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Gaps Found
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
Who uses the output
- Lessor technical manager uses the findings to decide which gaps block the next milestone.
- Asset manager uses the evidence map to request, correct, or reserve records items.
- Technical records manager uses the summary to brief stakeholders without reopening the full file.
How the work fits into the transaction or program
When redelivery review finds AD closures without evidence, the lessor inherits the problem the moment the aircraft comes back; triage which gaps the departing lessee must cure under the lease's redelivery conditions while leverage exists, and which the lessor will have to remediate itself: chasing prior-operator records, MRO duplicates, and OEM confirmations after handback; the exception log against redelivery conditions, lease records clauses, source documents recovered from prior. The evidence set centers on the exception log against redelivery conditions, lease records clauses, source documents recovered from prior custodians. The likely weak points are accepting an aircraft with an open exception log and losing contractual leverage, gaps from two operators back that the current lessee never held evidence for, and remarketing timelines forcing the next delivery before closures are substantiated. Handoff: lessor technical manager, redelivery exception log with unsupported AD closures, Lessor-side cure plan for unsupported AD closures.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Jurisdiction-specific considerations
FAA and EASA references are used as evidence criteria for records completeness and traceability. The review does not treat one authority's records as automatic acceptance by another authority or by a transaction counterparty.
Regulatory limits
The output does not replace regulator review, authorized release, engineering approval, conformity finding, or the buyer's own acceptance process. It documents records support and records limits for the responsible parties to use.
What this review does not cover
- lease dispute resolution
- AD maintenance accomplishment
- final airworthiness acceptance
Specific to this review
- The lessor-side problem is timing: leverage exists before acceptance and fades after handback.
- Not every AD gap is realistically curable by the departing lessee.
- Remarketing readiness depends on the status file the next buyer will inspect, not solely the lessor internal register.
- Reservation language should be evidence-led so it survives the next transaction.
- The scope uses the Lessor Evidence Gap Remediation question as the control point, so the review stays tied to Redelivery exception log with unsupported AD closures and the buyer decision behind it.
- The evidence starts with redelivery exception log and follows Side Cure Plan Unsupported references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for Lessor technical manager: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Closures Gaps Found Redelivery questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from lessee AD cure matrix; it gives the next reviewer a precise map instead of another broad request for a better file.
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
U.S. Government (eCFR). Requirement to transfer maintenance records with an aircraft on sale or transfer of ownership.
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
What makes this problems review different from a general file audit?
The scope is tied to lessor evidence gap remediation and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block redelivery exception log with unsupported ad closures or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is redelivery exception log, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives lessor technical manager a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
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.