Blockers by position, before the handback
Each event carries two faces: the removed part and the installed part. A workflow event with a missing face on MLG LH cannot be closed, so the gap surfaces when the event is closed, not at the inspection.
AerSynx Lease Management is aircraft lease management software for lessors that tracks lease contracts, aircraft delivery and end-of-lease redelivery, and the technical status and records of every leased aircraft.
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.
Check one redelivery before the inspection does.

Each event carries two faces: the removed part and the installed part. A workflow event with a missing face on MLG LH cannot be closed, so the gap surfaces when the event is closed, not at the inspection.
Delivery, operation and redelivery run on the same aircraft record the CAMO maintains. No monthly report, no reconciliation.
Values extracted from the documents on one event are compared; discrepancies are raised as findings before the lessee's inspector finds them.
Every event has two faces. An event with a missing face cannot be closed, and the blocker says which position.
12-Mar-2023 · TC-AXGmaster records by positionAviator Airlines · 3.5 yearsthe CAMO keeps the record14 / 16 positions · 96.4%checked at event close2 · MLG LH, APUnamed by position31-Mar-2027 · 194 daysreturn conditions rev. CWE-0298completeWE-0298completeWE-0305completeWE-0305missing: TSN/CSN at installWE-0305completeWE-0311missing: removal recordDelivery and redelivery transitions with a records checklist counted as received and missing, and return conditions whose live values are recalculated nightly while the met or not-met call stays yours. The events behind them carry position-aware master records: a workflow event with a missing face on MLG LH cannot be closed, and the blocker names the position.
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.

| Module | Primary job | Signals |
|---|---|---|
| Assets Overview | Lease asset lifecycle | technical state, not a reportlifecycle dashboard |
| Transitions | Delivery and redelivery readiness | two faces per positionevent close blocked by position |
| Portfolio | Yield and reserve analytics | yield analyticsreserve vs next check |
| Comparison | Cross-document discrepancy detection | title vs replacementseverity matrix |
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.
Delivery and redelivery transitions with a records checklist counted as received and missing, and return conditions whose live values are recalculated nightly while the met or not-met call stays yours. The events behind them carry position-aware master records: a workflow event with a missing face on MLG LH cannot be closed, and the blocker names the position.
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.
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.
The questions this workspace gets asked most often.
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.
As early as the events are recorded. Each workflow event is checked for master record completeness by position when it is closed, so a missing document on one landing gear position stops that event during normal operation rather than turning up during the handback. The transition's records checklist shows what has been received and what is still missing.
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.
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.
Bring an aircraft with a lease end in the next twelve months. We open its transition, count the records checklist as received and missing, and put each return condition's live value next to your own met or not-met call.