The accurate and disciplined application of technical knowledge, operating procedures and regulatory requirements — grounded in understanding rather than mechanical compliance.
Application of Knowledge and Procedures is one of the nine core competencies used in competency-based training and assessment (CBTA). It covers practical knowledge of aircraft systems, following standard operating procedures unless safety requires otherwise, using checklists and manuals effectively, recalling memory items, and keeping up to date with regulations, policies and crew notices.
Knowledge on its own is not the competency; applying it at the right moment is. It is the store every other competency draws on: you cannot generate good options, anticipate how a system will behave or spot an error without it. The articles below take each behaviour in turn, from SOP discipline to knowing where a procedure comes from.
Start here: The Competency That Holds Everything Together →
Opinionated, experience-led analysis of Application of Knowledge and Procedures on the real flight deck.
Knowledge isn't just one competency among nine. It's the substrate the others grow from. Without it, leadership is performance, decision-making is guesswork, and procedures are bureaucracy.
Detailed articles on individual observable behaviours — the specific skills the framework assesses.
Correct operation is not a speed test. Deliberate, considered, timely — and always from the verified source, never from memory alone.
SOPs are not a compliance mechanism. They are the infrastructure of the operation — the shared mental model, the workload management tool, and the early warning system. The safety net they provide is only available to the crew that built the habit before they needed it.
The checklist is the vehicle. The competencies are what it tests — Communication, Workload Management, and Leadership and Teamwork all working together in every exchange.
Compliance should be easy — normal operations are built on it. The challenge is the discipline to stay current and the professionalism to accept change without resistance.
Recall items are not a memory test. They are a performance requirement under conditions designed to degrade performance. The gap between knowing and performing is what this behaviour is about.
Knowing a system's limitation is declarative knowledge. Understanding why it exists, what it protects against, and how disabling it affects other systems — that is operational knowledge.
Memory is not a source. Knowing which document governs the task, that it is approved and current, and that it fits the situation in front of you.
The word that carries the weight in this behaviour is not procedural. It is relevant — and it is at the infrequent end of the procedural spectrum where the competency is actually being tested.
HPP maps every Application of Knowledge and Procedures behaviour across three development levels — with structured prompts to build honest self-assessment into your regular flying. Free to start.
Try Free →