A liquidator replies, in three lines, that no further technical request will be handled. The fleet, meanwhile, keeps flying: airworthiness certificates remain valid, checks are up to date, nothing is grounded. What has just stopped is not airworthiness itself, but the function that sustains it: the one that revises maintenance data, designs repairs, and proposes corrective actions. The question is no longer whether the aircraft will fly tomorrow, but for how much longer, and at what cost.
What Fades, What Survives
A type certificate is a design approval. It attests that a design — an airframe, its systems, its engines, and the associated limitations — meets a certification basis fixed at a given date. This title is held by a legal entity, but it is not the same as that entity. The disappearance of the holder does not cancel it: the certificate remains on record, the type certificate data sheet continues to describe the type, and each aircraft retains its individual certificate of airworthiness as long as it remains conforming to the approved design and in a condition for safe operation.
What ceases are the obligations attached to the title, and above all their execution. A type certificate holder carries a continuing burden: keeping the instructions for continued airworthiness up to date, preserving and maintaining the design data, collecting and cross-referencing in-service events, investigating failures liable to create an unsafe condition, proposing corrective actions, designing repairs that exceed published limits, and finally maintaining a design-office capability. None of these functions is automatically taken over by anyone.
The nuance is cruel because it is invisible day to day. An orphaned fleet does not collapse: it carries on exactly as the day before, until the first event that requires a design decision. It is this gap — nothing changes, then everything suddenly locks up on a specific case — that explains why the issue is addressed too late, and by the airworthiness department alone, when it is in fact a fleet-wide horizon.
When a company that certifies an aircraft type disappears, the aircraft can still fly, but no one is left to update maintenance rules or approve repairs. The fleet works fine until a problem arises that needs a fix no one can authorize anymore.
An airline operating a fleet of Airbus A320s with a type certificate holder in liquidation finds that a critical part (e.g., a landing gear actuator) fails. Without the original manufacturer to approve a repair, the airline must either find an approved alternative part (which may not exist) or ground the aircraft until a costly new design approval is obtained.
| Situation | Type Certificate | Maintenance Data | An Out-of-Limits Repair | A New Unsafe Condition |
|---|---|---|---|---|
| Active holder | Live and exercised | Revised from the experience of the worldwide fleet | Designed and approved by the holder | Service bulletin, then airworthiness directive |
| Holder defaulted, title not taken over | Persists, with no one to exercise it | Frozen at the last revision issued | Must be designed elsewhere, without the original assumptions | Directive drafted with no design solution available |
| Title transferred to an acquirer | Live, obligations taken over | Resumed if the data followed the title | Possible again through the normal channel | Handled normally, with a point of contact |
| Title abandoned or revoked | No longer a basis for new approvals | No issuer left, no update possible | Outside the ordinary framework | Continued operation falls under special provisions, decided case by case |
Maintenance Data That No Longer Ages
The maintenance manual, the illustrated parts catalogue, the structural repair manual, the wiring diagrams, and the maintenance planning document are not books: they are living objects, corrected at each revision by the experience of the worldwide fleet. The day the issuer stops, they cease to age — which is anything but reassuring: they describe a frozen state of the art while the airframes themselves keep accumulating hours.
The effects surface at the bottom, in details. A task refers to specific tooling whose supplier has closed. A procedure calls for a part reference that is no longer produced and for which no equivalent has ever been published. A torque value was corrected for other operators by a revision that no one issued. A limit in the structural repair manual applies to a zone that, on the oldest airframes, now falls outside the scope covered by the original analysis. Each of these points can be worked around; their accumulation changes the nature of an airworthiness department’s work, which shifts from application to justification.
The most constraining case remains that of airworthiness limitations. This part of the programme — life limits of critical parts, structural integrity tasks, maintenance certification requirements, tasks related to fuel tank ignition risk — is approved design data. An operator does not modify it, nor does a maintenance organisation: it can only be revised through a design approval. Without a holder, a task that has become impossible to perform as written has no ordinary path of correction left: an alternative means of compliance request is needed, assessed case by case, with the burden of demonstration resting entirely on the operator.
The trap. The licence to access the data is not the data itself. Many technical subscriptions are consulted online and end with the contract, sometimes as soon as insolvency proceedings open. Anyone who can no longer download on Monday the revision they consulted on Friday has not merely lost access: they have lost proof of the revision applicable at the time the work was performed — the very proof an auditor or a buyer will ask for. Locally archiving every revision received, complete and dated, is the only safeguard, and it must be in place beforehand, not afterwards.
The Airworthiness Directive Loop Runs Empty
An airworthiness directive is not a spontaneous document. It is the outcome of a loop: an operator reports an event, the type certificate holder aggregates it with others from the rest of the fleet, identifies an unsafe condition, works out a corrective action — inspection, modification, restriction — and publishes it as a service bulletin. The authority of the State of design then makes it mandatory, and the other authorities pick up the information.
Remove the second link and the loop no longer closes. Events continue to be reported, but no one cross-references them at the type level any more: the same symptom observed on three continents remains three isolated cases, each classed as anecdotal by an operator whose only sample is its own fleet. And when an unsafe condition is eventually identified — by an authority, by an accident investigation, by an operator large enough to have its own statistics — there is no design solution left to make mandatory.
The authority is not powerless, though, but its tools are cruder. It can impose a repeated inspection with no final fix, at an interval chosen out of caution. It can impose a life limit on a part whose extension no one can justify any more. It can restrict the domain of use or require the removal of equipment. Each of these measures is legitimate; all of them cost, in operation, far more than the modification a design office would have created.
There is also a dispersion effect. Registration authorities in principle adopt the mandatory information issued by the State of design; when it issues nothing more, each decides for its own register. Two identical aircraft, operated under two flags, can then find themselves subject to different requirements, and compliance ceases to be a property of the aircraft and becomes a property of its flag instead.
The right reflex. Document the method, not the reference. A compliance file that merely states « complies with the applicable service bulletin » becomes unusable once the bulletin is no longer accessible and its issuer can no longer confirm its content. Attaching the body of the procedure applied, the values recorded, the configuration obtained, and the means used turns a dead reference into a self-standing demonstration — work that costs little while the source exists, and a great deal afterwards.
Parts: Four Routes, None Free
The question of parts is rarely posed on day one, because buffer stock and the secondhand market absorb the shock. It becomes structural afterwards, and it does not concern consumables: it concerns type-specific items — fittings, cowlings, secondary structure parts, older computers, actuators whose original equipment manufacturer has itself discontinued the line.
Four routes exist, and it is better to evaluate them together than to discover them one after another. Two depend only on the market and are being depleted — the secondhand stock, whose tightening precisely brings back parts of dubious traceability, and cannibalisation of one’s own grounded aircraft. The other two depend on definition data that someone must hold and be able to license. This point, contractual before it is technical, decides everything: without the data, production under an approved organisation is closed off, and approval of a replacement part by a third party once again becomes a full design case, to be financed reference by reference.
| Route | What It Requires | Timeframe, Order of Magnitude | What Limits It |
|---|---|---|---|
| Stock and secondhand market | Full traceability and a valid authorised release | Immediate to a few weeks | Finite pool, unstable pricing, reappearance of unapproved parts |
| Production under an approved organisation | Licensed access to the definition data | On the order of several months | Impossible if the data did not survive the liquidation |
| New design approval | Design office, justification, qualification testing | Typically more than a year | Fixed cost per reference, rarely amortised over a small fleet |
| Cannibalisation from the fleet | Withdrawn aircraft, complete removal and traceability record | Immediate, since the aircraft is already withdrawn | Reduces the fleet and degrades the residual value of the remaining aircraft |
Repairing When No One Holds the Assumptions Any More
As long as damage stays within the limits of the structural repair manual, nothing changes: the repair is described, its consequences have already been assessed, and the maintenance organisation applies it. Outside these limits, the repair becomes a design change, which must be designed and then approved. This is where the absence of a holder is felt, and not in the way one might imagine.
The problem is not the approval. Approved design organisations exist, and alternative procedures make it possible to handle limited scopes. The problem is the raw material of the calculation: loads applied in the zone, allowable material stresses as qualified, damage tolerance assumptions, tests that validated the whole. All of this belongs to the holder’s certification file. Deprived of these elements, a third-party design office can only work by over-designing: more material, more fasteners, more mass, and special inspections imposed for life to compensate for the uncertainty.
The consequences show up in operations before they show up in the accounts. An ordinary piece of damage grounds an aircraft longer, an accepted repair carries permanent restrictions and recurring tasks, the list of tolerated discrepancies grows thicker with items that were not there before. At the fleet level, this is not an incident but a drift: the unscheduled share of maintenance takes up a place that the design of the flight programme had not anticipated.
The Structural Limit Cannot Be Negotiated
On transport aircraft, the structural maintenance programme rests on a damage tolerance demonstration and a full-scale fatigue test. This gives rise to a limit beyond which the demonstration is no longer held valid: the programme is no longer deemed to cover the simultaneous occurrence of multiple cracks. This limit is not a negotiable commercial life, it is approved design data.
Pushing it back is not a matter of paperwork. The fatigue test must be extended or a new one conducted, the analyses redone, new inspection tasks established, and the whole approved. This requires access to the test specimen, the recorded data, and the calculation models — that is, the technical asset most likely to have been scattered during the liquidation. For an orphaned fleet, the limit becomes a retirement date known in advance, one that nothing in operation can push back.
The same reasoning applies, on a smaller scale, to the life limits of critical parts. A life extension is justified by analysis and testing, never by good in-service behaviour. An operator who observes, across dozens of removals, an apparently comfortable margin has no way of drawing a regulatory conclusion from it. This is the point where accumulated experience, which is precisely what gives an operator its value, is worth nothing in regulatory terms.
Regaining Control: Arrangements That Hold Up
A type certificate can be transferred. It is the cleanest solution, and it does happen in practice: a company specialising in legacy-type support, a group of operators, sometimes the acquirer of the industrial assets, takes over the title and the obligations that go with it. The transfer is not automatic: the acquirer must demonstrate to the authority that it has the data, the design capability, and the organisation to carry the burden over time. This is where files fail — not on willingness, but on the dispersal of the data.
Hence the most cost-effective measure, and the least practised: dealing with the question beforehand. An escrow clause for the definition data and the instructions for continued airworthiness, triggerable in the event of the holder’s default, is negotiated at the time of purchase, when the buyer still has leverage. Years later, its absence is paid for directly out of whatever value remains in the fleet. The same logic applies to documentary access: demanding complete, offline sets at each revision, rather than a revocable right of consultation.
On the operator’s side, two capabilities change the picture. A continuing airworthiness management organisation that truly masters its own programme — rather than merely applying someone else’s — knows how to carry well-argued alternative means of compliance requests rather than suffer refusals. Stable access to a design capability, whether in-house or contracted, turns every out-of-limits damage into a handled case rather than a grounded aircraft. Pooling between operators of the same type, long reserved for general aviation, is often the only way to finance a design case when the fleet concerned numbers in the dozens.
What to Check in Your Own Documentation
Four documents deserve to be opened before the question arises. First, the technical data access contract: what it provides for in the event of the publisher’s insolvency proceedings, and whether offline sets are delivered. Then the part of the maintenance programme devoted to airworthiness limitations, with its revision index and issuer — knowing who, today, would be able to revise it. The compliance file for directives, to check whether it documents methods or only bulletin numbers. Finally, the list of references sourced from a single supplier: this is the true vulnerability map of a fleet, and it fits on a single page.

A grey area remains, and it is better to address it head-on: the boundary between replacing an obsolete part with an equivalent and changing the design. A connector, a relay, a seal whose reference has disappeared is in practice replaced with whatever the market offers; knowing at what point this substitution becomes a modification is not settled in a manual, it is discussed with the authority. It is better to open this dialogue on ten chosen references than to have it forced on you over a single one, discovered during an audit. These judgment calls are usefully compared between peers, in particular on the FL330 professional forum.
For anyone preparing a type rating, the stakes are different but very real. An orphaned type is operated with a thicker list of tolerated discrepancies, more workaround procedures, and a shorter fleet horizon than the size of the fleet would suggest. Three questions are enough: is there an active holder, when was the last revision of the maintenance data, and where does the type’s structural limit lie. The answers say what the rating will be worth in the medium term. The FL330 training programmes cover this airworthiness dimension, rarely addressed on the flight crew side.
This article describes a mechanism, not a rule applicable to a specific case: the text in force, the position of the competent authority, and the operator’s approved documentation prevail over everything stated above.
Questions fréquentes
Does the disappearance of the type certificate holder make the aircraft unfit to fly?
No. An aircraft’s certificate of airworthiness rests on its conformity to the approved design and on its condition for safe operation, not on the existence of the company holding the title. An orphaned fleet therefore keeps flying normally the next day. What disappears is the ability to restore airworthiness in unforeseen cases: repairs beyond published limits, a part with no equivalent, a task that has become impossible to perform, a new unsafe condition.
Can a major repair still be approved on an orphaned type?
Yes, the route exists: an approved design organisation, or an alternative procedure for a limited scope, can design and have the repair approved. The difficulty is not the approval but the input data: loads, material allowables, and damage tolerance assumptions belong to the holder’s certification file. Without them, the repair is designed by over-sizing the margins, which results in heavier solutions, often accompanied by inspections that recur for the aircraft’s whole life.
What becomes of an airworthiness directive when there is no longer a service bulletin to make mandatory?
The authority retains its competence to impose a measure, but it no longer has a design solution to prescribe. It therefore falls back on precautionary tools: repeated inspection with no final fix, a life limit on a part, a restriction on the domain of use, removal of equipment. These measures are more costly in operation than a designed modification, and they can diverge from one register to another since no State of design any longer sets the pace.
Can a type certificate be taken over by a third party?
Yes. A type certificate is transferable, subject to the agreement of the competent authority. The acquirer — a specialised support company, a group of operators, or an industrial party — must demonstrate that it holds the design data, that it has a design-office capability, and that it can assume the continuing obligations attached to the title. In practice, cases rarely fail on the acquirer’s willingness and almost always on the dispersal or loss of the data during the liquidation.
Can the structural programme's validity limit be extended without the holder?
In practice, no. This limit stems from a damage tolerance demonstration and a full-scale fatigue test. Pushing it back requires extending or redoing the test, redoing the analyses, and establishing new inspection tasks, hence accessing the specimen, the recorded data, and the calculation models. For an orphaned fleet, this limit becomes a retirement date known in advance, one that no amount of good in-service behaviour can push back.
What should be done before the problem arises, while the holder is still active?
Three actions change what follows. Negotiate, at the time of purchase or contract renewal, an escrow clause for the definition data and the instructions for continued airworthiness, triggerable in the event of default. Require the delivery of complete, offline documentation sets at each revision, rather than a mere right of consultation. And keep an up-to-date list of references sourced from a single supplier, which immediately gives the map of failure points.

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