Three dangerous incidents, and two were vehicles that nearly met

The edition summarises three incidents in detail, and all three are classed as dangerous incidents, the high-potential category a mine must report whether or not anyone was hurt. At an underground metals mine, a drill rig was working at an intersection when its boom struck the windscreen of a light vehicle. On the regulator's account the rig operator had seen a truck, directed it to reverse, then moved forward without noticing a light vehicle coming down the ramp ahead; the collision was stopped only when the light-vehicle operator called out. The regulator's advice is about positive communication between mobile plant, the discipline of the caller and the receiver each identifying their vehicle and confirming the move before anyone proceeds, and it points operators to the operating-compliance layer of its layered-defence guidance for vehicle interactions.

At an open cut coal mine, on a night shift in dusty conditions, a dozer and a haul truck reversed toward each other on a ramp and the dozer's ripper box made contact with two of the truck's tyres. The regulator ties the incident to lighting: poorly positioned lighting plant left the truck operator without a clear picture of what was behind and around the machine, and its advice is that lighting plants must be placed to avoid glare and shadowing of the work area, alongside the operator advisory controls, proximity alerts that warn when a vehicle is closing on another object or a person, in the same layered-defence framework. Two vehicles, one dark and dusty ramp, and no reliable way for each operator to know where the other was.

The third incident is a different failure but a familiar root. At an underground metals mine a light vehicle operator saw flames coming from a rear wheel while driving out of the mine. The cause the regulator records is a speed sensor that had snapped off and was leaking oil onto the hot sealed integrated braking system unit. Its recommendations are about change management: when plant is modified away from the original manufacturer's design, a formal process should assess the new hazards the modification introduces, from brakes dragging to sudden lock-up, and maintenance should stay within the manufacturer's specifications. A small modified part, an unassessed consequence, and a fire on a moving vehicle underground.

The thread the regulator keeps pulling: control of movement

Read one week's edition and it is three unrelated events. Read the run of them and the same hazard keeps surfacing: mobile plant and vehicles moving in a way, or a direction, no one intended. The week ending 19 June detailed a reversing van with no working reversing alarm or camera and a haul-truck near miss at an intersection. The week ending 26 June detailed two separate haul-truck steering failures and a reversing articulated-truck collision. The week ending 3 July detailed a haul truck reversing into a dozer. The week ending 10 July detailed a loader work platform that crowded down on its own and threw two workers. This week it is a boom into a windscreen at an intersection and two machines reversing toward each other in the dark. Five weeks, and vehicle interaction or unplanned plant movement is in every one. It is why the regulator keeps returning to the same controls: its layered defence for vehicle interactions, collision-avoidance and proximity technology, lighting and communication protocols, and change management on modified plant. For a general-industry duty-holder the hazard is not exotic and the parallels are direct: reversing plant in a yard, a blind loading-dock corner, a forklift and a pedestrian sharing a route, a modified machine no one reassessed. Our pages on machinery and plant safety and warehouse and forklift safety cover the same controls in general terms.

The count in context: 38 is flat on the week before

Thirty-eight reportable incidents is one more than the 37 of the previous week, which is to say flat; the raw number moves around week to week and a single-figure change should not be read as anything. The last five editions run 20 (week ending 19 June), 42 (26 June), 31 (3 July), 37 (10 July) and 38 (17 July), an average of about 34 a week. The summary's own footnote is the reason not to over-read any single week: incidents are recorded when they are notified and have not necessarily all occurred within the seven days named, so the weekly figure is a reporting tally, not a count of events that physically happened in that week. What the number does reliably show is a steady, high cadence of mandatory notification, which is the point of the system: near misses and dangerous incidents reaching a regulator and coming back out as public advice.

What got spotlighted: near-misses, not a fall in injuries

The honest comparison with last week is narrow, and it runs the other way from the fortnight before that. The three incidents the regulator chose to detail on 10 July put three workers in hospital between them; the three it chose to detail this week hurt no one that the summary records. That is a change in the severity of what was highlighted, not evidence that injuries fell across all 38 incidents, because the detailed entries are a curated selection by the Chief Inspector, not a statistical sample of the week. The useful takeaway for a duty-holder is not in the count and not in the injury tally. It is in the recommendations, which this week are specific and transferable: make positive, confirmed communication between mobile plant a rule and not a courtesy; light and lay out shared vehicle routes so every operator can see what is around them; fit and use proximity detection where people and plant mix; and never let a machine run modified from its design without reassessing what the change broke. If your own site ran the same three events, would each generate a report, an investigation and a changed control, or a near miss quietly forgotten by the next shift?

Methodology

The incident count, all three incident accounts and the recommendations to industry are from the NSW Resources Regulator's Weekly incident summary for the week ending 17 July 2026 (the same weekly series, ISSN 2982-1010), read in full; the recommendations are summarised in our words from the regulator's published advice rather than quoted. The five-week counts (20, 42, 31, 37, 38) are read from the successive weekly editions for the weeks ending 19 June, 26 June, 3 July, 10 July and 17 July 2026 respectively; the 17 July edition was the most recent available at publication. The regulator publishes incidents at operation-type level with no operators, sites or individuals named, and we have added no identifying detail. The summary's own caveat applies: incidents are mostly recorded within a week of the event but are not necessarily all from the seven days named, and all newly recorded incidents are reviewed weekly by the Chief Inspector. The earlier weeks' detailed incidents referenced in the pattern section are drawn from those editions. The regulator's site moved from resourcesregulator.nsw.gov.au to resources.nsw.gov.au during 2026.