Proportionate Safety Management: What Three Aircraft Let You Trim

A pilot in a cockpit reviewing a safety checklist at dusk

Almost every safety management requirement written in the last twenty years carries the same clause: the system shall be proportionate to the size of the organisation and to the nature and complexity of its activities. Small operators read that sentence as permission to do less. It is not. Proportionality governs the form the system takes — how many documents, how many meetings, how many named people — and it leaves the substance untouched. A three-aircraft operator owes exactly the same hazard identification and the same risk decisions as a fleet of two hundred; it simply cannot afford to describe them in four hundred pages.

Where the proportionality clause comes from

The idea is not a concession extracted by small operators. It is built into the international framework: ICAO Annex 19 requires States to mandate safety management systems and expects those systems to be implemented in a way that suits the organisation, and Doc 9859 spends a good part of its length explaining that a system which is too heavy for its organisation will be performed on paper and nowhere else. The European rules restate it in the management system requirements of Part-ORO for air operators, and in the equivalent management system provisions that now sit in Part-145 and in the continuing airworthiness rules for maintenance and airworthiness management organisations.

The wording matters. The system is proportionate to size and to the nature and complexity of the activity. Those are two different dials, and small operators habitually turn only the first. Three aircraft flying scheduled sectors between two well-equipped airports in daylight is a genuinely simple operation. Three aircraft doing medical evacuation into unprepared strips at night, on demand, with crews who also fly for someone else, is not a simple operation at all — and the fact that there are only three of them buys almost nothing.

Proportionality means adjusting the paperwork and structure of safety systems, not cutting corners on actual safety work. A small operator must still identify hazards and assess risks, but can do so with fewer meetings and documents.

A three-aircraft operator flying scheduled daytime routes between major airports might combine the safety manager role with a line pilot, using a shared folder for hazard tracking. But if the same operator starts nighttime medical evacuations, they must reassess risks and update procedures, even if the fleet size hasn’t changed.

What a three-aircraft operator legitimately gets to shrink

The reductions authorities routinely accept are structural rather than substantive. They are about the machinery, not about the output.

  • Committee structure. The two-tier arrangement of a safety review board and one or more safety action groups collapses into a single periodic safety meeting, chaired by the accountable manager, with the same agenda items and a written record.
  • Named post holders. Roles are combined. The accountable manager may hold an operational post; the safety manager may be a line pilot; the compliance monitoring function may be exercised by one of them or contracted out. Which combinations are acceptable is decided by the competent authority, case by case, on the arrangements proposed.
  • Documentation volume. A single manual can carry the management system rather than a separate safety management manual, an emergency response plan, a compliance monitoring programme and a training plan as four bound documents.
  • Meeting frequency and formality. Fewer scheduled meetings, provided the interval is defined and the record exists.
  • Analytical tooling. A spreadsheet and a shared folder are commonly accepted as the safety database at this scale. What is not acceptable is having no record at all because the number of events felt too small to bother with.

What it never gets to shrink

The core is invariant, and it is worth stating in the negative because that is how the finding is written when it is missed.

Proportionality: the two columns of a small operator’s management system
Element Accepted small-operator form What remains non-negotiable
Accountable manager Also the owner, the chief pilot or a line captain A single identified person with the authority and the budget to accept or refuse a risk
Safety policy One page, signed Signed by the accountable manager, communicated, and consistent with what actually happens on the line
Hazard identification A meeting, a list, a shared file Both reactive and proactive sources; a hazard log that is actually populated between events
Risk assessment A simple matrix agreed with the authority Documented reasoning, an explicit acceptance decision, and a named owner for every mitigation
Occurrence reporting A form, an address, one person collecting Mandatory reporting to the authority within the applicable deadlines, confidential internal reporting, and just culture protection that is written down
Compliance monitoring Combined with another function or contracted to an external auditor Independence from the activity being audited; a programme covering all applicable requirements over a defined cycle
Management of change An item on the safety meeting agenda A change is assessed before it happens, and changes requiring prior approval are not implemented while waiting
Safety training Delivered in-house, possibly by the safety manager All staff, recorded, including contracted personnel where the operator’s system covers them
Emergency response plan Short, with a call-out list Exercised, coordinated with the organisations named in it, and kept current

Two entries in that table are the ones small operators lose findings on. The first is the hazard log that only fills up after something goes wrong: a system fed exclusively by occurrences is a reactive system wearing a proactive label. The second is independence in compliance monitoring — combining roles is permitted, but the person who wrote the procedure and flew the sector cannot be the only person who audits both.

The conflict of interest is designed in, so manage it explicitly

At three aircraft the same six or eight people do everything. The safety manager investigating a rejected takeoff was very likely on the roster that week, may have trained the crew, and reports to an accountable manager who is also the commercial director deciding whether the contract that generated the pressure is renewed. Pretending this is not the case is the single most common failure of small-operator safety management. Naming it and building around it is what a mature small system looks like.

A group of uniformed personnel are gathered around a conference table, using laptops and reviewing documents in a dimly lit office with aircraft visible through the window.
Effective safety management requires collaborative data review and analysis.

The mechanisms are unglamorous and they work.

Role combinations at small scale: what holds and what has to be added
Combination Why it is workable What must be added for it to hold
Accountable manager is also the owner Authority and budget genuinely sit in one place, which is the point of the role A written rule that commercial decisions with a safety dimension go through the risk process, not around it
Safety manager is also a line pilot Credibility on the line and first-hand knowledge of the operation A recusal rule for events the safety manager was involved in, and a named substitute — internal or external
Safety manager is also the compliance monitoring manager Foreseen at small scale, subject to the competent authority accepting the specific arrangement Audits of the safety manager’s own outputs performed by someone else, typically contracted
Compliance monitoring contracted to an external auditor Buys real independence that headcount cannot provide The operator, not the contractor, remains accountable; the programme and the findings must be owned internally
Accountable manager also holds an operational post Common and often unavoidable The clearest possible separation between the accountable decision and the operational one, and a record showing which hat was worn
Nominated person for one discipline also covers another Accepted where competence is demonstrated for both Authority acceptance of the specific arrangement, and a workload assessment that is honest about hours

The trap. A reporting channel that consists of telling the boss. In a company of eight people the safety manager, the chief pilot and the person who decides on contract renewals may be the same individual, and a crew member weighing whether to file a report is weighing it against their employment. If the confidential channel is not genuinely usable — an external mailbox, a paper form in a locked box, an agreed third party — the reporting rate will look excellent and the system will be blind.

A safety system that cannot use statistics

Three aircraft do not generate a data set. Trend charts built on a handful of events per year are noise presented as a curve, and the classic small-operator error is to read a quiet quarter as evidence of good performance. Rate-based indicators need a denominator large enough to mean something, and at this scale it usually is not there. What works instead is a deliberate shift from outcomes to precursors, and from internal data to external data.

Where the information comes from when the fleet is too small for statistics
Source What it detects Limits at this scale
Confidential internal reports Precursors, workarounds, pressure that never became an occurrence Entirely dependent on whether the channel is trusted; a low count proves nothing
Flight data monitoring, where the fleet is in scope Exceedances and stable-approach behaviour, objectively and on every sector Applicability depends on aircraft mass and the applicable operating rules; de-identification is harder when crews are few
Line observation by an experienced peer How procedures are actually flown, and where the manual and the line diverge Observer independence is difficult; consider an external observer
Published sector data and authority safety information Hazards the operator has not yet met but is exposed to Only usable if internal events are classified in a compatible taxonomy
Pooling with comparable operators A denominator large enough to see patterns Requires an agreement on confidentiality and on what is comparable
Findings from audits and from the authority Systemic weaknesses, independent of whether anything went wrong Lagging, infrequent, and easy to close superficially

Classification is the piece most often skipped and the one that pays best. If internal events are coded in a taxonomy compatible with the one the authority and the industry use, a set of six events per year stops being an anecdote and becomes something that can be compared against a sector-wide picture. If they are coded in free text invented in-house, they stay anecdotes forever.

Small operators can’t rely on statistics. Instead, they must focus on precursors (early warning signs) and external data (like industry reports) to spot safety risks before they become serious problems.

A three-aircraft operator flying a Cessna Citation V in Europe might use flight data monitoring to track approach stability, but since they only have three pilots, they must ensure data is de-identified to protect privacy. They might also join a safety data pool with other small operators to compare hazard trends.

Change is the dominant risk at this size

Relative magnitude is the whole point. Adding a fourth aircraft is a thirty-three per cent fleet increase. Winning a contract that shifts the operation from daylight scheduled work to night on-demand work changes the nature and complexity dial, not just the size one. Losing the one engineer who knew the type is a single-point failure with no depth behind it. A large operator absorbs each of these; a three-aircraft operator is reshaped by them.

The management of change process therefore does more work here than anywhere else, and it has two hard edges. Changes are assessed before implementation, not documented afterwards. And changes that require prior approval from the competent authority are not implemented while the application is pending, however commercially inconvenient the wait is. The second is where small operators most often find themselves explaining an unapproved change after the fact.

The right habit. Keep the hazard log and the change log as one working document reviewed at the same meeting. At three aircraft, most new hazards arrive attached to a change — a new destination, a new contract, a new person, a new maintenance arrangement — and separating the two records simply guarantees that one of them is out of date.

The system covers work the operator does not perform

A small operator outsources almost everything: base maintenance to a Part-145 organisation, possibly continuing airworthiness management, training to an approved training organisation, ground handling at every station, sometimes dispatch. Every one of those interfaces sits inside the operator’s management system, and responsibility for the operation does not transfer with the work.

In practice this means the contracts have to say something about safety, not only about price and turnaround. It means the operator needs a way of knowing that a contracted organisation’s own findings and occurrences reach it when they concern its aircraft. And it means the interfaces belong in the hazard identification exercise, because the places where two organisations’ procedures meet are where assumptions go unstated — the handover of a defect, the acceptance of a task not fully completed, the ground handler who has never loaded this type.

What oversight actually looks for

Risk-based oversight rewards operators that can show the reasoning behind their decisions, and it is unimpressed by volume. An inspector at a three-aircraft operator is generally trying to answer four questions: does the accountable manager understand and own the risk picture; does the hazard log contain things nobody has yet been hurt by; can you show a decision where safety was chosen over commercial convenience; and is the reporting rate consistent with the operation as flown.

The last one deserves emphasis, because it inverts the intuition. A small operator reporting almost nothing is not read as safe. It is read as either not flying much or not reporting, and the inspector will find out which. A small operator with a steady flow of low-severity reports, a visible hazard log and short honest risk assessments is the profile that closes an audit quickly. Crews moving between operators of this size compare these arrangements constantly, and the practical detail gets argued out on forums.fl330.com.

The rule under all of this

Proportionality is about the wrapper. It permits one meeting instead of three, one manual instead of four, one person wearing several hats instead of a department, and a spreadsheet instead of a safety information system. It never permits fewer hazards to be identified, a risk to be accepted without a documented decision, an occurrence to go unreported, a change to be made without assessment, or an audit to be signed by the person who did the work. A small system done honestly is a real system. A large system copied from a bigger operator and never used is not, and it fails an audit faster.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

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