Aircraft mechanic license: what is the origin of the distinction between airframe and avionics categories?

Plan de travail d'atelier avec vérin hydraulique démonté, pied à coulisse et lampe d'inspection ambrée

The job card says “removal and installation of the computer.” The technician reinstalls the unit, runs the final task test, receives an anomaly message, pulls out the wiring diagram, and starts measuring. At that exact moment, the task has changed category, and the certification that covered it no longer applies. The separation between airframe and avionics categories does not divide two professions by mood: it separates two levels of intervention, and what it prohibits from signing says more than what it allows.

It’s not the manual chapter that decides, it’s the depth

The most common workshop reflex is to decide by system: flight controls to the airframe technician, navigation to the avionics technician, case closed. This shortcut is wrong in both directions. The breakdown of maintenance license categories does not follow the table of contents of the documentation; it crosses two criteria, the nature of the work and the depth required to prove the system is good.

Category B1 covers, in its own right, the structure, the powerplant, mechanical systems, and electrical systems. Category B2 covers, in its own right, avionics and electrical systems. So far, the image of a division by profession holds up. It falls apart in the next line: each category can also intervene in the other’s territory, but only for tasks whose proper execution is proven by simple tests, and which do not require any fault isolation.

This clause is the true articulator of the system, and it’s the one that is often overlooked. It states that an airframe technician can install an avionics unit as long as the final task test is a functional check, and they can no longer sign anything as soon as a fault needs to be isolated. The transition is not symmetrical: the avionics technician does not inherit mechanical work; they inherit electrical and avionics tasks located within mechanical and engine systems. A landing gear actuator removal remains a landing gear actuator removal.

The key difference isn’t what system you’re working on, but how deep you need to go. Simple checks (like “does it light up?”) can be done by either category, but troubleshooting (like “why isn’t it lighting up?”) requires the specialist for that system.

On an Airbus A320, a B1 technician can replace the Flight Management Computer (FMC) as long as the test is just powering it on and checking the display. But if the display shows errors, they must call a B2 technician to diagnose the issue – even though the FMC is part of the “mechanical” flight control system.

What decides the category: the nature of the work crossed with its depthA two-way matrix. On the horizontal axis, the nature of the task: on the left mechanical, structure and engine, on the right avionics and electrical. On the vertical axis, the depth required: at the bottom the simple test, at the top troubleshooting. The lower band is shaded: the boundary can be crossed there, with an airframe licence holder signing an avionics task and an avionics licence holder signing the electrical part of a mechanical task. The upper band is not: each box there refers only to the category of the system concerned.B1 seulB2 seulB1B2closed boundaryclosed boundaryB2: the electrical partB1: no troubleshootingmechanical, structure, engineavionics, electricalnature of the tasksimple test: prove correct operation without isolating a faultfaultfindingessai simpleprofondeur
The boundary can only be crossed in the lower band, that of the simple test. As soon as a fault has to be isolated, the task falls back into the system’s own category, and crossing is not symmetrical.

Where does the breakdown come from: five workshop trades reduced to two licenses

Before European harmonization, national authorities issued titles based on the organization of workshops: airframe, engines, electrical, instruments, radio. Each title corresponded to a workspace, tools, and a team leader, and the system worked as long as the aircraft could be disassembled in sections. It broke down on the line, where a single intervention—a computer removal, a sensor replacement—required three signatures for one hour of work, and where the aircraft waited for the missing certification longer than the repair itself.

The consolidation carried out during European harmonization in the late 1990s did not group trades by affinity, but by diagnostic action. Everything that is diagnosed by disassembling, measuring a clearance, tracking a leak or a crack initiation ended up on one side: structure, engine, mechanical systems, and wiring, which is routed, secured, and inspected like a part. Everything that is diagnosed by reading, comparing a configuration, or interpreting an integrated test message ended up on the other.

From trade-based shop licences to the two current categoriesOn the left, five stacked blocks represent the former national licences: airframe, engines, electrical, instruments, radio and radar. Three arrows group airframe, engines and electrical into a single mechanical category block; two arrows group instruments and radio into an avionics category block. The grouping follows the diagnostic action, not the affinity between trades.cellulemoteurselectricalinstrumentsradio, radartrade licencestwo categoriesmechanical, engine,electricalavionique,instrumentsB1B2
The grouping was done by diagnostic action, not by trade affinity. What is found by dismantling and measuring a clearance went to one side, wiring included; what is found by reading a bus and comparing a configuration went to the other.

Instruments and radio, long two separate worlds, merged for a material reason: their failures stopped being organ failures to become information chain failures. The day the needle and the transmitter shared the same data bus, they shared the same troubleshooting tool, and thus the same license. The trace of this genealogy is still visible in the basic programs: the common core—materials, rules of the art, human factors, regulations—remains largely shared, and it is from the systems modules that the two paths diverge sharply.

What each category opens, and what it leaves closed

The table below brings together what the text grants in its own right, what it authorizes to reach in the neighboring category, and what it locks. The last column is the one that should be displayed on the duty roster: no type training expands it.

Own scope, permitted crossover and locks, by maintenance licence category
Category Domaine propre What it reaches in the neighbouring category What remains closed to it
A Minor scheduled line maintenance and simple defect rectification Nothing beyond the tasks for which it has been trained Any task it has not carried out itself; any troubleshooting
B1, in four subcategories: aeroplane or helicopter, turbine or piston Structure, powerplant, mechanical and electrical systems Work on avionics systems proven by simple test Avionics troubleshooting; software configuration restoration
B2 Avionics and electrical systems Electrical and avionics tasks within mechanical and engine systems, by simple test Mechanical and structural work; base check certification
B3 Unpressurised piston aeroplanes below the maximum take-off mass threshold set by the regulation, around two tonnes The entire aircraft within this scope, airframe and avionics alike Everything outside this scope
C Approbation pour remise en service d’une visite complète en base Relies on the task sign-offs made by B1 and B2 staff Carry out tasks; certify line work

Two nuances deserve to be known. Category B2 does not automatically include Category A privileges, but the text allows them to be exercised provided the same task training and experience requirements are met—provided the company includes them in the certification, otherwise the privilege remains theoretical. Categories dedicated to light aircraft, gliders, and balloons also exist, with their own scope logic.

Two signature architectures: line and baseOn the left, line maintenance: a single task block, carried out and signed off by a category A, B1 or B2 holder, leads directly to the certificate of release to service block. On the right, base maintenance: three separate task sign-offs, two mechanical category and one avionics category, converge on a single certification block signed in category C. A dashed vertical line separates the two halves.line maintenancebase maintenancetask carried out and signed offby A, B1 or B2certificate of releaseto service for line workvisa B1visa B2visa B1check certificationsigned in category Cthe signatory did the workthe C signs on the strength of the sign-offs
In base maintenance, the final signature does not cover the tasks: it covers their closure. The category C holder does not carry out the work and replaces no sign-off; they certify that the check is complete on the basis of the B1 and B2 sign-offs made task by task.

The common area: where the task changes hands

Take a common chain: a position sensor, a harness, a computer, a servo-control, a control rod. The sensor is bolted, so mechanical? It delivers a signal, so avionics? The question is poorly framed. What matters is the action the job card requires to close the task.

Two men work on aircraft avionics in a hangar, one using a diagnostic device.
Avionics diagnostics require specialized tools and teamwork.

A removal-installation of equipment closed by a test that answers yes or no—light off, message cleared, travel within the template—remains in the category of the parent task, regardless of the box handled. A continuity to measure, a fault to locate between the sensor, the harness, and the computer, a configuration load to verify, an adjustment whose acceptance criterion is read on a system value: you have crossed over. The operational criterion is summed up in one question: does someone have to interpret a measurement? If yes, the signature belongs to the category of the system, not the task.

The trap. It’s the equipment exchange that degenerates into troubleshooting. The airframe technician removes and reinstalls the box according to the card, the test fails, and they naturally move on to the wiring diagram because they know how to do it and the aircraft must depart without delay. Technically, they are right; legally, the task has changed category without anything being written anywhere. The approval they will sign will cover work that their license does not cover, and the discrepancy will not be noticed on the same day or the next flight, but during an audit—or in the analysis of an event where the chain of signatures will be traced back.

The right reflex. Read the acceptance criterion of the card before deciding who signs, never the chapter number. If the closure requires interpreting a value, a trend, or an integrated test message, prepare two signatures from the start and split the work order at the handover point. Two signatures cost a few minutes; an approval without basis costs the file, and sometimes the authority’s trust in the company’s entire signing system.

Where the task changes hands in a control chainCinq blocs alignés de gauche à droite : capteur, faisceau, calculateur, servo-commande, tringlerie, reliés par des flèches. Une accolade sous les trois premiers blocs porte le domaine avionique, signal, logique et configuration ; une accolade sous les deux derniers blocs porte le domaine mécanique, organe, réglage et tringlerie. Une bande teintée encadre le calculateur et la servo-commande : c’est la zone où l’essai simple est admis des deux côtés. Un trait vertical tireté marque la limite entre les deux domaines.capteurfaisceaucalculateurservo-commandetringleriesimple test allowed on both sidesB2: signal, logic, configurationB1: component, rigging, linkagethe task card, not the chapter, sets the required depth
The hand changes mid-chain, not at the edge of the chapter. The computer and the servo-actuator belong to the same functional component: either can be removed on a simple test by the other category, but neither can be troubleshot by it.

Two models of responsibility: the individual or the workshop

The European breakdown seems natural to those who grew up with it; it is, however, a choice, and the North American comparison shows it. Across the Atlantic, the individual mechanic’s certificate includes airframe and powerplant mentions, with no avionics equivalent. The ability to approve avionics work does not come from an individual title but from the mentions on the workshop’s approval, supplemented if necessary by a repairman’s title tied to the position and which falls with it.

Where the avionics privilege sits and what that changes in practice
Question European model North American model
Where the avionics privilege sits On the individual licence, in a dedicated category In the ratings of the repair station’s approval
Who certifies avionics work A person authorised by the organisation, holding the category and the type The approved repair station, through the signature of a person it designates under its own approval
What the person takes with them when changing employer The licence and its type ratings; only the authorisation has to be redone Nothing transferable on the avionics side: the capability stays with the organisation
Weak point of the model Rigidity: two categories to keep up to date, two recent experience windows Dependence on the organisation and difficult recognition abroad

This divergence explains a good part of the misunderstandings in recognition files. A seasoned avionics technician trained under the second model has no individual title to convert: they have a skill set attested by an employer, which is not the same currency.

Two models: the avionics privilege on the person or on the shopTwo columns of three blocks. On the left, the European model: individual licence carrying the avionics category, then authorisation issued by the organisation, then certificate of release to service signed by the authorised person; the first block is shaded, the avionics privilege follows the person. On the right, the North American model: individual certificate limited to airframe and powerplant, then repair station approval carrying the avionics ratings, then release issued under the repair station’s authority; it is the second block that is shaded.European modelNorth American modelindividual licence,avionics categoryauthorisation issuedby the organisationrelease signed bythe authorised personindividual certificate,airframe and powerplantrepair station approvalwith avionics ratingsrelease issuedunder the repair stationthe privilege follows the personit follows the shop
The shaded block shows where the avionics privilege sits in each model. On one side it is an attribute of the person, portable from one employer to the next; on the other it is an attribute of the organisation, and it stops at the door.

The license signs nothing: what the certification adds on top

It must be repeated with each promotion: the license is a competence title, not a signing right. The right to sign comes from the certification to certify issued by the approved maintenance organization, within the limits of its own approval. It names the categories, the aircraft, sometimes the systems, and distinguishes line and base. A technician certified on a type is not certified on the neighboring type from the same manufacturer.

Three conditions are often overlooked with deplorable regularity. The license has a limited validity period and must be renewed. The exercise of privileges requires recent maintenance experience—on the order of six months over the past two years—and this experience is counted by category exercised, not globally. Finally, type mentions are entered after a type course and, when the text requires it, on-the-job training evaluated. A B1 who has not touched an avionics task in two years keeps their category on paper; what they have lost is the basis of their certification.

What remains gray, and what needs to be checked in-house

The boundary blurs where the architecture of recent aircraft contradicts it. A generic computer hosting multiple functions in software partitions no longer belongs to a system: it belongs to a platform. An electric brake, an electromechanical actuator, a mechanical-free flight control shift failures that were hydraulic yesterday toward software. On these fleets, the dual category becomes a real asset, at the cost of two knowledge bases to maintain and two experience windows to feed. The qualification paths preparing an additional category never exempt from the corresponding experience.

Four checks are worth making in your own documentation. Reread the exact wording of your certification: scope, categories, types, line or base, limitations. Identify, in the job cards of your fleet, those whose final test requires interpretation rather than observation—these are your handover points. Check whether the procedures provide for splitting the work order at these points, or if practice leaves a single signature stretched. Finally, check how your recent experience is recorded by category: it is this record, and not the team leader’s memory, that will be used in case of inspection.

For those preparing for a qualification, the question is not which profession is most attractive, but which half of the chain they want to have the right to troubleshoot. Choosing the mechanical category or the avionics category is choosing which side of the measurement you will stand on the day the test fails.

These guidelines describe a mechanism, not a specific case: the applicable text, the authority’s decisions, and the approved documentation of the maintenance organization prevail in all circumstances over this article, and it is the wording of your certification that is valid at the time of signing.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

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