Skip to content

ACMI approval package

Records package review before wet-lease or ACMI approval

airlines, operators, brokers use this review when Wet-lease / ACMI placement approval makes wet-lease records readiness records a decision item. The work checks certificate currency, registration, insurance, AD status, maintenance status summaries, AOC and ops-spec scope, and maintenance support arrangements against source evidence and the current status file. A discrepancy exists when the approval package is current in one record set but inconsistent or incomplete for the authority or lessee review. The buyer receives an approval package index, status exception register, and expiring-document action list for acceptance, pricing, audit, or remediation decisions.

When this review is needed

  • A wet-lease or ACMI placement needs authority or lessee approval.
  • Certificate dates fall inside the proposed operating period.
  • Status reports were generated from a system with unresolved audit findings.
  • Two regulatory document conventions must be presented in one package.

The problem

Wet-lease readiness is certificate heavy and time sensitive. The aircraft may remain on the supplying operator certificate, but the receiving side still needs a coherent package that explains current status, operating authority, and maintenance support.

What gets reviewed

  • Check certificate, registration, insurance, and airworthiness review dates against the placement period.
  • Reconcile AD and maintenance status summaries to the latest controlled records.
  • Confirm operating scope records cover the aircraft and intended placement arrangement.
  • Review maintenance support arrangements for the operating period.
  • Package records using labels the receiving reviewer can follow across systems.

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 certificates are current through the relevant approval window or renewal actions are diarized.
  • Fail when status summaries conflict with the latest audit finding list.
  • Check that maintenance support responsibilities are documented for the wet-lease period.
  • Reject packages that mix document versions without a controlled index.

Evidence normally required

  • CofA or ARC record set
  • Registration and insurance certificates
  • AD and maintenance status exports
  • AOC or operations scope records
  • Maintenance support agreement records

Common discrepancies

  • ARC expiry falls inside the proposed placement period.
  • AD status summary conflicts with a recent internal audit exception.
  • Insurance certificate version in the package is superseded.
  • Maintenance support arrangement absent for a location in the planned operation.

What is at stake

A missing or inconsistent certificate can delay approval past the placement window. Expiring ARC, insurance, or status documents can also create avoidable renegotiation when capacity is already committed.

How the work runs

01

Frame Wet Lease

Confirm the exact event, affected file set, buyer role, and decision standard before any certificate and registration set is treated as sufficient.

02

Trace Readiness Audit

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.

03

Sort Review Acmi

Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.

04

Package Placement Approved

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

  • For this review, wet-lease records package index
  • Certificate expiry action list
  • Status summary exception register
  • Authority and lessee request pack

Who uses the output

  • ACMI program manager uses the output to set acceptance conditions.
  • Quality manager uses the output to request missing evidence.
  • Fleet manager uses the output to price or schedule remediation.

How the work fits into the transaction or program

wet-lease records readiness review sits before the next commercial, audit, approval, or maintenance decision so the team can act on records evidence before the deadline controls the discussion. It converts loose records concerns into named exceptions, owners, and closure evidence. The page-specific framing is A wet-lease approval hinges on a records package the lessee's authority must accept while the aircraft stays on the lessor operator's AOC: the decision is whether certificates, status, and program evidence are current, consistent, and presentable within the approval timeline, which is usually weeks. Evidence reviewed: certificate set currency (CofA, ARC or equivalent, registration, insurance certificates), AD status snapshot and maintenance status summary in the format the receiving authority expects, AOC and. For wet lease records readiness, 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 records readiness audit scope is intentionally narrow: Assemble and verify the records package that supports a wet-lease or ACMI approval before the placement window closes.. The Wet Lease Records evidence question is tested against certificate and registration set and not against a generic checklist copied from another page. The Readiness Audit Package trigger is wet-lease / acmi placement approval, so the review ranks gaps by decision impact instead of document volume. The Review Acmi Approval searcher pattern is An ACMI operator or lessee airline arranging a wet-lease searches for what records the approving authority requires and how fast a compliant package can be assembled.. The Placement Approved Speed evidence trail has to show source location, current status, conflicting entries, and the owner who can close the issue. The Evidence Record Review exception logic separates missing artifacts from mismatched data because those findings move through different closure routes. The Closure Trace Baseline handoff is written for acmi program manager, with unresolved items preserved as decisions rather than softened into narrative prose. The deliverable stays anchored on for this review, wet-lease records package index, 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 A wet-lease approval hinges on a records package the lessee's authority must accept while the aircraft stays on the lessor operator's AOC: the decision is whether certificates, status, and program evidence are current, consistent, and presentable within the approval timeline, which is usually weeks. Evidence reviewed: certificate set currency (CofA, ARC or equivalent, registration, insurance certificates), AD status snapshot and maintenance status summary in the format the receiving authority expects, AOC and ops-specs scope covering the placement, and maintenance support arrangements documented for the operating period. The failure pattern includes an ARC expiring mid-placement that nobody diarized, status summaries generated from tracking that contradict the last audit's findings, and approval delays because the package mixed document conventions from two regulatory systems. The wet lease records readiness audit wet lease readiness lane records how acmi approval placement affects hinges lessee authority, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit readiness audit package lane records how placement approved speed affects authority must accept, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit package acmi approval lane records how speed hinges lessee affects accept while aircraft, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit approval placement approved lane records how lessee authority must affects aircraft stays lessor, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit approved speed hinges lane records how must accept while affects lessor operator aoc, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit hinges lessee authority lane records how while aircraft stays affects aoc decision whether, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit authority must accept lane records how stays lessor operator affects whether certificates status, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit accept while aircraft lane records how operator aoc decision affects status program are, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit aircraft stays lessor lane records how decision whether certificates affects are current consistent, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit lessor operator aoc lane records how certificates status program affects consistent presentable, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit aoc decision whether lane records how program are current affects wet lease readiness, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit whether certificates status lane records how current consistent presentable affects readiness audit package, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit status program are lane records how presentable affects package acmi approval, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit are current consistent lane records how lease readiness audit affects approval placement approved, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit consistent presentable lane records how audit package acmi affects approved speed hinges, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit wet lease readiness lane records how acmi approval placement affects hinges lessee authority, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit readiness audit package lane records how placement approved speed affects authority must accept, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The wet lease records readiness audit package acmi approval lane records how speed hinges lessee affects accept while aircraft, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The governing intent remains Assemble and verify the records package that supports a wet-lease or ACMI approval before the placement window closes.. The operating angle for this page is A wet-lease approval hinges on a records package the lessee's authority must accept while the aircraft stays on the lessor operator's AOC: the decision is whether certificates, status, and program evidence are current, consistent, and presentable within the approval timeline, which is usually weeks. Evidence reviewed: certificate set currency (CofA, ARC or equivalent, registration, insurance certificates), AD status snapshot and maintenance status summary in the format the receiving authority expects, AOC and ops-specs scope covering the placement, and maintenance support arrangements documented for the operating period. Failure modes: an ARC expiring mid-placement that nobody diarized, status summaries generated from tracking that contradict the last audit's findings, and approval delays because the package mixed document conventions from two regulatory.

Start with a single asset

Prove the review on a single tail, then scale across the fleet.

Jurisdiction-specific considerations

The package is organized so FAA and EASA and ICAO records references are visible without claiming automatic acceptance across authorities. Where a receiving reviewer needs a different format, the same source record is mapped to that review question.

Regulatory limits

This wet-lease records readiness review is a records completeness and traceability assessment. It does not issue approvals, make airworthiness determinations, approve maintenance, or guarantee acceptance by FAA and EASA and ICAO; those decisions remain with the operator, authorized persons, and the relevant authority.

What this review does not cover

  • Physical inspection of the aircraft, engine, component, or part condition.
  • Regulatory applications, authority submissions, or approval issuance.
  • Legal interpretation of lease, loan, purchase, insurance, or support agreement remedies.

Specific to this review

  • For this review, wet-lease records packages fail on currency and presentation as often as on missing technical records.
  • The same aircraft status may need to be explained in the supplying operator format and the receiving reviewer format.
  • Expiring documents inside the operating period should be treated as approval risks before submission.
  • The scope uses the Wet Lease Records Readiness question as the control point, so the review stays tied to Wet-lease / ACMI placement approval and the buyer decision behind it.
  • The evidence starts with Certificate and registration set and follows Audit Package Review Acmi 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 ACMI program 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 Approval Placement Approved Speed questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
  • The handoff value comes from For this review, wet-lease records package index; 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 Assemble and verify the records package that supports a wet-lease or ACMI approval before the placement window closes..

Sources

Frequently asked questions

What makes this workflows review different from a general file audit?

The scope is tied to wet lease records readiness 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-lease / acmi placement approval or can be closed later without changing the decision.

What evidence has to be available before this work starts?

The starting point is certificate and registration set, 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 acmi program 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.