ANAC AVSEC Instructor - Aerodrome Operators (Instrutor AVSEC - Operador de Aeródromo - IOAD) common mistakes
ANAC AVSEC Instructor - Aerodrome Operators (Instrutor AVSEC - Operador de Aeródromo - IOAD) · Understand the traps and how to avoid them.
When asked who is responsible for the aerodrome security programme, candidates answer that the competent authority (e.g., the national civil aviation security authority or police) owns it, and describe the aerodrome operator as merely complying with instructions.
Candidates conflate the State's regulatory and oversight role under Annex 17 with the operator's implementation role. Because the State sets the programme requirements and conducts audits, candidates assume the State also runs the programme, and they memorize the regulator's tasks more thoroughly than the operator's.
What to do instead
Build a two-column comparison table for every topic: 'State/competent authority obligation' versus 'aerodrome operator obligation'. For each, cite the instrument (Annex 17 Standard, Doc 8973 guidance, national regulation). Practise restating the operator's accountability in active voice: the operator establishes, implements, and maintains the aerodrome security programme, designates a security manager, and ensures contractors meet the same standards.
Candidates treat Annex 17 Standards and Doc 8973 guidance as interchangeable, quoting a Doc 8973 recommended practice as if it were a binding Standard, or claiming Annex 17 prescribes detailed operational procedures such as specific screening technology or exact patrol frequencies.
Both documents are studied together and share vocabulary, so the distinction between 'shall' Standards, 'should' recommended practices, and guidance material blurs. Candidates also overestimate Annex 17's granularity because it is the flagship document.
What to do instead
Annotate each item you study with its source and status: Annex 17 Standard, Annex 17 Recommended Practice, Doc 8973 guidance, or national regulation. When answering, state the source explicitly. Remember the design logic: Annex 17 sets the obligation, Doc 8973 explains how it may be met, and the national programme makes it enforceable and specific.
When asked to design or justify a contingency plan, candidates produce a generic emergency response list (fire, bomb threat, medical) without addressing security-specific elements: command and control arrangements, decision authority for raising/lowering security levels, communication with the competent authority, preservation of the crime scene, business continuity, and testing/review cycles.
Candidates borrow from general airport emergency planning, which they know better, and overlook that the security contingency plan must dovetail with, but remain distinct from, the emergency plan. They also memorize lists of threats rather than the plan's structure.
What to do instead
Learn a fixed skeleton for the security contingency plan: purpose and scope, roles and command structure, activation triggers and security-level escalation, communication and notification, response actions by threat type, coordination with the emergency plan and external agencies, recovery and continuity, and test, review, and revision. Practise populating the skeleton for two or three scenarios.
Candidates describe access control as a single measure (badges or a fence) rather than a layered system, and they omit the supporting processes: vetting and background checks before authorisation, need-to-know and least-privilege zoning, escort rules, challenge procedures, revocation and retrieval, and audit of access logs.
Access control is visually associated with gates and cards, so candidates recall the physical artefacts and forget the administrative and human processes that make them effective. The topic is also split across domains, so candidates study pieces without assembling the system.
What to do instead
Map access control as a chain: authorisation decision (vetting) → credential issuance → zone definition and least privilege → physical and procedural enforcement (readers, guards, escort, challenge) → monitoring and audit → revocation. For each link, be able to name the operator's responsibility and one common failure it prevents.
Candidates apply passenger and cabin baggage screening rules to cargo and mail, or assume cargo security is achieved solely by X-ray at the point of loading, ignoring the regulated agent/known consignor chain, chain-of-custody documentation, and the different treatment of mail.
Passenger screening is the most familiar and most rehearsed process, so candidates generalize it. Cargo security relies on supply-chain concepts that are less intuitive and less often practised in day-to-day aerodrome work.
What to do instead
Study passenger/baggage, cargo, and mail as three separate processes with their own control points, then compare them in a table: who applies the control, where in the chain it occurs, what documentation evidences it, and what happens when the chain is broken. Emphasize that secure supply-chain status must be protected from the point of screening to the aircraft.
In response-to-unlawful-interference questions, candidates jump directly to tactical actions (evacuation, arrest, storming) and omit the initial and coordinating steps: notification and escalation, establishing command, liaising with the competent authority and police, information management and media handling, and protecting evidence and records.
Scenario-style questions invite dramatic answers, and candidates conflate the aerodrome operator's supporting role with the police or tactical commander's role. They also underestimate how much of the response is coordination and documentation.
What to do instead
Answer response questions in strict chronological phases: detect and report → notify and escalate per the plan → support the designated command (the operator supports, it does not command police operations) → protect people, perimeter, and evidence → communicate internally and externally through authorised channels → recover, review, and report. Practise stating explicitly which actions belong to the operator and which to the authority.
Candidates explain insider threat purely as a screening or disciplinary problem, or as 'bad people doing bad things', and propose only background checks or punishment as controls, missing behavioural indicators, reporting culture, segregation of duties, and the interaction between human factors and security culture.
Insider threat is often taught through case studies that emphasize the individual's motive, which encourages a moral framing. The organizational and systemic controls that make insider activity harder and more detectable are less memorable and less discussed.
What to do instead
Structure insider threat answers around three control families: organizational (vetting, least privilege, segregation of duties, rotation), behavioural (indicators, confidential reporting, supervisor awareness, non-punitive reporting for honest mistakes), and cultural (leadership commitment, speaking up, learning from near misses). Use human-factors vocabulary such as workload, fatigue, complacency, and normalization of deviation.
When asked to design a training session, candidates list content topics and a duration but omit learning objectives written in observable terms, an assessment that matches those objectives, learner characteristics, and an evaluation level beyond 'learner satisfaction'.
Candidates equate a training plan with a syllabus. Instructional design models are learned as abstract theory and are rarely practised end-to-end, so the linkage from objective to method to assessment to evaluation is not internalized.
What to do instead
Practise producing a one-page design for any AVSEC topic: audience and prerequisites, two to four objectives using observable verbs (identify, apply, demonstrate), method matched to each objective, assessment item matched to each objective, and evaluation at reaction, learning, behaviour, and results levels. Check alignment explicitly: every objective has a method and an assessment.
Candidates answer adult-learning questions with generic principles (adults are busy, use discussion) without connecting principles to concrete delivery decisions, and they fail to distinguish formative from summative assessment or to explain how assessment validity and reliability are protected.
Adult-learning theory is easy to state and hard to apply, so candidates reproduce slogans. Assessment terminology is often memorized as definitions without understanding the consequences of poor design, such as teaching to the test or inconsistent marking.
What to do instead
For each principle (relevance, experience, problem-centred learning, self-direction), prepare one concrete delivery technique and the reason it works. For assessment, be able to define formative versus summative, validity, reliability, and fairness, and give one example of how each is threatened and one control (e.g., marking rubric, moderation, blueprint mapping items to objectives).
Candidates describe the instructor's role as delivering content and testing learners, omitting the competency dimensions expected of an AVSEC instructor: subject-matter currency, instructional competence, assessment competence, professional conduct and integrity, and the requirement to maintain and refresh competence through continuing development.
Candidates identify with the learner-facing part of the role and underestimate the standards expected of them as instructors. Instructor competency frameworks are often skimmed as administrative lists rather than studied as assessable content.
What to do instead
Prepare a four-dimension model of instructor competency (subject knowledge, instructional skill, assessment skill, professional conduct) and, for each, one way it is demonstrated and one way it is maintained. Be ready to explain why an instructor who cannot assess reliably undermines the whole training system, and link this to the operator's security programme.