On 22 December 2020, the pilot of a Robinson R44 II helicopter was conducting aerial agricultural spray operations on a property about 13 km south-east of Clare Valley Aerodrome, South Australia. After completing numerous spraying runs throughout the morning, the pilot started a gentle descending turn to the landing site to replenish with chemical product when a loud bang emanated from the rear of the helicopter. The pilot reported that the helicopter descended rapidly, and the flight controls appeared to be jammed. The helicopter collided heavily with the loading vehicle, coming to rest on its side. The pilot and ground crewman were uninjured, and the helicopter was substantially damaged.
What the ATSB found
The ATSB found that the forward yoke of the helicopter’s clutch shaft had failed due to an undetected fatigue crack that originated from an indent in one of the arms of the yoke. This resulted in loss of drive to the main and tail rotor systems. The unrestrained clutch shaft caused the displacement of the hydraulic reservoir and the loss of fluid. The loss of hydraulic fluid removed hydraulic power assistance to the flight control servos leading to increased control stick forces to operate the helicopter.
The pilot experienced difficulties in controlling the helicopter and executed an emergency descent from a low height without hydraulic power assistance and no tail rotor control. The pilot was presented with a compound emergency for which no training had been provided and for which they had no prior experience.
The ATSB found that the helicopter manufacturer’s maintenance instructions requiring verification that no cracks, corrosion or fretting were present on the yoke, lacked specific instructions on the method to be employed. The visual inspection that was employed increased the risk that a crack in the yoke arm may not be detected.
What has been done as a result
The helicopter manufacturer, the Robinson Helicopter Company, introduced new maintenance inspection requirements for the clutch shaft forward yoke at the 2,200/2,400-hourly inspection for the R44 helicopter. This included replacement of yokes of earlier revision status (A through G) and for later revision (H and subsequent), the option of replacement, or a more detailed examination that included a magnetic particle inspection. This update was included in the R44 maintenance manual in August 2022. The manufacturer also changed the paint colour of the yokes at the forward flex coupling from dark grey to white. This was to enhance the visibility of fretting dust during inspections, in the event of loose hardware.
Following the accident, the ATSB issued a Safety Advisory Notice, AO-2020-064-SAN-014 advising operators of R44 helicopters that based on the preliminary finding of fatigue cracking, to look for the presence of corrosion, fretting or cracking, which may not be visually obvious during all inspections of the clutch shaft yoke.
The Civil Aviation Safety Authority issued an Airworthiness Bulletin, AWB 63-010 advising industry of the failure of the yoke based on the ATSB investigation preliminary finding. It advised pilots and maintenance personnel to exercise vigilance for any signs of deterioration in the helicopter drive train components. This was further supported by the release of similar bulletins by the European Union Aviation Safety Agency and the US Federal Aviation Administration.
Safety message
This occurrence highlighted how non-life limited components such as a drive train yoke may still develop defects and fail in-flight. Aircraft owners and maintenance personnel are reminded of the importance of applying inspection and maintenance criteria specified in the aircraft manufacturer’s publications. Should maintenance information be lacking or unclear, the manufacturer or authorised representative should be contacted for appropriate, additional information.
The occurrence also serves as a reminder to pilots and maintenance personnel that when conducting inspections to be prepared for the unexpected, and to remain vigilant for defects in parts with an established history of reliability.
The occurrence
On the morning of 22 December 2020, the pilot of a Robinson Helicopter Company R44 II, registered VH-HOB, prepared the helicopter for aerial agricultural spray operations to be conducted on a property located about 13 km to the south-east of Clare Valley Aerodrome, South Australia. The pilot completed the daily inspection and departed the Clare Valley hangar at 0652 Central Daylight-saving Time[1] for the short flight to the loading zone, from where operations would be based.
The pilot arrived at the loading zone at 0700 and departed at 0702 with the property owner on board to conduct a short survey flight of the area to be sprayed, returning to the loading zone at 0708. Following the arrival of the ground crewman, the helicopter was loaded with chemical product, and at 0728 the pilot departed and conducted a series of spraying runs.
Numerous spraying runs were completed during the morning between 0728 and 0920 with the pilot returning to the loading zone periodically to replenish with chemical product and to refuel the helicopter. The pilot reported that the operation proceeded smoothly, and the long spray runs with minimal obstacles made for ideal spraying conditions.
During the final descent to the loading zone at about 0926, the pilot momentarily increased altitude to gain a better view of a light shower approaching from the south-west, and to assess its potential impact on further spraying operations. The pilot slowed the helicopter, and once satisfied that the shower did not pose a threat, started a gentle, right descending turn at 0926:20 towards the ground loading vehicle with the intent to land alongside as on previous occasions (Figure 1).
Figure 1: VH-HOB flight path showing return to loading zone and descent and inset providing accident location
Source: Google and DGPS data, annotated by the ATSB
About 10 seconds into the turn, at 0926:30, a loud bang from the rear of the helicopter was heard, followed by vibrations from the rotor systems. The ground crewman recalled looking up and seeing that the tail rotor had stopped turning. The pilot reported that the cockpit flight controls appeared to have jammed and of not being able to move the tail rotor pedals. The helicopter’s rate of descent increased to 550 ft/min and as reported by the pilot, its movement towards the ground loading vehicle was generally unaffected by the pilot’s attempts at control inputs. The helicopter’s flight path continued until its landing gear impacted the vehicle’s roof, which resulted in it rolling onto its right side and colliding with terrain at 0926:46.
The pilot was not injured in the collision and was assisted from the helicopter wreckage by the ground crewman. There was no post-impact fire, and the helicopter was substantially damaged.
Context
Pilot information
The pilot of VH-HOB held a Commercial Pilot Licence (Helicopter) and a Private Pilot Licence (Aeroplane), both issued in March 2015. The pilot held class ratings included single engine helicopters and helicopter low-level rating. From 2017, the pilot also held an aerial application rating for helicopter operations.
The pilot completed an aerial application proficiency check for single engine helicopters and a night Visual Flight Rules (Helicopter) flight review for Robinson R44 helicopters on 23 July 2020. Both were valid until 31 July 2021.
The pilot held a Class 2 Aviation Medical Certificate issued by the Civil Aviation Safety Authority (CASA), without medical restrictions, which was valid until 23 January 2023.
The pilot’s logbook indicated that at the time of the accident, the pilot had a total flying experience of about 6,521 hours. Of these, about 1,337 hours were in the Robinson R44 helicopter and 1,018 hours conducting aerial application work. The pilot had flown about 105 hours on type in the previous 90 days, and about 54 hours on type in the previous 30 days.
Aircraft information
VH-HOB was a Robinson Helicopter Company R44 II helicopter that was manufactured in the United States in 2005 with serial number 10801. It was first registered in Australia in 2005.
The R44 II is a single-engine, light utility and training helicopter with a semi-rigid, two-bladed main rotor, a two‑bladed tail rotor and skid type landing gear. It had an enclosed cabin with two rows of side‑by‑side seating for a pilot and three passengers.
The helicopter was powered by a Textron Lycoming IO-540-AE1A5, 6-cylinder, fuel-injected piston engine and was fitted with hydraulic servo-actuators providing hydraulic power assistance to the main rotor, flight control system.
VH-HOB was configured for aerial application work that included a belly-mounted storage tank and laterally mounted spray booms for chemical product dispersal.
The helicopter’s current maintenance release was issued on 20 October 2020, about 92 flight hours prior to the accident. It was valid for 12 months or 100 hours, whichever occurred sooner. At the time of the accident, VH-HOB had accumulated about 4,579 hours, total time-in-service. There were no open defects recorded on the maintenance release and no outstanding or overdue maintenance was noted.
Maintenance records also showed that about 188 flight hours prior to the accident, at an aircraft time-in-service of 4,391.0 hours, an airframe 2,200-hour/12-year inspection was completed.
Meteorological information
The forecast meteorological conditions for Clare Valley Aerodrome (13 km north-west of the accident site) area, indicated winds from the south-south-west at 19 kt and a temperature of 12 ⁰C. Visibility was forecast to be greater than 5 km with isolated showers of rain and broken cloud above 1,200 ft.
The METAR[2] for Clare Valley township issued at 0930 recorded wind from the south-west at 7 kt and a temperature of 14 ⁰C. This was consistent with witness in the accident area who reported that some cloud was present with isolated showers to the south.
Wreckage information
The ATSB did not attend the accident site and based assessment of the helicopter on imagery and reports supplied by the operator, maintenance personnel, interview records and witness account.
The helicopter presented as relatively intact with the tailboom broken aft of its forward mount point. The operator’s examination identified that one of the arms of the clutch shaft forward yoke had fractured resulting in loss of drive to the main and tail rotor systems. The tubular steel structure surrounding the shaft was damaged by the rotation of the unrestrained clutch shaft. The hydraulic reservoir was also found displaced from its mounting base and was located within the wreckage (Figure 2).
Figure 2: VH-HOB following the collision with inset showing clutch shaft with upper drive sheaves and displaced hydraulic reservoir
Source: Supplied, annotated by the ATSB
Following the accident, attending maintenance personnel reported they conducted a functional check of the flight control system and found the cyclic[3] and collective[4] controls had full and free movement. However, one of the tail rotor control tubes exhibited bending damage that was likely the result of contact with the unrestrained clutch shaft.
Both the pilot and the ground crewman reported that the engine stopped operating shortly before the collision. Images showed that a cutting action of the unrestrained clutch shaft forward yoke (see R44 rotor drive system below) penetrated the engine upper firewall and damaged the engine fuel system flow divider located on the engine below. The yoke perforated the flow divider top housing, which likely interrupted fuel flow to the engine, resulting in engine stoppage.
Both of the fuel tanks were found intact and there was little external distortion of the auxiliary tank following the impact with the ground.
At interview, the ground crewman commented that the helicopter was observed to approach at a low rate of descent, and had it not struck the vehicle, the landing would likely have resulted in significantly less damage to the helicopter.
R44 rotor drive system
The clutch shaft forward yoke assembly is part of the R44 rotor drive system. The R44 pilot’s operating handbook provided the following description of the main and tail rotor drive system and is illustrated in Figure 3.
A vee-belt sheave is bolted directly to the engine output shaft. Vee-belts transmit power to the upper sheave which has an overrunning clutch contained in its hub. The inner shaft of the clutch transmits power forward to the main rotor and aft to the tail rotor. Flexible couplings are located at the main gearbox input and at each end of the long tail rotor drive shaft.
Figure 3: R44 drive train with inset showing clutch shaft forward yoke and flex plate providing input power to the main and tail rotor gearboxes
Source: Robinson Helicopter Company R44 maintenance manual, annotated by the ATSB
Images provided by maintenance personnel showed that during the accident sequence, the vee‑belts had dislodged from the upper sheave.
A manual, cable operated rotor brake was mounted on the aft end of the main gearbox and when applied via the pull handle in the cabin ceiling, friction pads of the braking mechanism would contact the main gearbox input yoke to stop the rotor system. Images showed that the actuating cable was displaced from its guide pulley and was disconnected from the braking mechanism (Figure 4).
Figure 4: Rotor brake mechanism minus actuating cable attached and trapped wire material around the main gearbox input yoke shaft
Source: Maintenance organisation, annotated by the ATSB
The action of separating the cable from the braking mechanism likely caused the rotor brake to be momentarily actuated, and while considered minimal, may have affected the speed of the main rotor system.
R44 II hydraulic system
The R44 II hydraulic system consists of a pump mounted to the main rotor gearbox, a servo at each of the control tubes connecting the cockpit controls to the swashplate, a reservoir assembly, hydraulic fluid and interconnecting flexible hoses (Figure 5). Should a loss of hydraulic pressure occur, the servos contain an irreversible feature to reduce main rotor feedback forces to the pilot’s controls. However, in the absence of hydraulic pressure, the manufacturer advised that the cyclic control system is harder to move in the fore-and-aft and lateral planes, while the collective control can be easily lowered, but becomes harder to raise.
Following the accident, the hydraulic system was provided to the ATSB for further examination. Without hydraulic pressure applied, examination of each servo showed that the irreversible feature was functional. The forces required to move each servo were noted to be slightly higher in comparison to new servos but were considered acceptable.
The hydraulic reservoir had separated from the hydraulic manifold mounted to the tubular frame likely from the clutch shaft striking the manifold (mounting location circled, Figure 5). This resulted in significant loss of hydraulic fluid. The ATSB’s examination of the hydraulic reservoir revealed multiple impact marks attributed to striking, or being struck repeatedly by a rotating component, likely the main gearbox input yoke.
Figure 5: Hydraulic system and main gearbox installation from VH-HOB
Source: Maintenance organisation, annotated by ATSB
Yoke examination
The clutch shaft with the fractured yoke arm, the forward flex plate and the attaching hardware were provided to the ATSB for detailed examination (Figure 6). A portion of the flex plate that remained connected to the yoke and the separated section of the arm was also provided for examination.
The yoke presented with one arm intact, to which a portion of the forward flex plate and its attaching hardware were present. The opposite arm had fractured at the bolt hole that secured the arm to flex plate.
The surfaces of the yoke presented with scoring marks and indentations to the painted surfaces. Mechanical impact damage and gouging was also present with smearing damage to the arm fracture surfaces obscuring some of the original fracture features.
Figure 6: Fractured forward yoke arm with inset showing clutch shaft assembly and flex plate
Source: ATSB
A detailed visual inspection of the yoke arms using an optical microscope and a magnetic particle inspection of the yoke surfaces and bolt hole regions, did not identify additional cracks.
Red-coloured corrosion products were observed on the forward face of the yoke where it contacted the bonded stainless-steel washer from of the forward flex plate (Figure 7). Fretting damage was present on the aft face that was in contact with the attaching hardware. Microscopic examination of the red-coloured product identified it to have been produced from general corrosion/oxidation of the underlying steel surface. There were no indications of pitting corrosion.
Figure 7: Fractured yoke arm and separated section front and rear surface condition
Source: ATSB
Visual examination of the fracture surfaces on either side of the bolt hole showed evidence of fatigue fracture. The fracture surface showed concentric beach marks indicative of a progressive crack mechanism, which radiated outwards from the likely origin at the inner bolt hole surface on the front face of the yoke (Figure 8). The fatigue crack had propagated from the front to the aft face, and initially obscured from view by the presence of the attaching hardware.
Crack propagation continued across a substantial portion of the cross section (about 98% of fracture # 1 and about 80% of fracture #2), with a visible portion on the rear face of about 6 mm before final overstress fracture and separation occurred.
Figure 8: Separated yoke tip with fracture features identified
Source: ATSB
A scanning electron microscope (SEM) was used to further qualify the fracture surfaces at high magnifications. The SEM examination confirmed:
many hundreds of crack progression bands were observed, which indicated crack growth occurred as a result of high-cycle fatigue[5]
surface damage (an indent) approximately 0.10 mm in depth at the fatigue crack origin of fracture #1 had likely influenced the initiation of cracking within the yoke arm at the point of fracture
a clear boundary on the fracture surface existed between the region of corrosion and the region that was not corroded (Figure 9).
Figure 9: Fracture surface of separated section showing corrosion boundary with inset showing crack surface discoloration
Source: ATSB
Metallurgical, chemical and dimensional analysis established that the yoke conformed to the manufacturer’s specification for material type, hardness, and physical dimensions.
Overall corrosion protection had been specified by the manufacturer that was for the yoke to be cadmium-plated, primed and then painted. These corrosion protection schemes were confirmed during metallurgical examination of the yoke.
The manufacturer’s instructions for continuing airworthiness of the clutch shaft forward yoke (part number C907) were contained in the Robinson R44 II pilot’s operating handbook (POH) and the aircraft maintenance manual. The following was noted:
At each daily or pre-flight inspection, the yoke flanges[6] (yoke arms) were to be checked. No cracks were permitted.
At each 100-hour or annual airframe inspection, the yoke was to be checked for condition and to verify no cracks, corrosion or fretting was present. The yoke was also to be checked for security and operating clearance.
At each 2,200-hour inspection, a 100-hour or annual inspection is also conducted, and the yoke was to be checked for condition. Additionally, the aircraft maintenance manual provided a list of components that were to be replaced with new or overhauled exchanged parts when they had accumulated 2,200/2,400-hours time‑in‑service. There was no requirement for the yoke to be replaced with a new or overhauled part once those hours had accumulated.
Other than for unscheduled maintenance, the yoke was only separated from the forward flex plate (see Figure 3 insert) when parts were replaced at their assigned 2,200/2,400-hour service interval. The yoke was treated as an ‘on-condition’ item and was not assigned an operating time‑in‑service, fatigue, or calendar life-limit.
Maintenance personnel reported that when installed, the yoke can be viewed on a daily inspection via an access panel located on the right side of the helicopter. During the 100-hour or annual inspection, the yoke can also be inspected from above when the upper panel between the fuel tanks was removed. It was noted that cracking on the front face of the yoke arm would not be visible during these inspections as there was no requirement to remove the yoke from the flex plate.
The aircraft maintenance manual specified a range of examination methods for the detection of defects and identified specific parts that warranted examination above that provided by visual inspection means. Higher levels of examination for nominated parts included the use of a suitably powered magnifying glass, and fluorescent penetrant and magnetic particle inspection processes. However, the yoke was not included in the nominated parts list.
Maintenance practices
The pilot reported that on the day of the accident, a pre-flight inspection was completed, and no defects were noted. Maintenance personnel also reported that no defects associated with the forward yoke were noted during the 100-hour inspection that was conducted 92 hours prior to the accident.
During the most recent 2,200-hour inspection, the helicopter’s main rotor gearbox was refitted, and the three flex plates of the rotor system drive train were replaced with new items.
Records showed that the engine-to-gearbox clutch shaft assembly had been replaced about 701 hours prior to the 2,200-hour inspection with the forward yoke transferred to the replacement shaft. This may have provided another opportunity for detailed inspection of all yoke surfaces.
Maintenance personnel involved in the 2,200-hour inspection reported that at the time of replacing the flex plates, following separation from the forward flex plate, the yoke surfaces were visually examined for defects and the yoke was determined to be serviceable.
The manufacturer advised that yokes were commonly removed from service due to the presence of corrosion or fretting damage, but not due to cracks. When forward yokes were returned to the manufacturer as part of the clutch shaft for overhaul, the surface finish was removed, and a magnetic particle inspection for defects would be completed prior to release to service.
Helicopter emergency procedures
Hydraulic system normal and emergency procedures
The R44 II POH advised pilots that for training purposes, a hydraulic system failure may be simulated by switching the hydraulic system off by using the cyclic-mounted hydraulic switch. With hydraulics switched off, controlling the helicopter in a hover may be difficult due to control system feedback forces.
The handbook also advised pilots to expect control stiffness and feedback when conducting hydraulic systems checks or pre-take off control checks with the hydraulic system switched off.
The handbook described the symptoms for a hydraulic system failure as indicated by heavy or stiff cyclic and collective controls, and loss of hydraulic fluid may cause intermittent and/or vibrating feedback in the controls. Should that occur, the POH stated that control of the helicopter would be normal except for the increase in stick forces. Additionally, if hydraulic power was not restored after verifying that the hydraulic switch is in the ‘ON’ position, the pilot is to switch hydraulics to ‘OFF’ and to land as soon as practical.
Engine power loss or loss of tail rotor function
In the event of an engine or drive system failure, the POH advised pilots to immediately lower the collective lever and enter autorotation[7] while observing airspeed requirements. Pilots were also instructed to enter an autorotation if loss of tail rotor thrust in forward flight occurs.
An autorotation is typically conducted at a specified forward airspeed and rotor RPM at which a power-off glide is most efficient. Autorotation airspeed and RPM is different for each helicopter type and is characterised as a controlled descent. The flight controls are used to manoeuvre the helicopter during the autorotation, through to completion of the landing sequence.
Although the tail rotor is used to counteract the yawing effect of the main rotor at low speed, a loss of tail rotor control or drive to the tail rotor, is manageable provided adequate airspeed is maintained, as directional stability is provided by the helicopter’s vertical and/or dorsal fin.
Pilots are trained to perform autorotational descents, and autorotational capability is a certification requirement for helicopters.
At interview, the pilot reported that simulated engine failures, tail rotor system malfunctions and hydraulic failures were practised during training and flight reviews. However, they were trained and assessed as independent emergencies and were never conducted simultaneously as a compound emergency.
Recorded data
VH-HOB was not equipped with a flight data or cockpit voice recorder, nor was it required to be. Differential GPS[8] flight path data from the on-board SatLoc Bantam[9] aerial application tracking device was provided to the ATSB.
Speed and position data from the SatLoc device was used in the analysis of the helicopter’s movements in the final 3 minutes of flight (Table 1).
Table 1: Key events involving VH-HOB during the final minutes of flight with approximate values of flight behaviour
Time
VH-HOB movements
Height above ground level (ft)
Ground speed (kt)
Rate of descent (ROD) (fpm)
Rate of track change
(⁰ per minute)
0924:06
Pilot returning to loading zone, slows prior climbing flight from about 160 to 40 fpm.
250
19
0924:08
Pilot commences descent to loading zone
20
60
0925:44
Bottom of descent
62
21
0
0925:46
Pilot initiates a climb, rate of climb about 60 fpm
64
20
0926:18
Approaching top of climb, pilot slows rate of climb to about 20 fpm
124
5
0926:20
Helicopter on descent
122
5
60
0926:28
Bang heard (estimated time of noise)
104
4
200
475
0926:30
Descent
94
5
335
416
0926:36
Descent – maximum ROD
43
8
550
207
0926:38
Descent
30
10
413
232
0926:40
Descent
18
10
314
133
0926:42
Descent
10
11
236
74
0926:44
Descent
5
10
160
11
0926:46
Helicopter collides with vehicle/terrain
9
160
From 09:26:40 to collision at 09:26:46, the aircraft track varied by about 4 degrees. In the last two seconds of flight, the track varied by less than one degree, and aligned the helicopter’s movement with the position of the stationary ground vehicle (Figure 10).
Figure 10: VH-HOB flight path showing landing approach with momentary climb and descent towards ground vehicle
Source: Google, annotated by the ATSB
Related occurrences
This accident involving the clutch shaft forward yoke (part number C907) was the first occurrence to be investigated by the ATSB that involved an in-flight failure of a yoke on a helicopter model in the Robinson range.
Robinson advised of no other reports of fatigue cracks associated with forward yokes. Searches of the CASA, the US Federal Aviation Administration (FAA) and New Zealand Civil Aviation Authority (CAA) Service Difficulty Report databases did not reveal other documented cases of fatigue related cracking.
There was one similar R44 occurrence, involving loss of drive to the main and tail rotor due to weld failure of the forward yoke. The incident occurred during cruise flight in which the pilot heard a bang and experienced a loss of tail rotor effectiveness due to the failure of a weld joint in the forward yoke.
As a result of this incident, an airworthiness directive was issued by the FAA in August 1999 (FAA Priority Letter Airworthiness Directive AD 99-17-17), requiring the replacement of certain yoke assemblies in R44 helicopters before further flight. The manufacturer identified manufacturing lots associated with the failed yoke and retired the affected yokes from service. If uncorrected, the FAA advised that the condition could result in failure of the yoke assembly, loss of main and tail rotor drive, and subsequent loss of control of the helicopter. In October 1999, CASA issued AD/R44/13 in support of FAA action.
Safety analysis
The collision with terrain involving Robinson R44 II VH-HOB, about 13 km south-east of Clare Valley Aerodrome, South Australia, was the result of the loss of drive to the main and tail rotor systems due to fracture of the clutch shaft forward yoke. This analysis will focus on the failure of the yoke, the emergency descent, and the subsequent collision with terrain. The analysis will also consider maintenance information for the continued airworthiness of the yoke and management of in-flight emergencies.
Yoke failure and separation
The yoke failed as a result of fatigue crack propagation that initiated on the forward face of the yoke arm coincident with the bolt hole. On one side, the crack had initiated from a mechanical surface defect. The fatigue cracking was assessed to have propagated slowly as evidenced by the many hundreds of crack progression bands, with failure of the yoke arm occurring when minimal intact cross-sectional area remained.
A distinctly corroded region was identified on the forward-most surface of the yoke. A similarly corroded/stained region was identified on the fracture surface. The corroded regions were underneath where the bonded washer from the forward flex plate would normally be clamped. The varying nature of the corrosion within the fatigue crack and the demarcation between the various regions suggested that the crack had existed during an overhaul cycle of the component.
Following the fracture of the yoke, the clutch shaft became disconnected from the main gearbox creating misalignment of the upper and lower sheaves and displacement of the vee-belts. This resulted in a loss of drive from the engine to both the main and tail rotor systems. The loss of drive committed the pilot to find a suitable place to land the helicopter while conducting an emergency descent without tail rotor control.
Yoke inspections
The manufacturer’s in-service requirements for yoke serviceability specified that the yoke be inspected for cracks, fretting or corrosion at specific intervals that included the daily inspection, at scheduled time in service intervals and during the 2,200-hour inspection.
The drive train was inspected on the morning of the accident flight and at the previous scheduled inspection, and no defects were found. However, with the yoke connected to the forward flex plate, there was no opportunity to visually detect the crack on the forward face during the daily and 100-hour inspections. Once the crack had progressed to the rear surface of the yoke arm, it would have been difficult to see, given that the crack was estimated to be about 6 mm in length, and the area would have needed to have been sufficiently clean.
The only opportunity for detecting a crack initiating on the front face of the yoke would be when all yoke surfaces were exposed and not obscured by the presence of the flex plate and attaching hardware. This would be at the 2,200‑hour inspections, or at unscheduled clutch shaft or flex plate removal. The last time the yoke was separated from the forward flex plate was at the recent 2,200-hour inspection, about two months and 188 flight hours prior to the accident.
The presence of corrosion deposits in part of the cracked region indicated that the crack was likely present at that inspection. Once the yoke arm was re-installed, the forward face was obscured by the flex plate and the crack would not have been visible during the subsequent routine inspections.
Maintenance instructions for critical item
The forward yoke was not assigned a service life by the manufacturer so its continuation in service was dependent on it meeting specific inspection criteria to determine on-going serviceability. The maintenance instructions for continued airworthiness specified that the yoke be inspected for condition, and maintenance personnel were required to verify that no cracks, corrosion or fretting was present. No specific method on how to accomplish this was provided in the manufacturer’s documentation, and as such, a visual inspection would be acceptable.
Defects related to corrosion and fretting damage are likely detected by the un-aided eye, but crack identification may be not as obvious. At the 2,200-hour inspection, the yoke was separated from the forward flex plate and the visual inspection method that was used to detect cracks that existed on the helicopter’s forward yoke, was unsuccessful.
The methods used to verify the absence of cracks varied between this maintenance organisation and the aircraft manufacturer. When yokes were returned to the manufacturer as part of the clutch shaft assembly, the yokes were subject to magnetic particle inspection, which would have a greater chance of identifying a crack than visual inspection alone. This suggested that the inspection instruction was open to interpretation and was not consistently applied.
On this occasion, the failure of the yoke led to a loss of drive to both the main and tail rotor systems. The failure of this critical item further resulted in a secondary failure of the hydraulic system under the action of the unrestrained clutch shaft. This presented the pilot with a compound emergency resulting in an emergency descent and subsequent collision with the ground vehicle and terrain.
The reliability of the yoke and lack of history of removal from service due to cracking, likely influenced the use of visual inspection methods and reduced the expectation for a crack to be present. However, that further reduced the probability of detecting the crack when all the yoke surfaces are available for inspection.
Helicopter control
The pilot reported that when the yoke fractured the helicopter was configured for a gentle descent and turn towards the loading vehicle. However, the consequential failures that followed the failure of the yoke, which included a loss of tail rotor drive, resulted in degraded directional control. The pilot also reported that the cyclic and collective controls felt like they were jammed.
The significant bending of the tail rotor pitch control tube following impact by the intermediate flex coupling/clutch shaft aft yoke, likely restricted the movement of the tail rotor pedals, adding to the sense of difficulty in controlling the helicopter.
Post-accident examination of the collective and cyclic control systems found that they moved freely within their travel range. The loss of hydraulic power assistance would have increased the cyclic and collective feedback forces required by the pilot to control the helicopter. An unexpected increase in the control forces while flying with a normal relaxed grip on the cyclic and collective might have led the pilot to perceive the controls were jammed.
The multiple impact marks that presented on the hydraulic reservoir body indicated that the reservoir had become dislodged in flight rather than when the helicopter collided with terrain. The ATSB considered the possibility that the displaced hydraulic reservoir impeded the movement of the hydraulic servos or their control system, or that in the attempt to position the helicopter away from the ground vehicle, the flight controls were moved to their mechanical stops, which prevented further movement. However, based on the evidence available, neither of these possibilities could be confirmed.
The pilot’s usual practice was to land beside the loading vehicle to enable replenishment of chemical product and had configured the helicopter accordingly. Analysis of the flight path following the initial turn towards the ground support vehicle, revealed that the helicopter’s rate of descent repeatedly changed, as did the rate of turn as it approached the vehicle. This suggested that the helicopter was likely responding to some pilot control inputs and therefore some control of the helicopter was likely available. However, it was insufficient for the pilot to avoid a collision with the loading vehicle.
Multiple emergencies
The pilot reported that during their initial training and subsequent flight reviews, there was a requirement to demonstrate competency in performing autorotational descents and flying and landing the helicopter without hydraulic power assistance. However, there was no requirement to conduct compound major emergencies, such as the loss of tail rotor control coupled with a loss of hydraulic power assistance.
The hydraulic pump is driven by the helicopter’s main gearbox, so the hydraulic system is expected to continue providing hydraulic power during autorotation training. Consequently, this accident presented the pilot with a scenario for which they had no prior experience. It also occurred at a low height and low forward speed, which provided the pilot with very little time to diagnose the situation and manage the emergency landing.
Findings
ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition, ‘other findings’ may be included to provide important information about topics other than safety factors.
Safety issues are highlighted in bold to emphasise their importance. A safety issue is a safety factor that (a) can reasonably be regarded as having the potential to adversely affect the safety of future operations, and (b) is a characteristic of an organisation or a system, rather than a characteristic of a specific individual, or characteristic of an operating environment at a specific point in time.
These findings should not be read as apportioning blame or liability to any particular organisation or individual.
From the evidence available, the following findings are made with respect to the loss of control and collision with terrain involving Robinson R44, VH-HOB, near Clare, South Australia, on 22 December 2020.
Contributing factors
Fatigue cracks in the clutch shaft forward yoke progressed until the yoke fractured during operation, which led to a loss of drive to the main rotor system that necessitated an emergency descent.
During the emergency descent from a height of about 100 feet, the pilot experienced difficulties in controlling the helicopter and was unable to avoid colliding with the ground vehicle, which increased the severity of the collision with terrain.
Although it was very likely that a crack was present when the clutch shaft yoke was last disassembled from the forward flex plate, it was not detected during inspection. Once assembled, the crack, which had formed on the forward face of the yoke arm, was obscured by the presence of the flex plate.
Although the helicopter manufacturer’s instructions for continuation in service for the clutch shaft forward yoke specified that the condition of the yoke was to be inspected to verify that no cracks, corrosion, or fretting was present, it did not provide specific instructions for the method to be employed. The visual inspection that was employed increased the risk that a crack in that area may not be detected [Safety issue].
Other (key) finding
The emergency descent was performed without hydraulic power assistance to the main rotor control systems and without drive to the tail rotor. That required the pilot to manage simultaneous emergencies that were not concurrently presented during training sessions and for which they had no prior experience.
Safety issues and actions
Central to the ATSB’s investigation of transport safety matters is the early identification of safety issues. The ATSB expects relevant organisations will address all safety issues an investigation identifies.
Depending on the level of risk of a safety issue, the extent of corrective action taken by the relevant organisation(s), or the desirability of directing a broad safety message to the aviation industry, the ATSB may issue a formal safety recommendation or safety advisory notice as part of the final report.
All of the directly involved parties are invited to provide submissions to this draft report. As part of that process, each organisation is asked to communicate what safety actions, if any, they have carried out or are planning to carry out in relation to each safety issue relevant to their organisation.
Descriptions of each safety issue, and any associated safety recommendations, are detailed below. Click the link to read the full safety issue description, including the issue status and any safety action/s taken. Safety issues and actions are updated on this website when safety issue owners provide further information concerning the implementation of safety action.
Safety issue description: Although the helicopter manufacturer’s instructions for continuation in service for the clutch shaft forward yoke specified that the condition of the yoke was to be inspected to verify that no cracks, corrosion, or fretting was present, it did not provide specific instructions for the method to be employed. The visual inspection that was employed increased the risk that a crack in that area may not be detected.
Safety action not associated with an identified safety issue
Whether or not the ATSB identifies safety issues in the course of an investigation, relevant organisations may proactively initiate safety action in order to reduce their safety risk. All of the directly involved parties are invited to provide submissions to this draft report. As part of that process, each organisation is asked to communicate what safety actions, if any, they have carried out to reduce the risk associated with this type of occurrences in the future. The ATSB has so far been advised of the following proactive safety action in response to this occurrence
Safety advisory notice to operators of R44 helicopters
The ATSB advises operators of R44 helicopters to note the preliminary finding of this accident and to look for the presence of corrosion, fretting or cracking, which may not be visually obvious, during all inspections of the clutch shaft yoke. Any identified defects should be notified to both the ATSB and the Civil Aviation Safety Authority.
Additional safety action taken by CASA
CASA issued Airworthiness Bulletin AWB 63-010 Issue 1 to inform owners, registered operators, maintenance organisations and Licensed Aircraft Maintenance Engineers of a failure in a Robinson R44 drive train component (the yoke) that was found by the ATSB during investigation AO-2020-064 and that the ATSB has issued a Safety Notice AO-2020-064-SAN-014 to highlight the component failure.
A revision to the AWB (Issue 2) was issued by the CASA on 23 September 2021. Further to original references that signs of loose fasteners, corrosion or discolouration warrant further investigation, Issue 2 advised that further investigation may require the use of specialised inspection methods such as non-destructive testing (NDT). The manufacturer's maintenance data should be consulted and if lacking sufficient detail for the required inspection or method/s, then the manufacturer is to be contacted for the appropriate inspection data, or if a specialised inspection is required, then the inspection data will need to be generated and approved under civil aviation legislation. Further, any specialised inspections will need to be conducted using approved data by an appropriately authorised person.
Additional safety action taken by European Union Aviation Safety Agency (EASA)
Following the release of CASA AWB 63-010 Issue 1 dated 21 June 2021, EASA issued Safety Information Bulletin No. 2021-13 on 29 June 2021 advising owners and operators that EASA concurs with the AWB's recommendations and to ensure that owners and operators are aware of the recommendations.
Additional safety action taken by Federal Aviation Administration (FAA)
Following receipt of a report of a failed C907 yoke in the R44 main rotor drive system, the FAA issued a Special Airworthiness Information Bulletin (SAIB: AIR-22-08) to remind owners and operators of any Robinson R44 rotorcraft of the importance of adhering to existing inspection procedures in the applicable operating handbooks and maintenance manuals.
The SAIB advised of the presence of a fatigue crack near the bolt hole of the arm of the C907 yoke, and that an initial metallurgical examination found corrosion products and fretting damage on the surface near the fatigue crack. The yoke failure may have been caused by corrosion and/or improper hardware torque. Further, inadequate inspection and maintenance of all driveshaft yokes may result in undetected wear and/or corrosion that could lead to yoke failure and loss of main and tail rotor drive.
The FAA recommended that owners and operators of R22 and R44 series rotorcraft follow Robinson's published pre-flight inspection and periodic maintenance criteria regarding main and tail rotor driveshaft yokes in order to prevent future failures.
Glossary
FAA Federal Aviation Administration
CAA Civil Aviation Authority
GPS Global Positioning System
METAR Meteorological Terminal Air Report
POH Pilot Operating Handbook
RHC Robinson Helicopter Company
SAN Safety Advisory Notice
SDR Service Difficulty Report
TAF Terminal Aerodrome Forecast
Sources and submissions
Sources of information
The sources of information during the investigation included the:
accident witnesses
aircraft manufacturer
Bureau of Meteorology
Civil Aviation Safety Authority
maintenance organisations for VH-HOB
County Helicopters Pty Ltd
photographs and videos taken on the day of the accident
pilot of the accident flight
recorded data from the DGPS unit on the aircraft.
References
Federal Aviation Administration (2019), Helicopter Flying Handbook, U.S. Department of Transportation, FAA-H-8083-21B
Under section 26 of the Transport Safety Investigation Act 2003, the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. That section allows a person receiving a draft report to make submissions to the ATSB about the draft report.
A draft of this report was provided to the following directly involved parties:
aircraft manufacturer
Civil Aviation Safety Authority
County Helicopters Pty Ltd
pilot of the accident flight
maintenance organisations for VH-HOB.
Submissions were received from:
aircraft manufacturer
Civil Aviation Safety Authority
The submissions were reviewed and, where considered appropriate, the text of the report was amended accordingly.
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.
Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.
The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
[1] Central Daylight Time (CDT): Coordinated Universal Time (UTC) +10.5 hours
[2] METAR: a routine aerodrome weather report issued at routine times, hourly or half-hourly
[3] Cyclic: a primary helicopter flight control that is similar to an aircraft control column. Cyclic input tilts the main rotor disc, varying the attitude of the helicopter and hence the lateral direction.
[4] Collective: a primary helicopter flight control that simultaneously affects the pitch of all blades of a lifting rotor. Collective input is the main control for vertical velocity.
[5] Failure mechanism associated with high frequency vibration, flexing or rotation of machinery, typically at a rate of many times per second.
[6] Yoke flanges or arms: interchangeable terms used by the manufacturer to describe the connecting surfaces of the yoke
[7] Autorotation, also known as an autorotational descent, is a power off manoeuvre in which the engine is disengaged from the main rotor system and the rotor blades are driven solely by the upward flow of air through the main rotor.
[8] Differential GPS: an enhancement to global navigation satellite system (GNSS) systems. A differential GPS base station broadcasts a correction signal that allows differential GPS devices to provide sub-metre positional accuracy relative to the base. If the position of the base is precisely known, this allows for high absolute positional accuracy.
[9] SatLoc Bantam: a proprietary aerial application guidance system utilising differential GPS signals.
On 30 December 2020, Aurizon fertiliser freight train 9281, was travelling from Phosphate Hill to Townsville Jetty, Queensland. A short time, after commencing the downhill grade from 119 km towards Sellheim, train 9281 derailed while traversing over a culvert.
What the ATSB found
The investigation found that a series of rainfall events on the 29 December 2020, which included a heavy rain event between 1510 and 1615, compromised the drainage system at the 118.131 km. Water over-topped the track prior to the arrival and subsequent derailment of train 9281.
The corrugated metal pipe, that was an element of the drainage system at the 118.131 km, likely had rainwater throughput restricted. This was restriction was possibly due to sinking, debris from the upstream side blocking the corrugated metal pipe, or collapse of the corrugated metal pipe due to exceeding its service life, or a combination of the three, resulting in the rainwater pooling.
Extensive rainwater pooling resulting in over-topping of the track at the location of the corrugated metal pipe very likely undermined the track infrastructure, such that it could not support the weight of the rolling stock.
What has been done as a result
Following the derailment, Queensland Rail upgraded the culvert with three 900 mm corrugated metal pipes, which significantly improved drainage in the area. Queensland Rail is also considering actions around engineering studies, resilience works, and alternative and predictive weather monitoring.
Safety message
Rail infrastructure managers should ensure their drainage systems are fit for purpose, are clear, open, and in serviceable condition. This will minimise the risk of system inundation and track over‑topping.
The occurrence
Train 9261/9281 was a loaded fertiliser train, operated by Aurizon, travelling from Phosphate Hill to Townsville Jetty on the Mount Isa line in Queensland. The train departed Phosphate Hill as train number 9261 on 28 December 2020, before being renumbered 9281 from Hughenden on 29 December 2020. Both the drivers of train 9281 commenced work in Hughenden at 1815 Eastern Standard Time[1]on 29 December 2020.
On 29 December, at about 1830, while travelling from Hughenden to Charters Towers, the rail traffic crew of train 9281 were asked by the network control officer to report on the weather conditions. The rail traffic crew reported they had not observed any flooding or adverse conditions on the journey. Prior to the passage of train 9281 from Charters Towers, there were 2 periods of rainfall recorded near the site of the derailment, one in the afternoon, and another in the evening.
On 30 December 2020, at 0016, train 9281 was travelling from Charters Towers towards Sellheim (Figure 1). A short time after commencing the downhill grade from 119 km towards Sellheim, 11 wagons, not including the locomotives and first wagon, derailed while traversing a culvert.[2] As a result of the derailment, fertiliser was spilt into the waterway and towards a dam on a local property.
Figure 1: Location of the derailment
Source: Geoscience Australia, annotated by the ATSB
Context
Train
The train consisted of 2 locomotives, a 2800 class (2826) leading and a 4000 class (4046) trailing. The train was hauling 35 VFMQ class hopper wagons. The train was 562 m in length and had a trailing mass of 2,754 t and was crewed by 2 rail traffic crew, consisting of a tutor driver and a driver under route tuition.
Washout of track infrastructure
Evidence collected by Queensland Rail at the site of the derailment indicated it was the result of a washout of the track infrastructure. The washout was on the downstream beside a culvert and uncovered an old concrete abutment within the foundation (Figure 2).
Figure 2: Washout location
Source: Queensland Rail, annotated by the ATSB
Weather
The Mount Isa line from Mount Isa to Richmond, which is to the west of Charters Towers, is heavily impacted by adverse weather events during the monsoon season, which can close the line for periods of time. The closures allow water to dissipate from the rail corridor and inspection to be undertaken to ensure the line is fit for service. Areas east of Richmond, towards Townsville, are less impacted by adverse weather events. Queensland rail’s washout records have been kept since 1971 with no occurrence of washout or flooding recorded at the derailment site.
The northern Australian monsoon season generally lasts from December to March. The north Australian wet season encompasses the monsoon months but can extend several months on either side.[3]
The Bureau of Meteorology (BoM) forecast for Charters Towers on Tuesday, 29 December 2020, issued at 0455:[4]
Cloudy. Very high (95%) chance of showers, tending to rain. A thunderstorm likely with possible heavy falls. Light winds becoming north-easterly 15 to 20 km/h in the middle of the day then becoming light in the early afternoon.
The BoM record of total rainfall for 29 December 2020, indicated that near the site of the derailment, the intensity of rainfall from a series of rain events was in the range of 25–50 mm over the 24-hour period. (Figure 3).
Figure 3: 29 December 2020 Rainfall Total
Source: Bureau of Meteorology, annotated by the ATSB
The BoM weather station at Charters Towers, located about 8.5 km from the derailment site, recorded 33.2 mm of rain between 1500 on 28 December and 1500 on 29 December. A further 26.8 mm was recorded between 1500 on 29 December and 0900 on 30 December.
Weather radar data recorded a series of rainfall events at the derailment site in the 24 hours preceding the accident. They were during the periods 0105–0305 (light rainfall), 1310–1635 (moderate to heavy rainfall) and 1930–2210 (light rainfall) (Figure 4).
Figure 4: Weather radar rainfall intensity at derailment site over 24 hours
Source: The Weather Chaser, annotated by the ATSB
Queensland Rail weather monitoring systems for the region provided no alarms for flooding, significant rainfall or closed-circuit television camera images, which might have prompted a change in the operational status of the line.
The owner of a property, located about 800 m to the north of the derailment site, recorded about 84 mm of rain. The owner was in Charters Towers at the time, and was notified by their partner, who was at the property, at about 1520 on 29 December, that there was heavy rainfall. The owner stated that it was heavy rain (storm) that was isolated in a small area. The owner had last checked the rain gauge in the morning and noted the 84 mm after returning to the property from Charters Towers at about 1700.
The ATSB noted that there was a period of consistent moderate to heavy rainfall at the derailment site from about 1510-1615. The 1600 weather radar data depicted a heavy rainfall event over the accident site, which passed between the weather stations at Charters Towers and Mingela (Figure 5).
Figure 5: Weather radar rainfall intensity at derailment site
Source: The Weather Chaser, annotated by the ATSB
A rainfall of 84 mm from 1510–1615 equates to 78 mm/h rainfall intensity.
The BoM Design rainfall data system 2016 provides design rainfall data based on intensity‑frequency-duration, and includes average recurrence intervals, which refer to how often a particular level of rainfall intensity can be expected to occur in years and probabilities. The BoM intensity-frequency-duration data for the derailment location near Charters Towers can be seen in Figure 6.
The 78 mm/h observed was greater than a once in 20-year event (71.9 mm/h), but less than 50‑year event (83.5 mm/h) for the Charters Towers weather station.[5]
Figure 6: Bureau of Meteorology intensity-frequency-duration chart for Charters Towers
Drainage systems are designed to allow flow of water from known water courses under the track infrastructure, through a corrugated metal pipe (CMP) or other free-flow system, without adversely affecting the formation, ballast, sleepers, and rail. The drainage system located at the 118.130 km chainage was of a cross drainage design (Figure 7) with water flowing from a catchment area into longitudinal drains and progressing through a single CMP under the track infrastructure. The CMP was about 3 m below the rail head height (Figure 8).
Figure 7: External and local catchments, including cross drainage
Source: Rail Industry Safety and Standards Board, AS 7637 Hydrology and Hydraulics, Version 1.0, 2014
Figure 8: Drainage system
Source: Queensland Rail, annotated by the ATSB
Catchment area
The catchment area for the drainage system was about 200 m south of the rail corridor. Water flows from the catchment in a northerly direction, through the drainage system under the track infrastructure, and continues into a dam located about 800 m north of the drainage system, and about 180 m east of the home of the property owner.
The catchment area, south of the derailment site, as provided by Queensland Rail in their preliminary hydraulic assessment,[6] was about 30 ha (300,000 square metres, Figure 9 dotted red line). Within a 30-ha catchment area, this would have produced about 23,400 m3/h, or 6.5 m3/s (based on 78 mm/h).[7]
Figure 9: Drainage catchment system
Source: Google Earth, annotated by Aurizon and the ATSB
Construction of the culvert
Construction history
A 6 m single span timber bridge was built at the time or soon after original construction of the railway, circa 1882. At a construction date that was unknown by Queensland Rail, a 1.8 m long by 1.4 m high concrete floodway was constructed to replace the timber structure. Sometime between 1965 and 1980, a 1,050 mm CMP was installed at the location to replace the previous concrete floodway. Queensland Rail stated that it was likely constructed in the mid-1970’s.
Corrugated metal pipe
The rainwater from the catchment area was directed to a drainage system, which included a single 1,050 mm diameter by 8 m long CMP, which was of free-flow discharge and designed to be self-cleaning. The water then continued to flow north towards the dam and Gladstone Creek.
Based on the preliminary hydraulic assessment undertaken by Queensland Rail, the design flow rates of the CMP in the drainage system were between about 8 m3/s for a 50-year event and 9.5 m3/s for a 100-year event.
Corrugated metal pipe service life
Queensland Rail reported that the design life and the planned service life of CMPs was 50 years. Evidence provided showed the design life was determined for all CMPs, without consideration of local factors that could reduce the service life.
Service life of a CMP could be affected by pH soil levels, electrolysis and material/fluid passing through pipe, zinc or other coatings, wall thickness and method of installation.
Australian Standard AS/NZS 2041:1998 Appendix C provided guidance on factors that could affect service life assessment, such as:
pH and resistivity of backfill
aggressive backfill conditions
atmospheric corrosion of exposed surfaces
perforation of metal.
The service life of a CMP could be reasonably predicted based on the environmental conditions discussed above.
CMPs are galvanised using a zinc coating to prevent corrosion. The corrosion resistance provided by the zinc coating is in direct proportion to the coating's thickness. Current galvanising, in accordance with AS/NZS 2041.1:2011, is Z600 (600 g/m2 minimum zinc coating mass). Discussions with a manufacturer of CMP’s determined that, mid 1970’s, the CMP probably had galvanised at a Z250 coating[8](250 g/m2 minimum zinc coating mass).
The studies conducted in the United States show that corrugated steel pipe has a life expectancy of 10 years to about 35 years before perforation of the metal occurs.[9] Combined with the wall thickness, dynamic loads and infrastructure foundations, and backfill soils, the service life of a CMP may be less than the planned design life of the drainage system in its entirety.
Installation
The process for installation of CMPs from the mid-1970s to present day has evolved. There were no Australian rail industry standards in the 1970s for their installation. The Australian rail industry currently use AS/NZS 2041: Buried Corrugated Metal Structures and AS/NZS 2041.2: Buried Corrugated Metal Structures – Part 2: Installation.
During the installation of the new culvert, between 1965 and 1980, which, according to Queensland Rail, was likely in the mid-1970s, a concrete abutment that was part of the old concrete floodway structure, was not removed. Interviews with the Queensland Rail structures planners found that they were unaware that the concrete abutment was in-situ until it was exposed by the washaway and derailment. They noted that the location of the concrete abutment could have inhibited the compaction of the foundation and created a weakened area of earthworks.
Weather effect on corrugated metal pipes
With the cyclic dry-wet weather that occurs across the north of Australia, stressors from the passage of rolling stock would apply different dynamic loads to the drainage system and foundation. During dry weather, the foundation is hardened, and stressors from the dynamic loads would be applied across the foundation with minimal stressors applied to the barrel of the CMP.[10]
During wet soaking weather, as occurred during December 2020, the foundation becomes more malleable, and with the softening of the soils around the CMP, the stressors would be applied more to the barrel of the CMP as rolling stock traversed over the track. For CMP’s to withstand significant fill loads[11] and heavy repetitive dynamic loads, an effective soil-structure interaction is necessary. This composite behaviour uses the compressive strength of the culvert wall, with the compressive or bearing strength of the well-compacted soil surrounding the structure. As loads are applied to the culvert, the flexible structure attempts to deflect, with the vertical diameter decreasing and the horizontal diameter increasing.[12]
Corrugated metal pipes may fail due to rolling stock inducing buckling or crushing of the CMP. Factors such as overloading, corrosion of the CMP, soil loss from behind the CMP wall, and softening of the soil due to increased moisture content, the soil being washed away from around the CMP during wet periods and aging can contribute to a CMP failure. The soil can also be lost due to over-topping, loss of headwalls, as well as loss of soil through perforations in the culvert, or a combination of those elements.
Structures and track inspection
The Queensland Rail structures’ planners undertake detailed inspections of bridges, culverts, and associated drainage systems. Queensland Rail had 2 structures’ planners who usually undertook these inspections on the Townsville to Mount Isa and Phosphate Hill lines, which were conducted in accordance with the Queensland Rail Civil Engineering Structures Standard (CESS).[13] The structures’ planners usually inspected about 370 drainage systems per fortnight. On average, the structures planners inspect about 8 drains per hour. Drainage systems with multiple CMP cells, or more defects, took longer to inspect. The planners had undertaken enterprise[14] training with Queensland Rail and were deemed competent to undertake the tasks.
Detailed inspections
The CESS specified scheduled inspections, including that the Rail Infrastructure Manager shall determine the inspection interval for a structure based on the condition of the structure, the rate of deterioration, and local environmental factors. However, it also specified the intervals between scheduled inspections shall not exceed the maximum intervals specified. The CESS specified that ground level inspections of corrugated and sheet steel pipes, drains and arches were to be conducted at a maximum interval of 2 years.
In addition to the maximum interval, it also stated that:
The Rail Infrastructure Manager is to determine the interval according to the condition of the structure and the prevalence of damp silt and permanent water in the culvert throughout the year and an annual visual inspection just before the start of the wet season to check if the waterway is clear.
A detailed inspection in accordance with Appendix 1J of the CESS[15] was undertaken between the 111.224 km and the 129.534 km in July 2019. Sections of the CESS have requirements for inspection of drainage systems, including inspection for corrosion of CMPs.
Between 30 March and 29 April 2020, the CMP at the 118.130 km to 118.131 km was identified as scouring and sinking, which was the location of the derailment. A corrective work order further noted that the gabion baskets on the right side were rolling off the CMP. The CMP was also noted as scoured and sinking on the right side, which was clarified by Queensland Rail as the downstream side of the CMP.
The sinking of the CMP would restrict the outflows of any rainwater that would be diverted to the culvert from the local catchment area. If the CMP was restricted, the design flows would be reduced, and rainwater would pool if input flow from the catchment exceeded the output flow. The report of sinking on the northern side indicated that the CMP was sinking on the downstream side, which suggested that the siltage would be at a greater depth at the outlet.
The work order stated the gabions were to be removed and replaced with two 4 m by 1 m by 1 m gabion baskets. This work was given a low priority of 26 weeks, which was in accordance with the CESS. The work order was closed at the time of the derailment, which indicated that the work had been completed. While the replacement of the gabion baskets would alleviate the scouring around the formation, they would not address the sinking of the CMP.
Cleaning and clearing of culverts
Queensland Rail had undertaken cleaning and clearing of their culverts about December 2020 in accordance with CESS Appendix 1J. Their records indicated that culverts were cleaned and the work order was closed on 6 December 2020. There were no dates in their records for individual culverts.
The cleaning and clearing should remove any debris and other objects from the upstream side of the culvert, preventing the foreign material from entering the CMP when rainwater from the catchment area flowed towards the culvert. The area cleaned was restricted to the rail corridor on the upstream side for as far as the structures planner decided was adequate to prevent debris from entering the drainage system. Any material from outside of the rail corridor could still be deposited into the culvert and the CMP during rain events that had enough volume and force to move the debris. If debris entered the CMP, it could become lodged and restrict the flow of water, resulting in a dam-like effect and subsequent pooling of water on the upstream side.
Pooling of rainwater at the culvert and scouring of infrastructure
Photographs provided by Queensland Rail show that there was debris located on the ballast shoulder on the upstream and downstream side of the track and between the rails, which indicated over-topping of the track infrastructure at that location (Figure 10). Water over-topping of the rail would likely create a waterfall effect and scouring on the downstream side of the track infrastructure (Figure 11). The waterfall effect could also cause the gabion baskets on the downstream side to slide over the exit of the CMP, thereby further restricting the outflows from the CMP.
Figure 10: Evidence of debris on ballast shoulder and between rails
Source: Aurizon, annotated by the ATSB
Figure 11: Evidence of scouring on the downstream (outlet) side
Source: Queensland Rail, annotated by the ATSB
Operational information
Track inspection
Queensland Rail managed the railway where the derailment occurred, with the movement of rail traffic controlled from the Queensland Rail Network Control Centre located at Townsville. The section between Charters Towers and Sellheim was inspected by a Queensland Rail road-rail vehicle at about 1000 on 29 December 2020. The track was certified as fit for service. Aurizon ballast train OCB3 travelled across the section from Charters Towers to Sellheim about 1220 on 29 December 2020 and reported no issues.
Event recorder data
The analysis of the event recorder from diesel electric locomotive 2826 was undertaken by the ATSB and found at 00:20:25 (event recorder time, incident time about 00:16) the equalising reservoir (ER) and brake pipe (BP) pressure simultaneously begin to decrease. This was a likely indication that the initial brake application was driver induced as the ER is generally a good proxy for driver BP request.
Track speed at the 118 km was posted as 60 km/h, however, there was a speed restriction of 50 km/h on the section. The approach speed of train 9281 at the derailment point was, based on recorded data, about 38 km/h. The driver applied the brakes at about 37 km/h, following the derailment, and the train travelled a further 137 m before coming to a complete stop.
Operations
During the travel from Hughenden to Charters Towers, the rail traffic crew were requested by the network control officer to observe weather and effects on the rail infrastructure. The rail traffic crew relayed information to the network control officer at several locations on the travel, with no areas of concern observed.
There were no anomalies identified with the train speed, handling, rolling stock condition, or operational performance preceding the derailment.
Queensland Rail’s management of operations in response to the wet weather event was generally in accordance with their existing policies and procedures.
Safety analysis
On 30 December 2020, Aurizon fertiliser freight train 9281, derailed while traversing a culvert to the east of Charters Towers, Queensland. There was no evidence to suggest that any medical or physiological factors affected the driver’s performance leading up to or during the incident, or that the driver’s actions or health contributed to the derailment. This analysis will discuss the localised weather event, over-topping, and undermining of the track infrastructure.
Localised weather event
The ATSB reviewed several sources of evidence for the rainfall on the afternoon of 29 December. A property owner reported that 84 mm was recorded at the property. The phone call to the property owner at 1520 about the heavy rain indicated that rainfall in the vicinity of the derailment site had started earlier than 1520. Weather radar imagery at 1600 (Figure 5) depicted heavy rainfall over the derailment site from a cell that passed between the 2 nearest weather stations of Charters Towers to the west and Mingela to the east. The weather radar time series charts captured moderate to heavy rainfall over the derailment site in the period 1510 to 1615. As this was consistent with the time the property owner received the phone call reporting heavy rain at the property, this was the likely period over which the heaviest rainfall occurred on the afternoon of 29 December.
The weather radar rain rate intensity marker timeseries is a qualitative indicator only, and therefore the actual rainfall in the vicinity of the derailment could not be determined from weather radar imagery. The rainfall at the weather stations of Charters Towers and Mingela were not considered to be reliable indicators for the derailment site as the weather radar imagery depicted a heavy rain cell pass between these stations and over the top of the site. Therefore, the 84 mm of rain reported by the property owner, over a 65-minute period, was the best measurement available.
Corrugated metal pipe failure
Cleaning and clearing inspections of CMP in the area of the derailment was completed on 6 December 2020, which likely included the incident CMP. Therefore, it was likely that the CMP was open and clear at the time of the incident.
Using the period 1510-1615 as the worst-case scenario for the entire 84 mm of rainfall in the gauge, produced an average rainfall intensity of 78 mm/h. Within a 30-ha catchment area, this would have produced about 23,400 m3/h, or 6.5 m3/s, which was less than the CMP design flow rate (of between 8 m3/s and 9.5 m3/s). As such, the drainage system should have been able to manage this flow of rainwater, through an unrestricted CMP.
The inside of the CMP was not photographed or inspected at the derailment site, and no other evidence was provided to verify the condition of the pipe post-derailment. Therefore, while the age of the CMP combined with the wet conditions suggested the possibility of a collapse, it could not be confirmed if a collapse had occurred or if the CMP had become obstructed by debris. However, the maintenance records for the CMP indicated it had been reported as sinking on the northern side (downstream side) and that no rectification work was performed prior to the derailment. Imagery from the upstream end of the CMP post-derailment also indicated a high level of silt build‑up around the inlet (upstream side).
While the amount of sinkage and build-up of silt pre-derailment could not be determined, it would nevertheless have reduced the CMP flow rate to below the design rate. It was therefore likely that the combination of a localised heavy rainfall event and restricted flow through the CMP resulted in the rainwater over-topping the track infrastructure.
Track infrastructure undermined
Prior to the localised heavy rain fall from 1510 on 29 December, the track was twice seen to be serviceable (road-rail track inspection and previous train). However, after the derailment of train 9281, debris in the middle of the track indicated the formation was over-topped by rainwater. This must have occurred in the afternoon of 29 December, after the passage of ballast train OCB3. Extensive pooling resulted in over-topping, very likely resulted in the undermining of the track infrastructure and the subsequent derailment.
Findings
ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition ‘other findings’ may be included to provide important information about topics other than safety factors.
These findings should not be read as apportioning blame or liability to any particular organisation or individual.
From the evidence available, the following findings are made with respect to the derailment of freight train 9281 on 30 December 2020.
Contributing factors
A series of rainfall events on the 29 December 2020, which included a heavy rain event between 1510 and 1615, compromised the drainage system at the 118.131 km and water over-topped the track prior to the arrival and subsequent derailment of train 9281.
The corrugated metal pipe, that was an element of the drainage system at the 118.131 km, likely had rainwater throughput restricted due to sinking, debris from the upstream side blocking the corrugated metal pipe, or collapse of the corrugated metal pipe due to exceeding its service life, or a combination of the 3, resulting in the rainwater pooling.
Extensive rainwater pooling resulting in over-topping of the track at the location of the corrugated metal pipe very likely undermined the track infrastructure, such that it could not support the weight of the rolling stock.
Safety actions
Whether or not the ATSB identifies safety issues in the course of an investigation, relevant organisations may proactively initiate safety action in order to reduce their safety risk. All of the directly involved parties are invited to provide submissions to this draft report. As part of that process, each organisation is asked to communicate what safety actions, if any, they have carried out to reduce the risk associated with this type of occurrences in the future. The ATSB has so far been advised of the following proactive safety action in response to this occurrence.
Safety action by Queensland Rail
Following the derailment, Queensland Rail have completed the following proactive safety actions:
Upgraded the culvert with three 900 mm corrugated metal pipes, which significantly improved drainage in the area.
Engaged a contractor to conduct a hydrology study to include the derailment area from Stuart, through Hughenden to Cloncurry, Mount Isa and Flynn to Phosphate hill. This package of works has now been completed.
Commenced implementation of infrastructure reliance works that will form part of the outcome of the hydrology study. Notwithstanding significant works already completed as part of the last hydrology study including bridge strengthening in a number of locations.
Identified a further 44 sites for new and upgraded weather monitoring equipment. A business case to request capital expenditure has been progressed. Approval has been given to implement a monitoring system that is currently under trial in the far north. This system provides a level of predictive information based on set points. It collates the data from all current available weather monitoring devices not currently utilised by Queensland Rail e.g. registered farmer rain gauges and also the Bureau of Meteorology. The system then notifies Queensland Rail via text that a specific set point has been hit.
The condition affecting the network procedure has been reviewed and included the traffic light process to inform the broader business as to how Queensland Rail will be treating the event and train operators’ obligations.
Implementation of an additional engineering study into flooding to cover previously unassessed areas of Mount Isa Line to include review of engineering basis for bridges and culverts.
Implementation of infrastructure resilience works.
Review of alternative weather monitoring technology and consideration of installation of additional weather monitoring stations.
Sources and submissions
Sources of information
The sources of information during the investigation included the:
Queensland Rail
Rail traffic crew of 9281
Bureau of Meteorology.
References
Ezzeldin I & El Naggar H 2022, ‘Numerical Modelling of Induced Stresses in Buried Corrugated Metal Structures Due to Compaction Efforts’,Transportation Geotechnics (100706), vol. 32.
Haviland JE, Bellair PJ & Morrell VD n.d., Durability of Corrugated Metal Culverts, Bureau of Physical Research, New York State Department of Transportation.
Rail Industry Safety and Standards Board 2014, Hydrology and Hydraulics, Version 1.0, AS 7637:2014.
Standards Australia 2011, Buried Corrugated Metal Structures Part 1: Design methods, Australian/New Zealand Standard AS/NZS 2041.1-2011.
Standards Australia 1998, Buried Corrugated Metal Structures, Australian/New Zealand Standard AS/NZS 2041:1998.
Wysokowski A 2021, Impact of Live Load on Changes of Backfill Properties of Buried Flexible Steel Railway Structure, Retrieved from https://doi.org/10.1007/s40515-021-00204-4.
Submissions
Under section 26 of the Transport Safety Investigation Act 2003, the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. That section allows a person receiving a draft report to make submissions to the ATSB about the draft report.
A draft of this report was provided to the following directly involved parties:
Aurizon
rail traffic crew of 9281
Queensland Rail
Office of the National Rail Safety Regulator.
Submissions were received from:
Aurizon
Queensland Rail
Office of the National Rail Safety Regulator.
The submissions were reviewed and, where considered appropriate, the text of the report was amended accordingly.
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.
Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.
The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
This investigation was conducted under the Transport Safety Investigation Act 2003 (Commonwealth) by the Office of Transport Safety Investigations (NSW) on behalf of the ATSB in accordance with the Collaboration Agreement. Released in accordance with section 25 of the Transport Safety Investigation Act 2003.
Safety summary
What happened
On Tuesday, 15 December 2020 at 0454, the crew of Qube loaded grain train 3966, consisting of 41 wagons and two CM class locomotives, reported a runaway on the descent of the Moss Vale to Unanderra rail line. The train reached speeds up to 100 km/h on a 30 km/h section of track before it derailed and separated at two points between Dombarton and Farmborough Heights, New South Wales (NSW). Shortly after, the train crew advised they had brought the two locomotives and the remaining two wagons to a stand at Farmborough Heights. The train crew were not physically injured.
What the ATSB found
The investigation identified that ineffective braking caused by several factors contributed to the runaway. The ineffective application of train braking systems was influenced by a heavily loaded train with some overloaded wagons, wagons with variable net brake ratio (NBR), reduced brake cylinder pressure through the train, and train handling and locomotive dynamic braking affected by low track adhesion conditions.
The weight of the train was near, but likely not over, the maximum allowable tonnage limit specified by the Australian Rail Track Corporation (ARTC)’s Train Operating Conditions (TOC) Waiver 16002. It was likely, however, that several individual wagons across the train consist were over the allowable limit for a single wagon.
Measurements of NBR at different times and on different wagons returned varying results ranging from 10.7% to 19.5%. The minimum required NBR for these wagons, specified by Australian Standards was 13%. While modifications were made to improve braking performance on the wagons, the NBR on some wagons continued to change over time. The wagon type test met the NBR requirement when introduced into service and met NBR requirements when tested post modifications, however there was no requirement for regular testing of NBR, which may have identified the changes in NBR.
The mix of wagons with variable NBRs and variability in loading likely reduced braking effort on some of the wagons during the steep descent along the rail line.
During the occurrence, the second automatic brake application made by the driver was made before the brake pipe had fully recharged. This resulted in a reduced amount of available brake cylinder pressure and lessened braking effort on the trailing wagons.
The driver's operation of the train and braking actions did not always conform to the operator (Qube)’s instructions, and it is likely some of the driver’s decisions on the morning of the accident were affected by fatigue.
Once control was lost, the driver elected not to use the emergency brake because they believed, in accordance with Qube’s procedures, that the locomotive braking would have been diminished. This in turn lessened the opportunity to regain control of the train.
Qube’s operational procedure for train management between Moss Vale and Inner Harbour did not consider locomotive configurations that maintained locomotive dynamic braking during emergency applications. This increased the risk of train drivers not applying the emergency brake during a runaway event. This assumption was also found to be embedded within other rolling stock operators’ procedures with similarly configured locomotives in NSW.
The conditions on the rail line from Summit Tank to Farmborough Heights on the morning of the incident included wet rail and track contaminant that likely contributed to low track adhesion and also reduced dynamic braking effort by the locomotives. The wheel slip/slide protection system worked as designed to maximise traction through the use of auto sanding to increase friction and derated the dynamic braking effort through the wheels to match the lower adhesion conditions.
Several rail flange lubricators, which provided lubrication to the down and up rail, were less than the 500 m minimum separation requirement specified in ARTC’s engineering practices manual RC2411. A review of these to ensure consistency with the engineering practice and to minimise the risk of excess track lubrication on a steep gradient was warranted.
Finally, the brake pipe charging flow indicator on CM class locomotives only provided a numerical display without any corresponding audio or visual warning system to alert the driver of its status. This limited the ability of the driver to detect derailment or train separation events and, as in this incident, effectively monitor recharge of main reservoir air into the brake pipe to ensure it was fully charged before making another brake application.
What has been done as a result
During the investigation, a Safety Advisory Notice was issued by the Office of Transport Safety Investigations (OTSI) in collaboration with the ATSB to the rail industry to raise awareness of variable locomotive braking system configurations on locomotives across Australia. Qube and other affected rollingstock operators took immediate actions to review their locomotive configurations, to ensure their locomotive drivers had a clear understanding of the braking systems on the locomotives they were operating.
A forum was chaired by the Office of the National Rail Safety Regulator (ONRSR) in March 2023 with Rail Infrastructure Managers (RIMs) and Rollingstock Operators (RSOs) that operated on the Moss Vale to Unanderra rail line. This provided an opportunity to discuss and communicate the risks of operating on the rail line and how to manage them to mitigate runaway events.
The two RIMs, Sydney Trains and ARTC conducted a review and alignment of Transport for NSW (TfNSW) TOC Manual Illawarra operations and the ARTC Route Access Standard - Section Page D52 Moss Vale - Unanderra. The focus of the review was on providing interoperable train configuration and operating conditions between the two RIM interfaces. Additionally, conditions for managing degraded dynamic brakes and hauling dead attached locomotives were developed. All changes were held in consultation with RSOs, ARTC operations and Network Control stakeholders.
In consultation with TfNSW, ARTC developed joint assessment criterion for Unanderra Trial train configurations, operating conditions, and implementation plans. The RSO will be required to submit supporting documentation as part of a variation to existing approved train configurations.
ARTC has updated NBRs for vehicle classes following physical testing and has worked with others in the rail industry to promote NBR testing as part of preventive maintenance.
Safety message
The rail line between Summit Tank and Unanderra is one of the steepest sections of rail line in NSW. To prevent runaway occurrences on this rail line, operators must regularly review the effectiveness of their risk controls and proactively manage conditions that present greater risk of runaway.
RSOs should ensure their trains have sufficient braking, are loaded within safe load limits and are operated in accordance with their procedures.
RSOs and RIMs should ensure that risk assessments identify critical operational requirements to safely run trains down such steep sections of track. They should also ensure that there is sufficient error tolerance to enable control of trains on sections of rail line that present increased risks from long and steep descents.
RSOs should review the locomotive specifications and test those locomotives under their control to understand how the braking systems are configured and the associated error tolerance. RSOs must communicate this information through their organisation’s procedures and training material to ensure train crew have knowledge of and competence in operating locomotive braking systems, including emergency braking in the event of a runaway.
The use of two-pipe wagon braking systems significantly reduces the recharge times for the brake pipe after a brake application, but the starting air pressure of a wagon’s auxiliary reservoir remains a critical consideration. For example, low auxiliary reservoir starting pressure at the beginning of an automatic brake application reduces the response of a wagon’s supplementary reservoir, resulting in lower wagon brake cylinder pressure and therefore less effective braking effort.
Finally, while a ‘full service’ automatic brake application typically provides the maximum pneumatic braking force available on a train, in the unique circumstance of a train with low auxiliary reservoir starting pressure, lowering the brake pipe pressure further through the application of the emergency brake, will result in an increase in the available braking force. However, this increased braking force will remain less than that which would have been available in full service had the auxiliary reservoir been fully charged at the time of the brake application.
The occurrence
Overview
On 14 December 2020, at approximately 1815 Eastern Standard Time (EST),[1] Qube loaded grain train 3966 departed Temora, New South Wales (NSW) bound for Inner Harbour Port Kembla, NSW. The train travelled through the night and in the early hours of 15 December 2020 commenced the descent on the Moss Vale to Unanderra rail line. Between Summit Tank and Farmborough Heights, the train ran away,[2] derailed and separated at two locations. The 29th to 41st wagons derailed and separated at approximately 93.730 km from Sydney’s Central Station. Then the 3rd to the 28th wagons derailed and separated at approximately 93.220 km, before the locomotives and two remaining wagons came to a stop at Farmborough Heights (Figure 1).
Figure 1: Section of Moss Vale to Unanderra rail line between Summit Tank and Farmborough Heights
This image shows where the train stopped prior to descending the mountain, the points of derailment and where the train stopped. The inset is the track gradient diagram with corresponding stop points and derailments. Source: Google Earth and QUBE, annotated by OTSI
Start of shift
On 14 December 2020, the train crew, consisting of a driver and driver’s assistant, signed on at 2000 at the Junee depot for an 11-hour shift. They were scheduled to start at 1430 but were laid back[3] to 2000. They travelled to Cootamundra and relieved the train crew on service 3966 at approximately 2110. They were rostered to work the train from Cootamundra to Port Kembla. The driver operated the train, for the near seven-hour journey, reporting at interview that the journey was uneventful with the train operating predictably to the start of the descent at Summit Tank.
Start of the descent (~107.5 km)
On 15 December 2020, at approximately 0415, the driver made an automatic brake[4] application (about 70 kPa reduction) and brought train 3966 to a stop at the level crossing just after Summit Tank (see A in Figure 2), as required by Qube’s operational procedure. Once stopped, the driver applied the independent brake.[5]
After a stop of approximately four minutes, the driver released the independent brake and with the automatic (train) brake still applied, powered the locomotives to commence movement against the still applied train brakes.
This stop and start process conducted by the driver at Summit Tank differed to Qube’s operational procedure, which stated that the train should be stopped using a 100 kPa brake pipe reduction (refer to Brake release rollaway time test for further information).
The driver then maintained the automatic brake at a 70 kPa brake pipe reduction and graduated the dynamic brake[6] to manage the speed of the train. This form of brake management was known as ‘balanced braking’.[7] The driver descended the rail line between Summit Tank and the No.2 Tunnel using this method of braking control.
Figure 2: Sequence of events
This image shows the sequence of events leading up to the loss of control and derailments. Source: QUBE, annotated by OTSI
No.2 Tunnel (~102.5.0 km) to No.1 Tunnel (~99.0 km)
At 0436 the train entered No.2 Tunnel travelling at 24 km/h. The driver applied full dynamic brake and released the automatic brake (see B in Figure 2).
Releasing the automatic brake allowed the brake pipe to fully recharge[8] after about 50 seconds. The train slowed to approximately 6 km/h at this time (see C in Figure 2).
The driver then reduced the dynamic brake. Over the next minute, the train speed increased to about 15 km/h.
The driver applied the dynamic brake in full again (see D in Figure 2), then approximately 30 seconds later, with the train travelling at 17 km/h, the driver made a ‘minimum service’[9] automatic brake application (see E in Figure 2).
The train continued to increase speed over the next 30 seconds, with auto sanding[10] occurring three times as the train approached 18 km/h. The train then started to slow slightly over the next 45 seconds and auto sanding occurred another three times.
Over the next 2.5 minutes, without any further input from the driver, the train began to increase speed again. Auto sanding occurred 12 times, as the train speed reached 24 km/h. The driver increased the automatic brake application to about an 80 kPa brake pipe pressure reduction and the train started to slow (see F in Figure 2).
The frequent auto sanding on the descent from Summit Tank, in misty and wet weather conditions, indicated the locomotives' wheel slip/slide protection systems were working as designed to maintain dynamic braking under the adhesion conditions. The driver stated at interview that there were no wheel slip indications received on the locomotive to indicate reduced wheel-rail adhesion, and so they felt the dynamic brake was working effectively.[11]
The train speed reduced over the next 2.5 minutes to about 16 km/h, and auto sanding occurred 11 times. With the dynamic brake fully applied and the auto brake at 80 kPa reduction, the train speed continued to decrease over the next 2.25 minutes to 4 km/h, during which auto sanding occurred another four times (see G in Figure 2).
As the train slowed, the driver released the automatic brake and maintained the dynamic brake in full applied mode. The driver then managed the train speed using serial/cycling braking,[12] as per Qube work instruction WI-540 (Moss Vale to Inner Harbour Train Management). The braking instruction stated that if train speed could not be managed using a 75 kPa reduction and altering the dynamic braking to maintain speed, then the serial/cycle braking method must be used.
At 0448, at about 99.673 km,[13] with the train travelling at 15 km/h, the driver applied a minimum service brake application (see H in Figure 2). The automatic brake handle had been in the release position and charging for 43 seconds since the brakes were last applied.
Although the brake pipe pressure at the locomotive had, by this stage, recharged to 489 kPa on the cab gauge, the brake pipe charging flow indicator was still registering an air flow of 934 litres per minute. This meant that the brake pipe had not yet fully recharged throughout the length of the train (refer to Brake pipe charging flow indicator for further information). In interview, the driver recalled observing the flow meter indicating air flow of 934 litres per minute and judged the train brake pipe to be charged to about 90–95%.
The minimum reduction in brake pipe pressure did not appear to slow the train as the speed increased to 21 km/h over the following 14 seconds. The driver reduced the brake pipe by a further 14 kPa (425 kPa) but the speed continued to increase. The dynamic brake remained in the fully applied position and auto sanding was triggered regularly.
As the train’s speed reached the track section speed limit of 30 km/h, the driver reduced the brake pipe pressure by a further 7 kPa (418 kPa) and the train entered No.1 Tunnel.
No.1 Tunnel (~99.0) to Farmborough Heights (~92.0)
In interview the driver indicated that it was at this point they felt the train was behaving ‘unpredictably’, compared to its responsiveness to the two previous brake applications between Summit Tank and No.1 tunnel.
While in No.1 tunnel, the driver increased the automatic brake application, reducing the brake pipe pressure by a further 14 kPa (404 kPa). The train’s speed continued to increase to 32 km/h, just over the track speed limit of 30 km/h. The train passed through the tunnel and auto sanding was triggered eight times.
At 0450, at about 98.5 km, the driver increased the brake application again, reducing the brake pipe by another 7 kPa (397 kPa). The train was travelling at 34 km/h when the driver commented to the driver’s assistant, ‘I’m on the edge’. Auto sanding occurred two times.
Thirty seconds later, the driver increased the brake application. This reduced the brake pipe pressure by another 7 kPa, to 390 kPa. The train speed remained 34 km/h. Auto sanding occurred three times.
At this time, the head of the train was at about 98.2 km, entering a relatively straight section of track. The rear of the train was still passing through a series of 200 m curve radius left and right‑hand turns.
At about 98.0 km, the driver made another brake application (383 kPa). The train remained at 34 km/h.
As the head of the train reached 97.5 km, the speed increased from 34 km/h to 37 km/h over a 20 second period. At this point, the locomotives entered a 200m right hand curve with the full length of the trailing load on straight track behind it. This would have resulted in reduced dynamic locomotive braking and zero curve resistance on the wagons, which likely contributed to the acceleration. Although the driver made a further brake application (376 kPa), the train continued to increase speed over the next 15 seconds.
At 0453, at about 97.1 km, with the train speed at 42 km/h, the driver applied the automatic brake to ‘full service’[14] (see I in Figure 2). The train continued to increase speed up to 45 km/h over the next 20 seconds. The driver was heard on the in-cab recorder to say, ‘we’re not going to stop’, and then contacted Network Control. Over the next 90 seconds the speed increased to over 60 km/h.
The driver said to Network Control, ‘Can you guarantee me the road there at Unanderra, I’m having trouble stopping this train’. The network controller called Wollongong Panel and requested the rail line to be cleared at Unanderra and Wollongong Panel confirmed it would be done.
At 0455, the network controller called the driver of 3966 and confirmed the scale of the emergency. The driver said, ‘…I’m doing about 70 [km/h] and I’ve got it in full service, I don’t want to put it in emergency[15] because I’ll drop my dyno [dynamic brake] out.’ The network controller said, ‘so fairly dire then is it?’. The driver replied, ‘yeah I’m doing about 80 [km/h] now’.
The network controller kept the driver on the line while they called Wollongong Panel to confirm that the rail line was clear at Unanderra. Wollongong Panel confirmed it was, then the network controller asked the driver for an update. There was no response from the driver.
At 0456, the driver fully applied the independent brake with no apparent effect on reducing the speed of the train. The train was travelling at about 85 km/h, at track position 94.159 km. At this time wheel slide was recorded on the locomotives.
Seconds later, as the train passed the Dombarton distant signal WG1042U at 93.810 km, it went into a left-hand 200 m radius curve in the direction of travel, reaching a peak speed of about 100 km/h. The train was 70 km/h over the track speed limit of 30km/h. At this time, the 29th wagon and trailing wagons derailed and separated from the front part of the train (see J in Figure 2).
At 0457, with the front of the train at 93.100 km and travelling at about 98 km/h, the 3rd wagon up to the 28th wagon derailed and separated from the front part of the train. The train was on a right‑hand 200 m radius curve in the direction of travel (see K in Figure 2).
The train had started to slow after the first separation and at 0458, the two locomotives and remaining two wagons came to a stop at 92.040 km (see L in Figure 2).
As the train came to a stop, the driver advised Network Control ‘I’m at Farmborough Heights and all of a sudden it decided to grab [train started to slow]’.
Post occurrence
With the train immobile, the driver’s assistant stepped off the lead locomotive to check the rest of the train and secure it. They reported back to the driver, via radio, that there were only two wagons attached to the two locomotives.
The driver conveyed this information to Network Control and the Qube Control Centre shortly after.
Recovery teams and emergency services were arranged to attend the site. Inspection of the rail track and rolling stock commenced at approximately 0700 and at 1140 recovery operations commenced.
The locomotives and two attached wagons were inspected by Qube and Chicago Freight Car Leasing Australia (CFLCA, the owner) before being transferred to Port Kembla.
At Port Kembla, the wagons were emptied, and grain weighed to confirm the weight of the remaining two wagons. The tonnage in the wagons was within load limits.
Context
Incident Location
The runaway and derailment occurred between Summit Tank and Farmborough Heights on the Moss Vale to Unanderra rail line, near Dombarton, New South Wales (NSW). Dombarton is on the Illawarra Escarpment approximately 97 rail km south of Sydney Central Station. The train journey started in Temora and the train crew took control of the train at Jindalee (Cootamundra) (Figure 3).
Figure 3: Path of 3966
The orange line represents the rail route of 3966 from Temora to where it stopped at Farmborough Heights. Other key locations are identified. Source: Google Maps, annotated by OTSI
Moss Vale to Unanderra rail line
The Moss Vale to Unanderra rail line is a 57 km section of track connecting the Main South rail line with the Illawarra rail line. The 20 kilometres of track between Summit Tank and Unanderra traverses down the Illawarra escarpment through multiple curves varying in radius between 185 m and 2020 m, transitions and straights. The grade[16] is primarily 1 in 30, other than small sections through No.2 tunnel and Farmborough Heights where the grades are 1 in 120 and 1 in 105 respectively (Figure 1). It is a single-track rail line at Summit Tank, mostly tree lined (Figure 4) and passes through two tunnels and a Rock Fall Shelter before reaching Dombarton where the rail line becomes double-track.
Figure 4: Front of train footage of track
Taken from 3966 front of train camera between 104.000 km and prior to entering No.2 tunnel. Tree foliage lines the track.
Source: Qube
The rail line then remains double-track winding through more tree lined areas before reaching Farmborough Heights. At this location, the grade eases to 1 in 105 then changes back to 1 in 30 grade, winding down through more tree lined areas to Unanderra (see Figure 1 inset for track gradient).
Weather information
There were two Bureau of Meteorology weather stations in proximity to the occurrence: Moss Vale in the Southern Highlands, located at the top of the Illawarra escarpment, and Albion Park in the Illawarra region, located close to the bottom of the escarpment. The site of the incident was between these two locations.
The weather pattern recorded at both weather stations was similar. Recorded weather data logged light rain and moderate winds on the Moss Vale to Unanderra rail line (Table 1). In interview, the driver recalled the weather conditions on departure from Summit Tank to be that of ‘very misty rain’. The data logger also indicated the windscreen wipers of locomotive 3316 were activated between Tunnel 2 and Tunnel 1.
Table 1: Weather recorded at Moss Vale and Albion Park
Place/Date
Temperature
Rainfall
Winds
Moss Vale/14 Dec 20
13.4 – 19.1
2.6 mm
ENE up to 41 km/h
Moss Vale/15 Dec 20
14.6 – 23.6
4.4 mm
NE up to 39 km/h
Albion Park/14 Dec 20
16.8 – 24.3
4.0 mm
NE up to 30 km/h
Albion Park/15 Dec 20
18.6 – 25.3
3.2 mm
NE up to 33 km/h
Source: Bureau of Meteorology
Rail Transport Operators
Qube Holdings
Qube Holdings was a logistics and infrastructure company that provides import and export logistics services across Australia. Its rail logistics division, Qube Logistics (Rail) Pty Ltd (Qube), was accredited by the Office of the National Rail Safety Regulator (ONRSR) as a Rail Infrastructure Manager (RIM) and Rollingstock Operator (RSO) on the 20 January 2013, in the states of NSW, South Australia, Victoria, Western Australia and Queensland.
Qube was the RSO responsible for the operation of grain train 3966.
CFCL Australia Pty Ltd
Chicago Freight Car leasing Australia (CFCLA) was the owner and lessor of the locomotives and wagons. They were accredited as a RSO by ONRSR on 20 January 2013 and were primarily a locomotive and rollingstock leasing company providing assets to other RSOs in the Australian rail industry.
In January 2020, CFCLA was acquired by Anchorage Capital Partners and the company was rebranded as Rail First Asset Management in 2021.
Australian Rail Track Corporation
The Australian Rail Track Corporation (ARTC) manages and maintains approximately 8500 km of rail network across five states in Australia.
In NSW, ARTC leases the mainline interstate corridors from the NSW Government (Figure 5). ARTC is responsible for managing and maintaining these rail corridors in accordance with their accredited system standards.
Figure 5: ARTC leased rail network from NSW Government
Dark lines are the corridors managed and maintained by ARTC. The route of 3966 was between Cootamundra and PT (Port) Kembla Source: ARTC
ARTC was accredited by ONRSR as a RIM and RSO on 20 January 2013 in the states of South Australia, New South Wales, Victoria, Western Australia and Queensland.
ARTC was the RIM responsible for the management and maintenance of the section of track between Summit Tank and Farmborough Heights on the rail line between Moss Vale and Unanderra. Slightly further down the rail line from Farmborough Heights, at 91.080 km, is the interface between ARTC and Sydney Trains rail networks. Above rail operators that use the Moss Vale to Unanderra rail line are required to operate their trains in accordance with the train operating conditions[17] of both RIMs.
Train Crew
The train crew consisted of a driver and driver’s assistant. Both were employed by Qube.
Driver
The driver started working for Qube in September 2012. They were qualified as a locomotive driver for 23 years.
Before working with Qube, the driver had operated train services on the Moss Vale to Unanderra rail line with another freight operator.
The driver was assessed and deemed competent to operate services on the Moss Vale to Unanderra line by Qube. The driver operated five other services on that line in the week prior to the incident train service on the 15 December 2020.
During post incident interview with the driver, they said (of the incident train, 3966) they had taken a mental note of the train weight and got a feel for the train as they operated the train from Cootamundra, but did not calculate the train’s tonnes per operated brake (TOB) as required in their procedure.
The driver’s sleep-wake activity in the days prior to the incident was also established (Table 2). The previous train service operated by the driver was an empty grain service from Port Kembla to Cootamundra that departed at 1315 on 13 December 2020. The driver completed this shift at approximately 0100 on 14 December 2020.
At interview, the driver indicated that they were not feeling fatigued at the time of the incident.
The front of train recordings also captured the time when the train passes Robertson station, near the start of the descent of the Illawarra Mountain. The driver was heard yawning, and shortly after the driver’s assistant starts a discussion about the use of ‘No Doz’[18] to keep you awake. The driver indicated they were not aware of the tablets.
Qube calculated the driver’s FAID[19] score at the time of the incident to be 82.99. Scores between 80 to 100 represented high fatigue likelihood.
Table 2: Driver sleep-wake diary
This is the driver’s account of fatigue related factors and activities in the week leading up to the incident. Actual work hours from Qube Source: OTSI
According to Qube training records, the driver had current qualifications required to operate train services on the Moss Vale to Unanderra rail line. The relevant qualifications included:
Driver competency against Work Instruction WI-540 (Train Management Moss Vale to Inner Harbour [Port Kembla]) was assessed as part of FM-781 (Train Driver Route Assessment Checklist). It was conducted on 28 and 29 November 2020. Competency was current.
Rail Safety Worker medical last completed 28 July 2017, valid until 28 July 2022
FM-780 (Train Operations Performance Checklist) last completed 11 February 2020, valid until 11 February 2023, and
Qualified in CM locomotive operations on 11 April 2014 and competency was current.
Driver’s Assistant
The Driver’s Assistant started working for Qube in September 2020. They were qualified as a driver’s assistant and had no previous rail experience, prior to working for Qube.
According to Qube training records, the driver’s assistant had current qualifications required to assist train services on the Moss Vale to Unanderra rail line. Their relevant qualifications included:
Deemed competent to operate as an assistant under work instruction WI-540 (Train Management Moss Vale to Inner Harbour [Port Kembla], sign-off dated 9 October 2020 on Acknowledgement of Safety Critical Documents pro-forma. Competency was current, and
Rail Safety Worker medical last completed 7 September 2020, valid until 7 September 2025.
Post incident interviews with the driver’s assistant established their sleep-wake activity in the days prior to the incident (see Table 3).
Qube calculated the driver’s assistant FAID score at the time of the incident to be 79.41.
Table 3: Driver’s Assistant sleep-wake diary
This is the driver’s assistant’s account of fatigue related factors and activities in the week leading up to the incident. Actual work hours from Qube. Source: OTSI
Observation
The train crew was working within the special fatigue management program requirements of the Rail Safety National Law National Regulations 2012. However, in high risk operations where train crew are required to descend long steep gradients, an operator’s fatigue management program should consider the additional demand this places on train drivers.
Prior train services
ARTC provided information from ICE train radio[22] data to establish the volume of rail traffic that had descended the Moss Vale to Unanderra rail line in the months leading up to the incident. The data set included the average train speed of all train operators travelling in the Up direction (downhill) between Summit Tank and Unanderra.
Between 1 September 2020 and 15 December 2020 there were 412 services. Each coloured line on Figure 6 represents an RSO and the average speed of their combined services.
ARTC also noted that there had not been any reports of Condition Affecting the Network (CAN)[23] from the drivers of these services specifically related to lack of adhesion. Further, there had not been any reports of CANs from services travelling in the down direction (Uphill) related to lack of adhesion or loss of traction.
Generally, a train travelling up a hill requires a higher coefficient of friction at the wheel rail interface for the wheels to maintain traction (before the wheels start to slip). The same train, coming down the same hill can maintain adhesion (before the wheels start to slide) at a lower coefficient of friction.
Figure 6: Average train speed all RSOs 1 September 2020 to 15 December 2020
Each coloured line represents a RSO and the average speed of all their train services that travelled down the mountain. The red dotted line indicates the speed limit in that section of track.
Source: ARTC
Track inspection and measurements
Transport safety investigators inspected the track on the day of the incident. The track area inspected extended from the stop point of the two locomotives and two wagons (approximately 92.000 km) up to 600 m prior to the first derailment site (approximately 94.300 km).
Observations of the track leading up to the first derailment site and the second derailment site were documented and photographs taken (Figures 7, 8 and 9). Initial assessment of the track condition was noted as not having any obvious defects that could be expected to increase the risk of derailment. Track measurements were taken by ARTC post incident. Superelevation[24] measurements were compared against design superelevation and short twist and long twist[25] were calculated.
The track leading up to the first derailment site, 93.810 km to 93.714 km was measured. ARTC had identified a point of first derailment at 93.710 km. The results of the track measurements at this location showed no exceedances of short or long twist.
Figure 7: Rail line leading to first derailment site
Facing Up direction (towards Unanderra and down the mountain)
Source: OTSI
Figure 8: Rail line between first derailment site and Signal WG1042U
Facing Down direction (towards Moss Vale and up the mountain)
Source: OTSI
Figure 9: Signal WG1042U to second derailment site
Facing Up direction (towards Unanderra and down the mountain)
Source: OTSI
Qube also contracted an engineering group to inspect the track post incident, who identified evidence of a derailment point, for the second derailment, at 93.220 km. However, the associated wagon and wheelset that made the markings could not be conclusively determined.
ARTC also took measurements of the rail track before and after the second derailment site. There were no exceedances of short or long twist found.
A contaminant was observed on the head of the rail lines across the area of track that was inspected. The contamination was more prominent in areas with more tree foliage. There was evidence of wheels rolling over and skidding through the contaminant at 94.000 km (Figure 10 and Figure 11).
Figure 10: Track contaminant at 94.000 km
Figure 11: Close up of track contaminant at 94.000 km
Pictures of the contaminant in Figures 10 and 11 were taken approximately 300 m prior to the first derailment, evidence of wheels rolling over and skidding through the contaminant Source: OTSI
Investigators collected a sample of the track contaminant from the rail head, near the site of the second derailment (93.150 km), for testing at the ATSB laboratories.
The ATSB testing indicated the substance was leaf matter. There appeared to be a secondary substance which was described as balled up and highly compressed (dark and greasy) in appearance which was probably from the leaves but could not be ruled out as coming from another source.
Track maintenance
The preceding six months’ maintenance history for the Unanderra to Moss Vale rail line was reviewed. ARTC had undertaken inspections of the running line between 91.080 km (the ARTC rail network boundary with Sydney Trains Rail Network) and 150.600 km (Moss Vale Junction).
Inspections undertaken included track geometry, rail wear, front of train inspection, rail lubrication and rail lubrication devices.
The frequency of these inspections was specified in ETE-00-03(Civil Technical Maintenance Plan(CTMP)) and ARTC records indicated these inspections had been completed as required.
However, the requested maintenance history records did not account for a rail lubrication device located at 97.030 km (Figure 12). This lubricator was located close to the Landmark and Dombarton (Figure 1 inset).
Following draft report feedback, ARTC produced a listing of all rail flange lubricators which included a rail flange lubricator at 97.030 km. ARTC also stated that this rail flange lubricator serviced trains travelling on the down (uphill) (Figure 12). No additional maintenance records were provided with the revised list.
Figure 12: Rail flange lubrication device at 97.030 km and grease plume
Facing Up direction (towards Unanderra and down the mountain) device (left) and close up (right), this section of track was bi-directional
Source: Qube
General inspection of rail flange lubrication over this section of the rail line was last conducted between 96.893 km and 150.600 km on 14 June 2020, approximately six months prior to the incident.
The inspection intervals for rail flange lubricators were specified as once every 365 days. All rail flange lubrication devices listed in the maintenance records provided, from the ARTC boundary to Moss Vale Junction were inspected and deemed compliant on 30 August 2020, approximately 3.5 months prior to the incident.
The closest rail flange lubrication device to the one located at 97.030 km to have had a recorded general inspection was at 95.580 km on 30 August 2020.
Track Standards
ARTC’s Engineering Practices Manual, Civil Engineering, RC 2411 (Guidelines for Trackside Lubrication) stated on page 4:
Under very severe grade conditions (more than about 1:50 in either braking or climbing direction), lubricators on the Up and Down rails should not be positioned any closer than 0.5km of each other.
Approximately 1.2 km before the first derailment site, two rail flange lubricators providing lubrication for the down rail line (uphill) were located at 94.26 km and 94.30 km, 40 metres apart, the rail flange lubricator at 94.30 km was not listed on ARTC’s maintenance history records (see Figure 13).
Additionally, two rail flange lubricators listed in ARTC’s maintenance history records at 94.958 km and 94.535 km were less than the required 500 m separation stipulated in RC 2411.
Figure 13: Rail lubrication devices leading to left hand curve and site of first derailment
Facing Down direction (towards Moss Vale and up the mountain).
Source: OTSI
ARTC CoP (Code of Practice Rail)section 1.2.6.4 Performance Requirements stated:
Rail lubrication systems should be designed to meet the following performance requirements:
• The friction coefficient on the gauge face of outer rails on curves should be < 0.25
• The friction coefficient on the top of rail contact surfaces of both rails should be > 0.3 (> 0.40 preferred) and > 0.40 on grades steeper than 1 in 50
• A lower friction level may be acceptable on the contact surface in the immediate area of the lubricator (within 50 m)
• It is also desirable that the difference in the running surface friction coefficients between the high and low rails should be < 0.15.
Sufficient rail lubricant shall be applied to the gauge face of the outer rail of curves, so that rail wear and flanging noise are minimised. Note: The friction testing should be carried out with a tribometer[26] and cover at least 100 m in each track section to be assessed.
ARTC was requested to provide results of any friction testing undertaken on the Moss Vale to Unanderra rail line between Summit Tank Service Crossing (100.222 km) and Dombarton Down Signal WG1043 (92.222km), in the period from 1 January 2017 to 31 December 2021. They did not provide any results from friction testing conducted, in the requested period and stated in feedback that the Code of Practice does not require on-going coefficient of friction measurements.
ARTC noted:
The monitoring of rail friction levels is deliberately not mandated as the risks associated, firstly, could not be effectively managed through a process (not practical or achievable within the variation of the friction over vast track length and rapid change factors). Secondly, are not related to any high risk which has been identified as justifying monitoring as a SFAIRP control.
The nature of steel wheel on steel rail is such that the friction coefficient will vary significantly according to various factors including the nature of the steel in the rail and the wheel, temperature and presence of materials such as water (rain), grease, oil, sand and vegetative material such as leaf debris. The reality is that the friction coefficient on any railway changes significantly and vary significantly between the 2 rail lines that run parallel to each other only 4 feet apart. It is impossible in such circumstances for ARTC to be attempting to prescribe a level of friction coefficient, and ARTC has not sought to do so.
The purpose of (the CoP) is to provide guidance in rail management, not to prescribe criteria for operating conditions that are actually beyond the control of ARTC.
ARTC does not warrant, and RSOs should not expect, any particular level of friction coefficient, or for the friction coefficient to be above or below any specified level. What ARTC does embrace, and for the benefit of RSOs, is to manage the Network in a manner that safely reduces the wear on rail and wheels, including the use of rail lubrication devices at appropriate locations, where ARTC seeks to reduce the friction coefficient.
On 3 June 2021, 6 months post the incident, friction tests were conducted by Monash Institute of Railway Technology, commissioned by Qube. The testing was conducted between 97.580km (500 m before Dombarton in the direction of travel) and 95.461km (1.5 km after Dombarton in the direction of travel). The tests were undertaken using a push tribometer as required in the ARTC Code of Practice.
All tribometer measurements were performed under dry conditions and were conducted at four separate sites. The results are in Table 4.
Table 4: Tribometer measurements
Site
Tribometer test/ Grease pot location
Friction coefficient top of rail (range)
Friction coefficient top of rail (average)
1
97.4km to 97.2km
Up rail – 0.17 to 0.22
Down rail – 0.17 to 0.35
0.2
0.26
2
97.11km to 97.078km
Up rail – 0.24 to 0.37
Down rail – 0.19 to 0.24
0.32
0.2
Lubricator @ 97.03km (Down rail)
3
97.03km to 96.925km
Up rail – 0.3 to 0.4
Down rail – 0.26 to 0.37
0.36
0.32
4
95.77km to 95.461km
Up rail – 0.16 to 0.29
Down rail – 0.2 to 0.33
0.23
0.26
Lubricator @ 95.58km (Up rail)
Observation
Across the four sites tested relevant to this incident, the friction coefficient on the top of the up and down rails was lower than the design standard of 0.4 for grades steeper than 1 in 50. Also of note the friction coefficient in some locations under dry conditions was lower than the design standard of 0.3 for all other gradients.
Rollingstock
The rollingstock was supplied to Qube by CFCLA under a lease agreement. The locomotives were maintained by CFCLA under its agreement with Qube. The wagons were primarily maintained by a contracted rollingstock maintainer to CFCLA and Qube in line with the lease agreement.
The rollingstock involved in the incident included:
2 CM Class Locomotives, CM3316 and CM3304
39 CGSY bottom dump grain hopper wagons
2 CGDY bottom dump grain hopper wagons.
The length of the train was 679.3 m.
CM class locomotives
The CM class locomotives were manufactured in 2012-13. They had a 22 t axle load and maximum gross power of 3300 hp (2460 kW). They were fitted with a Wabtec Fastbrake braking system and dynamic brake. They were also fitted with the Q-Tron QES-III locomotive control system that would provide an adhesion control function. The functional requirements for the adhesion control function as specified in Schedule 3 (Technical Specifications of MP33 Locomotive for CFCLA Rail JV) were:
If poor wheel-to-rail adhesion persists, causing the horsepower of the locomotive to fall below a set percentage of the rated value, or a synchronous slip is detected, sand shall automatically be applied.
A train lined wheel slip indication shall be included.
The Locomotive Information Pack for the CM class locomotives[27] provided the operating conditions which included;
Maximum tractive effort – 414 kN, and continuous tractive effort – 363 kN, at a speed of 16 km/h
Peak dynamic braking effort – 244.6 kN, at a speed of 23.3 km/h.
The locomotive design fully provisioned mass at rail was 132 tonnes. The locomotive can carry 10000 litres of diesel fuel which would weigh 8500 kilograms and the weight of other provisions such as lube oil, water and sand, approximately 1 tonne. Therefore, the dry weight of the locomotive would be approximately 122.5 tonne.
Grain hopper wagons
There were two types of grain hopper wagons, making up the train consist of the grain train 3966. Thirty-nine wagons were CGSY type, brought into service on the NSW rail network in 2015. The other two wagons were CGDY type, brought into service on the NSW rail network in 2013. The grain hopper wagons were manufactured by China International Marine Containers Group Australia (CIMC), for CFCLA.
Before any rail vehicle was permitted to operate on a rail network, they were required to comply with the minimum operating standards of the rail network owner. The measurement of brake block forces was one of several vehicle compatibility tests conducted to ensure the vehicle complied with the minimum operating standards for rollingstock. Tests were conducted on one of every type of vehicle, prior to that type of vehicle operating on the rail network. This is known as the Type Test.
The average measured brake block force was used to calculate the net brake ratio (NBR). NBR is the sum of the measured forces applied by the brake blocks onto the wheels divided by the weight of the vehicle and is determined for both tare and gross (loaded) vehicle mass. For a loaded vehicle the minimum NBR specified by AS7510.2:2014 was 13% with a brake cylinder pressure of 350 kPa, for vehicles fitted with high friction composite brake blocks. ARTC’s standard WOS 01.400 also recommended an NBR of 13% in order to provide effective braking without skidding wheels. The brake blocks fitted to the CGSY and CGDY wagons were FIP HA30 high friction brake blocks.
The results of the type tests for the CGSY and CGDY wagons were provided by CFCLA. A brake block force test conducted on 13 September 2015, on wagon CGSY 4519A, achieved an NBR of 14.23% for the loaded vehicle. A brake force test conducted on CGDY 4027, on 14 September 2013, achieved an NBR of 15.79%.
Both wagon types had CIMC 120AK brake componentry, a two-pipe train braking system. The two pipes being a brake pipe and main reservoir. This system allowed for an improved recharge time of the brake pipe pressure and greater control of the train braking performance (see Means of operation – wagons).
Two-pipe braking systems on grain wagons was a requirement in ARTC’s Route Access Standard for the Moss Vale to Unanderra rail line, where the trailing tonnes was greater than 2400 t, as with 3966.
Inspection and maintenance of the brake blocks and brake adjustments were primarily completed by a contracted rollingstock maintainer, consistent with the lease agreement.
History of CGSY wagons
After delivery of the CGSY wagons into service, issues with the braking performance of the wagons were identified. CFCLA had investigated the issue and concluded the braking performance was unsatisfactory. As a result, CFCLA required the brake rigging ratio to be increased to improve the braking performance.
To achieve this, slack adjuster pivot holes were re-drilled in the brake lever (Figure 14).
Following this modification to the brake lever, CFCLA found that the braking performance of the wagons had not improved and advised the original engineering manufacturer (OEM) CIMC that they had undertaken modifications to the brake lever ratio to improve brake performance which was not successful and requested advice from CIMC on a possible fix. The detail of the modifications made by CFCLA was not provided to CIMC.
Observation
The configuration and change management processes employed to manage this modification to the wagons was not effective.
CIMC’s review of the wagon’s design identified an error in the brake rigging system, in the setup of the control rod on the slack adjuster. The control rod on the slack adjuster had been fixed to the wagon structure. This did not permit the slack adjuster to perform its primary function of reducing the slack in the brake system. This resulted in the brake cylinder piston travel increasing as brake blocks wear, with an eventual reduction in brake block forces on the wheels.
CIMC revised the design to incorporate a control lever.
Figure 14: Revised slack adjuster pivot holes
Source: Wayne Clift Consulting
When the revised control lever design was fitted by CFCLA to a trial wagon, they found there was no change to the operation of the brakes. The slack adjuster was still unable to reduce the slack in the brake rigging.
In March 2017, an independent subject matter expert (SME) was engaged by CIMC, to assess and determine the root cause of the braking issue on the CGSY wagons.
Conclusions and recommendations from the SME were as follows:
4. CONCLUSIONS
4.1. The issues relating to the slack adjuster operation were resultant from:
4.1.1. Change to the brake lever ratio by CFCLA not concisely reported back to the Chinese manufacturer.
Advising the manufacturer of the changes made to the brake lever ratio, would have ensured the proposed control lever would have had corrected dimension to accommodate.
4.1.2. Lack of brake rigging setup and slack adjuster operation training.
4.2. Once the correct setup geometry was established the slack adjuster performed as per specification.
4.3. The Brake Cylinder Stroke as specified appears excessive.
4.4. The change to the brake ratio initiated by CFCLA will deliver high NBR% bordering on excessive.
5. RECOMMENDATIONS
5.1. Brake force tests be undertaken with rigging as modified by CFCLA to confirm NBR% for loaded and empty conditions once first wagon is modified with correct control lever. No other wagons should be modified until this is confirmed.
5.2. Dependent upon outcome of 5.1 all wagons to be fitted with control levers.
5.3. Brake Cylinder travels be set to achieve either 85mm (Rigging Ratio of 6.45) or 70mm (Rigging Ratio of 5.07)
5.4. A training course be considered for staff to ensure competency in the principles of brake rigging and slack adjuster operation.
5.5. Critical changes made to the wagon should be reported back to the OEM to ensure continuity.
On 20 April 2017, the same SME was engaged by CFCLA to conduct the first article compliance inspection and testing sign-off and to provide a report on the revised control lever design. The SME conducted testing on CGSY 4542H and found and recommended the following:
The Control Lever design requires modification to the clevis opening from the current 76mm to 100mm to permit fitment over the existing D Shackle. The brake pin length will need to be extended to suit.
The arrangement drawing requires more detail on location of the control lever fulcrum bracket as per the appended report detail.
The revised control lever pin hole position and fulcrum bracket location is compliant with industry standards and now permits the slack adjuster to operate correctly.
Due to the use of Resilient Chevron pads between the wheelset and bogie frame, block clearance is compromised due to the compression of this pad during loaded brake applications.
- Hence the proposed BC Stroke of 85mm has been amended to 130mm nominally to ensure a minimum block clearance of 9 – 10mm.
- This stroke setting also permits removal of a new brake shoe without having to lengthen the slack adjuster manually.
The operation of the Slack adjuster was observed and found to be fully compliant with industry practice. The slack adjuster was observed to return the brake cylinder stroke to nominal setting within 3 full-service brake applications.
Brake force testing was conducted in accordance with industry practice and results were compliant with ASA requirements, NBR – 15%
CGSY wagons fitted with the modified slack adjuster control lever in accordance with the findings of this report will provide regulated brake cylinder stroke consistently, irrespective of brake block wear.
On 22 April 2017, a train consisting of 40 CGSY wagons was involved in a runaway down the Illawarra Mountain (see Related Occurrences).
On 18 May 2017, as a result of the runaway on 22 April 2017, the NBR was tested on CGSY 4502V and found to be 13.9%. This wagon was the 38th wagon in the train consist and was randomly chosen for testing.
On 10 July 2017, the CGSY wagons were returned to CFCLA and taken to Goulburn for care and maintenance. During this time, the CGSY wagons were modified with the slack adjuster control lever. They were returned to service on 3 April 2018, to service other bulk grain contracts.
On 16 November 2020, the CGSY wagons recommenced operation on the Moss Vale to Unanderra rail line. Qube provided information to confirm the wagons had received a 28 day periodical maintenance on 5 November 2020 and assurance FX exam brake tests had been conducted post return of the wagons to Qube.
The wagons completed 12 journeys on the Moss Vale to Unanderra rail corridor, including a trip two days prior to this incident journey on 15December 2020.
Train weight
There were several sources of data providing varying values of the weight of the train.
The load out tonnes[28] from Temora BFB[29] was 2703.9 t in 40 wagons + 1 empty wagon. This equated to a trailing tonnage of (39 x 23.2 t + 2 x 22.7 t + 2703.9 t) = 3654.1 t.
The train driver’s hand-written train consist stated the trailing tonnage was 3690 t. However, each loaded wagon was noted as 90 t which equated to a trailing tonnage of (40 x 90 t + 22.7 t) = 3622.7 t.
Qube’s computer printed train consist, provided when requested for copies of the train consist, had loaded wagons weighing 89 t each which equated to a trailing tonnage of (40 x 89 t + 1 x 22.7 t) = 3582.7 t.
The train consist provided to ARTC, from Qube, had a declared weight of the train of 3198 t, which included a declared weight of the locomotives at 123 t each. The trailing tonnage, according to this train consist, was (41 x 72 t) = 2952 t. The 41st wagon was indicating it was loaded which was incorrect. This declared weight was significantly lower (by 456.1 t) than the weight of the train calculated on the Temora BFB load out tonnes. This was a 12.5% difference.
The two remaining wagons from the derailment were taken to Port Kembla for unloading and weighing. CGSY 4516T and 4518Y total grain weight was 134.385 t, as observed on the belt weigh system at Port Kembla. The average weight for each wagon was therefore (67.2 t + 23.2 t) = 90.4 t.
Using this figure to estimate the trailing tonnage equated to (40 x 90.4 t + 22.7 t) = 3638.7 t.
This weight was greater than the declared weight to ARTC, the driver’s hand-written train consist and Qube’s computer printed train consist, but less than the trailing weight calculated using the load out tonnes from Temora BFB and below the maximum allowable trailing weight (3680 t) as per ARTC TOC Waiver 16002[30].
It was noted that the train journey required 3966 to traverse the TfNSW rail network[31]. As per the TfNSW TOC Manual (TS TOC.2.2020 Issue 2 v19.0 2 September 2020), the load tones for freight trains travelling on the rail line from 91.080 km to Unanderra was a maximum of 3300 t for locomotives of class L3, as the CM locomotives were. Based on this, the train weight was greater than the allowable tonnage (on the TfNSW rail network) on all records of the train weight, other than the train consist provided by Qube to ARTC and TfNSW, which had a declared weight of 3198 t.
The trailing load was also measured by ARTC’s Exeter wayside detector at 0248 hrs, 15 December 2020. The wayside detector calculates a weight in motion and uses specific locomotive classes as weight references to conduct an automatic calibration at every pass of one of the reference locomotives. ARTC stated the wayside was not a certified weighbridge but achieved a +/- 3% accuracy.
It was noted that the weight of the locomotives provided by the wayside detector were within 1% of the calculated weight of the locomotives, accounting for indicative fuel levels in the locomotives (taken from the data logger) and their tare weight.
It was also noted the wayside detector recorded the last wagon in the consist CGDY 4026 at 27.67 t, approximately 4.5 t higher than its documented tare weight. ARTC provided data from the wayside of the previous two tare weights taken of CGDY 4026, which indicated the tare weight as 25.53 t on 5 December 2020, and 26.0 t on 21 October 2020. The tare weights of other CGDY wagons taken by the wayside monitor on 21 October 2020 indicated the average tare weight of the CGDY wagons was 27.5 t.
These readings indicated the tare weight of the CGDY class wagon was not the documented 22.7 t as registered with the infrastructure manager.
The total trailing weight measured was 3748.5 t. With consideration of the +/-3% accuracy, the train was between 3636.045 t and 3860.95 t (Figure 15). This indicated the train may have been running heavier than allowable tonnage limit of 3680 t.
There was also variability in wagon weights of approximately 7%, ranging from 90.65 t to 96.44 t. The wayside data indicated 20 of the 41 wagons were over the allowable loaded wagon weight limit of 92 t.
Figure 15: Exeter wayside detector read out
Source: ARTC
While it could not be established with 100% certainty what the trailing weight of the train was, the total load out tonnes from Temora BFB plus the tare weight of the wagons was considered most representative as all other sources were only estimates of the grain weight in the wagons.
ARTC’s wayside detector at Exeter was considered an indicative source of weight in each wagon, which highlighted a 7% degree of variability in the amount of grain loaded in each wagon across the train consist. It also highlighted specific wagons were likely overloaded.
These combined indicated the weight of the train was near maximum allowable tonnage and probably under the 3680 t limit for the train. However, it was likely a number of these wagons were over the allowable limit for a single wagon and there was variation in loading across the train consist.
Observation
Inaccurate reporting of train weights presents an increased risk to operations, particularly when trains are operating heavier than expected.
Rollingstock inspections
Prior inspections
The most recent wagon periodical maintenance (28 day) inspection was conducted in Goulburn by a contracted wagon maintainer and signed off for release back into service on 25 November 2020, 20 days prior to the incident.
Post-incident inspections
Transport safety investigators’ observations of the rollingstock on the day of the incident included the portion of the train which had not derailed, the locomotives and two wagons (Figure 16), and both sites where rollingstock had derailed.
Figure 16: Stop point of runaway train 3966
Source: OTSI
On arrival at the locomotives and two wagons it was observed that the coupler knuckle was closed and locked on the back of the second wagon CGSY 04518Y and that both main reservoir (MR) and brake pipe (BP) isolation cocks were closed. It was later confirmed that the driver’s assistant had isolated the cocks post derailment to stop air leaking from the main reservoir and brake pipe.
The locomotives were shut down because noise from the running engines was disturbing nearby residents. Isolation cocks for the locomotive’s bogies and brake equipment appeared to be in the correct orientation when inspected.
The wheels on the remaining connected wagons showed some signs of heat (see Figure 17). There were no visual signs of flat spots on the wheels. This was later confirmed when the rolling stock was tested on 17 December 2020, prior to moving to Port Kembla to unload the wagons. Sand was also evident on the rail head located under the wagons and locomotives.
Figure 17: Back of 2nd wagon CGSY 04518Y
Source: OTSI
The brake shoes were in contact with the wheels across both locomotives and wagons. The contact patch of the brake shoes was not aligned with the wheel diameter on some wagons (Figure 18).
Figure 18: Side of 1st wagon CGSY 04516T brake shoe
Source: OTSI
On 17 December 2020, two days after the incident, testing on the rollingstock that had not derailed was conducted, to ensure the braking systems were operating to standard. The wagons were tested for brake pipe leakage rate (5 kPa/min) and given a brake holding test (13 mins). These were within specified limits.
The lead locomotive CM3316 had a functional brake test conducted by CFCLA and was given a Locomotive Ready to Go Certificate prior to the locomotives and two wagons being driven down to Port Kembla to unload and weigh the grain.
The trailing locomotive CM3304 brake function test was not conducted post incident. The locomotive event logger data for CM3304 indicated the control system acted as designed, with the air brake system and dynamic brake system performance recorded.
Net braking ratio tests
The NBR is the ratio of the sum of the measured actual brake block forces in kilograms divided by the total vehicle mass, in kilograms, at rail.
Qube conducted NBR tests on the two remaining CGSY wagons (4516T and 4518Y) that did not derail in the incident. The testing was conducted at Junee on 9 February 2021 by a qualified rollingstock engineer, under the observation of representatives from CFCLA.
The NBR test results were:
CGSY 4516T was 12.45%
CGSY 4518Y was 10.7%.
These results did not meet the minimum design standard net braking ratio for vehicles fitted with high friction composition brake blocks. Noting that the standard applied to new vehicles only and there was no requirement to test NBR on an ongoing basis.
The RISSB Standard AS 7510.2: 2014 Braking Systems – Part 2 – Hauled Rolling Stock stated:
The automatic air brake of a vehicle fitted with high friction composition brake blocks shall be designed to achieve a Net Braking Ratio of 13% to 16% with a Brake Cylinder pressure of 350kPa.
As per ARTC’s WOS 01.400 Freight Vehicle Specific Interface Requirements Issue 1.0 Dec 2005, the NBR for vehicles fitted with high friction brake blocks, fully loaded, recommended 13% to provide effective braking without skidding wheels.
Transport for NSW RSU 400 Series – Minimum Operating Standards for Rolling Stock – Freight Vehicle Specific Interface Requirements V2.0, issued 24 August 2017 required 16% NBR to be used as a minimum for all new rollingstock and provided the conditions when the net braking ratio was lower than 16% but higher than 13% (for existing rollingstock):
Figures less than 16%, down to 13% net brake ratio as a minimum, may be accepted; however the wagons will require a dynamic brake test in the loaded condition in a comparable consist to confirm that the train consisting of these wagons is able to stop within the brake performance curves applicable for the operating corridor.
As mentioned in Grain hopper wagons, the type test for the CGSY wagons was found to be greater than 13% but lower than 16%. The type test conducted on CGSY 4519A confirmed the NBR for the wagon was 14.23%.
It was understood by CFCLA at the time that the requirement for all new bulk commodity type wagons became effective as of 1 January 2018. The CGSY wagon type was published in the ASA Train Operating Conditions (TOC) Manual version 11.0 on 15 December 2017 with unrestricted operating conditions.
The two NBR tests on the remaining wagons could not statistically be considered representative of the entire consist. However, the NBR on a freight wagon should not be significantly different to other wagons of the same design assuming they are all built to the same drawings. The CGSY wagons had varying measured NBRs from 19.5% down to 10.7%, as seen from the various tests conducted on different CGSY wagons over their service life.
Post this incident on 15 December 2020, there remained five CGSY wagons in the fleet.
As noted in Net braking ratio tests, the NBR tests conducted on 9 February 2021 returned 12.45% and 10.7%.
The other three CGSY wagons not involved in the incident were tested on the 12 May 2021 and results were, CGSY 4542H – 12%; CGSY 4503H – 19.5%; CGSY 4513P – 14.5%.
It was noted that CGSY 4542H was modified by the SME to improve its brake performance. The NBR of this wagon when tested on 20 April 2017, post modifications, was 15.0% (see History of CGSY wagons).
Wagon brake pipe continuity
The ‘brake pipe’ is critical to the functionality of a train’s braking system. This pipe, which runs along the length of the train, provides the means through changes in air pressure to effect application and release of the train’s brakes (see Means of operation – wagons). A disruption in the continuity of this pipe, such as a brake pipe tap closed between wagons, will result in less wagons providing braking force.
To ensure brake pipe continuity and the correct functionality of a train’s brakes throughout the consist, the brake system is tested prior to commencement of a train’s journey. For the accident train, these tests were performed the previous day, with one wagon (of the 41 attached to the train) identified as having its brake components isolated.
In addition, Qube undertook a comparison of the time taken to recharge the brake pipe on the day of the accident (15 December 2020), against that of the train’s previous journey on 12 December 2020.
Qube found that there was no appreciable difference in the time taken to recharge the brake pipe between the two services, supporting the brake pipe was fully connected and continuous throughout the train consist on the day of the accident.
Contact patch of brake blocks
It was observed in the post incident inspection that some of the brake blocks on the wagons were not in contact with the wheel on the leading edge of the brake block. Qube also found this during their inspections and considered the gap at the outer edge of the brake blocks a contributor to lowered coefficient of friction[32] at the brake block/wheel interface. The reduced contact area between block and wheel also results in higher heat in the block contact area, which increases the risk of brake fade.
The manufacturer of the brake blocks had conducted tests of the high friction brake blocks in 2017. The testing indicated that brake block friction generally reduced as speed increased; and when the brake blocks were wet. Additionally, brake blocks were more susceptible to reduced friction with the wheel when the block had a gap at the leading edge of the brake block.
Of the 41 wagons attached to the accident train, the two remaining upright wagons with brakes applied were observable and found with gaps at the outer edge of the brake block.
There was evidence of a heat stripe (blue discolouration on metal occurs at approximately 300 degrees Celsius) on the left rear wheel of wagon CGSY 04518Y (see Figure 17). This indicated the contact patch from the brake block to the wheel was not consistent and evenly applied across the wheel. The corresponding right wheel did not show signs of heat build-up (no blue discolouration) to the same extent as found on the left wheel.
The wheels on CGSY 04516T and on the Locomotives showed very little signs of heat (no blue discolouration was present).
Train braking system
General description
There are three braking systems fitted to the CM class locomotive in addition to the parking brake. These comprise of two types of air operated (pneumatic) brake, that is, the automatic and independent, and an electrical dynamic brake. The use of each of the three braking systems is dependent on the circumstance during which braking effort is required.
Automatic brake
Introduction
The ‘automatic brake’ controls the brakes on the entire train, including the wagons and locomotive/s. Central to this system is the brake pipe, which runs along the length of the train. Changes to air pressure within the brake pipe regulate the application and release of the train’s brakes. When fully charged (that is, brakes released), the brake pipe pressure is about 500 kPa. Reduction of this pressure by the driver results in application of the train’s brakes.
Driver controls
The driver regulates the pressure within the brake pipe through operation of the automatic brake handle (see Figure 19). The brake handle positions on the CM class locomotive are:
Release – brake pipe charging or charged up to 500 kPa, which releases any automatic brake applied to the locomotive/s and wagons.
Minimum service – reduces the brake pipe pressure to 450 kPa which initiates a minimum application of the brakes on the locomotive/s and wagons.
Service zone – a graduated reduction of the brake pipe pressure from 450 kPa to 350 kPa, which correspondingly increases the braking forces at a graduated rate.
Full service – reduces the brake pipe pressure to 350 kPa which fully applies the brakes on the locomotive/s and wagons.
Suppression – reduces the brake pipe pressure to 350 kPa for the purposes of penalty brake[33] suppression and reset.
Handle off – reduces the brake pipe pressure to 0 kPa. This handle position configures the locomotive such that it cannot be used for initiating braking commands.
Emergency – rapidly reduces the brake pipe pressure to 0 kPa which quickly provides a full service brake application to the locomotive and wagons (see Means of operation – wagons).
Figure 19: Automatic and independent brake handles
Source: OTSI
Means of operation – wagons
In addition to the brake pipe, each CGDY and CGSY wagon was fitted with a pneumatic control valve, auxiliary reservoir, relay valve, supplementary reservoir and brake cylinders. The control valve responded to changes in pressure within the brake pipe. On sensing a reduction in brake pipe air pressure, the control valve would reduce the auxiliary reservoir air pressure by an equal amount. This auxiliary reservoir air would supply reference (signal) air to a relay valve, in-turn permitting air from the supplementary reservoir (continuously supplied by main reservoir air from the locomotive)[34] to enter the brake cylinder. A piston within the brake cylinder would then push the brake blocks against the wagon wheels, causing friction and slowing of the train (see Figure 20).
Figure 20: Wagon airbrake application process
The image is a simplified representation of an airbrake application on a wagon. The control and relay valves consist of rubber diaphragms, springs and ports that respond to air pressure differences to perform their functions. Source: OTSI
In effect, on two-pipe trains (as with the CGDY and CGSY wagons) the pressure in the brake cylinder is directly proportional to the air pressure reduction in the auxiliary reservoir. Maximum braking effort is achieved when brake pipe pressure is reduced to 350 kPa, known as a ‘full service’ brake application. At this point the brake pipe, auxiliary reservoir and brake cylinder pressures equalise with each other at about 350 kPa. Therefore, further reductions in brake pipe pressure do not result in increased braking effort. Table 5 provides an overview of braking system pressures in response to various brake pipe pressures.
Table 5: Automatic brake pressure equalisations for a 500 kPa brake pipe[35]
Automatic brake handle position
Brake pipe (kPa)
Auxiliary reservoir (kPa)
Brake cylinder (kPa)
Release
500
500
0
Minimum service
450
450[1]
118[2]
Service zone (example pressure)
400
400[1]
235[2]
Full service
350
350[3]
350[2]
Emergency
0
350[4]
350
[1] Auxiliary reservoir equalises with the brake pipe. [2] Brake cylinder pressure equates to about 235% of the pressure loss in the auxiliary reservoir. [3] Auxiliary reservoir equalises with both the brake pipe and brake cylinder. [4] Auxiliary reservoir equalises with the brake cylinder, preventing further equalisation with the brake pipe.
In a similar manner to the wagons, a reduction in brake pipe pressure also applies the brakes on the hauling locomotives. For a CM class locomotive, the maximum automatic brake applied locomotive brake cylinder pressure attainable is also 350 kPa.
Once the required speed reduction has taken effect, the driver places the automatic brake handle in the ‘release’ position which restores the brake pipe pressure to 500 kPa. On sensing an increase in brake pipe air pressure, the control valve allows air from the brake pipe to recharge the auxiliary reservoir to 500 kPa.[36] In addition, brake cylinder air pressure is vented to atmosphere allowing a spring within the brake cylinder to force the piston to retract, thereby removing the friction force of the brake blocks from the wagon wheels (see Figure 21).
Figure 21: Wagon airbrake release process
The image is a simplified representation of an airbrake release on a wagon. The control and relay valves consist of rubber diaphragms, springs and ports that respond to air pressure differences to perform their functions. Source: OTSI
With brake pipe operated pneumatic braking systems, the brakes on the train do not apply simultaneously. As brake pipe pressure is vented from the lead locomotive, the brakes on the leading wagon apply first, followed sequentially by the other wagons towards the rear of the train.
Similarly, when a train’s automatic brakes are released (actioned by the lead locomotive), there is a delay in the entire train’s brake pipe (and auxiliary reservoirs) recharging, particularly towards the rear of the train. A review of the incident train’s data logger indicated that it took about 26 seconds for the brake pipe to fully recharge after a minimum service (50 kPa brake pipe reduction) application. For a 70 kPa reduction in brake pipe pressure, this increased to over 50 seconds for a full recharge. That is, the greater the brake pipe pressure reduction, the longer it took to fully recharge the brake pipe and auxiliary reservoirs back to 500 kPa along the entire length of the train in readiness for another brake application.
Brake pipe charging flow indicator
During an automatic brake release, main reservoir air, produced by the main compressor on the locomotives, recharges the brake pipe to 500 kPa. Although brake pipe pressure is restored relatively quickly at the front of the train, this does not accurately reflect brake pipe pressure along the length of the train. To assist the driver in determining whether the brake pipe is fully recharged in readiness for another brake application, a brake pipe charging flow indicator is provided.
Due to the sensitivity of the brake pipe charging flow indicator, it is possible to detect small losses in brake pipe pressure. This is particularly useful in alerting the driver to a derailment or train separation[37] event towards the rear of the train, whereas the brake pipe pressure on the locomotive may indicate little or no pressure loss.
On the CM class locomotive, the brake pipe charging flow indicator is on a computer display unit (CDU) on the driver’s control station. The indicator consists of a numeric value of main reservoir to brake pipe air flow expressed in litres per minute. It is located at the bottom of a bank of similar numeric displays including the brake pipe, main reservoir and locomotive brake cylinder pressures (see Figure 22). There is no accompanying visual annunciator tile or audible alarm to draw the driver’s attention to the activation of the brake pipe charging flow indicator.
Figure 22: Driver’s computer display unit
Source: OTSI
Running out of air
As depicted in Table 5, a full service application of brake cylinder pressure (350 kPa) is achieved when the driver reduces the brake pipe pressure to 350 kPa. However, this is dependent on the auxiliary reservoirs on each wagon being fully charged to 500 kPa at the time the brake application is made.
Where the brake pipe has not been given a sufficient opportunity after an automatic brake application to recharge the brake pipe across the entire length of the train prior to the reapplication of the automatic brake, it will result in a lower auxiliary reservoir starting pressure, particularly on wagons at the rear of the train. As a result, there is a reduced pressure drop in the auxiliary reservoir when equalising with the brake pipe on the subsequent brake application. In response, the relay valve and supplementary reservoir provide less pressurised air to the brake cylinders, resulting in a reduced braking force than would be achieved if the auxiliary reservoir starting pressure is 500 kPa. Table 6 provides an example of this reduced brake cylinder pressure where an auxiliary reservoir has recharged to only 450 kPa prior to the reapplication of the automatic brake.
[1] Note: Braking system still in release mode, with the brake pipe in the process of recharging the auxiliary reservoirs. [2] Auxiliary reservoir remains equalised with the brake pipe, no brake cylinder pressure effected. [3] Auxiliary reservoir equalises with the brake pipe. [4] Brake cylinder pressure equates to about 235% of the pressure loss in the auxiliary reservoir.
In this example, the maximum achievable brake cylinder pressure in full service is about 235 kPa, where the auxiliary reservoir starting pressure is 450 kPa. This is one-third less than the 350 kPa brake cylinder pressure in full service where the auxiliary reservoir starting pressure is fully recharged to 500 kPa (refer Table 5).
This phenomenon of reduced available braking force due to low starting auxiliary reservoir pressure is termed ‘running out of air’. In summary, the lower the starting pressure of the auxiliary reservoir at commencement of an automatic brake application, the lower the braking force available.
Partial braking force recovery when running out of air
As explained in Means of operation – wagons, the maximum braking effort achievable is a full service brake application, due to the concurrent equalisation of the brake pipe, auxiliary reservoir and brake cylinder pressures. That is, further reductions in brake pipe pressure below 350 kPa do not result in increased braking effort. The only exception is when the train’s braking system is running out of air.
In this unique scenario a further reduction in brake pipe pressure will result in increased brake cylinder pressure. By lowering the auxiliary reservoir pressure below 350 kPa, it is possible to force an equalisation of the brake cylinder pressure at a higher rate than is by then achievable in full service. For example, as discussed in Running out of air, where an auxiliary reservoir is only recharged to 450 kPa prior to the reapplication of the automatic brake, the maximum brake cylinder pressure available in full service will be about 235 kPa. However, by reducing the brake pipe pressure further, an equalisation between the auxiliary reservoir and brake cylinder pressures will occur at about 314 kPa (see Table 7).
As described in Driver controls, it is not possible for the driver to graduate the brake pipe below 350kPa, for example, to 314 kPa as noted above. The next available command after full service is either ‘handle off’ or ‘emergency’, both of which result in 0 kPa brake pipe pressure, at a service (controlled) rate for the former and at a rapid rate for the latter.
Table 7 summarises various scenarios of reduced auxiliary reservoir starting pressures. This is then compared to the maximum brake cylinder pressures available in full service, versus the maximum brake cylinder pressures available with the brake pipe pressure reduced to 0 kPa.
Table 7: Approximate maximum brake cylinder pressures from auxiliary reservoir starting pressure[39], [40]
Auxiliary reservoir starting pressure (kPa)
Maximum achievable brake cylinder pressure (kPa)[2] in ‘full service’[3]
Maximum achievable brake cylinder pressure (kPa)[2] with brake pipe at 0 kPa
500[1]
350
350
490
329
343
480
306
336
470
282
329
460
259
321
450
235
314
440
212
307
430
188
300
420
165
293
410
141
286
400
118
278
390
94
271
380
71
264
370
47
257
360
24
250
350
0
243
[1] Fully charged auxiliary reservoir, with expected starting pressure during normal operations. [2] Brake cylinder pressure equates to about 235% of the pressure loss in the auxiliary reservoir. [3] Brake pipe reduced to 350 kPa.
Importantly, despite the ability to increase available brake cylinder pressure with the brake pipe reduced to 0 kPa in instances of running out of air, it is not possible to again obtain the maximum braking force available as would be provided by full service with a fully charged auxiliary reservoir starting pressure.
Observation
While ordinarily a ‘full service’ automatic brake application provides the maximum pneumatic braking force available on a train, in the unique circumstance of a train ‘running out of air’, a lower brake pipe pressure results in an increase in the available braking force. However, this increased braking force would still be less than that available in full service had the auxiliary reservoir been fully charged at the time of the automatic brake application.
This option was available to the driver.
Independent brake
The ‘independent brake’ applies pneumatic brakes to the locomotive/s only, independently of any trailing wagons. It is operated by the driver using the independent brake handle on the driver’s control station (see Figure 19). On the CM class locomotive, it has two positions: ‘release’ and ‘apply’, with an intermediate graduated service zone. The independent brake can be graduated in both application and release. In the fully applied position, the locomotive brake cylinder pressure is about 500 kPa.
Dynamic brake
The electrical dynamic brake is designed to reduce locomotive fuel usage and wear on wagon componentry as occurs with pneumatically operated friction brakes. It provides a supplementary means of train-speed control that complements the train’s pneumatic automatic brake.
When dynamic brake is selected, it alters the locomotive’s traction motor fields from a tractive power to a generator configuration. The subsequent power generated by the rotating locomotive wheels is fed to resistor grids and dissipated as heat, resulting in a retarding force. This retarding force is limited to the locomotive wheelsets only, rather than dispersed across the entire train. Increasing or decreasing the amount of electrical resistance varies the braking effort on the rotating locomotive wheels.
On the CM class locomotive, the dynamic brake is selected by the driver moving the throttle/dynamic brake handle on the driver’s control station into the dynamic braking zone (see Figure 23).
Figure 23: Dynamic brake / throttle handle
Source: OTSI
Automatic brake relationship with dynamic brake
As described in Means of operation – wagons, when the automatic brake is applied air pressure develops in the locomotive’s brake cylinders. Simultaneous application of both the dynamic brake and locomotive brake cylinder pressure can result in potential wheel lock-up and wheel slide. To prevent this, a dynamic brake inhibit (DBI) function[41] is supplied as part of the Fastbrake air brake system. The DBI automatically releases any automatic brake applied locomotive brake cylinder pressure whilst dynamic brake is in use. Independent brake applied locomotive brake cylinder pressure is not affected by the DBI.[42]
The Fastbrake system provides the option for the owner/operator to specify during the locomotive design the activation of the dynamic brake knockout (DKO) function during an emergency brake application. When activated, the DKO causes the locomotive’s dynamic brake to disengage, and the automatic brake applied locomotive brake cylinder pressure to be restored. Wabtec advised, that where the optional DKO function is not fitted, the dynamic brake is retained during an emergency brake application, resulting in extra available braking effort.
CM class locomotive braking systems
General
Braking system specifications for the CM class locomotives was contained in Schedule 3 (Technical specifications of MP33 locomotive for CFCLA Rail JV).
Information (page 12) included:
Wabtec Fastbrake system shall be provided.
Cut-off brake pipe charging in the event of an emergency application for any source and will provide:
• Instantaneous power knockdown.
• Instantaneous brake pipe charging cut-off.
• Continuous DB until the independent brake is applied to 100kPa (15 psi), then DB knockdown [DKO] occurs.[43]
CM class locomotive dynamic brake
As discussed in Dynamic brake, Wabtec manual 31394P (FASTBRAKE Operations and Maintenance MPI-CFCLA Locomotives) allowed for a DKO option, specifically:
If the Dynamic Brake is applied when the emergency brake application occurs, it is optional to have the Dynamic Brake CUT-OUT immediately via the Dynamic Brake Knock Off (DKO) or maintained and employed at the operator’s discretion.
Neither this manual or the driver’s manual[44] for the CM class locomotive stipulated if the DKO function was active or omitted for the CM class locomotive. Wabtec Australia advised that the Wabtec manual included the statement (set out above) as the owner/operator of the locomotive could determine and specify the way they wanted this feature to work.
Subsequent testing found that the CM class locomotive DKO option was not active, resulting in the retention of the dynamic brake during emergency automatic brake applications.
While not related to the incident, additional testing by OTSI also found that retention of the dynamic brake during an emergency brake application resulted in the automatic brake applied locomotive brake cylinder pressure being suppressed by the DBI on the CM class locomotive. This meant that when travelling as a light engine[45] the stopping distance could increase in the event of an emergency, if:
dynamic brake was engaged
the automatic brake was placed in the emergency position
the independent brake was not applied.
While Wabtec addressed this issue in earlier brake system designs by stipulating that ‘during independent, emergency, or penalty brake applications, the dynamic brake interlock magnet [DBI] MUST NOT restrict the flow of air to the [locomotive] brake cylinders’,[46] Wabtec Fastbrake did not. Rather, the Fastbrake manual (31394P) stated that during an emergency brake application the:
…(DBI) function will release the locomotive’s brake cylinder pressure developed from the [automatic brake] emergency brake application.
In recognition of the possibility of increased stopping distances on light engines, 31394P advised that in the event of an emergency:
firstly, the independent brake was to be fully applied
secondly, the automatic brake was to be applied to the emergency position.
This critical instruction was not replicated in the driver’s manual for the CM class locomotive.
CM class locomotive power cut-out switch
The power cut-out switch (PCS) activates in circumstances of low brake pipe pressure, for example, if the driver selects ‘handle off’ or ‘emergency’. Once activated, it automatically removes tractive effort from the traction motors and returns the locomotive to idle. The purpose of this is to prevent locomotive traction power working against the train’s brakes in the event of an emergency brake application.
The CM class locomotive was fitted with this function, as stated in the operator’s manual (MP33C Locomotives MP33C Units CM3301 – CM3316), page 2-29:
If emergency braking is activated while the throttle / DB handle is in one of the power notches (1-8), the pneumatic control switch (PCS)[47] opens automatically to cut power to the traction motors. …
Similar information was contained in the driver training materials supplied by Wabtec to CFCLA on handover of the CM class locomotive. For the CM class locomotive, the PCS activated at pressures below ~280 kPa.
Historically, the PCS and DKO were both contained on the same electrical circuit, whereby at low brake pipe pressures both locomotive traction power and dynamic brake would disengage.
However, the electrical circuit configuration allowed for the separation of the two functions. Static testing by OTSI on a CM class locomotive found that:
An ‘emergency’ automatic brake application during dynamic braking resulted in a PCS, but dynamic brake stayed engaged.
A ‘handle out’ automatic brake application during dynamic braking resulted in a PCS, but dynamic brake stayed engaged.
Qube later repeated these tests on a moving locomotive with the same results.
Operational procedures
Qube had a documented work instruction for operations on the Moss Vale to Unanderra rail line. WI-540 (Moss Vale to Inner Harbour [Port Kembla] Train Management).
Requirements in WI-540 included a calculation of the tonnes per operative brake (TOB) and a requirement to record a brake release rollaway time at Summit Tank. These actions were in the instruction to ensure train crew were aware of key train handling characteristics, to assist train management.
Tonnes per operative brake
TOB is calculated by dividing the gross weight of the train (3966 was 3922.1 t) by the number of wagons with operable brakes. The 14th wagon CGSY4539Q had been identified on the train inspector’s certificate for 3966 as having non-operative air brakes. Therefore, the number of wagons with operable brakes was 40. For 3966, the TOB was 98.
WI-540 also specified the TOB for grain trains could vary in value up to 100. Train crews were required to calculate the TOB to determine braking effort required on down grades. Grain trains with a TOB that exceeded 80 generally required higher brake cylinder pressures to bring the train to a stop or control the train speed. Drivers needed to be mindful of this when operating trains down steep grades.
Brake release rollaway time test
The brake release rollaway time test was required to be performed to give the driver an appreciation of the brake release and recharge times of the automatic brake. The train was required to be stopped using a 100 kPa brake pipe reduction. Once stopped, the driver would release the automatic brake and the train crew recorded the time it took for the train to start moving without the application of traction power. If the train moved following the 100 kPa reduction in less than 45 seconds, extra care was required to ensure sufficient recharge of the automatic brake after a stop was made, before continuing down the grade. Further information to clarify what ‘extra care’ meant was not detailed in the work instruction, but this may have been appropriate due to the subjective nature of the term ‘extra care’.
Serial/Cycle Braking
WI-540 specified serial/cycle braking, where the dynamic brake is fully applied and the air brake graduated to control the speed of the train, as the preferred method if the TOB was less than 80 and only two locomotives were provided for dynamic braking. The procedure for serial/cycle braking was:
When speed reached 15 km/h, apply automatic brake to minimum reduction.
Apply further reduction in brake pipe pressure to ensure train speed is not increasing on the grade, do not exceed 100 kPa reduction if possible. The dynamic brake must be left in full applied position.
If train speed increased towards 30 km/h, make a heavier brake pipe pressure reduction or stop the train.
The train must be brought to a stop using the fourth consecutive brake application cycle.
Balance Braking
WI-540 specified balance braking, where the dynamic brake is graduated, as the preferred braking method if the TOB was more than 80 and two or more locomotives are provided for dynamic brake purposes. The procedure for balance braking was:
When speed reached 15 km/h, apply automatic brake to minimum reduction.
Check if weight of the train can be balanced on the grade, maintaining about 25 km/h.
If train speed increased, reduce brake pipe pressure to 425 kPa. If speed then balanced, maintain control using the dynamic brake.
If weight and speed could not be balanced using 75 kPa brake pipe pressure reduction and full dynamic brake, serial / cycle braking was to be used.
Additional instructions were provided in section 10 which required the train crew to stop the train and apply the locomotive independent brakes if at any time the brake pipe pressure needed to exceed 100kPa to control the train speed.
Section 13 of WI-540 re-iterated the requirements from the ARTC RAS General Information 10.6:
Where braking problems occur on descending steep grades, the train crew shall advise the Network Controller and:
• Stop the train
• Rectify the problem
• Advise the Network Controller before continuing
In an emergency situation, Section 14 of WI-540 provided the Emergency Train Management Procedures which stated:
If in the event the train operation transition from standard train management to emergency train management, the following steps are to be completed:
• The automatic brake valve handle is to be placed into the full service position do not place the handle into the emergency position
• The dynamic brake handle is to be placed into the full position
• The independent brake must be manipulated so that the brake pressure does not exceed 100 kPa (the dynamic brake interlocking will activate at 105 kPa and the train will suffer a loss of dynamic brake capability)
• Operate the locomotive sands
• Train crew are to initiate an emergency call utilising the ICE Radio and communicate the current situation to the NCO
Related occurrences
El Zorro Transport, 7 February 2011
Loaded grain train 3996, travelling to Inner Harbour, Port Kembla, ran away as it descended the rail line between Summit Tank and Unanderra. The driver was unable to control the speed of the train towards the end of the descent. The 2988 t train was 691 m in length.
The investigation found that the driver did not test their air brakes at any stage after leaving Moss Vale although this was common practice. Several other RSO’s driving procedures included the requirement for a driver to stop in the vicinity of 107.000 km and make a 100 kPa automatic brake application. After coming to a stand and only after all pressures had equalised, was the driver to release the independent brakes on the locomotive and then release the automatic brake. As soon as the brakes were released, the driver was to note the elapsed time in seconds before the train began rolling. This gave the driver an understanding of the recharge rate for the brake pipe and the timing of the release of the exhaust chokes on the wagons.
Between Summit Tank and the point at which 3996 came to a stand, the driver made several brake application and releases. Only on two of these occasions did the brake pipe air pressure return to full pressure (500 kPa). Also, successive brake applications were greater than the preceding application, indicating the driver was having trouble controlling the train as it increased speed due to ‘running out of air’.
Qube Logistics, 22 April 2017
Loaded grain train 8960, travelling from Bogan Gate to Inner Harbour, Port Kembla, ran away as it descended the rail line between Summit Tank and Unanderra. After passing Dombarton, the driver realised he had lost control of the train. At 1248, the driver contacted the ARTC network controller who, in conjunction with Sydney Trains’ train controller, cleared a pathway for 8960.
The maximum allowable speed for the Dombarton to Unanderra line was 30 km/h; however, the train reached a maximum speed of 107 km/h. At 1255, the train stopped, assisted by a shallower gradient near Unanderra station. There were no injuries or damage because of the incident.
The investigation found that as train 8960 was operated down the rail line between Summit Tank and Unanderra, the train management actions by the driver did not conform to Qube’s train handling procedures. After passing Summit Tank, the driver made ten brake applications and releases and in doing so did not allow the train’s automatic brake system to fully recharge. This resulted in a loss of necessary braking capability to be able to control the train’s speed on the steep continuous descent. The incident was further compounded when the driver’s actions (applying the independent brake) caused the locomotive’s dynamic braking system to be rendered inoperative, further reducing control of the train.
The braking system of 8960 was operating within specification and wagons were loaded below the maximum allowable payload (3680 t). However, the train was loaded by approximately 10% more than that recorded on the train’s consist record. It is probable that the additional mass placed an extra load on the braking system and affected the handling characteristics of the train.
Safety analysis
The loss of control leading to the runaway of the train was influenced by several factors. The primary contributing factors included wagons with variable net brake ratio (NBR), reduced brake cylinder pressure, a heavy train with some overloaded wagons, and dynamic braking affected by low adhesion conditions. Several individual actions by the driver that were inconsistent with the requirements in the work instruction contributed to the loss of control. These are discussed in more detail below.
Operation and braking did not control the train
WI-540 work instruction required the train’s tonne per operative brake to be calculated prior to descending the Illawarra Mountain. Qube’s internal report documented that this was not performed in this occurrence. The tonnes per operative brake (TOB) of the train was 98. A TOB that exceeded 80 generally required higher brake cylinder pressures to bring the train to a stop or control the train speed. Drivers needed to be mindful of this when operating trains down steep grades.
WI-540 also required the driver stop using a 100kPa reduction and check the brake release and recharge time at Summit Tank. The driver did not do this and stated in Qube’s internal investigation that they had made a mental note of the train rollaway time and got a feel for the train brake during operation of the train. According to the data logger, the driver stopped the train using a 69 kPa reduction and did not release the brakes. This led to the driver dragging the train to commence descent down the mountain.
Without conducting this test, the driver was not aware if the train brakes would release in under 45 seconds, which would be an indicator for the driver to use extra care to ensure brakes were recharged after an automatic brake application. The absence of this brake test meant the driver was unable to confirm the effectiveness of the braking system, before commencing descent.
WI-540 also stated ‘The brake pipe air flow must indicate a fully charged or almost fully charged brake pipe before second and subsequent brake applications are initiated’. The data logger record shows that a second serial braking application was initiated with 934 lpm flow of air into the brake pipe, indicating a significant flow of air was still filling the brake pipe so it was not yet fully charged.
It was also noted, this instruction presented a challenge to a driver having regard for the small margins for error. Adding 'almost' is not quantifiable and so leaves the driver to make difficult decisions, with little margin for error, on when to apply brakes.
For high risk operations in particular, steep gradient management, drivers must constantly weigh the demand to reduce the fast-accelerating speed against the demand to delay application so that the brake pipe can charge.
WI-540 further required the train to be stopped in the event of a greater than 100 kPa brake pipe reduction or when speed exceeded 30 km/h. During the second serial / cycle braking (final brake application sequence), the data logger record indicated no attempt to stop the train when the speed exceeded 30 km/h. After 42 km/h was reached, the driver applied a full-service brake application. Just prior to this, at 0422:55 a 103 kPa equalising reservoir reduction while travelling at 35 km/h was reached, but full service was still not applied.
At 38 km/h the driver increased the brake pipe reduction to about 120 kPa. The driver increased this to about 135 kPa at 41 km/h and finally to a ‘full service’ application (150 kPa brake pipe reduction) at 42 km/h. The driver applied the maximum braking effort which they believed to be achievable. However, once the train had reached 42 km/h, control of the train was lost.
The train remained in this braking configuration until it reached a speed of 85 km/h, at which time the driver applied the independent brake. The train did not immediately slow as a result of this brake application and continued to increase speed until the rear portion of the train, from the 29th wagon derailed as it rounded a 200 m left-hand radius curve, at a speed of 100 km/h. The 3rd to the 28th wagons then derailed seconds later as the train rounded a right-hand 200 m radius curve at a speed of 98 km/h. The locomotives and remaining two wagons then slowed significantly, stopping about one kilometre later.
Appreciation of brake recharge time
According to work instruction WI-540 (Moss Vale to Inner Harbour Train Management), Qube drivers were required to calculate the train’s tonne per operative brake (TOB) prior to descending the Illawarra Mountain to estimate braking effectiveness. The TOB calculated for 3966 was 98, which was at the upper limit of 80−100 for grain trains. This meant that the train was almost at braking capacity limits for the long descending grade from Summit Tank to Unanderra. However, Qube found that the driver did not conduct this calculation prior to the descent.
To further assist drivers in judging the braking characteristics of their train consist, WI-540 required drivers to perform a running brake test enroute (that is, without stopping the train) and a rollaway time check at Summit Tank at the top of the grade. In the 45 minutes prior to arrival at Summit Tank, the driver made 15 running automatic brake applications and releases. In interview, the driver advised that at that stage the train appeared to brake normally.
For the rollaway time check, drivers were required to stop their train at Summit Tank using a 100 kPa brake pipe reduction and verify the amount of time it took for the train to commence rolling once the automatic brake was released. In addition to gauging the release time for the automatic brake, the stop and brake release at Summit Tank provided the driver with an indication of the brake pipe recharge time after a large service brake reduction.
This was one of the most critical checks conducted by train drivers prior to descending the mountain as it provided an indication of how much time it would take for the train’s brakes to recharge following a significant brake application (100 kPa).
Although the driver stopped the train on arrival at Summit Tank, they did so with a 70 kPa brake pipe reduction, 30 kPa less than that required by the instruction. Further, once stopped, the driver applied traction power against the still applied automatic brake and commenced the descent, rather than releasing and assessing the brake release, and recharge time as per the instruction.
While the driver stated he had gained an appreciation of how the train was handling along the journey, not conducting this brake stop and release rate test, may have deprived the driver of some critical information, that was, the recharge time of the train’s brake pipe following a significant brake application.
Discussions with other train drivers who have descended the same route over many years indicated the stop and check of the recharge time was an important step before descending the mountain because the recharge time on trains can vary.
Reduced dynamic braking
The driver made the first of the cycle braking applications with full dynamic brake at about 17 km/h. Sand operated automatically to assist in increasing the adhesion of the locomotive wheels under the heavy dynamic braking.
Wheel slip and slide occurs when adhesion between the wheel and rail interface is low.[48] The automatic sanding function on a locomotive occurs to improve or increase adhesion during braking. It also improves traction when locomotives are powering. In this case, frequent auto sanding occurred which was indicative that reduced or low friction impacted the ability of the locomotive’s dynamic brakes to effectively provide optimal braking force.
Based on the CM class locomotive specifications, the mass of the locomotive and the maximum dynamic braking force, to achieve the maximum dynamic braking force the required coefficient of friction at the wheel rail interface was 0.18. The top of rail friction measurements taken approximately 6 months after the event, in dry conditions indicated the coefficient of friction was in the range of 0.2 to 0.36. It is likely that at the time of the train’s descent, when the rail line was wet and featured significant leaf matter contamination that the coefficient of friction on the top of rail was lower than the locomotive required.
The dynamic brake was less effective under the low adhesion conditions than it would have been under higher adhesion conditions. The wheel slip/slide protection system, worked to maintain traction by use of auto sanding to increase friction and derating the dynamic braking effort through the wheels (as evidenced in the data logger, as dynamic brake power lowered sanding was initiated)
As the train’s speed increased, the driver increased the brake pipe reduction to 83 kPa which was initially effective in slowing the train. With additional braking effort applied to the 40 wagons with operable brakes, the train driver was able to successfully reduce the train’s speed. As discussed in Rollingstock adhesion requirements the friction level required by loaded freight wagons for braking was not compromised under the prevailing track conditions.
Wagons with variable net brake ratio
Measurements of NBR on various CGSY wagons ranged from 10.7% to 19.5%, which was a significant variation in NBR for a wagon type. These wagons were required by Australian Standards to achieve an NBR of 13% to 16% with a brake cylinder pressure of 350 kPa. ARTC recommended an NBR of 13% in order to provide effective braking without skidding wheels.
When these wagons were placed into service in September 2015, the type test, which was the industry standard requirement was met, with 14.23% NBR.
As stated inHistory of CGSY wagons, a design error that affected the braking performance on the CGSY wagons was identified shortly after their introduction into service. Although a few interventions were made to rectify the braking system, uncertainty remained as to the effectiveness of the modifications.
Evidence supported a degree of variability in the braking system in the CGSY fleet with varying results from NBR tests conducted on different wagons over time:
• 13September 2015, wagon CGSY 4519A was tested (type test) and achieved an NBR of 14.23%
• 20April 2017 wagon CGSY 4542H was tested (post modifications) and achieved an NBR of 15%
• 18 May 2017 wagon CGSY 4502V was tested (post incident) and achieved an NBR of 13.99%
• 9February 2021 the two wagons that remained attached to the incident train, CGSY 4516T and CGSY 4518Y were tested and achieved NBRs of 12.45% and 10.7% respectively.
On 12 May 2021, three CGSY wagons that were not involved in this incident were tested and achieved the following NBR results:
• CGSY 4542H – 12%;
• CGSY 4503H – 19.5%;
• CGSY 4513P – 14.5%.
As CGSY 4542H did not meet the AS requirements for braking while in a loaded condition, Chicago Freight Car Leasing Australia (CFCLA) cleaned and greased the brake rigging and repeated the brake test on the 20 May 2021. This resulted in the wagon returning an NBR of 15.8%.
On 9 July 2021, after consultation of the AAR standard S401, which prevented the addition of grease on brake rigging for testing, CGSY 4542H brake rigging was cleaned and all evidence of grease removed. The NBR test was then repeated several times in the loaded and empty conditions. The NBR in the loaded condition was found to have an average of 13.85%.
CGSY 4542H
This wagon was of particular interest, as modifications and tests could be observed over its life cycle.
Based on the wagon type test conducted in September 2015, it’s NBR should have remained in the vicinity of 14.23%
The wagon’s slack adjuster pivot holes were re-drilled on its brake levers by CFCLA. It had a CIMC revised control lever design fitted by CFCLA. It was further modified by CFCLA in accordance with the recommendations from the SME.
In April 2017, the SME tested the wagon and made some minor adjustments before determining that the slack adjuster on the wagon was fully compliant with industry practice and brake force testing showed the wagon had an NBR of 15%.
While this wagon was not involved in the runaway of train 8960 that occurred on 22 April 2017, nor was it involved in this runaway of train 3966, it was brake tested on 12 May 2021 and achieved an NBR of 12%.
Following the cleaning and greasing of its brake rigging by CFCLA, a re-test on the 20 May 2021 achieved an NBR of 15.8%.
Then on the 9 July 2021, with removal of the grease and being tested multiple times, it achieved an average NBR of 13.85%.
The modifications and testing on this wagon indicated its braking performance varied over its life cycle. After modifications to improve the brake performance, it did fade over time to drop below the standard requirements. With interventions, such as cleaning and greasing, which were not permitted by Engineering standards (EPR 005), the NBR was raised above requirements and were proven to remain above requirements once the greasing of the brake rigging was rectified.
Reduced brake cylinder air pressure
At 0448 travelling at 15 km/h, and consistent with WI-540, the driver reapplied the automatic brake in ‘minimum service’ and then increased the brake pipe reduction to 70 kPa. However, as noted by the driver in interview, the brake pipe had not yet fully recharged.
The brake pipe at the locomotive was registering 489 kPa and the brake pipe charging flow indicator was still registering a rate of recharge of 934 litres per minute.
This second cycle braking automatic brake application was made before the brake pipe had fully recharged after the release of the first cycle braking brake application. This resulted in a reduced amount of available brake cylinder pressure to the driver for that and subsequent brake pipe reductions, and a lessened braking effort on the 40 trailing wagons with operational air brakes.
As a result, the train continued to increase speed with this 70 kPa brake pipe reduction.
For the driver, this was likely considered an appropriate brake pipe reduction to slow the train. However, as discussed in Running out of air, when the brake pipe has not been given a sufficient opportunity to recharge across the entire length of the train prior to the reapplication of the automatic brake, it will result in a lower auxiliary reservoir starting pressure, particularly on wagons at the rear of the train. As a result, there is a reduced pressure drop in the auxiliary reservoir when equalising with the brake pipe on the subsequent brake application. In response, the relay valve and supplementary reservoir provide less pressurised air to the brake cylinders, resulting in a reduced braking force than would be achieved if the auxiliary reservoir starting pressure was 500 kPa.
As the driver experienced nil effect from the brake application, they continued to reduce brake pipe pressure incrementally against a faster moving train which required greater braking force than was being applied, to stop. Each incremental brake application made by the driver at this time was against a gradually increasing speed of train, with increasing momentum requiring an even greater braking force to slow or stop the train.
Heavy train with some overloaded wagons
The weight of the train was near maximum allowable tonnage and probably under the 3680 t limit. Notwithstanding, it was likely a number of these wagons were over the allowable limit for a single wagon.
As detailed in Train weight, the wagons had been loaded inconsistently with some wagons being heavier than others. While the overall weight of the train consist was likely under the allowable weight limit for grain trains, it was apparent there were some wagons that were overloaded.
With a train near peak weight, there would be less scope for error with train handling and maintaining appropriate speed when descending the 1 in 30 grade on the Illawarra Mountain. Minor over speeds result in much greater downhill force for the train braking system to retard.
With individual wagons overloaded, the dynamics of these wagons is also affected impacting the ability of the wagon to operate as designed.
It is likely the driver expected he was operating a heavy train as the handwritten tonnage on the train consist was 3690 t. This should have been a trigger that the train was overloaded, even though the addition of the nominated individual wagon weights of 90 t each equated to 3622.7 t.
At interview the driver said they took a mental note of the weight of the train even though they had not calculated the tonnes per operative brake.
While the driver said they were aware of the train being heavy, it did not appear to change their method of operating the train on the descent.
Train driver decisions affected by fatigue
Fatigue research has shown that increasing fatigue is typically associated with an increasing likelihood of error.
There were factors which may have increased the driver’s level of fatigue and consequently influenced their decision-making and handling of the train. Factors considered included prior sleep, wakefulness, hours of service and task demand.
Prior sleep
It is reasonably well established in the literature that sleep loss reduces the duration that a person can sustain alertness.[49] In a working environment (such as train driving) that requires the driver to remain vigilant and alert for several hours during the day and night, it is essential that drivers have enough sleep in the 24 and 48 hours prior to work to maximise opportunity for sustained alertness.
The sleep-wake history established during interview with the driver indicated they had slept 12 hours in the previous 48 hours, with 3 of the sleep hours being in the previous 24 hours leading up to the time of incident. These 3 hours consisted of the last 2 hours in regular sleep time (0500 to 0700) and 1 hour in the afternoon (1500) prior to commencing work.
The driver’s block of sleep in the early hours of 14 December was 6 hours (0100 to 0700). The recommended sleep time for adults in the National Sleep Foundation Guidelines is 7-9 hours.[50]
The driver had also worked the night shift on the previous night (17:00 12th December to 06:00 13th December) and had only 5 hours of sleep in the day (07:00 to 12:00). Including the first 4 hours of the driver’s sleep block on the 14th December, the driver had 9 hours sleep for that 24‑hour period.
It is likely that the 12 hours of sleep in the previous 48 hours created a sleep debt[51]. The typical sleep hours of the driver were 8 hours in a 24-hour cycle.
It is likely a sleep debt contributed to the driver’s level of fatigue.
Wakefulness
The time of the occurrence suggests the driver’s level of alertness may have been influenced by the natural circadian rhythm or sleep-wake cycle.[52] Humans have a natural circadian rhythm which governs sleeping and waking. In the early hours of the morning (0300 to 0500), the body is driven to sleep and hence is not as alert as it would be later in the morning when the sun has risen.
Due to the time of day leading up to the occurrence, it was likely the sleep-wake cycle contributed to the driver’s level of fatigue.
Hours of service
Leading up to the day of the incident, the driver was rostered and had worked an 11-hour night shift, had a 6-hour break, then an 11-hour afternoon shift, then a 20-hour break and was 10 hours into an 11-hour night shift when the incident happened.
The roster for the driver on the 14th December was planned to commence at 14:30, however, due to late running services the driver was informed approximately 2 hours prior to commencement that the shift was laid back to commence at 20:00.
The original roster was assessed by Qube and found to have a FAID score of 82.99. Scores between 80 to 100 represent a high fatigue likelihood. As this score was based on the driver’s rostered hours, it is an indicator the rostered working hours likely to contributed to fatigue. Additionally, the layback of the start time on the 14th December would only have exacerbated the driver’s level of fatigue.
Task demand
The driver commenced driving duties from Cootamundra and remained at the controls for the entire time leading up to the incident. This meant they were on the task of driving for approximately seven hours before starting the descent.
The second person was unable to relive the driver as they were not qualified to drive the route.
According to the train crew, they did not stop on the journey from Cootamundra, except for a momentary stop at Moss Vale to pick up a crew pass. This stop did not allow enough time for the driver to have a reasonable break from driving duties.
The time the driver spent driving the train without a significant break to relieve him from the task demand of driving the train likely contributed to the driver’s level of fatigue.
Considering each of these factors, it was likely the driver’s ability to make decisions at the time of driving the train between Summit Tank and Farmborough Heights was affected by fatigue. This was supported in review of the driver’s actions and from in-cab recordings described below.
While the driver made increasingly heavier automatic brake applications in response to increases in speed, these decisions were delayed. According to WI-540, the balance point at which efforts should have been made to stop the train and fully recharge the braking system was when the brake pipe pressure reduction exceeded 100 kPa or, the speed of the train approached 30 km/h. The driver did not exceed a 100 kPa brake pipe pressure reduction until the train was travelling at 38 km/h (about 25% over speed). The driver also delayed the use of a ‘full service’ brake application with full dynamic braking (the maximum braking effort they believed to be achievable), until 42 km/h.
Operational decisions made by the driver on the morning of the incident, such as delaying the full service brake application until after the train was travelling above 30 km/h, may have been affected by fatigue.
The driver was an experienced shift worker and had descended that section of track on previous occasions and at similar times of the morning, At interview, the driver indicated they were not feeling fatigued at the time of the incident.
The physiological effects of fatigue result from hours of wakefulness and high cognitive task demands. Individuals are not always aware of the impacts or effects and the momentary lapses in concentration which may occur as a result.
The fact that the driver indicated at interview that he was not fatigued is not necessarily reliable given the high levels of stress and high cognitive workload he would have experienced at the time and in the early hours of the morning.
Driver did not apply the emergency brake
Dynamic braking in an emergency
In interview, the driver advised that during the second cycle braking application after leaving Summit Tank the train began behaving ‘unpredictably’. That is, it was not slowing as expected based on the previous braking sequences.
Once the driver identified that control of the train had been lost, the driver advised the network control officer. During an update of the emergency to the network control officer, the driver stated ‘…I don’t want to put it in emergency because I’ll drop my dyno [dynamic brake] out’. The driver explained that as the automatic brake was already in the ‘full service’ position, they believed no further braking effort would be available in the ‘emergency’ position. Further, the driver believed that if the automatic brake was placed in the emergency position, the locomotive’s dynamic brake would disengage, thereby reducing braking capacity and worsening the runaway situation.
The driver’s actions were supported by Qube’s work instruction WI-540 (Moss Vale to Inner Harbour Train Management), which in part, stated that in the event of an emergency:
…the automatic brake valve handle is to be placed into the full-service position do not place the handle into the emergency position.
This was due to Qube’s similar understanding that the loss of dynamic brake with no increase in wagon braking effort would result if the automatic brake was placed in the emergency position.
However, testing by OTSI found that on the CM class locomotive the dynamic brake remained engaged and functional when the automatic brake was placed in emergency.
Low auxiliary reservoir starting pressure
In relation to the automatic brake on the day of the accident, analysis of the data logger of 3966 found that:
On average, the brake pipe took 10 seconds to reduce to a commanded ‘minimum service’ brake pipe reduction (50 kPa).
The second cycle braking sequence commenced before the brake pipe had fully recharged from the first cycle braking sequence. Specifically, at the time of the brake application, the brake pipe charging flow indicator indicated a rate of recharge of 934 litres per minute and the brake pipe pressure at the locomotive was 489 kPa, rather than 500 kPa.
The brake pipe took 3 seconds, rather than 10 from a full brake pipe, to reduce to the commanded ‘minimum service’ brake pipe reduction (50 kPa) for the second cycle braking sequence.
During a brake pipe recharge the brake pipe air pressure throughout the length of a train varied, with the rear of the train lower in pressure than the front. Further, as it was recharged by the brake pipe, auxiliary reservoir pressure would lag the brake pipe pressure. As such, the brake pipe pressure reading at the front of the train was an unreliable indicator of auxiliary reservoir pressure, which was markedly lower (particularly at the rear of a train).
The low starting level and rapid drop in brake pipe pressure at the commencement of the second cycle braking sequence, indicated that the auxiliary reservoirs on 3966 were not fully recharged to 500 kPa. Given the rapid attainment of the minimum service brake pipe reduction at commencement of the second cycle braking sequence, it was highly likely that the true brake pipe pressure (and therefore auxiliary reservoirs), particularly towards the rear of the train, was closer to about 450 kPa.
On two-pipe wagons such as the CGSY and CGDY, brake cylinder pressure was provided by a supplementary reservoir which was supplied continuously with main reservoir air pressure. This meant that provided main reservoir air supply was available, the brake cylinders could always be supplied with air pressure. However, this was reliant on a reference (signal) air supply from the auxiliary reservoir acting on the relay valve, which enabled supplementary reservoir air to enter the brake cylinders. So, unless air pressure from the auxiliary reservoir was available to activate the relay valve, the supplementary reservoir could not apply a wagon’s brake.
In normal braking circumstances, a full service automatic brake application would result in a concurrent equalisation of the brake pipe, auxiliary reservoir and brake cylinders (via the relay valve) at about 350 kPa. So, reducing the brake pipe further would not increase braking effort. However, in instances of low auxiliary reservoir starting pressure, the equalisation of the brake pipe with auxiliary reservoir in full service would result in a lower brake cylinder pressure. Specifically, for an auxiliary reservoir starting pressure of 450 kPa, the maximum brake cylinder pressure achievable in full service was substantially lower at approximately 235 kPa. This is consistent with the driver’s observation that the brakes were not as effective as they had been during the previous brake application sequences since leaving Summit Tank.
However, in the unique circumstance of a low auxiliary reservoir starting pressure as was in this incident, it was possible to force an equalisation of the brake cylinder pressure at a higher rate than was by then achievable in full service. Where the auxiliary reservoir starting pressure was for example, 450 kPa, through further reduction of the brake pipe pressure to zero, an equalisation between the auxiliary reservoir and brake cylinder pressures would occur at about 314 kPa, thereby resulting in an increase in wagon braking effort. As it was not possible for the driver to graduate the brake pipe below 350 kPa, this would have required the driver to select either the ‘handle off’ or ‘emergency’ automatic brake positions, both of which would result in 0 kPa brake pipe pressure.
The effect of this increased brake cylinder pressure would have been apparent across the 40 wagons with operating air brakes on the day of the accident, particularly where low rail adhesion was causing a reduction of the dynamic braking effort on the two lead locomotives. Without an indication in the form of an in-cabin warning light and/or alarm the driver lacked awareness of the situation. Although it cannot be said with certainty that the train could have been stopped with this increased braking effort, it is more likely than not that a lower speed could have at the very least been maintained. Particularly if the emergency automatic brake application had been made early during the incident sequence and at a lower speed. That is, at the time the train was found to be exceeding the speed limit and not responding as expected to braking commands.
Operational procedure and training discouraged use of emergency brakes
Work instruction WI-540 (Moss Vale to Inner Harbour Train Management) provided specific instructions to be followed in an emergency, including the requirement to place the brake handle into full service, not emergency.
The driver had been trained to respond to a loss of control down the Moss Vale to Unanderra rail line in accordance with the work instruction as recently as two weeks prior to the incident. During that training, the driver completed a route assessment of the Moss Vale to Inner Harbour rail line with one of Qube’s trainer assessors and was assessed as competent, including against the requirements of WI-540.
As discussed earlier in the analysis, in a situation where maximum braking from a full service application was not achievable due to less than full auxiliary reservoir starting pressure, the greatest braking power available would have come from reducing the brake pipe to 0 kPa. On the CM class locomotive, this would have resulted in a combination of full train air braking plus electrical dynamic braking from the locomotives.
In summary, Qube’s operational procedure for train management between Moss Vale and Inner Harbour did not account for locomotive configurations that maintained dynamic brakes during emergency brake applications. This meant that a driver who lost control while descending the Illawarra Mountain was highly unlikely to use the emergency brakes. The use of the emergency brake in conjunction with the dynamic brake in this accident may have acted to slow or at least better control the speed of the train, thereby reducing the risk of derailment.
Train operators unaware of locomotive specifications
It was evident from the RSO’s procedures that there were assumptions about the functionality of the dynamic brake, based on historical locomotive brake configurations and standards. That was, that dynamic brake functionality would be lost if the automatic brake handle was placed into the emergency position. This assumption was incorrect.
Wabtec, the manufacturer of the locomotive including its braking system, had stated in their Operations and Maintenance Manual for the CM class locomotives that the dynamic brake could be configured to remain active or to cut out in the event of low brake pipe pressure, but did not specify how the CM class was configured.
The technical specification provided to CFCLA and Qube was silent on whether the dynamic brake remained active after emergency automatic brake applications.
Post incident testing found the dynamic did in fact remain active with an emergency automatic brake application and Wabtec later advised, through the course of the investigation, that the dynamic brake cut out function had not been implemented on the CM locomotive class.
The Wabtec-developed driver training presentation also did not specifically mention that the dynamic brake would remain active when an emergency brake application was made. Conversely, there was no mention of the dynamic brake cutting out when an emergency brake application was made, so the assumption could be made that the dynamic brake would remain active, which is how the locomotive was configured.
Review of the locomotive handover information from the manufacturer to the owner (CFCLA) and the operator (Qube), did not provide a clear understanding as to what the dynamic brake would do when the emergency brake was applied. Given the significant change in functionality from what was historically understood by the RSO to be common practice, it was reasonable to expect that the details of the dynamic brake function would have been clearly articulated as part of the handover.
However, in the handover of the CM class locomotives, it was apparent that incorrect assumptions were made by the owner and operator about the dynamic brake and how it operated. These incorrect assumptions flowed into their procedures and training materials and so onto their drivers.
Other locomotives with functional changes
Similar functional changes on locomotives were identified more broadly across industry that were unknown to other operators. Dynamic brake functionality was found to be inconsistent across locomotives with electronic braking systems. While some locomotives would disengage the dynamic brake when an emergency brake application was made, this was not the case across all locomotive types.
This inconsistency in dynamic brake functionality coupled with this being unknown by many operators was considered significant as it reduced the ability of drivers to appropriately manage their trains.
As a result, the OTSI in collaboration with the ATSB published a Safety Advisory Notice about this safety issue (see Appendix A – Safety Advisory Notice).
Factors affecting rail adhesion
Wet rail
The weather conditions reported by the Bureau of Meteorology indicated there was moderate wind and light rain on the escarpment in the hours leading up to and at the time of the incident. These conditions likely increased the presence of water and leaf litter on the head of the rail.
At interview the driver stated there was ‘very misty rain’ when they started the descent between Summit Tank and Unanderra. The train data logger supported this statement, indicating the windscreen wipers activated between Tunnel 2 and Tunnel 1 for a duration over 6 minutes.
The United Kingdom’s Rail Safety Standards Board’s (RSSB) 2016 study[53] to model and quantify the influence of water on wheel rail adhesion coefficients found that light drizzle conditions had the greatest effect on reducing the adhesion coefficient. In these scenario’s friction values could get as low as 0.05, with light quantities of water that would mix with wear debris or surface rust to form a lubricating paste.[54]
Track contaminant
The effect of leaf matter in reducing the wheel rail adhesion coefficient on rail lines is a known issue[55] and was found in a previous ATSB investigation.[56] Trees drop leaves onto the rail track which are then crushed when rollingstock passes over the leaf littered rail head. This plant matter contributes to reduced wheel rail adhesion coefficients.
The wheel rail adhesion coefficient has been found to be lower than 0.05 under severe rail contamination such as dampened leaf contamination.[57]
Front of train footage from the night of the accident showed trees lining the rail corridor from Summit Tank through to Farmborough Heights. Leaf matter was present on various parts of the rail line and was observed on the rail line at the derailment sites during the post incident inspections.
The weather conditions leading up to the 15 December 2020 had been wet and windy likely causing leaves to fall from the trees onto the rail track.
During the post incident track inspections, the contaminant observed on the head of the rail lines was more prominent in areas where the tree foliage was denser and dissipated as the trees cleared. The condition of the rail line closer to the top of the escarpment near Summit Tank was not observed during the site inspection, however it was considered likely the condition of the rail line at that time would have been similar to that observed at the derailment sites. The front of train footage (see Figure 3) indicated the density of tree foliage to be similar.
The sample of the contaminant tested was found to be primarily leaf matter. Leaf matter on rail head is a known contaminant that reduces adhesion of the wheel rail interface.
Rollingstock adhesion requirements
To help understand whether the condition of the rail line effected braking of the train, braking adhesion requirements were provided by ARTC.
For a loaded wagon, under the assumptions the NBR was 13% and the brake block coefficient of friction was 0.3, the required friction level = 0.039, or 3.9% required braking adhesion.
For the CM class locomotive, given the max dynamic braking power was 230 kN, the required friction level = 0.18, or 18% required braking adhesion. Other factors considered which would have influenced adhesion between the rollingstock and the top of rail includes:
1) on long freight trains the adhesion improves back along the train as wheels successively clean and dry the rail - so the average adhesion for train 3966 was likely higher than the referenced single-wheel adhesion.
2) tread-braked wheels, such as on train 3966, are cleaned and dried by the brake block, which aids maintenance of higher adhesion between wheel and rail. It is noted the referenced report RO-2013-005 was a passenger train with disk-braked wheels.
Considering these values and factors, it is likely the dynamic braking on the CM class locomotives was affected by the conditions on the rail line. This was evidenced by the frequent automatic sanding and dynamic brake power derating seen on the data logger of CM3316.
However, the wagons braking capacity should not have been affected by the conditions as the required braking adhesion levels of loaded freight wagons is significantly lower (at 3.9%) than the dry adhesion levels found on the rail line when measured on the 3 June 2021 (lowest at 20%). Additionally, the braked train wheels would have been successively cleaning and drying the rail line as they ran over making it even less likely the wagon wheels were affected by water and contaminant.
In summary, the conditions on the rail line from Summit Tank to Farmborough Heights on the morning of the incident presented a mix of factors including wet rail and track contaminant that likely increased the risk of reduced adhesion at the wheel-rail interface. This reduced adhesion likely affected the locomotive dynamic braking power but not so much as to affect the braking of the freight wagons.
Management of rail friction
Friction at the wheel-rail interface is the bond linking the tangential and normal forces that varies depending on vehicle speed, vehicle weight, contact patch and other material characteristics.[58]
Managing the coefficient of friction at the interface of the top of rail and the wheel is important for predictable operation of the train’s acceleration and braking systems.
While ARTC specified the design friction coefficients in their Code of Practice, these requirements were for design only. In the operational system, the friction coefficient can vary significantly as a result of various factors, including the nature of the steel in the rail and wheels, temperature and presence of materials such as, water, grease, oil, sand and vegetative material.
It is reasonable to consider the friction coefficient on the top of rail could change between two trains running along the same rail line if water and leaf matter were introduced, such as from a localised storm occurring in between the two trains passing a given location. The introduction of water (rain) and leaf matter on the top of rail could reduce the coefficient of friction at the wheel rail interface.
For this reason, a regular testing and monitoring program, even if conducted monthly is unlikely to provide assurance of the top of rail friction remaining at the value measured on the day.
For the descent of the Moss Vale to Unanderra rail line, the risk of a train running away has been realised on a few occasions. For this incident, it was likely a number of factors contributed to the eventual loss of control and runaway of the train. The top of rail friction was only one element that affected the performance of the train.
In this regard, when known factors present which increase the risk of reducing top of rail friction levels, such as, localised rain and wind events, it would be reasonable to afford some level of warning to train drivers that the line may present added risk and should be taken with extra care. There are existing processes in place, such as reporting of conditions affecting the network (CAN), that once reported by a train driver, warnings to other train drivers are made. However, this control mechanism relies on the first train driver being exposed to the risk without any warning.
Rail flange lubricators and track lubrication
ARTC maintenance records indicated the rail lubrication devices on the rail line between Summit Tank and Unanderra had been serviced in accordance with standards and the general inspection of rail lubrication conducted on 14 June 2020 did not identify any issues with the spread of rail grease from the lubricators.
Approximately six months after the incident, observations made by Qube of a rail track lubricator at Dombarton (97.030 km, in between No.1 Tunnel and the first point of derailment), showed a grease plume extending from the rail track lubricator, indicative of the lubricant being picked up and flung from the wheels and deposited in the surrounding area, including on the top of the rail head.
It was noted that the location of this rail track lubricator did not coincide with any of the rail lubrication devices listed in ARTC’s maintenance history records and therefore could not be reconciled as to when its last general inspection was completed. It was not the only unlisted rail flange lubricator in the section as another at 94.30 km could not be reconciled with the maintenance history records. This rail flange lubricator was in very close proximity to the listed rail flange lubricator at 94.26 km. Visual inspection of these lubricators indicated both were operational.
These rail flange lubricators providing lubrication to the down rail, at 94.30 kms and 94.26 kms, were less than the 500 m minimum separation requirement specified in ARTC’s engineering practices manual RC2411. Another two listed rail flange lubricators located at 94.95 kms and 94.53 kms, servicing the up rail were also less the 500 m minimum separation requirement.
Although the number and positioning of these rail flange lubricators was possibly intended for the strategic delivery of flange lubrication, a review of these to ensure consistency with the engineering practice and minimise the risk of excess track lubrication on a steep gradient was warranted.
Monitoring air flow
Maximum brake cylinder pressure on wagons is reliant on auxiliary reservoirs being fully charged (500 kPa) before a brake application is made. The brake pipe charging flow indicator instrumentation is available to the driver to help determine when the brake pipe, and therefore the auxiliary reservoirs are fully recharged after a brake release.
Although the brake pipe gauge in the driver’s cabin may indicate a 500 kPa at the locomotive, where the brake pipe charging flow rate is above zero litres per minute, it is indicative of an incomplete brake pipe recharge throughout the train, particularly toward the back of the train. That is, main reservoir air is flowing into the brake pipe and auxiliary reservoirs. Whilst this is occurring, they are not fully charged and hence, it is not possible to reach maximum brake cylinder pressure if a brake application was made.
Knowing if and when main reservoir air was flowing into the brake system is important to the driver because it enables them to understand the condition (i.e. whether fully charged) of the brake pipe and auxiliary reservoir pressures across the entire train.
At interview, the driver recalled observing the brake pipe charging flow indicator and the brake pipe pressure gauge and judged the brake pipe to be about 90-95% recharged. The data logger recorded that the brake pipe pressure gauge was reading 489 kPa (that is, close to full pressure of 500 kPa) however, the brake pipe charging flow indicator was still registering a significant air flow of 934 litres per minute. This indicated that the train’s brake pipe and auxiliary reservoirs were still charging and not yet fully recharged.
The driver’s judgement of the brake pipe being 90-95% recharged was likely in relation to the brake pipe pressure gauge reading 489 kPa. Further, there was limited guidance for drivers of the significance of flow indicator gauge readings, in particular the level of recharge these were quantifying. For example, in this instance, 934 litres per minute, and what that indicated in relation to the physical state of recharge of the auxiliary reservoirs and the brake pipe across the train.
The brake pipe pressure and brake pipe charging flow indicator consisted of small numerical digital displays situated in the top left-hand corner of the driver’s HMI screen. In the case of the latter, the display did not provide an obvious or distinct representation of the critical values that could be easily understood or quantified by the driver. For example, at maximum recharge (more than 3000 litres per minute), the value remained the same colour (green) as it did when recharge was almost complete (low litres per minute value). In addition, no audible indication was associated with the recharge. That is, there were no indications, apart from a small numerical display, to alert the driver that main reservoir air flow to recharge the brake pipe was occurring or continuing.
Amongst the other tasks conducted while driving a train, a driver may only make a momentary glance at the gauges. As a result, it is possible a driver could miss the importance of the value the brake pipe charging flow indicator was providing where no further alert stimulus was provided.
In contrast, it was noted during the investigation that on some locomotives fitted with an identical braking system to the CM class locomotive, an audible alarm was provided in conjunction with a red flashing tile when high air flow from the main reservoir to the brake pipe was detected. This assisted in proactively drawing a driver’s attention to the state and condition of the brake pipe charging flow indicator. This assisted in the driver’s ability to detect uncommanded brake pipe pressure loss (for example, derailment) and monitor when the train’s brake pipe and auxiliary reservoirs were fully charged in preparation for an automatic brake application.
Communication of design changes
Prior to the design error in the CGSY wagons being identified by the CIMC, CFCLA considered the braking force on the wagons as not performing as required. CFCLA concluded the brake rigging ratio needed to be increased to improve the braking performance.
To achieve this, slack adjuster pivot holes were re-drilled in the brake lever. CIMC were advised that CFCLA were undertaking these modifications to the brake lever ratio, but the detail of the dimensional changes was not provided to CIMC.
Without the specifics of the design changes to the brake lever ratio, CIMC developed a design fault repair, that being a revised control lever, which when installed made no change to the operation of the brakes with the slack adjuster still unable to reduce the slack in the brake rigging.
Wayne Clift Consulting was engaged by CIMC to determine the root cause of the braking system performance.
The consultant found that changes had been made to the wagons braking system by CFCLA that had not been passed back to CIMC which resulted in the modified design failing to correct the issue.
CFCLA accepted the report from Wayne Clift Consulting and later engaged the consultant to complete the compliance and inspection report of the first modified wagons, in accordance with the Consultants recommendations.
The original change made to the brake levers by CFCLA were instigated without full consultation with the OEM, so the OEM was unaware of the details when they developed a repair. It is unclear whether CFCLA followed a systematic change management process when making the design changes to the brake levers.
Generally, any changes to equipment should be assessed and undertaken following a sound change management process. The rail industry in Australia has standards for management of change, such as AS7472:2018 Railway operations – Management of change.[59]
The standard describes the requirements to be applied by all rail organisations to ensure that safety risks associated with changes to railway operations, assets, or systems are identified and eliminated or reduced so far as is reasonably practicable.
Amongst other requirements in the standard, an integral step in the change process is to consult and communicate with relevant stakeholders. Prior to CFCLA making changes to the design of the braking system, consultation with the OEM (CIMC) would likely have assured a better outcome as input from the designer would have identified the design fault sooner and any ensuing changes would have considered this. However, CIMC was eventually informed of the changes made by CFLCA but the details of the changes, that is, the dimensions of the drilled holes from the original, were not provided, leaving CIMC to design a fault repair without full knowledge of the brake lever configuration.
Only through review of the fault by a contracted rollingstock specialist was the issue identified and further modifications made to address the issue.
CFCLA made changes to the CGSY wagons to improve the brake performance. While CIMC was informed of the changes, the details of the change were not provided which resulted in a design fault repair developed by the OEM being ineffective.
Findings
ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition, ‘other findings’ may be included to provide important information about topics other than safety factors.
Safety issues are highlighted in bold to emphasise their importance. A safety issue is a safety factor that (a) can reasonably be regarded as having the potential to adversely affect the safety of future operations, and (b) is a characteristic of an organisation or a system, rather than a characteristic of a specific individual, or characteristic of an operating environment at a specific point in time.
These findings should not be read as apportioning blame or liability to any particular organisation or individual.
From the evidence available, the following findings are made with respect to the runaway and derailment of loaded grain train 3966 near Dombarton, NSW, on 15 December 2020.
Contributing Factors
The weight of the train was near, but likely not over, the maximum allowable tonnage limit specified by the Australian Rail Track Corporation (ARTC)’s Train Operating Conditions (TOC) Waiver 16002. It was likely however that several individual wagons across the train consist were over the allowable limit for a single wagon.
The second automatic brake application was made before the brake pipe had fully recharged. This resulted in a reduced amount of available brake cylinder pressure to the driver for that and subsequent brake pipe reductions, and a lessened braking effort on the 40 trailing wagons with operational air brakes.
The train driver did not effectively manage the train’s speed or comply with operator prescribed braking, which resulted in the last cycle braking sequence not adequately controlling the train’s speed, leading to the runaway.
Some of the driver’s decisions on the morning of the accident were likely affected by fatigue.
Once control was lost, the driver did not select the emergency brake position based on the mistaken understanding that the dynamic brake would cut out when the emergency brake was applied. This resulted in less available braking effort, reducing the ability to control the speed of the train.
Qube’s operational procedure for train management between Moss Vale and Inner Harbour did not account for locomotive configurations that maintained locomotive dynamic braking during emergency applications. This increased the risk of the train driver not using the emergency brake during a runaway event. (Safety issue)
The conditions on the rail line from Summit Tank to Farmborough Heights on the morning of the incident presented a mix of factors including wet rail and track contaminant that likely contributed to a reduced dynamic braking effort by the locomotives.
Measurements of net brake ratio (NBR) at different times and on different wagons returned varying results ranging from 10.7% to 19.5%. While various modifications were made in order to improve braking performance on the wagons, the NBR on some wagons continued to change over time.
Other factors that increased risk
The wagon type test met the NBR requirement when introduced into service and met NBR requirements when tested post modifications, however there was no requirement for regular testing of net brake ratio, which may have identified the changes in NBR.
The assumptions regarding locomotive configurations that cut-out locomotive dynamic braking during emergency applications was found embedded in other rollingstock operator’s procedures with similarly configured locomotives in NSW. (Safety issue)
Several rail flange lubricators, which provided lubrication to the down and up rail were less than the 500 m minimum separation requirement specified in ARTC’s engineering practices manual RC2411. A review of these to ensure consistency with the engineering practice and to minimise the risk of excess track lubrication on a steep gradient was warranted.
The brake pipe charging flow indicator on CM class locomotives only provided a numerical display without any corresponding audio or visual warning system to alert the driver. This limited the ability for the driver to detect derailment or train separation events, and in this incident, effectively monitor recharge of main reservoir air to the brake pipe.
CFCLA made changes to the CGSY wagons to improve the brake performance. While CIMC (the Original Equipment Manufacturer) was informed of the changes, the details of the change were not provided which resulted in a design fault repair developed by the OEM that was ineffective.
Safety issues and actions
Central to the ATSB’s investigation of transport safety matters is the early identification of safety issues. The ATSB expects relevant organisations will address all safety issues an investigation identifies.
Depending on the level of risk of a safety issue, the extent of corrective action taken by the relevant organisation(s), or the desirability of directing a broad safety message to the rail industry, the ATSB may issue a formal safety recommendation or safety advisory notice as part of the final report.
Descriptions of each safety issue, and any associated safety recommendations, are detailed below. Click the link to read the full safety issue description, including the issue status and any safety action/s taken. Safety issues and actions are updated on this website when safety issue owners provide further information concerning the implementation of safety action.
Train Operators unaware of locomotive specifications
Safety issue description: The assumptions regarding locomotive configurations that cut-out locomotive dynamic braking during emergency applications was found embedded in other rollingstock operator’s procedures with similarly configured locomotives in NSW.
Safety advisory notice to Rail Transport Operators: The ATSB advises that all Rollingstock Operators (RSO) should review the specifications and test the locomotives under their control to understand how the braking systems are configured. RSO’s must communicate this knowledge through the organisation’s procedures and training material to ensure train crew knowledge and competence in operating locomotive braking systems.
Operational procedure and training discouraged use of emergency brakes
Safety issue description: Qube’s operational procedure for train management between Moss Vale and Inner Harbour did not account for locomotive configurations that maintained locomotive dynamic braking during emergency applications. This increased the risk of the train driver avoiding the use of the emergency brake during a runaway event.
Sources and submissions
Sources of information
The sources of information during the investigation included the:
Train crew of 3966
Qube Logistics (Rail) Pty Ltd
Australian Rail Track Corporation
Office of the National Rail Safety Regulator
Wabtec Australia
Railfirst, formerly Chicago Freight Car Leasing Australia (CFCLA)
References
A survey of Wheel/Rail Friction, Federal Railroad Administration, Sept 2017
Dorrian et al How much is left in your “sleep tank”? Proof of concept for a simple model for sleep history feedback, Accident Analysis and Prevention, 2019, 126, pp 177-183
El-Tayeb N M and Liew K W Effect of water spray on friction and wear behaviour of non-commercial and commercial brake pad materials, Journal of Materials and Processing Technology, 2008, 208(1); 135-144
Gunay et al - An investigation on braking systems used in railway vehicles - Engineering Science and Technology 23 2020 421-431
OTSI Investigation Report 04505 (2011) Uncontrolled movement of El Zorro grain service 3996 Unanderra 7 February 2011
Managing low adhesion, 6th Ed, January 2018 – Adhesion Working Group Modelling and quantifying the influence of water on wheel/rail adhesion levels – Phase 2 report, conducted for RSSB by University of Sheffield, L Buckley-Johnstone, University of Sheffield, R Lewis, University of Sheffield, K Six, Virtual Vehicle, G Trummer, Virtual Vehicle, 2016
Under section 26 of the Transport Safety Investigation Act 2003, the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. That section allows a person receiving a draft report to make submissions to the ATSB about the draft report.
A draft of this report was provided to the following directly involved parties:
Qube
ARTC
Wabtec
Railfirst
Office of the National Rail Safety Regulator
Monash Institute of Railway Technology
Train driver
Assistant train driver
Submissions were received from:
Qube
ARTC
Wabtec
Railfirst
Office of the National Rail Safety Regulator
Monash Institute of Railway Technology
The submissions were reviewed and, where considered appropriate, the text of the report was amended accordingly.
Appendices
Appendix A – Safety Advisory Notice
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.
Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.
The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
[1] EST: Coordinated Universal Time (UTC) + 10 hours.
[2] A runaway train includes unintended rolling stock movement and instances of loss of control of a train.
[3] Train crew can have their start time changed to suit operational needs, to be ‘laid back’ is to start at a later time from rostered start time.
[4] The automatic brake is used as the main mechanism for slowing and stopping the train (both locomotive/s and wagons) full details are provided in Train Braking System.
[5] The independent brake is the air actuated friction braking mechanism on the locomotives only. SeeIndependent brake.
[6] The dynamic brake is a braking mechanism of the locomotives only. It is supplementary and designed to reduce the wear and heat generated by the friction braking mechanisms. Refer to Dynamic brake.
[7] Balanced braking is a method of train speed control where an automatic brake application is maintained, while the dynamic brake is manipulated to control speed.
[8] A fully recharged brake pipe has approximately 500 kPa.
[9] A minimum service brake application is a reduction of the brake pipe by 50 kPa to 450 kPa.
[10] Sanding is the release of sand from the locomotive onto the head of the rail in front of the drive wheels. It improves traction at the interface of wheel and rail head. Auto sanding is the automatic release of sand when the system detects the wheel creep (micro slip or slide) at the interface with the rail.
[11] Where the wheel slip/slide was manageable by the locomotive systems, automatic sanding would occur without an indication to the driver.
[12] Serial/cycling braking is a method of train speed control where the dynamic brake is fully applied and the application and release of the automatic brake controls the speed.
[13] Distances measured from Central Station, Sydney (0.000 km).
[14] A ‘full service’ automatic brake application reduces the brake pipe pressure to 350kPa.
[15] An emergency automatic brake application reduces the brake pipe pressure to 0 kPa. Refer to Automatic brake for further information.
[16] 1 in 30 grade means that for every 30 metres of distance travelled, the track descends 1 metre. This grade can also be referred to as a percentage which for 1 in 30 the grade is 3.33%
[17] The train operating conditions are detailed in the infrastructure manager’s TOC Manuals and Waivers.
[18] No-Doz is a caffeine tablet readily available at pharmacies and supermarkets that is marketed to help relieve mental fatigue and drowsiness.
[19] The Fatigue Audit InterDyne (FAID) is a computerised bio-mathematical model, developed by Interdynamics Pty Ltd. The score is the University of South Australia's Centre for Sleep Research Fatigue Management Index (FMI). The FMI is a measure of fatigue risk arising from reduced sleep opportunity expected to be induced by working a particular pattern of work. This score is primarily used in industry to assist rostering. It does not calculate actual impairment.
[20] This competency was developed by Qube for their trainers of train drivers.
[21] This competency was developed by Qube for their driver’s assistants.
[22] ICE (In-cab Communications Equipment) train radio is the digital train radio system used on the ARTC network.
[23] A Condition Affecting the Network is any condition that can or do affect the safety of rail operations in the rail network, they must be reported promptly to the Network Control Officer responsible for the affected portions of track.
[24] Superelevation is the vertical distance between the inside and outside rails, typically measured in millimetres. Excessive difference between actual and design superelevation is one of many factors that can increase likelihood of derailment.
[25] Twist is the difference in level between the two rails, measured over a defined length. Short Twist – 2 metres, Long Twist – 14 metres. Twist can affect wheel-load and vehicle dynamics and is one of many factors that can increase likelihood of derailment.
[26]Tribometer or tribotester is a generic name for a device which is used to simulate and measure friction and wear at the interface between surfaces in a relative motion under controlled conditions.
[27] The locomotive information pack is submitted by the rollingstock owner to the rail network owner prior to its approval on the network and provides all technical and operational specifications of the locomotive.
[28] The load out tonnes is the total weight of the grain loaded into the grain hopper wagons.
[29] BFB is the Brabin, Firman and Block families partnership – BFB Pty Ltd delivering freight, grain, fertiliser and fuel services. Based in Temora, the grain loading terminal is located at Temora West. In 2023, BFB Pty Ltd merged to become AltoraAg
[30] A TOC waiver is a published variation to the train operating conditions manual.
[31] The TfNSW rail network started at 91.080 km to Unanderra, where it joined the South Coast rail line which was also part of the TfNSW rail network.
[32] The coefficient of friction is a measure of the frictional force (or resistance) between one object moving over another.
[33] The penalty brake resulted in an automatic reduction of the brake pipe to 0 kPa. This occurred after vigilance and detonator signal detection timeouts, and locomotive overspeed.
[34] Where a wagon is fitted with a main reservoir pipe to supply the supplementary reservoir, in addition to a brake pipe, the braking system is termed ‘two-pipe’.
[35] Based on information on general airbrake principles supplied by Wabtec Australia.
[36] The CGDY and CGSY wagons were fitted with a supplementary reservoir which was recharged by the main reservoir, not the brake pipe. Removing reliance on the brake pipe recharging all aspects of the train’s braking system resulted in reduced brake pipe recharge and brake release times.
[37] Train separation: where the rear of the train detached from the front of the train, either through coupler failure or uncommanded uncoupling.
[38] Based on information on general airbrake principles supplied by Wabtec Australia.
[39] Note: these pressures are an approximation. The exact pressures would be influenced by the number and diameter of the brake cylinders, diameter of the brake cylinder piston and, length and diameter of the pipework from the supplementary reservoir to the brake cylinder/s.
[40] Based on information on general airbrake principles supplied by Wabtec Australia.
[41] The DBI function was known on earlier locomotives as a ‘dynamic brake interlock’.
[42] OTSI found that the CM class locomotive manual stated that the independent brake was released by the DBI. Testing by OTSI confirmed this does not occur.
[43] Wabtec advised this configuration has not been implemented on the CM class locomotive.
[44] developed by MotivePower Inc. - a subsidiary of Wabtec USA, the locomotive builder
[45] Light engine: one or more locomotives coupled without wagons attached.
[46] Wabco 1988, “26-L” locomotive air brake equipment and devices. American Standard Incorporated, Pennsylvania.
[47] Also referred to within the manual as the ‘power cutout switch’.
[48] Managing low adhesion 2018; Braking systems 2017
[49] Dawson and McCulloch, 2005, Managing Fatigue: It’s about sleep.
[51] Van Dongen et al, 2003, Sleep debt: Theoretical and empirical issues. Sleep debt may be defined as the cumulative hours of sleep loss with respect to a subject-specific daily need for sleep.
[52] Circadian Rhythms first scientific observation in 1729 by Jean-Jaques d’Ortous de Mairan, they are a 24 hour internal cycle that regulates body functions such as sleep and wake times.
[53] Modelling and quantifying the influence of water on wheel/rail adhesion levels – Phase 2 report, conducted for RSSB by University of Sheffield, L Buckley-Johnstone, University of Sheffield, R Lewis, University of Sheffield, K Six, Virtual Vehicle, G Trummer, Virtual Vehicle, 2016
[59] AS 7472 Railway operations – Management of change was prepared by Rail Industry Safety and Standards Board (RISSB) Development Group consisting of representatives from the Australian Rail Industry.
On 11 December 2020, a crew member (from Shandong, China) on Luzon Strait fell into the cargo hold and sustained fatal injuries. The Hong Kong Marine Department, Marine Accident Investigation Section (MAIS), is investigating the accident.
At the request of MAIS, the ATSB assisted with the collection of information relevant to the investigation. To protect any information supplied by MAIS to the ATSB, and the ATSB's investigative work to assist MAIS, the ATSB initiated an investigation under the Transport Safety Investigation Act 2003. The ATSB has now concluded its involvement in the investigation.
The Hong Kong Marine Department, Marine Accident Investigation Section is responsible for and will administer the release of the final investigation report into this accident. Any enquires relating to the investigation should be directed to the Hong Kong Marine Department at mdenquiry@mardep.gov.hk.
On 7 December 2020, at about 1155 local time, SCT Logistics train 1MP9 was travelling on the Australian Rail Track Corporation (ARTC) network through Adelaide, South Australia en route to the SCT Logistics Penfield freight facility.
As the train traversed a slight left curve in the southern approach to the Torrens Road level crossing the driver saw that road traffic was still passing over the crossing about 90 m ahead, and that the level crossing warning equipment had not operated for the approach of the train. The driver initiated an emergency brake application before continuously sounding the locomotive horn, warning road traffic of the train’s approach. Shortly after, the locomotive entered the level crossing and continued to travel a further 260 m before stopping. The trailing freight wagons from the train stopped on the level crossing and blocked the passage of road traffic. There was no collision with road traffic or injury to any person.
What the ATSB found
The ATSB found that, earlier that day members of a subcontracted signal team working on the adjacent Adelaide metropolitan passenger rail network (AMPRN) had undertaken temporary wiring alterations to the control circuits of 2 level crossings to facilitate track tamping work. A late change to the scope of track work required the signal team to undertake additional work to alter the control circuits at another level crossing located at Torrens Road. This scope change placed an increased work demand with short notice on the signal team to implement the pre-approved Torrens Road inspection and test plan procedure. The procedure required the installation of 3 temporary jumper wires, 2 of which were superfluous. The inclusion of avoidable wiring placed an unnecessary task demand on the signal team during the wiring installation stage.
Following the installation stage, the signal team tested the temporary wiring for compliance to the inspection and test plan. The methodology adopted by the signal team did not ensure independence between the installation and testing tasks. This resulted in a wiring error not being corrected and remaining in the Torrens Road level crossing control circuit as a latent condition that could affect the correct operation of the level crossing warning equipment.
The uncorrected wiring error, combined with another signalling system condition that later presented on the AMPRN, resulted in the control input from the ARTC network signalling system not activating the Torrens Road level crossing warning equipment for train 1MP9 as it approached the crossing.
The ATSB established that the inspection and test plan that was used by the signal team did not include effective test procedures to verify and validate the safety integrity of the level crossing control circuits following the installation of the temporary wiring alterations. The South Australian Public Transport Authority reviewed and approved a package of level crossing inspection and test plans developed by their principal contractor, Acciona, which did not specify any requirement to test the altered wiring following installation. The effectiveness of any testing undertaken to control risk and assure the safety integrity of the rail infrastructure for trains operating on the ARTC network relied solely on the methodology adopted by the subcontracted signal team on the day.
What has been done as a result
Following the incident, Acciona undertook a risk assessment of the level crossing alteration works in consultation with the project stakeholders. New controls associated with works were incorporated into an updated construction work method statement that was subsequently submitted to the South Australian Public Transport Authority for approval. The controls addressed requirements for additional function testing activity and the potential for road closures where wiring alterations were required to facilitate track tamping work.
In December 2020, the Office of the National Rail Safety Regulator (ONRSR) published a notice to rail transport operators highlighting several incidents of the non-operation of level crossings on live lines due to incorrect isolation, and recommended operators ensure the completion of the key tasks specified in the notice.
The Rail Commissioner amended work instructions related to the temporary decommissioning and jumpering of signalling systems. Additionally, the Rail Commissioner worked with the contractor managing the AMPRN to develop improved procedures and forms for use in the temporary alteration of signalling systems.
The ARTC, although not directly involved in the installation of the jumpers at the Torrens Road level crossing, also reviewed and updated several ARTC engineering standards related to the modification of control circuitry of level crossings that were shared between operators.
Safety message
The correct operation of the active warning equipment installed at level crossings forms the primary engineered risk control for the management of safety at the road-rail interface. A failure of the level crossing warning equipment to operate on the approach of a train introduces significant risk of a collision that may result in fatalities or serious injury to road users, train passengers and crew.
Any installation or alteration of a signalling system introduces a potential risk to the safety of rail operations that may arise from a design or installation error. To manage the risk, signal designs typically underwent an independent review and approval process and the installed or altered signalling systems were then subjected to various levels of testing, dependent on the complexity of the system change. At a basic level these tests typically involved the certification of the system through the independent verification of the installed wiring followed by the validation of the systems control functions to ensure the safety of rail operations was maintained.
It is essential that rail transport operators and rail safety workers plan, document, and implement effective testing systems and auditable practices to ensure that new or altered safety‑critical railway infrastructure is rigorously verified and validated to assure the safety integrity of the infrastructure being placed into service.
The occurrence
Overview of the track work
On 2 December 2020, Acciona[1] commenced a program of track work[2] on the South Australian Public Transport Authority (SAPTA) Adelaide metropolitan rail network (AMPRN) as part of the Gawler rail electrification project (GREP). The Acciona worksite was located on the Gawler up line[3] between the 2.7 km mark[4] at North Adelaide Station and the 8.5 km mark at Grand Junction Road, located north of Islington Station (Figure 1 ,detailing the stations within the work area). The Australian Rail Track Corporation (ARTC) interstate rail line ran parallel to the AMPRN through the worksite and was protected by the AMPRN level crossing warning equipment at each road crossing location.
Source: NationalMap, Australian Government, annotated by the ATSB
To facilitate the track tamping work, rail safety workers[5] from Rail Industry Constructions undertook electrical work on the AMPRN signalling system under a subcontract to Acciona. The electrical work involved the removal of track circuit[6] connections from the rails and if required, the installation of temporary jumper wiring to the control circuit of a level crossing that would be affected by the removal.
The Gawler up and down rail lines were closed to scheduled passenger services and the jumper wiring was to prevent the unintended operation of the level crossing flashing lights, gongs and boom barriers due to the track work on the AMPRN. On completion of the track work each day, the signalling system was reinstated to the original state.
The ARTC interstate rail line was open to train services and normal operation of the level crossing warning equipment was to be maintained for a train travelling on that line.
Prior to the arrival of train 1MP9
4 December 2020
On the morning of 4 December 2020, the Rail Industry Constructions rail safety workers comprised a tester in charge (TIC), a signal electrician and 2 trade assistants (signal team). The team attended the daily Acciona pre-work briefing where the TIC spoke with the Acciona possession protection officer (PPO) and other Acciona project representatives to determine the scope of the team’s work for that day. The agreed work involved the removal of connections from the rails and alterations to the Pym Street and Belford Avenue level crossing control circuits.
Following the briefing, the TIC and signal electrician travelled to the Islington relay room, located around 500 m north of the Islington station, and used the pre-approved inspection and test plans (ITPs) to install and test the alterations to the 2 level crossings. On completion of this work, they moved from the relay room to the rail track where, in conjunction with the remainder of the signal team, they removed the required connections from the rails in preparation for the track work to commence.
At the end of the track work for that day, the signal team reinstated the connections and tested the track circuits. The TIC and signal electrician then went to the Islington relay room to remove the jumpers from the 2 level crossing control circuits before testing the correct operation of the associated warning equipment, as per the respective ITP.
7 December 2020
On 7 December 2020, at about 0630 local time, the signal team attended the routine Acciona pre-work briefing. The scope of the work for the day was to again remove connections from the rails and alter the Pym Street and Belford Avenue level crossing control circuits. The TIC recalled that during the pre-work brief, the Acciona work group supervisor asked them to remove as many of the connections from the rails that they could toward the Dudley Park station.
The TIC and signal electrician travelled to the Islington relay room to alter the control circuits for the 2 level crossings. At about 0805, the TIC and signal electrician completed work and moved to the track to remove the connections from the rails between the Islington and Dudley Park stations, as they had done on the previous days.
At about 1020, the signal team completed that work. Shortly after, the work group supervisor asked the TIC if they would also undertake alterations to the Torrens Road level crossing control circuit and remove additional connections from the rails, so that work could continue past Dudley Park station towards Torrens Road.
Although this work was not planned during the pre-work briefing, the TIC stated they felt an obligation to comply with the request and undertake the additional tasks, so the work group could recover from previous delays in their schedule. The TIC felt the signal team was under constant pressure to complete tasks and there was not an understanding from the tamping workgroup of the time needed to undertake the signal works. The TIC stated they agreed to the request on the proviso that the track work up to Dudley Park station be completed so that the signal team could start to reinstate the connections to the rails in preparation for testing the correct operation of the track circuit.
At about 1032, the TIC telephoned the Acciona PPO to tell them that the track work was progressing well, and the work group would likely reach the Torrens Road level crossing later that day. The TIC also told the PPO they had agreed with the supervisor of the work group to expand the signal team’s scope of work to include the alteration of the Torrens Road level crossing control circuit. The TIC reached agreement with the PPO that they would first undertake the alteration of Torrens Road control circuit, before meeting with them to provide a completed infrastructure booking advice form (IBA).[7]
At about 1045, the TIC told the signal electrician of the change to the scope of work and that they would now install jumpers at Torrens Road, before returning to remove the additional track connections between Dudley Park and Ovingham stations. Shortly after, the TIC and signal electrician arrived at the Torrens Road level crossing and accessed the location case that housed the level crossing control circuit.
The TIC and signal electrician positioned themselves at the front (Figure 2) and rear (Figure 3) of the location case (Loc 472) respectively to begin installation of the jumpers. The TIC kept the ITP, as was their usual practice, and called instructions to the signal electrician on where to connect the ends of each jumper wire. The ITP circuit diagram required 3 jumper wires to be installed. The TIC marked off the installation of each corresponding connection on the ITP as the work progressed.
The rear view of location case 472 shows the temporary jumper wiring (red). The installation method for the jumper wiring was intended and meant to make temporary wiring conspicuous from other wiring installed at that location.
Figure 2: Torrens Road location case (Loc 472) front view
Note: Location case 472 showing signalling control equipment, image modified by ATSB to annotate and remove graffiti tags from exterior of location case. Source: Acciona, annotated by the ATSB
Figure 3: Torrens Road location case (Loc 472) rear view
Source: Acciona, annotated by the ATSB
Following the installation of all the jumpers, the TIC operated the test switch[8] to check the correct operation of the level crossing warning equipment. The warning equipment functioned as the TIC expected.
The TIC and signal electrician then left the Torrens Road level crossing location. The TIC went to meet the PPO to complete the IBA. The signal electrician went to the track and met with the 2 trades assistants in readiness to remove the electrical connections from the rails.
At about 1120, the TIC and PPO completed the IBA for the work to the Torrens Road level crossing. Shortly after, the TIC contacted the signal electrician by telephone informing them that the IBA was complete, and they could commence removal of the connections from the rails.
During this work, connections to 572C track located between the Dudley Park and Ovingham stations were removed. The removal of the track connections caused an associated relay in the level crossing control circuit for the Torrens Road level crossing to also de-energise.
Arrival of train 1MP9 at Torrens Road level crossing
At about 1155, SCT Logistics train 1MP9, travelling on the ARTC rail line, occupied the Torrens Road level crossing southern approach circuit. The ARTC signalling system detected the train and sent a control input to the AMPRN Torrens Road level crossing control circuit to activate the warning equipment. The warning equipment did not activate in response to the ARTC control input. The train, travelling at a speed of 44 km/h continued to approach the Torrens Road level crossing.
At about 1156, as the train rounded a slight left curve about 90 m before the Torrens Road level crossing, the driver saw that road traffic was still crossing in front of the train and that the warning equipment had not activated. The driver immediately moved the automatic brake handle to the emergency position to apply maximum braking. About 45 m from the crossing the driver started to continuously sound the locomotive horn to warn road traffic of the train’s approach.
Train 1MP9 continued to brake, entered and travelled through the level crossing, narrowly missing a number of road vehicles before the lead locomotive stopped at the 5.25 km mark,[9] about 260 m north of the level crossing. Trailing freight wagons from 1MP9 blocked the Hawker Street and Torrens Road level crossings for the passage of road traffic.
Response to Torrens Road level crossing irregularity
At about 1158, the driver of 1MP9 made an emergency radio call to the ARTC network control officer (NCO) notifying the Torrens Road crossing warning equipment had failed to operate for their train and that there were several near misses with road vehicles as the locomotive passed over the level crossing.[10] The NCO instructed the train crew to remain in situ and wait for the arrival of support personnel to manage safety at the site (Figure 4).
Shortly after the incident, representatives from SAPTA, ARTC, Acciona, the Office of the National Rail Safety Regulator and South Australian Police attended the site. SAPTA representatives coordinated the onsite response, gathered evidence, and commenced an internal investigation.
Rail vehicles from 1MP9 continued to block the Hawker Street and Torrens Road level crossing until about 1505, when, following agreement with SAPTA representatives, the ARTC NCO issued an authority to the train crew to continue their journey to the SCT Logistics Penfield rail freight centre.
Figure 4: Train 1MP9 at Torrens Road level crossing
At the time of the incident, train 1MP9 was crewed by 2 drivers. Both drivers held route competencies that were current for the track section travelled. The health assessments of each driver were current, and they had both met the standard prescribed by the National standard for health assessment of rail safety workers without restriction.
Signal team
The Rail Industry Construction (RIC) signal team comprised the tester in charge (TIC), a signal electrician and 2 trades assistants. The TIC and signal electrician were rail safety workers, assessed to have the required competencies to undertake the rail safety work on the Adelaide metropolitan passenger rail network (AMPRN) signalling system. The statement of competency record for the TIC and signal electrician identified they had around 55 and 45 years of experience respectively undertaking rail safety work on signalling infrastructure. The experience included previous engagements and the successful completion of similar tasks on both the AMPRN and Australian Rail Track Corporation (ARTC) network signalling infrastructure.
The trades assistants were supervised by the TIC or signal electrician and were not qualified to undertake unsupervised rail safety work on the signalling equipment. Neither trades assistant was directly involved with work to implement the Torrens Road inspection and test plan (ITP).
The signal electrician and TIC underwent health assessments as per the requirements of the National standard for health assessment of rail safety worker as a rail safety worker category 1 and 3 respectively. Although there were anomalies with the TIC’s health assessment category and currency, there was no evidence the TIC or signal electrician health assessment categorisation or any physiological condition present at that time influenced the incident at Torrens Road.
In the week prior, the TIC and signal electrician worked between 8.5 and 12 hours each day on the Gawler rail electrification project (GREP) undertaking the signalling alterations to facilitate the track tamping works (see Appendix A – Fatigue risk management program). These hours were generally consistent with the Acciona fatigue management guidelines (10 to 12 hours per day up to a maximum cumulative total of 60 hours per week).
The Acciona Alliance rail safety management plan outlined the procedures put in place to satisfy the accreditation requirements of the Rail Commissioner[11] (RComm). In particular, the competency, health and fitness, and fatigue management programs applicable to the GREP rail safety workers of Acciona, and subcontractor RIC. For additional information related to each program see Appendix A – GREP safety management system procedures.
Train information
SCT Logistics train 1MP9 comprised locomotives CF4430, CF4410 and CSR002 hauling 46 rail vehicles. The train was 1,773 m in length and had a gross mass of 4,561 tonnes. The train was travelling from Dooen, Victoria to the SCT Logistics Penfield rail freight centre near Adelaide, South Australia.
Railway infrastructure
The Australian Rail Track Corporation
The ARTC interstate rail line at Torrens Road consisted of a single standard gauge (1,435 mm) rail track. The track was constructed using continuously welded rails secured to concrete sleepers by resilient fasteners and supported on crushed rock ballast.
The signalling system enabled the bi-directional operation of rail traffic. The system incorporated level crossing controls that functioned independently from the signalling system on the adjacent AMPRN. Rail traffic approaching Torrens Road level crossing on the ARTC rail line triggered a level crossing control, which then provided an input to the AMPRN signalling system to activate the level crossing warning equipment, and the road traffic light signals.
South Australian Public Transport Authority
The AMPRN at Torrens Road consisted of 2 broad gauge (1,600 mm) rail tracks. The tracks were constructed using continuously welded rails secured to concrete sleepers by resilient fasteners and supported on crushed rock ballast.
The Torrens Road level crossing was located on an arterial road near the north-western fringe of the Adelaide central business district. The rail track infrastructure of the AMPRN and ARTC network ran in parallel at that location (Figure 5).
The configuration of the signalling system for the AMPRN enabled passenger rail traffic to principally travel in either an up or down direction[12] on the respective track. The Torrens Road level crossing control equipment could be configured locally[13] to enable the automatic operation of the warning equipment to facilitate single line bi-directional working (with limited functionality). Prior to the implementation of single line bi-directional working, an alternative method of safe working was required for the management of rail vehicle movements.
All rail tracks were protected by flashing lights, gongs and half boom barriers mounted to mast assemblies. In addition, several mast assemblies were equipped with 3 aspect road traffic light signals. The traffic light signals interfaced with the railway level crossing control system and other road traffic light signals at an adjacent road traffic signalled intersection, located about 100 m to the south-east. The traffic light signals controlled the flow of road traffic to prevent queuing of road vehicles across the rail tracks at the Torrens Road level crossing.
The Torrens Road flashing lights, gongs, half boom barriers, and the associated trackside signalling and communication systems were operated and maintained by the South Australian Passenger Transport Authority (SAPTA) under the rail safety accreditation of the RComm.
Figure 5: Road and rail track layout at Torrens Road level crossing
Source: Google Earth, annotated by the ATSB
Gawler rail electrification project
Overview
The GREP works were managed by the South Australian Department of Infrastructure - Transport project delivery (TPD) and undertaken under the RComm rail safety accreditation. The RComm, SAPTA and TPD were all departments or bodies under the South Australian Department for Infrastructure and Transport (Figure 6). Relevant SAPTA safety management system standards, procedures and work instructions for the AMPRN signalling and communications systems were adopted by TPD to manage the GREP works.
Figure 6: AMPRN rail network and GREP project organisation structure
Source: ATSB
The TPD delivered the GREP works through the principal contractor, Acciona, managing the project alliance safety management plan. Acciona initially engaged subcontractor RIC to undertake works associated with the provision of electrical conduits and pits for the project. Acciona later varied the subcontract with RIC to include the provision of qualified rail safety workers to undertake project work as directed by Acciona. Specifically, the alteration and testing of parts of the level crossing control circuitry, and removal and reinstatement of connections to the rails in the areas affected by the GREP track works. The operation of rail maintenance and construction vehicles used in conjunction with the GREP work site was under the Acciona rail safety accreditation as a rolling stock operator. Acciona was not accredited in South Australia as a rail infrastructure manager (RIM).
The roles, responsibilities, authorities, accountabilities and general safety duties applicable to the various parties involved in the contractual arrangements to deliver a rail project, such as the GREP, were outlined in the Rail Safety National Law – South Australia Act 2012 (RSNL) and associated guideline documents published by the Office of the National Rail Safety Regulator and the Rail Industry Safety and Standards Board.
The RSNL incorporated the principles of shared responsibility and accountability in contractual arrangements and highlighted that the management of rail safety was the shared responsibility of everyone involved in undertaking the required rail safety work. The degree to which a person was accountable for rail safety was dependent on the nature of the risk their activities might pose to rail safety. The management of risks associated with railway operations was therefore predominantly the responsibility of the person best able to control them.
Additional information related to the RSNL and guidelines for contracting arrangements are contained under Appendix B – Contracting in the rail industry.
Procedures for temporary signalling system alterations
To manage potential risks to rail operations when undertaking temporary wiring alterations to the level crossing control circuits, RIC developed documentation that defined the project scope and responsibilities, work method statements, and the ITP specific to each level crossing location.
Level crossing inspection and test plan approval procedure
On 23 September 2020, representatives of Acciona, TPD and RIC met to establish the procedure that Acciona would follow to submit the draft ITPs, which included the level crossing control circuit schematic drawings to TPD for approval.
The agreed procedure (Figure 7) required Acciona to submit the draft ITPs for all the affected level crossing locations as a single package. TPD was then to forward the package to SAPTA for review and final approval. Once approved, SAPTA would endorse a network access authority application (NAA) to allow the RIC rail safety workers (the signal team) access to the AMPRN to commence work onsite.
Figure 7: Inspection and test plan approval flowchart
Source: Acciona
During the meeting, TPD identified that the work to isolate (decommission) level crossing functionality was ‘specialised works’ and that the SAPTA procedures for installing temporary wiring, testing, and commissioning activities were to be followed by the signal team.
Although this requirement was identified during the meeting, neither TPD nor SAPTA provided Acciona or RIC with a copy of the SAPTA work instruction WI-AM-SP-1234 Signalling system temporary decommissioning and jumpering or the SAPTA forms FO-AM-SE-1226 Inspection and test plan template and FO-EM-SE-1226 - Amendment log for their reference or use in the development of the GREP signalling procedures for the specialised works specific to the level crossings (see SAPTA signalling system temporary decommissioning and jumpering work instruction).
To develop the draft ITPs, RIC adapted a SAPTA ITP document sourced from a project RIC had previously undertaken for TPD on the AMPRN. The formatting of the ITP document was generally consistent with the SAPTA form FO-EM-SE-1226 and included sections related to the:
document and version control
plan approval and the allocation of roles and authority to implement the plan
master test plan listing in sequential order the equipment and a description of the required task to be undertaken
certification by the TIC of the tasks and related testing activity that were complete.
RIC representatives also prepared 2 copies of the relevant control circuit diagrams for each level crossing installation. One copy showed the jumpers (marked up in red) to illustrate the required termination point of each wire in the control circuit. The second copy showed the jumpers (marked up in green) to illustrate the wires that must be removed following completion of the track work for that day. A fresh copy of the ITP and circuit diagram package was produced for each occasion where modification of a level crossing control circuit was necessary.
On 25 September 2020, the RIC representatives[14] who had either produced, checked or approved content, signed off on version 1 of the draft ITP for each of the level crossing installations the GREP track work program would affect. Acciona subsequently submitted copies of the draft ITPs by email as a single package to TPD for forwarding to SAPTA for review and final approval, as per the ‘one review gate process’ in the approval flowchart.
Signalling work scope procedure
On 15 October 2020, RIC developed the GREP Tamping project signalling methodology document to describe the scope of work for the project, the network access arrangements and the division of responsibilities between Acciona, RIC and SAPTA for managing the affected signalling infrastructure.
The document specified that RIC would provide suitably competent staff (the signal team), and that prior to the commencement of any site activity, these staff would attend the daily Acciona and PPO pre-work briefings. During the pre-work briefings, RIC staff, in this case the TIC, was required to notify SAPTA maintenance staff and the PPO of the proposed location of work and the tasks to be performed that day. The document also specified that under no circumstances was the signal team to undertake any signalling work until the TIC had an Infrastructure booking advice (IBA) in place with the PPO (see Procedure for implementing an infrastructure booking advice.).
After implementation of the IBA, the scope of work specified the signal team was responsible for:
The disconnection of equipment and installation of temporary bridging [jumpers] to ensure that the level crossings remain working for ARTC trains will be carried out as per the approved ITP’s and recorded in the ITP’s.
On 20 October 2020, the TPD signal site manager approved the content of the signalling methodology document, which specified the signal team was to carry out the instructions contained in the approved ITP. The methodology document also specified that track circuit maintenance record cards and the ITP documents must be completed as each piece of signalling infrastructure was tested and certified and that photographic records were taken of the locations before commencement and on completion of works.
While the review and approval process for the tamping project signalling methodology document was ongoing, the ITPs referenced in the document were still in draft format, having been forwarded by TPD to SAPTA for review and approval the day prior to the finalisation of the methodology document.
Approval of draft inspection and test plans
On 22 October 2020, SAPTA responded to TPD requiring amendments to several ITPs that were identified to contain errors.[15] The review found no error or omission in the Torrens Road ITP document or circuit diagrams.
On 26 October 2020, Acciona resubmitted the corrected ITP packages.
On 30 October 2020, the SAPTA again responded highlighting 3 of the packages[16] still contained errors and required Acciona to correct and resubmit. SAPTA advised Acciona that the NAA for the track work would be withheld until the identified errors were corrected and the affected packages resubmitted for approval.
SAPTA communicated the outcome from the review process via a series of emails through TPD to Acciona. There was no record in the emails or respective electronic copies of the ITPs that SAPTA was satisfied the proposed testing arrangements managed risk, were consistent with the requirements of the SAPTA work instruction Signalling system temporary decommissioning and jumpering or that SAPTA had approved (certified) each ITP for use on the AMPRN. However, SAPTA did approve the NAA for the signal team to access the AMPRN and undertake the specialised work on the signalling system in accordance with the ITPs.
Although there were a series of amendments that occurred to some of the ITP documents to correct details related to the termination point of the jumpers, the document control version number and date recorded in the electronic copy of the respective documents remained as version 1 of 25 September 2020.
RIC subsequently provided the TIC with hard copies of the packages for each level crossing installation affected by the GREP. The package for each level crossing installation comprised a document describing the required plan for completing the inspection and test tasks and 2 copies of the circuit diagram marked up in red and green. None of the packages included a copy of the SAPTA forms FO-EM-SP-312 Signal circuit jumpering decommissioning or FO-EM-SP-313 Amendment log. Dependent on the planned track tamping work for that day, the TIC was then required to select and implement the relevant ITP.
The hard copy of the ITP documents subsequently issued by RIC for the TIC to implement, contained no record to identify the documents were the final version approved by SAPTA for use on the AMPRN. The TIC later reflected that the practice of issuing ITP documents without records of final certification by the RIM (in this case SAPTA) was unusual, but appeared normal for that particular operator.
Construction work method statement – track works
On 6 November 2020, Acciona released an updated version of the construction work method statement (CWMS) for the tamping and regulating track works on the AMPRN. The CWMS described the resources, processes and methodologies Acciona would use to undertake the track work on the Gawler rail line. The CWMS was developed to identify and control any risk that may arise during the works and document how these would be addressed.
The CWMS recorded that Acciona assumed the policies and procedures within the Acciona management systems were compliant with the requirements of the RComm rail safety accreditation. However, Acciona noted that, although the works were undertaken under the accreditation of the RComm it did not absolve Acciona from its responsibilities under the RSNL.
The CWMS detailed the planned scope of works and arrangements that included the identification of resource requirements, risk assessments, work health and safety, methodology procedures, and inspection and test plans to undertake the tamping and regulating work on the AMPRN. There was no consideration in the CWMS of the subcontracted work to RIC associated with the removal/reinstatement of connections to the rails or modification to the level crossing control circuity.
Although the engagement of RIC to undertake alterations to the signalling system was not specifically identified in the CWMS, the documentation developed by RIC for the identification of resource requirements, risk assessments, work health and safety, methodology procedures, and ITPs were generally consistent with the practice detailed in the CWMS.
Procedure for the installation of the temporary wiring
On 16 November 2020, RIC submitted a safe work method statement (SWMS)[17] to Acciona detailing how the connection, installation, termination and test and commission tasks were to be performed on the AMPRN signalling infrastructure. The SWMS outlined the worker competencies, site supervision arrangements and associated reference documents (NAA forms, approved tamping project signalling methodology and ITPs) necessary to undertake the work.
The SWMS listed the various steps involved in performing each task, identified the hazards and risk assessed the related controls. The resulting residual risk rating for the various steps was assessed as being either medium or low, dependent on the task. However, the overall risk assessment for the SWMS determined the work activity was high risk.
The potential hazards and associated controls were primarily focused on managing work health and safety implications and not the operational hazards and risk to rail safety that may arise from the modification of vital signalling control systems.
The SWMS did not address the requirements of the SAPTA work instruction Signalling system temporary decommissioning and jumpering, particularly in relation to managing the potential risk to rail safety for the adjacent ARTC network. There was no record Acciona, TPD, SAPTA or RComm had reviewed and approved the use of the SWMS document for the GREP works.
Procedure for implementing an infrastructure booking advice.
The TPD provided Acciona with a copy of the SAPTA AMPRN Train rules and procedures Volume 4 - Work on track rules and procedures. The document contained instructions to rail safety workers on the requirements and procedures to compile an infrastructure booking advice (IBA) form. The IBA must be used wherever infrastructure was:
permanently installed or commissioned
permanently decommissioned or removed
temporarily removed from service
returned to service following temporary removal from service.
The procedure provided various options to complete the IBA, one of which allowed the operations controller and rail safety worker to jointly compile the IBA. This allowed completion where the parties were remote from each other. If the rail infrastructure work was within a work site under the control of a PPO, a copy of the IBA was to be provided to the PPO before any equipment was either ‘booked out’ or ‘booked into’ service.
In this instance, the Gawler rail line was closed to rail traffic for the GREP track work and the worksite was under the control of a PPO. Under this arrangement the requirements of the AMPRN train rules were reflected in the GREP Tamping project - signalling methodology procedure, which required the TIC on arrival to contact the PPO and advise of the location of works and tasks to be undertaken. It also specified that no work be commenced unless the TIC had an IBA in place with the PPO. There was no mention in the methodology procedure of a requirement to provide a copy of the completed IBA to the PPO.
The IBA completed following the alterations to the Torrens Road level crossing control circuit recorded that the level crossing warning equipment would be operational by the test switch only for the AMPRN lines (indicating both up and down). This statement was only partially correct since the temporary control circuit modifications, detailed in the ITP, bridged control functions on the AMPRN up line but retained the down line control function.
The purpose of the IBA document was to communicate and record the intended status of critical rail infrastructure or equipment to the operations controller or PPO controlling the movement of rail traffic, which may be affected by the proposed infrastructure changes.
The IBA process, as applied to the GREP, considered only the infrastructure and equipment alterations that were planned to be affected by the work, in this instance the AMPRN Gawler rail line level crossing up direction approach. As the ARTC network was not intended to be affected or removed from service, there was no requirement stipulated in the IBA for the TIC or PPO to notify the ARTC network operations controller and advise that an alteration was made to the control circuitry of the level crossing protections shared by the 2 networks.
SAPTA signalling system temporary decommissioning and jumpering work instruction
The SAPTA work instruction Signalling system temporary decommissioning and jumpering specified the processes a qualified SAPTA employee must undertake to temporarily decommission signalling system infrastructure on the AMPRN. Decommissioning included the installation of circuit jumpering and the removal of track circuit connections, the same type of specialised work that SAPTA identified was to be undertaken by RIC for the GREP.
The SAPTA work instruction specified the roles and responsibilities of a SAPTA employee (rail safety worker) undertaking the specialised work as:
Qualified employees are responsible for ensuring signalling assets are decommissioned using the process below. Qualified employees performing temporary decommissioning and jumpering shall ensure another qualified employee is available on site to verify correct installation of jumpers. Qualified employees shall ensure all documentation associated with temporary decommissioning and jumpering contains complete and accurate information.
Where temporary jumpering affects adjacent railway (i.e. ARTC), personnel shall ensure the rail transport operator has been made aware of the work being undertaken. Where signalling functions on adjacent lines are required to remain active (i.e. level crossings isolated for AMPRN line but should operate for ARTC movements), the correct operation of those functions shall be verified by the qualified employee performing the decommissioning/jumpering.
Additionally, the instruction detailed the processes a qualified employee was to follow when undertaking either unplanned or planned decommissioning work. Unplanned or ‘emergency work’ covered situations where it was not possible to develop and use a pre-approved ITP, due to the unpredictable nature of the work and the resultant time constraints in responding to the particular emergency.
In such cases, the qualified employee was to first consult with the operations controller for that particular location to inform them of the signalling infrastructure affected. The qualified employee was then to record any decommissioning or reinstatement work undertaken on the signalling system infrastructure form FO-EM-SP-312Signal circuit jumpering decommissioning (Figure 8). The qualified employee was required to include detail for the:
identification of the qualified employee actioning the work including their qualification
identification of the qualified employee verifying the work including their qualification
notification to the operations controller of that area and the identification of the equipment to be decommissioned
description of the proposed task (that is, detailing the circuit functions jumpered and track leads removed)
verification by another qualified employee.
Figure 8: Example form – SAPTA signal circuit jumpering decommissioning
Source: South Australian Public Transport Authority
For occasions where the decommissioning works were able to be planned, the work instruction required the:
correlation of affected signalling circuits prior to the ITP development (to ensure accuracy of the control circuit drawings)
preparation and certification of an ITP by a qualified employee that recorded any decommissioning or reinstatement work to be undertaken on the signalling system infrastructure
independent review to check and certify the ITP prior to issue
inclusion of the form FO-EM-SP-312 Signal circuit jumpering decommissioning
TIC or qualified employee responsible for executing the plan to take receipt of the ITP
decommissioning work to be actioned in accordance with the approved ITP for that project or works
amendment (if required) to the ITP be recorded on form FO-EM-SP-313 Amendment log. Any amendment was to be independently verified.
For planned works, the work instruction required both the development of an ITP form and the inclusion of form FO-EM-SP-313. The format of the ITP and FO-EM-SP-313 form templates included duplicated information related to the required tasks and records to be kept. The work instruction did not specify how the template forms were to be used together when planning work in advance.
In summary, SAPTA required a qualified employee (rail safety worker) undertaking either unplanned or planned decommissioning work to ensure that:
another qualified employee was available onsite to verify the correct installation of jumpers
all documentation associated with temporary decommissioning and jumpering contained complete and accurate information
the correct operation of those functions was verified [validated] by the qualified employee performing the decommissioning/jumpering
where signalling functions on adjacent lines were required to remain active (that is, level crossings isolated for the AMPRN line but should operate for ARTC movements), the correct operation of those functions was to be verified by the qualified employee performing the decommissioning/jumpering.
Industry standards for signalling testing and commissioning plans
Overview
The Rail Industry Safety and Standards Board published standards AS-7717-2016 Signal testing and commissioning and AS-7716-2017-Signal testing process. These standards were to provide rail transport operators,[18] such as the RComm, with a common framework to plan and execute the inspection, testing and commissioning activity for new and altered signalling infrastructure on their respective networks.
Signal testing and commissioning
Standard AS-7717-2016 defined the range of inspection and test activities necessary for a rail transport operator to certify the safety of the new or modified signalling system before placing it into service. These included the testing activity required following minor works, such as alterations for the installation and removal of temporary jumper wiring to level crossing control circuits.
Such alterations were to be tested in accordance with the standard considering the type, extent, and risk associated with the particular alterations being made. The nature of the testing and commissioning activities could vary dependent on requirements determined by the accredited rail infrastructure manger,[19] which for the AMPRN and associated GREP works was also the RComm.
The standard stipulated the railway organisation and its management structure together with the planning process and staff competence were each critically important to ensure the railway signalling systems were safe for the operation of trains. The requirements for the planning process included elements such as:
the production of formal documentation of the required activities and tasks
the allocation of responsibilities and the personal competencies required to undertake the tasks
the independence required for people’s involvement among the different parts of the work
the documentation to be used for the testing and commissioning plans.
The overall objective was the development of a detailed ITP, which documented the processes, work activities, and the controls implemented to achieve the requirements of the standard, using an agreed format.
For the GREP works, the subcontractor, RIC, identified and undertook the development of the ITPs for each level crossing installation. These plans were then forwarded through Acciona and TPD to SAPTA for approval.
Identification of interfaces outside the commissioning boundaries
Standard AS-7717-2016 also required that before inspection and testing activities commenced at sites containing signalling equipment that was in use, the RIM was to be informed of the extent and program of work. Additionally, consideration should also be given to elements outside of the defined boundaries of the commissioning area.
For the GREP level crossing works, the TPD and SAPTA were aware of the extent of the works, and inspection and testing activity through the approval of the GREP Tamping Project Signalling Methodology document and the coordination activities through the TPD onsite project manager.
Interfaces outside the GREP boundaries were managed through the rail-to-rail interface agreement[20] between SAPTA and ARTC. The agreement managed the identified risks to safety that may arise from railway operations carried out by either operator (SAPTA or ARTC) that would affect the other at the shared road-rail interfaces. The agreement included the interface at the Torrens Road level crossing.
The agreement required each operator to provide advance notice to the other, prior to commencing any works likely to materially affect the other operator’s rail network. To address this requirement, Acciona, via TPD, provided ARTC advance notice of the proposed GREP work in the format of a draft train notice.
On 1 December 2020, ARTC published train notice TN2925 advising train crew operating on the ARTC network that tamping works were to be undertaken on the adjacent AMPRN. The notice contained the following information:
The GREP project will be undertaking tamping and regulating works on the Gawler line between 2.7km to 8.5km (AMPRN km) on both the up and the down track. The works will have no impact on ARTC line and there will be no potential to foul ARTC.
As part of the works some ballast will be placed inside the corridor North of Ovingham Railway station using the access gate on the ARTC side (at least 3m away from the tracks) and a loader will be intermittently at the stockpile area to load trucks with ballast under TOA [track occupancy authority] between trains.
The Qualified Rail Safety Worker will be required to take out adjacent line protection TOA [track occupancy authority] ATP [as traffic permits] when operating the Ballast Regulator Side Wing Plough on the Down Main Line.
The works will have no impact on ARTC Network Services or Operations.
The Qualified Rail Safety Worker will ensure that communications are made with the Network Controller prior & post work.
The notice indicated that the proposed tamping works would have no impact on the ARTC network nor the potential to obstruct traffic operating on that line.[21] Neither the notice, nor other communication between Acciona, TPD or SAPTA and ARTC identified that temporary alterations would occur to the level crossing control circuity of the shared level crossings in the work area between North Adelaide and Islington, encompassing Torrens Road.
Requirement for independence of persons undertaking testing activity
The planning and implementation of an effective inspection and test regime was a critical element to reduce risk to rail safety associated with undertaking works on vital signalling control equipment. This required the development of ITPs that must include sufficient tasks to support the verification[22] and validation[23] of any new or altered safety‑related signalling system. The standard required:
These verification and validation processes shall be performed at an appropriate level of independence from the construction and implementation process to be verified and validated. The degree and nature of this independence shall be determined by taking into account at least the following factors:
(a) The risk of errors being perpetuated during the verification and validation process due to there being too close an association between the persons performing the verification and validation and those involved in the construction and implementation process.
(b) The risk imposed on the existing system both by the introduction of the system to be verified and validated and by faults or inconsistencies in that system.
The TIC and signal electrician worked together in undertaking both the installation of the temporary jumper wiring and the verification and validation testing of the level crossing control circuitry. Although, in this instance there was close association between the persons performing the work, the standard allowed this arrangement through placing a higher weighting on competence of organisations rather than independence provided:
…where independence cannot be achieved other controls should be considered to assure any additional risk due to a lack of independence is controlled. If it is not possible to achieve independence, then approval shall be given by the RIM [rail infrastructure manger] of the alternative control measures that will be used to control the additional risk due to the lack of available competent independent resources
Other than reviewing the draft ITPs, there was no record of SAPTA assessing the competencies of the rail safety workers undertaking the signalling work. Further, there were no alternative control measures implemented to manage the risk due to the limited availability of other competent independent resources to undertake an independent inspection and test activity.
Signal testing process
The second standard, AS 7716-2017 signal testing process, provided greater detail of the types of testing methods and procedures that may be used when commissioning typical signalling apparatus and systems. Emphasis was again placed on the importance of maintaining independence between the performance of the installation and testing activities. Although the standard described the minimum requirements for undertaking inspection and testing activities, it did not diminish the obligation of the verification, validation and test personnel to decide what should be tested and how it should be tested respectively.
The types of testing methods and procedures were grouped under post‑installation testing, which was to independently verify the new or altered work was built in accordance with the design documentation (in this case the circuit diagram) and secondly, the function testing and validation phase, which proved the new or altered work performed as designed.
Installation testing verified the system was built in accordance with the design required testing include the following:
detailed circuit testing
cables testing
apparatus testing.
System testing and validation included the following:
For the GREP level crossing works, RIC provided the TIC with a pre-approved suite of ITPs to specify the tasks they were required to perform to install/remove temporary jumpers, and for the testing and validation of the altered control circuit to ensure the level crossing warning equipment functioned as the design intended.
Torrens Road inspection and test plan
Overview
The Torrens Road ITP document specified the processes approved by the RIM that RIC (TIC and signal electrician) would undertake for the planned temporary decommissioning of critical signalling system infrastructure (see Appendix C – Torrens Road inspection and test plan). The ITP was divided into 3 sections that contained the:
details for the document version control, plan approval signatures and allocated responsibilities to undertake defined roles
verification tasks to ensure the sign-off acceptance for the allocated responsibilities and confirmation of safe working and IBA arrangements
master test certificate tasks to confirm safe working arrangements and the specifications for the sequence of installation and inspection and test activities the TIC was required to coordinate and sign off as completed.
Plan implementation
The verification section of the Torrens Road ITP document required the TIC to ensure documents were attached and details of allocated responsibility completed. The section also required the TIC to confirm that safe working procedures were in place and to ‘take out’ an IBA before commencing work. The latter, in compliance with SAPTA rules, would include direct communication between the TIC and operations controller prior to the commencement of any work to alter signalling infrastructure.
On this occasion, the worksite was under the control of a PPO and there was no direct contact between the TIC and operations controller. The TIC and PPO, however, did not follow either the signalling methodology or IBA procedures, which required the completion of an IBA form prior to the commencement of work. The TIC and PPO instead agreed verbally to complete the jumper installation, before meeting later that morning to complete the IBA. Although the TIC had undertaken several actions to address the various safe working, IBA, and other tasks in the verification section, those tasks were not signed off in the plan document as complete.
Temporary jumper wiring installation
The plan detailed the series of tasks to be coordinated by the TIC that related to the temporary jumper installation (Figure 9).
Figure 9: Master test certificate, section 2 page 1 of the Torrens Road inspection and test plan
Note: Extract of the SAPTA‑approved ITP specifying the required tasks and records to evidence completion of that task. Source: South Australian Passenger Transport Authority, annotated by the ATSB
The ‘jumper install’ section of the plan contained a description of where to terminate each jumper wire and an associated field for the TIC to record the identification number of the jumper together with details of the date, time, and the tester who certified that task was completed. Although the tasks to install the 3 jumpers in the level crossing control circuit were actioned by the TIC, no entry was recorded in the plan to specify the jumper identification number or to certify that task was completed.
The task descriptions in the plan document for the installation of the jumpers (highlighted in red font) reflected the circuit diagram (marked up in red). The circuit diagram showed 3 jumpers positioned in the level crossing control circuit to bypass functions that could be affected by the track tamping works (Figure 10).
Temporary jumper wire ‘A’ bypassed the control function that incorporated the up-direction AMPRN track circuits to the level crossing that were to be disconnected to facilitate the track work. The jumper wires ‘B’ and ‘C’ bypassed control functions associated with the automatic operation of the level crossing warning equipment when configured for single line bi-directional working.
The TIC stated that, on reflection, only one temporary jumper wire was required. The other 2 jumpers (marked ‘B’ and ‘C’ in Figure 10) were superfluous[27] as they bypassed the single line working function, which was not planned to be in use on 7 December 2020. The single line working function would only be used where single line bi-directional working was instigated under an alternative method of safe working arrangement. This was not the case on 7 December 2020.
Figure 10: Extract of the SAPTA‑approved Torrens Road inspection and test plan showing approved temporary wiring configuration
Note: Extract of circuit diagram showing the SAPTA‑approved location for the 3 temporary jumper wires. Source: South Australian Passenger Transport Authority, annotated by the ATSB.
The TIC used the circuit diagram when calling instructions to the signal electrician on where to connect the ends of each jumper to the respective relay bases. The signal electrician did not have a copy of the diagram.
The relay base contained a matrix of termination points arranged in columns marked ‘A’ to ‘D’. The terminations in the ‘D’ column were located on the right side of the relay base. Each column then contained 8 rows of terminations. The base was embossed with markings that corresponded to the relative position of the termination in the matrix, for example ‘D1’ to ‘D8’. Each could connect up to a maximum of 2 wires. In addition to the embossed markings, each wire connected to a respective termination point that was fitted with a numbered colour‑coded sleeve. The colour of the sleeve was dependent on the column, for example, wires in the ‘D’ row were yellow. The sleeves were not fixed to the wire and could be moved along the wire to enable the rail safety worker to view the identification number of the wire if required.
During the installation of the temporary jumper (RIC01*11) between the function 47 1TR - B5 and 47 UpJR ‑ D7 (marked ‘Temporary jumper ‘B’’ in Figure 10), the probe from one end of the jumper was inadvertently placed into 47 UpJR - D6. This was located directly above the intended termination point (47 UpJR ‑ D7) detailed in the ITP and positioned on the bottom row of the relays in the equipment rack (Figure 11).
Figure 11: Rear of Torrens Road location case showing 47 UpJR control relay
Source: South Australian Passenger Transport Authority, annotated by the ATSB
One end of another jumper was installed to a termination (47 XSR R1) other than that identified in the approved circuit diagram. This was intentional and made under the instruction of the TIC. This amendment was undertaken as access to the nominated termination was impeded due to its physical location in the equipment rack and congestion from the existing wiring. This amendment did not change the intended functionality of the jumper or level crossing control circuit. The TIC subsequently illustrated the amended wiring on the circuit diagram. However, no corresponding amendment record was completed in the plan document to ensure correlation between the plan and circuit diagram.
The unintentional installation of a jumper probe into the 47 UpJR - D6 terminal and intentional termination of a jumper probe into the 47 XSR R1 termination meant the jumper wiring was configured as illustrated in Figure 12. This was inconsistent with the description in the approved plan document and detail shown on the amended circuit diagram.
Figure 12: Extract of the Torrens Road level crossing control circuit showing temporary jumper wires in the ‘as installed’ configuration
Note: Configuration of the temporary jumper wiring recorded by SAPTA during the post-incident onsite investigation. Source: South Australian Department for Infrastructure and Transport, annotated by the ATSB
Temporary jumper wiring testing
Verification
Following the temporary jumper install, there were no post‑installation testing tasks included in the ITP to specify the tests that the TIC was to coordinate to ensure correctness. Such tests were typically required to ensure the ‘as installed’ wiring conformed to the circuit diagram and that the required control functions would still operate the level crossing warning equipment as designed. In this case, the operation of the level crossing warning equipment for trains approaching on the ARTC network.
In the absence of any instruction from SAPTA to specify the testing or methodology required for recording test results, the TIC used their typical method for recording verification testing and marked up the circuit diagram with details to record the installation of each jumper together with its identification number (Figure 13).
Figure 13: Extract from the Torrens Road inspection and test plan marked up with testing annotations and amended jumper wiring configuration
Note: Extract of the circuit diagram showing the location of the temporary jumper wiring and TIC testing notations as completed on 7 November 2020. Signatures removed to de-identify the involved parties. Source: South Australian Passenger Transport Authority, annotated by the ATSB
The TIC recorded each test activity using a system of symbols to signify the installation and verification of the jumper wire in accordance with the approved circuit diagram. The markings indicated the TIC had certified the completion of a wire count[28] and continuity test[29] for each of the installed jumpers. The TIC also used an asterisk to denote that one end of a jumper was no longer connected at the terminal originally approved.
When marking up the circuit diagram, the TIC did not undertake an independent visual inspection to verify the correct installation of the jumper wiring. The TIC acknowledged that they should have undertaken an independent visual check, but instead had relied on the information provided by the signal electrician, due to their significant experience in undertaking work on signalling systems. The TIC stated that there were limited resources in the signal team and no other member had the qualification required to undertake independent testing. The TIC stated that there was therefore a tendency not to check the work undertaken as rigorously as would be the case for a team member with less experience.
The methodology used by the TIC to verify the ‘as installed’ wiring against the control circuit diagram did not detect the error made in the termination of the jumper wire RIC01*11 into the 47 UpJR - D6 terminal (instead of 47 UpJR – D7) or the transposition of the unique identification numbers for 2 of the jumper wires.
The TIC stated that the ITP (plan document) was not identified as a commissioning work instruction and, in their mind, it appeared only as a reference document to ensure the circuit diagrams were attached, the PPO was informed and the IBA had been completed. The TIC also noted the level of documentation provided to support their work was minimal in comparison to their experience when undertaking similar tasks with other rail organisations. The TIC stated the information in the ITP document basically reflected information related to the jumper installation and removal that was contained in the circuit diagrams. It did not appear to them as a typical work instruction forming part of a commissioning plan.
Validation
Following the completion of the verification tests, the TIC operated the level crossing test switch (Figure 13) located in an enclosure on the AMPRN location case to validate the correct operation of the level crossing circuit (and warning equipment). The level crossing warning equipment operated as the TIC expected. The TIC recalled that there was no mention in the ITP of testing the functionality of the ARTC level crossing, and that the only validation test specified was the operation of the test switch, following the removal of the temporary jumpers.
The test of the ARTC approach function required either the operation of the test switch on the ARTC signalling system control box or the interruption by other means of the ARTC approach control function relayed to the AMPRN signalling system. The TIC stated that, in hindsight, when testing the functionality of the level crossing warning equipment, the ARTC test switch should have also been operated to validate the correct operation of that function.
Although the TIC undertook tests to validate the correct operation of the level crossing equipment, the tests did not identify the wiring error. In this instance, another relay function in the control circuit needed to change state for the error to become apparent by the operation of the ARTC test switch or approach control function.
There was no record on the circuit diagram or plan document to indicate any testing of a control function had occurred (including by the operation of the test switch). The TIC signed off the ITP circuit diagram to certify the temporary jumper installation was completed, and the level crossing warning equipment functioned as expected.
In preparation for the track tamping work to commence, the signal team disconnected connections for the 572C track that caused a 572C T1P relay to de-energise. The change in state of this relay closed contacts A7 and A8. An alternative connection from the control circuit power supply was applied to the 47 XSR function via the incorrectly installed jumper wire RIC01*11 (Figure 14). The false feed subsequently maintained the 47 XSR function in an energised state (level crossing warning equipment inactive), regardless of the configuration of another AMPRN or ARTC control input in the circuit. The level crossing warning equipment would now not operate for train 1MP9 approaching Torrens Road on the ARTC network, or any other AMPRN or ARTC train approaching the level crossing.
Figure 14: Extract of the Torrens Road level crossing control circuit showing the path of false feed
Note: Red dashed line shows the path of the false feed applied to the Torrens Road level crossing control relay, after 572C T1P relay was de-energised. Source: South Australian Department for Infrastructure and Transport, annotated by the ATSB
Removal
The ITP document also specified tasks related to the ‘jumper removal’, which was to occur following the completion of the track work for that day. The work at Torrens Road had not progressed to a stage where these tasks needed to be actioned.
Associated with the tasks for jumper removal, additional tasks were included for the TIC to action. This included a test for the operation of the level crossing warning equipment with the test switch, to ensure the level crossing operated correctly, before advising the operations controller (in this case PPO) the works were complete.
The installation or removal of the jumper wiring did not affect the test switch. Operating the test switch only confirmed that the warning equipment would function using the switch. It did not confirm that a train approaching the Torrens Road level crossing on either the AMPRN or ARTC network would activate the warning equipment in the same way.
Summary
In summary, the extent of the testing requirements specified in the Torrens Road ITP following the jumper installation work were consistent with those developed for each of the other level crossings affected by the GREP track works that day (Bedford Road and Pym Street). None of the approved ITPs specified a requirement to:
verify the temporary jumpers were per the plan description and circuit diagram
validate the level crossing warning equipment would operate as intended with the temporary jumper wiring, particularly the continued operation of the level crossing warning equipment for trains approaching on the ARTC network.
Additionally, after completing the installation and testing phase, the scope of work for the signalling team on the day included the removal and reinstatement of several track circuit connections that were associated with the AMPRN up approach to the Torrens Road and other level crossings. In the absence of the use of form FO-EM-SP-312Signal circuit jumpering decommissioning, there was no provision made in the ITP documentation for the TIC to record the signal team’s actions associated with the removal, reinstatement or testing of the affected track circuit connections. Although there was no requirement in the ITP documentation, the GREP signalling methodology document specified the track maintenance record card for the affected track circuit must be completed as the equipment was tested and certified. These documents were distributed at various trackside location cases and were separate from the ITP document package developed to record the specialised rail safety work undertaken by the signal team for the GREP.
SAPTA post-incident onsite investigation
An onsite examination by SAPTA found:
The ITP used by RIC was not located in the location case as required by SAPTA procedures.
The ITP document, when provided, was not completed.
A comparison of the temporary wiring modifications against the ITP circuit diagrams identified the 3 temporary jumper wires were not installed in accordance with the details recorded in the approved circuit diagram.
One end of a temporary jumper wire was terminated to the wrong point in the circuit.
The incorrectly terminated temporary jumper wire subsequently provided a circuit, which falsely energised a relay that would have otherwise been de-energised during correct operation of the level crossing. This was determined as the reason for the level crossing warning equipment not activating for the approach of 1MP9 on the adjacent ARTC network.
Safety analysis
Introduction
On 7 December 2020, Specialised Container Transport train 1MP9 was travelling on the Australian Rail Track Corporation (ARTC) network through Adelaide in South Australia. As the train approached the Torrens Road level crossing, the driver saw that road traffic was still passing over the crossing, and that the level crossing warning equipment had not operated for the approach of the train. The driver initiated an emergency brake application before sounding the locomotive horn to alert any road traffic of the train’s approach. Shortly after, the train traversed the level crossing and continued a further 260 m before stopping.
This analysis will discuss the pre-planned tasks the signal team was required to undertake at short notice. It will then examine the limitations in the methodology adopted by members of the signal team during the installation and subsequent testing to certify the temporary wiring alterations and to ensure the level crossing warning equipment operated correctly.
Further, limitations in the development and approval processes for the inspection and test plans, and the associated procedures used to manage the specialised safety‑critical work to alter signalling infrastructure, such as the control circuits for level crossings, will also be considered.
Work plan change
On the morning of the incident, the signal team recommenced the planned work activity in support of the tamping works as was agreed during the pre-work briefing for that day. The signal team was familiar with the work as it was repeating an activity to alter the Pym Street and Belford Avenue level crossing control circuits, which it had successfully undertaken over the previous few days.
The control circuits for these 2 crossings were co-located in the Islington relay room situated at the northern end of the track worksite. This meant the tester in charge (TIC) and signal electrician could sequentially complete the tasks described in the respective inspection and test plans (ITPs) before relocating to the track area to commence the work associated with the removal of electrical connections to the rails. On completion of the track tamping works, the signal team would then reinstate and test the equipment before placing it back into service and signing off. The signal team was typically working 11.5 to 12 hour shifts each day to complete this scope of work involving the 2 level crossings and their associated track circuits.
The TIC had felt the signal team was under constant work pressure from the tamping workgroup to complete its work and that there was not an understanding of the time needed to undertake the signal works both before and after the track works were completed. The signal electrician reflected similar observations to that of the TIC and added that their workload at the commencement of that day was reasonable, but this had increased due to repair of damage to electrical connections caused by the tamping machine earlier that day.
However, the decision to add the third level crossing (at Torrens Road) at short notice and additional track circuit connections within the 12-hour workday requirement and allocated track possession timeframe placed further demands on the signal team. In addition, these tasks were not located near the Islington relay room like the previous works and were instead located toward the opposite end of the worksite. The TIC and signal electrician reported that they were cognisant that this work needed to be progressed as expeditiously as possible, to not further delay the track machine workgroup schedule in continuing its work toward Torrens Road, which had experienced previous delays. To save time, the TIC modified their usual approach to the infrastructure booking advice process (as part of the signalling method procedure), by making arrangements with the possession protection officer by telephone rather than meeting together to complete the advice form. This was likely to reduce the need to travel within the worksite before commencing work to modify the level crossing circuitry.
Work pressure is defined as degree to which employees feel under pressure to complete work, amount of time to plan and carry out work, and balance of workload (Glendon and Stanton, 2000). Employees who perceive that they are under pressure to increase production may deviate from safety rules that impede their progress, or perform tasks with less care, increasing the likelihood of errors. There is evidence for a link between work demands and accident involvement, where the higher the perception of work demands, the more accidents that occur (Clarke, 2006). Time pressure has also been found to degrade performance, such as task or load shedding, and a trading of accuracy for speed (Staal, 2004).
Together, this indicated that the signal team was experiencing actual or perceived work pressure with the addition of the Torrens Road level crossing, which influenced the deviation from adhering to the requirements outlined in the standard signalling methodology procedure.
Contributing factor
A late change to the planned scope of track tamping work on the day of the incident placed additional work demand with short notice on the signal team to implement the Torrens Road inspection and test plan.
Inspection and test plan – wiring
The ITP reviewed and approved by South Australian Public Transport Authority (SAPTA) required the TIC and signal electrician to install 3 temporary jumper wires to isolate the Adelaide metropolitan passenger rail network (AMPRN) up approach at the Torrens Road level crossing. Post-incident, both the TIC and signal electrician stated the installation could have been simpler, as the circuit alterations to facilitate the track work required the installation of only one of the jumpers, instead of 3.
During the installation of the jumpers, one of the superfluous jumpers was inadvertently installed to an incorrect point in the control circuit. Further, the installation of the second jumper required the TIC to undertake an amendment to the termination point to allow for simpler installation, increasing the complexity of the task. These 2 conditions could have been averted by the identification and removal of unnecessary jumpers from the Torrens Road ITP during the various stages of the review and approval process.
SAPTA required Acciona to submit the draft ITPs for their final review and approval prior to the commencement of work on the AMPRN. While the SAPTA review identified various drafting errors in some of the ITPs (excluding Torrens Road), there was no comment from SAPTA in relation to the inclusion of superfluous wiring. The inclusion of superfluous jumpers was common across the approved ITPs for the level crossings that were altered by the signal team during the track work earlier on that day and over the preceding days.
On 7 December 2020, each of the Bedford Avenue, Pym Street and Torrens Road ITPs required the signal team to install temporary wiring that bridged the single line working switches. The inclusion of superfluous wiring in the approved ITPs placed an unnecessary task demand on the signal electrician and TIC when performing work associated with the modification and testing of safety‑critical signalling infrastructure. The approved inspection and test plan for the Torrens Road level crossing control circuit included 2 superfluous temporary jumper wires. The inclusion of superfluous wiring both increased complexity of the task and placed unnecessary work demand on the signal electrician and tester in charge to implement the plan.
Contributing factor
The inspection and test plan for the Torrens Road level crossing control circuit included 2 superfluous temporary jumper wires. The inclusion of superfluous wiring both increased complexity of the task and placed unnecessary work demand on the signal electrician and tester in charge to implement the plan.
Temporary jumper wiring installation
After accessing the Torrens Road location case, the TIC and signal electrician positioned themselves on opposite sides of the equipment rack. During the installation, the TIC likely called out to the signal electrician to install the probe of a jumper into terminal D7 of the 47 UpJR.
The signal electrician did not have a copy of the circuit diagram to reference or cross‑check during the installation process for the jumpers and therefore relied on recalling the verbal instructions provided by the TIC. The signal electrician could however seek clarification from the TIC if they were unsure of the instruction or connection point that was provided. The 47 UpJR control relay was located in the bottom row of the relays installed in the equipment rack (Figure 11).
Together, it was possible that the increased time pressure, method for the installation of the temporary jumper wiring, and familiarity of the task from preceding work all combined to influence the unintentional installation of 47 UpJR into node D6, which was immediately above D7. This meant the jumper installed was not consistent with the approved ITP document and control circuit drawing and introduced a latent condition for the incorrect operation of the level crossing warning equipment.
Contributing factor
The signal electrician inadvertently installed one end of a superfluous temporary jumper wire to an incorrect terminal within the control circuit of the Torrens Road level crossing warning equipment. The installation error meant the jumper was not consistent with the approved control circuit.
Verification of signalling works
The Gawler rail electrification project (GREP) Tamping project signalling methodology procedure for planned work required the TIC to undertake and record their work in accordance with the content of the SAPTA‑approved ITP. However, none of the ITPs or other documentation developed for the GREP level crossing work specified a requirement for the TIC to undertake and record an independent verification of the correct installation of temporary jumper wiring. Although the verification task was not specified in the ITPs, the TIC (and signal electrician) had previous experience in commissioning signal system alterations and were cognisant of the need to undertake a verification inspection for the correct installation of the jumpers.
The independent verification of a control circuit alteration could be satisfied by a variety of arrangements dependent on the availability of suitably qualified resources. At a minimum level, independent verification would require the wiring installation work undertaken by one rail safety worker to be verified (inspected and certified) as correct by another rail safety worker, who held an equivalent or higher competency and was not directly involved with the initial wiring installation work.
For the work at Torrens Road (and other level crossing installations affected by the GREP work) the qualified resources of the signal team comprised 2 rail safety workers, the signal electrician and TIC. To satisfy the minimum level of independence would typically require the signal electrician to have access to a circuit diagram (construction copy) to carry out and record the installation or removal of each jumper independently from involvement of the TIC. On completion, the TIC, referencing the ITP documentation would then verify and certify the correct installation of the jumpers independently from involvement of the signal electrician.
The methodology adopted by the TIC during the installation of the wiring, where they retained the circuit diagram and called the termination node to the signal electrician before marking the respective wire as installed, essentially combined the installation and verification tasks into a single step. Consequently, there was no independent verification of the installed wiring. This resulted in the wiring error not being detected and remaining in the circuit as a latent condition.
The approach adopted by the signal team was likely influenced by the close working association it had established through the repeated implementation of the ITPs to alter the level crossing control circuits, as well as the completion of other tasks undertaken to facilitate the tack tamping works. The signal electrician and TIC repeatedly completed these specialised works successfully under time pressure over a number of preceding days and likely developed a level of trust in each other’s ability to competently complete the alteration work without error or omission.
The Rail Industry Safety and Standards Board standard required the planning and implementation of an effective inspection and test regime to reduce risk to rail safety. To achieve this, the standard required the verification and validation process that forms the inspection and test regime to be undertaken with independence between the construction (installation) and testing (commissioning) process. The standard, however, allowed for situations where the independence could not be achieved. In that instance, other controls should be considered and approved by the rail infrastructure manager to control the additional risk.
Contributing factor
The methodology adopted by the signal team when implementing the Torrens Road inspection and test plan did not ensure independence between the installation and verification tasks. This resulted in the wiring error not being corrected and remaining in the Torrens Road control circuit, potentially affecting the correct operation of the level crossing warning equipment.
Tamping preparation works
After completion of the temporary wiring alterations, the TIC and signal electrician concluded the jumpers were installed correctly and that the warning equipment would continue to function as intended. The signal team then left the Torrens Road level crossing. Following approval from the TIC, the signal electrician and trades assistants then commenced work to remove the required track circuit electrical connections from the rails so the track work could continue.
The removal of the track connections should have had no effect on the correct operation of the Torrens Road level crossing warning equipment. That is, the altered level crossing control circuit would not operate the warning equipment due to the removal of the track circuit connections on the AMPRN, but would still operate either by the use of the test switch or for the passage of a train on the adjacent ARTC network.
In this instance, due to the earlier undetected error in the installation of one of the jumpers, the removal of the track circuit connections for the 572C track resulted in a change of state of the 572C T1P function in the level crossing control circuit. This condition, together with the wiring error, resulted in a wiring connection that provided alternative connection from the control circuit power supply to the 47 XSR control relay. This now prevented the correct operation of the level crossing control circuit and warning equipment.
This condition was not present at the time the TIC and signal electrician tested (validated) the correct operation of the level crossing warning equipment by using the level crossing test switch. Therefore, the TIC and signal electrician, having left the Torrens Road level crossing after completing the installation and test tasks, would not have been aware the level crossing would now not operate either by the selection of the test switch or the passage of a train on the adjacent ARTC network.
As the alternative connection condition was not present during the time the TIC undertook the validation testing, the detection and correction of the wiring error was therefore solely reliant on the effectiveness of the verification testing that was undertaken following the installation of the temporary jumper wiring.
Other factor that increased risk
The inspection and test methodology used by the signal team to validate the operation of the level crossing warning equipment via the operation of the Adelaide Metropolitan Passenger Rail Network level crossing test switch did not prove the Australian Rail Track Corporation level crossing control function would operate the warning equipment.
Inspection and test plan – testing
For the GREP level crossing works, Rail Industry Constructions (RIC) developed a package of ITP documents through copying the format of ITPs that RIC had used for projects previously undertaken on the AMPRN signalling system. Other than stipulating the ITPs were to be submitted for approval, SAPTA provided no specification or guidance to define the minimum content that RIC was to follow during the drafting and later application of the ITP documents.
The ITPs subsequently developed by RIC reflected the content of various pre-populated fields that described generalised tasks to confirm details of plan references, responsibilities and authorities, safe working, and communication arrangements. A sequence of tasks was added to the master test certificate section that reflected information contained in the circuit diagrams for the temporary jumper wiring installation or removal tasks. RIC only specified a test of the signalling system integrity (by operation of the test switch) would occur after the removal of the jumpers.
The RISSB signalling testing process standards described the types of testing and methods for testing typical signalling apparatus and systems that form part of a signalling system. A key objective of a test activity was to provide assurance the new or altered signalling system conformed with defined functional requirements, such as maintaining the operation of level crossing warning equipment for trains operating on the ARTC network. The ITP provided a template to document the equipment to be altered, and the planned sequence of tasks including an effective auditable process for the verification and validation of the safety integrity of the altered signalling system to meet the defined functional requirements.
The ITPs subsequently developed by RIC for the GREP level crossing control circuit alterations were tailored toward a checklist addressing administrative tasks. Therefore, the ITPs did not include sufficient detail to form an effective and auditable test procedure to verify and validate the safety integrity of level crossing control circuits following the installation of the temporary jumper wiring.
Other factor that increased risk
Rail Industry Constructions developed a package of inspection and test plans that did not include effective and auditable test procedures to verify and validate the safety integrity of level crossing control circuits following the installation of the temporary jumper wiring.
Inspection and test plan checking/approval process – testing
On 25 September 2020, RIC representatives endorsed the draft ITPs for each level crossing location that would be affected by the GREP track tamping work. The ITPs were subsequently submitted to SAPTA for review and approval to verify that the specifications contained in the ITPs were appropriate for application on the AMPRN.
The review identified errors in several of the ITPs, which SAPTA returned to RIC for correction. The errors related to an inconsistency between the task description in the plan document and the related marked up circuit diagram. SAPTA identified no errors in the positioning of the various temporary jumper wires as marked-up on the control circuit diagrams.
In reviewing the proposed wiring alterations, SAPTA did not provide any feedback to RIC on the inclusion of the superfluous jumpers to inhibit control functions that were not necessary to achieve the objective. That is, to prevent the unnecessary operation of the level crossing warning equipment during the track work. The SAPTA acceptance of the extra wiring alterations both unnecessarily increased the workload on the signal team and introduced a potential risk to safety that may arise from an undetected error during the installation works.
A SAPTA‑qualified employee undertaking similar works must undertake the planned temporary decommissioning of signalling system infrastructure in accordance with the SAPTA work instruction Signalling system temporary decommissioning and jumpering. The instruction required the qualified employee implement a pre-approved ITP for the works. The work instruction emphasised to the SAPTA‑qualified employee their responsibility to ensure there was independence in the verification testing of the installed wiring. Additionally, where there were adjacent rail lines, the employee was to validate the correct operation of the signalling functions on that line to ensure they remained active following the completion of the alteration work. In this instance, the level crossing control functions were isolated for AMPRN but were to continue operating for trains on the adjacent ARTC network.
A key objective of the SAPTA review and approval process was to ensure the ITP procedures developed by subcontractors (RIC) for implementation by the signal team on the AMPRN were, at a minimum, consistent with SAPTA procedures and/or included methods that provided improved risk control. The SAPTA review did not identify the omission of specific inspection and test tasks to ensure there was independent verification that the jumpering was correctly installed, and that the ARTC control function to operate the level crossing warning equipment for a train approaching on the ARTC network was validated. Consequently, the effectiveness of the tests to control risk and assure the safety integrity of the rail infrastructure for trains operating on the ARTC network relied solely on the methodology adopted by a subcontracted signal team on the day.
Other factor that increased risk
The South Australian Passenger Transport Authority approved a package of inspection and test plan procedures that did not specify any requirement for testing to verify and validate the safety integrity of the altered level crossing control circuits. The effectiveness of inspection and test plan process to control risk and provide assurance the signalling system functioned safety for trains operating on the Australian Rail Track Corporation network relied solely on the methodology adopted by the subcontracted signal team. (Safety issue)
Validation of signalling works
The Rail Industry Safety and Standards Board standard for signal testing processes required the TIC to complete tests to verify the installed wiring alteration conformed to the control circuit diagrams and then confirm that the requirements of the alteration were fulfilled. In this instance, the requirements, although not specified in the ITP, were the correct operation of the level crossing warning equipment via the manual operation of the AMPRN test switch and the automatic operation for a train approaching the Torrens Road level crossing on the ARTC network.
The TIC stated that, on completion of the jumper installation, they did validate the correct operation of the level crossing warning equipment via the manual operation of the AMPRN test switch. Although the level crossing warning equipment did function as the TIC expected, this was not an effective inspection and test method to prove the ARTC approach control function would operate the warning equipment. While the test proved the AMPRN test switch function operated the level crossing warning equipment it did not prove the ARTC control function would similarly operate the warning equipment.
To prove the ARTC control function required the TIC to manually select the ARTC test switch (located on a separate ARTC location case) or interrupt by other means the ARTC approach control function relayed from the ARTC to the AMPRN signalling system. The validation testing conducted in this manner by the TIC would, in this instance, not identify the incorrect installation of the jumper unless a further condition related to the 572C T1P function was present at the time the validation testing occurred.
Other finding
The later disconnection of electrical connections to the rails on the Adelaide metropolitan passenger rail network caused a false feed to the level crossing control relay via the incorrectly installed temporary jumper wire. This false feed prevented the correct operation of the level crossing warning equipment for a train approaching on the Australian Rail Track Corporation network.
Findings
ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition ‘other findings’ may be included to provide important information about topics other than safety factors.
Safety issues are highlighted in bold to emphasise their importance. A safety issue is a safety factor that (a) can reasonably be regarded as having the potential to adversely affect the safety of future operations, and (b) is a characteristic of an organisation or a system, rather than a characteristic of a specific individual, or characteristic of an operating environment at a specific point in time.
These findings should not be read as apportioning blame or liability to any particular organisation or individual.
From the evidence available, the following findings are made with respect to the level crossing irregularity involving freight train 1MP9 that occurred on 7 December 2020 at Torrens Road level crossing, Ovingham, South Australia.
Contributing factors
A late change to the planned scope of track tamping work on the day of the incident placed additional work demand with short notice on the signal team to implement the Torrens Road inspection and test plan.
The inspection and test plan for the Torrens Road level crossing control circuit included 2 superfluous temporary jumper wires. The inclusion of superfluous wiring both increased complexity of the task and placed unnecessary work demand on the signal electrician and tester in charge to implement the plan.
The signal electrician inadvertently installed one end of a superfluous temporary jumper wire to an incorrect terminal within the control circuit of the Torrens Road level crossing warning equipment. The installation error meant the jumper was not consistent with the approved control circuit.
The methodology adopted by the signal team when implementing the Torrens Road inspection and test plan did not ensure independence between the installation and verification tasks. This resulted in the wiring error not being corrected and remaining in the Torrens Road control circuit, potentially affecting the correct operation of the level crossing warning equipment.
Other factors that increased risk
The inspection and test methodology used by the signal team to validate the operation of the level crossing warning equipment via the operation of the Adelaide Metropolitan Passenger Rail Network level crossing test switch did not prove the Australian Rail Track Corporation level crossing control function would operate the warning equipment.
Rail Industry Constructions developed a package of inspection and test plans that did not include effective and auditable test procedures to verify and validate the safety integrity of level crossing control circuits following the installation of the temporary jumper wiring.
The South Australian Passenger Transport Authority approved a package of inspection and test plan procedures that did not specify any requirement for testing to verify and validate the safety integrity of the altered level crossing control circuits. The effectiveness of inspection and test plan process to control risk and provide assurance the signalling system functioned safety for trains operating on the Australian Rail Track Corporation network relied solely on the methodology adopted by the subcontracted signal team. (Safety issue)
Other findings
The later disconnection of electrical connections to the rails on the Adelaide metropolitan passenger rail network caused a false feed to the level crossing control relay via the incorrectly installed temporary jumper wire. This false feed prevented the correct operation of the level crossing warning equipment for a train approaching on the Australian Rail Track Corporation network.
Safety issues and actions
Central to the ATSB’s investigation of transport safety matters is the early identification of safety issues. The ATSB expects relevant organisations will address all safety issues an investigation identifies.
Depending on the level of risk of a safety issue, the extent of corrective action taken by the relevant organisation(s), or the desirability of directing a broad safety message to the rail industry, the ATSB may issue a formal safety recommendation or safety advisory notice as part of the final report.
All of the directly involved parties were provided with a draft report and invited to provide submissions. As part of that process, each organisation was asked to communicate what safety actions, if any, they had carried out or were planning to carry out in relation to each safety issue relevant to their organisation.
Descriptions of each safety issue, and any associated safety recommendations, are detailed below. Click the link to read the full safety issue description, including the issue status and any safety action/s taken. Safety issues and actions are updated on this website when safety issue owners provide further information concerning the implementation of safety action.
Inspection and test plan checking/approval process - testing
Safety issue description: The South Australian Passenger Transport Authority approved a package of inspection and test plan procedures that did not specify any requirement for tests to verify and validate the safety integrity of the altered level crossing control circuits. The effectiveness of inspection and test plan procedure to control risk and provide assurance the signalling system functioned safety for trains operating on the ARTC network relied solely on the methodology adopted by the subcontracted signal team on the day.
Safety action not associated with an identified safety issue
Whether or not the ATSB identifies safety issues in the course of an investigation, relevant organisations may proactively initiate safety action in order to reduce their safety risk. The ATSB has been advised of the following proactive safety action in response to this occurrence.
Additional safety action by Acciona
Following the incident, Acciona undertook corrective action to:
Update the methodology to increase the level of controls for the activity. This may include additional function testing and road closures when jumpering-out was required for tamping/regulating.
Investigate the modification of level crossing control circuits to allow isolation of the level crossing without the installation of temporary jumper wiring. This action was considered a long-term solution to be considered by the South Australian Department for Infrastructure and Transport.
A complete risk assessment has been undertaken in consultation with Omada Rail Systems and the project team. The controls that came out from the risk assessment have been discussed with both Australian Rail Track Corporation and South Australian Department of Infrastructure - Transport project delivery in formal meetings and have been accepted by them.
Additional safety action by the Office of the National Rail Safety Regulator
On 16 December 2020, the Office of the National Rail Safety Regulator (ONRSR) published a Notice to Rail Transport Operators - Safety alert RSA-2020-001 in relation to several incidents of non-operation of level crossings on live lines due to incorrect isolation.
Each identified case (including Torrens Road) involved level crossings with multiple lines with more than one rail infrastructure manager and required the partial isolation of the crossing for some lines while leaving adjacent lines operational. However, the crossings were mistakenly isolated for the operational lines and workers were unaware of the mistake until the passage of trains through the unprotected crossing. ONRSR noted there was a significant risk to rail safety and reminded rail transport operators to ensure the completion of the key tasks outlined in the alert.
Additional safety action by the Australian Rail Track Corporation:
The ARTC undertook the following safety action related to several ARTC engineering standards in response to the level crossing incident at Torrens Road:
1) Reviewed and updated standard ESC-21-01 – Inspection and Testing of Signalling – Roles, Responsibilities and Authorities (Updated and published Sep 2021)
Clarified the roles and responsibilities for inspection and testing including TIC (Tester in Charge) responsibilities for shared level crossings.
2) Reviewed and updated standard ESM-24-01 - Bridging and false feeding signalling circuits. (Updated and published in Nov 2021)
Reviewed and updated requirements for bridging and false feeding signalling circuits and included a separate section for bridging on the shared level crossings
3) Reviewed and updated standard ESD-03-01 Level Crossing Design (Updated and published in Oct 2022)
Aligned with AS Standard AS7658 and guidance for shared level crossings.
Glossary
AMPRN
Adelaide metropolitan passenger rail network. Comprised 132 km of broad-gauge railway track between Seaford, Gawler, Outer Harbor, Belair, Grange and Tonsley.
ARA
Australasian Railway Association
ARTC
Australian Rail Track Corporation
CWMS
Construction work method statement
GREP
Gawler rail electrification project
IBA
Infrastructure booking advice
ITP
Inspection and test plan
KDA
Keolis Downer Adelaide
NAA
Network access application
NCO
ARTC network control officer
ONRSR
The Office of the National Rail Safety Regulator
PPO
Possession protection officer
RComm
Rail Commissioner, A body corporate established under the South Australia Rail Commissioner Act 2009
RIC
Rail Industry Constructions
RIM
Rail infrastructure manager
RSMP
Rail safety management plan
RSNL
Rail safety national law
RISSB
Rail Industry Safety and Standards Board
RTO
Rail transport operator
SAPTA
South Australian Public Transport Authority
SOC
Statement of competency
SWMS
Safe work method statement
TIC
Tester in charge
TPD
South Australian Department of Infrastructure - Transport project delivery
Sources and submissions
Sources of information
The sources of information during the investigation included:
South Australian Public Transport Authority
Acciona
Australian Rail Track Corporation
SCT Logistics
Rail Industry Constructions
the train crew
the tester in charge and signal electrician
recorded data from 1MP9.
References
Battelle Memorial Institute. (1998). An overview of the scientific literature concerning fatigue, sleep, and the circadian cycle. Report prepared for the Office of the Chief Scientific and Technical Advisor for Human Factors, United States Federal Aviation Administration.
Clarke, S. (1999). Perceptions of organizational safety: implications of the development of safety culture. Journal of Organizational Behaviour, 20, 185-198.
Staal, M.A. (2004). Stress, cognition, and human performance: a literature review and conceptual framework. Moffett Field: The National Aeronautics and Space Administration.
Submissions
Under section 26 of the Transport Safety Investigation Act 2003, the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. That section allows a person receiving a draft report to make submissions to the ATSB about the draft report.
A draft of this report was provided to the following directly involved parties:
Acciona
Australian Rail Track Corporation
South Australian Public Transport Authority
Office of the National Rail Safety Regulator
Rail Industry Constructions
SCT Logistics
the signal team
the train crew.
Submissions were received from:
Acciona
Australian Rail Track Corporation
South Australian Public Transport Authority
Office of the National Rail Safety Regulator.
Appendices
Appendix A – GREP safety management system procedures
Acciona competency management program
The Acciona procedure LLE1002 Attachment 2 – Training of rail workers required all employees and subcontractors accessing the Adelaide metropolitan passenger rail network (AMPRN) rail corridor to have a basic level of competency, such as track safety awareness. Acciona managed this competency together with other task‑related competencies, such as safe working and track vehicle operation through the requirements of the contractor and rail industry worker cards.
For specialist engineering competencies, such as those associated with signal installation and testing, the Acciona procedure allowed the recognition of another accredited rail operator’s statement of competency (SOC) as evidence the worker was competent. This recognition was dependent on whether the details of the engineering work undertaken were related to the required Gawler rail electrification project (GREP) tasks, and if the SOC was still current.
GREP signalling team statement of competency
Acciona recognised the Australian Rail Track Corporation (ARTC) SOC and associated work experience log as evidence of the competencies attained by the tester in charge (TIC) and signal electrician. The respective SOCs detailed their current employer, work role, ARTC certified competencies, health assessment status and the inductions completed. Each SOC was current, with an expiry date of May 2024 and December 2022 for the TIC and signal electrician respectively.
The SOCs specifically related to ARTC’s assessment of their competence and compliance with the ARTC network standards, procedures, practices and instructions when undertaking related rail safety work on that organisation’s network. ARTC stipulated that the SOC assessment was not transferrable for use on another rail network without further review and assessment by the rail transport operator (RTO) responsible for that network, in this instance the RComm.
The SOC document included a requirement for the individual to maintain a work experience log in accordance with the ARTC competency standards, and to make that record available for any future competency review. The work experience log was a critical element in ARTC establishing the ongoing experience of signalling staff through demonstration that the person had moved from the training level to a level that permitted the independent performance of signalling tasks. The log recorded details in chronological order of the various projects undertaken, timeframes, the specific tasks performed, equipment types worked on and the supervisor’s assessments of the individual’s performance in undertaking that work.
The log for the TIC recorded a range of projects undertaken on various rail networks throughout Australia including the AMPRN. Project entries recorded the TIC had worked on AMPRN projects since October 2010. The work typically involved coordination of the installation, testing and commissioning of modifications to signalling control circuity and interlocking systems. The Rail Industry Constructions (RIC) supervisor’s observations of the TIC’s work level standard performing those tasks was recorded as excellent, completed on time and to schedule, and that all documentation was completed to the applicable standards.
The latest project entry for the TIC undertaking signalling work on the AMPRN was the performance of signal support activities during September and November 2020 for track tamping works in the Adelaide yard area. There was no entry against this project recording the supervisor’s observation of the TIC’s work level standard.
The log for the signal electrician similarly recorded a range of projects undertaken on the ARTC and AMPRN networks. Project entries recorded the signal electrician had worked on AMPRN projects since September 2016. The latest project entry for the signal electrician undertaking work on the AMPRN was December 2020 during which the signal electrician undertook the following project tasks associated with the GREP level crossing works:
analysis of designed plans
bridge [jumper] out level crossings
removing track leads and install
certifying track circuits.
The RIC supervisor’s observation of the signal electricians work level standard for those tasks was recorded as excellent, completed on time and to schedule.
Both the TIC and signal electrician’s SOCs included the caveat the assessment was not transferrable to another rail network without further review and assessment by the RTO responsible for that network. Although there was no evidence provided of any review or assessment by RComm, SAPTA or South Australian Department of Infrastructure – Transport project delivery (TPD) prior to the commencement of the GREP works, the work experience logs contained evidence the TIC and signal electrician were assessed as having competently undertaken similar installation and testing tasks for other projects on the AMPRN signalling system.
The SAPTA internal investigation report into the incident at Torrens Road on 7 December 2020 identified that between July 2017 and January 2020, 3 incidents occurred involving the RIC rail safety workers (TIC and signal electrician) when undertaking signalling project works. The report noted that as a result, SAPTA notified RIC that the competencies held by the workers enabling them to work on the AMPRN were to be suspended, pending re-assessment by SAPTA.
The SAPTA report further noted there was no evidence of a formal response from RIC to the notification or that information of the suspension was communicated by SAPTA to TPD, as the project manager for the GREP. At the date of the Torrens Road incident, the RIC staff involved were not listed in the SAPTA/TPD signalling engineering statement of competency folder and had not completed the competency re-assessment process to permit work on the AMPRN, as SAPTA had required.
The competency status for the RIC rail safety workers was inconsistent between Acciona (assessed as competent) and the SAPTA (requiring re-assessment). The ATSB noted the work experience records available to Acciona indicated the signal electrician and TIC were assessed to have competently undertaken project work including similar installation and testing tasks on the AMPRN signalling infrastructure between July 2017 and January 2020. The records contained no notation related to the incidents identified in the SAPTA investigation report.
Acciona health and fitness management program
The Acciona Alliance work health and safety management plan referred to the National Standard for Health Assessment of Rail Safety Workers as a key guideline relevant to the management of worker health and safety during construction activity. The standard set out the health assessment criteria, including the frequency applicable to rail safety workers in each of the 4 defined categories. The 4 categories were based on the level of risk associated with the rail safety workers role. Categories 1 and 2 applied to safety critical work/workers and categories 3 and 4 to non-safety critical work/workers.
The Acciona Rail safety management plan - Rail operations management plan and LLE1001 Attachment 3, Medical standards and rail safety workers specified Acciona rail safety workers were to hold a health assessment category that was dependent on the role/task that worker was to perform. Acciona additionally required all workers to hold an Australasian Railway Association (ARA) rail industry worker card. The ARA rail industry worker card held rail compliance information related to the individual worker, including health assessment category held.
The ARA process required the rail industry worker’s employer to maintain the worker’s details, job roles, competencies, and health assessment information within the ARA system. This information was then available for a project administrator to access and assess against the criteria for the role the rail industry worker was to undertake for that project.
For the GREP, the card provided Acciona project administration a source of information to verify the worker’s suitability for the intended role. The Acciona procedure for subcontractors specified the health category required for each rail safety worker role for the GREP (Table 1). The table did not include the roles of TIC, signal electrician or trade assistant that were performed by the subcontracted RIC rail safety workers. The absence of a specific rail safety worker role for the TIC and signal electrician indicated they were assessed as a construction worker, requiring a Category 3 health assessment to undertake rail safety work on the signalling system.
Table 1: GREP Rail industry worker health requirements
Rail safety worker role
Health assessment category
Track vehicle operator, including linesman
Protection officers
Track machine operator
Road rail vehicle operator
Category 1
Plant operators (excavator, backhoe, crane, elevated work platform)
Category 2
Construction worker
Track labourer
Category 3
Rail Commissioner health and fitness management program
The RComm procedures used a rail safety worker checklist to determine the health assessment category applicable to a SAPTA rail safety worker who undertook work on the AMPRN infrastructure or rolling stock. The checklist determined firstly if the work activities were rail safety work and secondly defined the minimum health assessment category level applicable to that rail safety worker.
The RComm assessment for the position of signal maintenance fitter (signal electrician) undertaking work on rail infrastructure identified the following work activities:
Signalling (and signalling operations), receiving or relaying communications or any other activity which is capable of controlling or affecting the movement of rolling stock.
Maintaining, repairing, modifying, monitoring, inspecting or testing – rolling stock or rail infrastructure.
Work on or about rail infrastructure in relation to the design, construction, repair, modification maintenance, monitoring, upgrading, inspection or testing of rail infrastructure or associated works or equipment, including checking that the rail infrastructure is working properly before being used (excluding persons engaged in office-based design work).
Installation or maintenance of – telecommunications system relating to or used in connection with rail infrastructure or the means of supplying electricity directly to rail infrastructure or to any rolling stock using rail infrastructure or to telecommunications systems.
Work involving certification as to the safety of rail infrastructure or rolling stock or any part of a component of rail infrastructure or rolling stock.
Work involving the development, management or monitoring of safe working systems for railways.
Undertaking any of the above work activities identified the signal maintenance fitter (signal electrician) as a rail safety worker.
The second stage of the assessment applied a series of tests to determine if the worker was a safety‑critical worker and the category of health assessment applicable (Figure 15). The RComm assessment identified the position of signal maintenance fitter as a safety‑critical worker who required a category 1 health assessment.
The activities undertaken by the TIC were generally the same as those of the signal maintenance fitter described above. SAPTA did not have a rail safety worker checklist specifically for the position of TIC and advised it assessed all rail safety workers under training work on the AMPRN signalling infrastructure as safety critical workers, requiring a category 1 health assessment.
Figure 15: Rail safety worker health category assessment flowchart
Source: Rail Commissioner
Acciona/RIC signalling team health assessments
Although the required health assessment category for the project role of TIC or signal electrician was not specified in Acciona procedures, the signal electrician held a current health assessment for a rail safety worker category 1 (safety‑critical worker) with no restrictions and the TIC had held a rail safety worker category 3 (non-safety‑critical worker) assessment with no restrictions.
However, the category 3 assessment for the TIC expired on 31 August 2020, around 3 months prior to the incident at Torrens Road. The TIC later advised the ATSB they had renewed their category 3 health assessment on 5 February 2021, with no restrictions.
The work on the AMPRN signalling system undertaken by the TIC and signal electrician as part of the GREP works was safety‑critical work and if undertaken by a RComm/SAPTA rail safety worker would require a category 1 health assessment for both the TIC and signal electrician. There was no evidence that the RComm, SAPTA or TPD reviewed the suitability of the health assessments of the RIC rail safety workers (particularly the TIC), as applied by Acciona for the GREP works, to determine if the RComm requirements/expectation for rail safety workers undertaking safety‑critical work on the AMRRN were satisfied.
Fatigue risk management program
Fatigue can have a range of influences on performance, such as decreased short-term memory, slowed reaction time, decreased work efficiency, reduced motivational drive, increased variability in work performance, and increased errors of omission (Battelle Memorial Institute, 1998). Due to these negative effects on cognitive performance, fatigue is a factor that increases the risk of transport accidents.
The Acciona procedure LLE617 Fitness health and hygiene described the process for managing fatigue and mental health. The procedure applied to direct employees and subcontractors. The procedure involved establishing project rules for the hours of work, arrangements for providing suitable welfare facilities, and the identification and risk assessment of tasks where fatigue could lead to mistakes that could result in the fatal injury of any person. Controls to manage fatigue related risk were then included in the safe work method statement for the associated task.
The Acciona project rules stipulated the maximum hours of work must not exceed the normal shift hours of 10–12 hours maximum per day, up to a cumulative total of 60 hours per week. The procedure allowed for working extended hours in situations where the type of work, track possession length or other circumstances, such as emergency works may arise. In such cases the requirement to work extended hours was to be approved and the guidelines described in the procedure applied to manage the hours worked.
RIC signal team
The signal team’s work hours were not determined from a set roster pattern but were governed by the requirements of the project’s daily schedule or the progress of a particular task on that day. The team typically commenced work onsite at around 0600 and worked to the completion of the tasks commenced that day.
In the week prior to the incident, the TIC and signal electrician recorded workdays of between 8.5 and 12 hours each day undertaking the signalling alterations to facilitate the track tamping works (Table 2). On one occasion, the signal electrician exceeded the 12-hour daily limit by 30 minutes. The reason for this or whether approval was sought/granted to work the extra time could not be established.
Table 2: Signal team hours of work
Date
Tester in charge (hours include a 30-minute lunch break)
Signal electrician (hours include a 30-minute lunch break)
23 November 2020
Leave
Leave
24 November 2020
0730 – 1630, 9 hours
0700 – 1700, 10 hours
25 November 2020
0700 – 1630, 9.5 hours
0700 – 1730, 10.5 hours
26 November 2020
0700 – 1530, 8.5 hours
0700 – 1600, 9 hours
27 November 2020
0700 – 1530, 8.5 hours
0700 – 1600, 9 hours
28 November 2020
0700 – 1530, 8.5 hours
0600 – 1430, 8.5 hours
29 November 2020
0700 – 1530, 8.5 hours
0700 – 1530, 8.5 hours
30 November 2020
0700 – 1530, 8.5 hours
0700 – 1630, 9.5 hours
1 December 2020
Leave
0700 – 1700, 10 hours
2 December 2020
0600 – 1800, 12 hours
0600 – 1830, 12.5 hours
3 December 2020
0600 – 1930, 11.5 hours[1]
0600 – 1930, 11.5 hours[1]
4 December 2020
0600 – 1800, 12 hours
0600 – 1800, 12 hours
5 December 2020
0600 – 1730, 11.5 hours
OFF
6 December 2020
4 hours
OFF
7 December 2020
0600 – 1800, 12 hours
0600 – 1830, 12.5 hours
Although start and finish times reflect a duration of 11.5 hours, total hours were recorded in the respective timesheets as 13 hours.
The signal electrician had worked 11 days consecutively before taking the 2 days off over the weekend prior to the incident. On commencing work on the day of the incident, the signal electrician self-rated their fatigue level as 4 out of 7 (a little tired, and not at their peak).[30] The signal electrician felt that they tended to be like that after a while on the big jobs.
The TIC had worked on each of 5 days prior to the incident. On 6 December 2020, the TIC undertook office-based work preparing plans and tools required for the coming week’s work. The TIC recalled obtaining poor sleep quality over the 3 nights of the weekend prior to the incident. On commencing work on the day of the incident, the TIC self-rated their fatigue level as 3 out of 7 (Okay, somewhat fresh).
Both the TIC and signal electrician stated they were aware of the need to individually manage fatigue levels, but also felt obliged to work toward meeting the project targets. Neither the TIC nor signal electrician had been provided with site‑specific training in the policies or procedures related to the management of fatigue during the GREP works.
Appendix B – Contracting in the rail industry
ONRSR guidelines
The Office of the National Rail Safety Regulator (ONRSR) published a range of fact sheets, guidelines and policies to provide the rail industry with key information on specific rail safety issues and legislative, regulatory and technical matters associated with the administration by ONRSR. These documents included information to duty holders about their duties and related obligations under the Rail Safety National Law (RSNL) when undertaking major projects involving contractor management.
The fact sheet General safety duties under the Rail Safety National Law – ‘upstream’ duty holders emphasised the RSNL embedded the principles of shared responsibility across a range of entities, including rail transport operators, rail safety workers and other persons such as designers, manufacturers and suppliers. ONRSR categorised some entities as ‘upstream’ as there would be greater scope for those entities to remove foreseeable hazards than a ‘downstream’ duty holder.
ONRSR noted upstream duty holders generally did not require accreditation for the activities they undertook. However, they still had a responsibility (general safety duty) to ensure they undertook their activities safely and in a way that did not affect the safety of the railway operations, themselves or others. The level and nature of the responsibility was dependent on the nature of the risks, and the capacity of the duty holder to control, eliminate or mitigate those risks.
RISSB guideline contracting in the rail industry
To supplement the ONRSR publications the Rail Industry Safety and Standards Board published the Accreditation and safety management systems guideline – contracting in the rail industry. The purpose of the guideline was to assist rail transport operators in understanding their responsibilities under the RSNL for engaging contractors to carry out rail operations and for contractors to gain an understanding of what is expected of them when they were engaged to carry out rail operations and specific rail safety work.
The guideline reflected the RSNL and ONRSR fact sheet in highlighting the principle of shared responsibility and accountability (general safety duty) to effectively manage rail safety when engaged in rail safety work, such as the design, commissioning or modification of rail infrastructure.
The guideline also noted the RSNL takes the principle of shared responsibility and strengthens its application by prescribing that:
a duty under this Law cannot be transferred to another person
a person can have more than one duty under this Law by being in more than one class of duty holder
more than one person can concurrently have the same duty under this Law and each duty holder must comply with that duty to the standard required by this Law even if another duty holder has the same duty.
GREP arrangements
The South Australian Department for Infrastructure and Transport (DIT) encompassed the Rail Commissioner (RComm), the South Australian Passenger Transport Authority (SAPTA) and Transport project delivery (TPD). The RComm was the accredited rail infrastructure manager and rolling stock operator for the AMPRN. SAPTA managed the provision of passenger rolling stock operations and maintenance, train control functions and railway infrastructure maintenance under the RComm accreditation. The TPD, with a degree of involvement by SAPTA, managed the delivery of projects for the AMPRN, also under the RComm accreditation.
The TPD was the contract principal for the GREP that was undertaken by principal contractor Acciona in accordance with the Gawler rail electrification project alliance rail safety management plan (RSMP). The RSMP detailed how the alliance would meet the accreditation requirements of the RComm and general safety duties under the RSNL:
The purpose of the Rail Safety Management Plan is to describe the approach the Alliance will take (with the Constructor NOP [Acciona] being the Principal contractor), with WSP and Siemens [subcontractors] to manage the Gawler Rail Electrification Project Alliance. This Rail Safety Management Plan is focused on how the Project will comply with the safety requirements when carrying out railway activities, including survey, design, construction, commissioning, use, inspection, installation, modification, maintenance, repair, cleaning, decommissioning of rail infrastructure and the operation of rollingstock on the Adelaide Metropolitan Passenger Rail Network (AMPRN).
The Rail Safety Management Plan identifies how the Alliance delivery will meet the Rail Commissioner’s Rail Accreditation Requirements as a Rail Transport Operator. This is essential in order that the Rail Commissioner can fulfil its obligations under Rail Safety National Law and Regulations. The Principal will be relying upon the professed expertise of the Constructor NOP in Rail Safety to fulfil the Rail Commissioner’s obligations pursuant to the Rail Safety National Law.
The RSMP later detailed the arrangements for rail safety management:
In all cases the Rail Commissioner’s accreditation systems and processes will apply unless granted a waiver by the Rail Commissioner’s representative/s. The Rail Commissioner’s engineering standards, for the most part, reflect Australian Standards and Rail Industry Safety Standards Board (RISSB) documentation. As a contractor working under the Rail Commissioner’s accreditation, the Alliance will construct and carry out activities and reporting to the higher level whilst ensuring the Rail Commissioner’s accreditation is met.
The SAPTA final investigation report found that TPD and Acciona did not:
…have effective processes in place to provide assurance that the rail safety obligations of the Rail Commissioner's accreditation were being met by contractors and sub-contractors.
The statements in the alliance RSMP, SAPTA investigation and ONRSR fact sheet imply the RComm was a ‘downstream’ duty holder. The remaining entities, SAPTA, TPD, Acciona, RIC and the rail safety workers of the signal maintenance team were then upstream duty holders sharing responsibility for the rail safety duties associated with the development of safety management system procedures, work instructions and plans and approval processes to manage the specialised rail safety work required to alter the level crossings (including Torrens Road) as part of the GREP works.
Appendix C – Torrens Road inspection and test plan
Source: South Australian Public Transport Authority, image modified by the ATSB to deidentify signatories
Source: South Australian Passenger Transport Authority
Source: South Australian Passenger Transport Authority
Source: South Australian Passenger Transport Authority
Source: South Australian Passenger Transport Authority
Source: South Australian Passenger Transport Authority
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Commonwealth Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this report is licensed under a Creative Commons Attribution 4.0 International licence.
The CC BY 4.0 licence enables you to distribute, remix, adapt, and build upon our material in any medium or format, so long as attribution is given to the Australian Transport Safety Bureau.
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
[1]Acciona was the principal contractor for the railway infrastructure works.
[2]Work involved the operation of track tamping and ballast regulator machines to adjust the track alignment and reshape the ballast formation.
[3]Rolling stock movements on the up-rail line travel toward the Adelaide Railway Station.
[4]AMPRN track km marks measured from the 0 km mark at the Adelaide Railway Station.
[5]A competent worker who has carried out, is carrying out, or is about to carry out, rail safety work defined in the Rail Safety National Law.
[6]An electric circuit where current is carried through the rails and used to detect the presence of trains. Track circuits are used in the operation and control of points and signalling equipment.
[7]The IBA formally recorded that the AMPRN operations controller, or in this case the PPO in charge of the worksite, were notified and agreed to the modification of the nominated equipment prior to work being undertaken
[8]Control switch located in cabinet attached to the location case used primarily to operate the level crossing warning during maintenance work.
[9]ARTC track km marks at Torrens Road are measured from the 0 km mark at the Keswick rail passenger terminal.
[10]ARTC network control officer monitors do not display approach track circuit or level crossing status information for Hawker Street or Torrens Road level crossings.
[11]At the time of the incident, the Rail Commissioner was the accredited rail transport operator (rail infrastructure manager and rolling stock operator) for the AMPRN under the Rail Safety National Law (South Australia) Act 2012. See Organisational information section below detailing the contractual relationships associated with the GREP.
[12]Up direction toward Adelaide, down direction away from Adelaide and toward Gawler Central.
[13]Through the operation of a single line working function located within level crossing control circuit.
[14]This included the signal electrician who endorsed the review phase of the ITP approval process. The TIC was not involved in the production, review or approval phases of the ITP documentation.
[15]Errors were generally inconsistencies between the task description in the plan document and the marked-up circuit diagrams.
[16]Level crossings at Hawker Street, Pym Street and Park Terrace.
[17]SWMS RIC-031, Acciona – Signal support, Cable termination and Testing of signal infrastructure, version 3.
[18]A rail transport operator (RTO) can be a rail infrastructure manager (RIM) or a rolling stock operator (RSO) or a person who is both a RIM and RSO.
[19]In relation to the infrastructure of a railway, means the person who has effective management and control of the rail infrastructure.
[20]Rail-rail interface agreement, RComm and ARTC.
[21]The ARTC notice identified the GREP work area related to the Mile End to Crystal Brook route between the 3.8 km and 10.291 km marks on the ARTC network.
[22]Testing and evaluation of a product to assure compliance with its specification or other requirements.
[23]Confirmation that the particular requirements for a specific intended use are fulfilled.
[24]Control table: A part of the signalling system specification that defines the detail of the signalling controls for each signalling function.
[25]Aspect sequence testing verifies that only the correct aspect and route indication are displayed to the train driver.
[26]Principles testing shall be carried out to validate that the controls embodied in the system conform to signalling principles, performance specifications and site-specific operating requirements and the railway layout signalling plan.
[27]The inclusion of superfluous jumper wiring was common across all approved ITPs for the level crossing modification.
[28]Completion of a visual examination against the wiring diagram to confirm the termination contains the correct number of wires. Denoted on the circuit diagram by a small stroke across the wire next to the termination.
[29]Completion of examination for conductor continuity between wire termination points. Denoted by a small tick adjacent to the wire.
[30]The Samn-Perelli scale for self‑evaluating fatigue ranges from 1 (fully alert) to 7 (completely exhausted). A rating of 4 indicates ‘a little tired; less than fresh’.
At about 0825 (local time) on 4 December 2020, Pacific National (PN) freight train 3PM7 was passing through Werribee, about 32 km from Melbourne. The train was travelling from Perth (Western Australia) to Melbourne (Victoria) on the Australian Rail Track Corporation (ARTC) standard gauge network.
When the train approached the level crossing at Werribee Street, the crossing’s protection equipment did not operate. However, road traffic signals that were linked to rail systems did operate to stop road vehicles. The train continued through Werribee Station with its crew under the impression that road traffic at Werribee Street had been appropriately stopped.
The next level crossing encountered by train 3PM7 was at Cherry Street which was located about 940 m east of the Werribee Street level crossing. When the train approached the level crossing, the crossing’s protection equipment also did not operate, and the train’s crew observed road vehicles crossing ahead. In response, the crew made an emergency brake application and sounded the horn. The train entered the crossing travelling at approximately 48 km/h, with motor vehicles clearing the crossing less than 2 s before the train’s arrival.
What the ATSB found
The non-operation of the level crossing equipment occurred during signalling works associated with the removal of the level crossings at Werribee and Cherry Streets by the Western Program Alliance (WPA). Metro Trains Melbourne (MTM) was the accredited infrastructure manager for the level crossings and a member of WPA.
With a track occupation scheduled to run from 29 November to 7 December, the broad gauge lines were closed to rail traffic while signalling circuits were being rewired, tested and commissioned. During these broad gauge works, the standard gauge line was to continue to operate normally. To facilitate the operation of the 2 level crossings for the standard gauge traffic, required control circuits were isolated from broad gauge systems being modified.
It was found that the failure of the Werribee Street and Cherry Street level crossings was due to the isolation arrangements being disrupted. This occurred at about 0800 on the morning of the incident (4 December) when function testers replaced 2 fuses that had been disconnected as part of the isolation arrangement. The testers were not familiar with the isolation arrangement. Reinstatement of fuses was not unusual in their role of function testing completed circuits.
Relevant events prior to 4 December included:
The isolation design was changed on 27 November and involved the powering down of the Werribee relay room. The isolation arrangements also required the removal of 2 fuses and the installation of temporary (jumper) wires to facilitate a false power feed to the Werribee Street and Cherry Street crossing control circuits.
When installing the isolation arrangements on the night of 29–30 November, the fuses to be removed and secured were instead folded out with one end remaining in the fuse holder. This made the fuses vulnerable to reinstatement.
Power to the Werribee relay room was returned on 2 December with temporary jumper wires for the isolation retained. In this condition, reinstatement of the fuses would result in the level crossing circuits being energised and prevent operation of the level crossing equipment.
There were several safety factors identified with regard the late change to the isolation arrangements. Critically, the changed level crossing isolation arrangements were not reflected in planning and program documentation, nor effectively disseminated to all those potentially affected by the change. An earlier internal audit of this project also identified instances of scope changes not being documented.
The ATSB also found that:
Road traffic management was an available risk control that was not used for normal standard gauge rail traffic during testing.
There were opportunities for the updated isolation design to incorporate additional risk controls to reduce the likelihood of premature replacement of removed fuses.
Although approved by MTM, the isolation and reinstatement plans were not reviewed in accordance with MTM design approval processes.
Other identified safety issues requiring consideration are:
MTM standards and procedures did not specifically address requirements associated with fuse removal and securement in safety critical scenarios.
Contrary to the requirements of relevant standards and procedures, there was probably no independent check of the installed isolation arrangements. An earlier internal audit of this project also identified instances of testers in charge checking their own work.
What has been done as a result
The Western Program Alliance and Alliance member Metro Trains Melbourne (MTM) have taken several safety actions that should address identified safety issues in testing and commissioning practices and assurance. Safety actions include the update of assurance frameworks and associated procedures, and awareness initiatives.
As an active participant of Victoria’s Signalling Strategy Taskforce (SST), MTM is contributing to the development of consistent signalling practices and enhanced competency frameworks. The work of the SST has the potential to provide an industry-wide framework for, and contribute to, addressing safety issues like those identified in this investigation.
Safety message
This occurrence highlights the importance of considering the implications of late design changes, updating plans and programs, and ensuring all affected parties have a clear understanding of the implications for their work activities. This is particularly the case in complex projects that involve consortia, contractors, sub-contractors, and the responsible rail infrastructure manager.
The occurrence
Overview
At about 0825 (local time) on 4 December 2020, Pacific National freight train 3PM7 operating on the Australian Rail Track Corporation (ARTC) standard gauge network was travelling through Werribee towards Melbourne.[1] The train was to pass through level crossings at Werribee Street and Cherry Street which were located either side of Werribee Railway Station (Figure 1). For the passage of train 3PM7, the level crossing protection equipment at both Werribee and Cherry Street level crossings did not activate.
Figure 1: Location of Werribee Street and Cherry Street level crossings
Source: eWay Electronic Melway Street Directory – 2017 Edition, annotated by the Office Chief Investigator (OCI)
Events prior to the non-operation of level crossing protection
Level crossing removal
As part of the Level Crossing Removal Project (LXRP) for Melbourne, works had commenced to remove the Werribee and Cherry Street level crossings which serviced standard and broad gauge rail traffic.[2] The Werribee Street crossing was to be replaced with a rail flyover, and the Cherry Street level crossing was to be closed and a road overpass constructed to its east.
The LXRP in Werribee was being delivered by the Western Program Alliance (WPA) which included the network operator Metro Trains Melbourne (MTM). MTM was also the responsible rail infrastructure manager for the operation of the 2 level crossings. Several contractors and subcontractors were involved in signalling works associated with this removal project.
By November 2020, progress on infrastructure works meant that broad gauge tracks were only operational east of and up to Werribee Railway Station. This meant that only the standard gauge track was operational through the Werribee Street level crossing (west of the station) whereas both standard gauge and broad gauge tracks remained operational at Cherry Street.
Signalling works from 29 November 2020
Modification of the signalling systems at Werribee included extensive re-wiring of circuits in the Werribee relay room and their testing. The works, testing and commissioning were scheduled to take place from 29 November to 7 December. For this period, trains would not operate on the broad gauge lines,[3] while the single standard gauge track would remain operational. The level crossings at Werribee Street and Cherry Street were to remain operational for standard gauge rail traffic only.
The Testing and Commissioning Plan (TCP) for the 29 November to 7 December works was finalised as issued for construction (IFC) on 4 November. The TCP provided the methodology for level crossing isolation.
Subsequently, there was a change to the isolation strategy and an alternative isolation plan developed which included the powering down of the Werribee relay room. This change was made after the risk of circuits being undesirably energised in the relay room during the re-wiring works was identified. The new isolation arrangements were prepared by signalling contractor Active Railway Signalling (ARS) and isolation and reinstatement plans approved by MTM on 27 November.
The alternative isolation arrangements involved the cutting of the power supply to the relay room while providing an alternative power supply, referred to as a ‘false feed’, to circuits required for the operation of level crossing equipment for the passage of standard gauge traffic. The TCP was not updated to reflect the new isolation arrangements.
Implementation of isolation
On the night of 29 November, the Werribee relay room was powered down[4] and the temporary circuit configuration installed. Fuses 9C2 and 9C4 were disconnected by them being rotated through 90° (Figure 2) and temporary jumper wires were installed (Figure 3). In total there were 4 jumper wires installed in the Werribee relay room, and 3 in location cases near the level crossings.
Figure 2: The probable state of fuses removed on the night of 29 November
Source: MTM, taken on the morning of 4 December prior to the incident, annotated by OCI
Figure 3: One of the jumper wires installed in the Werribee relay room on 29 November
The jumper wire shown in this figure was identified as ‘number 2’. Personal details on the wire label have been redacted.
Source: MTM, taken on 4 December 2020, annotated by OCI.
Reinstatement of power to the Werribee relay room
The changeover[5] of circuits in the Werribee relay room was noted in the commissioning log[6] as complete and ready for testers on the morning of 2 December. The entry for the completion of the changeover was not annotated with a time, however, log entries either side were made at 0500 and 0700 suggesting that the changeover completion was between these times. It was reported that power to the relay room was also restored on the morning of 2 December, although this was not recorded in the logs.
The temporary isolation arrangements put in place on 29 November to facilitate the operation of level crossing equipment for standard gauge trains were not removed when the power was restored to the relay room following the changeover of circuits. The temporary jumper wires and disconnected fuses 9C2 and 9C4 remained as they were.
Signalling circuit function testing in the Werribee relay room
Signalling circuit function testing commenced in the Werribee relay room on 2 December and continued during the (12-hour) day shifts and (12-hour) night shifts between 2 and 4 December. The teams undertaking testing were independent of, and not involved with, the isolation installed on the night of 29 November. At the commencement of function testing, the program was behind schedule and the commissioning was unlikely to be completed by 7 December.
On 4 December, the day shift test team commenced at 0700. Soon after, a standard gauge train 5AM5 travelled through Werribee and the level crossing protection at both Cherry and Werribee Streets operated normally.
The function tests involved the replacement of fuses as required to complete circuits for testing. This was normal practice. At about 0800 and following discussions with others in the project regarding the need to progress the testing of all circuits, the lead tester instructed one of the team to reinstate fuses 9C2 and 9C4 (Figure 4). The testers were not aware that several temporary jumper wires had been installed as part of the level crossing isolation arrangements.
Figure 4: Fuses 9C2 and 9C4 replaced in Werribee relay room
Source: MTM, taken on 4 December after the incident, annotated by OCI
With the jumper wires still in place, control relays remained energised when the fuses were replaced, inhibiting the operation of the level crossing equipment at both Werribee and Cherry Street level crossings.[7]
The passage of train 3PM7 through Werribee
Passage through Werribee Street level crossing
At about 0825 on 4 December, train 3PM7 approached the Werribee Street level crossing travelling at about 50 km/h. The train was detected by rail control systems, but the level crossing equipment did not operate. However, road traffic signals on Werribee Street, which were interfaced with the train detection system, did operate and stopped road traffic.
The crew of train 3PM7 reported sighting traffic management staff at the Werribee Street level crossing and acknowledged their presence by an application of the train horn. Although the traffic management staff were present, they were not actively engaged in managing traffic at that time.
Passage through Cherry Street level crossing
Shortly after, train 3PM7 approached the Cherry Street level crossing travelling at about 52 km/h. The train crew observed that road vehicles were crossing, and that the crossing protection had not activated. In response, the crew made an emergency brake application and sounded the train horn several times. The train entered the crossing travelling at about 48 km/h. The lead locomotive came to a stand about 200 m past the crossing.
CCTV equipment installed at Werribee Railway Station showed motor vehicles crossing on Cherry Street ahead of train 3PM7 (Figure 5). It is estimated that the cars probably cleared the path of the train less than 2 s before the train occupied the crossing (Figure 6).
Figure 5: CCTV images showing road vehicles on Cherry Street as train approaches
Source: MTM, annotated by OCI
Figure 6: CCTV image showing the locomotive entering the level crossing
Source: MTM, annotated by OCI
Post incident management
In immediate response to the incident, the level crossings were secured with traffic management and (after being notified) ARTC train control applied a signal block to prevent standard gauge rail traffic from entering the section.
On inspection within the Werribee relay room, an MTM infrastructure team identified that fuses in positions 9C2 and 9C4 had been reinstated with temporary jumper wires still in place. The fuses were removed and secured, the crossing systems tested and the ARTC signal block removed later on 4 December to allow the resumption of standard gauge services.
For the remainder of the works, level crossing keepers[8] were put in place at the Werribee Street and Cherry Street level crossings to ensure level crossing operations.
Context
The train and actions by crew
Train 3PM7 was a Perth to Melbourne intermodal freight service operated by Pacific National (PN) on the Australian Rail Track Corporation (ARTC) standard gauge network. The train consisted of 2 locomotives and 26 wagons, was approximately 1.4 km long, and had a crew of 2.
Approaching the Werribee Street level crossing, the crew were controlling train speed at about 50 km/h and within the 60 km/h permitted speed. The horn was sounded about 400 m from the Werribee Street crossing and near the crossing to acknowledge track workers.
Records indicate that approaching the Cherry Street level crossing, the train was travelling at a speed of about 52 km/h, still within the permitted speed. Then, in response to the crew detecting cars on the crossing, an emergency brake application was made by the crew when the train was about 150 m from the crossing. The speed of the train commenced to slow and entered the level crossing travelling at about 48 km/h. Records indicate the train horn was sounded by the crew several times on the approach to the Cherry Street level crossing in response to road vehicles continuing to cross.
There was no evidence to suggest that train handling contributed to this event.
Infrastructure
Location
The Werribee Street and Cherry Street level crossings were on the Werribee line of the Melbourne metropolitan rail network and located either side of Werribee Railway Station which was about 32 rail-km from Southern Cross Station in Melbourne (Figure 7). Rail lines through the location included 2 broad gauge lines and a parallel single bi-directional standard gauge line.[9]
Figure 7: Location of Werribee Railway Station to the west of Melbourne
Not all railway stations on the Werribee line are shown in this figure.
Source: Department of Transport, annotated by OCI
Infrastructure management
Metro Trains Melbourne (MTM) was the rail infrastructure manager (RIM) of the broad gauge lines through Werribee and ARTC was the RIM of the standard gauge line. MTM was the responsible RIM for the level crossing equipment and control systems for the Werribee and Cherry Street level crossings.
Werribee Street Level crossing
The Werribee Street level crossing was located about 680 m on the down side (away from Melbourne) of Werribee Railway Station.[10]The road crossing was equipped with active protection that included flashing lights, audible warning (bells) and half-boom barriers, and an active pedestrian crossing was to its east. The railway crossing systems were also interfaced with traffic control systems (traffic signals) to assist the management of road traffic through the level crossing.
At the time of the occurrence, the rail flyover that would replace the level crossing had been constructed and new broad gauge tracks had been installed. Standard gauge traffic was still operating through the level crossing (Figure 8).
Figure 8: Aerial view of Werribee Street level crossing and rail flyover in December 2020
Source: nearmap on 12 December 2020, annotated by OCI
Cherry Street level crossing
The Cherry Street level crossing was located about 215 m10 on the up side (towards Melbourne) of Werribee Railway Station. The road crossing was equipped with active protection that included flashing lights, audible warning (bells) and half-boom barriers (cover photo). Unlike the arrangements at Werribee Street, there were no road traffic lights (interfaced with the railway systems) installed for road vehicles approaching the Cherry Street level crossing.
On the day of the occurrence, the layout of the Cherry Street level crossing included 2 broad gauge lines and a single bi-directional standard gauge line crossing Cherry Street (Figure 9).
Figure 9: Aerial view of Cherry Street level crossing in December 2020
Source: nearmap on 12 December 2020, annotated by OCI
Level crossing control
Both crossings were within the Werribee signal interlocking area. The operation of the active protection for the 2 level crossings involved train detection and signal interlocking functions.[11] Control circuitry was in trackside location cases (at each crossing) and the Werribee relay room located on the Werribee Railway Station platform (Figure 10).
Figure 10: Aerial view of Werribee Railway Station and relay room
Source: nearmap on 12 December 2020, annotated by OCI
Systems were designed so that energised control relays prevented the activation of level crossing equipment. Following the detection of an approaching train, the relays would be de-energised, activating the protection equipment. This design configuration was failsafe in that a loss of power to the control system would result in relays becoming de-energised and level crossing protection systems activating.
A Rail Interface Control Unit (RICU) was also installed at the Werribee Street level crossing to manage the interface functions between the railway crossing system and road traffic control system. The RICU was operational at the time of the incident and on detection of the approaching train by the rail systems, nearby road traffic signals were triggered to stop traffic. This arrangement was not in place at Cherry Street.
Level crossing removal project
Administration
In 2015 the Victorian State government established the Level Crossing Removal Authority (LXRA), an administrative office within the then Department of Economic Development, Jobs, Transport and Resources (DEDJTR). LXRA was responsible for the Level Crossing Removal Project (LXRP). In 2019, administrative responsibility associated with the LXRP was transferred to the Major Transport Infrastructure Authority (MTIA), an administrative office within the Department of Transport (DoT). MTIA used an alliance contracting model and grouped level crossing sites for contracting to program alliances.
Western Program Alliance (WPA)
WPA was one of the 4 alliances established by MTIA to deliver the LXRP. The alliance comprised McConnell Dowell as the principal contractor, Arup and Mott Macdonald as design partners, and Metro Trains Melbourne (MTM) as the rail infrastructure manager. In February 2020, WPA was contracted to remove level crossings at Old Geelong Road in Hoppers Crossing, and Cherry Street and Werribee Street in Werribee.
Stage 3 works at Werribee
To facilitate the removal of the level crossings at Werribee, the infrastructure changes were delivered in 4 main stages. The signalling cabling assets were confirmed during the first stage. Stage 2 comprised civil and structural enabling works, the removal of decommissioned equipment to the west of Werribee station, and interlocking changes. Stage 3 included the commissioning of the broad gauge flyover west of Werribee Station, the installation and commissioning of a new axle counter[12] configuration and the reconfiguration of the Werribee relay signal interlocking. Broad gauge train movements west of Werribee were scheduled to return after testing and commissioning of the new system.
John Holland Group (JHG) and Active Railway Signalling (ARS) were subcontracted to undertake the signalling works associated with stage 3 of the project. Traffic Diversions Group (TDG) was contracted to implement the road traffic management plan.
Metro Trains Melbourne (MTM)
As the accredited RIM,[13] MTM was responsible for ensuring that the design, construction, and commissioning of rail infrastructure was carried out in a way that ensured safety of railway operations. MTM was also listed as being responsible for signalling design within the WPA design and engineering management plan (WPA 2020d).
Works commencing 29 November 2020
Background
In mid-2020, Werribee Railway Station became a terminus for broad gauge trains, allowing construction works to the west of the station. Construction, testing and certification works from September to December would bring the new broad gauge signalling layout, which incorporated the elevated section (the rail flyover) over Werribee Street, into service.
Activities scheduled between 29 November to 7 December included extensive re-wiring of broad gauge circuits in the Werribee relay room, and testing and commissioning works. To enable these works, the project implemented a track occupation[14] and broad gauge trains were terminated at Laverton, about 10 km to the east of Werribee. This meant there would be no broad gauge traffic in Werribee during the occupation from 29 November to 7 December.
The bi-directional standard gauge line through Werribee was not part of the occupation and remained operational. It was planned that the level crossings at Werribee Street and Cherry Street were to be operational for standard gauge rail traffic for the duration of the broad gauge track occupation.
WPA management plans and guides
WPA produced a commissioning management plan (WPA 2020b) which described the framework for the pre-commissioning and commissioning activities. The WPA also developed a works guide (WPA 2020e) which, along with other track and civil works, described the high-level signalling tasks to be undertaken. It also stipulated that working shifts were to be back-to-back 12-hour shifts from 1900 on 29 November to 0700 on 7 December.
Test and commissioning plan
The Alliance produced a test and commissioning plan (TCP) (WPA 2020c) for the works to be undertaken between 29 November and 7 December. The plan was approved by the project’s management and issued for construction (IFC) on 4 November. The purpose of the document was to ensure that required testing and commissioning activities were identified and planned. The TCP outlined the structure of the test and commissioning team (Appendix A) which included the following key personnel:
The Tester in Charge (TIC): The TIC was an ARS employee. They were scheduled to work the 0700 to 1900 day shifts. They prepared the TCP issued on 4 November and were responsible for the satisfactory completion of system testing and commissioning requirements in readiness for service.
The Shift Tester in Charge, also referred to as the Alternate Tester in Charge (ATIC): The ATIC was contracted from HJW Signalling Services Pty Ltd and was scheduled to work the 1900 to 0700 night shifts. They oversaw testing and commissioning activities during the night shifts.
Testers and test assistants: Testers were contracted workers from Lineside Signalling, Dragon Rail and ARS. They were responsible for testing the function of circuits.
The Principles Tester (PT): The PT was employed by MTM and was responsible for confirming that the newly installed system operated in accordance with the relevant signalling principles and safeworking rules and regulations.
Consistent with the MTM standard for testing and commissioning of safety related railway signalling systems (MTM 2018a), the TCP stated that management and testers involved in the works should attend a pre-commissioning briefing. An invitation to a signalling pre-commissioning meeting (with draft TCP attached) was issued by WPA on 22 October 2020 and the meeting was held on 12 November. ARTC was included in the distribution of the TCP. The briefing was not attended by several personnel either because they did not receive the invitation or they chose not to attend. This briefing was held prior to the changes made to the level crossing isolation arrangements.
Level crossing isolation design changes
Isolation plan specified in TCP issued for construction
The testing and commissioning methodology section of the TCP issued for construction (IFC) on 4 November advised that the ARTC standard gauge line would remain operational. The TCP referred to a drawing for the isolation of Cherry Street level crossing which specified an isolation methodology consistent with that used for previous stages of the project. This isolation design did not require powering down of the relay room, did not specify the removal of any fuses, and required 1 temporary jumper wire. Testing work instructions in the TCP were also consistent with these arrangements.
Isolation design changes
About 3 weeks after the finalisation of the TCP, the decision was made to power down the Werribee relay room for the re-wiring works due to concerns that circuits may be undesirably energised during the works. As a result, an updated isolation arrangement was required.
On 25 November, the TIC instructed the ARS design team to develop a temporary feed arrangement for the isolation of the Cherry Street and Werribee Street level crossings. An alternative supply, referred to as a ‘false feed’, would power the control circuits required for the operation of level crossing equipment for the passage of standard gauge traffic.
The design was completed by ARS on 27 November. A simplified representation of the design concept for the Cherry Street level crossing isolation and power feed is shown in Figure 11.
Figure 11: Simplified representation of isolation for the Cherry Street level crossing
Image shows a simplified representation of the level crossing circuits for Cherry Street level crossing. Temporary jumper wire number 1 was put in place to bypass the broad gauge approach and signal interlocking circuits for Cherry Street level crossing. Temporary jumper wire number 2 was put in place to accommodate the planned shutdown of the relay room power supply.
Source: ATSB and OCI.
Temporary jumper wires were installed to isolate the broad gauge train detection circuits from the level crossing control circuits (label 1). During the planned shutdown of power to the relay room, the temporary jumper wire also allowed an alternative power supply (from the level crossing location case) via the control relay in the relay room to the repeater relay at the location case (label 2). The temporary modification required the removal of the power supply to the relay room by the removal of a fuse (label 3) and opening the relay room power supply circuit breaker (label 4).[15]
The isolation plan included instructions to switch circuit breakers off and provided details of temporary wiring changes and fuse removal. Construction notes on the isolation drawings included the instructions ‘install temporary purple jumper wire with green tape in the vicinity of the end of the wire’ and ‘fuses to be removed and secured’ in relation to fuse bay locations 9C2 and 9C4 (Figure 12).
Figure 12: Construction note extract from isolation plan
Source: ARS, extract by OCI
A second set of drawings (reinstatement plan) contained instructions for the reinstatement of power to the relay room. The drawings included instructions for circuit breakers to be switched back on, fuses to be reinstalled, and temporary jumper wires to be removed.
Approval of design changes
In accordance with the requirements of its safety management system, MTM had developed an engineering management system framework (MTM 2019a), a design assurance procedure (MTM 2019b) and a signalling design technical review procedure (MTM 2017). The signalling design technical review procedure defined requirements and responsibilities of contractors and required that design documents applicable to works on MTM signalling infrastructure be submitted to MTM for technical review. Any signalling equipment that was required to be isolated, false fed[16] or removed during project work was to be checked and verified by the contractor and details provided to the MTM Engineering Design Review Group (EDRG) for review.[17]
The revised isolation arrangements were sent by ARS to MTM for review and approval at 1838 on 27 November. Confirmation of approval by the MTM representative of WPA was sent to the contractor an hour later. This design was not issued to the MTM EDRG for review.
Management of the isolation design change
Procedures, guidelines and management plans
The MTM Design Assurance Procedure (MTM 2019b) applied to all MTM’s infrastructure and projects. This procedure defined a design change as a change occurring post-IFC and described the structure of a Design and Engineering Management Plan (DEMP) or Design Management Plan used to detail how the design change would be managed.
The TCP (section 6.5) noted that the process for the issue of design modifications may alter depending on project and contractors’ internal processes and the process being used for each project should be recorded within the design management plan.
The WPA Design and Engineering Management Plan existed as two documents, one referred to works at Werribee (WPA 2020d), the other was a program wide plan (WPA 2019). The purpose of a design change notification (DCN) referenced in the program wide plan was to provide stakeholders with a summary of the scope of a design change made to IFC documentation. The plan stated that a DCN resulting from a design change and the design change register (DCR) would be issued to the Level Crossing Review Group (LXRG) which would review the DCN. The program wide plan also stated that all temporary work that had the potential to impact train operations and/or have safety implications were required to be reviewed by the MTM LXRG.
Dissemination and notification of isolation design change
DCNs were recorded in the DCR for the LXRP at Werribee. Between 20 August 2020 and 4 December 2020, 19 DCNs were recorded in the register, for all infrastructure types. However, the change to the isolation arrangements in the relay room approved on 27 November was not included in the DCR and the TCP was not reissued following the change to the isolation arrangements. There was no record of communication with the LXRG concerning the design change for isolation of the level crossing.
Design changes made following the occurrence
Following the non-operation of the level crossing equipment on 4 December 2020, a design modification was made to the isolation arrangements. The design modification, dated 14 December,[18] included the addition of construction note #3 which required the wires connecting the temporary jumpers to the fuse holder to be removed, sleeved and secured (Figure 13). This modification strengthened the arrangement in that reinsertion of the fuses (alone) would not complete the electrical circuit.
Figure 13: Extract from design modification drawing, post incident
Source: ARS, extract by OCI
Implementation of isolation arrangements
Werribee relay room environment
At the time of the isolation, access restrictions associated with the COVID-19 pandemic were in place. The WPA Pandemic and Readiness response plan (WPA 2020a) required all buildings on site to have signage at the entry point displaying the maximum capacity for each building in accordance with a 4 m2 per person rule. This applied to the Werribee relay room and probably limited free access to the room during isolation activities.
At the time of the isolation, there were several technicians from the John Holland Group inside the room undertaking electrical work. The ATIC was also present at the relay room.
Installation of isolation arrangements on 29 November
The commissioning log recorded that the broad gauge track occupation started at 2100 on 29 November. The MTM level crossing disarrangement form showed that, as planned, the Werribee Street level crossing for broad gauge services was confirmed non-operational at 2220, and the Cherry Street broad gauge crossing non-operational at 2348. These times were consistent with entries in the commissioning log. The log also recorded that the Werribee relay room power was isolated at 0135 on 30 November 2020.
The isolation drawings and construction notes[19] required certain circuit breakers to be switched off, temporary jumper wires to be installed, other wires to be disconnected and sleeved and select fuses to be removed and secured. Based on available evidence, fuses 9C2 and 9C4 were not completely removed but were instead folded out (turned 90 degrees) with one end remaining in the holder. No specific instructions existed in the MTM specification for signalling supply, construction, and installation (MTM 2018b) on the method of securing a fuse bay to reduce the risk of premature reinstatement.[20]
The purple temporary jumper wires were installed broadly in accordance with the isolation drawings, excepting for the colour of identifying labels. White tape was used to label the wires instead of green as specified in the isolation drawings. The labels identified the designated number of the temporary jumper wire (in accordance with the isolation drawing) and the name of the installer as being the ATIC. The ATIC also annotated the isolation drawings, marking off the installation of each jumper wire and the removal of fuses. The ATIC had also added the annotation of ‘tested ok’ and signed the work instruction as having checked the work.
Several temporary jumper wire installations were recorded on the isolation drawings and in the test strap register which were inconsistent with the identification of the installer on jumper wire labels.[21] An ARS testing assistant, a cadet railway signalling engineer[22] under the supervision of the ATIC, signed the test strap register and the isolation drawing as the installer of the temporary jumper wires in the Werribee relay room when they had only installed the jumper wire at the Cherry Street location case.
Level crossing event during isolation
At about 2320 on 29 November during the application of the isolation, a freight train on the standard gauge line crossed the Cherry Street level crossing without activating the level crossing protection equipment. Traffic control was requested to stop road vehicles passing through the level crossing shortly before the train arrived. It was reported by the ATIC that this event may have distracted those involved in the isolation activities.
Testing
MTM engineering standards for testing and commissioning
The standard for testing and commissioning of safety related railway signalling systems (VRIOG 2008) was initially developed through the collaboration of members of the Victorian Rail Industry Operators’ Group[23] (VRIOG) and was adopted by the MTM as part of its engineering standard for testing and commissioning of safety related railway signalling systems (MTM 2018a). The practices specified in the standard applied to the testing and commissioning phases of new and modified railway signalling systems.
The standard stated that the objective of the testing and commissioning of new or modified signalling systems, including where disconnected wiring may be reconnected, was to ensure that, before the systems were used for the control of train operations, the systems were to satisfy all specified requirements, safe working standards and any application‑specific requirements.
Other sections of the standard pertinent to this investigation included:
Independence – The standard specified the independence required of persons involved across different parts of the work.
Pre-commissioning meeting – The standard required a pre-commissioning meeting to be held where key personnel involved in the commissioning works were briefed and a project scope, work sites and responsibilities were identified, and a test plan provided. This meeting was required to be separate from any occupation/safeworking or other discipline‑specific meeting associated with the project.
Testing strategy – The standard required that a written statement of the proposed testing methodology be prepared, along with proposed layout and anticipated testing content in consultation with other involved parties at an early stage of the project. The standard required that the statement was kept up to date throughout the project development. Amongst other items, the testing strategy was to include:
creation of a preliminary testing program that included personnel resources
a program of suitable and achievable work packages for individual testers to undertake any training needs
the limits of the testing, including responsibilities, interfaces (equipment interfaces, area interfaces, project interfaces), and stage work requirements
identification of hazards, risks and control measures
train operation and safe working arrangements.
Operational requirements – The standard stated that if train running was unavoidable, any testing that was going to disrupt the train running should be carefully planned and completed in the time available. All hazards during testing and commissioning were required to be identified and appropriate contingency plans put in place.
Testing procedures – These were to provide details of the tests that were required to be carried out and included:
The standard provided instruction on the installation and removal of wires and advised that new wires should be stripped and crimped, continuity tested and then insulated and secured. The standard stated testing should not commence until all yellowed wires had been disconnected and removed. Yellowed wires were those wires that the design requires to be removed during a signalling changeover and are marked in yellow on the circuit diagram.
Other relevant standards
The Rail Industry Safety and Standards Board (RISSB) Australian Standard for signal testing and commissioning, AS 7717 (Standards Australia 2016), stated that:
… before certification function testing is commenced, testers shall ensure that circuit wiring testing is complete, that the circuit wiring is secured against interference, and that the approved final circuit wiring diagrams are correctly certified as bell continuity tested, wire counted, and insulation tested.
Testing specified in the TCP
The testing regime outlined in the TCP described tests ‘broadly in the required sequence to be completed and some activities may be completed in parallel with others.’[29] In order of activity, these were:
insulation (megger) testing
continuity (bell) testing
wire / null count testing
strap and function testing
through testing.
Although the testing summary in the body of the TCP was consistent with AS 7717 and the MTM engineering standard, with the wire and null count testing listed for completion prior to strap and function testing, the detailed testing program differed. The detailed program in document WPA‑program v22 for 29/11-07/12 Occupation scheduled the strap and function testing before the wire and null counts (Figure 14).
Figure 14: Extract from ‘WPA-program v22 for 29/11-07/12 occupation’
Source: ARS, annotated by OCI.
Implementation of testing from 2 December
Restoration of power to the relay room on 2 December
A detailed occupation program (WPA 2020g) was issued on 27 November which indicated that testing in the Werribee relay room was scheduled to start on the morning of 30 November. However, owing to a delay, the Werribee relay room was not available to testers until the morning of 2 December. Entry 38 (of that morning) in the commissioning log recorded that the Werribee relay room changeover was completed and included the comment ‘ready for testers’. Although no specific time was recorded against this entry in the log, evidence suggests it was probably made between 0500 and 0700.
Power was restored to the relay room on the morning of 2 December to allow function testing although there was no record of this activity in the commissioning log. When power was restored to the relay room, it is very likely that technicians did not refer to the reinstatement plans. Isolation arrangements remained in place. Fuses 9C2 and 9C4 remained disconnected and a total of 7 temporary jumper wires remained in place, 4 in the relay room, one in the Cherry Street level crossing location case, and 2 in the Werribee Street level crossing location case.
Function testing
The commissioning log recorded that function testing in the relay room was conducted later on 2 December and continued into 3 December, during day and night shifts. Testing was undertaken by teams independent of those involved in the isolation of the relay room.
Function testers reported ‘finding wires in the wrong spots’. The TCP required that wire and null count testing occur prior to the strap and function testing. Had testing occurred in the order required of the TCP it is probable that incorrectly positioned wires would have been identified and repositioned prior to the strap and function testing.
Testing of signalling circuits in the Werribee relay room required that fuses be restored to their normal positions. The function tester leading the testing team that started work on the morning of 4 December instructed one of their team members to reinstate the fuses. This was reported to have occurred following discussions between project team members where it was decided that all fuses should be reinstated. This was probably intended to expedite function testing due to testing and commissioning being behind schedule.
As the temporary jumper wires used for the isolation were still in place, the reinstatement of the fuses and power being restored to the relay room meant the crossing control relays for both the Werribee Street and Cherry Street level crossings were inadvertently permanently powered.
Testing with redundant wiring and bare ends
The MTM standard for signalling installation (MTM 2018b) required that decommissioned signalling wiring should be removed immediately or should have its ends cut off, sleeved, tagged, and shall be removed prior to final testing and commissioning of any new works. The Australian Standard for Signalling testing process (Standards Australia 2017), though not mandatory, also stated that testing should not commence until all wires for removal have been disconnected and removed.
On 3 July 2020, the WPA submitted a request for information to MTM asking whether a standard waiver would be required from July to December 2020 to tag, cut, and sleeve redundant circuit ends while Werribee was being configured as a terminal station. MTM confirmed that a waiver was not required for the temporary retention of redundant equipment and that WPA’s proposal to remove all redundant equipment and wiring during the 29 November to 7 December occupation was acceptable. The project did not request a waiver nor had permission been given to conduct testing while bare ends were present on redundant wiring in the Werribee relay room.
For the December testing and commissioning activities, the TCP (section 6.5) referenced the need to remove redundant wiring from the Werribee relay room. Wires requiring removal were to be identified with yellow tape. The TCP stated that testing should not commence until all yellow wires[30] and equipment had been fully disconnected and permanently removed. However, the TCP also stated that yellow wires could remain subject to the approval of the MTM Head of Engineering Signalling and if the redundant wiring was not removed, it should be made safe using blind crimps[31] or terminated.
On 2 December, the principles tester (after attending the Werribee relay room) contacted the TIC by email, stating that principles testing[32] could not be started while there were wires with bare ends present which produced a risk of stray wires causing energisation of circuits. The principles tester advised that ‘unrecovered redundant wiring needed to be removed, and if not they needed to be made safe’. The commissioning log recorded that sleeving of wires to protect bare ends was not completed until 1400 on 3 December. The redundant wires were made safe prior to the level crossing occurrence on 4 December.
The timings recorded in the commissioning log, along with interview evidence indicates that function testing was conducted while bare ends were present. This was contrary to the TCP and continuation of function testing while redundant wiring was being made safe was probably influenced by schedule pressures.
Road traffic management
Applicable documents
Requirements and strategies for the management of road traffic risks were mentioned in several standards, guidelines and project documents. The following is a summary of those references:
MTM standard for testing and commissioning (MTM 2018a) stated that all hazards during testing and commissioning were required to be identified and appropriate contingency plans put in place.
The Level Crossing Removal Project – Western Program Alliance Works Guide (WPA 2020e) stated that traffic management personnel would be in place between 29 November 2020 and 7 December 2020 at level crossings, including Werribee Street and Cherry Street, for ‘monitoring the traffic ….’
The WPA Works Guide (WPA 2020e) also contained a section titled ‘Road Closures/Traffic Management’. For the period between the night shift of 29 November and the night shift of 1 December, the Works Guide required traffic management at Cherry Street to ‘Stop all lanes intermittently to allow Hi-Rail Access’.[33]For the period between the day shift of 3 December and the night shift of 6 December, the guide required traffic management at Cherry Street to ‘Stop traffic over level crossing intermittently to allow for principles testing & test trains’.[34]
The TCP did not mandate traffic management outside of the times that test trains were planned. The occupation notice (MTM 2020a) attached to the works guide that captured the area of the Cherry Street level crossing gave no specific instructions for the protection of level crossings.
The original isolation drawings issued for construction but subsequently superseded included a requirement for ‘crossing to be protected by traffic management and safe working at all times’. This requirement was removed from the revised isolation drawings that were approved on 27 November.
A daily train notice was issued for the standard gauge which advised of works adjacent to the ARTC rail corridor. This notice was included in the works guide (WPA 2020e), the purpose of which was to outline the details of the broad gauge track occupation for 29 November to 7 December. The daily train notice did not make reference to traffic protection or operation of the level crossings for the ARTC standard gauge line.
Implementation
The provision of traffic management at Werribee Street and Cherry Street was subcontracted to Traffic Diversions Group (TDG). A traffic guidance scheme produced by TDG (TDG 2020) for the occupation showed the provision of traffic controller staff at both crossing locations, for both directions of traffic.
Traffic management staff are reported to have been available at level crossings if needed for broad gauge movements but were not actively managing traffic for normal standard gauge rail traffic. Level crossing protection was expected to operate normally for standard gauge trains.
Interview evidence indicates there were differences in opinion amongst project personnel on implementation of road traffic management and a lack of clarity on managing the risks during testing. ARTC, the RIM for the standard gauge track, was not consulted by WPA or MTM in the implementation of traffic management as a risk control during testing.
MTM audit of the project in October 2020
Audit of signalling testing and commissioning works
MTM was responsible for ensuring the safety of railway operations during projects for which MTM was the accredited RIM. As part of its assurance program, MTM conducted an internal audit of testing and commissioning (T&C) activities on the Werribee project in October 2020 due to the number of incidents associated with T&C works performed in the field.[35]
The audit report (MTM 2020c) was published by MTM on 20 November 2020. The purpose of the audit was to determine the extent of MTM’s conformity with the requirements of the signalling works in TCPs. This project was selected as an audit subject as MTM had identified several new projects which were to be delivered by the Western Program Alliance (of which MTM was a member). Findings (and corrective actions as applicable) relevant to this investigation included:
Evidence provided by the project team was not sufficient to demonstrate that changes in scope during testing and commissioning works were evaluated ‘by the relevant people’[36]to determine potential consequences. In addition, it was found that scope change details were not formally recorded in the commissioning log. The finding was categorised high priority and agreed corrective action[37] (by 23 December) required TIC to ensure that any changes in scope were clearly identified, assessed and documented, and the potential consequences documented. Assuring conformity of changes with current standards was also identified in agreed corrective action.
There were instances of a TIC certifying their own work at a commissioning in August 2020. The finding was categorised as medium priority and an agreed corrective action date of 15 December was specified.
Some staff were not attending pre-commissioning meetings. No specific corrective action specified for this finding.
The audit recommended communication of the findings to all project managers, signalling project managers, testers in charge and principles testers to share learnings from the audit and to prevent recurrence of similar findings in future works. The TIC at the time of the incident in December 2020 was included in the audit report dissemination list.
Previous similar occurrence
Level crossing irregularity North Geelong, Victoria in 2019
The most recent example of a level crossing irregularity during infrastructure project works in Victoria involved the standard gauge passenger train 3MA8 at North Geelong, Victoria, on 8 January 2019 (ATSB 2020). The protection equipment did not activate for the passage of the train through the Thompson Road level crossing. In preparation for stage 1 track work, only the broad and dual gauge[38] tracks at the Thompson Road level crossing were to be isolated. The level crossing protections for the adjacent standard-gauge track were to remain active until stage 2 works at a later date. However, the signalling tester, having been provided with the isolation drawings for stages 1 and 2 as a single pack by the TIC, mistakenly isolated the level crossing for stage 2 work, in addition to stage 1.
VicTrack, through their contractor UGL Engineering Limited, did not provide the TIC or signalling testers with specific instructions detailing the scope of work to be conducted at each stage of the project, but rather, only provided packaged isolation drawings for the entire project. The absence of these specific instructions increased the risk of the works being incorrectly implemented.
Safety analysis
Introduction
For the passage of train 3PM7 through Werribee on the morning of 4 December 2020, the level crossing equipment at Werribee Street and Cherry Street did not operate to stop road traffic. This led to a near-collision between train 3PM7 and road vehicles at the Cherry Street level crossing. The analysis discusses:
The non-operation of the level crossing equipment
Installation of isolation arrangements on 29 November
The reinstatement of power and testing from 2 December
Isolation design change processes and communication
Testing protocols
Traffic management.
The non-operation of level crossing equipment
In preparation for works on broad gauge systems, temporary isolation arrangements were established on the night of 29 November to facilitate the operation of the Werribee Street and Cherry Street level crossings for standard gauge rail traffic. The isolation included the cutting of power to the Werribee relay room, the removal of fuses 9C2 and 9C4, the disconnection of wires and the addition of temporary jumper wires in the relay room and in location cases near the level crossings. Implementation of the plans was successful in achieving activation of level crossing equipment for standard gauge traffic while works were undertaken on the broad gauge systems.
Following the completion of circuit changeover works on 2 December, power was restored to the Werribee relay room in preparation for testing. The temporary isolation arrangements that had been installed to facilitate level crossing operation for standard gauge trains, including the temporary jumper wires, remained in place.
When the fuses at positions 9C2 and 9C4 were reinserted by the testing team on the morning of 4 December with the temporary wiring still in position, operation of level crossing protection equipment at Werribee Street and Cherry Street was inhibited by the unintended permanent powering of the crossing control relays. Testers were not aware of the isolation arrangements and that their action would affect the operation of the level crossings.
Installation of isolation arrangements on 29 November
Removal of fuses 9C2 and 9C4
The isolation installation was not fully consistent with the isolation plans. Fuses were not removed and secured as described in construction notes. When implementing the temporary isolation arrangements on the night of 29 November, one end of each of the fuses in positions 9C2 and 9C4 were turned out from their holders rather than being removed and secured as described in design drawings. Although this achieved the objective of disconnecting the circuits, it left the circuits vulnerable to re-connection.
The practice of turning a fuse outward in its holder (to facilitate its disconnection) without implementing other control measures carries risk, in this instance a safety critical risk. MTM guidelines were not specific regarding the work practices required of the removal of fuses in safety critical scenarios and the application of risk controls either through more robust design and/or more robust practices to secure fuses and block fuse holders.
Jumper wire labels
Construction notes on the isolation drawings provided the following instruction: ‘install temporary purple jumper wire with green tape in the vicinity of the end of the wire’. However, white tape was used as labelling on the jumper wires rather than the green as specified. This was a deviation from the isolation plans, although unlikely to have been noticed by testers who were not familiar with the isolation plan drawings.
Independent check of isolation arrangements
The principle of independent inspection and testing of new and altered work, including the design and/or installation of a vital circuit, requires that no person undertakes and then certifies their own work when that work produces a safety critical outcome.[39]
It is likely that the ATIC undertook parts of the isolation works and then verified that those same works had been completed in accordance with the isolation plans. This absence of independent checking of some works was consistent with the findings of the MTM audit of this project 2 months earlier which found instances of TICs certifying their own work.
Also, documentation recording the name of the person who had installed the temporary jumper wires in the Werribee relay room was signed (as installed) by a person who was not physically present in the relay room and had not installed the wires. This was probably to ensure documentation met the independence requirements.
Other factors
Other factors that may have influenced the installation and checking of isolation arrangements that night were considered, including project resourcing, access restrictions due to the COVID-19 pandemic, the presence of several other workers in the relay room, the passage of a standard gauge train at about 2320 during isolation implementation, and fatigue of involved personnel. Although one or more of these factors may have impacted isolation activities, there was insufficient evidence to conclude that any of these factors had significantly influenced the installation.
Project pressures to complete the testing and commissioning within the window of the track occupation probably did heighten the potential for error, particularly in the context of late changes to the isolation arrangements and limited dissemination of information on the changes to potentially affected parties.
Reinstatement of power on 2 December
Broad gauge works in the Werribee relay room were considered ready for testing on the morning of 2 December and power was restored to the relay room that morning. The arrangements specified in the isolation plans, including the positioning of jumper wires, were retained.
The investigation did not identify any evidence that the reinstatement plan was consulted by technicians when power was restored. The plan addressed the restoration of power to the relay room and the removal of the temporary isolation arrangements.
There was also no provision in the reinstatement plans for the isolation (that included powering down of the relay room) to be replaced with a simplified isolation when power was restored to the relay room. It is probable that the reinstatement sequence, which included restoration of power for testing, was not fully considered in the design or the programming of testing and commissioning activities from 2 December to completion.
Isolation change processes and communication
Change to design
To facilitate powering down of the Werribee relay room while maintaining level crossing operation for standard gauge traffic, the TIC requested the ARS design team to develop a new isolation design. Isolation and reinstatement plans were developed, and the isolation plan implemented. The design achieved the desired function although it was vulnerable to the replacement of fuses with jumper wires still in position.
On the isolation plan, construction notes stated that fuses in fuse bays 9C2 and 9C4 were to be ‘removed and secured’. The risk associated with inadvertent reinsertion of fuses could have been reduced with more explicit construction notes pertaining to the labelling and protection of fuse bays, and/or the disconnection and sleeving of fuse holder terminal wires. A design modification made to the isolation plans after the event on 4 December specified disconnection of the terminal wires.
Design change approval
The signalling design technical review procedure contained specific requirements in relation to isolations and false feeds. Project works requiring any signalling equipment to be isolated, false fed or removed required an isolation/re-instatement design package which was required to be checked, verified by the contractor, and issued to the MTM Engineering Design Review Group (EDRG) for review. The isolation and reinstatement plans approved by MTM on 27 November 2020 were not reviewed by the EDRG or the MTM Level Crossing Review Group (LXRG). Review may have led to more robust plans.
Documenting change
Test and Commissioning Plan
Standard AS 7717 (Standards Australia 2016) recognised that on occasion, there may be a need to vary from the Test and Commissioning Plan (TCP). The standard stated that the TCP should ‘remain flexible enough to allow changes in direction when problems arise’ and ‘should be kept up to date throughout the project development’.
The change to the isolation strategy was made after the TCP was issued for construction on 4 November 2020, and before the occupation that commenced on 29 November. The TCP was not updated and reissued to reflect the change to the isolation arrangements and did not detail any planned strategy for the return of power to the relay room, a partial implementation of the reinstatement plan. The risk that the design change would impact signal testing was not documented by the TIC and was probably not assessed.
Registration of change
The change to the isolation arrangements in the relay room was not included in the register of design change notifications (DCN). Inclusion of project changes in the register was important for ensuring the change was captured by MTM’s scope of accreditation and providing additional opportunities for MTM to monitor the change.
Incorporating change into program and work instructions
Excepting for the design drawing package, the change was not incorporated into program documentation. The reinstatement plan had been developed by ARS but the implementation schedule was not clearly documented in the work program and there was no evidence of consideration of how the reinstatement plan would practically be implemented when power was to be restored to the relay room for testing. An MTM audit of this project 2 months earlier also found instances of changes in scope not being assessed and documented.
The TCP did not contain instruction regarding the reinstatement of power to the relay room. The TCP lacked the relevant instruction because the IFC version was released on 4 November before the need to power down and repower the relay room had been realised.
Communicating change
Several key staff including the testing team working in the Werribee relay room on 4 December were not aware of the change to the isolation strategy and the temporary configuration.
Along with the change not being included in the register of DCNs, an initial change impact assessment was not undertaken. There was no record that interface with stakeholders who would be impacted by the change, such as testers, had been considered.
Pre-commissioning briefings
Several key personnel did not attend the pre-commissioning meeting held on 12 November, either by choice or because they did not receive an invitation. Although this had no impact on this event, the importance of attendance of critical staff at briefings is reflected in the MTM engineering standard for testing and commissioning of safety related railway signalling systems (MTM 2018a) and was a requirement of the TCP. Key staff not attending pre-commissioning meetings was also a finding of the internal MTM audit report released on 20 November, shortly before the incident.
Testing protocols
Context
Function testing commenced on the morning of 2 December and involved teams on day and night shifts. Testers were independent of installation works, had not been involved in the installation of isolation arrangements and were not briefed on the isolation design which differed from recent crossing removal projects undertaken by WPA. The leader of the testing team on the morning of 4 December was not aware of the isolation configuration implemented during the works and stated that the temporary purple jumper wires installed during the isolation were in addition to other purple wires installed in the relay room.
Reinstatement of fuses was required for function testing, and it was therefore not uncommon for testers to reinstate turned fuses. Practices amongst testers were reported to vary, some taking a systematic circuit-by-circuit approach to restoring circuits, others a batched approached. On 4 December and following conversations with a member of the project team, testers reinstated fuses (9C2 and 9C4) which had been turned out as part of the isolation design. The reinstatement of fuses was not considered unusual practice for testers although this team was influenced by the advice of others within the project, and probably by pressures associated with the testing and commissioning being behind schedule.
Order of testing
Signal testing comprised the following 3 main elements, each of which should be undertaken by independent teams:
verification, during which installed relays and wiring are visually compared to the detailed design documents. This ensures circuits do not include any contact, terminal, or wires not shown in the circuit diagram. This is generally satisfied by conducting a ‘continuity test’, a ‘wire count’ and a ‘null count’ test.
functional testing, undertaken by functional testers, during which the electrical operation of installed relays and wiring is checked against the detailed design documents.
principles testing, undertaken by principles testers using their knowledge of signalling principles.
The testing summary included within the main body of the TCP was consistent with this process and the MTM engineering standard for testing and commissioning of safety related railway signalling systems (MTM 2018a) which required circuit tests to be undertaken before the functionality of the signalling was tested.
Programmed and implemented testing varied from this approach. The function testing was conducted prior to the verification element being completed. Probably because the verification had not been completed, the testing team reported ‘finding wires in the wrong spots’ when they commenced function testing. The likelihood of wires being found incorrectly installed during function testing would probably have been reduced if the wire and null count testing had been concluded before strap and function testing. Undertaking function testing prior to verifying that the installed circuits were consistent with the drawings also increased the risk of an unintentional false feed being applied to affect working circuits. This risk was not directly associated with the non‑operation of the level crossings in this instance.
Redundant wiring and bare ends
Although the installation of the new signalling had been completed by the morning of 2 December, the removal of redundant wiring had not, and wiring with bare ends presenting a hazard was not reported as resolved until 1400 on 3 December. Function testing was conducted in the Werribee relay room while there were bare ends present. This was in contradiction to MTM’s procedures and Australian Standards for signal testing and increased the risk of erroneous signal testing results. This risk was not associated with the non-operation of the level crossings in this instance.
Traffic management as risk control
The isolation design drawings issued with the IFC version of the TCP on 4 November contained the instruction ‘Crossing to be protected by traffic management and safe working at all times’. However, this instruction was not present on the isolation drawings that were approved on 27 November. During testing, traffic management was limited to the protection of road rail vehicle movements on the broad gauge tracks as part of occupation works, and to mitigate circumstances where traffic might be caught queueing over the crossing. Traffic management was also to be used for test trains on the broad gauge lines.
The commissioning works for the level crossing removal project took place adjacent to the operational standard gauge railway managed by ARTC. Level crossing activation control equipment was located in the same relay room where signal function testing was being undertaken, and the risk of this testing affecting the safety of the operating railway was not sufficiently controlled. Traffic management for the passage of standard gauge rail traffic was an available, but unused, risk control during testing and commissioning activities. ARTC was not consulted on the use of traffic management as a risk control.
After the 4 December wrong side failure, level crossing keepers who could activate level crossing operation in the instance of a system failure were posted to the level crossings for the remainder of the testing and commissioning activities.
Findings
ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition ‘other findings’ may be included to provide important information about topics other than safety factors.
Safety issues are highlighted in bold to emphasise their importance. A safety issue is a safety factor that (a) can reasonably be regarded as having the potential to adversely affect the safety of future operations, and (b) is a characteristic of an organisation or a system, rather than a characteristic of a specific individual, or characteristic of an operating environment at a specific point in time.
These findings should not be read as apportioning blame or liability to any particular organisation or individual.
From the evidence available, the following findings are made with respect to level crossing irregularities involving freight train 3PM7 at Werribee, Victoria on 4 December 2020.
Contributing factors
Changed level crossing isolation arrangements were not effectively reflected in program documentation, nor effectively disseminated to all those potentially affected. An earlier internal audit of the project also identified instances of scope changes not being documented. (Safety issue)
When installing isolation arrangements on the night of 29–30 November, fuses to be removed and secured were instead probably folded out with one end remaining in the fuse holder. This made the fuses vulnerable to inadvertent reinstatement.
Power to the Werribee relay room was returned on 2 December with temporary jumper wires for the isolation retained. There was no evidence of reference being made by technicians to the reinstatement plan and the vulnerability of the isolation arrangements was probably not appreciated.
Fuses disconnected for the isolation were reinstated by testers on the morning of 4 December with the temporary wiring for the isolation still in position. With circuits in this configuration, operation of the level crossing equipment at Werribee and Cherry Streets was inhibited.
Other factors that increased risk
Isolation and reinstatement
Metro Trains Melbourne standards and procedures did not specifically address requirements associated with fuse removal and securement in safety critical scenarios. (Safety issue)
There was probably no independent check of the isolation arrangements installed on the night of 29 November. An earlier internal audit of the project also identified instances of testers in charge checking their own work. (Safety issue)
The change to isolation design
There were opportunities for the updated isolation design to incorporate additional risk controls to reduce the likelihood of inadvertent replacement of removed fuses.
Although approved by MTM, the isolation and reinstatement plans that included false feed arrangements were not reviewed in accordance with MTM design approval processes.
The change to the isolation design was not documented with a design change notification.
Other risk controls
Road traffic management was an available risk control but not used during function testing. This became more critical following the reinstatement of power to the Werribee relay room.
Testing did not follow the order identified in the MTM engineering standard and the body of the Test and Commissioning Plan.
Contrary to standards and procedure, function testing was conducted while there were signalling wire bare ends present on redundant wiring in the Werribee relay room.
Several staff critical to the testing program did not attend the pre-commissioning meeting for the testing and commissioning activities between 29 November and 7 December. An earlier internal audit of the project identified previous instances of this practice.
Other findings
Records for the installation of temporary jumper wires in the relay room were signed-off as being completed by a worker who did not undertake the installation.
Safety issues and actions
Central to the ATSB’s investigation of transport safety matters is the early identification of safety issues. The ATSB expects relevant organisations will address all safety issues an investigation identifies.
All directly involved parties were provided with the draft report and invited to provide submissions. As part of that process, each organisation was asked to communicate what safety actions, if any, they had carried out or were planning to carry out in relation to each safety issue relevant to their organisation.
Descriptions of each safety issue, and any associated safety recommendations, are detailed below. Click the link to read the full safety issue description, including the issue status and any safety action/s taken. Safety issues and actions are updated on this website when safety issue owners provide further information concerning the implementation of safety action.
Safety issue description: Changed level crossing isolation arrangements were not effectively reflected in program documentation, nor effectively disseminated to all those potentially affected. An earlier internal audit of the project also identified instances of scope changes not being documented.
Safety issue description: Metro Trains Melbourne standards and procedures did not specifically address requirements associated with fuse removal and securement in safety critical scenarios.
Safety issue description: There was probably no independent check of the isolation arrangements installed on the night of 29 November. An earlier internal audit of the project also reported instances of testers in charge checking their own work.
Additional safety actions
Proactive safety action taken by the Australian Rail Track Corporation
Safety actions taken by the Australian Rail Track Corporation (ARTC) in response to this level crossing irregularity and a similar irregularity in Adelaide on 7 December 2020 include:
Executive engagement with adjoining rail infrastructure managers on interim risk control measures at the shared active level crossings
Updates to ARTC’s standard for bridging or false feeding signalling circuits including the ARTC requirement for bridging on the shared active level crossings
The introduction of additional protocols for shared rail corridors and improvements to the rail/rail interface agreement with Metro Trains Melbourne, including communications.
Other relevant safety initiatives
Victoria’s Signalling Strategy Taskforce
The Signalling Strategy Taskforce (SST) was established in June 2021 as a specialist advisory group of the Office of the Director General within Victoria’s Major Transport Infrastructure Authority (MTIA). The MTIA was replaced by the Victorian Infrastructure Delivery Authority (VIDA) in April 2024.
The SST was established to address systemic issues affecting the efficient and effective delivery of signalling works required to support Victoria’s rail projects. VIDA advised that an objective of the SST is to identify and implement changes to practices, processes and methods of engagement to address key vulnerabilities identified as impacting signalling project delivery.
The SST is focused on delivering improvements in several areas of signalling planning, support and delivery. Of relevance to the circumstances of this occurrence are:
The development of a uniform, objectively assessed, signalling competency attainment and recognition system, particularly in the areas of signalling design, testing and commissioning, that supports skills development and portability, including alignment with other national and internationally recognised schemes.
The updating and unifying of Victoria’s railway signalling standards and related guidance material to prepare for and support the application of modern signalling and signalling control systems, as well as to reduce ambiguity and uncertainty.
ATSB comment
The successful implementation of the activities of the SST within VIDA should provide a framework for, and contribute to, addressing the safety issues identified in this investigation.
Glossary
AS
Australian Standard
ARS
Active Railway Signalling
ARTC
Australian Rail Track Corporation
ATIC
Alternate Tester In Charge
CCTV
Closed-circuit television
CSFGR
Cherry Street Level Crossing Control Relay
DCN
Design Change Notification
DCR
Design Change Register
DEDJTR
Department of Economic Development, Jobs, Transport and Resources
DoT
Department of Transport
EDRG
Engineering Design Review Group
IFC
Issued For Construction
JHG
John Holland Group
LXRA
Level Crossing Removal Authority
LXRG
Level Crossing Review Group
LXRP
Level Crossing Removal Project
MTIA
Major Transport Infrastructure Authority
MTM
Metro Trains Melbourne
ONRSR
The Office of the National Rail Safety Regulator
PN
Pacific National
RFI
Request For Information
RIM
Rail Infrastructure Manager
RTO
Rail Transport Operator
RISSB
Rail Industry Safety and Standards Board
SMS
Safety Management System
TCP
Test and Commissioning Plan
TDG
Traffic Diversions Group
TIC
Tester In Charge
TWI
Testing Work Instruction
UPS
Uninterruptable Power Supply
VRIOG
Victorian Rail Industry Operators’ Group
WPA
Western Programme Alliance
Sources and submissions
Sources of information
The sources of information during the investigation included:
Metro Trains Melbourne
Western Program Alliance
Active Railway Signalling
Pacific National
CCTV footage from Werribee
References
ATSB (Australian Transport Safety Bureau) (2020) Rail Occurrence Investigation Report RO‑2019-002 Level crossing irregularity involving passenger train 3MA8, North Geelong, Victoria, on 8 January 2019, Australia.
MTM (Metro Trains Melbourne) (2018a) Testing and commissioning of safety related railway signalling systems - engineering standard L1-CHE-STD-073, version 1.
MTM (Metro Trains Melbourne) (2018b) MTM L1-CHE-STD-070, Specification for signalling supply, construction and installation, version 1.
MTM (Metro Trains Melbourne) (2019a) Engineering Management System Framework, L1_CHE‑MAN-001 –Version 1.
MTM (Metro Trains Melbourne) (2019b) Design Assurance Procedure, L1-CHE-PRO-045–Version 1.
MTM (Metro Trains Melbourne) (2020a) Absolute Occupation Notice, 2101/2020.
MTM (Metro Trains Melbourne) (2020c) Internal Audit Independent Inspection Report, Western Program Alliance (WPA), Testing & Commissioning Compliance (WPA), 2 & 7 October 2020.
Standards Australia (2016) Signal testing and commissioning (AS 7717-2016), Rail Industry Safety and Standards Board (RISSB).
Standards Australia (2017) Signalling testing process (AS7716:2017), Rail Industry Safety and Standards Board (RISSB).
VRIOG (Victorian Rail Industry Operators’ Group) (2008) Testing and commissioning of safety related railway signalling systems, 012.5 revision A Issue Date: 11/12/2008.
WPA (Western Program Alliance) (2019) Design and engineering management plan WSP‑000‑WPA-PLN-XPN-0019.
WPA (Western Program Alliance) (2020a) Pandemic and readiness response plan, 2792‑0000‑OHS-PLN-0003.
WPA (Western Program Alliance) (2020c) Test and commissioning plan, WSP-050-C-WPA-PLN-09- WER-GSG-0003 Revision: 0 (IFC).
WPA (Western Program Alliance) (2020d) Design and engineering management plan, WSP‑030‑WPA-PLN-XPM-0019, revision 3.
WPA (Western Program Alliance) (2020e) Works guide, LXRP-WPA-WES: 29 Nov to 7 Dec 2020.
WPA (Western Program Alliance) (2020g) Occupation plan WPA-WES DEC OCCO, version 22, date of issue 26/11/2020
Appendices
Appendix A – Organisation structure as specified in TCP
Source: WPA project TCP adapted by OCI
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.
Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.
The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
[1]The standard gauge (1435 mm) network was predominantly used by interstate rail traffic.
[2]The broad gauge (1600 mm) network was used by Melbourne metropolitan and Victorian regional train services.
[3]The broad gauge lines would be temporarily removed from service by applying a track occupation.
[4]Circuit breakers were ‘turned off’ and an Uninterruptable Power Supply (UPS) also disconnected.
[5]Changeover is where vital signalling equipment and/or circuits are altered or renewed. The works were extensive.
[6]A Commissioning Log is log of key events or issues encountered by the commissioning team during commissioning of the works and will include pre-start briefs, shift changes and testing issues. The Commissioning Log is managed by the TIC.
[7]The level crossing protection would normally be activated by the level crossing control relay being de-energised.
[8]Rail worker positioned at a level crossing to activate crossing equipment if required for the passage of rail traffic.
[9]The standard gauge line was on the north side of the broad gauge lines.
[10] Distance from the mid-point of the Werribee Street Railway Station.
[11]A system composed of signalling apparatus that prevents conflicting movements by only allowing trains to receive authority to proceed when routes have been set, locked and detected in safe combinations.
[12]Equipment used to detect the presence of rail vehicles by counting the number of axles entering or leaving a location.
[13]Accredited by the Office of the National Rail Safety Regulator.
[14]Occupancy of a portion of rail track (an occupation) is allowed once a formal notice to occupy the track has been issued by the relevant rail authority. An occupation is usually issued to allow maintenance or other works on the rail track. Rail traffic is usually suspended, modified or restricted.
[15]Disconnection of an Uninterruptable Power Supply (UPS) that supplied power to the relay room was also required, which is not shown in Figure 11.
[16]A circuit that is energised from a source alternative to its design, for example through an intended temporary bridging arrangement, or by a current/voltage unintentionally fed into a circuit.
[18]Additional controls were also put in place between 4 December 2020 and 14 December 2020 to prevent a repetition of the occurrence at Cherry Street level crossing.
[19]Construction notes are instructions for implementation made by the signal designer when the drawings are produced.
[20]The MTM specification for signalling supply, construction, and installation referenced AS/NZS 3000: Wiring Rules, which in turn referenced AS/NZS 4836 (2001): Safe working on or near low-voltage and extra-low voltage electrical installations and equipment.
[21]The TCP stated that ‘all test straps and simulation equipment for testing shall be uniquely numbered and recorded on a test strap/equipment register.’ Further, the TCP stated that ‘temporary wiring and/or false feeds shall be recorded on the test copy and in the temporary jumper register.’ For the Werribee commissioning, a test strap register was used to record both test straps and temporary wiring. The signature space on the test copy stated ‘TEMPORARY JUMPER INSTALLED BY…’
[22]The railway engineering cadetship, an LXRP initiative, is a 3-year program initiative offering a pathway into the railway industry.
[23]VRIOG members consisted of VicTrack, V/Line Pty Ltd, MTM, Yarra Trams and the Department of Transport (Vic).
[24] In signalling installations where safety integrity is dependent upon the insulation between individual circuits, insulation tests on multicore and power cables are required to be made after their permanent installation and termination has been completed..
[25]A test to confirm wire continuity between the two terminals.
[26]A visual inspection to verify that the correct number of wires are connected at each termination point in accordance with the circuit diagrams and/or wiring diagrams and that the wire identification sleeves correspond with its termination position number.
[27] A null count is a visual inspection of all relay bases, fuses, links and terminations against the documentation sheets to ensure there is no surplus wiring to that specified.
[28] Test to determine that the circuit function is correctly energised/de-energised by the electrical “strapping” of the control device if the control device is not available to be electrically power operated. (eg “strap” front/back relay contacts, remove/replace fuses, links etc).
[30]A ‘yellow wire’ refers to a redundant wire that was identified with yellow tape and was to be removed.
[31]A termination made by inserting the stripped end of a stranded wire into a portion of the connector, which is then mechanically deformed by compressing (crimping) it tightly around the wire.
[32]The process for confirming that the installed system operates in accordance with the required signalling principles and safeworking rules and regulations. The Principles Tester confirms the integrity of the interlocking design by trying to defeat it, attempting to set up conflicting conditions, checking that all operational conditions that should be able to be simultaneously set up can be.
[33]A Hi-Rail is a road rail vehicle which can operate on rail tracks and a conventional road.
[34]A train used to test the operation of signalling equipment. Test trains were only planned to operate on the broad gauge.
[35]An IFC Signalling Test and Commissioning Plan for the Werribee Street level crossing removal was used for the audit.
[36]The relevant people were not defined in the audit report.
[37]The MTM audit report advised that corrective actions had been ‘discussed and agreed with relevant control owners and validated by relevant management for implementation’.
[38]Dual gauge track has 3 rails to accommodate both broad gauge and standard gauge rolling stock.
[39]This principle was stated in AS 7717 – 2016 section 2.15 and in the TCP, section‑1.3.2.
On the morning of 28 November 2020, a Jetstar Airways Airbus A320, registered VH-VGP (VGP), was conducting an approach to land at Ballina Byron Gateway Airport, New South Wales (NSW). At the same time, a Jabiru J230D, registered 24-7456 (7456), was conducting a private flight from Heck Field, Queensland, to Evans Head, NSW. About 12 NM south-west of Ballina Airport, the flight paths of the two aircraft inadvertently intersected. The crew of VGP received a traffic collision avoidance system (TCAS) traffic advisory alert prior to passing beneath 7456. The vertical separation between the two aircraft reduced to about 600 ft. Both the pilot of 7456 and the flight crew of VGP observed no lateral separation between the two aircraft.
What the ATSB found
The ATSB’s investigation identified that the pilot of 7456 was not aware of the presence of VGP, or that the two aircraft were converging, until having passed above VGP. The flight crew of VGP were also unaware of the presence of 7456 until they were alerted to the impending conflict by the aircraft’s TCAS. The ATSB also found the pilot of 7456 did not set the aircraft’s transponder to broadcast altitude data. Consequently, the TCAS on board VGP was unable to provide the flight crew with the necessary information to positively avoid the potential collision. The flight crew of VGP were unable to sight the aircraft until just before the flight paths intersected. The vertical separation between the two aircraft was influenced by chance alone as the flight crew of VGP and the pilot of 7456 were not aware of the altitude of the opposing aircraft.
The ATSB also found that the most recent regulatory review of the airspace surrounding Ballina Byron Gateway Airport, and subsequent periodic reviews, had not specifically considered the risks associated with aircraft transiting the airspace without taking off or landing at the airport (such as 7456).
What has been done as a result
The Ballina Airport broadcast area was expanded to a radius of 15 NM in January 2021 and an Airservices Australia surveillance flight information service (SFIS) began operating in August 2021. The SFIS provided traffic information to aircraft operating within the broadcast area on the airport’s common traffic advisory frequency.
The Civil Aviation Safety Authority (CASA) has advised that the current Ballina Airport airspace review (due for release in February 2022) utilises data that includes transiting aircraft. Additionally, CASA has developed an airspace risk modelling system (ARMS) that should provide an enhanced capability to consider transiting aircraft. CASA also advised that an initiative by the Australian Government to increase the uptake of automatic dependent surveillance broadcast (ADS-B) equipment in general aviation would result in improved aircraft detection.
While the proposed CASA actions have the potential to address the safety issue, this will largely depend on the conclusions of the current Ballina Airport airspace review and the effectiveness of the new ARMS. As such, the ATSB will monitor and assess their effect on the safety issue.
Safety message
Communication and self-separation in non-controlled airspace is one of the ATSB’s SafetyWatch priorities. Pilots can guard against similar issues to those highlighted by this incident by:
making the recommended broadcasts when in the vicinity of a non-controlled aerodrome
actively monitoring the common traffic advisory frequency while maintaining a visual lookout for other aircraft
ensuring transponders, where fitted, are selected to transmit altitude information.
The occurrence
On the morning of 28 November 2020, a Jetstar Airways Airbus A320-232 aircraft, registered VH‑VGP (VGP) (Figure 1), was conducting a scheduled passenger service from Melbourne Airport, Victoria, to Ballina Byron Gateway Airport (Ballina Airport), New South Wales (NSW). There were two flight crew, five cabin crew and 163 passengers on board. The captain was pilot flying (PF) and the first officer (FO) was pilot monitoring.[1]
Figure 1: VH-VGP
Source: Supplied
At about 1122 Eastern Daylight-saving Time,[2] when VGP was approximately 40 NM to the south‑west of Ballina Airport, the FO made a positional broadcast on the Ballina Airport common traffic advisory frequency (CTAF).[3] This CTAF was also used by two neighbouring airports and several neighbouring aircraft landing areas (ALAs) (see the section titled Common traffic advisory frequency).
On receipt of the broadcast from VGP, the Ballina Airport certified air/ground radio operator (CA/GRO) (see the section titled Certified air/ground radio service) responded. The CA/GRO confirmed that the flight crew were aware of two other passenger services, an Airbus A320 aircraft departing to the south from runway 06 at Ballina Airport, and a Boeing 737 inbound to Ballina Airport from the south.
At about the same time, a Jabiru J230D aircraft, registered 24-7456 (7456) (Figure 2), was conducting a private visual flight rules flight from Heck Field ALA, Queensland, to Evans Head ALA, NSW. There was one pilot and one passenger on board. At 1124:49, the pilot of 7456 made a broadcast on the shared CTAF, addressed to Lismore traffic, advising that the aircraft was 4 NM to the east of Lismore at 5,300 feet and descending. The flight crew of VGP did not respond to (or recall hearing) this broadcast.
Figure 2: 24-7456
Source: Andrei Bezmylov
Meanwhile, VGP continued tracking towards Ballina Airport via the waypoint[4] OPESO, descending to an altitude of about 3,200 feet in preparation for the required navigation performance[5] approach for runway 06. Prior to crossing the OPESO waypoint, the flight crew of VGP received a traffic collision avoidance system (TCAS) proximate traffic alert for an unidentified aircraft at an unspecified altitude in the 11 o’clock[6] position relative to VGP (see the section titled Traffic collision avoidance system). Unbeknown to the flight crew of VGP, the proximate traffic was 7456 tracking in a southerly direction towards Evans Head (Figure 3).
Figure 3: VH-VGP and 24-7456 tracks
Source: Google Earth, annotated by the ATSB
The pilot of 7456 did not recall hearing the earlier CTAF broadcast from VGP and was unaware that the two aircraft were on converging tracks. 7456 was fitted with a transponder that could transmit the aircraft’s altitude (see the section titled Transponder). However, 7456’s transponder was selected ‘ON’ (not ALT) and was not transmitting the altitude of the aircraft.
Without the altitude information, the TCAS on board VGP could only display the relative bearing and distance of 7456.
The flight crew of VGP attempted, unsuccessfully, to visually acquire the proximate traffic (visibility was greater than 10 km and there was no cloud at the time). The crew later reported experiencing ‘tunnel vision’ while conducting the visual search. They did not attempt to contact the traffic on the CTAF.
At 1128:18, VGP’s flight crew received a TCAS traffic advisory. The flight crew maintained their visual scan and continued with the approach to runway 06.
At 1128:38, the flight crew of VGP made a broadcast on the shared CTAF and advised Ballina traffic, and the Boeing 737 aircraft in the vicinity, that VGP had just passed waypoint OPESO. The pilot of 7456 did not respond to, or recall hearing, this broadcast.
The data obtained from VGP’s quick access recorder and the OzRunways program used by the pilot of 7456, indicated that, at 11:28:41 and 12 NM south-west of Ballina Airport, the tracks of VGP and 7456 intersected, with vertical separation between the two aircraft reducing to about 600 ft. The flight crew of VGP sighted 7456 just prior to passing below the aircraft. The pilot of 7456 sighted VGP shortly after passing above the aircraft. Both the pilot of 7456 and the flight crew of VGP observed no lateral separation between the two aircraft (Figure 4).
Figure 4: : Recorded flight paths of VH-VGP and 24-7456
Source: Google Earth, annotated by the ATSB
At 1128:59, the flight crew of VGP contacted the crew of the Boeing 737 inbound to Ballina Airport on the shared CTAF to advise that they had experienced a traffic advisory, and the involved aircraft was headed in the direction of the Boeing 737.
A short time later, VGP landed at Ballina Airport while 7456 continued on to Evans Head ALA.
The captain held an Air Transport Pilot Licence (ATPL) (Aeroplane) and had a total flying time of 13,935 hours, having flown 66.5 hours in the previous 90 days. The captain was familiar with Ballina Airport but had not operated there often. The captain’s last flight to Ballina Airport took place in June 2019.
The FO held an ATPL (Aeroplane) and a total flying time of 4,830 hours, having flown 10.5 hours in the previous 90 days. The FO was somewhat familiar with Ballina Airport having operated there twice before the incident flight. The FO’s last flight to Ballina Airport took place the day prior to the incident.
Pilot 24-7456
The pilot held a recreational pilot certificate and a total flying time of 775 hours, having flown 56 hours in the previous 90 days. The pilot was familiar with Ballina Airport and transited the surrounding airspace about eight times a year. The pilot reported being unfamiliar with the radio phraseology commonly used by passenger transport flight crew, including reference to waypoints such as OPESO.
Ballina Byron Gateway Airport
Ballina Byron Gateway Airport is a certified airport situated approximately 3 NM from the city of Ballina, NSW. The airport has an elevation of 7 feet above mean sea level (AMSL) and a single sealed runway orientated in a 062°-242° magnetic direction (Figure 5). The airport had GPS‑based instrument approaches and a non-directional beacon ground-based navigation aid.
Figure 5: Ballina Byron Gateway Airport
Source: Airservices Australia
Airspace and traffic services
Ballina Airport was located within non‑controlled Class G airspace which extended from the ground surface to 8,500 feet AMSL. The airport did not have a control tower and was not supported by air traffic control (a non-controlled airport).
Overlying the non‑controlled airspace was Class C controlled airspace which extended up to flight level (FL) 180,[7] and controlled Class A airspace above that. An air traffic information and separation service was provided within the Class C airspace and a separation service was provided within the Class A airspace. A restricted area existed approximately 5 NM south of the airport (the aircraft involved in this incident were clear of this area).[8]
The non‑controlled airspace surrounding Ballina Airport was available for use by aircraft operating under visual flight rules and instrument flight rules. No separation service was provided to aircraft operating in this airspace with pilots responsible for making themselves aware of nearby aircraft and maintaining self‑separation.
The primary method of traffic separation at Ballina Airport was visual and relied on pilots using ‘alerted see-and-avoid’[9]practices. A broadcast area was in place requiring aircraft to use a radio on the Ballina Airport CTAF when operating within a 10 NM radius of the airport.
Common traffic advisory frequency
The Ballina Airport CTAF was a designated frequency on which pilots made positional broadcasts when operating in the vicinity of the airport. The Ballina Airport CTAF was shared with neighbouring airports and ALAs Casino, Lismore and Evans Head to assist traffic coordination and enhance the situational awareness of pilots operating within the surrounding airspace (Figure 6).
Figure 6: Shared common traffic advisory frequency
Source: Airservices Australia, annotated by the ATSB
When operating within the Ballina Airport broadcast area, pilots were required to make mandatory transmissions when arriving or departing from the airport, and when flying through the broadcast area.
When operating outside of the Ballina Airport broadcast area, but within the vicinity of the other non‑controlled airports on the shared CTAF, pilots were required to make a broadcast whenever it was reasonably necessary to do so to avoid a collision, or the risk of collision, with another aircraft. There were also several recommended positional broadcasts (Table 1).
Table 1: Recommended positional broadcasts in the vicinity of a non-controlled airport
Recommended calls in all circumstances
Situation
Broadcast
The pilot intends to take-off
Immediately before, or during taxiing
The pilot is inbound to an aerodrome
10 NM from the aerodrome, or earlier, commensurate with aeroplane performance and pilot workload, with an estimated time of arrival for the aerodrome
The pilot intends to fly through the vicinity of, but not land at, a non-controlled aerodrome
10 NM from the aerodrome, or earlier, commensurate with aeroplane performance and pilot workload, with an estimated time of arrival
Recommended calls dependent on traffic
Situation
Broadcast
The pilot intends to enter a runway
Immediately before entering a runway
The pilot is ready to join the circuit
Immediately before joining the circuit
The pilot intends to make a straight-in approach
On final approach at not less than 3 NM from the threshold
The pilot intends to join on base leg
Prior to joining on base
During an instrument approach when:
a. departing final approach fix or established on final approach segment inbound
b. terminating the approach, commencing the missed approach
Including details of position and intentions that are clear to all pilots (both instrument flight rules and visual flight rules)
The aircraft is clear of the active runway(s)
Once established outside the runway strip
Source: Civil Aviation Advisory Publication 166-01 V4.2 (Feb 2019) with minor amendments by the ATSB
Certified air/ground radio service
At the time of the incident, Ballina Airport was one of two airports in Australia to have a certified air/ground radio service (CA/GRS) in operation.
According to CASA’s guidelines for a CA/GRS, the primary purpose of the service was to enhance the safety of passenger operations by providing all pilots with information to enhance their ability to see-and-avoid potentially conflicting traffic.
The information provided to pilots included:
frequency confirmation
traffic information on first call
airport weather
other advice to facilitate aeronautical safety and efficiency
The Ballina Airport CA/GRS commenced operations in March 2017 in response to the increasing number of aircraft movements at the airport. The service was delivered by the airport operator, via a third-party contractor, and had formal CASA approval. The service was delivered by a certified air/ground radio operator located at the airport.
At the time of the incident, the service was provided to all aircraft operating within the Ballina Airport broadcast area of 10 NM, during passenger service operations (greater than 30 seats) between the hours of 0800-1800 local time.
The CA/GRS did not provide a traffic separation service to aircraft as would occur at airports located within Class D or higher airspace (controlled airports).
Regulatory oversight
The Airspace Act 2007 assigned the administration and regulation of Australian administered airspace to the Civil Aviation Safety Authority (CASA). As part of this function, CASA was required to undertake regular reviews to determine if:
existing classifications of ‘volumes of airspace’ were appropriate
existing air navigation services and facilities provided to volumes of airspace were appropriate
there was safe and efficient use of airspace, and equitable access to that airspace for all users
any identifiable risk factors were present
Ballina airport airspace review
At the time of this occurrence, CASA had last completed a review of the airspace surrounding Ballina Airport in July 2015. The purpose of that airspace review was to examine the airspace classification within 20 NM of the airport from ground level to 8,500 feet AMSL.
The objective of the review was to assess the risk levels for passenger transport operations to determine if the airspace classification was appropriate and whether an air traffic service was required. The options considered during the review included upgrading the airspace to Class D or higher classification (a controlled airport).
The Australian Airspace Policy Statement (AAPS) contained airspace review criteria thresholds for volumes of airspace around airports (Table 2). If an airport met or exceeded any of the thresholds for a classification, then CASA was required to undertake a review of the volume of airspace in question. This review was to consider public, industry and agency comments, forecast future traffic levels, and any significant risk mitigators before finalising an airspace determination.
Table 2: Airspace criteria thresholds AAPS 2015
Class B
Class C
Class D
Service provider
ATC
ATC
ATC
Total annual aircraft movements
750,000
400,000
80,000
Total annual PTO aircraft movements
250,000
30,000
15,000
Total annual PTO passengers
25 million
1 million
350,000
Source: Civil Aviation Safety Authority
The 2015 airspace review found that the Ballina Airport exceeded the AAPS passenger criteria threshold for Class D airspace with 437,940 passenger movements recorded in 2014. However, it also found that both passenger transport aircraft movements and total aircraft movements for 2014 were significantly below the Class D trigger criteria. Therefore, CASA decided not to upgrade Ballina to a controlled airport on the basis that:
Considering the total aircraft movements, total passenger transport aircraft movements, stakeholder feedback and aviation safety incident reports CASA considers Class D or higher would currently be a disproportionate response to the identified airspace issues at Ballina.
The ATSB noted that, in reaching that conclusion, the airspace review had not assessed risks associated with aircraft transiting the airspace surrounding Ballina Airport without taking off or landing at the airport (that is, transiting aircraft such as 24-7456 was in this occurrence). While the review included analysis of reportable events near Ballina Airport from 2009 to 2014, it did not specifically consider the involvement of transiting aircraft in those events or the influence such aircraft may have on future separation events to properly assess the risks involved. Of the 11 separation events in the area that the review identified, 6 involved a passenger transport service. However, while CASA advised that all of these occurrences were considered, the review did not identify that 2 of those 6 also involved a conflict with a transiting aircraft.
The review primarily focused on aircraft movements (the total number of take-offs and landings at an airport) specified in the AAPS threshold criteria. Movement data for Ballina Airport was sourced from Airservices Australia (Airservices) and the Bureau of Infrastructure, Transport and Regional Economics.
While Airservices had some data on transiting aircraft, it was not readily available as computational analysis of this data was required to extract information on aircraft operating under the visual flight rules and/or aircraft operating without a flight plan. Notwithstanding these difficulties, data for transiting aircraft was available, but not obtained or analysed in the 2015 review.
In March 2020, CASA commenced another review of the airspace, but following the expansion of the Ballina Airport broadcast area, decided to defer its finalisation. At the time of writing, a final report had not been released.
Periodic assessments
In addition to the 2015 airspace review, CASA conducted periodic risk assessments of Ballina Airport and the surrounding airspace. The information considered for these assessments included:
aircraft and passenger movements
incident reports
IFR to VFR traffic ratios
stakeholder feedback
previous risk assessments.
Records provided by CASA indicated eight documented risk assessments between July 2015 (when the 2015 airspace review was published) and the time of the incident. The last of these assessments was completed in June 2020. The analysis recorded within these assessments primarily focused on aircraft and passenger movements. There was no reference to transiting aircraft, either in terms of occurrences involving such aircraft or overall numbers/movements.
Comments included in this assessment stated that passenger transport aircraft and passenger numbers had declined at the airport, probably due to the impact of COVID-19,[10] but passenger numbers continued to exceed the AAPS 2018 threshold by 19 per cent. The assessment indicated three reported incidents had occurred in the vicinity of the airport but provided no detail about those incidents. The last periodic assessment concluded that the risk level was lower than that of the previous assessment.
Previous events
A search of the ATSB database identified that between 1 January 2010 and 28 November 2020, there were 20 separation events involving passenger transport services (including this incident) within a radius of approximately 20 NM of Ballina Airport below 8,500 feet AMSL (Table 3). Of those 20 events, seven involved a conflict between an aircraft transiting the airspace and a passenger transport service approaching or departing from Ballina Airport (Table 4). Two of these events occurred prior to the publication of the 2015 CASA airspace review.
Table 3: Ballina separation events involving passenger transport services
Year
Total
Not involving transiting aircraft
Involving transiting aircraft
2020
1
0
1
2019
4
3
1
2018
4
2
2
2017
2
2
0
2016
2
2
0
2015
1
0
1
2014
0
0
0
2013
1
0
1
2012
0
0
0
2011
3
2
1
2010
2
2
0
Total
20
13
7
Source: ATSB
Table 4: Separation events involving passenger transport service and transiting aircraft
Year
Aircraft 1
Aircraft 2
Overview
2020
Airbus A320
Jabiru J230D
During approach, the crew of the Airbus A320 received a TCAS TA on the Jabiru J230 on a crossing path.
2019
Airbus A320
Cessna 180
During approach, an Airbus A320 came into close proximity with the Cessna 180. No radio broadcasts were heard from the light aircraft.
2018
Boeing 737 & Airbus A320
Diamond DA40
During approach, a Boeing 737 and Airbus A320 came into close proximity with a Diamond DA40. There were no radio broadcasts identified from the crew of the DA40.
2018
Jetstream Series 3206
Aerospatiale Ind AS350B2
During approach, the crew of a Jetstream Series 3206 observed an Aerospatiale AS.350 helicopter on a reciprocal track. Both aircraft turned to increase separation. The crew of the 3206 did not hear any radio broadcasts from the AS.350.
2015
Airbus A320
Cessna 182
During approach, the crew of an Airbus A320 coordinated separation from a Cessna 182 that was in the vicinity. However, the pilot of the Cessna 182 did not follow their broadcast intentions, resulting in the crew of the Airbus A320 conducting a missed approach.
2013
Airbus A320
Unknown
During take-off, the crew of the Airbus A320 heard a broadcast from an aircraft transiting through Ballina airspace. The crew subsequently observed a TCAS return but were unable to sight the inbound aircraft.
2011
Airbus A320
Piper PA20
While an Airbus A320 was in a holding pattern an instrument flight rules aircraft in the vicinity did not track as expected. The A320 was turned early to ensure that separation was maintained.
Source: ATSB
Aircraft systems
Traffic collision avoidance system
A traffic collision avoidance system (TCAS), as fitted to VGP, interrogates the transponders (see the section titled Transponder) of nearby aircraft and uses this information to calculate the relative range and altitude of this traffic. The system provides a visual representation of this information to the flight crew as well as issuing alerts should a traffic issue be identified. These alerts include:
Proximate traffic – an alert issued when an aircraft is within a range of less than 6 NM and 1,200 ft, or a range of 6 NM if the traffic is not transmitting altitude information. Depicted as a white filled diamond on the navigation display (ND)
Traffic advisory (TA) – an alert issued when the detected traffic may result in a conflict (the closest point of separation is about 40 seconds away on the current projected flight paths). Depicted as an amber filled circle on the ND and an aural alert. Pilots are expected to initiate a visual search for the traffic causing the TA (the operator’s procedures required flight crew not to perform a manoeuvre based solely on a TA).
Resolution advisory (RA) – a manoeuvre, or a manoeuvre restriction, calculated by the TCAS to avoid a collision (the closest point of separation is approximately 25 seconds away or less). Depicted as a red filled square on the ND and vertical speed orders on the primary flight display. A series of aural alerts will also sound. Pilots are expected to respond immediately to an RA.
Due to its method of operation, a TCAS cannot detect aircraft that are not equipped with a transponder (or switched off). Additionally, the system is unable to issue an RA for traffic that is not fitted with an altitude reporting transponder (mode C or S), or in circumstances where the mode C or S transponder on board the conflicting traffic is not transmitting altitude information (as was the case with 7456).
Transponder
A transponder is a receiver/transmitter which transmits an automatic reply upon receiving an interrogation request. A manual ‘ident’ transmission can also be initiated by the pilot. The information transmitted by a transponder is dependent on the ‘mode’ of equipment fitted and the mode of transmission selected by the pilot.
The transponder fitted to 24-7456 was capable of operating in mode 3A and 3C. In mode 3A (ON) the equipment would transmit the configured transponder code only. In mode 3C (ALT) the equipment would transmit the aircraft’s altitude in addition to the configured transponder code.
The pilot of 24-7456 had elected to set the transponder to mode A only so the altitude of the aircraft was not being transmitted. The pilot incorrectly believed there were no requirements relating to the use of modes 3A and 3C.
The Aeronautical Information Publication (AIP) contained information on the operation of aircraft transponders. AIP ENR 1.6 paragraph 7.1.2 stated:
Unless advised otherwise by ATC, pilots of Mode 3A or Mode S transponder equipped aircraft operating in Australian airspace must activate their transponders, and where a Mode C capability is also available it must be activated simultaneously with Mode 3A.
Note: Pilots must ensure that transponders and ADS-B transmitters are activated and the altitude function is selected as:
a. primary radar coverage only exists within 50NM of major airports and the remainder of the ATS surveillance system relies on SSR transponder and ADS-B transmitter information, and b. TCAS relies on transponder information for its pilot alerting and collision avoidance functions.
AIP GEN 1.5 paragraph 7.1.2 stated:
Pilots of transponder-equipped aircraft should ensure their transponder is switched to ON/ALT (Mode C) at all times.
Human factors
The ATSB investigation considered a range of human factors that could have influenced the decisions and actions of the pilots involved. No indicators that increased the risk of any of the individuals experiencing a level of fatigue known to influence performance were found. The following factors, however, were likely to have had an influence.
cognitive tunnelling
human visual system limitations.
Cognitive tunnelling is an inattentional blindness where an individual becomes overly‑focused on some variable other than the present environment (Mack & Rock 1998). Cognitive tunnelling may also impact an individual’s decision-making processes (Bell et al 2005). The comments by VGP’s flight crew about ‘tunnel vision’ after they received the TCAS TA was a reference to this factor.
Limitations associated with the human visual system include:
empty field myopia – in an empty field, such as blue sky, the eye will focus at around 56 cm which may reduce the chance of identifying a distant object
a lack of relative motion when on a collision course – the human visual system is less effective at detecting stationary objects than moving objects. Because of the geometry of collision flightpaths, from each pilot’s point of view, the converging aircraft will grow in size while remaining fixed at a particular point in the windscreen
visual angle – an approaching aircraft at high speed will present a small visual angle until a short time before impact. Limitations associated with visual acuity mean this small visual angle may make it impossible for a pilot to detect the aircraft in time to take evasive action (Hobbs 1991).
All these limitations impair the effectiveness of ‘see-and-avoid’ practices, the primary method of self-separation in uncontrolled airspace, which requires pilots to conduct a visual search to ‘see-and-avoid’ potentially conflicting traffic.
An ‘unalerted’ search is one where reliance is entirely on the pilot searching for, and sighting, another aircraft without prior knowledge of its presence. On the other hand, an ‘alerted’ search is one where the pilot is alerted to another aircraft’s presence, typically via radio communications or aircraft based alerting systems. An alerted search is likely to be eight times more effective than an unalerted search (Hobbs 1991).
On 28 November 2020, the flights paths of Airbus A320, VH-VGP, and Jabiru J230D, 24-7456, intersected about 12 NM south-west of Ballina Byron Gateway Airport, with the vertical separation between them reducing to about 600 ft. The aircraft were outside the airport’s broadcast area and within non‑controlled Class G airspace. That meant that the pilots were responsible for safe separation using radio communications and collision avoidance aids to support ‘see-and-avoid’ practices.
Communications and collision avoidance aids
The flight crew of VGP did not recall hearing the broadcast from 7456 prefixed with ‘Lismore traffic’ on the common traffic advisory frequency (CTAF). That prefix (a different airport to their destination, Ballina) probably did not trigger their auditory attention. In any case, they were not aware of 7456 until alerted to a conflict by the aircraft’s traffic collision avoidance system (TCAS).
Similarly, the pilot of 7456 did not recall hearing broadcasts from VGP on the CTAF. Additionally, the pilot was not familiar with phraseology commonly used in passenger transport operations, including reference to instrument approach waypoints such as OPESO. That probably contributed to the pilot not registering those broadcasts and being unaware of the presence of VGP before the incident.
The pilot of 7456 incorrectly selected mode 3A (instead of the required 3C) on the aircraft’s transponder resulting in altitude data not being transmitted. As the aircraft approached VGP, its TCAS issued the conflict alert and, subsequently, a traffic advisory alert with the relative bearing and distance of 7456. However, the TCAS could not indicate the approaching aircraft’s altitude or provide a resolution advisory, significantly disadvantaging the flight crew in managing the situation.
See-and-avoid
The circumstances and the restrictions imposed on the available electronic aids, particularly TCAS functionality, were impediments to effectively applying see-and-avoid practices.
Since the pilot of 7456 was not aware of VGP, seeing and avoiding it depended on the success of ‘unalerted’ visual searches by the pilot. Although visibility was greater than 10 km with no cloud in the area, any searches were unsuccessful as the pilot only sighted VGP after passing above it.
On the other hand, VGP’s TCAS alerted the flight crew to 7456. However, their ‘alerted’ search was unsuccessful in part due to the limitations associated with the human visual system and the absence of altitude data. Additionally, the effects of cognitive tunnelling, together with the rapid sequence of events following the TCAS alerts, possibly resulted in them not considering options such as contacting the approaching aircraft via radio on the CTAF. With no TCAS resolution advisory manoeuvre available, they continued visually searching, sighting 7456 moments before it passed and too late to take any action to avoid a potential collision.
Therefore, the vertical separation of about 600 ft when the aircraft passed was entirely fortuitous.
This incident, together with previous events involving transiting aircraft shows that separation occurrences, with potentially serious consequences, can and do occur (Table 4) in the airspace encompassing the approach and departure flight paths of large transport aircraft operating at Ballina Airport.
Airspace classification
The objective of the 2015 Civil Aviation Safety Authority (CASA) review of the airspace surrounding Ballina Byron Gateway Airport was to assess the level of risk posed to passenger transport services and determine if the airspace classification was appropriate. The review considered total aircraft movements (including passenger transport aircraft) at the airport, some reportable events near the airport and stakeholder feedback and determined that a Class D or higher airspace classification was not appropriate. Significantly, transiting aircraft movements were not considered, primarily due to difficulty in extracting this data.
However, the review had not specifically considered the risks associated with aircraft transiting the airspace without taking off or landing at Ballina Airport. Recognising that such a consideration at the time of the review would have only identified 2 occurrences associated with transiting aircraft, additional occurrences in the intervening years indicate that the risk of a proximity event in these circumstances may be significant. However, opportunities to consider such risk events in the periodic risk assessments of the airspace since the 2015 review had not been taken.
Capturing these tangible risks through the airspace review and periodic assessment mechanisms would result in a more accurate and realistic risk assessment. Such a risk assessment would, in turn, better inform an assessment of the appropriate airspace classification.
When operating in non-controlled airspace (such as the current Class G airspace around Ballina), whether under the instrument or visual flight rules, pilots hold responsibility for separation from other aircraft. A review of past occurrences indicates that self-separation using broadcast traffic advice has been a largely reliable procedure.
The ATSB does however note that the effectiveness of the current pilot-separation method relies on individual pilots:
recognising a potentially unsafe situation
formulating an effective separation plan that often requires coordination with the occupants of the other involved aircraft.
While on this occasion one of the involved aircraft was equipped with TCAS, this process is almost exclusively reliant on individual human actions without other mechanisms potentially acting as a safeguard and/or safety redundancy, and as such subject to human error, even when it involves experienced pilots. Furthermore, such errors often increase under high workload associated with, for example, instrument flying approach procedures, low experience or a busy airspace environment.
Of note, the airspace surrounding Ballina Airport accommodates a complex mix of aircraft types and operations, including high-capacity passenger transport, while also being located close to several other non‑controlled airports.
In that context, while the available evidence in this investigation does not support a conclusion that the present self‑separation system is unsafe, there is an opportunity to potentially reduce safety risk further.
The ATSB therefore supports systemic enhancements to the overall air traffic system that have been assessed by regulatory and air traffic specialists, in keeping with their obligations as providing a net overall safety increase. Key examples of such enhancements include:
the increased use of controlled airspace and ADS‑B aircraft surveillance data (both by air traffic services and in‑cockpit)
improved monitoring of air traffic movements (both quantity and complexity) to assist the identification of increasing risk areas.
With respect to this occurrence, had the aircraft been operating in controlled airspace the crew of VGP would have, at a minimum, received traffic information from air traffic control on 7456 and may have been positively separated.
Findings
ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition, ‘other findings’ may be included to provide important information about topics other than safety factors.
Safety issues are highlighted in bold to emphasise their importance. A safety issue is a safety factor that (a) can reasonably be regarded as having the potential to adversely affect the safety of future operations, and (b) is a characteristic of an organisation or a system, rather than a characteristic of a specific individual, or characteristic of an operating environment at a specific point in time.
These findings should not be read as apportioning blame or liability to any particular organisation or individual.
From the evidence available, the following findings are made with respect to the separation occurrence involving Airbus A320-232, VH-VGP and Jabiru J230D, 24-7456 about 12 NM south‑west Ballina Byron Gateway Airport, New South Wales on 28 November 2020.
Contributing factors
The mode of the transponder on board 24-7456 was not selected to transmit altitude data, which resulted in VH-VGP’s traffic collision avoidance system (TCAS) not indicating the approaching aircraft’s altitude or providing a resolution advisory.
The pilot of 24-7456 did not recall hearing broadcasts from VH-VGP and remained unaware of the other aircraft until passing above it.
The flight crew of VH-VGP did not recall hearing the broadcast from 24-7456 when it was near Lismore and remained unaware of the aircraft until receiving a TCAS alert. However, they did not know the approaching aircraft’s altitude, did not attempt to make radio contact and only sighted it moments before the aircraft passed.
The vertical separation between the aircraft when their flight paths inadvertently intersected reduced to about 600 ft, which was entirely fortuitous as the pilots of neither aircraft had been able to manage aircraft separation in the circumstances.
Other factors that increased risk
The Civil Aviation Safety Authority review and periodic risk assessments of the airspace surrounding Ballina Byron Gateway Airport did not include data for aircraft transiting the airspace without using the airport. Therefore, the risk associated with occurrences such as this one were not specifically considered when assessing the appropriate airspace classification. (Safety issue)
Safety issues and actions
Central to the ATSB’s investigation of transport safety matters is the early identification of safety issues. The ATSB expects relevant organisations will address all safety issues an investigation identifies.
Depending on the level of risk of a safety issue, the extent of corrective action taken by the relevant organisation(s), or the desirability of directing a broad safety message to the aviation industry, the ATSB may issue a formal safety recommendation or safety advisory notice as part of the final report.
All of the directly involved parties are invited to provide submissions to this draft report. As part of that process, each organisation is asked to communicate what safety actions, if any, they have carried out or are planning to carry out in relation to each safety issue relevant to their organisation.
Descriptions of each safety issue, and any associated safety recommendations, are detailed below. Click the link to read the full safety issue description, including the issue status and any safety action/s taken. Safety issues and actions are updated on this website when safety issue owners provide further information concerning the implementation of safety action.
Safety issue description: The Civil Aviation Safety Authority review of the airspace surrounding Ballina Byron Gateway Airport did not include data for aircraft transiting the airspace without using the airport. Therefore, the risk associated with occurrences such as this one were not specifically considered when assessing the appropriate airspace classification.
Glossary
AIP Aviation information publication
ALA Aircraft landing area
AMSL Above mean sea level
ATC Air traffic control
ATSB Australian Transport Safety Bureau
CA/GRS Certified air/ground radio service
CASA Civil Aviation Safety Authority
CTAF Common traffic advisory frequency
EDT Eastern daylight-saving time
FDR Flight data recorder
FL Flight level
FO First officer
NM Nautical mile
NSW New South Wales
PF Pilot flying
PM Pilot monitoring
RA Resolution advisory
SFIS Surveillance flight information service
TA Traffic advisory
TCAS Traffic collision avoidance system
UTC Coordinated universal time
Sources and submissions
Sources of information
The sources of information during the investigation included:
the flight crew of VH-VGP and pilot of 24‑7456
the CA/GRO and CA/GRS service provider
Jetstar Airways
Ballina Byron Gateway Airport
Avdata
Bureau of Infrastructure and Transport Research Economics
Civil Aviation Safety Authority
Airservices Australia
References
Bell, M, Facci, E, & Nayeem, R 2005, Cognitive Tunnelling, Aircraft-Pilot Coupling Design Issues and Scenario Interpretation Under Stress in Recent Airline Accidents, 2005 International Symposium on Aviation Psychology, 45-49
Hobbs A 1991, Limitations of the See-and-Avoid Principle, Australian Transport Safety Bureau
Mack A & Rock I 1998, Inattentional blindness, MIT Press Cambridge MA
Submissions
Under section 26 of the Transport Safety Investigation Act 2003, the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. That section allows a person receiving a draft report to make submissions to the ATSB about the draft report.
A draft of this report was provided to:
the crew of VH-VGP and pilot of 24-7456
Jetstar Airways
Ballina Byron Gateway Airport
Civil Aviation Safety Authority
Airservices Australia.
Submissions were received from:
the crew of VH-VGP
Civil Aviation Safety Authority
Airservices Australia
The submissions were reviewed and, where considered appropriate, the text of the report was amended accordingly.
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.
Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.
The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
Preliminary report
Report release date: 01/03/2021
This preliminary report details factual information established in the investigation’s early evidence collection phase and has been prepared to provide timely information to the industry and public. Preliminary reports contain no analysis or findings, which will be detailed in the investigation’s final report. The information contained in this preliminary report is released in accordance with section 25 of the Transport Safety Investigation Act 2003.
The occurrence
On 28 November 2020, a Jetstar Airways Airbus A320-232 aircraft, registered VH-VGP (VGP), was conducting a regular public transport (RPT) flight from Melbourne Airport, Victoria, to Ballina Byron Gateway Airport (Ballina Airport), New South Wales (NSW). At about 1122 Eastern Daylight-saving Time,[1] when VGP was approximately 40 NM to the south-west of Ballina Airport, the flight crew made a broadcast on the common traffic advisory frequency (CTAF).[2] This CTAF is shared with two neighbouring airports and several neighbouring aircraft landing areas (ALAs) including Evans Head (Figure 1).
Figure 1: CTAF Airports
Source: Airservices Australia, annotated by the ATSB
On receipt of VGP’s broadcast, the Ballina Airport certified air/ground radio operator (CA/GRO) (see Certified air/ground radio service section) contacted the flight crew of VGP. The CA/GRO confirmed that the flight crew were aware of an RPT A320 aircraft departing to the south from runway 06 at Ballina Airport, and an RPT Boeing 737 inbound to Ballina Airport from the south.
At about the same time, a Jabiru J230D aircraft, registered 24-7456 (7456), was conducting a private visual flight rules flight from Heck Field ALA, Queensland, to Evans Head ALA, NSW. At 1124:49, the pilot of 7456 made a broadcast on the CTAF, addressed to Lismore traffic, advising that the aircraft was 4 NM to the east of Lismore at 5,300 feet and descending. The flight crew of VGP did not respond to, or recall hearing, this broadcast.
Meanwhile, VGP continued its track towards Ballina Airport via the waypoint[3] ‘OPESO’, descending to an altitude of about 3,200 feet in preparation for the required navigation performance[4] approach for runway 06. Prior to crossing the OPESO waypoint, the flight crew of VGP received a traffic collision avoidance system (TCAS) proximate traffic alert for an unidentified aircraft at an unspecified altitude in the 11 o’clock[5] position relative to VGP (see Traffic collision avoidance system section). Unbeknown to the flight crew of VGP, the proximate traffic was probably 7456 tracking in a southerly direction towards Evans Head (Figure 2).
Figure 2: VH-VGP and 24-7456 tracks
Source: Google Earth, annotated by the ATSB
The pilot of 7456 had not heard the earlier CTAF broadcast from VGP and was unaware that the two aircraft were on converging tracks. 7456 was fitted with a transponder that could transmit the aircraft’s altitude. However, 7456’s transponder was selected ‘ON’ (not ALT) and was not transmitting the altitude of the aircraft (without the altitude information, the TCAS on board VGP could only display the relative horizontal position of 7456).
At that time, there was no cloud and visibility was greater than 10 km. The flight crew of VGP attempted, unsuccessfully, to visually acquire the proximate traffic, but did not attempt to contact the traffic on the CTAF.
At 1128:17, VGP’s flight crew received a TCAS traffic advisory. The flight crew maintained their visual scan and continued with the approach to runway 06.
At 1128:38, the flight crew of VGP made a broadcast on the shared CTAF and advised Ballina traffic, and the Boeing 737 aircraft in the vicinity, that VGP had just passed waypoint OPESO. The pilot of 7456 did not respond to, or recall hearing, this broadcast.
The data obtained from VGP’s quick access recorder and the OzRunways program used by the pilot of 7456, indicates that, at approximately 12 NM south west of Ballina Airport, the tracks of VGP and 7456 intersected, with vertical separation between the two aircraft reducing to about 600 feet. The flight crew of VGP sighted 7456 just prior to passing below the aircraft. The pilot of 7456 sighted VGP shortly after passing above the aircraft. Both the pilot of 7456 and the flight crew of VGP observed no lateral separation between the two aircraft (Figure 3).
Figure 3: Recorded flight paths of VH-VGP and 24-7456
Source: Google Earth, annotated by the ATSB
At 1128:59, the flight crew of VGP contacted the crew of the Boeing 737 inbound to Ballina Airport on the shared CTAF to advise that they had experienced a traffic advisory, and the involved aircraft was now headed in the direction of the Boeing 737.
A short time later, VGP landed at Ballina Airport while 7456 continued on to Evans Head ALA.
Context
Airspace
Ballina Airport is located within uncontrolled Class G airspace. Overlying this airspace is Class C controlled airspace with a base of 8,500 feet above mean sea level.
The airspace surrounding Ballina Airport is available for use by aircraft operating under visual flight rules and instrument flight rules with significant recreational and sport aviation activity in the area. Ballina Airport is also serviced by several low and high capacity regular public transport operators.
Common traffic advisory frequency
The Ballina Airport CTAF is a designated frequency on which pilots make positional broadcasts when operating in the vicinity of the airport. The Ballina Airport CTAF is shared with neighbouring airports and ALAs in order to aid with traffic coordination and enhance the situational awareness of pilots operating within the surrounding airspace.
Pilots are required to make a CTAF broadcast whenever it is reasonably necessary to do so to avoid a collision, or the risk of collision, with another aircraft. Recommended positional broadcasts are listed in the table below (Figure 4)
Figure 4: CTAF recommended positional broadcasts
Source: Civil Aviation Safety Authority, modified by the ATSB
Certified air/ground radio service
Ballina Airport is one of only two airports in Australia to have a certified air/ground radio service (CA/GRS) in operation. A CA/GRS is a radio information service that is operated at a non-controlled airport and is provided by the airport operator.
The Ballina Airport CA/GRS commenced operations in March 2017 in response to the increasing number of aircraft movements at the airport. The purpose of the service is to provide pilots with operational information relevant to the airport to aid with decision making. The information provided includes:
frequency confirmation
traffic information on first call
airport weather
other advice to facilitate aeronautical safety and efficiency.
At the time of the incident, the service was provided to all aircraft operating within a designated broadcast area of 10 NM, during RPT operations (greater than 30 seats) between the hours of 0800-1800 local time.
Traffic collision avoidance system
A traffic collision avoidance system, as fitted to VGP, interrogates the transponders[6] of nearby aircraft and uses this information to calculate the relative range and altitude of this traffic. The system provides a visual representation of this information to the flight crew as well as issuing alerts should a traffic issue be identified. These alerts include:
Proximate traffic – an alert issued when an aircraft is within a range of less than 6 NM and 1200 feet, or a range of 6 NM if the traffic is not transmitting altitude information.
Traffic advisory (TA) – an alert issued when the detected traffic may result in a conflict. Pilots are expected to initiate a visual search for the traffic causing the TA.
Resolution advisory (RA) – a manoeuvre, or a manoeuvre restriction, calculated by the TCAS to avoid a collision. Pilots are expected to respond immediately to an RA unless doing so would jeopardise the safe operation of the flight.
A TCAS cannot detect aircraft that are not equipped with a transponder. Additionally, the system is unable to issue a RA for traffic that is not fitted with an altitude reporting transponder (mode C or S), or in circumstances where the mode C or S transponder on board the conflicting traffic is not transmitting altitude information—as was the case with 7456.
Further investigation
The investigation is continuing and will include the examination of:
airspace density levels
airspace suitability
flight crew actions
CA/GRS procedural design and application
future Ballina airspace plans
TCAS and recorded flight data
CTAF recordings.
Should a critical safety issue be identified during the course of the investigation, the ATSB will immediately notify relevant parties so appropriate and timely safety action can be taken.
A final report will be released at the conclusion of the investigation.
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.
Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.
The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
On the afternoon of 2 December 2020, a Robinson Helicopter Company (RHC) R44 Raven I, registered VH-HGU, departed Goulburn Airport, New South Wales with a student pilot and instructor on board. The helicopter flew east, and the last recorded automatic dependent surveillance broadcast (ADS-B) detected it descending into a valley in the Bungonia State Conservation Area. A search commenced when the helicopter did not return as expected, and the wreckage of VH-HGU was found in a valley, approximately 4 km north-west of its last ADS-B transmission. Both pilots were fatally injured, and the helicopter was destroyed.
What the ATSB found
Wreckage examination indicated that while flying in the vicinity of the valley, the helicopter entered a low-G condition due to turbulence, inappropriate control inputs, or a combination of both. This condition, probably in combination with inappropriate recovery control inputs resulted in extreme teetering of the main rotor. A mast bump occurred as a result, and the helicopter subsequently broke up in flight.
An intense post-impact fire prevented a complete examination of the wreckage. However, the evidence available gave no indication that the helicopter was operating abnormally prior to the in‑flight break-up.
The circumstances leading to in-flight break-ups from mast bumping and extreme teetering are usually not identified. While the fire would likely have prevented data recovery in this case, the inclusion of readily available cockpit video recorders on helicopters with semi-rigid rotor heads would provide valuable insights into low-G mast bumping events, which could help to prevent future occurrences.
What has been done as a result
The operator has introduced a limit of 6 consecutive training days. In addition, an online flight and duty monitoring system will be used to assess and adjust duty hours for instructors and students.
Since the occurrence, RHC has introduced cockpit video/audio recorders as standard equipment on new R44 helicopters, having previously been available on R66 models. The recorders are optional on R22 models, but will be standard equipment in 2023, with retrofit kits made available.
Safety message
Low-G conditions can be catastrophic for helicopters with semi-rigid rotor heads. A pilot’s ability to recover from low-G remains uncertain, though all parties agree that it is dependent on airspeed and time available. Pilots must therefore avoid low-G situations, and take the following actions to mitigate risk:
Make a careful study of the terrain, forecasts and observations applicable to the proposed flight to identify significant weather such as fronts or mechanical turbulence and avoid flying in those conditions.
Reduce airspeed when encountering significant turbulence.
Avoid flight downwind of hills, ridges or other potential sources of turbulence, particularly during changing or unpredictable weather conditions.
Allow plenty of altitude so that there is enough time for recovery from unexpected flight conditions.
Use slow and small control inputs.
Recording devices have long been recognised as an invaluable tool for investigators in identifying the factors behind an accident, and their contribution to aviation safety is irrefutable. While not required by regulations, operators should consider the benefits of installing such devices.
The occurrence
On the morning of 2 December 2020, an instructor and student pilot began a day of flight training operations in a Robinson R44 Raven I, registered VH-HGU. The pilots conducted a training area familiarisation from Goulburn Airport, New South Wales, after which the student pilot’s first solo flight was conducted.
Over the course of the morning and early afternoon, the student completed two sets of solo circuits and a solo navigation flight around the edge of the training area. Immediately after the navigation flight, the instructor joined the student pilot on board VH-HGU, and at 1558 Eastern Daylight‑saving Time,[1] they departed Goulburn Airport toward the east.
At 1846, when the helicopter had not returned to Goulburn as expected, the training operator’s chief pilot contacted the Australian Maritime Safety Authority’s Joint Rescue Coordination Centre (JRCC). The chief pilot then began an aerial search of the training area in another helicopter.
During the search, JRCC provided the chief pilot with the helicopter’s last known location—the last recorded automatic dependent surveillance broadcast (ADS-B)—which had detected it descending into a valley in the Bungonia State Conservation Area at 1611. At about 2000, the chief pilot located the helicopter’s wreckage 4 km north‑west of its last ADS-B transmission, which was in a valley approximately 31 km east of Goulburn Airport (Figure 1). The pilot then provided the wreckage location to emergency services. The helicopter’s engine and fuselage had been exposed to a fire at the main wreckage site, which had self‑extinguished before emergency services arrived. Both pilots had been fatally injured.
Figure 1: Flight path and wreckage location of VH-HGU
The aircraft track was calculated from ADS-B data.
Source: Google Earth, FlightAware, annotated by the ATSB
The instructor held a commercial helicopter pilot licence and a Grade 3 helicopter flight instructor rating. At the time of the occurrence, the instructor had accrued a total flying time of 690 hours. This included 684 hours in the Robinson R44, of which 103.1 hours had been in the past 90 days and 64.3 hours in the previous 30 days. The pilot held a Class 1 Aviation Medical Certificate valid until 7 December 2021.
Student
The student was 12 days into an intensive flight training course for the issue of a private helicopter pilot licence (PPL), having not flown previously. Over that time, the student had accrued a total of 37.9 hours of dual flying, all on VH‑HGU. Prior to the accident, the student pilot had accrued 3 hours of solo flying. The student pilot held a Class 2 Aviation Medical Certificate valid to 23 September 2022.
Fatigue considerations
During the 12 days of flying training, the work patterns of the instructor and the student identified some factors that placed them both at risk of their performance being affected by fatigue. Some research (Powell and others, 2007) conducted on short-haul airline pilots indicated that the most important influences on fatigue were the number of sectors conducted and the duty period. This study indicated that fatigue increased with each additional sector studied, up to a maximum of 5 sectors studied. On 30 November, the pilots conducted four flights totalling 4.2 hours flying time. The instructor also conducted a fifth flight with another student, 1.5 hours long. On 1 December, the day before the accident, the pilots conducted five flights with 5.5 hours total flying time. On 2 December, prior to the accident flight, the student pilot had conducted three solo flights totalling 3 hours, and two dual flights totalling 1.3 hours.
The nature of the work also could have contributed to fatigue—the Civil Aviation Safety Authority has stated that from a workload perspective, training and monitoring another flight crew member is often more fatiguing than regular operations[2].
In the days prior to the accident, the student pilot was reportedly working into the night studying PPL theory. In conjunction with the flight operations and other training activities conducted during training days, this could have resulted in duty limits[3] being exceeded. However, it was not possible to obtain an accurate record of the amount of time either pilot spent on ground operations, including PPL study.
Helicopter information
The Robinson Helicopter Company (RHC) R44 Raven I is a four-seat, piston-engine helicopter, powered by a Lycoming O-540-F series six-cylinder carburetted engine. At the end of 2020, there were 566 R44 helicopters on the Australian civil aircraft register.
The R44 Raven I helicopter involved in the accident, serial number 2615, was built in May 2020 in the United States. The helicopter was first placed on the Australian register as VH-HGU on 10 July 2020.
Rotor system
The Robinson R44 main rotor hub assembly design is a semi-rigid rotor head, otherwise known as a teetering rotor head (Figure 2). Bolts secure the blades to the hub at the coning hinges. During stopping and starting of the main rotor, when rpm is low, the blade tusks rest against the droop stops, restricting teetering and preventing the blades from drooping. As the main rotor rpm increases, the blades become rigid and straighten due to rotational forces, and the tusks shift off the droop stop as the blades lift. During normal flight, the rotor is free to teeter and flap around its designed flight axis via the teeter hinge, while polyurethane teeter stops limit the degree of teetering.
Figure 2: R44 main rotor hub assembly
Source: Robinson Helicopters, annotated by the ATSB
Under certain specific flight conditions, semi-rigid rotor systems are susceptible to extreme teetering where the blades teeter beyond their normal operational range, resulting in a what is commonly known as ‘mast bumping’. Mast bumping is the act of the inboard end of the blade (the spindle) contacting the main rotor shaft. In R44 helicopters, this can generally be identified by extensive damage to the teeter stops and varying degrees of damage to the main rotor shaft. Extreme teetering will also result in failure of one or both pitch links,[4] allowing uncontrolled pitching of the blade(s). This allows the blade(s) to deviate from their normal path of rotation.
Maintenance
The operator was using the RHC R44 manual suite to maintain VH-HGU. The most recent maintenance release was not recovered from the wreckage, but the helicopter had an estimated 150 hours total time in service.
According to RHC, it had received reports of burned intake valves on engines with serial numbers ending in ‘40E’ and less than 500 hours’ time-in-service, which included VH-HGU. It noted that a burned valve can result in partial or complete loss of power. On 14 October 2020, RHC issued a safety alert for engine intake valves installed on O-540-F1B5 engines. The alert stated:
Pilots should observe the following precautions:
1. Perform a complete run up and stabilized hover check prior to every flight. Do not initiate flight if there is any indication of engine roughness or sudden yaw.
2. If engine roughness or a sudden yaw occurs in flight, land as soon as practical and be prepared to land immediately.
The intake valves were inspected, and a compression check was conducted at a recent periodic inspection (about 101 hours total time in service), with no issues identified.
Meteorological information
Weather forecast
The Goulburn aerodrome forecast (TAF)[5] for the day of the accident predicted clear conditions up until a change at about 1600, which was expected to bring 13 kt easterly winds and broken cloud with a base 2,000 ft above ground level (AGL). The cloud was expected to descend to 1,000 ft AGL over the next few hours following the change.
The flight took place on the borders of several Graphical Area Forecasts[6] (GAF) with different predicted conditions. Forecast conditions issued at 1515 and valid from 1600 indicated some areas of:
greater than 10 km visibility
isolated drizzle, rain and thunderstorms reducing visibility, with associated broken cumulous and stratocumulus clouds as low as 2,000 ft above mean sea level (AMSL)
isolated drizzle with broken stratus clouds between 1,000 and 2,000 ft AMSL.
Reported weather conditions
The Bureau of Meteorology (BoM) provided METAR[7] and SPECI[8] data from Goulburn and Moss Vale aerodromes, located 31 km west and 43 km north-east of the accident site, respectively. These were the two automatic weather stations closest to the accident site, but indicated significantly different weather conditions—at the time of the accident and 1 hour prior.
Between 1530 and 1630, the METARs for Goulburn aerodrome recorded the wind varying in direction from 290° to 340°, up to 9 kt. The visibility remained greater than 10 km, and the temperature was 25 °C. There was no other significant weather observed. The 1530 METAR at Moss Vale recorded the wind from 080° at 14 kt, and a layer of overcast[9] cloud at 1,800 ft AGL and 2,600 ft AGL.
Based on the Moss Vale observations, a SPECI was first issued at 1538, due to a significant deterioration of cloud conditions in the area. Conditions at this time included a layer of broken cloud at 1,300 ft AGL and overcast layer at 2,000 ft AGL. The SPECI issued at 1600 included a layer of broken cloud at 1,100 ft AGL an overcast layer at 1,800 ft AGL. These conditions continued to deteriorate for several hours.
Bureau of Meteorology analysis
The BoM provided an analysis of the likely weather conditions based on nearby observations and the geographical features of the accident location, such as the valley. It estimated that the weather change would have arrived at the accident site between 1540 and 1610. It would then have taken 30 minutes or more for the change to pass.
Before the change, the BoM determined that conditions would probably have been fine and clear with light to moderate winds. Low cloud and turbulence would not have been expected. Similarly, after the change, conditions would likely have been clear, with cloud probably not developing until approximately 1630.
At the time of the change, however, the BoM predicted the possibility of a short period of moderate or greater low-level windshear and turbulence. As the change moved across the area, it noted that low-level vertical windshear of 20 kt or more would be expected, with possible turbulence and rotor winds[10] induced by the local terrain.
Recorded information
The ADS-B transmissions detected during the accident flight provided the helicopter’s track after departing Goulburn towards the Bungonia State Conservation Area. The last recorded transmission at 1611 indicated that the helicopter was descending into a system of valleys, approximately 4 km southeast of where it later impacted terrain.
The training operation regularly used OzRunways[11] for flight planning and tracking, however there was no data recorded for the accident flight. There were no other recording devices fitted to the aircraft, and data from personal electronic devices found at the accident site could not be recovered.
In early 2021, RHC introduced cockpit video cameras, standard on the R66 and optional for the R22 and R44. The forward-facing camera records video (encompassing view through the windshield, pilot controls and the instrument panel), intercom audio, radio transmission and GPS data. RHC advised the recordings (up to 10 hours) can be used as a training tool, maintenance aid, or aerial-tour souvenir. VH-HGU did not have a cockpit video camera installed.
Purpose of the flight
There was nothing in either pilot’s logbook or the training syllabus to indicate the purpose of the accident flight. The chief pilot—who was also the owner of the training operation—reported that the flight was likely to provide the student with area familiarisation. Previous students of the instructor were asked about any similar flights during their training—none had any recollection of such a flight. However, these students trained in regions without any substantial mountain ranges or valley systems nearby.
Without any documentation or recorded information to indicate the purpose of the flight, it could not be determined which pilot might have been flying the helicopter at the time of the accident.
Wreckage and impact information
Accident site and distribution of wreckage
The accident site was located about 31 km east of Goulburn Airport, near the bottom of a valley in the Bungonia State Conservation Area. The valley was about 1 km wide and 500 m deep.
The wreckage trail was approximately 275 m long on a south-easterly heading, parallel to the river. Figure 3 shows the location of the wreckage and calculated direction of flight prior to impact, as well as the helicopter’s last detected ADS-B transmission.
Figure 3: Wreckage trail and final ADS-B transmission from VH-HGU
Orange arrows show the aircraft heading at its last transmission point and prior to the break-up. Heading at its last transmission point was determined using ADS-B data, while the heading prior to the break-up was estimated based on the direction of wreckage and damage to trees around the accident site.
Source: Google earth, annotated by the ATSB
The start of the wreckage trail consisted of:
multiple pieces of windshield Perspex
fragments of the forward left door
a small piece of main rotor blade trailing edge skin
left landing gear skid toe cap
covers for the left and forward sections of the landing gear.
Extensive examination of surrounding vegetation identified no evidence of a tree strike at the start of the wreckage trail.
Figure 4 shows the locations of some of the components identified in the wreckage trail. An outboard section of one main rotor blade was located about halfway along the debris trail, along with liberated pieces of landing gear skids and struts. Damage to vegetation commenced about 20 m prior to the impact zone and was consistent with a relatively shallow descent profile. Impact forces likely ruptured the crash-resistant fuel tanks and an intense fire ensued, destroying the fuselage, engine and main gearbox. The fire zone was about 10 m in diameter. The tail cone assembly was situated a few metres to the west of the fire zone and was unaffected by the fire. All extremities of the helicopter were identified.
Figure 4: Location of aircraft components following in-flight break-up
Source: Google earth, annotated by the ATSB
Wreckage examination
Fuselage
The fuselage was upright, but almost entirely destroyed by the fire. The few flight instruments that were identifiable did not exhibit any witness marks that could assist the investigation. All of the seat belt buckles were found in the secure (closed) configuration, but the belt webbing had perished in the fire.
Main rotor drive and hydraulics
The main rotor drive assembly was primarily intact, however, the intense heat of the post-impact fire had reduced the integrity of the mounts, and the assembly had collapsed. Examination of the main gearbox did not identify any pre-existing condition that could have affected its operation.
Damage due to impact forces and fire also prevented a complete examination of the hydraulic system. However, a hydraulic system failure should not result in a loss of control or in-flight break‑up.
Engine
Examination of the severely fire damaged engine and clutch assembly identified no pre-existing issues that might have affected operations. The cooling fan exhibited some rotational scoring, consistent with the engine operating up to the point of impact. Based on the presence of fire and a fuel odour present during the on-site examination, there was a considerable amount of fuel on board at the time of the break-up
Various engine components—including the throttle and magnetos—were identified, however, the fire damage prevented complete examination. The engine was retained for further examination (see section titled Engine inspection).
Flight controls
Most of the flight control tubes had melted in the fire. Those that were recovered showed fractures consistent with overstress due to the impact. Without all flight control tubes, examination of the bellcranks was used to confirm flight control continuity from the main rotor hub through to the tail rotor—The steel rod ends were securely attached despite the control rod having melted. Damage to the pilot dual flight controls did not provide any indication as to whether the left or right seat pilot was in control.
Main rotor assembly
The main rotor hub was secured to the mast, and both spindles—including an inboard portion of each main rotor blade—were attached. Both main rotor pitch links had failed in overstress at the upper rod end thread, probably as a result of extreme teetering. The pitch link rod ends were secured to their respective pitch horns. The remainder of the pitch links were secured to the swashplate. Both spindles could be rotated freely about their axis of operation.
The coning hinge bolts were removed to allow removal of the spindles and remains of the main rotor blades (designated red and blue) from the main rotor hub (MRH). While the MRH attachment point on the red rotor blade was undamaged, the blue rotor blade tusk had been severely deformed (bent downwards nearly 90°), and the coning hinge bolt bore was split open as a result. This damage is shown in Figure 5, with the undamaged tusk from the red rotor blade for comparison. Following removal of the MRH, the teeter stops were seen to exhibit damage consistent with severe impact from the blade spindles, shown in Figure 6.
Figure 5: Blue blade tusk and coning hinge bolt bore
Source: ATSB
Figure 6: Teeter stop damage
Source: ATSB
The underside of the blue main rotor blade exhibited impact damage and a witness mark consistent with the dimensions of a landing gear strut. In addition, the forward left landing strut showed some scrapes and scuff marks. The location of the damage on the blade was consistent with the measured distance of the left forward strut from the main rotor hub. Some yellow paint transfer was noted on the forward section of the left skid, consistent with a main rotor strike.
Figure 7: Damage to the blue main rotor blade and the forward left landing strut
Source: ATSB
Tail cone
On-site examination of the separated tail cone assembly, including tail rotor drive components and flight control surfaces identified no pre-existing anomalies that could have contributed to a loss of control. In addition, black paint transfer was noted on the tail cone, just aft of where it had separated from the fuselage. The red main rotor blade had impact marks consistent with the rivet pattern at that location, including comparative distance from the main rotor hub. The paint transfer and rivet marks were indicative of tail cone separation due to a main rotor blade strike, likely just prior to the collision with terrain. The black paint was from the underside of the main rotor blade, indicating that it was inverted due to the fractured pitch link.
Engine inspection
catastrophic mechanical failure
oil starvation to the crankshaft journals and conrod bearings
damage to the valves, valve faces or cylinder bore.
Summary
Distribution of the wreckage, damage to the main rotor system, and damage to the fuselage and skids are all consistent with a main rotor blade striking the left forward fuselage at the commencement of an in-flight break-up.
Examination of the wreckage did not identify any pre-existing issues with the helicopter that could have contributed to:
loss of control
engine power loss
in-flight break-up.
Comments from the manufacturer
According to RHC, the damage observed was consistent with an extreme teetering event leading to mast bumping. It described the two different scenarios below to explain further:
Low rotor rpm mast bumping
In a low rotor rpm situation, the main rotor disc can start to cone, and subsequent mast bumping events tend to result in the main rotor striking the tail cone, often leading to separation of the tail.
Low-G mast bumping
RHC stated that extreme teetering and subsequent mast bumping can result from the pilot attempting to recover from an uncommanded right roll while in a low-G condition. This condition is expanded in the section below (see the section titled The low-G condition). RHC stated that inappropriate recovery control inputs often resulted in the main rotor blade impacting the forward left side of the fuselage.
In the case of VH-HGU, RHC concluded from the available evidence that mast bumping was the result of an extreme cyclic input while in a low-G condition. However, there was insufficient evidence to determine whether low-G was induced by a pilot input, turbulence or a combination of both.
The low-G condition
‘G’ or ‘g’ is an abbreviation for the acceleration due to the earth’s gravity. Positive G is necessary for helicopters to respond to pilot control inputs. In a low-G condition (that is, approaching the feeling of weightlessness), the pilot’s ability to control the attitude of the helicopter is greatly reduced. A low-G condition could be induced by an unusual attitude (for example, if the helicopter was inverted due to spatial disorientation). However, during normal flight, low-G is typically induced either by a cyclic pushover, or by turbulence.
Low-G due to cyclic pushover
The FAA Helicopter Flying Handbook[12] provided a description of how cyclic pushover can induce low-G and ultimately result in a mast bump:
During a pushover from moderate or high airspeed, as the helicopter noses over, it enters a low-G condition. Thrust is reduced, and the pilot has lost control of fuselage attitude but may not immediately realize it. Tail rotor thrust or other aerodynamic factors will often induce a roll. The pilot still has control of the rotor disk, and may instinctively try to correct the roll, but the fuselage does not respond due to the lack of thrust. If the fuselage is rolling right, and the pilot puts in left cyclic to correct, the combination of fuselage angle to the right and rotor disk angle to the left becomes quite large and may exceed the clearances built into the rotor hub. This results in the hub contacting the rotor mast, which is known as mast bumping.
RHC Safety Notice SN-11[13] provided a descriptive warning about the cyclic pushover manoeuvre described above. It also stated that severe in-flight mast bumping usually results in main rotor shaft separation and/or rotor blade contact with the fuselage. The following warning was included:
Never attempt to demonstrate or experiment with low-G manoeuvres, regardless of your skill or experience level. Even highly experienced test pilots have been killed investigating the low-G flight condition. Always use great care to avoid any manoeuvre which could result in a low-G condition. Low-G mast bumping accidents are almost always fatal.
Low-G due to turbulence
The FAA Helicopter Flying Handbook stated that ‘Turbulence, especially severe downdrafts, can also cause a low-G condition and, when combined with high airspeed, may lead to mast bumping.’ RHC Safety Notice SN-32[14] referred to flying in high winds or turbulence, firstly stating that it should be avoided. It continued:
A pilot’s improper application of control inputs in response to turbulence can increase the likelihood of a mast bumping accident.
The following were among RHC’s recommendations when encountering turbulence:
- Reduce power and use a slower than normal cruise speed. Mast bumping is less likely at lower airspeeds.
- Avoid flying on the downwind side of hills, ridges, or tall buildings where turbulence will likely be most severe.
In November 2016, RHC released a safety alert[15] reiterating the dangers of cyclic pushovers and the low-G condition, warning against over-reacting or flying too fast when in turbulence. If pilots found themselves flying in the low-G condition, RHC recommended the application of gentle aft cyclic in order to reload the rotor.
Previous occurrences
There have been a number of fatal mast bumping accidents involving helicopters with semi-rigid rotor heads worldwide. A review of occurrences in Australia, New Zealand and the United States identified the following accidents, dating back to 1983:
In New Zealand, there have been 12 fatal mast bumping accidents, all involving RHC helicopters, 6 of which have been deemed low-G accidents.
In the United States, there have been 18 fatal accidents where mast bumping was the primary occurrence. Eleven of those accidents involved RHC helicopters.
In Australia, there has been one other known fatal mast bumping accident.[16] It was determined to be induced by low rpm rather than low-G.
Many of the low-G fatal mast bumping accidents in New Zealand and the United States share other similarities with the in-flight break-up of VH-HGU. Two such accident investigations by the New Zealand Transport Accident Investigation Commission (TAIC) are summarised below:
Loss of control, R44 helicopter ZK-HTB, New Zealand (AO-2018-006)
The helicopter was travelling to Upper Estuary Burn Valley when it departed controlled fight and crashed into Lake Wanaka, fatally injuring the pilot who was the sole occupant. Wreckage examination found signs of mast bumping, including teeter stop damage and evidence of the main rotor striking the canopy, however it was not conclusively determined to be an initiator of the occurrence. With regard to turbulence, the report stated:
Turbulence is a known contributor to mast bumping. Large, sudden upward or downward gusts can upset a helicopter and cause the blades to flap up or down excessively, or cause a low-G situation. Inappropriate or inadvertent pilot inputs or over-controlling by the pilot can further exacerbate the effects of the turbulence.
The investigation found that the helicopter probably encountered turbulence that was strong enough to have resulted in the in-flight break-up of the helicopter. The report also made note of the lack of available data regarding mast bumping accidents in RHC helicopters
In-flight break-up, R44 helicopter ZK-IPY, New Zealand (AO-2015-002)
The helicopter was returning to Queenstown from a training flight when it broke up in mid-air and crashed near the Lochy River, fatally injuring the instructor and student. The break-up occurred after a main rotor blade struck the cabin due to mast bumping. The investigation report stated that mast bumping was typically caused by one or a combination of the following factors:
low main rotor rpm
the helicopter entering a low-G condition
turbulence
the pilot making large and abrupt movements with the helicopter controls.
The report noted that a low-G scenario could have been induced by a combination of airspeed and the pilot’s response to turbulence. In a safety recommendation, TAIC stated:
The uncertainty around the circumstances of this accident are not unique. The nature of mast bump accidents is that they are usually fatal, leaving no one to explain what was happening at the time. In-flight break-ups are destructive, making it difficult to determine with certainty whether mechanical failures of some kind could have initiated the mast bumps.
The report included a recommendation emphasising ‘…the need for cockpit video recorders and/or other forms of data capture in the cockpits of certain classes of helicopter to address this safety issue [mast bumping]’. The report identified the following key lesson:
Helicopter pilots must be fully aware that a condition of low-G (feeling of lightness or weightlessness) can result in: a rapid right roll; mast bumping; and in-flight break-up before even the most experienced pilot can react and recover the situation. Pilots need to fly in a manner that avoids low-G conditions rather than allow them to develop and then expect that they can recover from them.
While flying in the vicinity of a valley in the Bungonia State Conservation Area on the afternoon of 2 December 2020, the R44 helicopter, VH-HGU, experienced an in-flight break-up. As a result, both pilots were fatally injured, and the helicopter was destroyed.
Although fire and impact damage had destroyed some parts of the helicopter, the ATSB was able to use available evidence to make certain important findings. Components recovered near the beginning of the wreckage trail indicated that a main rotor blade had struck the left side of the fuselage at the beginning of the break-up sequence. No evidence was found to indicate pre-existing mechanical defects or issues that could have prevented normal engine operation. While a transient condition such as a partial or complete power loss could not be ruled out, such an event should not have resulted in an in-flight break-up.
The investigation considered the possibility of clouds or reduced visibility forcing a descent. However, a Bureau of Meteorology (BoM) analysis of the weather conditions indicated that low cloud would not have created difficulties until after the time of the accident. Further, any unfavourable weather coming with the easterly change would not have prevented the pilots from safely returning to Goulburn at any point.
As there were no survivors and no available records, the purpose of the flight could not be determined, nor which pilot had been flying the helicopter. For the same reason, their working hours that day and in the preceding days could not be ascertained. While the nature of their work and work patterns in terms of overall duty hours and time spent on ground operations suggested that both pilots could have been at risk of fatigue, there was insufficient evidence to determine whether or not fatigue was a factor in this accident.
The following analysis focuses on factors that probably contributed to the in-flight break-up, which include the low-G condition in helicopters with semi-rigid rotor heads, the effects of turbulence, and the influence of control inputs (pilot actions) in such conditions.
Helicopter entered low-G
The broken teeter stops, failed pitch links, bent tusk and blade impact damage were consistent with the low-G mast bumping scenario described by the Robinson Helicopter Company (RHC). The damage was also similar to many other in-flight break-up incidents that were the result of extreme teetering after entering a low-G condition.
There have been several fatal mast bumping accidents where turbulence has probably contributed to inducing a low-G scenario. While not a necessary condition to enter low-G, the Federal Aviation Administration has stated that turbulence can induce a low-G condition. RHC has also stated that turbulence can contribute to a low-G mast bumping event and encourages pilots to avoid the severe turbulence associated with flying on downwind side of hills and ridges.
Based on the weather and the geographical conditions at the accident location, the BoM analysis noted the potential for windshear and moderate or greater turbulence at the time of the accident, dependent on the arrival of a weather change. It is likely but not certain that turbulence was present in the area at the time of the break-up. The various weather forecasts showed differing conditions, but it could not be determined which, if any, the pilots checked before departure nor the conditions that they were expecting.
While the evidence shows that VH-HGU entered a low-G condition, it was not possible to determine the contribution that turbulence or incorrect/inappropriate pilot control inputs (for example, initiating a cyclic pushover) had in triggering the condition. However, one or both of these factors must have been present.
In-flight break-up following low-G
While it has been well established that a low-G condition can result in mast bumping and an in-flight break-up, there remains some uncertainty regarding a pilot’s ability to recover from a low-G situation, and whether inappropriate recovery control inputs are necessary for an accident to occur.
Both RHC and New Zealand’s Transport Accident Investigation Commission (TAIC) have acknowledged that turbulence and airspeed can contribute to a low-G mast bump and subsequent in-flight break-up. The latter has identified turbulence as a sufficient condition for low-G mast bumping to occur and stated that certain low-G situations can lead to mast bumping and in-flight break-up before a pilot can reasonably react. Conversely, RHC has stated that turbulence only results in mast bumping when pilots react with inappropriate control inputs. However, it should be noted that according to RHC, even highly experienced test pilots have sometimes failed to recover from a low-G condition.
In this accident, once the helicopter entered a low-G condition, inappropriate recovery control inputs probably contributed to the mast bumping and subsequent in-flight break-up. Following the right roll that can be induced by low-G, either pilot could have reacted by instinctively applying left cyclic, rather than the gentle aft cyclic recommended by RHC. Extreme teetering, potentially in combination with broken pitch links resulted in the main rotor striking the fuselage and the helicopter breaking up in flight.
Video recorders
Throughout the accident sequence, the relative contribution of turbulence and pilot actions could not be determined due to the lack of available evidence. This lack of evidence is common to many previous low-G mast bumping accidents. While the post-impact fire in this accident would probably have destroyed recorded data, including readily available cockpit video recorders on helicopters with semi-rigid rotor heads would provide valuable insights into low-G mast bumping events, and help to prevent future occurrences.
Findings
ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition, ‘other findings’ may be included to provide important information about topics other than safety factors. These findings should not be read as apportioning blame or liability to any particular organisation or individual.
From the evidence available, the following findings are made with respect to the in-flight break-up of Robinson R44 VH-HGU on 2 December 2020.
Contributing factors
While flying in the vicinity of the valley, the helicopter entered a low-G condition due to turbulence, inappropriate control inputs, or a combination of both.
The low-G condition, probably in combination with inappropriate recovery control inputs resulted in extreme teetering of the main rotor and subsequent in-flight break-up.
Other findings
No evidence was found to indicate that the helicopter was not capable of normal operation prior to the in-flight break-up.
In helicopters with semi-rigid rotor heads, the circumstances leading to in-flight break-ups from mast bumping and extreme teetering are not well understood. Recorded cockpit imagery could provide valuable insight for understanding the effect that weather conditions and pilot input has in these occurrences.
Safety action
Whether or not the ATSB identifies safety issues in the course of an investigation, relevant organisations may proactively initiate safety action in order to reduce their safety risk. The ATSB has been advised of the following proactive safety action in response to this occurrence.
Safety action by Hughes Helicopters
Following this accident, Hughes Helicopters placed a limit of 6 consecutive training days on the intensive flight training course. An online flight and duty system has been introduced so that the head of operations can monitor and adjust the duty periods and hours flown by students and instructors. Instructors will be continuously monitoring student fatigue levels and adjusting the training program accordingly.
Safety action by the Robinson Helicopter Company
In 2022, video and audio recorders that were already equipped on R66 models became standard equipment on all new production R44 models and optional on R22 models. In 2023, the recorders will be standard on all three models and retrofit kits will be available.
Glossary
ADS-B
Automatic dependent surveillance broadcast
AGL
Above ground level
BoM
Bureau of Meteorology
CASA
Civil Aviation Safety Authority
CASAR
Civil Aviation Safety Regulations
FAA
Federal Aviation Administration
GAF
Graphical area forecast. Provides information on weather, cloud, visibility, icing, turbulence and freezing level in a graphical layout with supporting text. These are produced for 10 areas across Australia, broadly State-based.
ICAO
International Civil Aviation Organisation
JRCC
Joint Rescue Coordination Centre
METAR
A meteorological report for an aerodrome at a routine time (half hourly) when conditions are better than specified thresholds.
MRH
Main rotor hub
NTSB
National Transportation Safety Board
PPL
Private pilot licence
RHC
Robinson Helicopter Company
RPM
Revolutions per minute
SPECI
A weather report for an aerodrome or significant location issued whenever weather conditions fluctuate below specified criteria.
TAF
Aerodrome forecast. A statement of meteorological conditions expected for a specific period of time in the airspace within a radius of 5 NM (9 km) of the aerodrome reference point.
TAIC
Transport Accident Investigation Commission
Sources and submissions
Sources of information
The sources of information during the investigation included the:
chief pilot
Bureau of Meteorology
Robinson Helicopter Company
OzRunways
maintenance organisation for VH-HGU
former trainee pilots
Civil Aviation Safety Authority
New South Wales Police Force
New Zealand Transport Accident Investigation Commission
United States National Transportation Safety Board
Powell, DMC; Spencer, MB; Holland, D; Broadbent, E and Petrie KJ (2007) Pilot fatigue in short-haul operations; effects of number of sectors, duty length and time of day. Aviation Space and Environmental Medicine 2007; 78:698-701.
Submissions
Under section 26 of the Transport Safety Investigation Act 2003, the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. That section allows a person receiving a draft report to make submissions to the ATSB about the draft report.
A draft of this report was provided to the following directly involved parties:
the operator
the Robinson Helicopter Company
the Civil Aviation Safety Authority
the United States National Transportation Safety Board.
Submissions were received from:
the operator
Robinson Helicopter Company
Civil Aviation Safety Authority.
The submissions were reviewed and, where considered appropriate, the text of the report was amended accordingly.
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.
Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.
The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
Preliminary report
Report release date: 24/02/2021
This preliminary report details factual information established in the investigation’s early evidence collection phase and has been prepared to provide timely information to the industry and public. Preliminary reports contain no analysis or findings, which will be detailed in the investigation’s final report. The information contained in this preliminary report is released in accordance with section 25 of the Transport Safety Investigation Act 2003.
The occurrence
On 2 December 2020, at 1558 Eastern Daylight‑saving Time[1] a Robinson Helicopter Company (RHC) R44 Raven I, registered VH-HGU, departed Goulburn Airport, New South Wales with a trainee pilot and an instructor on board. The helicopter flew east from Goulburn Airport, and the last recorded automatic dependent surveillance broadcast (ADS-B) detected it descending into a valley in the Morton National Park at 1611.
Later that evening, when VH-HGU had not returned to Goulburn as expected, the chief pilot began an aerial search of the training area in another helicopter. The wreckage of VH-HGU was found in a valley, approximately 4 km north‑west of its last ADS-B transmission.
Wreckage examination indicated that, during the accident sequence, the main rotor struck the helicopter’s fuselage in flight. The uncontrollable aircraft subsequently collided with terrain. Both pilots were fatally injured, and the helicopter was destroyed.
The engine and fuselage were exposed to a fire at the main wreckage site, which self‑extinguished before emergency services arrived. Figure 1 shows the direction and location of the helicopter’s last detected ADS-B transmission and the wreckage trail orientation.
Figure 1: Wreckage trail and final ADS-B transmission from VH-HGU
The aircraft track at its last transmission point was calculated from ADS-B data, while the direction at impact was estimated based on the direction of wreckage and damage to trees around the accident site.
Source: Google earth, modified by ATSB
Context
Pilot information
The instructor held a Grade 3 helicopter flight instructor rating, and had 690 hours of flying experience, predominantly in R44 helicopters.
The trainee pilot was undergoing intensive flight training for the issue of a private pilot licence and was 11 days into the course with the operator at the time of the accident. The trainee had accrued a total of 38 hours of dual flying on VH‑HGU. The trainee pilot’s first solo flight was conducted on the morning of the accident.
Aircraft and maintenance
The Robinson R44 is a four-seat, single piston engine helicopter, first certified in December 1992. In January 2000, RHC introduced the R44 Raven I. At the end of 2020, there were 566 R44 helicopters on the Australian civil aircraft register.
The R44 Raven I helicopter involved in the accident, serial number 2615, was built in May 2020 in the United States. The helicopter was first placed on the Australian register as VH-HGU on 10 July 2020. VH-HGU was being maintained in accordance with the RHC R44 manual suite. The most recent maintenance release was not recovered from the wreckage, but the helicopter had an estimated 150 hours total time in service.
On 14 October 2020, RHC issued a safety alert for engine intake valves installed on O-540-F1B5 engines. RHC reported they had been advised of burned intake valves on engines whose serial number ended in ‘40E’, with less than 500 hours’ time-in-service, which included VH-HGU. The alert stated:
Pilots should observe the following precautions:
Perform a complete run up and stabilized hover check prior to every flight. Do not initiate flight if there is any indication of engine roughness or sudden yaw.
If engine roughness or a sudden yaw occurs in flight, land as soon as practical and be prepared to land immediately.
Following any engine roughness or a sudden yaw, have a mechanic check valve condition before further flight. The mechanic should listen for sound of leakage at each intake valve while performing a compression check. Any intake valve with audible leakage requires repair prior to further flight. Check may be done with engine hot or cold.
A periodic inspection of VH-HGU was completed on 18 November 2020, at 100.57 hours total time in service. The intake valves were inspected, and the valve covers were reinstalled with new gaskets. A compression check was conducted, and no issues were identified.
Meteorological information
The two closest automatic weather stations showed significantly different weather 1 hour prior to, and at the time of the accident.
The half-hourly weather report at Goulburn Airport (31 km west of the accident site) recorded the wind from a north-westerly direction, up to 9 kt. The visibility remained greater than 10 km, and the temperature was 25°C. There was no other significant weather observed.
The half-hourly weather report at Moss Vale (43 km north-east of the accident site) recorded the wind from an easterly direction, up to 14 kt.
Based on the Moss Vale observations, a special weather report was first issued at 1538, due to a significant deterioration of weather conditions in the area. These conditions continued for several hours. A layer of broken [2] cloud commenced descending to 1,100 ft AMSL, with a second layer of overcast cloud descending to 1,600 ft AMSL. The temperature reduced to 16°C, with the dew point also reducing to 12°C.
Further investigation
To date, the ATSB has:
attended the accident site on two occasions for wreckage assessment and evidence collection
completed a subsequent examination of the helicopter’s engine and tail rotor driveshaft
conducted interviews with relevant parties, including the operator.
The investigation is continuing and will include:
consideration of factors that contributed to a rotor blade impacting the fuselage in flight, such as turbulence, pilot input, engine issues, and aircraft controllability
a review of the performance and handling characteristics of the helicopter
analysis of the weather conditions at the time of the accident
detailed technical examination of the engine and other retained components/electronic devices
a review of available training and aircraft maintenance documentation
assessment of related occurrences in Australia and overseas.
Should a critical safety issue be identified during the course of the investigation, the ATSB will immediately notify relevant parties so appropriate and timely safety action can be taken.
A final report will be released at the conclusion of the investigation.
Acknowledgements
The ATSB would like to acknowledge the significant assistance provided by the New South Wales Police Force during the initial investigation response.
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.
Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.
The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
At around 1736 on 23 November 2020, V/Line loco-hauled passenger service 8239 from Southern Cross to Melton passed signal SST535 at stop, about 700 m north-west of Southern Cross Station. The signal was at stop to protect the movement of V/Line passenger service 8156 (Wendouree to Southern Cross) that was to cross ahead of train 8239. Train 8239 passed the signal at about 23 km/h and continued for about 200 m before stopping across the junction through which train 8156 would pass. The driver of train 8156 brought their train to a stop about 100 m prior to that junction. The drivers of both services had stopped their trains following an emergency broadcast from the controlling signaller.
What the ATSB found
When approaching signal SST535 at stop, the driver of train 8239 was probably distracted by task unrelated thoughts. They did not respond to the indication of the signal and probably looked past to another signal further along the track that they incorrectly believed was the signal where they were to stop.
Once signal SST535 had been passed, the risk control to reduce the likelihood of a collision was primarily the action of the signaller to respond to system alarms. In this instance, the signaller responded by making an emergency broadcast to train 8156 and this was sufficient to stop that train. The driver of train 8239 also overheard this broadcast and stopped their train.
Some signals on the V/Line network were fitted with Train Protection and Warning System (TPWS) equipment that automatically initiated a brake application when a signal was passed at danger (SPAD). Signal SST535 was not fitted with TPWS and its absence at this signal increased the potential consequences of a SPAD. A 2014 V/Line risk assessment of signal SST535 had not considered a head-on or side-on collision as a credible scenario. Such a consideration would have increased the risk rating of this signal and probably led to the fitting of TPWS.
Train 8156 was approaching signal SST578 as train 8239 passed signal SST535 at danger. However, signal SST578 continued to show a proceed aspect and did not restore to danger until train 8156 had passed that signal. There were no further signals in front of train 8156 to warn that the junction ahead was occupied by train 8239. The V/Line signalling standards did not include specific reference to a design that would require signal SST578 to restore to danger in this scenario (flank-track protection).
What has been done as a result
V/Line Corporation has advised that a funding submission to fit TPWS to signal SST535 and other similar signals in the Southern Cross area was approved in July 2021. Plans are underway to complete this installation during 2022.
The Rail Industry Safety and Standards Board (RISSB) advised that flank - track protection has been recorded for inclusion when the signalling principles standard AS 7711 is next under review.
Safety message
This occurrence has highlighted the importance for passenger rail networks to have engineering controls in place to detect SPAD events and prevent potential consequences such as collision. In determining applicable SPAD risk controls, rail operators should consider all SPAD precursors and potential collision scenarios.
The occurrence
Prior to the event
The driver of V/Line Corporation[1] (V/Line) loco-hauled passenger service 8239 had signed on for duty at 1505 on the day of the incident and moved the train from the yard at Southern Cross Station to platform 3 at approximately 1600. At 1633 the conductor of train 8239 informed the driver that platform work had been completed. At the same time, a passenger approached the locomotive at the front of the train. The driver then turned on the headlights and revved the train engine to warn that the train was departing, and the train left without the passenger boarding.
Figure 1: Map showing location of incident
Source: PASS Assets (Department of Transport, Victoria) adapted by CITS
Journey of Train 8239
Train 8239 was a loco-hauled passenger train scheduled to travel from Southern Cross Station to Melton. Closed circuit television (CCTV) showed train 8239 departed Southern Cross Station on-time at 16:33:58, and passed signal SST537 at 16:34:53. This signal was located at the northern end of the station and displayed a red aspect over a yellow aspect,[2] which advised the driver to proceed at a limit of medium speed[3] but be ready to stop at the next signal. The train then approached the LaTrobe Street road-over-rail bridge and diverged onto the dual gauge track. On passing under the LaTrobe Street bridge, train 8239 passed signal SST535 showing a stop (red aspect over red aspect) indication and occupied the track circuit[4] past this signal at 16:35:40. Train 8239 passed the signal at 23 km/h. The speed limit for this section of track was 25 km/h.
At 16:35:50, train 8239 progressed onto the next track circuit that was located 53 m after signal SST535. At 16:36:03 the on-board event recorder[5] on train 8239 recorded the application of the train brakes, and at 16:36:13, with train 8239 having stopped approximately 228 m past signal SST535. This placed train 8239 over a junction that was on the intended route of train 8156. The driver of train 8239 reported having stopped on seeing train 8156 on the flyover approach to Southern Cross Station and hearing a radio communication from the signaller requesting train 8156 to stop.
The signaller had observed CCTV of train 8239 approaching signal SST535 and reported that based on their observations, anticipated that the train would not stop at the red signal. At approximately the same time, the signaller reported hearing and seeing a SPAD alarm warning from the train control system. Consequently, the signaller commenced a radio broadcast to the driver of train 8156, requesting that they stop owing to a train having passed a signal at danger.
Figure 2: Simplified layout of the relevant tracks and signals at Docklands (not to scale)
Source: CITS
Journey of Train 8156
Train 8156 was a Diesel Multiple Unit (DMU) passenger train scheduled to run from Wendouree to Southern Cross Station. The on-board event recorder showed the train departed Footscray Station, the station prior to Southern Cross Station, on time at 1629. A recording of the signalling display[6] showed that the train was routed via the ‘Up Regional Rail Link (RRL) dual gauge’[7] track (Figure 2).
On approaching Southern Cross Station, the driver received the radio communication from the signaller instructing the train to be stopped, and the on-board event recorder showed that the driver responded by making a brake application at 16:35:47. At this point the train was travelling at 27 km/h. At 16:35:57 the signal interlocking recorded that train 8156 passed signal SST578 at a proceed aspect and occupied track circuit SST584T. The on-board event recorder showed that the emergency brake was applied at 16:35:58 and that the train came to a stop at 16:36:01, approximately 20 m past signal SST578 and about 100 m from train 8239.
The SPAD occurred on a section of track that had been constructed in 2014 as part of the Regional Rail Link project (RRL). The RRL project included extensive track and signalling works for accessing platforms 1 to 8 at Southern Cross Station. V/Line provided both the infrastructure management and train control functions for this section of track, under a lease arrangement with VicTrack.[8]
Train and driver information
Details of trains
Train 8239 was a scheduled passenger service operated by V/Line. It consisted of an N-class locomotive and six carriages, with an overall length of 136 m. Train 8156 was a three carriage VLocity DMU with a length of 76 m. Both trains were operated by solo drivers.
Driver of train 8239
The driver commenced with V/Line as a trainee driver in 2017 and qualified as a V/Line driver in August 2019. A V/Line train driver safety re-accreditation audit was conducted in September 2020 and no non-conformances were recorded. Medical records provided by V/Line showed the driver had undertaken a medical assessment (rail category 1 – high-level safety worker) in 2017 and was assessed as fit for duty. The fitness certificate was still valid at the time of the incident. V/Line information did not record any safety incidents related to the driver during the 36 months prior to the SPAD, and reported the driver was compliant with the V/Line driver fatigue policy. The driver advised that they were feeling physically well and had a good night’s sleep prior to the incident. The driver was familiar with the route taken by train 8239, having last driven the same service over the same route two weeks earlier.
The driver had signed on for duty at 1505 on the day of the incident and following some train preparation duties, train 8239 was their first passenger service of the day. The driver reported being distracted by a personal issue on the afternoon of the incident and that they were reminded of this issue by a passenger who had just missed the departure of the train from Southern Cross Station. The passenger event, that was captured on station CCTV, was not reported to Train Control and was not required to be reported. At the time of the SPAD, the driver was not in conversation with the train’s conductor and there was no record of the driver using a mobile phone at the time.
The driver reported thinking about the passenger they had left behind when passing signal SST537 on the departure from Southern Cross Station. This signal displayed a red indication over a yellow indication, which advised the driver to be ready to stop at the next signal. The driver reported seeing signal SST537 and acknowledging it by repeating the aspect to themselves. While the driver reported acknowledging this warning signal, they also advised that they did not at that time think about the next signal, SST535, which was 351 m ahead of signal SST537. The driver reported they looked past ground-mounted signal SST535 at LaTrobe St bridge and saw gantry-mounted signal SST991 at Dudley St showing a red indication (Figure 3). The driver reported they erroneously matched stop signal SST991 to the warning (to be ready to stop at the next signal) provided by SST537.
The driver saw train 8156 and around the same time heard the signaller on the train radio requesting train 8156 to stop. The driver of train 8239 then applied emergency braking.
Following the incident, testing of the driver returned a zero blood alcohol result and nil presence of drugs.
Figure 3: Signals SST535 and SST991 at stop
Source: CITS. Photo taken from the cab of an N-Class locomotive post-incident.
Driver of train 8156
The driver was qualified for the operation of this train on this route and was medically fit for duty.
Recordings of the train radio and the on-board event recorder show that the driver promptly stopped the train on being requested to do so by the signaller.
Environmental conditions
Meteorological conditions recorded at Melbourne for the afternoon indicated mild and cloudy conditions, 7 oktas[9] of cloud cover, and light south westerly winds.[10] Ambient temperature was recorded as 17.8 °C at 1500. The cloud cover recordings were consistent with CCTV recordings from Southern Cross Station. It was determined that the environmental conditions did not contribute to the incident.
Train control and signalling
Overview
The signalling of the V/Line infrastructure at Southern Cross Station was operated from Southern Cross Number 1 signal box. Absolute Block Signalling rules applied at this location.[11] A computer-based interlocking controlled points and signals to prevent conflicting movements of signals, and to make sure routes were set correctly.
In relation to the real-time monitoring and management of field signalling equipment, the train control system provided the signaller with a video display unit (VDU) and interface to enter control requests. The signaller was responsible for the day-to-day operational management of the rail corridor for V/Line trains departing and entering Southern Cross Station.
Signal, points, track, and train movement data were captured by a computer-based interlocking event logger. Voice communication between train drivers and the signallers at the Southern Cross Number 1 signal box was via channel one of the Local Radio System (LRS), which was recorded. The radio channel was an open system and communications from the signaller could be heard by the drivers of all train in the area.
Signalling system playback
The status of signals and the movement of trains were captured by the Southern Cross train control system (TCS) event logger. Figure 4 shows the position of trains, the status of signals and points, and routes set at 16:35:31 (9 seconds prior to the SPAD event), as were shown on the signaller’s train control system display. Red indicated the presence of a train on a section of track and green indicated the track was clear and the route was set. Train 8239 approached signal SST535 at stop. A route had been set for train 8156 to pass in front of train 8239 and onto the ‘Through Country’ track, with signals SST986 and SST578 both at proceed.
Source: V/Line Southern Cross Train Control System, annotated by CITS.
Figure 5 shows that at 16:35:47, train 8239 had passed signal SST535 at stop, and train 8156 was approaching signal SST578 at proceed. It is estimated that train 8156 was between 50 m and 80 m from signal SST578 when train 8239 passed signal SST535 at stop.
Figure 5: TCS playback showing train 8239 having passed SST535 at stop
Source: V/Line Southern Cross Train Control System, annotated by CITS
Figure 6 shows that at 16:36:03 train 8239 was continuing to travel towards the route set for train 8156. The system playback shows train 8156 had passed SST578 when it showed a proceed indication, and this signal had subsequently restored to danger once the train had moved onto the track circuit past the signal. Both trains had come to rest by 16:36:13.
Source: V/Line Southern Cross Train Control System, annotated by CITS
Signaller
The signaller advised that they commenced work as a signaller at Southern Cross in 2018, having worked previously for another rail infrastructure manager for 25 years in various safeworking roles. The signaller was qualified to operate the signalling control panel at Number 1 signal box at Southern Cross.
On 23 November, the signaller had signed on for duty at 1300 to commence an eight-hour shift. The signaller reported observing CCTV of train 8239 approaching signal SST535 and based on their observations, anticipated that the train would not stop at the red signal. Consequently, the signaller commenced a radio broadcast directed to the driver of train 8156, requesting that they stop owing to a train having passed a signal at danger. At approximately the same time, the signaller reported hearing and seeing a SPAD alarm warning from the train control system. Following the communication with the driver 8156, the signaller directed a broadcast to the driver of train 8239.
The signaller was subjected to post-incident drug and alcohol testing returning negative results for both tests.
Signaller radio communications
The following communications took place between the signaller and the driver of train 8156 (Table 1). The time log on the radio communication showed that the initial call from the signaller to the driver of train 8156 was followed 8 seconds later with a second ‘urgent’ call. The driver of train 8156 replied immediately after this second call.
Table 1: Radio communications between signaller and driver of train 8156
Person
Dialogue
Signaller
Number 1 calls 8156, urgent, urgent to number 8156.
Signaller
Number 1 calls 8156 urgent.
Driver, train 8156
8156 receiving.
Signaller
Drive [sic], stop where you are, stop where you are, the down train has just SPAD the signal in front of you.
Driver, train 8156
Uh, …, yeah, I’ve just got it now, thanks.
Signaller
Roger that and thanks drive [sic].
The following communications then took place between the signaller and the driver of train 8239 (Table 2).
Table 2: Radio communications between signaller and driver of train 8239
Person
Dialogue
Signaller
Number 1 to 8239.
Signaller
Number 1 calls 8239.
Driver, train 8239
8239 receiving.
Signaller
Alright drive [sic], you realise what’s happened, have you stopped clear of the points?
Driver, train 8239
No, I believe I’ve just gone onto the points.
Signaller
Alright drive [sic], stop and hold where you are, stop and hold where you are.
Signal STT535 information
Overview
Signal SST535 (Figure 7) was commissioned in 2014 as part of the RRL project as a ground mounted mainline three-position home signal. The main signal aspects were displayed as light-emitting diode (LED) colour light combinations on the “A” and “B” lights. The “C” light could display a yellow low speed aspect when both A and B lights were red. As the signal was located on a dual gauge line, it was provided with “V” and “S” indicators. A “V” indicator displayed in conjunction with another proceed aspect authorised a broad-gauge train to pass the signal, and an “S” indicator displayed in conjunction with another proceed aspect authorised a standard gauge train to pass the signal. The signal was not equipped with Train Protection and Warning System (TPWS)[12] or other train protection equipment.
Post-incident observations from the driver’s cab showed that signal SST535 was visible to the driver for approximately 60 seconds when approached in compliance at the allowable track speed from platforms 1 to 5 at Southern Cross Station.
Risk of SPAD at signal SST535
In May 2014, the V/Line RRL Management of Change and Risk Team undertook a risk review to determine which signals should be fitted with TPWS. At that time, the Rail Safety National Law (RSNL), the V/Line Safety Management System (SMS), and the RRL Scope and Technical Requirements required risk assessments to be undertaken to assess the risk of train-to-train collision and determine whether additional signal enforcement mitigation measures were required. This work assessed a total of 54 signals. Twenty-six of these signals were in the Southern Cross Station to West Footscray area, which was defined as work package B of the RRL project.
Signals that had experienced a SPAD event[13] on more than one occasion were chosen to be fitted with TPWS, as were those that V/Line ranked as ‘Potentially Severe’. Seventeen signals were ranked as ‘Potentially Significant’ and subjected to a cost-benefit analysis to determine if fitment of TPWS was cost effective. The ranking was determined using a ‘SPAD Ranked Risk Tool’ (SRRT), and a ranking of ‘Potentially Significant’ was evaluated to be equivalent to a ‘medium risk’ in accordance with the rankings used by the V/Line Enterprise-Wide Risk Model (EWRM).[14]
The SRRT was made up of three elements: an initial collision potential assessment, an accident vulnerability ranking, and a final risk ranking score. For signal SST535, the analysis of the SRRT considered a potential collision type of ‘Plain line rear-on or buffer’.
V/Line used the Signal Passed at Danger Assessment Model (SPADAM) to assist in the ongoing assessment and control of risks associated with trains passing signals at danger. An assessment using the model that was dated 1 December 2020 was provided by V/Line as being that applicable to SST535 at the time of the SPAD on 23 November 2020. The signal had been ranked as the 50th highest for risk. Approximately 250 signals had been assessed using the SPADAM tool by around the time of the incident. Signal SST535 had obtained a semi-quantitative risk exposure score of 1940, which fell below the normal V/Line threshold of 2500 for increasing the priority of introducing further risk controls.
Figure 7: Signal SST535 at stop
Source: CITS, observed post-incident
Other SPADs at or near SST535
Signal SST535 was located on the ‘Down Dual Gauge’ line, one of five bi-directional lines leading to platforms 1-5 at Southern Cross Station. Parallel to SST535 were three other mainline signals (SST533, SST527 and SST507). All were located at ground level and under the LaTrobe St bridge, as shown in Figure 3.
On 22 December 2017, a SPAD at signal SST533 was reported. The driver of train 8921 had received a medium speed warning aspect on the preceding signal. Train 8921 passed signal SST533 at stop by approximately 255 m. The driver was reportedly distracted by a person walking near the track. The South Geelong to Southern Cross service (train 8742) was waiting for a proceed aspect on signal SST578, which briefly displayed a proceed aspect before reverting to stop. The driver of train 8742 then saw train 8921 approaching in head-to-head conflict and flashed the headlight and sounded the whistle. Train 8921 stopped approximately 60 m from train 8742.
Eight SPADs[15] at signal SST507 involving shunting moves were reported between 11 December 2014 and 16 January 2021. A SPAD at signal SST535 involving a shunt move was also reported on 23 December 2019.
Risk management
Overview
The V/line Safety Management System (SMS)[16] had risk controls in place to manage the risk of a train-to-train collision because of a SPAD. Additional risk controls had been identified but not adopted at the time of the incident.
Procedural SPAD controls
V/Line applied the requirements of the 1994 Book of Rules and Operating Procedures for train operations. Section 2 rule 14b stated that no train must pass a home signal showing a stop aspect except under certain circumstances, which did not apply for this incident.
Engineering controls
SPAD Detection (in conjunction with radio communication)
The train control system at Southern Cross was equipped with SPAD detection such that an alarm was activated at the signaller’s workstation in the signal box if a train passed a controlled signal[17] at stop. Therefore, the system had the potential to mitigate the consequences of a SPAD occurrence by the signaller making a radio broadcast requesting trains to stop (as was the case in this instance).
The V/Line Book of Rules and Operating Procedures (revision 7) referred to a SPAD alarm in section 36, rule 14, part g. This rule defined the steps a controlling signaller must take on observing a SPAD alarm in relation to a SPAD at a TPWS location. SST535 was not a TPWS location and the V/Line Book of Rules and Operating Procedures did not define actions to be taken on observing a SPAD alarm for non-TPWS locations.
Train Protection and Warning System
Trains 8239 and 8156 were equipped with TPWS equipment that would activate a brake application where a train passed a signal at stop and the signal was linked to track-mounted TPWS transmitters. The system was also capable of enforcing medium speed signal aspects and train speeds through junctions at chosen locations. The V/Line passenger train fleet was equipped with this system to facilitate operation on the Regional Fast Rail (RFR) network which began operations with a maximum speed of 160 km/h in 2005. TPWS was extensively utilised on the V/Line network however signal SST535 was not equipped with TPWS at the time of the incident.
Flank protection
Flank protection is defined as protection from overrunning movements approaching on converging tracks, usually by additional point interlocking or train detection.
The V/Line standard for signal principles (NIST-12.0, revision 3, dated 10/8/2020) referenced catch protection as providing physical protection of main line moves from the unauthorised movement of vehicles from sidings, yards, or maintenance facilities. It is described in the standard as a form of flank protection[18] which is provided to prevent a train from being hit in the side by another train. No other references to flank protection were provided in the standard.
Flank protection is often provided through the setting of signals and points. In Figure 8: for example, a route from signal SST578 is at proceed for train A. Points 421 are set to the normal (straight through) position so that if train B proceeds past signal SST572, it is not routed into the side of train A. That is, the flank of train A is protected by points 421 set normal and routing train B straight ahead rather than towards the junction.
Figure 8: Simplified track layout for the relevant tracks at Docklands
Image shows a simplified representation of the track layout at Docklands with a route called from signal SST578 (green).
Source: ATSB and CITS
However, for the SPAD that occurred on 23 November 2020, similar protection was not available for an unauthorised movement past signal SST535 since there were no facing points to route the movement of train 8239 away from the junction.
Flank-track protection
Where flank protection cannot be provided by setting flank points, the provision of flank-track protection can be considered. If a route is set over a junction, flank-track protection requires the tracks between a signal protecting a converging route and the junction to be clear before the signal will display a proceed aspect.
Figure 9 provides an example of a route called from signal SST578 for train A. However, if train B passes signal SST535 at stop (SPAD) and occupies a track circuit between the signal and the junction (tracks 419T and/or 401T), a potential conflict with train A would be imminent. If flank-track protection was provided, any unauthorised occupancy of track circuits 419T or 401T would revert signal SST578 to a stop aspect. This would provide the opportunity for the driver of train A to react and stop prior to the junction and the potential conflict with train B (braking distances permitting and assuming train A had not already passed signal SST578).
Figure 9: Simplified track layout for the relevant tracks at Docklands
Image shows a simplified representation of the track layout at Docklands with a flank-track occupied by train B. While a route has been called from signal SST578 for train A, flank-track protection would place signal SST578 at stop.
Source: ATSB and CITS
However, the risk control of flank-track protection was not provided for the section of track where the SPAD occurred on 23 November 2020.
Train Vigilance System
Trains 8239 and 8156 were both equipped with vigilance control systems that verified the driver was not incapacitated by monitoring task-linked activities. In the absence of any such activities, the systems would provide intervention through alarms and subsequently by applying the train’s brakes. In this instance, recordings from both trains indicated that the drivers were providing active task-linked inputs and there were no activation of the trains’ brakes by the vigilance systems.
Interview comments revealed that the driver was distracted by task unrelated thoughts on the approach to signal SST535. While there is diversity in the definition of distraction, a version commonly referenced is:
the diversion of attention away from activities critical for safe driving toward a competing activity.[19]
Attention is conceived as a focusing response to a stimulus or task that reflects a state of arousal or concentration.[20] Studies indicate that attention paid to a particular stimulus or task generally occurs in the context of competition among multiple stimuli or tasks for limited processing capacity.[21][22] Multiple stimuli or tasks that make simultaneous demands on an individual’s central processing mechanism will tend to interfere with each other. These demands can come from a range of factors either inside or outside a vehicle, that draws on the limited physical, visual, and cognitive resources, resulting in a degradation of the driver’s performance. Thought intrusions, or mind-wandering, can be a type of distraction. In train driving, the inherent propensity to mind-wandering can generate an unacceptable level of operational risk.
Should one or more of these competing demands be of sufficient magnitude to interfere with or divert attention from the original focus of attention, then the individual becomes distracted.[23] It is within the context of attention that the process of distraction occurs. According to Nelson et al. (1993) this involves (i) a primary task (ii) a secondary or distracting stimulus or task (i.e., distractor) and (iii) the diversion of attention in response to the secondary task.
The driver of train 8239 reported being distracted by a personal issue on the afternoon of the incident and that they were reminded of this by a passenger who had just missed the departure of the train from Southern Cross Station
Distraction is strongly linked to decrements in driving performance and a higher risk of accident by motor vehicle drivers.[24][25] While rates of distraction amongst train drivers in Australia are not available, research from the U.K.[26] of 1021 reported SPADs between 2006 and 2009 on Network Rail managed infrastructure found approximately one third of SPADs in this period were associated with some form of distraction or inattention.[27]
The driver of train 8239 reported they sighted another stop signal further down the track (signal SST991 at Dudley St) and associated this signal with the warning provided by SST537 that the next signal would be at stop. Attention plays an important role in visual inspection strategy, especially in planning eye movements either toward locations preselected by expectations or toward an object that automatically attracts attention.[28] Research has found that mind-wandering is associated with horizontal narrowing of motor vehicle drivers’ visual scanning process.[29][30]
During their training, V/Line trainee train drivers were made aware of the importance of controlling distraction and advised of factors which can lead to distraction. Drivers were also made aware of techniques to manage distraction, and to refocus after distraction. This information was also published by V/Line in their Professional Driving Booklet. While these techniques to control distraction are not mandatory, drivers were encouraged to determine or develop the ones that worked best for themselves.
In this incident the distraction was at a critical time after departure and when the train was approaching signal SST535. While the driver was familiar with techniques to manage distraction and reported having acknowledged the warning signal before signal SST535, this was insufficient in preventing the SPAD.
Reading through signal SST535
Reading through or reading across to another signal was listed as a common cause of passing a signal at stop in the V/Line Professional Driving Booklet. Often, the scenario considered is not stopping at a signal due to sighting a proceed signal beyond the stop signal and incorrectly acting in response to the proceed signal. However, just as relevant is the scenario that existed in this case. The driver advised not observing SST535 and intending to stop at another signal beyond.
To assist in the assessment and control of risks associated with trains passing a signal a danger, V/Line used the Signal Passed at Danger Assessment Model (SPADAM). For the signal being assessed, information relating to the signal location, signal characteristics, rail traffic volumes, consequence factors (such as track speed), and control measures were inputs to the model. As an output, the model provided a ‘likelihood score’, ‘exposure score’, and ‘consequence score’ which were combined to provide an overall risk exposure score for the signal.
In relation to the input of ‘signal sighting’, there were 13 factors considered, including ‘read across (adjacent line/track)’ and ‘read through (same line/track). Signal SST535 had been assessed against the model on a number of occasions. For the assessment of January 2020, ‘read across’ had been assigned a risk score of five, corresponding to ‘definite potential to read across’. Signal SST535 had been assigned a risk score of zero for ‘read through’, corresponding to there being no potential to read through to another signal. Had the signal been assessed as having a ‘definite potential to read through’, then the risk score for the signal would have increased from 1940 to 2116 and would have still been below the normal V/Line threshold of 2500 for increasing the priority of introducing further risk controls.
Based on the risk score calculated for signal SST535, TPWS was identified as a potential control for further investigation. The model identified ‘adequate length of signal overlap’ and ‘SPAD alarm and signaller response’ as existing signal location control measures.
Flank and flank-track protection
At junctions, flank protection is a means of preventing collisions of trains by setting points to prevent unauthorised movement of another train from also occupying the junction. That is, points are set to route the unauthorised movement away from the junction. In the SPAD incident of 23 November 2020 such flank protection was not available for an unauthorised movement past signal SST535 since there were no facing points to route the unauthorised movement of train 8239 away from the junction.
Where flank protection cannot be provided, flank-track protection can be considered. If a route is set over a junction, flank-track protection requires the tracks between a signal protecting a converging route[31] and the junction to be clear before the signal will display a proceed aspect.
When train 8239 passed signal SST535 at stop and continued towards the junction, signal SST578 continued to display a proceed aspect for train 8156. Consequently, both trains were on a converging path and the risk of collision was significantly increased. Had flank-track protection been included in the signalling design, any SPAD at signal SST535 would have restored signal SST578 to stop. In this instance, train 8156 was relatively close to signal SST578 when the SPAD occurred at signal SST535, so there may have been insufficient time to stop prior to passing the signal. However, the installation of flank-track protection at this location would have reduced the risk of collision.
Infrastructure standards pertinent to this event did not specifically reference the potential application of flank-track protection. V/Line signalling standards did not call for flank-track protection to be considered.
Although not published at the time of the 2014 commissioning of new infrastructure at this location, subsequent RISSB standards[32] also did not reference the potential control of flank-track protection,[33]although the control of flank protection was referenced in RISSB AS 7711:2018 Signalling Principles, and RISSB AS 7724:2020 Unauthorized movement protection - Operational requirements.
Flank-track protection was referenced by some infrastructure managers in Australia. Signalling principles[34] for the Adelaide network required flank protection to be provided where a risk assessment determined the track layout warrants additional protection. The standard stated:
Where it is not practicable to provide flank protection by setting flank or trap points, and a significant safety benefit would arise, the provision of flank track section overrun detection at vulnerable signals should be considered. It may be initiated by overlap track section, or treadle, occupied without signal having cleared, or by sequential operation of track sections (e.g. overlap track occupied after berth track occupied). It may effect automatic replacement of conflicting signals…
An inquiry[35][36] into the Ladbroke Grove (U.K.) incident on 5 October 1999 considered the availability of automatic replacement of a signal at danger where a SPAD had occurred, and the layout was such that there was a significant danger of collision. A recommendation of the inquiry resulted in a Railway Group Standard being produced for U.K. railway infrastructure managers[37] which stated:
Overrun detection shall usually be provided so that where a train overruns a stop signal which protects an area of conflict, other stop signals protecting the same area of conflict are automatically placed or maintained at danger. The replacement of signals to danger shall take place as quickly as possible after an overrun occurs.
Authority-overrun protection at SST535
Risk review for the initial installation in 2014
The risk review to determine fitment of TPWS considered a potential collision type of ‘Plain line rear-on or buffer’ for a SPAD at signal SST535. A potential collision input for the model of a head-on or side-on collision, that may have been experienced on 23 November 2020, was not considered for the 2014 analysis of a SPAD at signal ST535. Using the semi-quantitative input rankings of the model, a ‘head-on’ collision type would have resulted in a higher overall risk ranking score for signal SST535. If a ‘head-on’ potential collision type had been attributed to signal SST535, the resulting consequence potential score and final risk ranking score would have placed signal SST535 in the ‘Potentially Severe’ category, and the signal would probably have been equipped with TPWS.[38]
TPWS proposal of 2020
V/Line provided documentation to the investigation that showed that in January 2020 V/Line costed a series of projects for installing TPWS, one of which was for the Southern Cross area and included signal SST535. The proposal was based on Southern Cross being identified as a high risk SPAD location and included input from the SPADAM model.[39] V/Line had commenced the funding process, but it had not been finalised at the time of the SPAD in November 2020.
Radio communications
Instructions for radio communications during an emergency were provided in documents SAPR-78 Verbal Safety Critical Communications Protocol and train control training unit NCT5, titled Communications. Both documents allowed for an emergency message to be sent when the passage of a train is endangered and require an emergency message to be answered immediately. Both documents stated that an emergency message is commenced with the phrase “Emergency, Emergency, Emergency.”
The V/Line Book of Rules and Operating Procedures (revision 7), Safety Critical Communications Protocol, and the training unit provided generic advice and allowed for a broad range of scenarios. They did not provide specific instructions on communicating with multiple trains in an emergency. The V/Line Verbal Safety Critical Communications Protocol stated that Rail Safety Workers must use the principle of safety critical communications being accurate, brief, and clear.
The signaller promptly commenced a radio broadcast to the driver of train 8156 on observing CCTV of train 8239 approaching signal SST535 and anticipating that the train would not stop at the red signal. This broadcast was heard by train 8239 and resulted in the trains receiving enough warning time to stop short of each other.
Other options were available to the signaller including a broadcast directed at both trains simultaneously, or a broadcast for all trains to stop. V/Line procedures do not provide specific advice on the preferred option in such a scenario.
The signaller stated later at interview that they were aware of the requirements concerning an emergency message, though during the incident used the word ‘urgent’ rather than ‘emergency’ to warn the driver of train 8156.
ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition, ‘other findings’ may be included to provide important information about topics other than safety factors.
These findings should not be read as apportioning blame or liability to any particular organisation or individual.
From the evidence available, the following findings are made with respect to passenger train 8239 passing signal SST535 at danger and near collision with another passenger train at Docklands, Victoria, on 23 November 2020.
Contributing factors
The driver of train 8239 was probably distracted when approaching ground-mounted signal SST535 and did not notice it displaying a stop indication. The driver probably noticed a gantry-mounted stop signal located further along the track and continued past signal SST535.
The absence of authority-overrun protection (such as TPWS) at signal SST535 increased the potential consequences of a SPAD. (Safety issue)
The V/Line risk assessment for signal SST535 that was conducted in 2014 did not consider a head-on or side-on collision as a credible scenario. As a result, TPWS was not considered a necessary control at the time of commissioning.
Other factors that increased risk
Signal SST578 did not restore to danger when train 8239 SPAD signal SST535. With signal SST578 at proceed, the opportunity for the signalling to provide a warning to train 8156 of a potential conflict condition was not available.
V/Line signalling standards did not identify flank-track protection as a control to prevent collision because of a SPAD, and none was installed at the incident location. The absence of flank-track protection increased the risk of side-on collision at the junction of track SST416T.
RISSB signalling standards did not identify flank-track protection as a potential control to prevent collision because of a SPAD.
Other findings
The signaller promptly broadcast a warning to the driver of train 8156 to stop their train, preventing a potential collision.
There was no specific advice in the V/Line radio communication directions for a signaller to direct multiple trains in an emergency.
Safety issues and actions
Central to the ATSB’s investigation of transport safety matters is the early identification of safety issues. The ATSB expects relevant organisations will address all safety issues an investigation identifies.
Depending on the level of risk of a safety issue, the extent of corrective action taken by the relevant organisation(s), or the desirability of directing a broad safety message to the rail industry, the ATSB may issue a formal safety recommendation or safety advisory notice as part of the final report.
All of the directly involved parties were provided with a draft report and invited to provide submissions. As part of that process, each organisation was asked to communicate what safety actions, if any, they had carried out or were planning to carry out in relation to each safety issue relevant to their organisation.
Descriptions of each safety issue, and any associated safety recommendations, are detailed below. Click the link to read the full safety issue description, including the issue status and any safety action/s taken. Safety issues and actions are updated on this website when safety issue owners provide further information concerning the implementation of safety action.
Safety issue description: The absence of authority-overrun protection (such as TPWS) at signal SST535 increased the potential consequences of a SPAD.
Additional safety actions
Whether or not the ATSB identifies safety issues in the course of an investigation, relevant organisations may proactively initiate safety action in order to reduce their safety risk. The ATSB has been advised of the following proactive safety action in response to this occurrence.
Additional safety action by V/Line Corporation
Coaching and a return-to-work plan has been implemented for the driver of train 8239, and the signaller has undertaken additional communications training.
Additional safety action by RISSB
RISSB advised that flank - track protection has been recorded for inclusion when the signalling principles standard AS 7711 is next under review.
Glossary
AS Australian Standard
CCTV Closed-circuit television
DMU Diesel Multiple Unit
EWRM Enterprise-Wide Risk Model
LEDLight-emitting diode
LRS Local Radio System
ONRSR The Office of the National Rail Safety Regulator
RFR Regional Fast Rail
RISSB Rail Industry Safety and Standards Board
RRL Regional Rail Link
SMS Safety Management System
SPAD Signal Passed at Danger
SPADAM Signal Passed at Danger Assessment Model
SRRT SPAD Ranked Risk Tool
TCSTrain Control System
TPWS Train Protection and Warning System
UK United Kingdom of Great Britain and Northern Ireland
VDU Video Display Unit
Sources and submissions
Sources of information
The sources of information during the investigation included the:
V/Line
V/Line personnel
Telstra
Event recorders from trains 8156 and 8239
Signalling event logger
Radio broadcast recordings
Bureau of Meteorology
CCTV footage from Southern Cross Station
Photographs taken on the day of the incident
References
Berlyne DE (1960) Conflict, arousal and curiosity, McGraw-Hill, New York.
Broadbent DE (1958) Perception and communication, Pergamon Press, New York.
Cullen Rt. Hon Lord (2000a) The Ladbroke Grove Rail Inquiry: Volume 1, Health and Safety Commission, London.
Cullen, Rt. Hon Lord (2000) The Ladbroke Grove Rail Inquiry: Volume 2, Health and Safety Commission, London.
Galera C, Orriols L, M’Bailara K, Laborey M, Contrand B, Ribéreau-Gayon R, Mason F, Bakiri S, Gadbaude C, Fort A, Maury B, Lemercier C, Cours M, Bouvard M, Lagarde E (2012) ‘Mind wandering and driving: responsibility case-control study’,BMJ, 345, doi: https://doi.org/10.1136/bmj.e8105.
Government of South Australia Rail Commissioner (2017) South Australia Signalling Principles and Practices for the Adelaide Metropolitan Passenger Rail Network, Engineering Standard, Adelaide.
He J, Becic E, Lee Y, and McCarley JS (2009) ‘Identifying Mind-wandering Behind the Wheel’, Proceedings of the Human Factors and Ergonomics Society 53rd annual meeting, doi:10.1177/0018720810391530
Henderson JM (1993) ‘Visual Attention and Saccadic Eye Movements in Complex Visual Tasks’, Behavioural and Brain Sciences, 16(3), 579-580. doi:10.1017/S0140525X00031721
Kahneman D (1973). Attention and effort, Prentice Hall, New Jersey.
Klauer SG, Dingus TA, NealeVL, Sudweeks JD, and Ramsey DJ (2006) The Impact of Driver Inattention on Near-Crash/Crash Risk: An Analysis Using the 100-Car Naturalistic Driving Study Data, Report No. DOT HS 810 594. National Highway Traffic Safety Administration, Washington DC.
Lee JD, Young KL, and Regan, MA (2008) Defining driver distraction. In: Regan MA, Lee JD, Young .L (Eds.) Driver Distraction: Theory, Effects, and Mitigation, CRC Press Taylor & Francis Group, Boca Raton, FL, USA.
Luke T, Heavisides J, and Basacik D (2013) Management of Distraction Risk from Mobile Phones in the UK Rail Industry. Driver distraction and inattention. Advances in Research and Countermeasures. Ashgate, UK.
Nelson JE, Duncan CP & Kiecker P L (1993) ‘Toward an understanding of the distraction construct in marketing’, Journal of Business Research, 26, 201-221,https://doi.org/10.1016/0148-2963(93)90032-K
Office of the National Rail Safety Regulator (n.d.) national-safety-data, ONRSR website, accessed 2 July 2021.
Rail Safety Standards Board (2000), Railway Group Standard RGS GK/RT/0064 Issue 1, Provision of overlaps, flank protection, and trapping, London.
Rail Safety National Law (SA) Act 2012, part III division 1.
Rail Industry Safety and Standards Board (2018), AS 7711:2018 Signalling Principles, Rail Industry Safety and Standards Board, Queensland.
Recarte M, Nunes L (2000) ‘Effects of Verbal and Spatial-Imagery Tasks on Eye Fixations While Driving’, Journal of Experimental Psychology: Applied, Vol. 6, No. 1,31-43.
V/Line (2108) Train control training unit NCT5: Communications,TLI42215 Certificate IV in Rail Network Control.
V/Line (2020) 1994 Book of Rules and Operating Procedures (revision 7).
V/Line (2020) Signalling principles, NIST-12.0.
V/Line (n.d.) Professional Driving Booklet MSR01345
Submissions
Under section 26 of the Transport Safety Investigation Act 2003, the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. That section allows a person receiving a draft report to make submissions to the ATSB about the draft report.
A draft of this report was provided to the following directly involved parties:
V/Line
Driver of train 8239
V/Line signaller on duty at Southern Cross at the time of the incident
ONRSR
RISSB
Any submissions from those parties will be reviewed and, where considered appropriate, the text of the draft report will be amended accordingly.
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.
Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.
The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
Occurrence summary
Investigation number
RO-2020-019
Occurrence date
23/11/2020
Location
Docklands, about 700 m north-west of Southern Cross Station
On 6 November 2020, the pilot of a S.E.D.E. Morane-Saulnier MS.893A (Rallye) aircraft, registered VH‑UQI, was conducting a private flight from Moruya, New South Wales, to Archerfield, Queensland. About 22 km south-west of Archerfield Airport, the engine began running rough before eventually failing. The pilot elected to conduct a forced landing into an open but slightly undulating paddock. The approach direction resulted in a tail wind landing. The aircraft over-ran the open area before it impacted with a grove of trees, significantly disrupting the aircraft structure. A post impact fire consumed most of the fuselage.
Witnesses to the forced landing arrived at the scene and removed the unconscious pilot from the periphery of the fire zone and called emergency services. The pilot was seriously injured, and the aircraft was destroyed.
What the ATSB found
The aircraft’s engine had a catastrophic mechanical failure. The initiation of the mechanical failure was the separation of the number 2 piston connecting rod which subsequently created a hole in the upper crank case and seized the engine. The engine failure reduced the pilot’s forward visibility due to engine oil over the windscreen, as well as smoke created by escaping oil on the exhaust system.
The pilot was ferrying the aircraft on behalf of the owner and had limited aircraft type experience and knowledge of its performance capabilities. Additionally, it was found that the pre-flight planning was limited, an emergency locator transmitter or portable locator beacon was not carried on board the aircraft for the flight.
The aircraft engine had not been overhauled since 1997. The aircraft had limited usage for an extended period, possibly with no specific engine preservation done while in storage. Had the engine been overhauled at the manufacturer's recommended calendar time, the connecting rod journal bearings would have been replaced with post-modification bearings as part of the overhaul process.
Safety message
This investigation is a timely reminder for aircraft owners and maintainers to be cognisant of the manufacturer’s service information which ensures that the serviceability of engine and airframe systems are maintained to the highest standards. This includes strict monitoring of on-condition items, and that replacement of some parts may be warranted to ensure continued and safe operation. Consideration should also be given to preservation of the engine and its systems, should an aircraft be infrequently utilised.
The investigation
Decisions regarding whether to conduct an investigation, and the scope of an investigation, are based on many factors, including the level of safety benefit likely to be obtained from an investigation. For this occurrence, a limited-scope investigation was conducted in order to produce a short investigation report and allow for greater industry awareness of findings that affect safety and potential learning opportunities.
The occurrence
On 6 November 2020, at about 0800 Eastern Daylight-saving Time,[1] a S.E.D.E. Morane-Saulnier MS.893A Rallye (Rallye) aircraft, registered VH-UQI, departed Moruya Airport, New South Wales, for a private flight to Archerfield Airport, Queensland. The pilot, who was ferrying the aircraft on behalf of the owner and was the sole occupant, conducted the flight under the visual flight rules[2]and had planned fuel stops in Bathurst and Gunnedah, NSW. The ferry flight was a planned delivery of the aircraft to the new owner and was intended to take about 5 hours flight time.
Figure 1 shows the flight track for the aircraft. The pilot flew to Bathurst without incident, where the aircraft was refuelled. Departing Bathurst, the aircraft tracked toward Gilgandra, before changing course to Gunnedah. The pilot recalled tracking around Danger area[3] 538B, a military flying area, as the reason for this indirect route.
After refuelling, the aircraft departed Gunnedah for Archerfield. At about 55 km south-west of Archerfield, the pilot descended to below 2,000 ft above mean sea level (AMSL). The pilot’s intention was to track between two restricted areas[4] in the vicinity of Greenbank, Queensland and continue their descent to the Goodna inbound reporting point for entry into Archerfield Airport.
At about 1425 Eastern Standard Time,[5] while cruising at 2,000 ft and about 32 km south-west from Archerfield, the pilot made an inbound radio call to Archerfield air traffic control tower requesting an ‘airways clearance’, adding that their location was to the south-east of Archerfield. This call was made on the Brisbane approach frequency. Brisbane approach advised the pilot that their broadcast was on the incorrect frequency and provided the correct frequency for Archerfield Tower, however, this was not acknowledged by the pilot.
About 90 seconds later, the pilot broadcast a MAYDAY[6] call stating:
MAYDAY MAYDAY. Uniform Quebec India Uniform Quebec India. 2-0 miles south-east of Archerfield. Total engine failure.
That broadcast was again made on the Brisbane approach frequency. Brisbane approach acknowledged the MAYDAY and no further radio calls were made by the pilot of VH‑UQI.
Figure 1: Recorded flight track of VH-UQI from Moruya, NSW to accident site
Source: Google Earth and OzRunways, annotated by the ATSB
The pilot recalled that the aircraft ran rough and lost engine power, before complete engine stoppage. At the time, VH-UQI was approaching numerous built-up areas and the pilot had limited suitable forced landing area options. The pilot reported that their forward vision was obscured by black smoke and oil emanating from the engine. The recorded flight path showed that the aircraft conducted a right turn towards an open paddock (Figure 2).
The pilot had no recollection of the wind direction from the Archerfield aerodrome terminal information service[7] or from local wind indicators. The final approach was in a south-westerly direction, which was downwind. The aircraft touched down about two-thirds of the way into the paddock and then became temporarily airborne due to ground undulations before impacting trees. The impact resulted in significant disruption to the aircraft structure and initiated a post-impact fire.
Figure 2: VH-UQI flight path and forced landing area
Source: Google Earth, OzRunways and witness descriptions, annotated by the ATSB
Witnesses under the flight path observed the aircraft trailing black smoke, saw it turn towards the paddock, and subsequently observed smoke rising in the area that the aircraft had landed. They immediately attended the accident site and located the pilot at the edge of the fire, outside the cockpit. They moved the pilot a safe distance from the wreckage, alerted emergency services, and commenced first aid while waiting for emergency services to arrive. The pilot was seriously injured, and the aircraft was destroyed.
Context
Pilot information
The pilot held a valid private pilot (aeroplane) licence, issued in August 2020 (3 months before the accident) with a single engine aeroplane class rating and endorsements for manual pitch propeller control and retractable undercarriage. The pilot held a valid Class 2 aviation medical certificate that was issued on 30 July 2019 with no listed restrictions. The pilot had about 99 hours total flying time prior to the accident flight.
Aircraft type training and familiarity
The pilot had previous flying experience in Cessna 152, 172, and Piper PA28 aircraft. They had planned to carry out a familiarisation flight on VH-UQI with an instructor 2 days prior to the flight, however due to other work commitments, they had arrived at the aerodrome late in the afternoon after the instructor had left for the day. The pilot then conducted a short (18 minute) familiarisation flight by themself. Prior to that, the pilot had had no familiarisation on the aircraft type to allow them to experience the slow speed and short landing performance characteristics of VH-UQI (see Aircraft information). Further, the pilot reported at interview that they were not aware of the aircraft’s performance characteristics.
Prescribed aircraft type training was not required under Civil Aviation Safety Regulation 1998 (CASR) Part 61 in relation to the Rallye. Furthermore, there was not a large aircraft performance disparity between the Rallye and the Piper Cherokee PA-28 that the pilot was previously operating.
Flight planning
After discussing the flight with an instructor, the pilot opted to conduct the flight inland (rather than along the coast) to avoid controlled airspace, which also enabled them to fly at a higher altitude and to have more favourable weather for the flight. The pilot stated they were utilising a tablet with the OzRunways RWY[8] application for navigation.
Danger area D538B (Figure 1), located between Bathurst and Gunnedah was visible on the OzRunways application when active on RWY, however there was no evidence that the pilot had previously considered avoiding D538B during pre-flight planning. A direct route to Gunnedah was possible at the planned altitude on the day of the flight.
Archerfield Airport was a busy metropolitan aerodrome operating as Class D controlled airspace. The pilot was unfamiliar with the Archerfield area and Class D operations and stated that they had an increased level of ‘nervousness’, due to inexperience when operating in controlled airspace.
The pilot recalled that their fuel plan was to fill the aircraft to maximum at Bathurst and Gunnedah. This would have allowed sufficient fuel for the conduct of the flight. The total usable fuel quantity for the Rallye is 178 L. The aircraft was fuelled to full 2 days prior to departure. The pilot refuelled at Bathurst on the day of the accident with about 75 L and then again at Gunnedah, with about 90 L.
Meteorological Information
Forecast conditions for the delivery flight from Moruya to Archerfield provided by the Bureau of Meteorology (BoM) indicated good flying conditions, visibility more than 10 km, and little cloud along the intended track.
BoM also provided the ATSB with an Aviation Safety Investigation Meteorological Report regarding the weather conditions at the occurrence location. The following was noted:
Visibility greater than 10 km
Nil significant weather or cloud
Mod turbulence below 6,000 ft
Wind forecast from the south-south-west at 6-9 kt from 1,000-5,000 ft
One-minute automatic weather station observations were provided by the BoM for the nearest station to the accident site, Greenbank military base, which indicated that the wind close to ground level was fluctuating below 10 kt from east to north-east.
Aircraft information
The S.E.D.E. Morane-Saulnier MS.893A[9] Rallye is a single engine, low wing, 4 seat aircraft of all metal construction and fitted with fixed tricycle, trailing link undercarriage. It is powered by a Lycoming O-360 4-cylinder piston engine driving a Hartzell 2-blade constant speed propeller. It has interconnected full-span leading-edge slats,[10] wide-chord slotted ailerons,[11] and wide-span Fowler-type flaps.[12] The combination of full-span slats and large Fowler flaps provide the aircraft with its capability for slow-speed flight performance required for short field take-off and landing.
Information from the aircraft flight manual indicated that the landing distance required for the aircraft in nil wind conditions at 26° C, were about 160 m at 1,000 kg gross weight and about 125 m at 750 kg. Both distances were with flaps in full down position, extended to 30°. The approach speeds were 65 kt and 54 kt respectively.
VH-UQI was manufactured in France in 1969 and was imported into Australia in the same year. The aircraft total time in service was 2,321.92 hours and the previous annual inspection was at 2,312.73 hours on 20 May 2020. The aircraft had a current certificate of registration, airworthiness, and maintenance release with no noted defects. The previous owner had owned VH-UQI for about 20 years and had stored the aircraft for about 7 years at Moruya, a coastal airport. The aircraft had seen little use in that time and was sold because of this.
Engine information
The engine fitted to VH-UQI was last overhauled in 1997 and had accrued about 324 hours since overhaul. The time between overhaul schedule as listed in Lycoming Service Instruction SI 1009BE was 12 years or 2,000 hours, whichever came first.
Although the engine had exceeded the calendar schedule of the manufacturer’s time between overhaul, this was permissible when the engine was maintained in accordance with the Civil Aviation Safety Authority (CASA) on-condition[13] requirements. At the last annual inspection in May 2020, the maintenance organisation had completed a piston engine condition report, verifying the engine serviceability, which then permitted the engine to continue in service.
Connecting rod journal bearings
Copper-lead alloy connecting rod journal bearings were initially supplied by Lycoming prior to 1995. These were replaced by aluminium-tin alloy bearings, which were available between 1995 to 2001 (corresponding with the time of the last engine overhaul in 1997.) These were then superseded in September 2004 by Lycoming Service Instruction No. 1512. The aluminium-tin bearings were required to be replaced with the upgraded bearings (copper-lead alloy) whenever new bearings were to be installed (such as at engine overhaul).
Site & Wreckage information
The accident site was located about 22 km south-west of Archerfield Airport. The main wreckage was situated in trees at the south-west end of a sparsely vegetated paddock, which was oriented in a north-east / south-west direction and was about 400 m in length with a relatively clear approach from obstacles due to sparse vegetation. The first impact point was with a fence post, followed by intermittent wheel marks in the grass, indicating that the aircraft had bounced multiple times during the landing. The distance from initial impact with the fence to the main wreckage was about 170 m (Figure 3).
Figure 3: Aircraft ground contact and accident site
Source: Google Earth, annotated by the ATSB
The right-wing tip struck trees about 2 m above the ground and separated from the wing. The right wing then impacted another tree, between the wing root and midway along the wing, then separated from the fuselage. This impact pivoted the aircraft 90° to the right. The fuselage and left wing travelled a further 10 m before coming to rest. The forward left side of the aircraft impacted a large tree, resulting in the engine, firewall and nose gear separating from the fuselage.
The engine, fuselage and left wing were exposed to a post-impact fire, and the empennage section remained largely unburnt (Figure 4). Examination of the aircraft structure and flight controls did not identify any pre-impact defects. The flaps were determined to be in the full down position at impact.
Figure 4: VH-UQI accident site
Source: ATSB
On-site engine examination
On-site examination of the engine identified a large hole in the top of the crankcase, between the number 1 and 2 cylinders. Visible through the hole was the fractured camshaft and number 2 piston connecting rod (Figure 5).
Figure 5: Engine assembly showing a hole in the crank case and internal damage
Source: ATSB
A smaller hole was noted on the underside of the crankcase, adjacent the number 1 cylinder and forward of the number 2 cylinder. The propeller and it’s mounting flange on the crankshaft had fractured in overload level with the front of the crankcase and was not affected by fire.
The outer area surrounding the upper crankcase hole was heavily coated with engine oil, as were sections of windshield and the unburnt empennage. A coating of engine oil was evident on the inner surfaces of the engine cowls and over the outside of the exhaust muffler, which was the likely source of the black smoke. The engine cowls, right magneto and exhaust muffler had separated from the engine and were unburnt. The engine was removed from the accident site and taken to an approved overhaul facility for a further detailed examination by the ATSB.
Engine examination
The engine was disassembled and inspected under the supervision of the ATSB. The examination revealed that all components were heat affected from the post-impact fire. The crankcase had large holes either side of the number 2 cylinder and a series of adjacent impact marks on the internal surface. The number 2 connecting rod was fractured and separated from the crankshaft journal and piston. The connecting rod fracture surfaces were significantly damaged, which precluded any meaningful materials failure analysis.
The piston pin boss had fractured due to overstress; however, the piston pin showed no damage. The crankshaft showed significant impact damage and wear of the number 2 journal. The other journals were also discoloured but were otherwise undamaged. The number 2 journal bearing was destroyed, such that only small fragments remained. The number 1, 3 and 4 journal bearings did not exhibit any cracking, damage, or severe wear. Discrete areas of the bearing surface had a ‘cratered’ appearance, which was likely the result of localised melting of the thin bearing layer adjacent to the crankshaft journal. The absence of any significant operational wear associated with these areas, indicated that the melting was most likely due to the post-impact fire.
It was also found that the crankshaft oil supply galleries to the internal components were unobstructed. The damage to the number 2 conrod and bearing journals were consistent with the engine failure initiating due to breakdown of the number 2 bearing (Figure 6).
Figure 6: Damaged engine components removed from VH-UQI
Source: ATSB
The connecting rod journal bearings fitted to the engine for VH-UQI were part number LW-13521 and marked with a manufacture date of 12-95. These were premodification bearings composed of an aluminium-tin alloy on a steel backing, which had been superseded in September 2004 by Lycoming Service Instruction No. 1512. The LW-13521 bearings were required to be replaced with the upgraded bearings whenever new bearings were to be installed (such as at engine overhaul).
The upgraded bearings have a bearing surface composed of a copper-lead alloy, which provides increased durability and is more resilient to wear during operation. The properties of lead within the alloy acts as a lubricant, while the copper provides high strength and fatigue resistance. The aluminium-tin alloy bearings became standard use in Lycoming engines during the 1990’s. Prior to their introduction, the bearings used were made of a copper-lead alloy.
ATSB research on piston engine structural failure
In 2007, the ATSB published a research and analysis report (B20070191) into aircraft reciprocating (piston) engine failures. The report examines 20 high-power[14] piston engine structural failure occurrences in Australia, between 2000 and 2005. The report focused on failures of the combustion chamber, connecting rods and crankshaft assemblies. The failures of engine crankshafts could be linked to failure of the bearings, both crankshaft main bearings and the connecting rod (big end) bearings.
The report found an increasing trend (for the period 1993 – 2003) that bearings composed with an aluminium-tin alloy would separate from the steel backing material. The same separation was not observed on bearings with a copper-lead alloy.
The ATSB research report noted that the CASA Airworthiness Bulletin AWB 85-001 Issue 4 (April 2006), Textron Lycoming engine bearings, also stated that the aluminium-tin bearings had a high failure rate and were therefore being replaced with the original copper-tin bearings.
Aircraft storage practices
In March 2017, CASA released Airworthiness Bulletin AWB 85-021, Piston engine low utilisation maintenance practices. This AWB related to protection of piston engines, through preservation techniques dependent on aircraft inactivity.
The geographical location of the aircraft influences the extent of the preservation that should be considered by the operator and maintenance personnel. Aircraft engines exposed to coastal areas and environments where there is high relative humidity can experience corrosion at a greater rate than an engine located in an area with more favourable environmental conditions.
The recommendations were to have a preservation regime for engine protection to prevent internal engine wear due to corrosion, to carry out oil changes based on calendar time limits, and that engine ground running is not a substitute for regular flying and can aggravate the corrosion condition.
The preservation and utilisation for VH-UQI could not be determined due to the logbooks being carried onboard the aircraft for the ferry flight. These were to be delivered with the aircraft to the new owner, however they were consumed by fire at the accident site and could not be referenced. The previous owner stated that they could not remember any specific storage practices used to preserve the aircraft or the engine during periods on non-usage.
Survivability
The cabin structure surrounding the cockpit was severely disrupted during the accident sequence. Further, the pilot’s seat belt attachment failed at the inboard mounting point. That led to the pilot being ejected from the cockpit, fortuitously to an area outside the fire zone.
VH-UQI was not fitted with an emergency locator transmitter (ELT) and the pilot did not carry a portable locator beacon (PLB). The carriage of an ELT and/or PLB was a requirement under Civil Aviation Regulation (CAR) 252A unless, among other requirements, the aircraft would be operating within a 50 NM radius from the original point of departure.
The pilot had not lodged a flight plan or arranged a SARTIME[15] to be held by a responsible person. The new owner of VH-UQI was awaiting the arrival the aircraft at Archerfield Airport but was not in receipt of a flight plan.
Other information
Several flight planning resources exist to assist pilots with the entry to Class D airports such as Archerfield. The Civil Aviation Safety Authority Stay OnTrack series is a good example of this, providing detailed and easy to read instructions, illustrations, pictures and further references to increase understanding prior to arrival. In particular to Archerfield, there was a procedures overview for pilots that included providing air traffic control with the phrase ‘unfamiliar with Archerfield’ to assist pilots. There was also radio call proformas and detailed instructions for arrivals.
Safety analysis
Introduction
While enroute from Gunnedah to Archerfield, VH-UQI had a catastrophic engine failure about 22 km to the south-west of its destination. With reduced visibility due to smoke and oil on the windscreen, the pilot conducted a forced landing in an open, slightly undulating field with a 9 kt tail wind. The aircraft touched down towards the end of a clear area, impacted trees at the paddock boundary. The pilot was seriously injured, and the aircraft was destroyed.
This analysis will explore the engine history and failure, flight planning and decision making of the pilot in command, and post impact survivability factors.
Engine information
Engine failure mode
The ATSB determined that the initiating factor of the engine failure was likely the breakdown of the number 2 connecting rod journal bearings. This would have resulted in excessive clearance between the connecting rod and crankshaft journal. Therefore, this allowed increased flexure of the big end bearing housing under continued loading cycles, and ultimately fatigue failure of the connecting rod and damage to the surrounding components.
The ATSB research and analysis report B20070191 was based on information compiled from incidents involving high-power horizontally opposed piston engines. Although not high-power engine, the engine fitted to VH-UQI contained bearings that were composed of the same material which had failed in the high-powered engines. The ATSB report stated that the bearings with an aluminium-tin composition were found to have sections of the bearing material separate from the backing, leading to bearing failure. The upgraded bearings have a copper-lead alloy composition, which does not exhibit the material separation failure mode seen in the aluminium-tin type.
Analysis of the remaining connecting rod bearings removed from VH-UQIs engine showed limited damage to the bearing surface that might have indicated a developing, material-related failure mode. As such, from the available evidence, the ATSB was unable to conclusively determine the reason for the number 2 connecting rod journal bearing failure. However, the original bearings fitted to the engine and low aircraft utilisation without preservation have shown to contribute to previous bearing failures under similar circumstances.
Modification history
The connecting rod journal bearings fitted to VH-UQI were a pre-modification type that had been superseded in September 2004 by Lycoming Service Instruction No. 1512. The engine had been maintained in accordance with the CASA regulatory requirements for an on-condition engine and had not been overhauled since 1997 (23 years prior to the accident). Had the engine been overhauled utilising the engine manufacturer’s recommended calendar time of every 12 years, it is likely that the journal bearings would have been replaced with upgraded bearings which had improved endurance, corrosion, and wear qualities.
Low utilisation maintenance practices
Since the last engine overhaul in 1997, VH-UQI had flown about 324 hours, which was an average of about 14 hours per year. As the aircraft logbooks were destroyed in the post-accident fire, it is unknown if the aircraft had been under-utilised for extended periods of time prior to the flight and what preservation, if any, had been performed on the engine. No preservation activities were remembered by the previous owner, so it is possible none were done. It was unable to be determined if the limited usage may have led to the failure of the connecting rod bearing.
Emergency landing
After the engine failure, the pilot attempted to conduct an emergency landing into a paddock immediately to their right. They reported reduced visibility through the windscreen due to smoke and oil emanating from the engine during the conduct of the emergency landing. The length of the paddock chosen was about 400 m with a relatively clear approach. There was sufficient area to bring the aircraft to a stop safely with knowledge of the aircraft capabilities. The pilot was unaware of the local wind indicators and conducted a descending right turn from the original direction of travel. This led to the aircraft positioning to land with a tailwind, substantially increasing the landing distance required.
The tailwind significantly increased the aircraft groundspeed while landing, contributing to the aircraft touching down about two thirds of the way into the paddock, before passing between a fence post and a tree. Still travelling at significant speed, VH-UQI became temporarily airborne over ground undulations and then impacted trees. The lack of pilot familiarisation of the aircraft and its slow speed performance capabilities may have exacerbated the consequences of the off‑field landing.
Pre-flight planning and preparation
The pilot had conducted limited aircraft familiarisation prior to the accident flight. While specific aircraft type training was not required, the pilot was unaware of the aircraft’s slow speed performance capability. A full understanding of this capability may have been beneficial when responding to the engine failure and forced landing.
The pilot did not use a flight log or formal flight plan and diverted around Danger Area 538B adding an extra 150 km of non-essential distance to the flight track.
Many sources of information were available to educate and reduce the pilot’s anxiety over the entry to Class D airspace and in particular Archerfield. This information along with appropriate pre-flight preparation including awareness of local area procedures and correct radio frequencies for communication, would have prepared the pilot for the final stages of the flight and provided greater navigational awareness.
The lack of aircraft familiarisation before the ferry flight, minimal pre-flight preparation for the flight, the non-carriage of emergency locator beacon and absence of a flight note with a responsible person, substantially increased the safety risk of the flight.
Had the pilot utilised flight planning resources and gained an awareness of local operating information and publication for Archerfield, then they would have been less reliant on electronic navigation during the flight and more situationally aware.
Emergency locator transmitter
Emergency locator transmitters (ELT) and/or portable personal locator beacons (PLB) are carried on aircraft so that in the event of an accident in a remote location, the aircraft wreckage and its occupants can be located quickly and efficiently by SAR operations.
Finding the aircraft wreckage quickly not only increases the chance of survival of the occupants, but also reduces the risk to crew of SAR aircraft who commonly need to operate in less-than-optimal conditions. In this instance, not carrying an ELT and/or PLB, did increase the risk of delayed search and rescue action, however, in this case was fortuitously witnessed by nearby landowners. Additionally, the pilot did not leave a flight note with a responsible person in case the flight did not reach its intended destination, diverted to other locations, or if a timely activation of a search and rescue (SAR) response was required.
Findings
ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition ‘other findings’ may be included to provide important information about topics other than safety factors.
These findings should not be read as apportioning blame or liability to any particular organisation or individual.
From the evidence available, the following findings are made with respect to the engine failure and collision with terrain involving a S.E.D.E. Morane-Saulnier MS-893A, 22 km south-west of Archerfield Airport, Queensland, on 6 November 2020.
Contributing factors
The engine sustained a mechanical failure, most likely as a result of material degradation and impulse loading of the number 2 connecting rod journal bearing.
After experiencing an inflight engine failure, the pilot conducted a downwind forced landing into a paddock while experiencing reduced visibility from smoke and oil over the windscreen. The landing roll could not be arrested before over-running the paddock and impacting trees.
Other factors that increased risk
The pilot's pre-flight planning, preparation, and aircraft familiarisation was limited for the flight, leading to a reduced situational awareness and reduced ability to effectively manage the emergency.
The aircraft was not fitted with a fixed or portable emergency locator transmitter. Further, the pilot did not leave a flight note with a responsible person for the ferry flight. This increased the risk of post-impact survival factors, such as delayed search and rescue arrival medical attention.
Other findings
The aircraft had limited usage for an extended period, possibly with no specific engine preservation done while in storage.
Had the engine been overhauled at the manufacturer's recommended calendar time, the connecting rod journal bearings would have been replaced with post-modification bearings as part of the overhaul process.
Sources and submissions
Sources of information
The sources of information during the investigation included:
Under section 26 of the Transport Safety Investigation Act 2003, the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. That section allows a person receiving a draft report to make submissions to the ATSB about the draft report.
A draft of this report was provided to the following directly involved parties:
the pilot of VH-UQI
the owner of VH-UQI
the Civil Aviation Safety Authority
the maintenance provider.
A submission was received from the Civil Aviation Safety Authority. The submission was reviewed and, where considered appropriate, the text of the draft report was amended accordingly.
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.
Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.
The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
[1] Eastern Daylight-saving Time: Coordinated Universal Time (UTC) +11 hours.
[2] Visual flight rules (VFR): a set of regulations that permit a pilot to operate an aircraft only in weather conditions generally clear enough to allow the pilot to see where the aircraft is going.
[3] Danger area: Airspace of defined dimensions in which activities dangerous to flight may exist at specific times.
[4] Restricted area: Airspace within which the flight of aircraft is restricted in accordance with specified conditions.
[5] Eastern Standard Time: Coordinated Universal Time (UTC) +10 hours.
[6] MAYDAY: an internationally recognised radio call announcing a distress condition where an aircraft or its occupants are being threatened by serious and/or imminent danger and the flight crew require immediate assistance.
[7] Aerodrome terminal information service (ATIS): a continuous and repetitive broadcast that provides current, routine information to arriving and departing aircraft. That information normally includes current meteorological conditions at the airfield, as well as expected approach requirements.
[8] OzRunways utilises approved data for electronic maps to be used for navigation. RWY is the application utilised on Android devices.
[9] During 1966, the Morane-Saulnier company changed its name to Societe de Construction d'Avions de Tourisme et d'Affaires (S.O.C.A.T.A.). The aircraft is also known as a SOCATA MS.893A.
[10] Slat: Moveable portion of leading edge of aerofoil, which in cruising flight is recessed against main structure and forms part of the profile; at high angle of attack either lifts away under its own aerodynamic load or is driven under power to move forward and down and leave an intervening slot.
[11] Aileron: Control Surface, traditionally hinged to outer wing and forming part of the trailing edge, providing control in roll about the longitudinal axis.
[12] Fowler flap: Special form of split flap that moves at first rearwards and then downwards along a track, thus producing an initial large increase in lift and at full deflection giving high lift and drag for landing.
[13] On-condition: Performed only when the condition of an item demands, instead of at scheduled intervals.
[14] The high-power engines analysed as part of the study were Lycoming TIO-540 and IO-540, and Continental TSIO-520 and GTSIO-520 engines.
[15] SARTIME: An abbreviation for ‘time search action required’. A SARTIME is the time nominated by a pilot for the initiation of Search and Rescue (SAR) action.