IL Elevator Mechanic common mistakes
IL Elevator Mechanic · Understand the traps and how to avoid them.
Answering code questions from memory of how a job was wired in the field instead of citing the actual code section, so the answer reflects local practice rather than the adopted code.
Most candidates learn on installations governed by a locally amended code and a specific code edition; exam items are written against a named edition, and the local habit can differ on clearances, wiring methods, or required devices.
What to do instead
Before answering any code item, identify which code edition the exam names, then practice by looking up each rule in that edition's table of contents and index until you can locate sections in under a minute. Keep a one-page map of the chapters you use most, and note where your local amendments diverge so you consciously set them aside.
Confusing the minimum required overhead, pit, and runby clearances, or applying the wrong clearance to the wrong condition (occupant clearance versus equipment clearance versus refuge space).
These values are similar numbers attached to different conditions, and candidates memorize a single figure rather than the condition that triggers it; the exam deliberately pairs a scenario with a near-miss value.
What to do instead
Build a comparison table with columns for the condition, the required dimension, and the code section, and fill it from the code text rather than from notes. Then write your own scenario questions that each hinge on one condition, and check every answer against the table.
Treating hydraulic and traction systems as interchangeable when answering questions about stopping, leveling, or what happens on power loss, giving a traction answer to a hydraulic scenario.
Both drive types share door operators, controllers, and fixtures, so the distinguishing behaviour is easy to blur; candidates also overgeneralize from the equipment they service most.
What to do instead
For each drive type, write a short narrative of what occurs from the moment power is lost through the stop: valving and check valve behaviour for hydraulic, brake and machine inertia for traction. Practice classifying a scenario as hydraulic or traction from its symptoms before answering, and state the mechanism in one sentence before choosing an option.
Mixing up rope reeving and suspension relationships, such as assuming car speed equals rope speed or misstating how 2:1 roping changes travel, load, and rope movement.
Reeving is usually learned by looking at a machine, and the arithmetic is rarely practiced in isolation; exam items test the relationship numerically and conceptually.
What to do instead
Redraw 1:1 and 2:1 reeving from scratch and derive the relationships yourself: for a given car travel, how far the rope and piston or drum move, and how tension divides. Then solve several numeric problems with invented values and verify each against your diagram.
Answering electrical items using wiring colors or terminal numbering remembered from one manufacturer's controller rather than the standard conventions the exam tests.
Technicians memorize the panel in front of them; manufacturer designations vary, and the exam asks about conventions and safe practice rather than a specific product.
What to do instead
Separate the two bodies of knowledge on paper: universal conventions (grounding and bonding, conductor identification, disconnecting means) versus product-specific labeling. Study the universal set from the code and standard wiring practice, and treat any manufacturer numbering you know as a personal note that must not drive an exam answer.
Describing a troubleshooting sequence that begins by probing live circuits or swapping parts, rather than isolating, locking out, and verifying the fault before replacement.
Under time pressure, experienced candidates jump to the failure they have seen before, and exam scenarios reward a defensible sequence rather than a lucky guess.
What to do instead
Practice writing a five-step diagnostic sequence for each common symptom (car will not start, door will not close, leveling drift) that starts with verification and isolation and ends with a functional test after repair. Answer sequence questions by ordering the steps first, then reading the options.
Confusing the roles of the safety devices: which device is the final overspeed protection, which prevents unintended motion, which detects slack or broken suspension, and which is a door protective device.
Device names overlap in casual speech, and several devices act on the same machine, so candidates attribute one device's function to another.
What to do instead
Make a device table with three columns: what it senses, what it acts on, and what condition it protects against. Fill one row per device from the code and standard, then cover the middle column and quiz yourself until you can state each device's action without hesitation.
Skipping the required test steps or acceptance criteria for safety devices, such as describing a governor test without the tripping speed relationship or a buffer test without the required conditions.
Candidates know the device exists but have not rehearsed the test procedure and its pass criteria, which is exactly what inspection items ask for.
What to do instead
Write out each periodic test as a numbered procedure with the setup, the measurement, and the acceptance criterion. Rehearse them aloud as if explaining to an inspector, and mark any criterion you cannot state precisely for focused review.
Answering maintenance items with a task list but no intervals or triggers, or stating intervals from a single building's practice rather than from the code and standard requirements.
Real maintenance schedules are customized per installation, so candidates remember what their route looked like rather than the minimum required frequency and the conditions that change it.
What to do instead
Build a maintenance matrix of task, minimum required interval, and the condition that prompts additional attention (usage, environment, observed wear). Study the code and standard text for the required frequencies, and practice distinguishing required minimums from recommended good practice.
Approaching inspection scenarios as pass or fail without stating the deficiency category, the code basis, and the corrective action, so the answer is incomplete even when the defect is identified.
Field inspections end in a conversation, not a multiple-choice selection; candidates identify the problem but have not practiced framing it in the structure the exam expects.
What to do instead
Practice writing inspection findings in a fixed three-part format: the observed condition, the requirement it violates with its section, and the corrective action with any retest required. Do this for a set of common deficiencies until the structure is automatic, then apply it when reading scenario options.