Scope note: no issuer, exam format, or official syllabus has been established for this catalog label, so this guide teaches the subject itself and marks every scenario as a paper exercise rather than an official preparation blueprint. Inside: the road-versus-rail mode map, two worked decision scenarios (on-tracking and a facing switch), the distinction between authority and protection, inspection and log-writing practice, a ten-point scored walkthrough, and an adaptable preparation sequence with readiness checks.
What Actually Changes When Road Wheels Meet the Rail
In rail mode, flanged guide wheels clamp the rail heads and steer the vehicle while road tires carry its weight; steering, speed basis, and your standing on the network all shift from road logic to rail logic.
In the common arrangement, hi-rail gear places two flanged steel guide wheels against each rail head, ahead of and behind the road wheels on each side, held by hydraulic force and locking pins. Once deployed, the road tires ride the rail top and carry the load while the guide wheel flanges hold alignment in the grooves. The rail now chooses your path: large steering inputs achieve little and can fight the gear at speed, so corrections become small and early rather than continuous.
Separate what transfers from what does not. Vehicle checks, load security, and observation habits carry over; steering technique, braking reference, speed basis, and legal standing do not. On rail you are rail traffic working under a track access authority, not a general road user. Before drilling procedures, build the two-column map in the table below and keep it beside every practice scenario — each case should be answerable by asking which column the decision belongs to.
| Aspect | Road mode | Rail mode |
|---|---|---|
| Steering | Front-wheel steering on pavement | Rail geometry steers; guide wheel flanges hold alignment |
| Speed basis | Road speed limits and traffic | Access conditions, machine rating, and track features govern speed |
| Standing on the network | General road user | Rail traffic under a track access authority |
| Braking reference | Tire grip on pavement | Steel contact; adhesion varies with rain, leaves, and grease |
| Key pre-move check | Mirrors and road conditions | Authority confirmed, gear engaged and locked, track ahead clear |
On-Tracking: Why Partial Engagement Becomes an Emergency
On-tracking converts the vehicle at an approved location. The sequence protects you only if each step completes — authority confirmed, vehicle square, gear seated, pins locked, brake tested — before the first rail movement begins.
Paper scenario: you stop beside a straight, level section on a narrow shoulder and swing the vehicle onto the rail at an angle to save space. You deploy the gear, glance at the indicator, and ease forward while still copying the authority message. The plausible mistake is overlap: positioning, deployment, communication, and movement compressed into one blur, so a partly seated guide wheel meets the first rail joint while still settling.
The better decision treats deployment as a stop-and-complete event: bring the vehicle to rest square to the rail, confirm the authority limits by reading them back, deploy and verify full seating with locking pins checked, then test the brake at walking pace before increasing speed. It matters because a guide wheel that is only partly seated can climb at the first rail joint, and a climb may only become obvious once the vehicle's full weight arrives on the gear.
Facing Versus Trailing Moves Through a Switch
A facing move meets the points point-first, so the blades choose your route; a trailing move converges behind you. Each direction demands a different verification before you commit the guide wheels.
Paper scenario: approaching a facing switch in rail mode, you assume the blades are set for the main line because a controlling party manages routing, and you pass over at normal rail speed. The mistake is treating routing as someone else's completed task. Better: stop short of the fouling point, verify the blades match your intended route and are secured, confirm with the controlling party, then pass at the reduced speed the feature demands — a wrong-route facing move can put you on a line you hold no authority for.
Trailing moves carry a different failure: the route is fixed behind you, but blades set against your movement can be picked or damaged by the flange striking the back of the blade. Check points set for the move before trailing, especially after another vehicle has passed, and remember that a reverse movement crosses the same points facing. On a paper diagram, trace the line a guide wheel flange would run: through a facing move it rides the blade taper; against a trailing move it strikes steel.
Authority and Protection: Becoming Known on the Rail
Rail presence is two tasks: holding permission to occupy the track and running the protection your access arrangement specifies. Neither substitutes for the other, and signalling detection must never be assumed.
Distinguish the named concepts. Authority is a defined permission with stated limits — a location and window — obtained through the access process and confirmed by reading the limits back; you operate inside them and stop short when unsure. Protection is the arrangement of lookouts, warnings, or blockage that keeps other movements away from your work area. In scenario answers, name which one each step serves: requesting authority is not setting protection, and a protected site still needs the permission held.
Detection deserves care: steel wheels commonly shunt track circuits, which can display your occupation to the controlling system, but behaviour varies with vehicle equipment and track conditions, so treat it as unverified. Report on-tracking, position updates, and off-tracking to the controlling party and log the times, so your presence rests on communication and record rather than assumption. Between calls, stop clear of junctions, crossings, and other fouling points so the line stays usable.
Pre-Deployment Checks and the Log That Follows Them
Inspection and documentation are one skill in two parts: find the defect that matters for rail mode, then record and report it so the machine's status is unambiguous for the next operator.
Walk-around items specific to rail mode include hydraulic hoses and cylinders for the gear, locking pins and retainers, guide wheel flange wear or cracks, and road tire condition with correct pressure — the tires carry the machine's weight on the rail head. Add lights, audible warnings, and radio function. A defect in the gear itself removes the machine from rail mode until it is cleared through the reporting process; a tagged fault must stay tagged.
Log entries should let a stranger reconstruct the shift: on- and off-tracking times and locations, the authority reference you worked under, compliance with restrictions, defects with clear descriptions, and near misses. Write what, where, when, and who was informed. Practise by drafting a log line after every scenario you complete — the discipline of one accurate sentence per event is exactly what written case answers and real shift records both reward.
Paper Exercise: On-Tracking Walkthrough With a Scored Rubric
Run a written walkthrough under a ten-point rubric: the goal is justifying each checkpoint, not reciting it, because written case answers reward reasons attached to steps.
Draw a plan with two running lines, a siding, an approved on-track point beside the near line, and a facing switch some distance ahead in your direction of travel. The task: you are called to inspect track several kilometres ahead inside a stated work window. Write every step from stopping on the shoulder to your first rail movement, naming who you inform and what you physically verify at each point.
Score each checkpoint zero to two: zero if missing, one if mentioned without a reason, two if justified. A total of sixteen or more across repeated runs indicates sequence fluency — a study milestone, not a pass prediction. Audit your first attempt for steps that are easy to drop when writing quickly: the brake test after deployment, the read-back of authority limits, and the switch verification ahead. A second run that fixes exactly those gaps is diagnostic rather than a formality.
- Authority limits confirmed and read back before the vehicle nears the rail
- Vehicle square to the track at the approved on-track point
- Gear deployed with full seating verified and locking pins checked
- Low-speed brake test completed before normal rail speed is used
- Facing switch ahead verified set and secured for the intended route
- Controlling party informed of on-tracking; times and location logged
An Adaptable Preparation Sequence and Readiness Checks
Study moves from concepts to decisions: build the boundary map, trace wheel paths on diagrams, drill sequences from memory, then run mixed scenarios with written justifications and finish each case with a log entry.
Phase one covers vocabulary and the boundary map: mode changes, facing versus trailing, authority versus protection. Phase two is diagram work — draw plain track, both switch directions, and a crossing, tracing guide wheel paths. Phase three mixes scenarios so each case pairs one mechanical fault, one track feature, and one communication task; write the decision plus the reason. Phase four adds a drafted log line per case. Scale phase lengths to the weeks you have rather than fixed daily targets.
Readiness is demonstrable, not felt. Check that you can write the on-tracking sequence unaided with the authority and engagement steps intact; explain the different checks a facing and a trailing move require; complete a mock log a third party could reconstruct; and rework one scenario you answered badly, naming the decision you changed. If a check fails, return to the matching phase — diagrams for track features, memory drills for sequences, scenario sets for judgement.