The contract is ready, the aircraft is available in a month, and it carries a registration that does not belong to the zone where it will fly. The question raised in committee is almost always the same: how long will the repaint take. That is the wrong question. What actually drives the entry-into-service date is the gap between two sets of obligations — those of the State of Registry and those of the State of the Operator — and the time needed to close that gap before the authority that must grant its approval.
What the authority approves, and for how long
A dry lease is not simply making an aircraft available: it is an entry into the lessee operator’s certificate. The aircraft flies under the lessee’s operations manual, its minimum equipment list, its procedures, its crews and its continuing airworthiness management organisation. The lessor retains only ownership and the return conditions. Operational control belongs entirely to the lessee, and that is the first thing the authority looks for in the contract submitted to it: a clause that would leave the lessor any oversight of the conduct of the flight, of crew assignment or of the acceptance of a technical deferral shifts the operation into an entirely different regime.
The approval therefore does not bear on the aircraft alone. It bears on a pairing — this operator, this aircraft — for a given duration. It is formalised through an amendment to the operations specifications, where the registration is named explicitly, and it lapses with the lease: an extension must be requested, it cannot simply be assumed. When the aircraft comes from a register outside the zone, this approval is a prerequisite, and the demonstration expected fits in one sentence that the whole file exists to support: the continuing airworthiness and operating standards applied to this aircraft are equivalent to those that would apply if it were registered within the zone.
A scheduling constraint is built into the principle itself: an aircraft cannot appear simultaneously on the specifications of two operators. The previous operator must have removed it from its own, which in practice only happens on delivery. Hence the form the decision almost always takes: a conditional approval, signed subject to production, on the day the aircraft is made available, of documents that do not yet exist at the time of the review.
Two States, two sets of obligations
The convention governing international civil aviation splits obligations between the State of Registry and the State of the Operator. The former carries the aircraft’s airworthiness, its crew licences and its radio station licence; the latter oversees the operation. As long as the two coincide, no one gives it a thought. As soon as they separate, the dividing line runs straight through the middle of the aircraft, and nothing guarantees it falls where the operator expects.
When an aircraft is registered in one country but operated by a company in another, the two countries have different rules. The State of Registry controls things like airworthiness and crew licenses, while the State of the Operator controls how the plane is flown. If these rules aren’t aligned, the operator has to follow both sets, which can cause delays and extra work. The best solution is for the two countries to sign an agreement to transfer some responsibilities to the operator’s country, but this can take a long time and isn’t guaranteed.
An airline in France wants to lease a Boeing 737 registered in the U.S. The U.S. controls airworthiness, while France controls operations. Without a transfer agreement, the airline must follow both U.S. and French rules for maintenance, crew licenses, and radio stations. This means extra paperwork, two sets of deadlines, and potential delays if the rules conflict. The airline must request a transfer agreement, which can take months, or manage the double workload until the agreement is signed.
The same text provides the remedy: an agreement concluded between the two States transfers to the State of the Operator specifically named functions, for listed registrations. It is not the operator who signs it. It is negotiated authority to authority, and it is the most poorly estimated schedule item in the whole project, because it depends on no supplier and offers no leverage for follow-up.
Absent that, the two sets of rules add up instead of replacing one another. The aircraft remains subject to the directives made applicable by its State of Registry while the operator remains subject to its own: two task calendars, two points of contact for the same deferral, two ways of counting a deadline. This double bookkeeping costs staff time in the technical office and must be described in the continuing airworthiness management organisation’s exposition before it is lived through. On this point European law leaves no choice: its continuing airworthiness requirements also cover aircraft registered in a third country as soon as they are used by an operator whose operations are overseen by a Member State.
| Function | Without a transfer agreement | With a transfer agreement |
|---|---|---|
| Airworthiness directives | Those of the State of Design, augmented by those made applicable by the State of Registry | A single list, maintained under the rules of the State of the Operator |
| Maintenance programme | Approved by the State of Registry, in its own format | Approved within the framework of the operator’s continuing airworthiness management organisation |
| Airworthiness review | Conducted and certified under the regime of the original register | Conducted under the regime applicable to the operator |
| Exemptions and alternative means of compliance | To be requested from the authority of the original register, often with no dedicated point of contact | To be requested from the authority already overseeing the operator |
| Crew licences | The State of Registry may require validation of its own licences | Licences issued to the operator’s crew are sufficient |
| Radio station licence | Issued and renewed by the State of Registry | May be among the transferred functions |
| Real burden on the operator | Permanent dual framework, described in the exposition and staffed accordingly | Single framework, at the cost of a negotiation between authorities whose timeline no one controls |
The equipment gap is the real critical path
Two regulations pursuing the same safety objective do not impose the same fittings, at the same thresholds, or on the same dates. The inventory is always worked in order of lead time: flight recorders, whose duration and parameter list depend on the date the certificate of airworthiness was first issued; surveillance equipment, with the required collision-avoidance system version, the transponder and position broadcasting; communication, with the radio channel spacing and the data link required in upper airspace; ground proximity warning; distress beacon; then the cabin, with the extinguishing agents permitted, oxygen, life vests and rafts tied to the area of operation, first-aid kits, floor-path lighting, placards and markings in the operator’s language.
The trap is not in the list, it is in how it is read. A piece of equipment is not simply present or absent: it passes through five layers and only serves its purpose once all five have been cleared. A receiver bolted to the panel with no corresponding supplement in the flight manual is dead weight; a documented function absent from the minimum equipment list forbids any departure at the first failure; an installed capability that was never taught brings down the approval that relied on it.
| Layer | Question asked | Evidence expected | What falls if it is missing |
|---|---|---|---|
| Installed | Is the equipment on board and connected? | Logbook, installation record | Nothing to discuss: the requirement is not met |
| Approved | Does the modification rest on approval data accepted by the incoming authority? | Design approval or supplemental type certificate recognised | The aircraft no longer conforms to an enforceable definition |
| Documented | Does the flight manual cover this definition? | Flight manual supplement, up-to-date weighing record | The crew has no enforceable limitation or procedure |
| Usable | Do the procedure and the failure tolerance exist? | Operations manual part B, minimum equipment list | No departure allowed with the equipment inoperative, no codified use |
| Trained | Has the crew been trained on this definition? | Adaptation or differences programme, recorded checks | The specific approval that relied on it |
Installed does not mean usable. The costliest gap is not seen in the hangar, it is on paper: a delivered definition that departs from the one covered by the flight manual supplement, a supplement issued under another State, a design approval the incoming authority does not accept as is. In all three cases the equipment is genuinely on board and the approval that depends on it falls. The restriction is then written into the operations specifications, and it reads as lost routes.
The records, and what cannot be reconstructed
Taking over the airworthiness records is archival work that no one likes to price out. It begins with reconciling the directives: those of the State of Design, which apply everywhere, and those the State of Registry may have added or adjusted. Life-limited parts are then handled without discussion: a part whose traceability from origin is not established is not a part to debate, it is a part to remove. Repairs and modifications require approval data acceptable to the incoming authority, which is far from automatic when they rest on a supplemental type certificate issued elsewhere. Damage mapping, a currently valid weighing, and the cabin configuration actually installed round out a set that the lessor will readily hand over — in its own format.
Exemptions do not follow the aircraft. An alternative means of compliance, a deadline extension, an interval extension granted to the previous operator are tied to that organisation and that authority. On change of operator, they lapse. A schedule built on the deadlines read in the lessor’s logbook is therefore wrong by construction: it must be recalculated on baseline deadlines, then the extensions must be requested afresh in the operator’s own name, which takes the time of a full review.
What remains is the maintenance programme, which is the real undertaking. A programme is not translated: a transition document is built that checks, task by task, what has been accomplished under the outgoing programme against what the incoming programme requires. This document almost always produces the same unwelcome effect, a batch of tasks that were not yet due under one programme and turn out overdue under the other on day one. It is this catch-up, not the livery, that sets the grounding period. Two edge cases deserve to be raised before signing: an airframe whose outgoing programme relied on condition monitoring, while the incoming programme imposes calendar-based inspections, arrives with deadlines that no logbook shows; and an engine or propeller covered by a support contract tied to the lessor falls outside the scope of that contract on change of operator, which shifts the burden of removal and reinstallation onto the lessee without any line of the lease having said so.
What the operator must demonstrate about itself
The authority does not review only an aircraft: it reviews an organisation’s capacity to keep it airworthy. The continuing airworthiness management organisation’s scope must cover the type and this specific aircraft, the maintenance contract must name a workshop whose scope covers both, the minimum equipment list must be established by the operator from the type certificate holder’s master list — never taken over from the previous lessee — and remain consistent with the definition actually delivered. The operations manual’s performance data must match the thrust retained, the fittings installed and the maximum masses actually acquired; the mass and balance system must be fed by this aircraft’s own weighing, not a fleet average. The insurance certificate, finally, must show the registration in clear and cover the area of operation actually planned, including the States overflown: a certificate issued in the lessor’s name, or silent on the aircraft, sends the file back without further examination.
Specific approvals, finally, do not carry over from one registration to another. Reduced vertical separation, performance-based navigation, low-visibility operations, extended diversion time operations: each must be re-demonstrated on this aircraft, with its equipment, its procedures and the training that goes with them. This is where workload planning most often goes wrong, because the approval already exists — on the fleet’s other aircraft.
The gap table is produced before the letter of intent, never after. Ask the management organisation and the workshop for one line per item: actual state observed, incoming requirement, action, long-lead part, days grounded, cost. Long lines become suspensive conditions of the lease, with the financial burden assigned by name and a document-production date. A gap discovered after signature is no longer negotiable: it is paid for.
The approval window, and what remains grey
The approval rarely arrives in one piece. It is conditional, signed subject to production of documents on delivery. It is restricted, the aircraft entering the specifications with a note barring it from a volume of airspace, an approach procedure or a type of operation, until the gap is closed. It is full, finally, which assumes everything has already been produced. These three forms are not chosen: they follow from just two parameters, the length of the lease and the size of the gap.

On a short lease, a large gap does not close: the investment amortises on nothing, and the only useful decision is to know from the study stage which routes and which approvals fall away, then to check that the flight programme avoids them. On a long lease, the same gap becomes an ordinary undertaking, provided it has been costed before signature. In both cases, the return conditions deserve the same attention as the entry conditions: a gap closed for the incoming register is a gap to be reopened on exit, and the contract must state who pays for the removal, the restoration to original condition and the reconstruction of the records.
Four checks are worth making in one’s own documentation before opening a file of this kind. Does the management organisation’s scope mention aircraft registered in a third country? Does the exposition describe how a dual set of directives is maintained, with the person accountable for it? Does the operations specifications amendment procedure allow for a realistic review time, or the theoretical duration of a perfect file? Does the standard lease agreement include a technical gap annex, or only a generic compliance clause that says nothing and commits no one?
What remains are the grey areas that nothing closes. States of Registry that do not sign transfer agreements, or that sign them without the means to carry out the oversight they retain. Registers where the maintenance history is kept in a language and format the management organisation cannot use without certified translation. Airframes that have passed through several successive registers, where each passage has left a layer of acceptances whose origin no one can trace any more. When these three signs pile up, registering within the zone, where the financing structure allows it, regularly ends up cheaper than keeping the original register — and that is a trade-off to raise at the start of the study, not at the moment the aircraft is waiting in a hangar.
The foregoing describes a mechanism, not an enforceable procedure: the applicable text, the terms of the agreement concluded between the two States and the operator’s approved documentation prevail in all circumstances over this article.
Questions fréquentes
Can operations begin before the approval is signed?
No. For an aircraft registered outside the zone, a dry lease is subject to prior approval, formalised through an amendment to the operations specifications where the registration is named explicitly. Until that amendment is signed, the aircraft may be delivered, insured, equipped and its crew qualified, but it will not carry anyone under the lessee’s certificate. The approval is further bounded by the lease term: an extension must be requested before it expires, it cannot simply be assumed.
Is the function-transfer agreement between States mandatory?
On its own it is not a condition of the lease, but its absence changes the nature of the work. Without it, the State of Registry retains airworthiness, crew licences and the radio station licence, and the operator lives with two simultaneous frameworks that must be described in its exposition. With it, the framework becomes single, at the cost of a negotiation between authorities whose timeline belongs to no one in the project.
Can the previous operator's minimum equipment list be reused?
No, it is specific to the operator. It is established from the type certificate holder’s master list, based on the definition actually installed and the incoming operator’s procedures. Reusing the previous lessee’s list risks granting a tolerance on equipment that is absent, or refusing one on equipment that is present — two defects the review detects immediately.
Do specific approvals already held cover the new aircraft?
No. Reduced vertical separation, performance-based navigation, low-visibility operations and extended diversion time operations are granted for a combination of aircraft, equipment, procedures and training. Each approval must be re-demonstrated on the leased aircraft, based on its flight manual supplements and the state of its definition. This is the item schedules most often underestimate, because the approval already exists on the fleet.
What happens to equipment that is installed but not covered by the flight manual?
It is treated as absent as long as the documentation does not cover it. Without a flight manual supplement applicable to the delivered definition, the crew has no enforceable limitation or procedure, and the approval that relied on that capability cannot be granted. There are only two ways out: have approval data accepted by the incoming authority, or accept a restriction written into the operations specifications.
Can the maintenance deadlines read in the lessor's logbook be used as they stand?
They serve only as a starting point, never as a schedule. Alternative means of compliance, deferrals and interval extensions granted to the previous operator lapse with them, and moving from one maintenance programme to another brings out tasks that are overdue from day one. The real schedule must be recalculated on baseline deadlines, from the transition document drawn up between the two programmes.

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