Gold Standard Doesn't Have to Mean Gold-Plated
What would better general aviation look like if resources were unlimited — and how much of it could we build anyway?
Imagine two regional operators introducing broadly similar changes at about the same time.
The first has resources. There is a project manager assigned to the change. The HOTC has protected time away from normal line duties. Several instructors are involved. There is specialist technical support, a structured management-of-change process, formal implementation meetings and enough staffing that the existing operation does not have to absorb every hour of project work.
Before commencement, procedures are tested. Instructors are standardised. Training records are reviewed. Normal operations are observed. The organisation has enough people to challenge assumptions before they turn into operating practice.
After implementation, somebody is specifically responsible for looking at what happens next. The first week is reviewed. Then the first month. Training feedback is examined alongside safety reports and operational performance. If something does not work as expected, there is capacity to change it.
It sounds excellent. And, given unlimited resources, I would want most of it.
Now imagine the second operator.
Six or seven pilots. A small management team. The HOFO and HOTC are both still flying the line. One of the instructors is also covering operational duties. The person managing the project is probably managing three other things at the same time. Training has to fit around revenue flying. Maintenance support is external. There is no dedicated standards department, no analyst waiting to interrogate training data and certainly nobody whose only job for the next eight weeks is implementation assurance.
The first version of the story can make the second operator look immediately disadvantaged.
Perhaps it is.
But I do not think the conclusion should be that good systems belong to organisations that can afford more people.
Because if we strip away the infrastructure around the first operator and ask what actually made the system good, a surprising amount of it remains available to the second.
The mechanisms may need to change. The thinking does not.
If resources really were unlimited
It is worth starting with the ideal rather than lowering the expectation too early.
If I could design a GA operation without worrying about time, people or cost, I would want clear competency frameworks for every safety-critical role. I would want pilots to know what good performance looks like at each stage of development rather than simply accumulating hours and completed events. I would want instructors who are excellent teachers and who are regularly calibrated with one another.
I would want technical skills developed deliberately, then integrated with judgement, workload management, threat and error management and decision-making through well-designed scenarios. I would want recurrent training informed by what the operation is actually seeing rather than repeating the same collection of exercises indefinitely.
I would want normal line operations observed occasionally, because a proficiency check tells us something different from watching a normal Tuesday afternoon sector. I would want safety reports, training outcomes, checking trends, instructor feedback and operational experience to talk to each other.
I would want SOPs tested with the people expected to use them before they become the standard. I would want significant changes treated as organisational changes rather than document projects. I would want enough depth in the organisation that the entire capability did not live inside one particularly experienced person's head.
And after introducing something new, I would want someone to look back and ask:
Did it actually work the way we thought it would?
None of that feels particularly controversial. The harder question is what happens when we start taking the resources away.
Take away the standards department
Our small operator cannot employ a training analyst.
Fine. What were we actually asking the analyst to achieve?
We wanted somebody to notice whether several pilots were struggling with the same thing.
Perhaps, in a seven-pilot operation, that does not require software. Maybe every three months the HOTC, two instructors and a senior line pilot sit around a table with the training records and ask what keeps appearing, what they are reteaching, where instructors disagree, what pilots are finding difficult after line release, and whether anything in the operation has changed that the training system has not caught up with.
That meeting might take ninety minutes.
The mechanism is less sophisticated. The thinking is not.
Take away the simulator
An excellent simulator program gives us enormous freedom. We can reproduce complex situations safely, control variables, pause the exercise, repeat decisions and create events that would be inappropriate to manufacture in an aircraft.
A small operator may not have access to one. Does that mean it cannot deliberately develop judgement? Of course not.
A scenario may be as simple as changing one piece of information during an otherwise normal training flight. The destination weather is still legal but trending down. The preferred runway becomes unavailable. A passenger request changes the time pressure. The fuel figure is slightly different from expected.
The instructor does not need to manufacture a crisis. They need to know what competence they are trying to develop, provide enough cues for the pilot to recognise the changing picture, and give them enough room to think.
That is the same instructional-design principle. It just costs considerably less.
Take away the dedicated project manager
This one becomes harder.
Some constraints genuinely matter. If the HOFO is simultaneously flying, managing daily operations, writing procedures and introducing a new aircraft, no amount of clever simplification magically creates another twenty hours in the week. The answer cannot always be “work smarter”. Sometimes an organisation genuinely needs more capacity.
But before assuming that the only alternatives are hiring a project team or accepting a weaker implementation, we can ask what the dedicated project manager was providing.
Someone knew what needed to happen. Someone was tracking assumptions and dependencies. Someone knew which decisions were unresolved. Someone was watching the implementation timeline. Someone was making sure temporary arrangements did not quietly become permanent.
A small operator might distribute those jobs. Perhaps there is a single weekly change meeting with a one-page implementation board. Perhaps each workstream has a named owner. Perhaps the organisation deliberately removes some lower-priority work from the HOFO and HOTC for six weeks. Perhaps an external specialist carries one part of the project while the operator retains the decisions that need internal knowledge.
Again, it is not equivalent. But it can preserve the important part of the system.
Proportionality is not asking what we can remove because we are small. It is asking what the gold-standard mechanism is actually achieving, and what the simplest credible way is to achieve the same purpose.
And then there is the resource we routinely underuse
There is another source of capability available to small operators that costs remarkably little.
Each other.
Imagine our two operators are only a few hundred kilometres apart. They operate in similar conditions. They recruit from the same pilot population. They have both introduced similar aircraft. Both have spent time deciding how to train inexperienced commercial pilots into demanding regional operations. Both have had to solve instructor-standardisation problems. Both have developed procedures for the same kinds of weather, destinations and operational pressures.
And both independently spend hundreds of hours solving variations of the same problems.
They never talk about them.
That seems like an extraordinary waste of experience.
I do not mean competitors should exchange commercially sensitive information, hand over proprietary material or pretend every operation is interchangeable. They are not. But there is an enormous space between sharing nothing and sharing everything.
A HOFO can ring another HOFO and ask how they structured the first few weeks after introducing an aircraft. A HOTC can ask what their external conversion course failed to prepare pilots for. An instructor can ask another operator's instructor how they are developing decision-making without turning every scenario into an emergency. A safety manager can say, “We are seeing this pattern. Have you seen anything similar?”
Nobody has to adopt the answer. That is not the point.
The conversation expands the number of experiences available before the organisation makes its own decision.
Sometimes that conversation is a formal safety forum. Sometimes a conference. Sometimes an instructor-standardisation day involving people from several organisations. Sometimes it is two operators deliberately peer-reviewing a problem without exchanging confidential material. Sometimes it is simply a phone call to somebody whose judgement you respect.
The infrastructure does not have to be impressive. The conversation has to be useful.
We should probably talk to people outside our own role as well
There is another version of the same problem inside organisations.
Pilots talk to pilots. Engineers talk to engineers. Instructors talk to instructors. Management talks to management. Then we are surprised when a technically reasonable decision creates a problem somewhere else.
Some of the best discussions happen when we widen the room.
Ask maintenance what a proposed operating procedure means for defect recovery. Ask the operations person what information pilots actually receive when a late schedule change occurs. Ask a recently released line pilot which parts of training turned out to be different from the real operation. Ask the experienced captain where the written SOP creates unnecessary workload. Ask the junior instructor which parts of the syllabus are difficult to interpret without somebody explaining the history behind them.
Ask the chief pilot at another company what they wish they had known six months before introducing the same class of aircraft.
This does something valuable that no manual template can do. It exposes our assumptions to people who do not share them.
And that is particularly valuable in small operations, because a system can remain apparently successful for a very long time when the same few experienced people designed it, teach it, supervise it and assess whether it works.
Broad discussion introduces friction. Useful friction.
Someone asks why. Someone has seen the same idea fail somewhere else. Someone points out a consequence the original group never considered. Someone says, “We tried that. Here is what surprised us.”
You may still choose exactly the same solution. But now you are choosing it with more information.
Networking should not mean collecting business cards
When we talk about networking in aviation, the word can sound transactional: meet people, build contacts, find the next job.
There is nothing wrong with any of that. But for an industry made up of many small organisations, networking can be something much more operationally useful.
It can be part of how the industry learns.
The value is not in knowing more people. It is in having enough trusted relationships that you can have meaningful conversations before you need them.
That might mean regular informal discussions between key personnel from neighbouring operators. Shared professional-development sessions. Cross-operator instructor workshops. A regional safety forum. Inviting somebody from another operation to challenge a proposed system before it is implemented. Calling another operator after an internal event — not to disclose protected information, but to discuss the general problem it exposed.
Sharing an idea that worked. Sharing one that did not.
And perhaps most importantly, being willing to say:
We have not solved this particularly well yet. How are you approaching it?
There is a great deal of maturity in that sentence.
The gold standard includes borrowing other people's lessons
With unlimited resources, we would commission research, collect data, run trials and employ specialists.
With limited resources, one of the most powerful questions available to us is:
Who has already thought deeply about this?
Not so we can copy them.
Imported systems often fail precisely because somebody copied the artefact without understanding the operation behind it.
The value of talking to another operator is not receiving their SOP. It is understanding why they made the decision they made. What problem were they solving? What alternatives did they consider? What went wrong initially? What would they do differently? Which part turned out to matter far more than expected? Which control looked good on paper and created unnecessary work in practice?
Those answers are much more transferable than the document itself. They help us understand the design problem before designing our own answer.
There are still things we should spend money on
Practicality should not become an excuse for under-resourcing.
There are points where the answer really is: we need more capability.
If nobody in the organisation has the expertise to design a system, outside expertise may be appropriate. If the HOTC cannot meaningfully supervise the training program because they are carrying an impossible workload, another spreadsheet is not the solution. If a simulator provides an important training capability that cannot safely or effectively be achieved in the aircraft, access to simulation may be worth paying for. If one person's departure would remove the organisation's ability to train or check its pilots, succession deserves resources.
Proportionality is not about finding the cheapest possible version of everything.
It is about spending limited resources where they change the capability.
That may be money. Often it is time. Sometimes it is simply management attention. And occasionally it is the willingness to stop and have a conversation before producing another document.
Go back to our two operators
Six months later, the first organisation still has more resources.
That advantage is real. It has better data, more resilience and more capacity to test and refine its systems.
The second operator has not somehow erased that difference through enthusiasm.
But perhaps it has done something more useful than trying to imitate the first operator badly.
Its three instructors have agreed what readiness actually means. A senior pilot conducts occasional structured line observations. The HOTC reviews training patterns rather than individual records in isolation. The aircraft introduction began inside a deliberately limited operating envelope while internal capability matured. Temporary dependencies are written down and reviewed. SOP changes are discussed with the people who use them before release.
And every month or two, the HOFO speaks to peers at other operators about what they are seeing in their own operations. Once a quarter, people from several organisations sit in a room together and explore a problem none of them owns exclusively.
There is no enormous department behind any of it. Most of the mechanisms are surprisingly simple.
But they are deliberate.
Because small operators have always relied heavily on experienced people talking to one another. The opportunity is not to replace that with bureaucracy. It is to recognise it as a source of capability and make sure the learning does not disappear when the conversation ends.
So what does gold standard actually mean?
Perhaps we need to stop equating it with scale.
The gold standard is not the operator with the most manuals, the largest training department, the most software or the longest implementation plan. Those things can support an excellent operation. They can also support an average one.
The gold standard is an organisation that understands what capability it needs, deliberately builds it, knows where its weaknesses and dependencies are, listens to the people doing the work, learns from what happens, and changes when the evidence tells it to.
With unlimited resources, we can build extraordinary infrastructure around those principles.
With limited resources, we have to be much more thoughtful about which mechanisms preserve them.
And sometimes the highest-value thing we can do costs almost nothing: ask another instructor, ring another operator, bring maintenance into the conversation, compare how two organisations solved the same problem, let someone outside our own system challenge an assumption before it becomes a procedure, and talk openly about what worked — and, when we can, what did not.
General aviation will probably always work inside constraints. There will never be enough people, enough training time, enough aeroplanes or enough money to build every system we could imagine.
But the choice is not between airline-scale infrastructure and accepting whatever develops organically.
There is a much larger space between those extremes.
That is where some of the most interesting work in GA sits: take the standard we would want if resources were unlimited, work out what actually makes it effective, talk broadly enough that we do not have to learn every lesson ourselves, and then build the simplest system that preserves the parts that matter.
Not a lower standard because the operation is small. A smarter way of reaching it — and an industry willing to help each other get there.
Sources and further reading
CASA — Part 119 of CASR: certification and management
CASA — Training and checking systems for flight operators
ICAO — Safety Management Manual and safety management guidance material
