Registry transition
Wet Lease Vs Dry Lease Records Responsibilities source evidence review
operators, lessors, CAMOs use this review when wet or dry lease structuring makes wet-lease vs dry-lease evidence material. The work checks registration file, maintenance status summary against export package, release documents, modification approvals and the current configuration or transfer need. Discrepancies are logged when the source page does not prove the same asset, date, requirement, or status claim. The buyer receives wet-lease vs dry-lease baseline reconciliation table, Conflicting-evidence log, Transfer readiness request list.
When this review is needed
- A Wet or dry lease structuring makes wet-lease vs dry-lease a gating item for closing, import, or continued tracking.
- Different systems show different dates, intervals, or component identities.
- The current holder needs a clean explanation for the receiving registry, CAMO, lender, or lessor.
- The package has enough paperwork to review, but it lacks a clear evidence path.
The problem
The hard part of wet-lease vs dry-lease is deciding which document controls the answer. Log entries, certificates, program extracts, and status reports may all be present, yet only some prove the specific claim now being made.
What gets reviewed
- Establish the current wet-lease vs dry-lease baseline from the supplied status file.
- Compare the baseline with source records, certificates, and program extracts.
- Look for breaks caused by custody changes, replacement parts, or revised instructions.
- Document whether each open line is missing evidence, conflicting evidence, or outside scope.
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 identity, timing, and source basis align across independent records.
- Fail when the status depends on an unreferenced note or unsupported manual entry.
- Check whether the receiving party can rely on the same document set after transfer.
- Escalate conflicts where two source records support different conclusions.
Evidence normally required
- registration file
- maintenance status summary
- export package
- release documents
- modification approvals
- maintenance program mapping
Common discrepancies
- an ACMI arrangement where the lessee assumes it owns records it never held.
- a dry lease where the lessor cannot get its own asset's status.
- continuing-airworthiness responsibility assumed by both or neither.
- authority requests answered by the party that does not hold the record.
What is at stake
A loose package can push the issue into a closing checklist, an import review, or a post-delivery dispute. Clear evidence grading gives the parties a record-based basis for acceptance, reserve, or recovery.
How the work runs
Frame Wet Lease
Confirm the exact event, affected file set, buyer role, and decision standard before any registration file is treated as sufficient.
Trace Records Responsibilities
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 Evidence Review
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Transition Owns
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
- wet-lease vs dry-lease baseline reconciliation table.
- Conflicting-evidence log.
- Transfer readiness request list.
- Reviewer notes for unresolved exceptions.
Who uses the output
How the work fits into the transaction or program
The regulation-intersection burden: whether a lease is wet (ACMI, lessor keeps operational control and maintenance) or dry (lessee takes the aircraft onto its own AOC and CAMO) determines who holds the records, who is responsible for continuing airworthiness, and who must produce evidence to which authority; the operational-control and maintenance-responsibility split in the lease, the record-system ownership (lessor's vs lessee's CAMO), the release-document and AD-status responsibility, the. The evidence set centers on the operational-control and maintenance-responsibility split in the lease, the record-system ownership (lessor's vs lessee's CAMO), the release-document and AD-status responsibility, the retention duties on each party, and the access rights when the other party needs the file. The likely weak points are an ACMI arrangement where the lessee assumes it owns records it never held, a dry lease where the lessor cannot get its own asset's status, continuing-airworthiness responsibility assumed by both or neither, and authority requests answered by the party that does not hold the record. Handoff: operator technical director, wet or dry lease structuring, Wet Lease Vs Dry Lease Records Responsibilities source.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Jurisdiction-specific considerations
The receiving registry or operator may ask for the same evidence in a different order, so the package is organized by decision, source page, and open acceptance question.
Regulatory limits
EASA and approved organizations retain responsibility for approvals, airworthiness review outcomes, and continuing airworthiness decisions. This work packages evidence and exceptions for review, and it does not grant acceptance.
What this review does not cover
- Physical inspection of the aircraft or component.
- Regulatory applications or formal authority submissions.
- Legal interpretation of purchase, lease, or financing remedies.
Specific to this review
- Conflicts between independent records need a named controlling source, not a blended answer.
- A transfer-ready package shows why the evidence applies to this asset today.
- The most useful findings identify the mismatch, the affected decision, and the next document to request.
- The scope uses the Wet Lease Dry Records question as the control point, so the review stays tied to Wet or dry lease structuring and the buyer decision behind it.
- The evidence starts with registration file and follows Responsibilities Source Evidence Review 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 operator technical director: 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 Registry Transition Owns Maintenance questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from wet-lease vs dry-lease baseline reconciliation table.; it gives the next reviewer a precise map instead of another broad request for a better file.
- The source discipline is stricter on this page than on a general audit because the claim being tested is Determine records ownership and continuing-airworthiness responsibility by lease type (wet vs dry)..
Sources
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
International Civil Aviation Organization. International standards for aircraft operation, including maintenance program and recordkeeping expectations.
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
Frequently asked questions
What makes this transitions review different from a general file audit?
The scope is tied to wet lease dry records and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block wet or dry lease structuring or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is registration file, 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 operator technical director 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.