BR-ANAC-CMS common mistakes
BR-ANAC-CMS · Understand the traps and how to avoid them.
Treating Advisory Circulars and manufacturer service documents as mandatory airworthiness requirements, and treating Airworthiness Directives as advisory recommendations.
Candidates memorize document names without classifying them by legal force, so they misjudge which publications create enforceable obligations.
What to do instead
Build a two-column sort table: binding (regulations, Airworthiness Directives, approved type design data) versus non-binding (Advisory Circulars, service letters, recommended practices). For each document, state who issued it, its legal basis, and whether it mandates action or only provides an acceptable means of compliance.
Selecting the wrong return-to-service authority, certifying an aircraft after a major repair or alteration with only a maintenance release, or signing off work outside the ratings and privileges held.
The difference between a maintenance release and an approval for return to service after major work is subtle, and candidates conflate the two acts or ignore the scope of their authorization.
What to do instead
Map each work category (routine maintenance, major repair, major alteration, inspection) to the exact person or body authorized to approve return to service. Practice with short scenarios that vary the work type and the credential of the signer, and state the governing rule for each.
Recording only the work performed and omitting the required identity data such as part numbers, serial numbers, total time, or the reference to approved data used.
Candidates focus on describing the task and overlook that a record must let a later reader reconstruct what was done, on what item, and under what authority.
What to do instead
Use a fixed checklist for every record entry: date, item identification, work description, approved data reference, parts installed with numbers and serials, signature, and credential. Rewrite sample incomplete entries against the checklist until every field is habitually captured.
Approving a task as complete while an inspection step, functional check, or operational test specified in the maintenance program has not actually been performed or documented.
Candidates treat inspection and testing as optional add-ons rather than integral parts of the task, and under time pressure they sign for work that was only partially accomplished.
What to do instead
For each scheduled task, separate the actions into perform, inspect, and test, and require an explicit sign-off for each. Practice writing task cards that cannot be closed until every required check has its own recorded result.
Misjudging whether a defect or damage finding is within acceptable limits, and either releasing an aircraft with damage beyond limits or grounding one that is within limits.
Candidates rely on memory of limit values instead of locating and applying the structural repair or inspection criteria in the approved data for that specific aircraft and location.
What to do instead
Practice the lookup sequence: identify the structure and location, find the applicable allowable damage or repair limit in the approved data, compare measured values, and record the disposition. Work through several damage scenarios where the correct answer depends on location and size, not on a single universal limit.
Treating an approved repair or alteration as automatically acceptable without checking that it remains compatible with the existing type design and other installed modifications.
Candidates assume approval of a document equals approval of the specific installation, ignoring interactions between repairs, alterations, and the original design.
What to do instead
For each repair or alteration scenario, verify three things: the approved data covers this model and configuration, the change does not invalidate other approved data already embodied, and any required supporting analysis or test is identified. Practice spotting conflicts such as a repair that changes a load path assumed by another modification.
Confusing scheduled maintenance intervals with airworthiness limitation items, and treating a maintenance planning document interval as if it were an enforceable limit.
Both appear as time or cycle values in planning documents, and candidates do not distinguish the operator's approved program from items that carry a mandatory limit.
What to do instead
Classify each interval by source and consequence: program interval set by the operator's approved schedule versus limitation that must be met for continued airworthiness. For each, state what happens if it is exceeded and who can extend it, if anyone.
Explaining an accident or incident solely as an individual error, without identifying the organizational and systemic factors that allowed the error to occur and persist.
Candidates default to blame-based reasoning and do not apply human factors models that separate active failures from latent conditions.
What to do instead
Practice writing short analyses that name at least one active failure and two latent conditions such as inadequate training, unclear procedures, or missing feedback loops. Then propose a corrective action aimed at the system rather than at reminding people to be careful.
Assuming that a component removed from an aircraft and later reinstalled needs no further documentation or verification of serviceability.
Candidates treat removal and reinstallation as a trivial action and skip the traceability and condition checks that apply to components moving through storage and maintenance.
What to do instead
For each component scenario, list the required evidence: serviceable status, storage conditions, shelf-life or life-limited status, and the record linking the specific part to the specific installation. Practice identifying cases where a part must be quarantined or recertified before use.
Describing a system fault by its symptom and replacing parts without following a structured troubleshooting path that uses the approved fault isolation data.
Candidates jump from symptom to a familiar component, skipping the verification steps that confirm the fault and the tests that prove the fix.
What to do instead
Use a fixed troubleshooting sequence: confirm and characterize the fault, consult the approved isolation procedure, test the suspected cause, replace or adjust, then repeat the operational test to prove the fault is cleared. Practice writing the sequence for faults where two systems produce similar symptoms.