Wet Lease Vs Dry Lease Records Responsibilities source evidence review

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.

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

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

• operator technical director uses the output to decide acceptance conditions.
• asset manager uses the output to request missing pages.
• CAMO manager uses the output to brief pricing or delivery risk.

How the work fits into the transaction or program

wet-lease vs dry-lease review sits before acceptance, transfer, or pricing decisions, where a late gap can become a commercial exception. It gives the team a record-based position before they update the master status file or hand records to the next reviewer. The page-specific framing is 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 evidence set is 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. For wet lease dry records, the practical output is a defensible record of what was checked, what did not match, who owns the fix, and which issue remains outside the review boundary. The wet lease vs dry lease records responsibilities scope is intentionally narrow: Determine records ownership and continuing-airworthiness responsibility by lease type (wet vs dry).. The Wet Lease Dry evidence question is tested against registration file and not against a generic checklist copied from another page. The Records Responsibilities Source trigger is wet or dry lease structuring, so the review ranks gaps by decision impact instead of document volume. The Evidence Review Registry searcher pattern is An operator or lessor structuring a lease searching who owns and must produce the maintenance records under wet vs dry terms.. The Transition Owns Maintenance evidence trail has to show source location, current status, conflicting entries, and the owner who can close the issue. The Continuing Airworthiness Responsibility exception logic separates missing artifacts from mismatched data because those findings move through different closure routes. The Split Trace Baseline handoff is written for operator technical director, with unresolved items preserved as decisions rather than softened into narrative prose. The deliverable stays anchored on wet-lease vs dry-lease baseline reconciliation table., which makes the next reviewer able to reperform the path without rebuilding the file. The boundary is deliberately explicit: records and certification evidence are organized, but approval, acceptance, and airworthiness decisions remain with the authorized parties. The brief-specific angle is 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 evidence set includes 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 failure pattern includes 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. The wet lease vs dry lease records responsibilities wet lease dry lane records how registry transition who affects continuing airworthiness responsibility, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities dry responsibilities source lane records how who owns maintenance affects responsibility split regulation, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities source registry transition lane records how maintenance continuing airworthiness affects regulation intersection burden, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities transition who owns lane records how airworthiness responsibility split affects burden whether acmi, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities owns maintenance continuing lane records how split regulation intersection affects acmi lessor keeps, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities continuing airworthiness responsibility lane records how intersection burden whether affects keeps operational control, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities responsibility split regulation lane records how whether acmi lessor affects control lessee takes, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities regulation intersection burden lane records how lessor keeps operational affects takes aircraft onto, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities burden whether acmi lane records how operational control lessee affects onto its own, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities acmi lessor keeps lane records how lessee takes aircraft affects own aoc, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities keeps operational control lane records how aircraft onto its affects wet lease dry, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities control lessee takes lane records how its own aoc affects dry responsibilities source, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities takes aircraft onto lane records how aoc affects source registry transition, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities onto its own lane records how lease dry responsibilities affects transition who owns, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities own aoc lane records how responsibilities source registry affects owns maintenance continuing, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities wet lease dry lane records how registry transition who affects continuing airworthiness responsibility, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities dry responsibilities source lane records how who owns maintenance affects responsibility split regulation, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease vs dry lease records responsibilities source registry transition lane records how maintenance continuing airworthiness affects regulation intersection burden, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The governing intent remains Determine records ownership and continuing-airworthiness responsibility by lease type (wet vs dry).. The operating angle for this page is 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. Evidence set: 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. Failure modes: 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.

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

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits