8.2 Error Types in Maintenance, Violations & the Implications of Errors

8.2 Error Classification: Slips, Lapses, Rule/Knowledge Mistakes & Violations

In aviation maintenance engineering, preventing recurrence requires a precise technical diagnosis of the cognitive failure mode that produced an error. Labeling an incident as simple "carelessness" or "mechanic error" provides zero insight into systemic causes and yields no effective safety intervention. To scientifically categorize human error, modern aviation regulations and investigation methodologies integrate two classic frameworks: Danish engineer Jens Rasmussen's Skill-Rule-Knowledge (SRK) framework of cognitive control and British psychologist James Reason's Taxonomy of Unsafe Acts.

Rasmussen's Skill-Rule-Knowledge (SRK) Framework

Jens Rasmussen established that human cognitive processing operates across three distinct levels depending on task familiarity, cognitive workload, and operational competence:

1. Skill-Based Behavior (SBB)

Skill-based behavior governs highly practiced, familiar, and automatic sensory-motor actions that occur with minimal conscious attention. Technicians perform skill-based tasks almost subconsciously. Examples include lockwiring a turnbuckle, installing standard AN hardware, or applying sealant. Because these actions are automated, the technician can simultaneously monitor other environmental factors. However, because attentional monitoring is relaxed, skill-based behavior is uniquely vulnerable to slips (attentional failures) and lapses (memory omissions), particularly when the technician is fatigued or distracted.

2. Rule-Based Behavior (RBB)

Rule-based behavior applies when a technician performs a familiar task or solves a known diagnostic problem by following structured procedures, checklists, task cards, or conditional rules ("if symptom X occurs, execute procedure Y"). Here, conscious cognitive control is engaged to recognize the operational situation and retrieve the appropriate stored rule or maintenance procedure. Errors at this level are rule-based mistakes, which occur when a technician chooses the wrong rule, misapplies a good rule to an inappropriate context, or adheres to an outdated or flawed technical rule.

3. Knowledge-Based Behavior (KBB)

Knowledge-based behavior is triggered when a technician encounters an unfamiliar, novel, or unexpected system fault for which no pre-existing maintenance procedure, rule, or task card exists. At this level, automated skills and standardized rules are useless. The technician must consciously analyze system architecture, formulate mental models, test diagnostic hypotheses, and improvise troubleshooting paths. Knowledge-based performance demands immense cognitive effort, consumes working memory, and is highly susceptible to knowledge-based mistakes driven by cognitive tunnel vision, incomplete mental models, and confirmation bias.

                    COGNITIVE CONTROL SPECTRUM

  Unconscious / Automatic                Conscious / High Mental Effort
<--------------------------------------------------------------------->
SKILL-BASED (SBB)        RULE-BASED (RBB)        KNOWLEDGE-BASED (KBB)
• Automated motor tasks  • Structured rules      • Novel troubleshooting
• Minimal mental effort  • 'If-Then' procedures  • Complex mental models
• Susceptible to Slips   • Susceptible to Rule   • Susceptible to Knowledge
  and Lapses               Mistakes                Mistakes

James Reason's Taxonomy of Unsafe Acts

Building upon Rasmussen's cognitive levels, James Reason organized human actions into a rigorous hierarchical taxonomy that classifies unsafe acts based on two fundamental criteria: intentionality of the physical action and intentionality of the outcome.

                               UNSAFE ACTS
                                    |
         +--------------------------+--------------------------+
         |                                                     |
  UNINTENDED ACTIONS                                    INTENDED ACTIONS
(Execution / Memory Failures)                     (Cognitive / Motivational)
         |                                                     |
    +----+----+                                           +----+----+ 
    |         |                                           |         |
  SLIPS     LAPSES                                     MISTAKES   VIOLATIONS
(Attentive)(Memory)                                       |         |
                                               +----------+         +---------+
                                               |          |         |    |    |
                                             RULE-      KNOWL-    ROUT- SIT- OPT/EXC
                                             BASED      EDGE-     INE   UAT- EPTIONAL
                                             MISTAKE    MISTAKE         IONAL

1. Unintended Actions (Execution and Storage Failures)

In unintended actions, the original plan was sound and appropriate, but the physical execution deviated from intention. The technician knew exactly what should be done, but the action did not proceed as intended.

• Slips (Attentional Failures): Slips occur at the execution stage of an automated physical action. The plan was correct, but an attentional diversion or perceptual confusion causes the physical execution to fail. Common forms include:
  • Capture slips: An intended novel action is "captured" by a heavily practiced, habitual action routine. For example, intending to flip a hydraulic bypass switch to TEST, but habitually flipping it to the standard OFF position.
  • Perceptual slips: Confusing two identically shaped switches, knobs, or fluid lines placed close together.
• Lapses (Memory and Storage Failures): Lapses involve internal failures of memory retrieval or prospective memory. The plan was correct, but a step, item, or verification was omitted. Omissions, many of them memory lapses, are repeatedly found to be the most common type of maintenance error (one airline analysis of 122 errors found 56% were omissions), and interruptions and distractions are frequent triggers. For example, a technician removes a drain plug, gets interrupted by a phone call, and returns to pour new oil into the gearbox without reinstalling the plug.

2. Intended Actions (Planning and Motivational Failures)

In intended actions, the physical actions went exactly according to the person's immediate intent, but the action was either inherently flawed (mistakes) or deliberately departed from approved procedures (violations).

• Mistakes (Planning Failures): In a mistake, the technician executes their intended physical plan flawlessly, but the plan was fundamentally incorrect. The deficiency lies in judgement, perception, or inferential reasoning. Mistakes are categorized into:
  • Rule-based mistakes: The technician recognizes a problem but selects the wrong procedure (e.g., applying the torque values for dry threads when the manual mandates wet/lubricated assembly), applies a bad rule found in an obsolete manual revision, or incorrectly generalizes a valid rule to a variant where it does not apply.
  • Knowledge-based mistakes: In an unfamiliar diagnostic scenario, the technician constructs an inaccurate mental model of the system. For instance, misinterpreting the electronic logic of a digital fly-by-wire flight control computer and cutting a wiring harness wire under the erroneous belief that it carries analog ground.
• Violations (Deliberate Procedural Deviations): Violations represent conscious, deliberate deviations from approved maintenance procedures, company regulations, or airworthiness standards. Unlike errors, violations involve a deliberate choice to depart from the mandated method. Violations are sub-categorized as:
  • Routine violations: Everyday shortcuts and procedural workarounds that have become habitual within a working group. The group normalizes the deviance because "we've always done it this way and nothing ever went wrong," often enabled by lax supervisory enforcement.
  • Situational violations: Deviations driven by acute operational pressures, environmental adversity, or a lack of proper resources. For example, using an open-ended wrench as an improvised drift punch because the certified tool is locked in a distant hangar store and the flight departs in ten minutes.
  • Optimizing violations: Deviations executed for personal convenience, ego gratification, or to finish a shift early (e.g., leaving a structural sealant curing check incomplete to catch the company shuttle bus).
  • Exceptional violations: Rare, unprecedented procedural breaches occurring during acute operational crises or unprecedented aircraft recovery situations.

Implications of Errors

The 9.8 syllabus asks what errors lead to. Most maintenance errors are caught or have no effect, but the same error in a different context can be catastrophic:

Three features make maintenance errors especially serious:

• Delayed effect: The defect usually lies dormant until the aircraft flies, so there is no immediate feedback to the technician.
• Repeated or multiple errors: The same person doing identical tasks can repeat an error on both engines or both sides of the aircraft. Point 145.A.48(c) therefore requires organisations to minimise the risk of multiple errors and of errors being repeated in identical tasks.
• Hidden costs: Beyond safety, errors cause rework, damaged parts, lost aircraft availability, regulatory findings, and loss of reputation.

Error vs. Violation Matrix

Worked Maintenance Scenario: The Elevator Trim Tab Rigging Failure

During a scheduled 1,000-hour airframe inspection on a twin-engine turboprop, a licensed Category B1 engineer was assigned to check the cable tensions of the elevator manual trim tab control circuit.

1. The Slip: While setting up the mechanical tensiometer on the forward control cable, the technician's thumb accidentally nudged the scale multiplier dial from the required 1x scale to the 2x scale—an attentional slip that went unnoticed.
2. The Lapse: As the technician reached for the cable clamping block, a hangar fire alarm sounded for an unannounced evacuation drill. The technician evacuated the hangar for 25 minutes. Upon returning, the technician suffered a memory lapse, forgetting that the tensiometer had not been locked down or re-zeroed, and immediately recorded the cable tension as compliant based on a hasty glance.
3. The Rule-Based Mistake: Noticing that the elevator trim tab pointer sat 1.5 degrees off neutral on the cockpit quadrant, the technician attempted to re-center the rigging. However, the technician consulted an obsolete paper revision of the maintenance manual that applied to pre-modification airframes with inverted bellcranks. Following this obsolete rule, the technician adjusted the pushrod turnbuckle in the wrong direction—a textbook rule-based mistake.
4. The Situational Violation: Realizing the aircraft was scheduled for an engine ground run in 20 minutes and that the proper cable safety-wire pliers were locked inside a colleague's toolbox who had left the hangar, the technician used standard diagonal cutting pliers to twist the turnbuckle locking wire, over-stressing and nicking the safety wire—a situational violation driven by time pressure.

During pre-flight checks, the flight crew noted anomalous trim response. A subsequent quality audit caught the nicked safety wire, the reversed pushrod rigging, and the loose cables, illustrating how all four error categories can intersect in a single maintenance event.

Exam Pitfalls / Common Traps

• Trap 1: Confusing slips with mistakes. A slip is an execution failure where the intention was correct but physical performance failed (e.g., finger slips to the wrong switch). A mistake is a planning failure where the action was executed exactly as intended, but the plan was incorrect (e.g., deliberately selecting a switch believing it to be the correct procedure).
• Trap 2: Assuming violations are always malicious sabotage. In aviation human factors, violations are deliberate procedural departures, but they are rarely committed with intent to cause damage. Technicians frequently commit situational or routine violations in a well-intentioned attempt to get the aircraft dispatched on time.
• Trap 3: Classifying lapses as lack of technical knowledge. A lapse is a failure of memory storage or retrieval (forgetting a step), occurring predominantly during routine tasks due to distraction or interruption. It has nothing to do with technical knowledge or competence.
• Trap 4: Rule-based versus knowledge-based mistakes. If a documented maintenance procedure or recognized rule existed and the technician misapplied it or followed an obsolete version, it is a rule-based mistake. If no procedure existed and the technician had to invent a novel troubleshooting solution using their own reasoning, it is a knowledge-based mistake.