Signing a maintenance agreement per flight hour is like a purchasing decision: comparing the hourly rate, comparing the shop visit budgets, giving a notice period. It’s not. The number that decides the exit is the engine’s condition on the day the contract ends, expressed in cycles, margin, and records — and that number almost never appears on the comparison sheet anyone signs.
What the contract bought, and what it never owned
An engine support agreement — an agreement per flight hour, an arrangement per flight flight hour rate, it doesn’t matter how the program is marketed — is a service contract with an attached payment mechanism. The operator pays an accrual for each hour or cycle flown, and in return, the provider assumes the defined maintenance events, generally shop visits, the replacement of life-limited parts to a certain extent, the incorporation of service bulletins, and a certain level of spare engine support.
What it does not do is transfer ownership of the asset or the state of the asset. The engines remain the property of the operator, or the lessor, throughout the entire time. The accruals have bought a smoothing of cash flows and a transfer of technical risk; they have not bought a right to a particular state on the day the arrangement ends. Whether they have depends on what the exit clause says, and the honest answer in many contracts is that it says very little, because it was negotiated by people focused on the entry rate and the escalation formula.
This asymmetry is the whole point. Within the contract, the engine’s condition is the provider’s problem. Outside the contract, the engine’s condition is the operator’s balance sheet — and the moment of transition is when a value that no one has put on a slide appears or disappears.
Three clocks decide the number
The value of an engine at a given moment is not a single number. It is the answer to three distinct questions, and a weak answer to one of them can dominate the other two.

Remaining cycles of life-limited parts. The disks, drums, shafts, and spools have fixed cyclic limits in the airworthiness limitations of the type’s instructions for continued airworthiness. They are not repairable, not extendable by the operator, and not negotiable: at the limit, they are scrapped. In a large, mature turbofan, the replacement of a full set of life-limited parts is one of the largest individual lines in a heavy shop visit, and a buyer or lessor evaluating an engine will value the remaining cycles as a direct liability. An engine near the end of its cyclic life is not a cheap engine; it is an engine with a costly event attached.
Performance margin. The exhaust gas temperature margin and its equivalents determine how long the engine can remain on the wing before a performance restoration is imposed. The margin is consumed by hours, cycles, derating policy, environment, and the depth of the last shop visit. Two engines with identical cycle counts and very different margins are very different assets, and the difference is invisible in a table that records only hours and cycles.
Records. This is the clock no one adjusts and everyone trips over. Each life-limited part requires continuous traceability from birth — the cycles accumulated in this individual serial number, attested by an unbroken chain of release documents. Where the chain is broken, the buyer, lessor, or prudent airworthiness review authority assumes the worst-case scenario, which in practice means treating the part as if it has no remaining usable life. A perfectly serviceable disk with a missing certificate is worth what a scrapped disk is worth. Continuing airworthiness rules require these records to be kept; the exit from a support contract is the moment when the quality of this record-keeping stops being an audit finding and starts being a cash number.
The engine’s value depends on three things: how much life is left in its key parts, how well it’s performing, and whether all its paperwork is in order. If any of these is bad, it can make the engine much less valuable, even if the other two are fine.
A Boeing 737-800 with CFM56-7B engines has life-limited parts with a limit of 30,000 cycles. If one engine has 25,000 cycles left and the other has 5,000, the second engine will need a costly overhaul much sooner, making it far less valuable at contract exit.
| Element | Adds value at exit | Destroys value at exit |
|---|---|---|
| Life-limited parts | Long remaining cycles, a set replaced together in the last visit | Residual life, mismatched remaining cycles in the set forcing an early visit for a part |
| Performance margin | Recent restoration, sufficient margin for a full additional interval | Exhausted margin, a removal already planned in the months following the exit |
| Records | Full traceability from birth with valid release documents for each serial item | Any gap in the chain, regardless of the physical condition of the part |
| Provenance of the parts | Configuration consistent with what the lease or next buyer accepts | Parts or repairs not from the manufacturer that the lease or subsequent contract do not authorize |
| Modification status | Service bulletins incorporated, no ongoing campaign modifications | Deferred incorporations that pass to the operator on the day the contract ends |
Two documents that have never been reconciled
Most operators of leased fleets are simultaneously part of two contracts that talk about the same engines and do not talk to each other. The aircraft lease sets the redelivery condition: minimum remaining cycles of life-limited parts, minimum time since the last performance restoration, borescope criteria, an acceptable configuration, and a cash formula for everything that is below. The engine support agreement sets what the provider will do and when, and what the position is at the end.
Neither of the drafting teams has read the other document. The result is a gap that is invisible while the support contract is in force — the provider keeps the engines in a serviceable state, and no one tests whether this state also satisfies the lease — and becomes a bill as soon as the arrangement ends before the aircraft is redelivered. The operator then owns the difference between the state left by the support contract and the state required by the lease, in cash, on a date they did not choose.
The trap. Treating the exit clause of the support contract and the redelivery condition of the lease as two separate negotiations managed by two separate teams. They describe the same physical engine on overlapping dates. Put the two documents on the same table, with the same fleet cycle forecast, before anyone drafts a notice letter.
The cash impact that is never modeled
On leased aircraft, lessors generally bill maintenance reserves or additional rent against future engine events. When the operator has a credible manufacturer support agreement, many lessors accept it in lieu of these reserves, or substantially reduce them. This concession is written against the existence of the contract.
Terminate the contract and the concession ends. The reserves resume under the terms the lease provides, and some leases add a surcharge for the period during which the exemption applied. It is a sharp change in monthly cash flows that has nothing to do with the maintenance cost per hour and everything to do with a third party’s security position. It is regularly absent from the comparison model, because the model was built by an engineering team comparing shop visit costs and not by a treasury team examining the lease covenants.
The accounting follows the same path. A return condition obligation is a provision, and the assumptions that support it — expected engine state at redelivery, expected compensation to be paid — change as soon as the support arrangement changes. Discovering this at the end of the year, rather than at the decision, is an uncomfortable conversation with an auditor.
Serial numbers, pools, and the substitution problem
Under many support arrangements, the provider manages a pool of engines. An engine removed from an aircraft can be replaced by a different serial number from this pool, and in a decade, a fleet can end up with almost none of the engines it started with. Within the contract, this is completely rational: it minimizes the aircraft’s ground time and allows the provider to optimize its own shop workflow.
At exit, this becomes a three-sided problem. First, the serial numbers on the wing may not be those the aircraft lease contemplates, and some leases restrict substitution or require the lessor’s consent. Second, the substituted engines carry their own life-limited part state and their own records, which may be materially worse than those the operator originally financed. Third, the accrual history was paid against the hours flown by the fleet, and not against the state of any particular serial number, so there is no natural link between what was paid and what is on the wing on the last day.
The defense is unglamorous and is a discipline of record-keeping: maintaining a condition log at the serial number level for the entire fleet, updated at each removal and installation, independent of the provider’s own system. An operator who cannot indicate, from their own data, the remaining cycles and margin on each installed engine has no negotiating position, because the only person in the room who knows the asset’s value is the other party.
What follows you at exit, and what stays behind
Exiting a manufacturer program is not just about exiting a payment mechanism. Several things that seemed to be part of the aircraft turn out to have been part of the support contract.
| Element | Within the contract | After exit |
|---|---|---|
| Shop capacity | Induction slot managed by the provider | Negotiated with an independent shop, subject to that shop’s queue and delivery times |
| Approval scope | Provider’s own network | The chosen organization must possess an approval with the correct qualification for the engine type, and access to the applicable maintenance data |
| Test capacity | Provided in the network | Requires a test cell correlated for the type — a rare resource, and a real constraint in shop choice |
| Spare engine coverage | Lease or pool engine provided under the agreement | Own spare engine, a short-term lease at market rate, or accepted exposure to aircraft on ground |
| Service bulletin incorporation | Frequently absorbed by the provider | Billed item by item, on the operator’s account |
| Part price | Program price, escalated by formula | Catalog price, or what the operator’s own volume supports |
Each of these elements is manageable. What is not is discovering them in sequence in the months following the signing, which is the usual scheme when the exit was decided solely on the hourly rate.
Sequencing the exit based on the shop visit, and not the notice period date
The natural instinct is to fit the decision to the contract’s notice period window, because it is the date on the calendar. It is the wrong reference point. The right reference point is the next shop visit on each engine, because it is the event where value is created or destroyed and where the difference between providers is truly expressed.
Exiting immediately before a heavy visit means the operator finances a full scope of work that has accumulated over years, with a recovery of the accrual balance that the contract allows — often little or nothing. Exiting immediately after a visit means leaving with fresh engines and a long runway, having paid for the visit thanks to the accruals. The gap between these two positions, per engine, is the largest number in the entire exercise, and it depends entirely on timing.
The right reflex. Building the decision on a serial number forecast of the next removal for each installed and spare engine, then overlaying the contract notice period window, the lease redelivery dates, and the aircraft retirement or return plan. The exit date must be chosen in this framework. If the notice period window imposes a date that falls badly, the cost of an additional contract period is often lower than the cost of poor timing.
The numbers to have before the first meeting
A negotiation with a provider or lessor is decided by whoever has better data on the asset. The list is short and the work is entirely internal.
- Remaining cycles of life-limited parts for each serial part, per installed and spare engine, with the limiting part identified in each case.
- Current performance margin and the expected removal date built from this, with the stated assumptions.
- A record completeness score per engine: which serial parts lack continuous traceability, and what the cost would be to fill each gap or replace the part.
- The accrual balance retained by the provider, the contractual treatment of this balance in case of termination, and any termination fee.
- The redelivery condition of each lease in the fleet, translated into the same units of cycles and margin as the engineering forecast.
- The reserve position that resumes at exit, and any surcharge if applicable.
- Service bulletins and ongoing campaign modifications, with an incorporation cost and a compliance date.
Each of these elements already exists somewhere in the organization. The exercise is not a search, it is an assembly, and the reason this rarely happens before the decision is that no department owns all seven lines.
When staying is the cheapest answer
None of this argues that support contracts should not be abandoned. Rates increase, fleets change, and an arrangement negotiated for a growing operator may be inadequate for a shrinking operator. But the exit is worth it in a more restricted set of circumstances than the rate comparison suggests: when the engines are in good condition and the records are complete, when the next shop visits are far enough away to give a new provider a good start, when the fleet stays long enough to amortize the transition cost, and when the aircraft leases do not exist or have redelivery dates that align.
When these conditions are not met, the cheapest answer is usually to renegotiate rather than exit — and the same seven lines of data that would have supported an exit are exactly what makes a renegotiation credible. The work is not wasted either way, which is the only comforting thing about this topic. More fleet management and technical material is available at fl330.com.

Leave a Reply
You must be logged in to post a comment.