Suspension of an Approval: The Signals That Almost Always Precede It

A senior inspector in a control room reviews a file under a desk lamp, surrounded by aviation regulations and a monitor displaying a suspended operator's flight schedule.

The letter fits on one page and its subject line is neutral: “intent to limit the operations specifications.” It arrives on a Tuesday, and the accountable manager swears in good faith that nothing happened. He is right about the facts, and wrong about everything else: the file that produced this letter began to be written more than a year earlier, piece by piece, and each of these pieces was notified, signed, acknowledged. A suspension of an approval almost never falls out of the sky. It builds slowly, on a handful of signals that look alike from one operator to the next and that can be named one by one.

A Safeguard Measure, Not a Punishment

The first analytical error is to treat suspension as a penalty. It is not one. A fine, a prosecution, an entry in a professional’s record all look to the past and presuppose an established fault. The suspension of an approval looks to the future: it interrupts an activity because the authority no longer has the conviction that the required level of safety will be maintained tomorrow. It does not require proof of a fault, only a sufficiently substantiated doubt about a capability.

This nature changes everything about how to defend oneself. Facing a penalty, one argues the facts, the legal characterization and the proportionality. Facing a safeguard measure, these arguments miss the target: even won, they do not restore the lost conviction. What restores it is a forward-looking demonstration — here is the cause, here is what removes it, here is how we will know it has been removed. The operator who answers a formal notice with a brief on the merits of the finding has just spent the only time it had left.

Second consequence, a more favourable one: the measure is designed to be lifted. A suspension carries within its own decision the exit door that ends it, and the burden of proving that exit rests on the operator. A revocation, by contrast, carries none. Between the two, the difference is not one of degree but of meaning: one assumes an organisation can be restored, the other that it can no longer be. The whole stake of the period that precedes it is to stay on the right side of that assumption.

The trap. Contesting the grading of a finding stops the clock inside the operator’s head, never inside the authority’s file. Contestation and correction are two parallel paths: the first is argued, the second runs on its own deadline. Whoever waits for the outcome of the first before starting the second reaches the deadline without a corrective action, and turns a disputable grading disagreement into an unclosed finding, which is no longer open to discussion.

Suspension is not a punishment but a safety measure. It happens when authorities doubt an operator can maintain safety, not because of proven faults. The key is to show you’ve fixed the real problems, not just argue about the findings.

An airline operating Airbus A320s on a 2,500m runway at 30°C gets repeated findings on weight and balance errors. Instead of just training staff, they redesign their dispatch process, add automated checks, and prove it works. The authority lifts the suspension because they fixed the root cause, not just the symptoms.

The Typical Trajectory, and the Order in Which It Plays Out

Suspension files resemble one another because the deterioration almost always follows the same order. It begins with an erosion of resources that nobody classifies as a safety problem: a postholder who leaves and is replaced by a stand-in who does not give up their previous role, an internal audit cycle postponed by a quarter because the season is busy, a compliance monitoring function that loses its administrative support. At this stage, no finding, no correspondence, no indicator in the red. Yet this is exactly where the trajectory begins.

Next comes repetition. The same deviation reappears under different labels — onboard documentation, application of the minimum equipment list, entry of the technical log — and each occurrence receives the same correction: a reminder of the instruction to the staff concerned. The corrective action register fills up with closed lines, and the deviation returns. Nobody lied: the cause was simply never sought, because seeking it would have pointed to a workload, a staffing level or a commercial trade-off that the person writing the finding has no power to change.

The third phase is the one that decides everything. Detection reverses: external sources — ramp inspections, occurrence reports, charterer audits, authority sampling — find more than the internal audit does. The authority never puts it this way, but this is the moment it stops believing the picture the operator gives of itself. Everything that follows flows from this mechanically: the granted deadlines shorten, requested evidence replaces the commitments accepted until then, and sampling stops being random and starts targeting exactly the areas where the operator has declared itself compliant.

The fourth phase is administrative. The authority substitutes itself for the failing management system: it sets the topics, the deadlines and the format of the response itself. The operator still works, still flies, but it no longer writes its own plan. It is at this stage that most crews start to notice something, several quarters behind the file.

The crossing point between what opens and what closesA two-curve chart on a time axis. A solid, decreasing curve represents the number of findings closed within the agreed deadline; a dashed, increasing curve represents the number of open, unclosed findings. The two cross at two-thirds of the axis. Beyond this tipping point, a shaded band signals the drift zone, where the backlog grows faster than processing capacity.number of findingsfindings closed on timeopen, unclosed findingstipping pointtimedrift zone
The decisive signal is not the number of findings, it is the moment when fewer are closed than are opened. Before the crossing, a high backlog can still be read as an organisation that is searching. After it, the same curve reads as an organisation overwhelmed, and it is this reading that triggers what follows.

The Signals, One by One

None of these signals is spectacular, and that is precisely why they go unnoticed. Taken in isolation, each is explained by a circumstance, and the explanation is often true. It is their coexistence that builds the file: the authority reads them together because its own information system files them under the same heading, whereas the operator experiences them separately, in departments that do not talk to one another.

Six early warning signals, how the authority reads them, and what extinguishes them
Observable signal What the authority deduces from it What extinguishes it
A level 2 finding extended for a second time The root cause analysis was never carried out; the deadline is being used to buy time A written cause that also explains neighbouring findings, and a dated action that removes it
The same deviation picked up by two sources that do not talk to each other: ramp inspection, charterer audit, occurrence report Internal detection is not working; the operator learns of its deviations from the outside Internal sampling built on operational data, not on the audit calendar
An internal audit cycle that produces only formal deviations The compliance monitoring function has neither the resources nor the independence to look further An audit plan arbitrated and signed by the accountable manager, with dedicated time and unfiltered access
A postholder position held on an interim basis for more than a few months The structure accepted at the time of issue no longer exists as such A filled and notified appointment, or a voluntary reduction of scope until the position is filled
Maintenance or training deadlines routinely handled through tolerance The margin is no longer a reserve but a production resource A deadline tracking system that alerts before the due date and makes margin consumption visible
Correspondence that is only answered after a follow-up reminder The operator no longer has the resources to maintain its own representation before the authority A single point of contact, and an internal response deadline shorter than the one requested

The right-hand column deserves to be read on its own: none of the responses that extinguish a signal is a document. They are management decisions — time, a position, access, a scope. That is what makes these signals hard to handle internally, and easy to read from the outside.

The File Changes Tone Before It Changes Nature

Official correspondence is a free, under-used measuring instrument. Well before the first mention of a measure, the register of language changes, and it changes in a stable order. One moves from “we invite you to” to “you are requested to,” then to “it is incumbent upon you to.” The deadline stops being a duration and becomes a date. The addressee stops being a department and becomes the accountable manager, by name. Copies widen towards the level above. And the phrase “failing which” appears, followed by a consequence.

The decisive milestone bears a neutral name: the opening of the adversarial procedure, that is, the formal invitation to submit observations before a decision is taken. This is not a threat, it is a right, and it must be exercised seriously. But its opening means that the decision is already being drafted and that the administration considers it has gathered enough to found it. From this point on, producing an action plan is no longer enough: only proof of an action already carried out and already verified counts.

The correspondence timeline and its zone of reversibilityHorizontal timeline of five successive milestones: finding notified, action plan agreed, follow-up and interview, formal notice, opening of the adversarial procedure. Below the timeline, a shaded band extends from the first milestone to the formal notice: this is the interval where correction alone still suffices. A dashed vertical line closes this band just after the formal notice and carries the label of the practical point of no return; to the right, the decision is under way.findingnotifiedaction planagreedfollow-upand interviewformalnoticeadversarialproceduretimecorrection alone still sufficesdecision under waypractical point of no return
The authority’s register of language shifts before its decision, and it shifts in a stable order. Each milestone can be spotted by a word: an invitation, then a dated deadline, then the phrase “failing which.” Past the formal notice, an action plan no longer substitutes for completed proof.

The right reflex. Keep a single register of correspondence with the authority, maintained by one person, recording for each item the date of arrival, the verb used, the requested deadline and the actual date of the response. Reviewed every quarter, it reveals the slope before it becomes visible: three follow-up reminders in six months say more about the trajectory than the content of any one of them.

The Three Points of No Return

A trajectory remains reversible as long as it has not crossed any of these three thresholds. They have nothing formal about them and appear in no text: they are points beyond which the usual arguments stop working.

  • The finding that concerns detection itself. As long as a deviation concerns an operation, the operator can promise to correct it and be taken at its word, because there still exists, in-house, a body supposed to verify that promise. As soon as the deviation concerns the compliance monitoring function, the safety management system, or the independence of the internal auditor, the promise loses all value: the one who should guarantee the correction is the one being called into question. The operator is then judged on measured results, never again on plans.
  • The personal commitment of the accountable manager, not honoured. Their signature at the bottom of an action plan does not commit a department, it commits a natural person whom the authority has accepted by name and whose financial and hierarchical authority it verified at the time of issue. A missed deadline on a plan signed by their own hand is therefore not read as a delay: it is read as the absence of that person’s real authority over resources, that is, as a deficiency affecting one of the very conditions for issuing the certificate.
  • The loss of a supporting element. Insurance cover, the continuing airworthiness management organisation, the financial condition, a postholder position left vacant on a lasting basis: these elements are not safety findings, they are conditions for the existence of the certificate itself. Their absence is objective, immediately verifiable, and is addressed by no root-cause analysis whatsoever — only by restoration. This is the fastest route to a suspension, the only one that can conclude very quickly, and the one where negotiation has no grip. The financial condition deserves a separate mention, because it does not bear on the same title as the others: within the European area, it conditions the operating licence, that is, the economic title that accompanies the technical certificate. An operator can therefore be irreproachable on its findings and see its activity stopped through the other door, on a review of its ability to honour its commitments — a chain of events that safety action plans never address, since it does not fall within their remit.

Narrowing Before Extinction

An authority that suspended an entire certificate outright would expose itself to the charge of disproportion: a safeguard measure is not meant to be broader than the risk it addresses. In practice, this produces an orderly erosion. Special approvals go first, because they are detachable and each rests on a dated demonstration that can be declared out of date: low-visibility operations, extended diversion time, performance-based navigation, dangerous goods transport. Next come restrictions on fleet, geographic area, or type of operation. Suspension of the certificate itself comes last.

This sequencing produces a consequence that regulatory tables do not show: the operator dies commercially before dying administratively. Losing the low-visibility approval at the start of winter on a northern network, or the extended diversion time on a transoceanic route, does not merely trim the programme at the margin: it makes it untenable. The viability threshold is crossed during the restriction phase, while the certificate is still valid and, legally, nothing has yet been lost.

The scope narrows before it is extinguishedFour horizontal bars of decreasing length, stacked from top to bottom, represent the extent of the authorised scope at four successive moments: certificate issued, special approvals frozen, fleet and areas restricted, suspension. A dashed vertical line marks, for a given operator, the minimum scope below which its programme no longer holds. This line is crossed as early as the restriction stage, that is, before the suspension itself.certificate issuedapprovals frozenfleet restrictedsuspensionminimum viable scopeextent of the authorised scope
Suspension arrives after commercial death, not before. Special approvals go first because they are detachable; an operator’s programme, meanwhile, stops being tenable well before the certificate itself is affected.

Hence a counter-intuitive move, and yet one of the most effective: proposing the restriction oneself before it is imposed. An operator that writes to the authority to freeze a special approval, stating the date of review and the criterion for resumption, loses exactly the same activity — but it loses it on a file it still controls, and along the way it demonstrates again the one thing the authority is trying to verify: that it knows where its limits lie.

Two Systems, Two Ways Out

The two major systems arrive at the same result by paths that share neither the same timetable nor the same balance point between execution and appeal. The practical difference does not lie in substance — on both sides, the measure looks to the future and is lifted upon demonstration — but in the moment it produces its effects, and therefore in what remains to be operated during the dispute.

Suspension of an operator’s certificate: two legal architectures for the same result
Point of comparison European area US federal system
Nature of the act Reasoned decision by the competent authority of the State that issued the certificate Written order from the federal aviation administration, notified to the holder
Most frequent formal trigger Level 1 finding, or level 2 finding not closed within the agreed deadline Deviation taken out of handling via the compliance track and switched to enforcement action
Right to be heard Prior adversarial procedure, except where safety requires immediate effect Prior exchanges and an informal conference, except for an order issued as an emergency
Effect of an appeal Depending on the State, judicial appeal generally does not automatically suspend the decision: a separate application for suspension of the decision must be made Appeal before the national transportation safety board in principle suspends the execution of an ordinary order, but has no effect on an order issued as an emergency
Granularity of the measure Adjustable approval by approval within the operations specifications Also adjustable by specification, up to revocation of the certificate
Condition for lifting Verified demonstration of compliance, most often through an on-site visit before restoration Term reached, or demonstration accepted where lifting is subject to a condition

The line that matters for an international operator is the fourth. Where the appeal protects operations for the duration of the proceedings, contesting makes sense; where it does not, contesting without first applying for suspension of the decision amounts to winning a case over a business that has been shut down. And in both systems, a measure taken as an emergency escapes this protection: that is the price of its preventive nature.

What Remains Playable Once the Trajectory Is Under Way

Four moves produce a measurable effect on how the file develops, and only one of them really costs money.

  • Changing the scale of the cause. Stop treating findings one by one and produce a single, written analysis that also explains neighbouring findings and names what makes them possible: a workload, a staffing level, an interface between two departments, a trade-off owned by management. A cause that implies no management decision is not a cause, it is a rewording of the deviation.
  • Renegotiating the deadline before it expires. A request for an extension filed before the deadline, accompanied by the status of progress and the root-cause analysis, reads as proof of control. The same request filed after the deadline is an additional finding, and the first in a series that can no longer be caught up. The date matters more than the content.
  • Bringing in an outside view and handing over its report in full. An external audit transmitted to the authority without redacting what it found restores more credit than ten pages of commitments. The cost is real; it bears no comparison with that of a month of grounding, and it buys what the operator can no longer produce on its own: a credible finding.
  • Giving each action an owner, a date and a criterion. A corrective action with no named owner, no deadline, and no way to verify that it produced its effect is not an action: the inspector reads it as an intention, and an intention closes nothing.

The trap. The most common correction — adding a procedure to the operations manual and issuing a memo — is also the one that worsens the file. It adds a requirement to a system that was already not keeping the ones it had, and the next finding will bear on the new procedure, this time with written proof that the operator knows the subject.

The right reflex. Before sending a response to the authority, have it proofread by someone who does not work in the field concerned, with a single instruction: circle every sentence that promises without dating, and every cause that is merely a rewording of the deviation. What remains circled is exactly what the inspector will flag.

What to Go and Check in One’s Own Documentation

Three checks fit within an hour and can be done without alerting anyone. The first: who signs, according to the manual, the responses addressed to the authority, and whether this person has the power to commit the resources they promise. When the signature and the power sit with two different people, every response is a commitment made on credit.

A man in a suit writes in a notebook beside a laptop with a spreadsheet.
Documentation is critical when approvals are at risk.

The second: open ten closed lines of the corrective action register at random and read the “cause” field. If it contains the deviation reworded instead of what made it possible, the root-cause handling function does not exist, whatever the number of closed lines. The third: verify that the deadlines entered in this register are indeed the ones agreed with the authority, and not more comfortable internal dates copied in good faith.

There remains a grey area that few pieces of documentation address: the exact status of a frozen approval. Depending on the State and the case, its resumption goes through a simple notification, a new demonstration, or an application processed as a first-time application, with the corresponding time limits. The question is usefully asked before the freeze, never after. And for someone preparing to take up a post — designated postholder, internal auditor, a commander joining a company they do not know — it arises differently: read the operations specifications in force, compare them with those of two or three years ago, and ask what has disappeared between the two versions. A missing line tells a story that nobody will volunteer at interview.

The text applicable in the operator’s State, the individual decisions of its authority, and its own approved documentation prevail over this article, which describes a mechanism and not a specific case.

Questions fréquentes

Do a suspension and a revocation follow the same procedure?

Both are decisions by the same authority and follow the same preliminary formalities, but they do not have the same purpose. Suspension interrupts the exercise of the certificate while leaving open the possibility of restoration, and the decision generally states what must be demonstrated to lift it. Revocation extinguishes the certificate: resuming activity then requires a new application processed from scratch, with the timelines and cost of a first-time certification.

Can operations continue during an appeal against the decision?

This depends entirely on the legal system and on whether the measure is urgent or not. In the US federal system, an appeal against an ordinary order in principle suspends its execution, whereas an order issued as an emergency takes effect immediately despite the appeal. In most European States, judicial appeal is not automatically suspensive: a separate and prompt application must be made for suspension of the decision, failing which operations stop during the proceedings.

How many findings does it take to trigger a suspension?

The question is poorly framed, because no such counter exists. What triggers a measure is a level 1 finding, or a finding not closed within the agreed deadline, or a demonstration that the internal detection function no longer works. An operator can carry a large backlog without worrying its authority if it closes what it opens, and an operator with very few findings can tip over on a single deviation if it touches the management system.

Is a voluntary self-restriction held against the operator?

On the contrary, it is one of the few moves that improve the file, provided it is in writing, dated, and accompanied by the criterion for resumption. It demonstrates that the operator knows its own limits and is able to step back before reaching them, which is exactly the capability oversight is trying to verify. It also has a practical effect: resumption of an approval frozen voluntarily is generally processed more simply than one revoked by decision.

What happens to crew qualifications during a suspension?

Licences and type ratings are personal and are not affected by the measure, which strikes the operator, not the flight crew. What deteriorates are the elements tied to activity: the recent experience required to carry passengers, which relies on take-offs and landings performed in the last ninety days, then the checks and line adaptation specific to the operator. A resumption after several weeks of grounding therefore requires a return-to-line plan, which must be prepared during the suspension, not after it is lifted.

What actually makes it possible to obtain the lifting of a suspension?

A verified demonstration, almost always on site, that the identified cause has disappeared and that the system is now able to detect it on its own. Written commitments are not enough at this stage: the authority expects data generated after the correction, an internal audit cycle that has actually found the deviation before it does, and a trail of management decisions that freed up the resources. Lifting frequently comes with a reduced scope and tightened oversight for several months.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

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