Operations Manual Amendment: Prior Approval or Simple Notification

A flight operations manager and colleague review a takeoff weight calculation on a tablet and printed manual in a dimly lit office at dusk, with aircraft visible outside

The Part B amendment went out to the tablets on Tuesday evening: a new method for calculating takeoff weight on a contaminated runway, with a noticeably higher payload as a result. The approval arrives several weeks later, with a reservation on one of the scenarios. In between, a large number of flight preparations applied a method the approved documentation did not contain, and the corrected version must now catch up with the first one across a fleet of tablets, two translations, and the backup copies. The question had seemed administrative: should they have waited for the approval?

It Is Not the Manual That Is Approved

The binder itself has no regulatory status; its contents do, and not the same one from one paragraph to the next. A single page may carry, side by side, a table of operating minima, which falls under approval, and a reminder of good practice, which does not. Status is read at the level of the content, not the binding.

An operator unable to state, chapter by chapter, what is approved and what is accepted cannot sort its amendments. It then commits one of two symmetrical errors: it submits everything, and a typo correction waits for weeks; or it submits almost nothing, and builds up a liability that will surface at the first audit.

The division into four parts — general, aircraft operation, routes and aerodromes, training — does not map onto this sorting. The most volatile of them, routes and aerodromes, mixes documentary data with elements that bear on the conditions of use. Hence the uselessness of a list of effective pages that would carry only the revision number: it must carry the applicable regime.

Three Regimes, Not Two

Everyday vocabulary opposes “approved” to “accepted,” as if the sorting were binary. Three pathways coexist, and it is the second one that makes the difference between a smoothly running documentation department and a suffocated one.

The first is explicit prior approval: the authority rules by a dated act before any entry into force. The second is the agreed amendment procedure, or indirect approval: the authority has approved, once and for all, a mechanism that delegates to the operator the entry into force of a defined class of changes. It is not the amendment that is approved, it is the process. The third is notification: the operator amends, applies, transmits a copy; the authority retains the right to react downstream.

Sorting an Amendment by Its RegimeDecision sequence. A proposed amendment arrives at a first question: does it concern content subject to approval? If not, it is notified to the authority and applies. If yes, a second question asks whether the agreed amendment procedure covers it. If yes, the operator distributes it and transmits the file. If no, it must wait for written approval before any distribution.AmendmentContentapproved?Procedureagreed?Distributeand transmitWait forwritten approvalNotifyand applyyesyesnono
Two questions are enough to route any amendment. The first concerns the status of the content affected, the second the scope of the agreed procedure. Any uncertain answer is treated as a “no”: it is the only branch that never creates an unapproved version.
The Three Amendment Regimes and What Sets Them Apart
Criterion Prior approval Agreed procedure Notification
Subject of the agreement the amendment itself the process, granted once and for all no agreement; the authority is informed
Who puts into force the operator, after the authority’s act the signatory named in the procedure the operator
Time before application that of the review process, not controlled the one the procedure itself sets immediate
Content concerned limitations, minima, training and checking, minimum equipment list approved content but explicitly delegated, within a closed scope description, organization, information, editorial
Evidence to keep the authority’s dated act the eligibility form and the transmission the transmission and its acknowledgment
Effect of the authority’s silence none: without an act, nothing applies not applicable: the agreement has already been given the amendment stands, subject to a reaction

The bottom row is the one most often forgotten. Silence only counts as agreement if a written mechanism gives it that value, with a deadline and a scope — in other words, only if one is already within the second regime.

There are three ways to update an operations manual: full approval (slowest), a pre-approved process (faster), or simple notification (fastest). The key is knowing which one applies to each change. If you use the wrong one, you might fly with unapproved procedures until the authority catches it.

An airline updates its takeoff performance calculations for a Boeing 737 on a wet runway. The new method allows 500 kg more payload. If they distribute this change before approval, flights use the new method for weeks. Later, the authority approves it with a reservation (only valid above 15°C). Now, all flights using the old method below 15°C must be rechecked.

The Agreed Procedure Is a Contract, Not a Convenience

It is often presented internally as a relaxation obtained from the authority. It is the opposite: a commitment to method, more demanding than a case-by-case submission, whose value lies solely in removing the waiting time.

A usable procedure designates its scope by subject or by chapter, never by exclusion — “everything that is not subject to approval” is not a scope, it is an open door. It states negative eligibility criteria: no reduction of an existing margin, no effect on approved content located elsewhere, no consequence for training. It names the signatory and their deputy, sets the deadline and the transmission channel, and describes the conditions under which the authority suspends it.

Two points regularly fall through the cracks. The first: the agreed procedure is itself approved content. It is not expanded by internal decision, and a scope broadened by usage — “aerodrome data sheets always go through this” — amounts to applying a regime that no one has granted. The second: the delegation covers entry into force, not responsibility for the substance. The amendment will be examined at the same level of scrutiny at the first inspection visit, except that it will already have been applied.

The size of the organization changes the real value of the procedure. In a well-staffed documentation department, the drafter proposes and a separate signatory qualifies eligibility: the filter exists because the two people do not share the same interest in concluding quickly. Where the same manager writes the amendment, fills in the eligibility form, and signs off the entry into force, the procedure no longer filters anything — it converts a review period into self-review. The remedy is not to create a new position: it is to name the deputy in another function, operations or training depending on the subject affected, and to give them the right to refer back to prior approval without having to justify it.

The right reflex: draft the eligibility form before the text of the amendment. A form that must demonstrate, once the drafting is complete, that nothing approved is affected is always written to reach a conclusion. Prepared upstream, it reveals the change’s true scope while it is still free to narrow it.

Three Dates, Only One Governs Onboard

An amendment carries three dates that everyday conversation confuses. Approval is set by the authority. Publication, set by the operator, only means the version is available. Effect, also set by the operator within the limits of the other two, is the only one that answers the question “what governs on this flight.”

Three Dates Carried by the Same Amendment
Date Who sets it What it proves What it does not prove
Approval the authority that the content is acceptable that anyone on board is aware of it
Publication the operator that the version is available that it is applicable
Effect the operator, bounded by the other two what governs in flight that day that the previous version has stopped circulating

The most widespread mistake is to make publication and effect coincide. On tablets, synchronization is almost instantaneous; awareness is not. A crew on a long rotation or on leave discovers the amendment after the fact, and a few calendar days have been traded for a risk of inconsistent application.

The opposite excess also exists. An effective date set too far out keeps alive a version everyone knows is outdated: informed crews anticipate it, others do not, and one ends up with exactly what one meant to avoid — two practices for a single text.

The Divergence Window

Distributing before approval does not create an administrative problem: it creates a period during which two versions are in service. The important word is period — it has a beginning, an end, and operational content.

Five men in military uniforms discuss documents and a tablet in a control room.
Military personnel review operational changes, ensuring compliance with updated protocols.
Documentation Divergence WindowTwo overlaid timelines. On the first, approval precedes distribution: the effective date opens a period in which only one version is in service. On the second, distribution precedes approval: between the two markers a hatched band opens during which two versions circulate, one applied on board, the other still under review.Approval before distributionfilingapprovaleffectsingle versionDistribution before approvalfilingdistributionapprovaltwo versions in servicetime
Divergence is not an instant, it is a duration one chooses. At the top, the gap between approval and effect serves familiarization. At the bottom, the same band width becomes a zone where applied documentation and approved documentation no longer coincide.

This window is asymmetric, and that is what makes it costly. Distribution pushes: one send, one synchronization, done. Withdrawal must reach, one by one, every place where the first version has settled — backup copies, translations, the cabin safety manual, printed quick-reference cards and lists, handling agents and training organizations that copied the passage.

Distribution Is Fast, Withdrawal Is NotTwo curves start from the origin. On the vertical axis, the share of recipients aligned on the correct version; on the horizontal axis, time. The solid distribution curve rises almost vertically and plateaus very quickly. The dashed curve for withdrawing an already distributed version rises slowly and only approaches the ceiling near the end of the chart, leaving a persistent gap between the two.share of recipients up to datetimeallhalfdistributionactual withdrawalpersistent gap
A version pushes out, it does not recall itself. The solid curve describes distribution, nearly immediate; the dashed one, the catch-up of a version that has already gone out. The gap between the two is the tail, and it is that tail that must be budgeted for before distributing.

The operational content of the window is the serious point: flights are conducted during it using a non-approved method. If the authority subsequently approves it unchanged, a procedural gap remains, awkward but bounded. If it approves with a reservation, the affected flights must be revisited. A partial refusal is, moreover, harder to handle than a complete one: it produces a third version, which must be explained to crews already trained on the second.

The trap: believing that an amendment can be withdrawn the way it is distributed. The withdrawal message reaches those who read their messages, that is, those who already had the correct version. Those who printed it, copied it into a quick-reference card, or translated it for their base remain on the distributed version. Anyone who has gone through this exercise once stops opening the window to save a few weeks on the calendar.

The Safety Exception, and Its Counterpart

There is a path for immediate application when safety requires it: publish without waiting, requesting approval in parallel. It is legitimate and narrow. Three conditions make it a defensible use: the safety rationale is written before distribution and not reconstructed afterward; the request goes out before or together with distribution; the change remains reversible, without a training program having been modified in the meantime.

The drift is easy to recognize. A change that opens up an operation or eases a constraint is not a safety change, even if one can find a safety argument for it. The test: in the other direction — a tightening — would it have been judged urgent enough to be distributed that same evening?

A Temporary Bulletin Is Not an Amendment Pathway

Crew notice, operational bulletin, temporary instruction: these tools are legitimate for carrying information with a bounded effect, for the duration of runway works, say. They stop being legitimate as soon as they durably modify the manual, and the tipping point occurs without anyone deciding it.

Four signs betray it: the bulletin is renewed a second time; it is cited in a checklist; it contradicts a paragraph of the manual instead of complementing it; it has no end date. The last is the most reliable. An operator whose library of active bulletins exceeds what a crew can hold in mind has moved part of its manual outside the manual, without approval or traceability.

The right reflex: every bulletin is born with two mandatory fields — its expiry date and the address of the chapter it will amend. The second turns a stock that accumulates into a queue that empties, and makes visible the bulletin that should have become an amendment long ago.

The Cascading Effect

An isolated amendment does not exist. A change to Part B is checked first against the approved flight manual: the operator’s documentation may be more restrictive, never more permissive, and an amendment that gains margin over the manufacturer’s data is unacceptable. It is then checked against the minimum equipment list, the operations specifications, the training programs, derived cabin documents, and the translations.

An internal contradiction within the manual is the easiest finding to identify: it requires no expertise, only reading two pages side by side. This is why the impact matrix — the documents examined and the outcome of each review — is often the first document an inspector asks for, ahead of the text of the amendment.

An operator answerable to several authorities — aircraft registered in another State, wet-leased aircraft, activity conducted under a second certificate — finds the same paragraph falling under two regimes at once, because it is the approval that attaches to the certificate, not to the text. Sorting must then be redone authority by authority, and the common part aligns with the more constraining of the two pathways, even if that means losing the benefit of the agreed procedure where it existed. The reverse arrangement — applying each authority’s own regime to a shared text — amounts to keeping alive two versions of a manual bearing the same revision number, exactly what the list of effective pages is supposed to make impossible.

What to Go and Check at Home

Four checks give an honest picture in a single morning. Go back over the last five amendments and find, for each, the claimed regime and its evidence. Compare the written scope of the agreed procedure against what actually passes through it. Count the active bulletins and identify the ones that have been renewed. Finally, ask three crews where they read the effective date: if the answer varies, that date does not govern, it is décor.

One gray area remains that no one settles in writing: the threshold beyond which a rewording becomes a substantive change. Rewriting a procedure “to clarify it” changes how it will be applied, and a clarification that changes a crew’s behavior is an amendment, whatever the number of words touched. The only safeguard is to have every rewording reviewed by someone whose job is to apply it.

For anyone preparing for a type rating, a nominated post holder role, or an interview, three questions suffice: which regime applies to the chapter you have just cited, who holds the entry-into-force signature at your organization, and where the effective date is read on board. Concrete cases are discussed on the FL330 forums; preparation for documentation and management functions is on the training side.

This article describes documentation management mechanisms and does not replace any official source. The text applicable in the State of issue of the certificate, the operations specifications, the amendment procedure accepted by the competent authority, and the operator’s approved documentation prevail over what is written here.

Questions fréquentes

Can an amendment be applied if the authority does not respond within the announced deadline?

No, unless a written mechanism gives silence that value, with a defined scope and deadline. Under the prior approval regime, the absence of a response is not a response: the previous content remains the one that governs, and an amendment applied without an act is an unapproved amendment. The proper course of action is to follow up in writing and keep a record of that follow-up, which documents the operator’s diligence should the delay become an issue.

Does correcting a typo go through the approval circuit?

A purely editorial correction falls under notification, provided it changes neither a figure, nor a condition, nor the scope of a sentence. The practical test is to ask whether a crew would apply the procedure differently after the correction. If the answer is yes, it is no longer a typo but a substantive change, and the applicable regime is that of the content affected.

What should be done when it is discovered that an amendment was distributed without the required agreement?

The first step is to determine whether the distributed practice is more restrictive or more permissive than the approved content. If more restrictive, it can generally remain in force while regularization proceeds, since it does not create a safety gap. If more permissive, it must be suspended immediately and the approved content restored, even before opening the regularization file. In both cases, the deviation is reported internally and handled as a finding, with a review of the flights conducted during the period.

Can the agreed amendment procedure be withdrawn by the authority?

Yes, and that is one of the conditions of its existence. It rests on the trust granted to a process; a series of misqualified amendments, an overrun scope, or a faulty transmission justify its suspension. The operator then reverts to the prior approval regime for all content concerned, which mechanically lengthens all its publication timelines and is felt immediately in operations.

Must a temporary operational bulletin be transmitted to the authority?

The answer depends on the content it affects, never on its title. A bulletin that merely relays information with a limited duration falls under internal information. A bulletin that modifies a procedure, a limitation, or a calculation method is a disguised amendment and follows the regime of the content it modifies, transmission included. The sorting rule is the same as for an amendment: it is not the form of the medium that decides, it is the status of the content affected.

How much time should be left between publication and the effective date?

No universal deadline applies, but it must cover the longest activity cycle of the operation concerned, including long rotations and leave periods. An amendment affecting a procedure applied in flight requires more than an organizational amendment, since it calls for familiarization and sometimes a briefing session. The chosen deadline is justified in the amendment file, which is preferable to defending it after an application deviation.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

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