Adding a Type to a Maintenance Licence: The Gap Between the Course and the Practice

Baie d'équipements ouverte sur un avion, faisceaux de câbles denses et panneaux éteints en lumière froide

The file comes back with three words in the remarks box: “insufficient practical elements.” The candidate nevertheless holds the training organisation’s certificate, the mark obtained in the type examination, and a binder of work orders. What is missing is almost never the course itself. It is the task-by-task demonstration that the work was actually performed on the aircraft, at an identifiable level of involvement, under a signature that had the right to be affixed there.

What the organisation’s certificate proves, and what it does not

The certificate issued by an approved maintenance training organisation states one precise thing, and only one: the person attended the type course at the level required for their category, sat the examination, and passed it. Where the course includes one, it also covers the practical element conducted under that organisation’s responsibility. It states nothing more. In particular, it does not state that the person has worked on that aircraft under production conditions: a deadline, maintenance documentation open at the correct amendment, a team leader, an aircraft that has to depart.

Entering the first type of a category onto a licence therefore adds a second demonstration, independent of the first: on-the-job training, conducted at an approved maintenance organisation, on real work, against a programme approved by the authority. The two building blocks do not substitute for one another and do not offset one another. An excellent course does not make up for a thin task record, and a well-filled record does not exempt anyone from anything.

The confusion stems from the resemblance between the documents produced. Both sides show sheets with tasks, dates and signatures. But the training organisation’s sheet attests to supervised learning in an environment built for learning; the maintenance organisation’s sheet attests to production, tied to a work order, a registered aircraft, and a release to service. A file examiner reads that difference first, before even counting the lines.

The training certificate proves you passed the course, but not that you can do the job. The task record proves you did the job, but not that you learned it. Both are needed, and neither can replace the other.

A technician completes a course on the Airbus A320 and passes the exam. They then work on 20 real A320 maintenance tasks over six months, supervised by a licensed B1. The record includes troubleshooting, adjustments, and functional tests across different systems. This combination—course + real work—is what gets the type added to their licence.

The four steps of entering a type on a maintenance licenceFour blocks aligned left to right: theoretical course, then practical element, both under the responsibility of the approved training organisation; then on-the-job training, under the responsibility of the maintenance organisation; then entry of the rating by the authority. A dashed vertical line placed between the second and third block marks the point where most files stall.TheoreticalcoursePracticalelementOn-the-jobtrainingTypeentryapproved training organisationmaintenance organisationauthoritycertificate of recognitionassessed task recordrating on the licencebreaking point of the files
The organisation’s certificate closes the first two boxes, never the third. The dashed line marks the boundary of responsibility: on the left, a training organisation attesting to learning; on the right, a maintenance organisation attesting to work produced.

The two regimes the file almost always confuses

The practical element of the type course pursues a narrow objective: to show that the trainee handles equipment safely, opens the right page, chooses the right tooling, and breaks nothing. It is often conducted on a grounded aircraft, a test rig, a working mock-up or a training aircraft. It remains training, and the organisation answers for it under its exposition.

On-the-job training pursues an entirely different objective: to show that the person can hold a position. It takes place on work that would have happened anyway, whose result is delivered to the customer, and whose trace lives in the organisation’s work file. The programme that governs it sets out the list of tasks to be covered, how the level of involvement is recorded, who supervises and who assesses. It is this programme, not the department’s good will, that makes the record admissible.

Practical element of the type course and on-the-job training: two regimes a file cannot interchange
Criterion Practical element of the course On-the-job training
Approval framework Maintenance training organisation Maintenance organisation
Work medium Training aircraft, rig, working mock-up In-service aircraft, real work
What is demonstrated Safe handling, use of documentation, tooling Holding a position, growing autonomy, judgement
Record produced Course tracking sheet, certificate of recognition Task record tied to work orders
Who signs Instructor designated by the training organisation Supervisor, then designated assessor
Most common reason for rejection Course attended at a level lower than required for the category Non-representative tasks, ungraded involvement
  • Training course practicals are about safe handling and following procedures.
  • On-the-job training is about doing real maintenance work under supervision.
  • You can’t use one to replace the other—both are required.

A task performed during the practical element cannot be recycled as on-the-job training, even if its title is worded identically. This is not administrative pettifogging: the chain of responsibility and the traceability differ, and that is precisely what the file must demonstrate. Copying lines from one record to another is the fastest way to sink an entire file, because duplicated dates jump out immediately.

Representativeness: what the examiner really reads in a record

No one counts the lines first. What is looked at first is how they are distributed, across two dimensions. The first is the system concerned: a record that never leaves the airframe and landing gear demonstrates an assignment, not a type competence. The second is the nature of the work: removal and installation, adjustment, functional test, troubleshooting. The first three are learned by following a work card; the fourth requires understanding the system’s architecture, and it is the one that is almost always missing.

Two technicians work on an engine component, one consulting a manual and the other inspecting the part at dusk.
Practical experience complements theoretical training in maintenance work.
Two task records of identical volume, only one representativeTwo matrices of four columns, corresponding to the nature of the task, and four rows, corresponding to the system concerned. On the left, six tasks concentrated in one and a half columns, but spread across the four rows. On the right, the same six tasks spread across the four columns and the four rows.record returnedrecord acceptednature of the tasknature of the tasksix tasks, a single type of worksix tasks, four types of worksystemsystem
The number of lines does not make representativeness: spread does. Columns: removal and installation, adjustment, functional test, troubleshooting; rows: the aircraft’s systems. A record that covers every system but stays in one column demonstrates a habit acquired at a position, not a type competence.

The second reading concerns the level of involvement. Programmes typically distinguish three levels: the person assisted, performed under direct supervision, or performed and reported. A record where every line carries the same mention tells no story of progression, and the assessor who must conclude on competence is left with nothing to work with. Conversely, a few complex tasks performed autonomously at the end of the course carry more weight than a long series of assisted interventions.

Level of involvement across recorded tasksA chart whose vertical axis carries three levels, assisted, supervised and autonomous, and whose horizontal axis carries the recorded tasks. A step curve rises from the assisted level to the autonomous level before the final assessment. A second, dashed curve stays at the assisted level throughout.assistedsupervisedautonomousrecord that never evolvesrecorded tasksreal progressionassessment
A record that stays flat at the “assisted” level prepares no favourable assessment. The level of involvement is recorded task by task; it is its slope, not its total, that makes the final assessment sustainable.

The trap. The record filled in at the end of the month, from memory, based on the roster. It produces round dates, tasks grouped in batches, and approximate work order references. At the first cross-check against the organisation’s work file — and that cross-check does happen — a single line that does not match its work order casts doubt on all the others. The file is not merely returned: it becomes suspect, and the next one from the same department will be read under a magnifying glass.

Who signs what, and why the signature is the real bottleneck

A task record is not a personal logbook. Every line commits at least two people: the one who did the work, and the one who watched it being done. Supervision must be exercised by someone whose scope covers the type and the work concerned, and that person must be identifiable within the organisation — not merely present on that day. An experienced colleague who does not hold the type rating cannot usefully attest to what he nonetheless saw perfectly well.

The assessor is yet another role. He does not sign off tasks; he draws a conclusion on competence, based on the record and an interview. Confusing him with the supervisor amounts to removing an outside perspective, and it is a classic reason for return when the same signature appears everywhere. Finally, the organisation attests that the approved programme was indeed applied — not merely that it exists, but that it was applied to that person, over that period.

What each signature commits in a type-entry fileFive steps rising from left to right. The first, the performer, carries out the task. The second, the supervisor, attests to the action. The third, the designated assessor, attests to competence. The fourth, the organisation, attests to the application of the approved programme. The fifth, the authority, enters the rating on the licence.performersupervisorassessororganisationauthorityperforms the taskattests the actionattests competenceattests the programmeenters the ratingeach signature commits a distinct scope
Four signatures before the authority’s, and none replaces the previous one. A record where the supervisor and the assessor are the same person loses a step: competence is no longer attested by someone outside the action.

The right reflex. Before the first task, get three names written down in black and white: the reference supervisor, the designated assessor, and the manager who will sign the certificate of programme application. Check that each one indeed appears with that role in the organisation’s documentation, and that the assessor is not the supervisor. Writing down these three names in advance saves an entire record from having to be redone, because a missing signature cannot be made up for retroactively.

The timeline: the part of the file that expires

Recognition of a type course is not eternal. It opens a window during which the entry can be requested; once that window has passed, the theoretical part must be retaken, even if the practical part was exemplary. The practical consequence is counter-intuitive: the calendar risk does not weigh on the tasks, it weighs on the course already paid for. On-the-job training spread over several years because the aircraft was not available can cause the course’s recognition to lapse before it has produced any effect at all.

The window during which the achievements remain admissibleA horizontal time axis. A light band opens at the end of the theoretical course and closes at the admissibility deadline. A first path, in solid line, results in a submission located within the band. A second, in dashed line, leaves the practical part waiting and results in a submission located after the deadline.end of the theoretical courseadmissibility deadlinepractical part left waitinglate submissiontasks recorded as they occuradmissible submissionadmissibility windowtime
It is not the practical part that expires, it is the course’s recognition that carries it. The dashed path performs exactly the same tasks, but records them too late: by the time of submission, the theory no longer covers anything, and everything has to be redone.

A second calendar point often goes unnoticed: the type designation. Maintenance ratings are expressed according to a published list, which sometimes groups several variants under a single rating and sometimes separates them. A task record established on one variant may then either fail to cover the requested rating, or cover it fully. This list is a living document: it is revised as variants appear. Checking the exact designation at the time of the application, rather than at the time of the course, avoids the late discovery that the intended rating is no longer written the way it was noted down.

To this is added the question of recent experience attached to the licence’s privileges, assessed over a rolling reference period. It does not condition the entry of the type itself, but it does condition how it will be used. A type entered on a licence whose privileges are dormant serves no one, and the organisation issuing the authorisation will check it before the authority does.

B1, B2, Category C: three paths that do not resemble one another

The category determines what the practical part must demonstrate, and that is where record templates circulating between colleagues do the most damage. A record built for a B1 entry does not fit a B2 entry as-is: the systems targeted are not the same, nor is the balance between removal-installation and troubleshooting. Category C, finally, is not demonstrated by hands-on work but by the ability to issue a release to service at the end of base maintenance, which shifts the question toward the licence’s access route rather than toward a workshop task record.

What the practical demonstration must cover according to the category sought
Category What the practical part must cover Typical point of friction
B1 Structure, powerplant, associated mechanical and electrical circuits, post-intervention tests Record saturated with removals and installations, without troubleshooting
B2 Avionics, electrical circuits, functional tests and diagnostics on integrated systems Tasks recorded at the level of the replaced equipment, without a diagnostic approach
Category C Ability to issue the release to service of base maintenance based on the teams’ work Poorly identified access route, and scope confused with that of a B1 or B2

There are also group ratings, which cover sets of aircraft rather than a single type. They follow the same logic of proof, but representativeness is assessed at the level of the group: covering a single aircraft of the group is not enough to demonstrate competence on the others. Here again, the question arises upstream: the record must be calibrated to the scope of the intended rating, not to the aircraft the workshop happens to have on hand.

What to go and check in your own documentation

Five points must be checked before starting, not after. The on-the-job training programme applicable to the targeted type, with its approval reference and validity date. The named list of designated supervisors and assessors, with their scope. The record format actually accepted by your authority, which is not always the same as the internal template. The rule for linking a record line to a work order, as it is the only auditable link. Finally, the exact designation of the type as it must appear on the application.

Some grey areas remain, openly acknowledged. The proportion of tasks that can be performed away from the aircraft — on a rig, in the workshop, on a training device — depends on the approved programme and is negotiated with the authority, not with the team leader. Recognition of tasks performed at a subcontractor or another company within the group requires prior written agreement, failing which the lines are discarded. And the portability of a record from one authority to another is not automatic at all, which is worth anticipating when changing employer partway through the process.

For anyone preparing an entry, the consequence is concrete: the useful clock does not start on the first day of the course, it starts on the day the programme, the signatories and the record format are put in writing. Anything produced before that date has a strong chance of counting for nothing.

This text describes a mechanism; it does not constitute authorisation. The applicable regulation, the decision of the competent authority, and your organisation’s approved documentation prevail over everything above, and it is the approved programme that is authoritative on the expected content of a record.

Questions fréquentes

Is the certificate issued by the training organisation enough to have the type entered?

No, except in cases where on-the-job training is not required. This certificate covers the theoretical course, the examination and, where applicable, the practical element conducted under the organisation’s responsibility. For a first type within a category, a task record produced at a maintenance organisation must be added, against an approved programme, with supervision and assessment.

Can tasks performed during the practical element of the course be counted?

No. The two demonstrations fall under different approval frameworks and distinct chains of responsibility. Carrying the same lines over from one record to another is spotted immediately from the dates and weakens the entire file, including the valid lines.

How many tasks must be recorded for a record to be deemed sufficient?

The expected volume is set by the approved programme and by the task list annexed to it, not by a general rule. What decides in practice is the spread: several systems, several types of work — removal and installation, adjustment, functional test, troubleshooting — and a level of involvement that progresses over the course of the training.

Can the supervisor and the assessor be the same person?

This is strongly discouraged and often refused, because it removes the outside perspective on which the competence conclusion relies. The supervisor attests to the actions he has seen; the assessor draws a conclusion on the entire course. Have both roles designated in writing before the first task.

What happens if the on-the-job training spans several years?

The risk concerns the theoretical part: recognition of the type course opens a limited window during which the entry application must be filed. If it expires, the course has to be retaken, even with an irreproachable task record. The duration of the practical course must therefore be fitted to this window, not the other way round.

Can tasks performed at a subcontractor be counted?

Only if the approved programme provides for it and a written agreement governs supervision and traceability. Without this prior agreement, the lines concerned are discarded because the organisation signing the record cannot answer for work performed outside its approval scope.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

FL330, c’est toute l’aviation professionnelle — explorez nos autres espaces.