BR-ANAC-IOAR common mistakes
BR-ANAC-IOAR · Understand the traps and how to avoid them.
When asked which RBAC requirement applies, the candidate answers from memory of the regulation's general intent instead of citing the specific RBAC number, subpart, and paragraph, and invents or misattributes a paragraph number to fill the gap.
RBAC texts are long and paragraph-numbered; candidates study summaries and flowcharts rather than the regulation itself, so the structure is familiar but the exact citation is not. Exam items that ask 'under which requirement' reward precise citation and punish plausible-sounding paraphrase.
What to do instead
Build a one-page citation map per RBAC (e.g., RBAC 145 for maintenance organizations, RBAC 121/135 for operators, RBAC 43 for maintenance and alteration, RBAC 21 for certification) listing only the subparts and paragraph numbers you can defend. For each, write the requirement in one sentence in your own words. Drill by covering the sentence and recalling the citation, and vice versa. If a citation cannot be recalled with confidence, practise the discipline of describing the requirement's content and stating that the exact paragraph must be verified rather than guessing a number.
Treating an airworthiness certificate as a one-time event: answering questions about continued validity as if the certificate itself expires on a calendar date or requires periodic re-issuance, and confusing certificate validity with the continuing airworthiness obligations that keep it valid.
Initial certification is taught as a discrete process with defined steps, so the mental model becomes 'certificate issued equals task complete'. The continuing obligations (maintenance programme, airworthiness directives, defect reporting, mass and balance, approved data) are learned separately and never linked back to certificate validity.
What to do instead
Draw a single lifecycle diagram from type design through individual certificate to retirement, and annotate on it every condition that suspends or invalidates the certificate (unapproved maintenance, overdue directive, unapproved modification, loss of maintenance programme approval). Answer practice items by tracing the scenario on the diagram before choosing an option. Explicitly separate 'the document' from 'the state of airworthiness' in your notes.
Confusing the roles of the type certificate holder, the design approval holder, and the operator when assigning responsibility for continued airworthiness tasks such as instructions for continued airworthiness, airworthiness directives, and service information.
The same organisation may hold several approvals, and training material often presents certification and continued airworthiness as separate chapters, so candidates never build an explicit responsibility matrix. Exam scenarios deliberately place the candidate in one role and test whether they know where the obligation sits.
What to do instead
Create a responsibility matrix with rows for design approval holder, production organisation, maintenance organisation, operator, and the authority, and columns for issuing instructions for continued airworthiness, proposing and mandating directives, compliance demonstration, and record keeping. For every practice scenario, state the role of the person described before answering. Review the matrix until you can reproduce it from memory.
Designing or evaluating a maintenance programme by copying interval values from a familiar aircraft or from a manufacturer's generic schedule without justifying them against the operator's utilisation, environment, and reliability data, and without addressing how intervals are escalated or adjusted.
Candidates memorise example intervals because numbers are easy to recall, and they mistake a sample programme for a method. The examined skill is the method: deriving tasks, justifying intervals, and managing change through reliability data and authority approval.
What to do instead
Practise producing a programme outline from a scenario: identify the source documents, list task categories, show how intervals are initially set, and describe the reliability programme and the approval route for escalation. When a question supplies utilisation or environmental data, explicitly connect each proposed interval to that data in your reasoning. Never quote an interval without stating its basis.
Conducting an audit or surveillance exercise by listing findings without classifying them, without tracing them to a requirement, and without distinguishing a systemic deficiency from an isolated non-compliance.
Candidates treat audit questions as comprehension questions about what is wrong, rather than as exercises in evidence, requirement, and grading. They also skip the corrective-action loop, so the answer stops at the finding and never reaches root cause, action plan, and verification of effectiveness.
What to do instead
Use a fixed four-column template for every audit scenario: objective evidence observed, requirement it breaches, classification and severity, required corrective action with root-cause expectation. Then add a fifth column for verification of effectiveness. Practise writing findings in that structure under time pressure so the format becomes automatic, and always state whether the finding indicates a system failure or an individual lapse.
Answering certification and oversight questions about operators and maintenance organisations by describing what a well-run organisation would do, rather than the specific approval stages, documented procedures, personnel qualification requirements, and authority acceptance steps the regulation requires.
Candidates have operational experience of how organisations behave and substitute that intuition for the formal certification sequence. The formal sequence (pre-application, application, documentation assessment, inspection, demonstration, approval, and continued oversight) is procedural knowledge that experience does not supply.
What to do instead
Write the certification sequence for a maintenance organisation and for an air operator as numbered flowcharts, with the document produced at each stage and the authority decision at each gate. Add the qualification and staffing requirements as a side list. Rehearse by describing the sequence aloud from memory, then check against the regulation and correct gaps.
Treating a safety management system as a documentation set: answering that a SMS is satisfied by having a manual, a reporting form, and a safety manager, and failing to describe the four components, the interfaces between them, and how safety assurance closes the loop back into policy and risk management.
SMS material is often presented as a list of required manuals and positions, which is easy to memorise and hard to apply. Candidates therefore reproduce the artefacts instead of the functioning system, and miss items that describe a broken feedback loop.
What to do instead
Learn the four components with their sub-elements and, for each, write one sentence describing the evidence that would prove it is working, not merely present. Practise diagnosing scenarios: identify which component is failing and what evidence would demonstrate recovery. Emphasise the feedback path from safety assurance to safety policy and objectives.
Reporting an occurrence by describing the technical defect only, omitting the human, organisational, and procedural context, and misjudging whether an occurrence is reportable at all.
Candidates conflate occurrence reporting with technical defect logging, and they learn reportable categories as a list without the protective purpose behind them. As a result they under-report and under-describe, and they miss questions that test the boundary of reportability.
What to do instead
For each practice occurrence, write the report in three layers: what happened technically, what the human and organisational conditions were, and what the safety consequence could have been. Separately memorise the reportable categories and the reporting channel and timeframe, and test yourself on borderline cases by stating the criterion you applied. Remember that the report protects safety information, which is why completeness matters.
Answering human factors items with generic attitude or motivation language instead of naming the specific factor, its mechanism, and the maintenance-error outcome it produces, such as a shift handover losing task status, a duplicate inspection defeated by expectation bias, or fatigue degrading error detection.
Human factors is perceived as common sense, so candidates answer from intuition and never build a vocabulary linking factors to error types. Exam items require the mechanism, not the moral, and distractors are written to sound like sensible advice.
What to do instead
Build a table of factors (fatigue, complacency, pressure, distraction, lack of communication, lack of resources, lack of teamwork, lack of awareness, normative behaviour) with columns for the mechanism, the typical maintenance task where it bites, and the countermeasure. Practise converting every scenario into 'factor, mechanism, outcome, barrier'. Use the same structure for safety culture questions, distinguishing a reporting culture from a just culture.
Treating ICAO standards and national regulation as interchangeable: applying an ICAO Annex provision directly as if it were binding domestic law, or assuming a national requirement is identical to the Annex because the topic matches.
Candidates learn Annex content and RBAC content in separate study blocks and never examine the relationship between them. The distinction between standards, recommended practices, and the state's implementing regulation is subtle but is exactly what harmonisation questions test.
What to do instead
For each major topic, note the ICAO Annex provision, the corresponding RBAC implementing text, and any difference in stringency or scope, including how the state notifies differences. Learn the hierarchy explicitly: the Convention, Annexes with standards and recommended practices, national implementing regulation, and approved organisational procedures. Answer harmonisation items by naming which layer the question is about before evaluating the options.