The accountable manager is the only post in an aviation organisation defined by what its holder can spend rather than by what its holder knows. Every other management function is described by competence, experience and scope; this one is described by corporate authority over money and people. That difference is not drafting style. It is the entire mechanism, and it explains why some decisions can be pushed down an organisation chart and others come straight back up no matter how carefully the delegation was written.
The definition contains a capability test
Read the wording used across the European regimes and one thing stands out. A maintenance organisation under Part-145 must have an accountable manager with corporate authority for ensuring that all the work required can be financed and carried out to the required standard. An air operator under the organisation requirements must nominate an accountable manager with the authority to ensure that all activities can be financed and carried out in accordance with the applicable requirements. ICAO’s safety management provisions, in Annex 19 and the guidance that supports it, describe an accountable executive with final authority over the operation, control of the human resources and control of the financial resources.
None of that is a job description. It is a test. A person who cannot commit money and cannot move people does not satisfy the definition, whatever the appointment letter says and whatever appears in the exposition or the management system manual. That is a much sharper instrument than most organisations expect, because it means the question an inspector should ask is not “who is the accountable manager?” but “what is the largest unbudgeted sum this person can commit without asking anyone, and who can overrule them?”
The corollary is uncomfortable in a group structure. If the certificate holder’s accountable manager has to obtain a parent company’s agreement for anything that costs real money, the definition is not met in substance, whatever the appointment letter says: the certificate holder has a signature rather than an accountable manager. The authority does not deal with the parent company; it deals with the certificate, and the certificate has one accountable manager on it.
The accountable manager must have real power to spend money and direct people. If they need permission from higher up, they don’t truly meet the role’s requirements.
A small airline with 10 aircraft needs to replace a critical avionics component. The accountable manager must be able to approve the €500,000 purchase without seeking higher approval. If they must ask the parent company, they fail the test.
Accountability and responsibility are not the same word
The two terms are used interchangeably in everyday speech and are strictly distinct here. Responsibility is the duty to perform a task, and it distributes: a nominated person is responsible for flight operations, a maintenance manager for the release of aircraft, a safety manager for running the risk process. Accountability is the obligation to answer for the outcome, and it does not distribute — it accumulates upward and stops at one named individual.
This is why an organisation can be perfectly organised and still fail an audit on this point. Every task has an owner, every owner has a procedure, and nobody can say who answers if the whole arrangement turns out to be under-resourced. That answer is the accountable manager’s, by construction, and no amount of internal delegation changes it.
| Decision | Stays or delegates | Why |
|---|---|---|
| Signing the safety policy | Stays | The policy commits resources; only the person who controls resources can commit them credibly |
| Accepting a risk assessed above the organisation’s tolerability threshold | Stays | Accepting an intolerable-band risk is a decision to keep operating despite the assessment — a commercial act as much as a technical one |
| Deciding the level of resource given to safety and compliance functions | Stays | This is the definition itself, not an application of it |
| Suspending or continuing an operation after a serious event | Stays | Nobody below the accountable manager holds both the safety and the commercial authority needed to make it stick |
| Assessing a specific hazard and proposing mitigations | Delegates | Technical work with a technical owner; the assessment is prepared, not decided, at that level |
| Running the compliance monitoring programme and its audit schedule | Delegates | Must be independent of the activity audited, which is exactly why it is not the accountable manager’s daily work |
| Day-to-day operational control, rostering, maintenance planning | Delegates | Requires competence the accountable manager is not required to hold |
Money is the substance of the job, not a detail of it
The safety management literature tends to describe the accountable manager in terms of leadership and visible commitment. Those matter, but they are the soft edge of a hard requirement. What the rule actually asks for is that a named person be able to answer one question: how did you determine that the resources given to safety are sufficient?
The answers that survive scrutiny are specific. So many hours per week of the safety manager’s time, protected against operational tasking, with the protection written down. A training budget with a line for the recurrent items the risk register generated this year, not last year. Enough staff in continuing airworthiness that a deferred defect gets reviewed on its merits rather than at the end of a shift. A reporting system with someone whose job includes reading what comes in.
The answers that fail are equally recognisable. Resource levels inherited from a previous year with no review. A safety manager who also holds an operational post and whose operational post always wins. Training paid for only when a licence is about to lapse. In each case the organisation has a functioning safety management system on paper and an accountable manager who cannot explain the sizing of any part of it — which is the finding, whatever else the audit turns up.
The trap Appointing the finance director or the chief executive as accountable manager solves the money test and creates a different problem: a post-holder with no aviation background who signs risk acceptances they cannot interrogate. The rule does not require technical competence in the post, which is precisely why the organisation has to build the briefing that makes the signature meaningful.
The accountable manager must prove they’ve allocated enough money and people to safety. Vague answers or inherited budgets won’t pass inspection.
An airline’s safety manager reports that they can only spend 2 hours per week on safety tasks because they’re also handling flight operations. The accountable manager must either free up more time or justify why 2 hours is sufficient – and that justification must be documented.
Who holds what, and who cannot hold it
| Function | Owns | Cannot own |
|---|---|---|
| Accountable manager | Resources, the safety policy, the tolerability criteria, final risk acceptance, the answer given to the authority | The technical judgements themselves — those are prepared elsewhere and must be traceable to their author |
| Nominated persons (flight operations, crew training, ground operations, continuing airworthiness) | Competence and day-to-day conduct of their domain; they must be acceptable to the authority | The resource envelope they operate inside |
| Safety manager | The risk management process, the reporting system, the analysis put in front of the decision-maker | The acceptance decision — proposing and accepting a risk cannot be the same signature |
| Compliance monitoring manager | The audit programme and the independence of the finding | Any activity they audit, which is what independence means in practice |
Small organisations are allowed to combine several of these, and the rules make room for it. What they do not allow is combination by default. Where an authority accepts that one person holds two of these functions, the acceptance is explicit, it rests on the size and complexity of the organisation, and it is revisited when either changes. An operator that grew from six aircraft to eighteen without revisiting its combined post-holders has drifted out of the arrangement it was granted, and nobody will have noticed, because nothing visibly changed on the day it happened.
Risk acceptance cannot be pre-signed
The safety risk management component of any compliant system ends in a decision: the risk is tolerable as it stands, tolerable subject to mitigations, or not tolerable. The first two are decisions about how the organisation will operate; the third is a decision to stop doing something. The threshold that separates them is set by the accountable manager, and once set, the acceptances above it belong to the same person.
What organisations attempt instead is a standing delegation: a matrix stating that risks in a given band may be accepted at director level. This works well and legitimately for the lower bands. It stops working the moment the band in question is the one where the organisation has decided the risk is only barely acceptable, because that is the point where the acceptance is really a statement about the resources not being made available to remove the hazard — and that statement can only be made by the person who controls the resources.
The practical test is worth stating plainly. If the mitigation that would remove the risk is affordable and simply was not funded, the acceptance is a budget decision wearing a safety label, and it belongs at the top. If the mitigation is genuinely unavailable at any price, the acceptance is a technical decision and can sit with the technical owner, provided the reasoning is recorded.
Only the accountable manager can approve risks that are barely acceptable, because that means they’re choosing not to spend money to fix them. Lower-level managers can approve smaller risks, but not the big ones.
An airline identifies a risk of runway overrun at a high-altitude airport. The safety team proposes installing better braking systems (cost: €200,000 per aircraft). If the accountable manager refuses to fund this but still approves the risk, that’s their decision – not a delegate’s.
The board that has to be chaired, and by whom
The two-tier structure recommended by the ICAO guidance and adopted across European operators makes the same point structurally. A safety action group does the work: it is chaired by a manager, it is populated by people who know the operation, and it produces analysis, mitigations and follow-up. A safety review board sits above it, is strategic, meets less often, and is chaired by the accountable manager.
That chairmanship is not ceremonial and it is not delegable in substance, because the review board exists to do exactly the thing only the accountable manager can do: look at the safety performance the organisation is actually achieving, compare it with what it said it would achieve, and decide whether to move resources. A review board chaired by a deputy produces recommendations. A review board chaired by the accountable manager produces decisions, and the difference shows up in the minutes within two meetings.
The right reflex Judge the arrangement by the minutes, not by the chart. Take the last four review board records and count how many produced a change in a resource — money, hours, headcount, equipment. If the answer is none, the board is a reporting forum and the accountability is nominal, whatever the manual says.
Where a delegation stops binding the authority
Internal delegation is a matter between an organisation and its staff. The certificate is a matter between the organisation and the authority, and the authority is not a party to the internal arrangement. That gap produces the effect this whole article turns on: a delegation can be perfectly valid inside the company and simply irrelevant outside it.
The clearest case is contracted work. When an operator contracts continuing airworthiness management, or a maintenance organisation subcontracts a task, the work moves and the accountability does not. The contract governs performance between two parties; the certificate still names one accountable manager, and the authority will ask that person how the contracted activity is controlled, monitored and resourced. “We contracted it out” is an explanation of a method, never an answer to that question.
The same applies to occurrence reporting. The mandatory reporting obligation, the protection regime that goes with it and the just-culture policy that makes the whole thing work are organisational commitments. A just-culture policy signed by a safety manager and unknown to line managers is not a policy; it is a document. The signature that gives it force is the one belonging to the person who can protect a reporter from the consequences of reporting, and that authority sits in exactly one place.
| Symptom | What the audit finds | What it usually indicates |
|---|---|---|
| The accountable manager has never attended a safety review board | Minutes signed by a deputy across several cycles | The strategic loop has been delegated, so nothing changes resource levels |
| Risk acceptances above the threshold are signed by different people | Inconsistent signatures on comparable risks | No threshold is really in force; acceptance follows availability |
| Safety objectives repeat unchanged year on year | Identical wording, no measurement | The objectives were never used to steer anything |
| The accountable manager cannot state the top three risks | An interview answer that describes the process instead of the content | Reporting flows upward and stops before it reaches the decision |
| Resource decisions are traced to a parent company | Approval chains leaving the certificate holder | The definition itself is not met, regardless of the title held |
Changing the person, and what changes with them
A change of accountable manager is not an internal reshuffle. Across the European regimes it is a change the authority has to be told about, and in several of them it requires prior approval, with the incoming holder assessed for acceptability. That assessment is not a formality: it is the moment the authority checks that the capability test above is still satisfied by the new arrangement.

Two things are worth doing on that transition, neither of which is written in a rule. The first is a handover of the open risk acceptances, item by item, because they are the previous holder’s decisions and the new holder inherits them without having made them. The second is an honest statement of what the previous holder could and could not commit, so that the new appointment does not quietly shrink the authority attached to the post while keeping the title. Both are also the moments where an organisation discovers what its safety management system genuinely costs to run — a subject treated in more depth in the management-system material on the FL330 training platform.
Personal exposure beyond the certificate varies enormously between states, and generalising about it is a good way to be wrong. What does not vary is the administrative reality: the authority has one name, it will use it, and it will not accept a delegation as a substitute for it.

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