Aviation Incompetence Is Often a Training Gap

A new engineer joins an organisation and asks a basic question about how a local procedure works.

Someone quietly labels the person as weak.

But the procedure is hard to find. The training was generic. The internal system is messy. The local way of working was never explained properly. The person is expected to perform confidently inside a system they have not yet been taught to navigate.

That is not always incompetence.

Often, it is a training and familiarisation problem.

Aviation is full of capable people who look less capable when they cannot quickly access the right procedure, understand the local process, or connect a regulation to the organisation’s actual way of working.

This does not mean incompetence is never real. It is real, and it matters. But aviation organisations should be careful before treating every performance gap as a personal weakness.

Sometimes the system has not made competence easy to maintain.

Competence is not just experience

Aviation people often talk about competence as if it belongs only to the individual.

The engineer is competent. The planner is competent. The auditor is competent. The CAMO officer is competent. The instructor is competent.

That is partly true.

People need knowledge, skill, judgement and experience. They need to understand the aircraft, the regulation, the procedure and the limits of their authorisation.

But competence also depends on the environment.

A person can be experienced and still struggle if the organisation’s procedures are unclear, the document system is difficult, the training is too generic, or the local expectations are not explained.

A person can know the regulation and still make mistakes if they cannot find the current internal procedure.

A person can hold the right licence and still need familiarisation before working safely in a new organisation.

That is why competence should not be reduced to a CV, licence or previous job title.

It has to be established, supported and controlled inside the organisation.

EASA already points toward controlled competence

This is not only a management opinion.

The following are paraphrases, checked against the regulation database on 24 September 2026, using the 2025-09-02 Easy Access Rules baseline and the current provision versions. The regulation points are requirements; AMC1 describes an acceptable means of compliance, not an additional regulation. Read EASA’s Continuing Airworthiness rules alongside the organisation’s controlled procedure.

For Part-145, point 145.A.30(e) requires the organisation to establish and control the competency of personnel involved in maintenance, airworthiness reviews, safety management and compliance monitoring. The requirement also includes understanding safety management principles, including human factors and human performance issues, appropriate to the person’s function and responsibilities.

The associated acceptable means of compliance, AMC1 145.A.30(e), says personnel such as planners, mechanics, specialised services staff, supervisors, certifying staff and support staff should be assessed for competency before unsupervised work starts, and that competency should be controlled on a continuous basis.

It also points to assessment using on-the-job performance, knowledge testing, training records, product or task training and experience records.

That is important.

Competence is not assumed forever. It is assessed, recorded and maintained.

For certifying staff and support staff, 145.A.35(d) requires sufficient recurrent training in each two-year period so they keep up-to-date knowledge of relevant technologies, organisation procedures and safety management, including human factor issues. 145.A.35(e) requires a recurrent training programme. 145.A.35(f) requires assessment of certifying staff for competency, qualifications and capability to carry out their intended certifying duties before issue or reissue of a certification authorisation, except for the defined unforeseen cases.

For CAMO, CAMO.A.305(g) requires the organisation to establish and control the competency of personnel involved in compliance monitoring, safety management, continuing airworthiness management, airworthiness reviews or recommendations and, where applicable, permits to fly. It also requires an understanding of safety management and human factors principles appropriate to the person’s function and responsibilities.

CAMO.A.220(c) requires qualification and experience records for continuing airworthiness management, compliance monitoring and safety management personnel, as well as airworthiness review staff and staff issuing recommendations or permits to fly. For those latter staff, records include the relevant qualifications, experience and training summary, and a copy of the authorisation. Personnel records remain while the person works for the organisation and for three years after departure.

The pattern is clear.

Aviation competence needs structure, records, recurrent training and procedure awareness.

The hidden problem is local procedure knowledge

Aviation professionals can usually talk about regulations.

The harder part is often local procedure knowledge.

Where is the current procedure? Which form is used? Which system is the official record? Who approves this step? Which evidence is expected? Which local limitation applies? What changed since the last revision? What does the organisation actually do when the regulation leaves room for process design?

This is where new staff, contractors and transferred personnel often struggle.

They may understand the general requirement but not the local implementation.

That gap can look like incompetence from the outside.

In reality, it may be poor onboarding, weak familiarisation, unclear procedures or missing access to information.

This matters because aviation work is not performed against regulation alone. It is performed through the organisation’s approved or accepted procedures.

If people cannot find and understand those procedures, performance will suffer.

Generic training is not enough

Many organisations provide induction training, human factors training, SMS awareness and recurrent training.

That is necessary.

But it may not be enough.

Generic training tells people the principles. It does not always show them how to work inside the company’s actual system.

A useful familiarisation process should answer practical questions:

• Which procedures apply to my role?
• Which systems do I use every day?
• Which records must I create?
• Which approvals do I need before acting?
• Which tasks am I authorised to perform?
• Where do I find current forms and templates?
• What should I do when the procedure is unclear?
• Who do I ask before I make a decision?

This is not hand-holding.

It is operational control.

Aviation organisations should not expect people to absorb local knowledge through guessing, informal messages or corridor explanations.

If the knowledge matters, it should be taught, accessible and reviewable.

Poor access creates poor performance

Even trained people make weaker decisions when access is poor.

If the document control system is hard to search, people ask colleagues instead of checking the source. If procedure names are unclear, people use old bookmarks. If forms are hidden, people copy previous versions. If training records are difficult to see, managers may miss renewal gaps. If audit findings are disconnected from procedures, the same issues repeat.

This is not a people problem only.

It is an information design problem.

The organisation may have the correct procedure, but if staff cannot find it at the moment of need, the practical effect is similar to not having it.

Aviation work needs current, role-relevant knowledge near the task.

That is where many SaaS systems and document folders fall short. They may store the information, but they do not always help the person use it under time pressure.

Be careful with the word incompetence

The word “incompetence” is heavy.

It can be accurate. There are cases where a person does not meet the required standard, cannot perform the task safely, or should not hold an authorisation.

But the word should be used carefully.

Before calling someone incompetent, an organisation should ask:

• Was the person trained on the relevant local procedure?
• Was the procedure current, clear and accessible?
• Was the person’s scope of authorisation clear?
• Was supervision appropriate before unsupervised work?
• Were gaps identified during competence assessment?
• Was recurrent training linked to real issues and changes?
• Were human factors and workload considered?

These questions do not remove personal responsibility.

They make the assessment fairer and more useful.

If the problem is individual competence, address it. If the problem is weak familiarisation, fix the familiarisation. If the problem is procedure access, fix the access.

Different causes need different actions.

What this means for Avioverse

Avioverse is being built as a personal aviation workbench and second brain for professionals working in an EASA environment.

It is not a replacement for the organisation’s approved exposition, training system, document control system or competence process.

But it can support the professional before the formal decision.

The right aviation AI assistant can help users ask precise, procedure-based questions. It can help them connect a task to a source. It can show cited answers with visible disclaimers. It can support guided checks. It can help draft review-ready notes. It can turn gaps into tasks for follow-up.

For Avioverse, the useful role is not “AI declares this person competent.”

That would be wrong.

The useful role is: “Here are the relevant source points, here are the procedure questions to check, here are the missing inputs, and here is a draft structure for review.”

That helps professionals learn faster and work more consistently, while keeping accountability with the organisation and the approved process.

Better systems make better people visible

Aviation does not become safer by blaming people too quickly.

It becomes safer when organisations understand why performance gaps happen and fix the right layer.

Sometimes the issue is individual competence. Sometimes it is weak training. Sometimes it is poor procedure familiarisation. Sometimes it is a knowledge-access problem. Often, it is a mixture.

The practical lesson is simple.

If you want competent performance, make the right knowledge easy to find, easy to understand and easy to connect to the task.

Then assess the person fairly against the real requirement, the local procedure and the evidence.

That is how aviation organisations move from blame to control.

And that is where structured, source-aware aviation AI can help.