An outstation, a three-month contract placed through an agency, a certification authorisation handed over on the first morning as two stapled pages nobody has read since. Eighteen months later the agency has closed, the organisation has changed its name, and a technical investigation traces its way back to a work card closed on an evening of delay. The question asked is never who was invoicing the service: it is who signed, under which privilege, and within which written scope.
Three separate credentials, a single signatory
Hangar language conflates three things that share neither the same author, nor the same lifespan, nor the same effect. The aircraft maintenance licence is issued by the authority. It attests to a body of knowledge and to verified experience, it carries categories — routine line maintenance, mechanical, avionics, release to service after base maintenance — and type ratings. It follows the individual from one country to another and from one employer to another. Taken on its own, it grants no right at all to sign for an aircraft operated in commercial air transport.
The certification authorisation is issued by the approved maintenance organisation. It is personal, written, numbered and, above all, bounded: types and variants covered, task categories, sites, explicit limitations. It comes into being the day the organisation signs it and lapses the day the organisation withdraws it, or when the assignment ends, with no notice and no useful appeal. It is not portable: two organisations maintaining the same family of aircraft issue two different authorisations, with two scopes that do not overlap exactly.
The organisation approval, finally, is the framework under which the certificate is issued. It is what the authority oversees, what sets the maintenance data baseline, the forms, the quality process and the authorisation procedure itself. A certifying staff member’s signature is affixed in the name of that approval — but it is affixed by an identified natural person, and it is that person who answers for what has been certified.
One case escapes this pattern: the simplest aircraft, not operated in commercial air transport, for which a certificate may be issued directly by the licence holder, within the limits of their category. The scope is narrow, and it confirms the rule rather than weakening it.
What the certificate says, and what it does not
A CRS does not state that the aircraft is free of defects. It states two things, precise and verifiable: that the recorded work was carried out in accordance with the applicable maintenance data, at the revision in force at the time of execution, and that nothing found prevents release to service under the conditions recorded. Everything else — the general condition of the machine, what was not requested, what someone else would have inspected — falls outside the scope of the certificate.
That narrow scope is what protects the signatory, provided it is held to. It requires that open deferred defects be recorded and carried forward under the applicable procedure, that fitted parts be traced with their release document, that tasks whose execution was shared be identifiable. A clean certificate is one whose exact content can be reconstructed two years later without relying on anybody’s memory.
It is, finally, irreversible: a release to service is not withdrawn, a new one is issued after further work. An act that cannot be recalled cannot be delegated, cannot be covered retroactively and cannot be cancelled by agreement between the parties.
The certificate only confirms that the work was done correctly and that nothing stops the plane from flying. It doesn’t mean the plane is perfect—just that the specific tasks done were done right. Once signed, the certificate can’t be undone, even if more work is needed later.
On a hot day in Dubai, a mechanic certifies an A320’s landing gear after a routine check, even though the runway was wet. Later, the plane skids during landing. The certificate doesn’t cover the runway conditions—it only confirms the gear was checked properly. The mechanic isn’t liable for the skid because the certificate didn’t claim the runway was safe.
The written scope is the only perimeter that counts
A serious certification authorisation sets out rows and columns: aircraft types or groups, the task categories opened, the sites where the privilege applies, and the exclusions. So-called specialised work — non-destructive testing, welding, compass compensation, particular workshop operations — is almost always left out, and falls under separate authorisations. Certifying staff arriving on assignment inherit that document, not local custom.
That is where the gap opens between what the organisation believes it has granted and what it has written. A type variant introduced into the fleet six months earlier, an extension granted verbally “until the paperwork is updated”, a station added to the network: all of them situations where the work gets done, where the form accepts the signature, and where the written scope says no.
The trap. A signature is not retroactive supervision. On an evening of delay you will be asked to close a work card carried out by a mechanic you did not oversee, or to cover a variant absent from your authorisation until the document is updated. The two acts look alike on the form and still look alike in the maintenance record; they look nothing alike before the authority, which compares the written scope with the date of the act, not the organisation’s intention with the reality of the workload.
Three liabilities, a single contract
Action against a certifying staff member takes not one form but three, and they do not follow the same route. The first is administrative: the organisation can withdraw the authorisation at any time, the authority can limit, suspend or revoke the licence. Those decisions strike the individual, follow them into the neighbouring country and show up in every later recruitment file. No contractual stipulation has any hold on them, because neither of the two bodies concerned is a party to the contract.

The second is criminal, and it is personal by construction: two companies do not agree between themselves on who will answer for an offence. The third is civil, and it is the only one where status changes anything. An employee acting within the limits of the task entrusted by their employer is, under most European legal systems, covered by that employer’s liability towards third parties, save for intentional fault or fault detachable from their duties. The independent contractor, by contrast, contracts in their own name: the organisation that has compensated a victim may seek recovery against them within the limits of the contract and of the insurance.
| Item | Staff employed by the organisation | Authorised independent contractor |
|---|---|---|
| Licence | held by the individual | identical, held by the individual |
| Certification authorisation | issued and revised by the employer | reissued by each client organisation, for each assignment |
| Administrative sanction | identical | identical |
| Criminal liability | personal | personal |
| Civil liability towards third parties | in principle absorbed by the employer | borne in one’s own name, subject to the clauses negotiated |
| Recovery after compensation | tightly constrained by employment law | open within the limits of the contract |
| Insurance | the employer’s policy | to be taken out, with explicit aviation cover |
| Recency and continuation training | organised and funded by the employer | to be organised, evidenced and funded yourself |
| Working reference documentation | one only, familiar | one per organisation, to be relearned each time |
Hence the most widespread misunderstanding. A clause stating that the organisation assumes full responsibility for the certifications issued is not useless: it allocates the final economic burden between two parties. It does nothing else, and certainly not what it is credited with.
| Action brought | Who decides | Effect of the assignment clause |
|---|---|---|
| Withdrawal or reduction of the authorisation | the organisation | none |
| Suspension or restriction of the licence | the authority | none |
| Criminal prosecution | the criminal court | none |
| Claim by an injured third party | the civil court | cannot be invoked against the third party |
| Final allocation between organisation and contractor | the parties, then the court | real: this is the only useful ground |
The sequence that protects, before the signature
Experienced certifying staff have absorbed this sequence to the point of no longer seeing it. It nevertheless comes down to five questions, and each one has an exit. Does the written scope cover exactly this type, this task, this site? Is the maintenance data used the organisation’s own, at the applicable revision, and did you have direct access to it rather than through a photocopy left on the bench? Was the work carried out or verified under conditions you can genuinely attest to? Are the deferred defects recorded, carried forward and acceptable against the operator’s reference documentation? Only then, the signature.
The fifth possible answer is not a production failure, it is the counterpart of the privilege. Refusing to sign and recording the reason is a normal technical act, and an organisation that treats that refusal as a commercial incident has just told you something useful about the rest of the assignment.
The right reflex. Ask for the written copy of your certification authorisation on the first day, date it, keep a personal copy of every revision, and have it written into the assignment contract that a reasoned refusal to sign can be neither deducted, nor charged back, nor penalised. A no-consequence refusal clause protects you more than ten lines of hold-harmless wording, because it acts before the act rather than after the damage.
Holding the privilege when you change organisation three times a year
The certification privilege does not maintain itself. Three requirements run in parallel: recent maintenance experience, which the regulation expresses as a cumulative total of months of actual practice within a rolling window — the order of magnitude commonly applied is counted in a few months over a few years, and the exact figure is read in the applicable regulation, not in workshop custom; periodic continuation training, typically every two years, covering changes to the reference documentation; and human factors training, initial and then maintained. To this is added, at each new organisation, training on internal procedures: forms, management of deferred defects, quality process, occurrence reporting system. Two organisations applying the same regulation never write their manual in the same way.
For an employee, these obligations are a scheduling item. For an independent contractor, they are a cash-flow item, and above all an evidence item: the organisation keeps its own records, not your career. A personal experience log — dates, types, sites, nature of the work, authorisation references — is either kept day by day or not kept at all. Reconstructing it three years later from invoices is a painful exercise, and it falls at the worst possible moment: renewal.
The same mechanism outside the hangar
This architecture is in no way peculiar to maintenance, and seeing it elsewhere helps to understand it. An examiner exercises a personal authorisation issued by the authority, within the framework of a training organisation or an operator. The test report they sign commits their assessment, not the company that invoiced their day. To challenge a test is to put that authorisation in question: the service contract appears nowhere in the discussion.
The captain follows a neighbouring logic when accepting an aircraft with an open deferred defect: they apply the operator’s reference documentation, but the decision remains theirs and attaches to their licence. Everywhere, the same rule: the privilege belongs to a person, it is exercised within the framework of an approval, and the commercial relationship that brought that person on site enters into neither of the other two.
What to check in your own file
Six items deserve to be in order before the next assignment rather than after the next summons. The written, dated copy of the scope of authorisation, with its limitations, for each organisation. The training certificates for internal procedures, which prove the authorisation rested on something other than a handshake. The personal experience log, kept continuously. The professional indemnity policy, of which three precise points must be read: the existence of explicit aviation cover, the trigger basis adopted — occurrence or claims made — and the length of the extended reporting period, the one that covers claims arriving after the end of the contract. A waiver of subrogation from the operator or the organisation, or failing that the contractor’s name on their own policy. Finally, the no-consequence refusal clause.
One grey area remains that nobody fills completely: access to the records after leaving. Maintenance documents belong to the organisation and to the operator, they cannot be taken away, and confidentiality forbids it. Certifying staff can nonetheless record their own references — dates, registrations worked on, nature of the work, authorisation number — without reproducing any document. It is little, and it is the only thing that will remain if the entity that held the records has disappeared in the meantime.
For anyone preparing a type rating or still hesitating between employment and contracting, the consequence is concrete: the organisation is chosen as much as the assignment. A clear maintenance organisation exposition, an authorisation procedure that issues a precise document, a reporting culture that does not equate a refusal to sign with a production incident are worth more, over a career, than a slightly higher day rate.
On each of these points, the applicable regulation, the maintenance organisation exposition and the operator’s approved documentation prevail over what you have just read: this article describes a mechanism, it replaces neither the manual that authorises you, nor the particular conditions of your insurance policy.
Questions fréquentes
Can an assignment clause put the organisation in my place if something goes wrong?
It allocates the final economic burden between the two parties that signed it, and on that count it is useful. It has, however, no effect on the authority’s decision to suspend or restrict a licence, none on a criminal prosecution, and it cannot be invoked against an injured third party bringing a direct action. Negotiate it for what it can actually do: cap a recovery claim and organise the insurance.
Does my certification authorisation follow me from one organisation to another?
No. Only the licence follows the individual. The authorisation is issued by each approved organisation, with its own scope, and it ends with the assignment or by decision of the organisation. Two organisations maintaining the same fleet will issue two documents whose limitations differ, and the second must be read afresh instead of being assumed to repeat the first.
Am I entitled to refuse to sign a release to service?
Yes, and that refusal is the normal counterpart of the privilege: the signature would be worthless if it were owed. The refusal must be reasoned and recorded under the organisation’s procedure, then escalated to the quality function. Having it written into the assignment contract that a reasoned refusal entails neither deduction nor termination avoids having to arbitrate between an invoice and a signature.
What insurance should an independent certifying staff member take out?
Professional indemnity insurance including explicit aviation cover, since most general policies exclude this sector. Three points are to be checked before signing the contract: the trigger basis adopted, the length of the extended reporting period that covers late claims, and the existence of a waiver of subrogation from the organisation, or the contractor’s name on its policy.
What should be kept personally after an assignment ends?
The dated copy of the scope of authorisation and its limitations, the training certificates for internal procedures and human factors, and an experience log kept continuously: dates, types, sites, nature of the work. The maintenance documents themselves belong to the organisation and to the operator and cannot be taken away, but nothing forbids recording your own references.
Can a release to service be issued without going through an approved organisation?
Only for the simplest aircraft, not operated in commercial air transport, and within the limits of the licence category held. Outside that case, the privilege is exercised under the approval of a maintenance organisation, which supplies the reference documentation, the forms and the personal authorisation. The scope of the exception is narrow and is checked against the text before being invoked.

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