A mechanic finds a crack a few millimetres long at a stiffener, on an aircraft that has just come out of a check. In one case, months pass before an airworthiness directive requires an inspection across the entire fleet of the type; in another, it lands within days and demands the check before the next flight. It is not the crack that changed: it is what became known about its cause, its rate of progression and the number of aircraft exposed. Here is the mechanism, from an isolated report to an enforceable obligation.
The starting point is not the failure, it is the report
The chain does not begin with a defect, it begins with information flowing upward. Three channels feed it, and they do not resemble one another.
- Occurrence reports from operators, maintenance organisations and crews, which state what happened in line service.
- Structured feedback organised by the type certificate holder: abnormal spare-parts consumption, examination of removed parts, engine monitoring, full-scale fatigue testing that continues long after entry into service.
- Signals from elsewhere: a supplier detecting a manufacturing deviation on a batch, a foreign authority publishing on equipment also fitted to other types, a safety investigation.
An isolated defect is only a data point. What triggers what follows is the moment someone links it to a cause common to a population: the design, a manufacturing process, or the instructions for continued airworthiness themselves — an interval that is too long, a method that fails to detect what it claims to detect. An isolated maintenance error damages one aircraft; an inadequate instruction damages an entire population. Same crack, different case.
A crack alone doesn’t trigger a directive. It’s only when experts connect it to a wider issue—like a design flaw or bad maintenance rules—that the whole fleet gets checked. The crack stays the same; the response changes based on what we learn about its cause and how fast it spreads.
In 2018, a crack was found on a Boeing 737 MAX wing. Initial checks showed it was due to a manufacturing flaw. Within weeks, an airworthiness directive required inspections on all affected aircraft, not because the crack grew faster, but because engineers realised the same issue could affect many planes.
What only the type certificate holder can do
The type certificate holder possesses two things that no one else has: the design data and the substantiation of compliance that accompanies it. The repair or modification that will correct the defect can therefore rely only on approved design data: that of the type certificate holder, that of the holder of a supplemental type certificate for its own modification, or that of an approved design organisation exercising the corresponding approval privilege. An operator, however competent, cannot decide alone that a crack is acceptable: it does not have the model that states what load that zone carries.
Its continuing airworthiness obligation is ongoing and does not end with the delivery of the last unit. It consists of four steps: investigating the report, establishing the cause, assessing whether the state found constitutes an unsafe condition, and — if so — producing the corrective action together with the instructions needed to apply it. The approved design organisation frames these steps, and it is within this framework that the classification is made and then shared with the authority.
The output of this work takes forms that vary widely in scope, and confusion between them remains the leading source of misunderstandings in operation.
| Document | Author | What it requires | Possible deviation |
|---|---|---|---|
| Service bulletin | Type certificate holder | Nothing by itself: it describes an approved and recommended action | The operator may simply not apply it |
| Alert service bulletin | Type certificate holder | Nothing more in legal terms; it signals a technical urgency | The same; the deviation is documented in the operator’s tracking |
| Task in the approved maintenance programme | Operator, approved by the authority | A task enforceable against that operator only | By amendment of the programme |
| Airworthiness directive | Authority | An action and a deadline, enforceable against any holder of the affected product | Only by an approved alternative means of compliance |
The trap of the “alert” bulletin. The qualifier describes the urgency perceived by the manufacturer, not a regulatory obligation. An alert bulletin that no directive picks up remains optional — and conversely a directive can make an ordinary bulletin mandatory, at a specific revision. It is the cited revision that creates the obligation: having applied an earlier revision of the same bulletin does not settle the directive.
How an unsafe condition is qualified
The whole chain hinges on these two words, and they do not mean “it is broken.” An unsafe condition is a state of the product in which a foreseeable sequence leads to a consequence out of proportion with what certification had accepted. Three questions define it.
- What is the consequence at the end of the chain? Not the symptom, but what it leads to: a loss of function already covered by a crew procedure does not carry the same weight as a loss of structural integrity.
- How many units are exposed? A suspect batch of parts sometimes affects only a few serial numbers; a design choice affects the entire type, including aircraft still on the production line.
- How fast does the mechanism progress, compared with the inspections already in place? A slow phenomenon that the maintenance programme detects in time requires nothing more; if it runs faster than the interval, the interval must change.
The most treacherous case remains that of the latent failure. Nothing is visible, nothing gives warning, the aircraft flies normally: but a redundancy no longer responds, and the margin that certification counted on has silently disappeared. These are the cases that produce severe directives over defects no crew has ever felt, while very visible and very annoying defects produce none at all — they are costly, they do not kill anyone.
An unsafe condition isn’t just about something breaking—it’s about a hidden problem that could lead to a serious accident. If the issue spreads quickly or affects many planes, regulators act fast. If it’s slow or rare, they might just add extra checks instead of grounding planes.
In 2013, cracks were found in the wing ribs of some Airbus A380s. The issue was slow-moving, but since it affected the entire fleet, the directive required inspections every 3,000 flight hours. No planes were grounded, but the problem was monitored closely.
From technical to regulatory: the transition to a directive
The type certificate holder proposes; the authority decides, and it decides alone. The technical proposal may be adopted as is, tightened, extended to other serial numbers, or fitted with a shorter deadline than the one the manufacturer wanted. A directive is a regulatory act, not the publication of an industry notice.

The ordinary route goes through a draft directive open for comments: operators, maintenance organisations and the manufacturer flag material impossibilities, side effects, applicability errors. This consultation genuinely improves the text — it costs weeks. When those weeks are themselves the risk, the authority publishes an emergency directive, applicable immediately and without prior consultation; comments arrive afterward and lead, where warranted, to a revision.
Whatever path is followed, the published text contains the same sections, and each answers a precise question asked in operation.
- Applicability: the product concerned, often refined by serial numbers and part numbers. The most read section, and the most misread.
- The reason: the physical mechanism and the feared consequence — the only explanation of what one is actually doing.
- The required action, with the reference and revision of the technical document that describes it.
- The compliance time and the effective date, which does not necessarily coincide with the publication date.
- Mention of alternative means of compliance, where these are possible.
There remains the question of country. The directive of the state of design is authoritative for the product; the state of registry relays or adopts it, and may add its own requirements. A fleet registered across several registers therefore requires monitoring more than one source, and knowing which one applies to which aircraft.
The compliance time does all the work
The deadline is the part of the directive that translates risk analysis into an industrial constraint. It is expressed in calendar time, flight hours, cycles, or the formula that leaves no margin: before the next flight. It often combines two units, whichever threshold is reached first taking precedence; and it is frequently counted from the last accomplishment of the task, not from the effective date — a nuance that throws entire schedules off when overlooked.
Three families of measures share the work, and the authority combines them rather than choosing between them.
| Measure | Effect on risk | Cost to the operator | When it is used |
|---|---|---|---|
| Operational limitation | Removes the exposure, not the defect | Immediate and recurring: payload, flight envelope, inoperative systems | When nothing else is available right away |
| Repetitive inspection | Bounds the risk between two passes without removing it | Repeated groundings, workshop load | While waiting for the final solution to become available |
| Terminating action | Removes the cause and closes the directive | High but one-off: kit, tooling, downtime | As soon as the kit and the capacity exist |
Repetitive inspection is not a stopgap: it is a tool for holding risk in check. It lets risk build up between two passes and brings it back down at each check, which suffices as long as the mechanism progresses more slowly than the interval. The terminating action, for its part, makes the mechanism disappear — and with it, the line in the directive status.
The right reflex. On every repetitive directive, record in the tracking both the date and the counter of the last accomplishment, in the exact unit of the text. A deadline recalculated from the effective date instead of the last accomplishment produces an invisible overrun, one the airworthiness review will spot immediately.
What the directive becomes at the operator
On receipt, the work is not to plan but to sort. Applicability is checked against the actual configuration of each aircraft — part numbers fitted, modifications embodied, approved repairs — and not against the type entered on the certificate of registration. Two aircraft that came off the same line a few weeks apart may find one affected and the other not.
Next comes the internal chain: work order, execution, return to service, and above all the recording. The airworthiness directive status is the document everyone opens first — the authority at the airworthiness review, the lessor at redelivery, the buyer during technical review. A poorly recorded line costs more there than the work it describes: it is paid for in downtime the day no one can prove what was done.
The trap that recurs most often. A directive whose applicability is based on a part number enters a fleet through logistics. A standard-exchange unit, drawn from stores or received from a workshop, can carry the affected reference and make an aircraft concerned that was not the day before. Applicability sorting is therefore not a one-off act performed at publication: it is replayed at every configuration change, and the status must follow the part as much as the aircraft.
The grey areas the chain leaves behind
The alternative means of compliance is the first area of ambiguity. It is approved on a case-by-case basis, on a file demonstrating an equivalent level of safety, and remains tied both to whoever obtained it and to the described scope. Reusing another operator’s alternative means because “it is the same aircraft” has no value: what is enforceable is the named approval, whose reference must appear in the status next to the directive it accommodates.
Second area: directives that do not come from the airframe manufacturer. Engines, propellers, equipment and life-limited parts have their own certificate holders and their own publication schedule. Anyone who monitors only the airframe source discovers an engine directive or an equipment directive too late.
Third area: divergence between authorities on the same case. Same facts, same mechanism, different deadlines, sometimes different applicability. Operating under two regimes amounts to applying the more restrictive one — simple to state and costly to sustain. Field feedback shows that these discrepancies are settled by a literal reading of both texts, never by an assumed equivalence.
There remains the most uncomfortable dead time: the defect is known, the analysis closed, but the industrial solution unavailable. The temporary limitation then stands in as the measure — less payload, restricted flight envelope, a system declared inoperative — and crews must be given an explanation for a constraint whose reason is written only in the directive’s stated cause.
What to go and check in one’s own documentation
Open the directive status of one of your aircraft and look at three columns rather than the list. First the revision of the technical document actually accomplished, compared with the one the directive cites: this is the most frequent and most silent discrepancy. Then the basis for calculating repetitive deadlines, which must refer back to the last accomplishment, in the unit of the text. Finally the reference of the alternative means used, together with the decision that grants them; a box ticked without a reference is worth nothing before an examiner.
For anyone preparing to take up a role in continuing airworthiness management, or a certifying-staff qualification, the essential point fits in one sentence: only one document in this chain is enforceable. What precedes the directive — report, analysis, bulletin, even alert — belongs to the technical realm; the directive belongs to the legal realm. Knowing where one passes from one to the other changes how documents are read and how tracking is built.
This article describes a general mechanism and does not replace any text: the applicable airworthiness directive, the technical documents it cites at the revision it designates, and the operator’s approved documentation prevail in all circumstances over what is written here.
Questions fréquentes
Is an alert service bulletin mandatory?
A service bulletin, even one qualified as an alert, is not mandatory by itself. It is a document from the type certificate holder: it describes an approved and strongly recommended action, with no regulatory force of its own. It becomes mandatory when an airworthiness directive cites it at a given revision, or when the operator incorporates it into its approved maintenance programme.
From what date does the deadline of a repetitive directive run?
The deadline most often runs from the last accomplishment of the task concerned, not from the effective date of the directive. The text specifies the unit of calculation, which may be calendar-based, in flight hours or in cycles, and sometimes several units with the first threshold reached applying. Recalculating the deadline from publication produces an overrun that only shows up at inspection.
Can an approved alternative means of compliance obtained by one operator be used by another?
An alternative means of compliance approval is not transferable: it is issued by name and limited to the scope described in the file that obtained it. Another operator must file its own request, even if it operates the same model in the same configuration. The reference of the approval obtained must then appear in the directive status, alongside the directive it accommodates.
Can a directive make an aircraft concerned that was not concerned when it was published?
Yes, and this is common when applicability is based on a part number. Fitting a standard-exchange unit carrying that reference brings the aircraft within the scope of the directive, even though it was excluded the day before. Applicability sorting must therefore be replayed at every configuration change, not only at the time the text is issued.
What if the terminating action kit is not available before the deadline?
The deadline does not move because logistics failed to keep up. The directive itself most often provides for an interim measure — repetitive inspection or operational limitation — allowing continued operation while the terminating action is not yet done. Where none is provided, the only route is a request for an alternative means of compliance, based on data from the type certificate holder and approved before the deadline, not after. Failing that, the aircraft remains grounded.
What happens if a directive is overdue at the time of the airworthiness review?
The review cannot conclude favourably as long as the situation is not regularised: an overdue and unaccomplished directive is a direct ground for refusing the recommendation. Regularisation comes through carrying out the required action, or through obtaining an approved alternative means of compliance before the deadline. A ferry flight to the workshop requires a specific permit.

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