Aircraft Redelivery: Why CAMO Planning Should Start Long Before Lease Return

Aircraft redelivery is often treated as an end-of-lease records exercise. In reality, the most successful transitions are managed as a long-range continuing-airworthiness project. The difference between an orderly handback and an expensive last-minute recovery usually comes down to when the CAMO starts converting lease language into technical actions.

Start with the lease, not the delivery checklist

A redelivery condition is not the same thing as an airworthiness requirement. The aircraft can be fully airworthy and still fail a contractual return condition. CAMO therefore needs two parallel compliance views: regulatory compliance and lease compliance. The earlier these are mapped together, the fewer surprises appear when the lessor begins its detailed review.

Each return condition should be translated into an auditable technical requirement with a source, owner, evidence and due date. Typical examples include minimum remaining life on hard-time components, LLP status, landing-gear overhaul position, engine and APU build standards, AD and modification status, structural repair documentation, OCCM requirements and maintenance-check timing.

Build the redelivery baseline early

A useful baseline is not simply a snapshot of today's aircraft status. It should project the aircraft to the contractual return date. That means forecasting utilisation, scheduled maintenance, component removals, engine and APU exposure, LLP consumption and calendar-driven limits.

• Forecast aircraft FH/FC and calendar position at return, using realistic utilisation assumptions.

• Identify every hard-time, LLP and OCCM item that could cross a contractual threshold before handback.

• Compare upcoming maintenance with the lease return-condition window before committing work packages.

• Track configuration-sensitive items such as modifications, repairs, cabin changes and life-limited assemblies against the documentary evidence required for acceptance.

Technical records are a workstream, not an archive

Records gaps become disproportionately expensive near redelivery because the physical component may be serviceable while its accumulated life, modification status or release history cannot be substantiated. CAMO and records teams should therefore perform targeted trace reviews well before the formal lessor audit.

For engines, APUs, landing gear and other high-value assemblies, the review should follow the life history rather than just the latest certificate. LLP traceability, shop-visit build records, back-to-birth evidence where contractually required, release documentation and installation/removal history need to tell one consistent story.

Control ADs, SBs, modifications and repairs as configuration data

A redelivery review frequently exposes a weakness that normal day-to-day operation can hide: compliance status and aircraft configuration are stored in different places and do not always reconcile. An AD may be closed correctly while the associated modification evidence is incomplete; a repair may be structurally approved while the records package lacks the document set expected by the next operator or lessor.

The practical solution is a configuration reconciliation: status report, embodiment evidence, release documentation and physical aircraft configuration should support each other. Any mismatch should become an action item with a defined closure route rather than a remark left for the final records review.

Use the maintenance plan to create value

Redelivery planning should influence maintenance decisions months in advance. Performing a task too early may waste remaining life; performing it too late may force additional maintenance just before return. The same applies to component changes, landing-gear planning and engine shop strategy.

A good CAMO redelivery plan evaluates the economic effect of each maintenance decision against the lease return condition. The objective is not simply to maximize remaining life. It is to deliver the required condition with the minimum unnecessary maintenance exposure while preserving regulatory compliance and operational reliability.

Create one controlled findings list

Separate spreadsheets maintained by CAMO, records, the MRO, the lessor and the transition team quickly create duplicated or contradictory actions. A single controlled findings register should define the requirement, source, responsible party, evidence needed, target date and closure status. It should distinguish regulatory findings from contractual findings and commercial observations.

The last 90 days should be verification, not discovery

By the final phase, major technical risks should already be understood. The team should be validating completed work, closing documentary gaps, confirming projected return status and preparing a coherent delivery data package. Discovering an LLP trace gap, missing repair approval or incompatible return-condition interpretation at this point can threaten both schedule and economics.

A practical CAMO rule

Treat redelivery as a project that starts while the aircraft is still comfortably inside the lease term. Translate the contract into engineering requirements, project the technical status to the return date, reconcile configuration and records, and make maintenance decisions with the return condition in view. A smooth handback is rarely the result of a heroic final audit; it is the result of disciplined preparation.

AVOLAR supports aircraft owners, operators and transition teams with continuing-airworthiness review, technical records analysis and redelivery planning focused on clear evidence, controlled risk and efficient aircraft transitions.