The brake alarm was disabled. The maintenance system knew.
- Safety Jon
- 2 minutes ago
- 6 min read
A runaway prime mover and trailer travelled approximately 140 metres through fences, across a road and into neighbouring businesses. The immediate error occurred in the cab, but the organisational failure had been documented months earlier.
On 20 Sep 23, a driver parked a 2021 Kenworth prime mover and attached tipper trailer on sloping ground at a civil construction site in Totness, in the Adelaide Hills.
The driver left the vehicle without applying the park brake.
The unattended combination rolled across the worksite, continued down a paddock, passed through fences and crossed a public road before crashing through an industrial building. Four businesses sustained property damage, a specialist vehicle restoration business was partially demolished, and a worker escaped being struck when the truck came through the wall.
Nobody was physically injured. The South Australian Employment Court nevertheless found that the foreseeable consequences included multiple fatalities.
The control was installed, then allowed to become useless
The truck had an audible warning system intended to sound when the cab door was opened without the park brake engaged. That engineering control did not operate because the horn relay had been removed.
The problem was not discovered after the incident as some obscure electrical fault.
Routine servicing in June and August 2023 had identified that the relay was missing, and both service reports recommended further investigation.
Schwarz Excavations and Civil Pty Ltd did not act on either warning. The incident occurred on 20 Sep 23, several weeks after the second service report.
The company was subsequently prosecuted by SafeWork SA and pleaded guilty to failing to comply with its health and safety duty under section 19 of the Work Health and Safety Act 2012 (SA). On 30 Jul 26, the company was convicted and fined $140,000, with additional orders for a $451 Victim of Crime Levy and a $1,210 contribution towards SafeWork SA’s legal costs.
The court adopted a starting penalty of $200,000 before applying a 30 per cent reduction for the early guilty plea and demonstrated contrition. Deputy President
Lieschke assessed the objective seriousness of the offence as moderate to mid-range. SafeWork SA’s prosecution summary records that the risk to people was high because the work occurred on elevated land above an established industrial area.
This was not simply a driver forgetting the park brake
The driver’s failure to apply the brake was the immediate act that released the vehicle.
Treating that as the complete explanation, however, would remove nearly everything operationally useful from the incident.
The company had already recognised that drivers can make this mistake. It had installed an audible warning system specifically to detect the condition and alert the driver before leaving the cab.
That control was then disabled. Two maintenance reports identified the problem, yet the information did not result in the vehicle being repaired, isolated, restricted or subjected to compensating controls.
The court found that the company had safety policies, daily pre-start requirements and a stated commitment to safety. Those arrangements failed at the point where maintenance intelligence needed to become an accountable action.
Deputy President Lieschke described the company’s approach to obtaining maintenance reports as “ad hoc”. The court’s conclusion was blunt: comprehensive written policies and good intentions had fallen short of practical compliance.
A service report is part of the risk-control system
Vehicle maintenance is not merely an arrangement between the workshop and accounts payable. Where a service report identifies a defect affecting a safety device, the report becomes operational risk information requiring assessment, ownership, action and verification.
In this case, the service provider’s invoices passed through a third-party financial arrangement. According to a published summary of the decision, detailed maintenance recommendations were not passed to the company through that process, and the missing reports were only obtained after the incident.
That does not transfer the duty to the workshop, finance provider or driver. A business responsible for heavy vehicles must have a dependable process for receiving complete service findings, identifying safety-critical defects and confirming that corrective work has been completed before the vehicle continues operating.
An invoice marked as paid is not evidence that the vehicle is safe. A completed service is not evidence that every identified defect was repaired.
Pre-starts cannot compensate for weak maintenance assurance
The company also required drivers to complete electronic pre-start checks. A case summary reports that the driver’s last recorded check, completed two days before the incident, marked the warning devices as serviceable, while no pre-start was completed on the day of the incident or the preceding day.
Management reportedly reviewed pre-starts when a driver recorded a fault. That creates a closed loop only when the check is completed, the relevant function is actually tested, the driver recognises the defect and the defect is honestly entered.
A ticked box cannot verify a warning device that has not been functionally tested. Nor can a manager respond to an omitted check if the system does not flag the omission.
Pre-start inspections and scheduled maintenance perform different functions. One does not excuse failure of the other, and neither is useful if exceptions disappear into the system without review.
An engineering control needs an owner
I have implemented in-cab audible park brake alarms through consultation with operational leaders and frontline drivers. They are a practical control because they intervene at the precise point where a parking error can become a runaway.
They are not infallible. A disconnected relay, failed switch, muted buzzer or warning that drivers have stopped noticing can quietly turn an engineering control into cab decoration.
The control therefore needs an identified owner and a defined assurance method. The organisation must know how the warning is functionally tested, how defects are reported, who has authority to isolate the vehicle, what temporary controls are permitted, who approves its return to service and how overdue corrective actions are escalated.
Without those elements, the organisation has purchased a device rather than implemented a control.
What a defensible rollaway prevention system should address
A practical system should specify how vehicles are parked on slopes and other elevated areas, including site selection, park brake application, transmission or gear selection and the use of wheel chocks where required by the assessed conditions. It should also account for whether an uncontrolled vehicle could reach workers, public roads, occupied buildings or other vulnerable areas.
The system should require functional testing of park brake warning devices rather than a generic inspection of “warning equipment”. Missing pre-starts, reported defects and inconsistent results should generate visible exceptions requiring review.
Maintenance reports should be received in full, regardless of whether servicing and payment are managed through another entity. Safety-critical findings should be classified, assigned, tracked to closure and independently verified before the vehicle is released.
Supervisors and fleet managers also need clear isolation authority. Production pressure has an impressive ability to convert “repair immediately” into “keep an eye on it”, usually without producing any actual eyes.
Questions for the operation
Does the pre-start require the park brake warning to be functionally tested, or does the driver merely tick a general warning-device box?
What happens automatically when a required pre-start is not completed, and who reviews that exception?
Does the business receive the complete service report and technician recommendations, including where invoices pass through a finance or fleet-management provider?
Which defects require immediate vehicle isolation, and can drivers and supervisors exercise that authority without seeking commercial approval?
Are safety-critical defects tracked through to verified closure, or does the system treat the workshop invoice as proof of completion?
Has the organisation assessed where an unattended vehicle could travel from sloping parking areas, including beyond the formal workplace boundary?
The lesson
The driver forgot the park brake, but the organisation had already anticipated that human error and installed a control. The prosecution followed because the control was allowed to remain disabled after two separate maintenance warnings.
This was not a hidden hazard or an unforeseeable equipment failure. The information existed, the control existed and the opportunity to intervene existed, but the system did not connect them before the truck started moving.
Good safety systems do not merely collect information. They make unresolved risk difficult to ignore.
Sources
Safety Jon commentary is general information and does not replace legal advice or a task-specific risk assessment.
Comments