INRAT-H common mistakes
INRAT-H · Understand the traps and how to avoid them.
When a scenario describes a shift handover where the outgoing operator gives a confident verbal summary but the written log is incomplete, candidates blame the individual operator's carelessness and stop there, missing the systemic breakdown in the handover procedure.
Candidates tend to default to person-centred blame because it is the fastest explanation and feels decisive under time pressure; they have not practised pushing past the first plausible cause to the procedural and organisational layers.
What to do instead
Before answering, force a three-layer pass: write down one individual, one procedural, and one organisational contributing factor for the scenario, then choose the option that addresses the layer the question actually asks about. Practise on five handover vignettes until the layered habit is automatic.
Candidates treat the three vigilance decrement explanations (sensitivity loss, criterion shift, expectancy/attention) as interchangeable and pick whichever sounds most intuitive, rather than matching the described detection pattern to the correct mechanism.
The mechanisms produce superficially similar outcomes (fewer detections over time), and candidates memorise the labels without learning the diagnostic signature that distinguishes them.
What to do instead
Build a comparison table with one column per mechanism and rows for: what happens to hit rate, false alarm rate, and response criterion over time. Learn the signature pattern for each, then apply it to signal-detection-style vignettes.
On workload questions, candidates equate high workload with high stress and choose 'reduce workload' as the fix even when the scenario describes underload, boredom, or complacency in a highly automated control room.
The stress-workload association is strong in everyday thinking, so candidates apply a mental shortcut that ignores the inverted-U relationship and the distinct failure modes of low workload.
What to do instead
For every workload item, first classify the scenario as overload, optimal, or underload using concrete cues (task queue length, time available, reported boredom, monitoring-only tasks). Choose remedies that match the classification, and rehearse the underload cues explicitly.
Candidates answer control room design questions from general aesthetic preference ('this layout looks cleaner') instead of applying specific human factors principles such as alarm prioritisation, display proximity, or compatibility of movement.
Without a rehearsed checklist, candidates fall back on lay intuition about what looks organised, and exam distractors are deliberately written to sound like sensible design taste.
What to do instead
Memorise a short principle checklist (importance-frequency grouping, compatibility, feedback, alarm hierarchy, glare and lighting, reach and sight lines) and verbally justify each answer by naming the principle it satisfies or violates before selecting.
In crew resource management scenarios, candidates select the option that resolves the immediate technical problem fastest, overlooking that the question is testing whether the junior crew member asserts a concern and whether the leader invites and acts on it.
Technical problem-solving is over-trained relative to non-technical skills, and the assertive communication option often looks slower or more confrontational than just fixing the issue.
What to do instead
When a scenario contains a hierarchy or a dissenting crew member, scan first for the communication behaviour being tested (briefing, callout, challenge-and-response, closed-loop confirmation) and evaluate options on that dimension before technical efficiency.
Candidates describe fatigue countermeasures only as 'get more sleep' and fail to distinguish acute sleep loss, cumulative sleep debt, circadian misalignment, and time-on-task effects when the scenario points to one specific mechanism.
Fatigue is treated as a single folk concept, so candidates do not hold the separate mechanisms in mind and cannot map scenario details (e.g. night shift, long duty, short sleep before day shift) to the right cause and countermeasure.
What to do instead
Learn a four-category fatigue taxonomy with one distinguishing scenario cue and one matched countermeasure each, then practise classifying ten short vignettes by category before choosing an answer.
On event investigation items, candidates stop at the immediate technical cause and select it as the root cause, rather than tracing the causal chain to the latent organisational conditions the question is probing.
The proximal cause is vivid and concrete in the scenario, while latent conditions are described more abstractly, so the concrete option feels more defensible.
What to do instead
Apply a fixed causal chain: trigger, active failure, local workplace conditions, organisational factors. Eliminate any option that names only the trigger or active failure when the stem asks for root cause or systemic contributors.
Candidates confuse the purpose and content of different training and competence instruments, for example treating a refresher requirement, a simulator assessment, and a licence renewal as interchangeable, and pick an option that applies the wrong instrument to the described situation.
The instruments share vocabulary (training, assessment, competence, licence) and candidates learn definitions in isolation without comparing scope, frequency, and authority.
What to do instead
Create a matrix of instruments with rows for purpose, who conducts it, frequency, and outcome (pass/fail, licence action, remedial training). Answer by locating the scenario in the matrix rather than by keyword matching.
Candidates answer attention and perception items by assuming operators see what is physically present on the display, ignoring expectation-driven inattentional blindness, change blindness, and top-down perceptual set described in the scenario.
Naive realism makes it feel obvious that a displayed indication would be noticed, so candidates underweight the scenario details about expectation, high task load, or a non-salient change.
What to do instead
When a scenario mentions a missed indication, explicitly ask: what was the operator expecting, what was salient, and what change occurred without a transient cue? Choose the option consistent with expectation-driven selection rather than display availability.
On human reliability and error classification items, candidates label every unintended action as a slip and every mistaken belief as a lapse, without applying the skill-rule-knowledge distinction or separating slips from mistakes.
The taxonomy terms are learned as loose synonyms, and candidates do not rehearse the defining question of whether the intention itself was correct.
What to do instead
Memorise the single discriminating question: was the intended action correct (execution error: slip or lapse) or was the intention itself wrong (mistake: rule-based or knowledge-based)? Apply it aloud to each option before eliminating.