LESSOR OPERATIONSDelivered, operated, redelivered.

Lease assets, delivery and redelivery transitions, and portfolio analytics on the same aircraft record the CAMO maintains — so the redelivery inspector finds nothing the lessor did not already see.

For the lessor's technical manager who owns the asset, and the transition lead who has to hand it back.

  • 4 key modules
  • two faces per event
  • readiness by position, not by memory
Clean white airliner inside a bright daylight hangar
Lease / Transitions
AerSynx redelivery transition with master record completeness by position and return-condition checklist
WHAT CHANGES FOR YOU
01

Blockers by position, months early

Each event carries two faces: the removed part and the installed part. A missing face on MLG LH blocks the transition today, not at the inspection.

02

The record the CAMO keeps

Delivery, operation and redelivery run on the same aircraft record the CAMO maintains. No monthly report, no reconciliation.

03

Title versus replacement, compared

Values extracted from the documents on one event are compared; discrepancies are raised as findings before the lessee's inspector finds them.

SIGNATURE VIEW

From delivery to transition closure.

Every event has two faces. A missing face is visible today, not at the inspection.

  1. 01Delivery12-Mar-2023 · TC-AXGmaster records by position
  2. 02OperationAviator Airlines · 3.5 yearsthe CAMO keeps the record
  3. 03Record completeness14 / 16 positions · 96.4%recalculated nightly
  4. 04Redelivery blockers2 · MLG LH, APUnamed by position
  5. 05Transition closure31-Mar-2027 · 194 daysreturn conditions rev. C
  • ENG 1WE-0298complete
  • ENG 2WE-0298complete
  • NLGWE-0305complete
  • MLG LHWE-0305missing: TSN/CSN at install
  • MLG RHWE-0305complete
  • APUWE-0311missing: removal record
Redelivery transition with completeness by position
ReadinessAmber · 2 blockers · 194 days to lease end
Return conditions42 items · 3 met · 1 pending · 1 gap
CONNECTS TO
KEY MODULES

Transitions

Delivery and redelivery transitions with per-position master record completeness: both faces of every event, removed part and installed part, checked position by position. A missing face on MLG LH blocks the transition today and says which position; metrics are recalculated nightly.

  • two faces per position
  • blocks early, by position
  • nightly metrics
Transitions
AerSynx screen for Transitions

Comparison

Cross-document comparison of the records attached to one workflow event: values AI extracted from each document compared against each other, scored by a severity matrix and raised as findings. The lessee's inspector should not be the first to notice that two documents disagree.

  • title vs replacement
  • severity matrix
  • raised as findings
Comparison
AerSynx screen for Comparison
ALL MODULES IN LEASE MANAGEMENT
ModulePrimary jobSignals
Assets OverviewLease asset lifecycletechnical state, not a reportlifecycle dashboard
TransitionsDelivery and redelivery readinesstwo faces per positionblocks early, by position
PortfolioYield and reserve analyticsyield analyticsreserve vs next check
ComparisonCross-document discrepancy detectiontitle vs replacementseverity matrix
Assets Overview

Lease assets and their lifecycle on one dashboard, with the technical state pulled from the CAMO workspace rather than reported by email. Owners, operators and lessors see the same aircraft through their own entitlement.

Transitions

Delivery and redelivery transitions with per-position master record completeness: both faces of every event, removed part and installed part, checked position by position. A missing face on MLG LH blocks the transition today and says which position; metrics are recalculated nightly.

Portfolio

Portfolio and yield analytics across owners and operators, with maintenance reserve accruals against the next heavy check and readiness colour per aircraft. Filtered by what each viewer is allowed to see.

Comparison

Cross-document comparison of the records attached to one workflow event: values AI extracted from each document compared against each other, scored by a severity matrix and raised as findings. The lessee's inspector should not be the first to notice that two documents disagree.

IN THE BACKGROUND

Still working when nobody is logged in.

  1. Nightly 06:30Redelivery metrics recalculated
  2. On every eventMaster record completeness derived per position
  3. On comparisonDiscrepancies raised as findings
COMMON QUESTIONS

Lease Management

The questions this workspace gets asked most often.

What does aircraft lease management software do?

It follows the asset through delivery, operation and redelivery, and reports on the portfolio behind it. Because the lease workspace reads the same aircraft record the CAMO maintains, the lessor is not asking the operator for a status that a system already knows.

How early can redelivery problems be seen?

Months before the inspection. Master record completeness is derived after every event and reported per position, so a missing document on one landing gear position is a visible blocker during normal operation rather than a discovery during the handback.

Why is a master record tracked by position?

Because a ship-set is not one part. A narrowbody landing gear set is three positions, each with a removed part and a replacement, so completeness reported as a single figure hides exactly the gap that matters. Each position answers for itself.

Does the lessor see the same record as the CAMO?

Yes — one record, read by both. The lessor does not maintain a parallel copy that drifts from the operator's, which is the usual reason a redelivery negotiation turns into a reconciliation of two spreadsheets.

IN THE FIRST SESSION

Check one redelivery before the inspection does.

Bring an aircraft with a lease end in the next twelve months. We map its events, show master record completeness by position and the return-condition gaps.