Engine failure and collision with terrain involving Robinson R44, VH-KJJ, 154 km south-west of Timber Creek, Northern Territory, on 14 June 2015

Final report

Safety summary

What happened

On 14 June 2015, the pilot of a Robinson Helicopter Company R44 helicopter, registered VH-KJJ, was conducting cattle mustering operations at Waterloo Station, about 154 km south-west of Timber Creek, Northern Territory. After refuelling from drum fuel supply, the helicopter took off and, a short time later, experienced a loss of engine power at low altitude. The loss of engine power was a result of fuel starvation due to contaminants introduced into the helicopter’s fuel system during the drum refuelling. The loss of engine power required the pilot to conduct an autorotation and forced landing.

For reasons that could not be determined, the pilot was unable to satisfactorily reduce the rate of descent before the helicopter impacted the ground heavily. The pilot survived the impact but later succumbed to their injuries. The helicopter was destroyed.

What the ATSB found

The ATSB identified that the operator did not have adequate procedures to ensure fuel quality during drum refuelling.

The pilot was overdue for a helicopter flight review for low-level helicopter mustering operations. This potentially reduced the pilot’s familiarity and proficiency with managing engine failures and autorotations from low altitude. Had the pilot been able to satisfactorily reduce the rate of descent before touchdown, the impact forces would have been reduced.

The helicopter was likely ‘hot refuelled’, meaning that as a pilot only operation, the pilot had to exit the helicopter to refuel while it was operating. This increased the risk of loss of control of the helicopter as the flight controls were unmonitored.

What's been done as a result

The operator has informed the ATSB that they now test fuel supplies with water detection paste, and have restricted any aviation fuelling activities to be performed by authorised personnel.

In addition, an operator trial of a filter monitor-type filter highlighted that, although filter monitors increased the probability of detecting water contamination while refuelling, operators should assess the suitability and practicality of the available filter monitors for their operations.

Safety message

A number of defences are available to eliminate or significantly reduce the chance of using contaminated fuel from drum fuel supplies. These include:

  • application of appropriate aviation drum handling and storage methods
  • testing drum fuel supplies for contaminants prior to undertaking refuelling activities
  • use of filter monitors on drum hand pump supply lines
  • conducting fuel drains from aircraft after each refuel to ensure fuel quality.

In addition, the ATSB cautions pilots and operators to conduct hot refuelling in accordance with the aircraft flight manual and Civil Aviation Safety Authority regulations. Further, leaving the flight controls of an operating Robinson Helicopter Company R44 helicopter to conduct refuelling increases the risk of a loss of control.

Finally, this accident provides a timely reminder that the conduct of recurrent flight training allows pilots to practice and better respond to time critical emergencies such as those that occur from a low altitude.

The occurrence

On 14 June 2015, the pilot of a Robinson Helicopter Company R44 Raven 1 helicopter, registered VH-KJJ (KJJ), was conducting cattle mustering operations at Waterloo Station, about 154 km south-west of Timber Creek, Northern Territory (Figure 1). At about 0700 Central Standard Time[1], the pilot reportedly refuelled KJJ from the station’s main aviation gasoline (Avgas) fuel storage tank and conducted a daily inspection of the helicopter before commencing the days mustering activities.

Figure 1: Accident site location 

Figure 1: Accident site location, about 154 km south-west of Timber Creek, Northern Territory

Source: Google earth, modified by the ATSB

The mustering activities required two additional helicopters (Robinson R22 helicopters) to assist with drafting[2] cattle toward holding yards that were located about 19 km east-south-east of the Waterloo Station homestead. The pilots of the helicopters worked together to herd the cattle south along a dry creek bed that led toward the holding yards.

After operating the helicopter for about 3.5 hours, the pilot of KJJ radioed the R22 pilots to inform them of the need to refuel KJJ from a drum fuel supply that was close to the area of operation. This supply consisted of three 200 L Avgas fuel drums:

  • an older, rusty drum that had been refilled from the station’s main fuel supply prior to the mustering operations
  • a newer, undamaged drum that was also refilled from the station’s main fuel supply prior to the mustering operations
  • a third drum, on which the manufacturer’s bung seals were in place. These seals indicated that the drum had not been opened previously.

One of the R22 pilots responded by radio that as the drum fuel hand pump was on board their helicopter, they would refuel before KJJ. The R22 pilot reported using about 60 L of fuel from the oldest of the three fuel drums. About 10 minutes later the pilot of KJJ landed to refuel using most of the remaining fuel from that drum and a smaller quantity from the newer, undamaged drum. The third drum remained unopened after the refuels, with the manufacturer’s bung seals still in place.

A stockman, who was erecting the holding yards about 2 km south-east of the drum fuel supply, reported an awareness of the pilot of KJJ landing in the area of the drum fuel supply. The stockman confirmed being sure that the pilot landed to refuel the helicopter, although there was no-one near the landing area that observed the pilot refuelling KJJ.

The stockman indicated that, after spending about 5 minutes refuelling, the pilot of KJJ took off to the south to confirm the progress of the fencing activities at the holding yards. The pilot flew past the yards and reportedly continued south to check gates ahead of the cattle herd. The stockman at the holding yard recalled that the helicopter flew past at about 150 ft above ground level. This was broadly consistent with the aircraft’s height of about 190 ft as derived from altitude data downloaded from the helicopter’s global positioning system (GPS) equipment. The stockman also reported the engine noise of the helicopter as ‘normal’ and that the helicopter appeared to have been in normal flight at that time.

The stockman reported going back to work after the helicopter passed, only to be alerted seconds later by the ‘spluttering’ of the helicopter’s engine. Looking toward KJJ’s direction of travel, the stockman observed the helicopter in a nose-down attitude, just above the tree line. At about that time, they heard the pilot broadcast over the ultra-high frequency radio that KJJ’s engine had failed. The stockman recalled that the engine noise had stopped, which was followed shortly after by the sound of the helicopter impacting terrain.

The stockmen immediately drove to the accident site, which was located about 1 km south-east of the holding yard. The R22 pilots, who also heard the radio transmission, flew to that location. The stockman reported that on arrival at the site, the injured pilot was removed from the wreckage and comforted for about 2 hours until medical attention arrived.

The pilot later succumbed to their injuries. The helicopter was destroyed during the impact sequence.

  1. Central Standard Time (CST) was Coordinated Universal Time (UTC) + 9.5 hours.
  2. ‘Draft out’ or ‘off’. To separate livestock from the herd or flock for a specific purpose (for example, branding).

Context

Personnel information

Pilot

The pilot held a Commercial Pilot (Helicopter) Licence and was endorsed on the Robinson Helicopter Company (Robinson) R44 (R44) helicopter. The pilot also held a valid Class 2 Aviation Medical Certificate.

The pilot’s total aeronautical experience at the time of the accident could not be determined as the pilot’s logbooks were incomplete. The last recorded entry was on 19 August 2013 and indicated a total of 6,592.5 flying hours, of which 214 hours were on R44 helicopters. The pilot also held a helicopter aerial stock mustering permission, sling approval and a low-level flying endorsement.

A review of the pilot’s training file identified that the pilot had satisfactorily completed a helicopter flight review on 25 March 2013. The review was conducted under Civil Aviation Regulation (CAR) 1988, Part 5 and included a Robinson R44 type endorsement. This authorised the pilot to conduct helicopter operations until the end of the flight review period on 31 March 2015.

The aerial mustering component of the pilot’s licence was valid if the pilot had completed at least 20 hours of aerial mustering in the previous 12 months. There was evidence that the pilot had likely completed at least 20 hours of aerial mustering in the previous 12 months. However, there was no evidence that the pilot conducted another flight review prior to the end of the flight review period.

Civil Aviation Safety Regulation 1998 (CASR) Part 61 was implemented on 1 September 2014, during the pilot’s flight review period. This meant that the competencies in the CASR Part 61 Manual of Standards (MOS) were required to be met if, after that time, the pilot completed a flight review for the ratings they held (seeTraining requirements).

Stockmen

A number of stockmen or station hands were employed on the cattle station to perform various tasks. This included general station work, drafting and cattle yarding. Occasionally, the stockmen worked to support aerial mustering operations by refuelling empty aviation gasoline (Avgas) fuel drums and relocating them close to the area of operations.

Prior to the accident, the pilot of VH-KJJ (KJJ) tasked one of the stockmen to reposition three full Avgas fuel drums from the station’s aircraft hangar for use in the muster. The stockman reported that two of the three drums selected from the hanger required refuelling from the station’s main Avgas fuel supply before repositioning.

The stockman that repositioned the drums reported that, although familiar with the operation of the main fuel supply bowser to refuel the drums, they were not aware of any particular refuelling process, or trained to inspect the empty stored drums for contaminants and damage. As such, the stockman loaded the three drums onto a transport truck and refuelled the two empty drums without inspection or fuel quality testing.

Aircraft information

General information

The Robinson R44 Raven 1 is a four-seat, single main and tail rotor helicopter powered by a six‑cylinder piston-engine and is equipped with skid-type landing gear. KJJ, serial number 1558, was manufactured in the United States in March 2006. First registered in Australia on 18 January 2012, KJJ had accumulated 1,009.9 flight hours total time in service at the time of the accident.

Maintenance history

The last recorded maintenance was a 100-hourly inspection at 916.4 hours total time in service on 24 February 2015 that resulted in the issue of a new maintenance release. Since that inspection, the helicopter had accumulated 93.5 hours. In that period:

  • one daily inspection was annotated on the maintenance release
  • there were no certifications for the required engine oil and filter changes in the helicopter’s logbook or maintenance release.

Meteorological information

Nearby stockmen and other pilots operating in the area reported that the temperature at the time of the accident was about 30 °C. They recalled that generally the weather conditions were fine with a light breeze. The pilots reported good flying conditions with little or no in-flight turbulence.

Recorded meteorological information at Kununnurra Airport, about 110 km to the north-west, indicated the temperature at 0900 was 28.7 °C with a relative humidity of 38 per cent. The wind was from the south-south-east at about 13 km/h and there was no recorded rain for the period.

Wreckage information

Accident site and wreckage information

The wreckage of the helicopter was located just beyond the bank of a dry creek bed in a relatively flat, sandy area that was surrounded by trees (Figure 2).

Damage to the engine, airframe and skids indicated that the helicopter impacted the ground in an upright, relatively flat attitude, with some forward movement and a high rate of descent. Calculations based on impact damage to trees located along the flight path indicated a final descent angle of about 40°.

The main rotor blades sustained penetrating damage to the blade skins, with little evidence of impact damage to their leading edges. Upward bending of the main rotor blades was also evident.

All of the critical helicopter components were accounted for at the site.

Figure 2: Accident site showing the surrounding terrain and wreckage distribution (looking south-east) 

Figure 2: Accident site showing the surrounding terrain and wreckage distribution (looking south-east)

Source: ATSB

Functionality of the critical components was established. The two forward rotor drive vee-belts were intact and located in their respective upper and lower sheaves. The two rear rotor drive vee‑belts were located in the upper rear sheaves but were displaced from the lower sheaves, probably due to impact forces.

The helicopter’s GPS was recovered for further technical examination and download at the ATSB’s technical facilities in Canberra, Australian Capital Territory. The downloaded data provided information about the operation of the helicopter on the morning of the accident including the final flight path (Figure 3).

Figure 3: KJJ’s recorded GPS flight path, showing the helicopter’s track from the drum refuelling site to the accident site 

Figure 3: KJJ’s recorded GPS flight path, showing the helicopter’s track from the drum refuelling site to the accident site

Source: Google earth, modified by the ATSB
Engine examination

Other than impact damage, no mechanical defects or anomalies were noted that would have precluded normal engine operation. Evidence at the accident site indicated that the engine was not operating at the time of impact.

Aircraft fuel system

The R44 has two interconnected fuel tanks. The main fuel tank holds 112 L total useable fuel and the auxiliary fuel tank 64 L useable fuel. Both fuel tanks were fitted with fuel tank bladders, which remained intact despite the outer aluminium skin being perforated during the accident sequence (auxiliary tank shown at Figure 4). Both fuel tanks were almost full, consistent with the recent drum refuelling.

Figure 4: Perforated auxiliary fuel tank outer aluminium skin. Note the intact rubber bladder tank (circled in yellow) 

Figure 4: Perforated auxiliary fuel tank outer aluminium skin. Note the intact rubber bladder tank (circled in yellow)

Source: ATSB

On-site samples from the helicopter’s gascolator (fuel strainer), carburettor and fuel tanks identified the presence of water and particulates (Figure 5 and Figure 6). Approximately 800 mL of water was drained from the auxiliary fuel tank and water was also siphoned from the main tank. Residual water remained in the tanks and could not be drained due to the crush damage to the fuselage. A fuel tank dip test with water detecting paste confirmed that a depth of about 3.5 cm of water remained in the lower areas of each tank.

Fuel samples that were able to be recovered from the helicopter’s fuel tanks were heavily contaminated with water and rust-like particles (Figure 6). This contamination was similar to that identified in the fuel sample taken from the older, rusted fuel drum that was first used by the pilot during the drum refuelling.

Figure 5: Gascolator (left) and carburettor (right) showing fuel contamination as indicated by the change in colour of the water detecting paste to red 

Figure 5: Gascolator (left) and carburettor (right) showing fuel contamination as indicated by the change in colour of the water detecting paste to red

Source: ATSB

Figure 6: Water and particulate matter identified in a fuel sample obtained from KJJ’s fuel tanks 

Figure 6: Water and particulate matter identified in a fuel sample obtained from KJJ’s fuel tanks

Source: ATSB

Drum fuel supply

The three 200 L drums of Avgas that were relocated from the station’s aircraft hangar were found upright in an open paddock close to the mustering operations (Figure 7). The two open drums and their contents were examined by the ATSB to eliminate them as potential sources of fuel contamination. The drum fuel hand pump was found positioned in the newer of the two open drums.

The older, rusty and dented drum contained a mixture of about 6 L total of fuel, rust and water. The inside lining of that drum was heavily rusted and was considered not suitable for aviation use.

Water and particulate contamination was also identified in a sample of fuel taken from the fuel pump filter (Figure 8).

The second, newer-type drum used by the pilot of KJJ during the refuel was about 3/4 full of Avgas and contained negligible traces of water. Any water contamination was probably introduced from the hand pump after its use in the older, heavily-contaminated drum.

Negligible traces of water were identified in the station’s main Avgas fuel supply that was used by the stockman to refill the two drums.

Figure 7: Drum fuel supply with a close-up (right) of the older, rusty and dented Avgas fuel drum. The left picture shows the drum fuel hand pump positioned in the newer of the two open drums 

Figure 7: Drum fuel supply with a close-up (right) of the older, rusty and dented Avgas fuel drum. The left picture shows the drum fuel hand pump positioned in the newer of the two open drums

Source: ATSB

Figure 8: Fuel sample from the drum fuel hand pump filter showing the change in colour of the water-detecting paste to red indicating water contamination 

Figure 8: Fuel sample from the drum fuel hand pump filter showing the change in colour of the water-detecting paste to red indicating water contamination

Source: ATSB

Operational information

Petroleum industry fuel management and handling guidance

A petroleum company in Australia reported that although they supplied aviation drum fuel to their regional distribution depots, the quality of the drum fuel could not be assured once it left the depot. This was reported to be a consequence of varying procedures surrounding the management of drum fuel once out of the control of the supplier.

General information about aviation drum fuelling was published by some petroleum companies in an effort to maintain fuel quality. The information was available online and was last updated in 2013. It provided information about drum storage, pump filter standards, drum refuelling and precautions. The publications reinforced that users of aviation drum fuel should ensure that:

  • the grade of drum and its labels are appropriate for the fuel it contains
  • the drum and drum linings are intact and of suitable quality prior to refilling
  • the drum contents are checked for water using a dipstick and water-detecting paste
  • an appropriate aviation grade filter (filter monitor preferred) and pump is used during the delivery of fuel to an aircraft
  • proper drum storage techniques are used.
Fuel filter monitors

Representatives from the petroleum industry advised that many companies involved with the supply of aviation fuel in Australia adopted the Joint Industry Group (JIG) and the Energy Institute (EI) standards. Those standards outlined the requirements for fuelling from drums, drum storage and the equipment required to ensure fuel quality during the refuelling process. This included filter standards. The relevant drum-refuelling standards at the time of the accident included JIG 4 and EI 1530 and EI 1583.

At the time of the accident, the Civil Aviation Safety Authority (CASA) was not aware of any fuel delivery filtration standard, however specific aircraft refuelling requirements were published that would provide a defence against fuel contamination (see the following section titled Aircraft refuelling requirements).

A number of filters were available for use with various fuel types. It was preferable to use filters meeting the EI standard for aviation fuel filters (EI 1583) during aircraft refuelling operations. Commonly used filter types included:

  • particulate only (particulate)
  • filter water separator
  • particulate/water absorbing (filter monitor).

Figure 9 shows a particulate filter that has a relatively low particulate removal capability of about 10 µm. This filter type was used on the day of the accident and did not meet the requirements of EI 1583 or provide a suitable level of particulate screening during the helicopter refuelling. In addition, the filter did not have the capability to remove or separate water, although the ability to detect and remove water was not a requirement to meet the EI standard.

A filter monitor-type filter is also shown in Figure 9. This filter has a much higher capability to remove particulates than the particulate filter shown. It can also absorb any water present in aviation fuels, except that it is not recommended for use with fuel containing anti-icing additives. As water and/or particulates are absorbed within the filter, differential pressure increases and reduces the flow. The reduction in the flow depends on the level of contamination in the fuel.

An operator reported trialling the effectiveness of aviation fuel filter monitors for use with drum hand pumps. The operator’s trial identified that one type of filter monitor:

  • had a non-transparent filter housing that reduced the ability to observe any contamination
  • had non-standard thread fittings, making it difficult to adapt existing hand pump equipment
  • was not a screw-on-type filter, which made changing contaminated filters difficult
  • required re-priming after the drum hand pump unit was disassembled to facilitate transportation between drum fuel supply locations.

The operator indicated that, although the practicality of this particular type of filter monitor was not ideal, the effectiveness of the filter monitor-type filter to inhibit continued pumping of water‑contaminated fuel was beneficial.

The results of the operator’s test would suggest that it would be appropriate for individual operators to assess the suitability and practicality of the available filter monitors to their operations.

Figure 9: Examples of two types of filters used during drum refuelling. Note the off-white filter monitor (at left) meets the industry standard 

Figure 9: Examples of two types of filters used during drum refuelling. Note the off-white filter monitor (at left) meets the industry standard

Source: ATSB
Aircraft refuelling requirements

CASA Civil Aviation Order (CAO) 20.9, outlined the requirements for refuelling aircraft. Specifically, when refuelling using ground fuel stock (such as drum fuel), a pilot needed to ensure:

…that the aircraft is not flown unless the aviation fuel… complies with the specification and grade required or approved for the purpose by CASA.

and that:

All ground fuel stock shall be carefully checked for the presence of undissolved water before the fuelling operation is commenced.

Note 1 This precaution is particularly important when handling fuel from drum stocks.

Note 2 Attention is drawn to the necessity of using a positive method, such as suitable water detecting paste or paper, in testing for the presence of free water since sensory perceptions of colour and smell, if used alone, can be quite misleading…

and finally that:

All fuel shall be strained or filtered for the removal of free or suspended water and other contaminating matter before entering the aircraft tanks.

CAO 20.9 also stated that when fuelling an aircraft, all fuelling equipment and the aircraft needed to be bonded[3] to allow for dissipation of static electricity that may have been present and reduce the chance of a fire. The fuelling equipment used to refuel KJJ did not have a bonding wire for that purpose. Further, there were no fire extinguishers at the refuelling area in case of fire.

Operator’s refuelling processes

The operator maintained an 11,000 L Avgas bulk storage container at the station that was refilled on an as required basis. When needed, 200 L drums of Avgas were filled from the bulk storage and transported to the area of the mustering operation.

On the day of the accident, the pilots used another operator’s drum fuel hand pump. Although the filter attached to that pump was reported changed on a regular basis, it was not the correct type for use with aviation fuel in accordance with EI standard 1583 (see the previous section titled Fuel filter monitors). In addition, the drum fuel hand pump bung fitting was not threaded into the drum (Figure 10). When secured, that fitting provided a barrier to prevent dust from entering the opened drum and located the hand pump shaft while in use. Some pilots reported that they preferred not to secure the bung fitting to allow for movement of the hand pump inlet pick-up to the higher side of the drum.[4]

Operator fuel policy, procedures and practices

The ATSB could not identify any formal operator procedures for use in aerial mustering operations. This was consistent with the conduct of the muster as a private operation, which meant that there was no regulatory requirement for the operator to have an operations manual.

It was reported, however that the pilot replaced damaged or older fuel drums with new drum fuel stock supplied by the fuel distributer. Although there was evidence that new drum fuel supply was used, some older, damaged drums were in use at the time of the accident. It could be expected that an operations manual would help standardise procedures in relation to fuel management, refuelling and low-level helicopter operations among all personnel involved in those activities.

Figure 10: Drum refueling equipment used to refuel KJJ, showing the unsecured bung fitting

Figure 10: Drum refueling equipment used to refuel KJJ, showing the unsecured bung fitting

Source: ATSB

Risk of engine failure during mustering operations

Mustering operations entail operations at low level and at varying airspeeds. Such operations increase the risk associated with loss of engine power. More specifically, under certain height and airspeed combinations, it can be difficult to perform a safe landing in the event of an engine failure.[5] At the time of KJJ’s engine failure, the helicopter was operated in an appropriate height‑velocity region. All else being equal, it might be expected that an appropriately-qualified pilot might normally conduct a successful autorotation to touchdown from that region (appendix B).

Training requirements

Helicopter pilot training standards and guidelines

Given the pilot attained their Commercial Pilot (Helicopter) Licence in 2000, the associated training would have been in accordance with the CASA Day Visual Flight Rules (VFR) Syllabus‑Helicopters. This syllabus was replaced from 1 September 2014 with the introduction of Civil Aviation Safety Regulation (CASR) Part 61, which incorporated a number of elements of the former Day VFR Syllabus-Helicopters.

A review of the Part 61 Manual of Standards (MOS) identified that for a flight review conducted after 1 September 2014, the pilot was required to demonstrate competency for the rating held. If the pilot held a low-level flight operational rating, this included:

  • dealing with emergencies
  • various helicopter handling techniques
  • handling and avoiding overpitching
  • low main rotor revolutions per minute (RPM).

The Flight Instructors Manual – Helicopter, which was published by CASA and the Civil Aviation Authority New Zealand, was a basic guide to elementary flight training. Although there was no specific guidance regarding overpitching, or low main rotor RPM avoidance and recovery in the manual, those areas were highlighted as key teaching points for instructors during autorotation, low-level and hazard-training exercises.

Civil Aviation Advisory Publication (CAAP) 5.81-1(1) titled Flight Crew LicencingFlight Reviews gave context to the value and limitations of a flight review and would have applied when the pilot last conducted their helicopter flight review. The CAAP suggested that although a flight review was required by the regulations, it was but one method that contributed to pilot proficiency and the safety of flight. Importantly, pilots were encouraged to continually identify hazards and manage the risks associated with their own aviation activities. This included regularly practicing piloting skills and actively applying threat and error management principles.

A flight review provided an opportunity for pilots to refresh their flying skills and knowledge, and to have an independent assessment of their abilities. It would be unrealistic to expect that all of a pilot’s skills and knowledge would be assessed during a flight review. However, it would be expected that a number of safety critical aspects that, if not managed appropriately, could elevate the risk of damage or injury to persons, should be assessed. These could be expected to include:

  • the management of engine failures leading to autorotation and forced landing
  • awareness and avoidance of adverse aerodynamic situations, such as rotor stall
  • management of emergencies.
  • application of threat and error management and human factors practice.

While the CAAP included useful information about flight reviews prior to the introduction of CASR Part 61, the MOS was the current document that detailed the units of competency and standards for flight reviews after 1 September 2014.

Special Federal Aviation Regulation No.73 Robinson R-22/R-44 Special Training and Experience Requirements was introduced by the United States Federal Aviation Administration in 1995. CASA has subsequently introduced many of the R-22/R-44 special training and experience requirements into the CASR Part 61 MOS.

The United States Special Federal Aviation Regulation that was current at the time of the accident required specific awareness training, aeronautical experience, endorsements, and flight reviews for pilots operating Robinson helicopters. Specifically, this training included:

  • enhanced training in autorotation procedures
  • engine rotor RPM control without the use of the governor
  • low rotor RPM recognition and recovery
  • the effects of low G[6] manoeuvres and proper recovery procedures.
Low-level flying

Prior to the introduction of CASR Part 61, Civil Aviation Regulation (CAR) 5 required pilots holding a flight crew licence to undertake a biennial flight review for each category of aircraft on their licence. Guidance as to what constituted an acceptable flight review was contained in CAAP 5.81 1 (1), which emphasised the importance of flight safety through the application of the standards stipulated in the Day VFR Syllabus. There was no mandated requirement for pilots to demonstrate low-level flying or mustering in a flight review under the CAR 5 regulations.

With the introduction of CASR Part 61, pilots were required to conduct a flight review for low-level flying every 12 months. However, CASA subsequently changed this requirement under Regulation 61.1060, instrument number CASA EX92/15 on 25 May 2015. This instrument increased the low‑level flight review requirement to 24 months.

Helicopter operation

Autorotation

In the case of an engine failure, a helicopter pilot is required to immediately enter autorotation. This is achieved by lowering the collective lever[7] to reduce the drag generated by the main rotor blades and establishing the appropriate speed for the autorotative descent. Robinson stated that if autorotation is not entered immediately, the rotor RPM rapidly decays, the main rotor system stalls and the results are likely fatal.

As the helicopter descends, there is an upward flow of air through the main rotor system. This upward flow provides an autorotative force to create rotor thrust that, if properly managed, maintains rotor RPM throughout the descent and provides for a steady rate of descent. Amongst other factors, the rate of descent in autorotation is affected by the forward airspeed of the helicopter. If the airspeed is zero, the rate of descent will be high. The rate of descent reduces with increasing airspeed until reaching the minimum rate of descent airspeed. The rate of descent again increases with increased airspeed beyond the minimum rate of descent speed. If managed correctly, the pilot can maintain the rotor RPM within limits by manipulating the collective lever.

In general, autorotative descents are carried out at an optimum forward airspeed that approximates the minimum rate of descent airspeed. When landing from an autorotation:

  • Initially the forward airspeed is reduced by raising the nose of the helicopter (flaring) with aft cyclic.[8] This has the added benefit of reducing the ground speed and rate of descent and increasing (or recovering) the main rotor RPM.
  • At an appropriate height above the ground, the helicopter is established in the landing attitude with cyclic.
  • As the aircraft settles towards the ground, the pilot raises the collective lever to ‘cushion’ the aircraft onto the ground. Critically, this action decays the main rotor RPM and therefore rotational energy stored in the main rotor.

The final stages of an autorotation rely heavily on pilot judgement. In addition to the height and speed on entry into autorotation, factors such as uneven and/or wooded terrain, ploughed fields, the ambient conditions and the availability of suitable landing areas can all combine to affect the likelihood of a successful autorotation and touchdown.

If the pilot does not respond quickly and appropriately to a low rotor RPM situation, the main rotor RPM decreases further and the helicopter’s rate of descent increases. If the collective is maintained or raised further in an effort to decrease the rate of descent, the rotor RPM reduces to a point where the main rotor blades cone up.[9] The result is a loss of lift, an increased rate of descent and a further reduction in rotor RPM. The situation can rapidly deteriorate into a vicious cycle that culminates in the rotor blades effectively stalling and losing all lift. Once the blades are aerodynamically stalled, in-flight recovery is almost impossible.

The R44 helicopter is equipped with a low rotor RPM warning horn and caution light, which activates at 97 per cent main rotor RPM. The R44 pilot’s operating handbook (POH)[10] emergency procedure in response to the activation of the low RPM horn and associated caution light stated:

A horn and an illuminated caution light indicate that rotor RPM may be below safe limits. To restore RPM, immediately roll throttle on, lower collective and, in forward flight, apply aft cyclic. The horn and caution light are disabled when collective is fully down.

That procedure decreases main rotor blade pitch and reduces blade drag in an effort to increase rotor RPM. This may be counter instinctive to the pilot of a helicopter at low altitude.

Robinson safety notices SN-10 FATAL ACCIDENTS CAUSED BY LOW ROTOR STALL and SN‑24 LOW RPM ROTOR STALL CAN BE FATAL discussed blade stall and the associated risks and recovery actions and were available for inclusion in owner/operators’ R44 POHs. These safety notices are reproduced at appendix A.

Hot refuelling

Although pilots were permitted to hot refuel[11] helicopters in accordance with Civil Aviation Amendment order (No. R11) 2004, the operator and pilot had a number of responsibilities to ensure the safety of operations. Schedule 1, Substitution of section 20.10 of the CAOs included that, before authorising the hot refuelling of a helicopter, the operator should satisfy themselves that it can be done safely by considering the:

  • the configuration of the helicopter and it’s engine or engines; and
  • the location of the components of the helicopter’s fuel system; and
  • the refuelling system or systems to be used and it’s or their components; and
  • the helicopter’s flight manual [POH].

Additionally, the operator was required to include appropriate procedures in their operations manual. As the operator was conducting the mustering operations under the Private Category, there was no requirement for an operations manual.

In relation to fuel testing, the regulations stipulated that the operator should ensure that the pilot in command inspected and tested the helicopter’s fuel system for the presence of water on completion of each hot refuelling. This was because there was no fuel quality audit program or system for monitoring the quality of fuel used by the helicopter.

Additional pilot responsibilities during hot refuelling included that, unless they were exempted under CAO 95.7, the pilot must remain at the controls of the helicopter while refuelling was carried out. Under that order, exiting an operating R44 helicopter to conduct refuelling was not a valid reason to leave the flight controls.

Safety notice SN-17 NEVER EXIT HELICOPTER WITH ENGINE RUNNING was included in the R44 POH and highlighted that a number of accidents have occurred when pilots momentarily left an operating helicopter (appendix A). The notice advised that, unmonitored, the collective lever could creep up, increasing pitch and throttle and allowing the helicopter to lift‑off without pilot control.

To prevent inadvertent upward movement of the collective lever, it was reported by a number of helicopter pilots that an elastic strap was commonly positioned over the lever. There was evidence that the pilot of KJJ may have used this technique while not at the controls of the helicopter during ground operations (Figure 11). However, no approval for this method of securing the flight controls was found in the helicopter’s maintenance documentation. In any case, the POH stipulated that pilots must not leave flight controls unattended while the helicopter is operating. Civil Aviation Regulation 138 Pilot to comply with requirements etc of aircraft’s flight manual etc required Australian pilots to comply with that requirement.

CASA flight safety article titled Don’t walk away and an ATSB safety investigation highlighted the risks associated with leaving flight controls unattended while the helicopter was still operating. They can be viewed at:

Figure 11: Elastic strap found positioned near the collective (such as reported used by some pilots to secure the collective lever)

Figure 11: Elastic strap found positioned near the collective (such as reported used by some pilots to secure the collective lever)

Source: ATSB

Related fuel contamination occurrences

A search of the ATSB’s occurrence database revealed that in the 10-year period from 2004 there was an average of about three reported fuel contamination-related occurrences per year. A number of the occurrences identified issues with water bypassing the aircraft’s fuel tank cap seals after periods of rain or entering the fuel system during the refuelling process. In many cases, the effects of water contamination remained unnoticed until the aircraft experienced an in‑flight engine power loss requiring the pilot to conduct a forced landing or return to an aerodrome.

The following occurrence investigations that relate to fuel contamination are available from the ATSB website at www.atsb.gov.au:

Total power loss - Cessna 152, registered VH-HCE (AO-2011-118)

At an altitude of approximately 200 ft above ground level, the instructor heard the engine noise reducing and observed the engine RPM decreasing. The instructor immediately assumed control, lowered the nose of the aircraft to maintain airspeed and performed a successful emergency landing.

Water contamination was identified in the post-accident fuel samples taken from the aircraft’s fuel filter and the right fuel tank. Surface rust on the right tank fuel cap receptacle indicated that water had most likely entered the system through that point during the heavy rainfall in the previous days. During that period, the aircraft was parked in the open. The water contamination was not identified during the pre-flight fuel drain check that was conducted by the instructor and witnessed by the student.

Total power loss - Robinson R22 helicopter, registered VH-FDL (AO-2010-107)

On 13 December 2010, at about 1500 Eastern Standard Time, a Robinson R22 Alpha helicopter, registered VH-FDL, departed the Georgetown aeroplane landing area, Queensland with one pilot and one passenger on board.

The pilot reported that, when 9 km to the north of Georgetown on descent from 1,000 ft above ground level and passing through 150 ft, engine power was applied before the engine spluttered twice. This was immediately followed by a decrease in engine RPM and the low rotor RPM warning horn sounding. The engine subsequently failed. The pilot reported that carburettor heat was not applied during the descent and the carburettor temperature was above the yellow arc.

The pilot regained control of the rotor RPM and conducted a forced landing. During the landing, the helicopter’s skids struck a tree. The left skid then contacted the ground and the helicopter cartwheeled. The pilot was not injured, however the passenger sustained serious injuries.

The subsequent examination of the helicopter’s engine and fuel system did not identify any anomalies. It was possible that the small amount of water that was found in the carburettor contributed to the reported engine failure.

Collision with terrain, registered VH-KZF, on 14 September 2010 (AO-2010-069)

The pilot commenced the take-off from an elevated, 700 m long gravel airstrip on the eleventh of 12 flights. During the take-off, the aircraft did not achieve the required take-off performance. In an attempt to become airborne before the end of the useable runway surface, the pilot elected to dump some of the chemical load and continued the take-off. The aircraft subsequently collided with terrain a short distance from the departure end of the airstrip.

The loader reported that the aircraft was refuelled at the airstrip from drums that were previously used to store aviation oil. The drums themselves were refuelled on the morning of the accident from a Geraldton, Western Australia fuel facility. Fuel sample tests of the drum stock fuel after the accident indicated higher-than-normal gum levels.

The pilot was reported to have refuelled the aircraft’s left wing tank from those drums three times prior to the accident. The investigation concluded that the quality of the fuel for the flight was not a factor.

It could not be determined why the fuel samples from the load truck’s fuel hose returned higher‑than‑recommended gum levels. However, the use by the pilot of fuel that was stored in disused aviation oil drums increased the risk that the fuel would not be suitable for the intended application.

Departure from controlled flight and collision with terrain involving Ayres Corporation S2R Thrush, VH-JAY, 17 km south-east of Hyden, Western Australia on 18 October 2013 (AO-2013-183)

The ATSB found that the aircraft departed controlled flight from which the pilot was unable to recover, leading to a collision with terrain. Based on the available evidence, it was not possible to determine the reasons for the loss of control.

The ATSB identified two aspects of the aircraft’s operation with the potential to affect safety. These were the use of an unapproved fuel mix and operation of the aircraft above its published maximum take-off weight.

Other research information

Although not captured in the ATSB’s occurrence database, it was reported by a number of pilots using aviation drum fuel supply in Australia that they often identified water contamination in their fuel drums. The water contamination was normally identified using water detecting paste prior to refuelling, or by visually inspecting the hand pump filter bowl during the refuelling process (Figure 12). It was also reported that pilots would normally inspect fuel samples taken from the aircraft’s fuel tanks after refuelling to confirm there was no contamination.

Figure 12: Unrelated example of a visual indication of water contamination in a fuel filter bowl

Figure 12: Unrelated example of a visual indication of water contamination in a fuel filter bowl

Source: Operator
  1. ‘Bonding’ the aircraft and fuelling equipment ensures that both have the same electrical potential.
  2. During refuelling, the practice of keeping the fuel drum tilted so that the large bunghole is on the high side ensures the hand pump inlet pick-up is away from potential contamination on the low side of the drum.
  3. The Robinson R44 Pilot’s Operating Handbook contained a Height-Velocity diagram. This diagram highlighted ‘avoid’ areas, such as operations at high airspeed-low altitude or at higher altitude-low airspeed combinations.
  4. G load: the nominal value for acceleration. In flight, g load represents the combined effects of flight manoeuvring loads and turbulence and can have a positive or negative value.
  5. Collective lever: 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.
  6. 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.
  7. Coning of the main rotor blades: the upwards movement of the main rotor blades while they are rotating. This is usually in response to an increase in aerodynamic force as a result of a control input from the pilot. It is more pronounced at high weights and/or low main rotor speed.
  8. The Robinson R44 1 PILOT’S OPERATING HANDBOOK AND FAA APPROVED ROTORCRAFT FLIGHT MANUAL is also the helicopter’s flight manual. Robinson prefer to term this publication the Pilot’s Operating Handbook. This preference is reflected in this investigation report.
  9. Hot refuelling means the refuelling of a helicopter with its engine or engines running

Safety analysis

The pilot of VH-KJJ (KJJ) experienced a loss of engine power after a significant amount of water in the helicopter’s fuel system interrupted the flow of fuel to the engine. The engine lost power while the helicopter was in low-level cruise flight, a short time after refuelling from a local drum fuel supply.

In response to the loss of engine power, the pilot entered autorotation and attempted a forced landing in a largely timbered environment. The impact damage to the helicopter from the forced landing was consistent with a high rate of descent at touchdown, most likely due to low main rotor revolutions per minute (RPM) in the latter stages of the autorotation.

This analysis will examine the circumstances surrounding the fuel contamination and the autorotation in response to the loss of engine power. It will also highlight a number of important operational safety considerations in respect of fuel-handling practices and low-level helicopter operations.

Response to the engine failure

Entry into and conduct of the autorotation

On-site evidence and data recovered from the helicopter’s global positioning system equipment provided an understanding of the helicopter’s operation on the day of the accident and, in particular, during the final stages of flight. This did not include the degree or sequence of control inputs by the pilot after the loss of engine power. However, it was evident that the pilot entered autorotation, established an initial speed of about 70 kt and completed a slight turn to the south‑east. This was consistent with a turn towards the ultimate touchdown point. In response to a loss of engine power, helicopter pilots enter autorotation and normally turn into wind and select the most suitable landing area before planning their descent.

Evidence of coning of the main rotor blades was consistent with decreased main rotor energy. Although the reason for this loss of energy could not be determined, any loss of energy would have decreased the pilot’s ability to arrest the helicopter’s rate of descent. In addition, the wooded terrain and limited suitable landing areas would have increased the difficulty faced by the pilot.

Ultimately, for reasons that could not be established, but consistent with the difficulties faced by the pilot, the pilot was unable to satisfactorily reduce the rate of descent before impacting the ground. The heavier-than-normal forces experienced during the touchdown influenced the likelihood of survival from the autorotation.

Expectancy and training currency

The ATSB considered a range of factors that may have influenced the pilot’s ability to conduct a successful autorotation touchdown from the low-level cruise height. These included expectancy and skill decay.

Pilots expect certain abnormal events during flight review and proficiency checks, and they are generally well prepared to respond to those scenarios. Research has shown that performance is slower, less effective and more variable when an abnormal event is not expected (Casner and others 2013, Hendrickson and others 2006).

Engine failures and power loss from fuel contamination are rare events and therefore they are generally not expected. In this case, the pilot had probably refuelled on many occasions from drum fuel supply without experiencing adverse in-flight effects from fuel contamination. Further, the pilot was aware that another helicopter had just refuelled using the same fuel supply without any reported engine-related difficulties. This likely reinforced the pilot’s expectation that there would be no issues related to fuel contamination.

Low expectancy has been associated with many previous occurrences related to in-flight management of abnormal events. To help overcome these problems, pilots conduct regular flight reviews and proficiency checks to ensure they have, or can regain the operational skills to respond to those events.

In this case, the pilot had not conducted a flight review since March 2013. A flight review would likely have provided an opportunity for the pilot to practice low-level autorotation in response to simulated loss of engine power, and react to other risks associated with low-level mustering operations. In consequence of this lack of recency, the pilot’s skill managing in-flight emergencies could be expected to have deteriorated, influencing their ability to execute and successfully recover from an autorotation.

Operators should not underestimate the value of regular emergency procedure training, flight reviews and the continual assessment of operational threats and risks. Some emergencies, like a loss of engine power at low level, require prompt and appropriate action. Importantly, recurrent flight training allows mustering pilots to review their low-level operations to increase the available options in the event of an in-flight emergency.

Fuel handling practices

Proper management of ground fuel supplies and assurance of fuel quality throughout the refuelling process should not be understated. There have been many aviation occurrences where pilots have experienced in-flight difficulties relating to fuel starvation or exhaustion. This includes instances of fuel starvation from contaminated fuel.

While there was industry guidance available to operators about acceptable fuel standards and practices to help prevent fuel contamination, it was evident that the application of, and adherence to those standards varied across the aviation industry. In this case, the mustering operation was conducted as a private operation. Therefore, it did not require an operations manual that would have outlined the drum-fuelling procedures and necessary equipment. Although some newer-type drums were being used on the day of the accident, the operator’s reported procedure for renewing fuel drums did not include isolating damaged fuel drums from the main drum supply. This allowed the re-use of the damaged drum after refilling.

It was probable that most of the contamination was introduced into KJJ’s fuel system while refuelling from the older, rusted and damaged drum. This was consistent with the negligible amounts of water, rust or particulates identified in the operator’s other fuel supplies. The water and rust particulates in the old, rusted and dented drum may have resulted from its storage unused for a period in a hot and humid environment.

Previous ATSB aviation safety investigations have highlighted risks associated with the improper use of drums for storage of aviation fuel, and the absence of recommended aviation filters during refuelling operations. Although the regulations required pilots and operators to have a suitable means of testing fuel prior to and after filling an aircraft’s fuel tanks, it was evident that no robust procedure was in place for testing fuel at the time of the accident.

A number of issues were identified with the refuelling procedures and use of drum fuel that, if addressed, could have prevented, or provided an opportunity to detect water and particulate contamination in the drum stock. The ability to detect contamination in fuel using visual inspection and smell can vary. As a result, it is recommended that pilots check for the presence of water using a positive test method, such as water-detecting paste. In this case, visual detection of water may have been difficult because of the amber colour of the fuel filter bowl, turbid colour of the contamination and quantity of water in the fuel. The use of water‑detecting paste would have identified the contamination prior to refuelling the helicopter, indicating that the fuel was unsuitable for aviation use. It was therefore likely that during the last refuel, the pilot was unable to identify any visible water or particulates transferred into the helicopter’s fuel from the drum fuel stock. Alternately, the pilot did not test the fuel from the helicopter’s fuel tanks and gascolator after refuelling.

Pilots from the other helicopters operating on the same muster reported no contamination when their helicopters’ fuel tanks were examined after the accident. This was most likely due to their only using half of the older, damaged drum, along with their method of tilting the drum fuel pump toward the higher side of the drum. This meant that any contaminants were, if present, drained away from the fuel pump inlet. The pilot of KJJ used almost all of the remaining fuel in the older, rusted drum. This would require the pilot to position the fuel pump inlet at the base of the drum, near the water and particulate contamination.

The addition of a filter monitor would have provided another line of defence before the fuel entered KJJ’s fuel tanks. Used correctly, a filter monitor meeting the petroleum industry standard would have inhibited the pilot from pumping the contaminated fuel once water contacted the filter membrane, as the pilot would feel increased pressure or resistance. The associated difficulty pumping fuel through the filter would have alerted the pilot of the potential water contamination. It could be expected that this would most likely have prompted testing and subsequent removal of any contamination from the helicopter’s fuel tanks.

The use of a filter that met the petroleum industry standard would have reduced the size of particulate able to pass through the filter to as low as 1 µm. This compares with the larger 10 µm particulate size filtered by the filter that was used on the day of the accident. This would have minimised the amount of particulate identified in KJJ’s fuel tank, carburettor and gascolator.

The use of appropriate fuel pump filters (filter monitors) and checks of the helicopter’s fuel system would have increased the likelihood that the pilot would detect the contaminated fuel. The importance of operators having appropriate fuel handling and storage procedures to ensure fuel quality is also highlighted.

Hot refuelling

The timing of the refuel that was derived from the recorded global positioning system data suggested that the pilot of KJJ did not shutdown the helicopter prior to refuelling (hot refuelling). The time normally required for a refuel, compared to the time spent on the ground that day, was insufficient for completion of the:

  • helicopter shutdown and start-up procedures
  • the actual refuelling process.

While the R44 pilot’s operating handbook did not exclude hot refuelling, there were regulations that stipulated the responsibilities of operators and pilots during such refuelling processes. Of note, the operator was required to have an operations manual that set out the operational circumstances and procedures to ensure the safe refuelling of aircraft. As the helicopter was being operated privately that day, and therefore there was no operations manual, hot refuelling should not have been conducted. In addition, the R44 pilot’s operating handbook required the pilot to remain at the controls while the helicopter was operating.

Unmonitored helicopter flight controls with the rotors running, such as during hot refuelling, increases the risk of the helicopter unintentionally becoming airborne and subsequent injury to bystanders.

Findings

From the evidence available, the following findings are made with respect to the collision with terrain involving Robinson Helicopter Company R44, registered VH-KJJ, which occurred 153 km south-west of Timber Creek, Northern Territory on 14 June 2015. These findings should not be read as apportioning blame or liability to any particular organisation or individual.

Contributing factors

  • Following drum refuelling, fuel from the helicopter's fuel tanks and gascolator were likely not tested for the presence of contamination. This was a missed opportunity for the pilot to detect water and particulates introduced from the drum fuel supply.
  • The helicopter’s fuel system was contaminated with water and particulates during the drum refuelling, preventing a combustible fuel supply to the helicopter’s engine during flight and causing it to stop shortly after take-off.
  • During a low-level autorotation and forced landing, and for reasons that could not be determined, the pilot was unable to satisfactorily reduce the rate of descent before impacting the ground. The heavier-than-normal forces experienced during the touchdown influenced the likelihood of survival from the autorotation.

Other factors that increased risk

  • The operator did not have an effective procedure for testing and managing drum fuel supply, increasing the risk of fuel contamination from that supply.
  • The operator did not use a filter monitor that was recommended by the petroleum industry and was suitable for aviation use. Such a filter would have minimised the risk of water contamination during the drum refuelling.
  • The pilot had not completed the stipulated helicopter flight review for low-level helicopter operations. This likely influenced the pilot’s familiarity and proficiency with managing time‑critical emergencies that occur from a low altitude.
  • The unmonitored flight controls during the hot refuelling increased the risk of the helicopter unintentionally becoming airborne and injuring bystanders.

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • the Civil Aviation Safety Authority
  • a number of helicopter training providers
  • a number of other helicopter operators
  • a petroleum company that supplied aviation drum fuel in Australia
  • a number of property station hands.

References

Casner, SM Geven, RW & Williams, RT 2013, ‘The effectiveness of airline pilot training for abnormal events’, Human Factors: The Journal of the Human Factors and Ergonomics Society, vol. 55, pp.477-485.

Hendrickson, SM Goldsmith, TE & Johnson, PJ 2006, ‘Retention of airline pilots’ knowledge and skill’, Proceedings of the Human Factors and Ergonomics Society 50th Annual Meeting, pp.1973‑1976.

Submissions

Under Part 4, Division 2 (Investigation Reports), Section 26 of the Transport Safety Investigation Act 2003 (the Act), the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. Section 26 (1) (a) of the Act 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 helicopter operators, the Civil Aviation Safety Authority and a petroleum company that supplied aviation drum fuel in Australia.

Submissions were received from the helicopter operators and a petroleum company that supplied aviation drum fuel in Australia. The submissions were reviewed and where considered appropriate, the text of the report was amended accordingly.

Appendices

Appendix A – Robinson Helicopter Company Safety Notices

Appendix A – Robinson Helicopter Company Safety Notices SN-10

Appendix A – Robinson Helicopter Company Safety Notices SN-15

Appendix A – Robinson Helicopter Company Safety Notices SN-17

Appendix A – Robinson Helicopter Company Safety Notices SN-24

Appendix A – Robinson Helicopter Company Safety Notices SN-24 cont.

Appendix B – R44 Height – Velocity Diagram

Appendix B – R44 Height – Velocity Diagram

Purpose of safety investigations & publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2016

image_5.png

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 AO-2015-062
Occurrence date 14/06/2015
Location 154 km south-west of Timber Creek
State Northern Territory
Report release date 17/11/2016
Report status Final
Investigation level Defined
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Robinson Helicopter Co
Model R44
Registration VH-KJJ
Serial number 1558
Sector Helicopter
Operation type Private
Departure point Waterloo Station, NT
Damage Destroyed

Loss of separation involving a Cessna 441, VH-JLT and a Raytheon B200, VH-ZCJ, near Darwin Airport, Northern Territory, on 10 June 2015

Final report

What happened

On 10 June 2015, the pilot of a Cessna 441 aircraft, registered VH-JLT (JLT), conducted pre-flight preparations for a charter flight from Darwin to Oenpelli, Northern Territory with 6 passengers. The pilot planned to track direct to Oenpelli, but on requesting an airways clearance, was advised by the clearance delivery controller that there was a requirement to plan via the VANDI ONE standard instrument departure (SID) (Figure 1). The pilot then reviewed the SID chart and noted the left turn on departure and the height limit of 6,000 ft at waypoint BAXIB. The pilot wrote ‘6,000’ on the navigation log. As part of the airways clearance issued to JLT, the pilot was initially issued a clearance to climb to 3,000 ft. The pilot entered ‘3000’ into the aircraft’s altitude alerter.

Figure 1: Extract of VANDI ONE SID

Figure 1: Extract of VANDI ONE SID

Source: Airservices Australia – annotated by the ATSB

At about 0856 Central Standard Time (CST), a Raytheon B200 aircraft, registered VH-ZCJ (ZCJ), operating an aeromedical flight with a pilot, a flight nurse and four passengers on board, was approaching Darwin from Elcho Island, Northern Territory, on the GATOR THREE A standard arrival route (STAR) (Figure 2). The pilot had been advised to expect track shortening and a visual approach to runway 11. At 0856:16, the Darwin approach controller cleared ZCJ to descend to 7,000 ft.[1]

At about 0859, JLT took off. The pilot conducted a left turn as required by the SID, and the Tower controller directed the pilot to contact Approach. At 0859:52, the pilot of JLT contacted the approach controller and advised that they were conducting a VANDI SID, and passing 1,000 ft on climb to 3,000 ft. About 20 seconds later, the pilot of ZCJ reported that they were visual and were then passing about 8,400 ft on descent.

At 0900:44, the approach controller cleared JLT to climb to flight level (FL) 130.[2] The pilot then selected 13,000 in the altitude alerter. The controller did not cancel any requirements, hence JLT was still required to be at or below 6,000 ft at waypoint BAXIB in accordance with the SID. Shortly after that communication, the pilot of JLT inadvertently selected Brisbane Centre frequency (on COM1), and was no longer able to hear Darwin Approach frequency.

At 0901:00, the approach controller cleared ZCJ, which was then passing about 7,700 ft, to descend to 3,000 ft. In accordance with the STAR, that could only be complied with after passing waypoint VIKUV at or above the 7,000 ft height restriction published for that point on the STAR.

Figure 2: Extract of GATOR THREE A STAR

rId22 Picture 5.PNG

Source: Airservices Australia – annotated by the ATSB

About 13 seconds later, the approach controller observed ZCJ approaching 7,000 ft. The controller asked the pilot of ZCJ to confirm they were aware that the level restriction at VIKUV still applied, and to expect track shortening after VIKUV. The pilot responded ‘roger’. The radar display indicated the aircraft then descended below 7,000 ft to 6,800 ft, which was still within the specified tolerances (+/- 200 ft) of the level restriction. At 0901:41, the radar display showed the ZCJ at 6,700 ft, and the controller asked the pilot to confirm they were maintaining 7,000 ft, and the pilot responded ‘affirm’.[3] JLT was then about 11 NM away, and there was still about 3,100 ft vertical separation between the aircraft at that time.

At about 0902, ZCJ was approaching waypoint BITES at 7,000 ft, JLT was at 5,000 ft and the aircraft were about 6 NM apart (Figure 3). The controller then issued JLT as traffic to the pilot of ZCJ, and advised that JLT had been assigned FL130 and had a 6,000 ft requirement at BAXIB. The pilot of ZCJ acknowledged the traffic and could see it on the aircraft’s traffic collision avoidance system (TCAS). The pilot of JLT did not hear that communication as they were not listening on the approach frequency at that time.

At 0902:41, as the two aircraft converged, an Australian Defence Air Traffic System (ADATS) predicted conflict alert (PCA) activated on the controller’s situational display (Figure 4). The controller advised the supervisor, as required following a PCA activation, that vertical navigation ‘strategic’ separation was in place (see right). JLT was then at 6,100 ft, above the level restriction of 6,000 ft, and ZCJ at 7,000 ft with less than 2 NM between the aircraft. At 0903:07, 1.6 NM and 800 ft existed between the aircraft, and the pilot of ZCJ reported that they had JLT in sight. The approach controller confirmed that the pilot of ZCJ was able to maintain separation with JLT. The pilot of ZCJ then received a TCAS ‘TRAFFIC TRAFFIC’ alert and disconnected the autopilot in anticipation of taking avoiding action. The approach controller quickly attempted to contact JLT, advising that ZCJ was maintaining separation with them and to confirm they were complying with the level restriction, but did not receive a reply; JLT continued to climb. The controller then advised the pilot of ZCJ that the aircraft had climbed through the 6,000 ft level restriction and issued a requirement to the pilot of ZCJ to maintain separation with that aircraft. By the time the controller had completed that transmission, the two aircraft had passed. The approach controller then cancelled ZCJ’s level restrictions, and cleared the aircraft to descend to 4,000 ft. ZCJ continued to descend in accordance with the STAR route and the pilot did not take any avoiding action.

At 0903:36, the approach controller again called JLT and received no response. At 0903:55, the approach controller received an ADATS conflict alert (CA), with the closest proximity according to the radar reducing to 400 ft vertically and 0.3 NM between the two aircraft. The pilot of ZCJ estimated the proximity between the aircraft to be about 200 ft vertically and 100-200 m horizontally. The controller stated that ‘surveillance passing’ separation standard was in place (see right).

The pilot of JLT sighted ZCJ slightly above, to their left, and closer than normal. The pilot realised the radio was selected to Brisbane Centre frequency and switched it to the Darwin Approach frequency. After two more unsuccessful attempts to contact JLT on the Darwin frequency, Brisbane Centre advised the controller that JLT was with them. The pilot of JLT, then back on Darwin Approach frequency, asked the approach controller whether they had been trying to contact them. The approach controller advised the pilot that the aircraft had climbed through a level restriction, and the pilot asked the controller to confirm they had been cleared to FL130. The controller said yes, but in accordance with the SID. The controller then handed JLT off to Brisbane Centre. ZCJ landed on runway 11 without further incident.

At 0903:36, the approach controller again called JLT and received no response. At 0903:55, the approach controller received an ADATS conflict alert (CA), with the closest proximity according to the radar reducing to 400 ft vertically and 0.3 NM between the two aircraft. The pilot of ZCJ estimated the proximity between the aircraft to be about 200 ft vertically and 100-200 m horizontally. The controller stated that ‘surveillance passing’ separation standard was in place. 

__________________

Separation Standards
According to the Manual of Air Traffic Services (MATS), separation is the concept of ensuring aircraft maintain a prescribed minimum from another aircraft (or object), whilst meeting the associated conditions, and requirements of the standard. A separation standard is a prescribed means to ensure separation between aircraft using longitudinal, lateral, vertical and visual standards.
__________________

Strategic Separation
Strategic separation is achieved by designing flight paths that minimise conflictions between arriving and departing aircraft. Tactical separation is achieved by changing an aircraft’s speed, altitude or direction, including requiring aircraft to proceed at specific times to preserve separation.
__________________

Surveillance Passing
The ‘surveillance passing’ standard applies to aircraft on reciprocal tracks (within 45° of each other’s track), when aircraft are observed by an air traffic surveillance system to have definitely passed and their position symbols are not touching.
__________________

The pilot of JLT sighted ZCJ slightly above, to their left, and closer than normal. The pilot realised the radio was selected to Brisbane Centre frequency and switched it to the Darwin Approach frequency. After two more unsuccessful attempts to contact JLT on the Darwin frequency, Brisbane Centre advised the controller that JLT was with them. The pilot of JLT, then back on Darwin Approach frequency, asked the approach controller whether they had been trying to contact them. The approach controller advised the pilot that the aircraft had climbed through a level restriction, and the pilot asked the controller to confirm they had been cleared to FL130. The controller said yes, but in accordance with the SID. The controller then handed JLT off to Brisbane Centre. ZCJ landed on runway 11 without further incident.

Figure 3: Situation display showing JLT at 5,000 ft and ZCJ at 7,000 ft

Figure 3: Situation display showing JLT at 5,000 ft and ZCJ at 7,000 ft

Source: Defence air traffic control – annotated by the ATSB

Figure 4: Situation display showing the predicted conflict alert, with JLT at 6,100 ft and ZCJ at 7,000 ft

rId24 Picture 5.PNG

Source: Defence air traffic control – annotated by the ATSB

New traffic management plan (TMP) for Darwin Airport

A new traffic management plan (TMP) for Darwin Airport came into effect on 28 May 2015. This was the result of about two years of design and development, and included consultation with industry. Traffic management planning regulates the flight profiles of arriving and departing aircraft to improve the traffic flow. The new procedures consisted of a number of vertical navigation requirements, with intermediate level restrictions. Several notices to airmen (NOTAMs) were promulgated by Airservices Australia advising of the new TMP, commencing in December 2014. Local operators were asked to provide feedback on the plan.

An Airservices Air Traffic Management (ATM) specialist reported that the new TMP was based on fulfilling a requirement from the Civil Aviation Safety Authority (CASA) to reduce controller workload. Removing the need to assign levels to each aircraft, also reduces the number of radio transmissions. The new procedures meant that the controllers would not be required to issue as much tactical separation, as the new procedures provided strategic separation. The TMP was designed to be of most benefit during busy periods, when Darwin can have up to 45 aircraft on frequency at the same time, including military jet aircraft. Controllers would then have more time to process and communicate with aircraft that are not captured in the TMP.

Since the implementation of the new plan, there had been a significant number of non-compliance events with the vertical navigation requirements. Darwin was one of the few airports in Australia with vertical navigation requirements on SIDs and STARs, and has more of them than any other airport in Australia.

Controller comments

The approach controller provided the following comments:

  • The duty runway was runway 11.
  • In accordance with the TMP, ZCJ was inbound on the GATOR THREE STAR, and JLT outbound on the VANDI ONE SID. With the vertical requirement for that STAR and SID, there was a 1,000 ft buffer between the planned routes of the two aircraft.
  • All communications and clearances were issued in accordance with the current Airservices Australia Aeronautical Information Package (AIP). Phraseology published in the AIP refers to cancellation of STAR level restrictions but not SID level restrictions. Consequently, the controllers had been advised to cancel the waypoint level restriction on a SID using the phrase, for example, ‘cancel BAXIB level restriction’.
  • The new TMP included changes to the departure and approach procedures design and charts, radiotelephony, and was a significant change to the airspace and their mode of operations. The controllers had been directed to issue full climb and descent clearances, which was consistent with Airservices operations in other locations where intermediate level restrictions existed.
  • The controller did not, and was not required to issue a safety alert to ZCJ, and believed that to do so would increase risk. The controller did not issue a safety alert to JLT and assigned separation responsibility to the pilot of ZCJ. The pilot of ZCJ had JLT in sight and if the controller had issued a heading or climb instruction to the pilot of ZCJ, the pilot may have looked inside at the instruments to follow the instruction, instead of keeping JLT in sight.
  • The controller’s initial response was to attempt to communicate with the pilot of JLT and confirm they were maintaining 6,000 ft, but the pilot did not respond. The controller wanted to issue a safety alert to the pilot of JLT as they had not been issued ZCJ as traffic. However, on receiving no response from the pilot of JLT, the controller immediately assigned safety recovery to ZCJ, and then confirmed the aircraft had passed each other.
  • The controller was also the senior training officer in Darwin, and because of the significant number of VNAV restrictions in the new TMP, the controller created maps and diagrams, and clearly depicted the restrictions on SIDs and STARs, and placed them on the console as a situational awareness tool for the controllers.
  • Prior to a controller operating under the new TMP, they had completed two simulator sessions. The scenarios included common and predicted conflictions and multiple aircraft not tracking via SIDs and STARs, and aircraft not in compliance with the TMP requirements.

Immediate actions

Following the incident, the pilots of both aircraft participated in a briefing with the controllers. They viewed the radar tapes and discussed the TMP. The aim was to educate the pilots, as local operators, and discuss the TMP with the aim to prevent further incidents from occurring.

The operator of JLT attended this briefing. They were surprised that the controllers had assumed the Cessna 441 was equipped with a traffic collision avoidance system (TCAS) and a flight management system (FMS). It was not fitted with either. The operator also stated that the same applies to most of the general aviation aircraft operating in and out of Darwin Airport.

Pilot comments

Pilot of VH-JLT

The pilot of JLT provided the following comments:

  • The pilot should have reviewed the en route section of the Jeppesen for the planning. The new Jeppesen charts only arrived the day before the new TMP came into effect.
  • The Planner advised that four other pilots had also flight planned direct to Oenpelli that morning (instead of via the VANDI ONE SID).
  • They had never had altitude restrictions before on the SIDs. It was the first time the pilot had ever been cleared to an altitude above a level restriction. The STARs have intermediate level restrictions, but prior to the new TMP, the pilot had only ever been cleared to an altitude lower than the restriction when also cancelling the height restriction (for example ‘descend to 4,000 cancel STAR level restriction’).
Pilot of VH-ZCJ

The pilot of ZCJ stated that the flight management system (FMS) calculated the top of descent point based on the track of the STAR. As the pilot had been advised to expect track shortening and a visual approach, they had to commence the descent earlier. The aircraft was slightly above the normal approach path and at a slightly higher rate of descent than normal, when approaching 7,000 ft. The pilot had vertical navigation (VNAV) mode selected, with VPATH in the flight mode annunciator, and ALTV armed, therefore the FMS follows the STAR profile programmed and captured the approach level restriction (of 7,000 ft).

In addition, the pilot commented that the company had sent emails and a flight operations notice to company flight crew highlighting the changes and new procedures for Darwin, prior to the commencement of the new TMP. There were NOTAMs issued months beforehand about the new SIDs and STARs to ensure the pilots were aware of the new procedures.

Operator comments – operator of VH-JLT

The operator of JLT advised that the auto-flight system of JLT was unserviceable on the incident flight. That unserviceability led to increased pilot workload, therefore reducing the pilot’s spare capacity to maintain situational awareness.

The operator believed that the change management process prior to the airspace changes was insufficient. The number of incidents that occurred immediately following the implementation of the new TMP supported that belief. The operator suggested that face-to-face briefings with the local pilots would have been more effective than just issuing NOTAMs.

The Jeppesen Charts with the new procedures were only released the day before the changes were implemented. Additionally, the associated GPS software was not available until 10 hours after the new procedures commenced at midnight.

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 actions in response to this occurrence.

Aircraft operator – VH-ZCJ

As a result of this occurrence, the operator of ZCJ has advised the ATSB that they have taken the following safety actions:

Education email from Defence air traffic control (ATC)

An email from Defence ATC was sent by CASA to the operator of ZCJ, who then distributed the email to company pilots operating out of Darwin. The email advised that since the new TMP came into effect on 28 May, there had been nine occurrences of pilots failing to comply with the VNAV requirements of the SIDs and STARs. The email directed pilots to the relevant sections of the AIP. These stated that when ATC issues climb clearances to an aircraft on a SID, or descent clearances to an aircraft on a STAR, the aircraft must comply with all level restrictions or requirements published on the SID or STAR charts unless ATC explicitly cancels the restrictions or requirements.

Safety bulletin

A safety bulletin was issued to all flight crew operating out of Darwin. The bulletin advised flight crew of the recent violations of SID and STAR altitude restrictions under the new TMP. Pilots were reminded to maintain extra vigilance and situational awareness while briefing and approaching the new level restrictions. The bulletin noted that as evidenced by this incident, other aircraft may not comply with the restrictions. Flight crew were directed to engage VNAV with active vertical mode where available. In aircraft without VNAV capability, the Altitude Selector was to be set to the limiting altitude and the cleared level written down until the SID or STAR restriction had been passed.

Critical to Safety Operations notice

A ‘Critical to Safety Operations’ notice was issued to all flight crew operating out of Darwin. The notice reiterated the need to comply with level restrictions unless explicitly cancelled. The notice also provided directives regarding the use of VNAV and the FMS to conduct SIDs and STARs in Darwin.

Flight operations manual update

The Flight operations manual is being updated with further guidance on the new Darwin procedures.

Local airspace briefing

The local airspace briefing presentation for new pilots has been updated to incorporate the new Darwin TMP procedures.

Aircraft operator – VH-JLT

As a result of this occurrence, the operator of JLT has advised the ATSB that they are taking the following safety actions:

Training information for flight crew

Company flight crew have been reminded of the importance of adhering to standard operating procedures and regulatory requirements.

Traffic control facility training

The operator will participate in training sessions in the Air Traffic Control Facility with Defence ATC Darwin, to develop understanding of the issues that flight crew and air traffic control personnel identify with the airspace.

Safety newsletter

A safety newsletter will be sent to all company flight crew to remind them of the importance of understanding the SID and STAR chart requirements.

Air traffic control

New procedure implemented

With immediate effect, Darwin ATC implemented a new procedure following this incident. If a VNAV restriction is in place and one aircraft has not complied, the controller is to immediately resort to tactical separation until that confliction is cleared.

Training and awareness

Materials designed to enhance awareness of the requirements and implications of the new traffic management plan will be promulgated to local aviation operators.

Incident briefings

Defence ATC provided briefings with other local operators at the ATC Facility showing this incident, discussing the TMP and the need for compliance of VNAV on the SID's and STARs.

Safety message

For controllers, this incident highlights the need to monitor aircraft after issuing a full climb or descent, where an intermediate level restriction applies. If an aircraft appears not to be complying with a level restriction, apply tactical separation.

For pilots, this incident provides a reminder to become familiar with published standard departure and arrival procedures and charts, particularly those with intermediate level restrictions, and the associated phraseology used by air traffic controllers and pilots.

Aviation Short Investigations Bulletin - Issue 43

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2015

image_5.png

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 Australian Defence Force provides the air traffic control services in Darwin.
  2. In Australia, altitudes below 10,000 ft are reference the local or area QNH and are referred to as feet (ft). When operating at altitudes above 10,000 ft an aircraft’s height above mean sea level is referred to as a flight level (FL) and is reference a standard pressure setting of 1013.2 HPa.
  3. The radar has a predictive capability due to a 5 second refresh rate so if an aircraft is approaching an assigned altitude with a high rate of descent the radar read out will effectively ‘predict’ the attitude in five seconds time. The pilot reported the aircraft indicated about 6,900 ft, but the radar indicated 6,700 ft.

 

Occurrence summary

Investigation number AO-2015-061
Occurrence date 10/06/2015
Location near Darwin Airport
State Northern Territory
Report release date 07/10/2015
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of separation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Cessna Aircraft Company
Model 441
Registration VH-JLT
Serial number 441-0138
Sector Turboprop
Operation type Charter
Departure point Darwin, NT
Damage Nil

Aircraft details

Manufacturer Raytheon Aircraft Company
Model B200
Registration VH-ZCJ
Serial number BB-1853
Sector Turboprop
Operation type Medical Transport
Departure point Elcho Island, NT
Destination Darwin, NT
Damage Nil

Separation issue involving a Pacific Aerospace Corporation CT/4B, VH-YCU and a Diamond DA 40, VH-UNV, near Quirindi, New South Wales, on 4 June 2015

Final report

What happened

Early in the afternoon on 4 June 2015, a Pacific Aerospace CT/4B, registered VH-YCU (YCU), was conducting an instrument training flight in the training area to the south-west of Tamworth, New South Wales, with an instructor and student on board. At the same time, a Diamond DA 40, registered VH-UNV (UNV), departed Tamworth on a visual navigation student assessment flight, bound for Bankstown, New South Wales, also with an instructor and student on board. Both aircraft were operating under the visual flight rules,[1] and the weather conditions were fine and clear.

As part of the training sequence, the instructor in YCU directed the student to intercept the 360 degree bearing from the Quirindi non-directional beacon (NDB)[2] The instructor further directed the student to track inbound to the Quirindi NDB at 4,500 ft[3] on that bearing (Figure 1), and carry out a Quirindi NDBA approach.

When about 10 NM north of Quirindi, the student in YCU broadcast their position and intentions on the Quirindi Common Traffic Advisory Frequency (CTAF).[4] The pilot of a recreational aircraft responded to the effect that they were operating in the circuit area at Quirindi. There was no response from any other aircraft. When about 5 NM from Quirindi, the student in YCU made another broadcast on the CTAF, indicating their intention to enter a holding pattern from overhead the NDB, in preparation for the NDBA approach. There was no response from any other aircraft to that broadcast.

At about the same time, UNV was tracking from Gate South (a reporting point south-west of Tamworth) towards Quirindi, also at 4,500 ft (Figure 1). The crew of UNV planned to overfly Quirindi then turn to the south-east and track towards Scone. The crew of UNV were monitoring the area VHF,[5] but not the Quirindi CTAF. As such, the crew of UNV did not hear the CTAF broadcasts made by the student in YCU. Even though the crew of both aircraft were monitoring the area VHF, neither had made any broadcasts on that frequency, so neither crew was aware of the other aircraft. At the time, both were tracking towards Quirindi at the same altitude.

Figure 1: Extract from a visual chart showing the manner in which the tracks of the two aircraft converged as they neared Quirindi, and the general direction of flight of each aircraft after they passed Quirindi (YCU turning to the north-east and UNV turning to the south-east)

Figure 1: Extract from a visual chart showing the manner in which the tracks of the two aircraft converged as they neared Quirindi, and the general direction of flight of each aircraft after they passed Quirindi (YCU turning to the north-east and UNV turning to the south-east)

Source: Airservices Australia, additions by the ATSB

Just north of Quirindi, the traffic collision avoidance device fitted to YCU alerted the crew to an aircraft in their vicinity, at a distance of 0.4 NM, at the same altitude. The instructor commenced an intensified lookout and soon sighted UNV. At that moment, UNV was in about the 10 o’clock position[6] relative to YCU, at the same altitude, on a slightly converging flight path. The instructor in YCU estimated that at the time UNV was sighted, YCU was in approximately the 4 o’clock position relative to UNV.

Although there was no immediate risk of a collision, the instructor in YCU took control of the aircraft from the student and made a heading adjustment through about 20 degrees to the right. On the new heading, the instructor was satisfied that the flight path of the two aircraft would diverge. In recalling the incident, the instructor in YCU estimated that, at their closest point, the separation between the two aircraft was about 60 m laterally, at the same altitude.

After sighting UNV, the instructor in YCU attempted to establish contact with the crew of UNV on the Quirindi CTAF. The pilot of the recreational aircraft operating at Quirindi responded, but there was no response from the crew of UNV.

Still unaware of the proximity of YCU, the crew of UNV passed over Quirindi then turned to the south-east towards Scone, and commenced a climb to 5,500 ft. As they climbed, the instructor in UNV sighted YCU behind and beneath them, in about their 8 o’clock position. By that time, the crew in YCU had also passed Quirindi, and were now turning towards the north-east for the NDBA holding pattern. Having sighted YCU, the instructor in UNV was satisfied that the two aircraft were on divergent headings and vertical separation was increasing as UNV climbed.

Following the separation issue, the instructor in YCU called air traffic control (Brisbane Centre) on the area VHF in an attempt to establish communications with the crew of UNV. The crew of UNV, who were still monitoring the area VHF, intercepted that call and responded. The crew of UNV then selected the Quirindi CTAF on one of their radios, and they had a brief discussion on that frequency. By the time communications were established on the CTAF, UNV was nearing 5,500 ft on a south-easterly heading towards Scone. The crew of YCU were resuming their planned exercise, entering the Quirindi NDBA holding pattern.

Instructor comments - YCU

The instructor in YCU made a number of comments regarding the incident, including:

Use of radios. YCU was fitted with two VHF radios. During operations in the training area, the crew were monitoring the area VHF on one radio, and company operations on the other. The radio that was being used to monitor the company operations frequency, was switched to the Quirindi CTAF as they prepared for their NDBA approach at Quirindi. As such, the crew were monitoring the area VHF and Quirindi CTAF at the time of the incident.

Instrument flight training hood. The student in YCU was wearing an instrument flight training hood. The hood projected forward from the student’s helmet in a manner that denied the student external visual reference, but allowed the student to scan cockpit instruments (to simulate instrument meteorological conditions). Under these circumstances, the instructor maintained a lookout for other aircraft and hazards, but the position of the student’s helmet and hood was such that the instructor’s visibility to the left of the aircraft was partially obscured. With that in mind, when alerted to other traffic in the vicinity, the instructor targeted a lookout to the left of the aircraft, past the student’s helmet and hood. During this targeted lookout, the instructor sighted UNV. When the instructor sighted UNV, the aircraft was remaining on a constant line of sight relative to YCU, in approximately the 10 o’clock position.

Density of training operations at Quirindi and Gunnedah. The instructor in YCU noted that even though Quirindi and Gunnedah are often used for flight training purposes, there is nothing in the En route Supplement Australia (ERSA) to alert pilots accordingly.

Instructor comments - UNV

The instructor in UNV made a number of comments regarding the incident, including:

Use of radios. UNV was fitted with two VHF radios. The instructor commented that depending on the circumstances, either radio could be used to monitor and broadcast on relevant CTAFs. At the time of this incident, the crew were monitoring the area VHF with one radio, and the company operations frequency on the other.

Monitoring the CTAF. The instructor in UNV was aware that the student in UNV was not monitoring the Quirindi CTAF as they approached from the north, even though it was normal practise to monitor a CTAF under these circumstances (overflying an aerodrome). On this occasion, the instructor elected not to prompt the student to monitor the CTAF in order to reinforce a teaching point to the student regarding frequency management. The instructor was satisfied that a visual lookout would suffice under the circumstances – the conditions were fine and clear, and there were no broadcasts or other transmissions on the area VHF to suggest that there was any potentially conflicting traffic in their area.

ATSB comment

The separation issue in this case may have been avoided if the pilots of the two aircraft involved had been monitoring and broadcasting on the same frequency. Both crews were monitoring the area VHF, but operating under the visual flight rules, there was no specific requirement for the crew of either aircraft to make a broadcast on that frequency. The crew of YCU broadcast their position and intentions on the Quirindi CTAF, but the crew of UNV were not monitoring that frequency.

The requirement to monitor a CTAF is subject to a level of interpretation, particularly with respect to the altitude above an airfield at which the requirement applies. The Aeronautical Information Package (AIP) requires a pilot to broadcast on the CTAF when he/she enters the vicinity of a non-controlled aerodrome. AIP goes on to describe the vicinity of a non-controlled aerodrome as being:

…within 10 nm of the aerodrome and at a height above the aerodrome that could result in conflict with operations at the aerodrome.

Existing forums and processes (managed by CASA and Airservices Australia) allow airspace users to influence the manner in which airspace is managed and propose changes to relevant documents (such as the En Route Supplement Australia). Where changes have the potential to improve safety, operators are encouraged to present proposals for consideration, using those forums and processes. One relevant forum for proposing airspace-related safety improvements is the CASA Regional Airspace and Procedures Advisory Committee.

Safety message

Pilots are encouraged to ‘err on the side of caution’ when considering when to make broadcasts and whether specific frequencies should be monitored, particularly noting the fundamental importance of communication in the effective application of the principles of see-and-avoid. An ATSB report titled Limitations of the See-and-Avoid Principle outlines the major factors that limit the effectiveness of un-alerted see-and avoid.

Insufficient communication between pilots operating in the same area is the most common cause of safety incidents near non-controlled aerodromes.

A search for other traffic is eight times more effective when a radio is used in combination with a visual lookout than when no radio is used.

The CASA booklet titled Operations at non-controlled aerodromes provides guidance with respect to the limitations of the see-and-avoid principle and relevant radio procedures.

also provides relevant guidance with respect to CTAF procedures.

Aviation Short Investigations Bulletin Issue 44

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2015

image_5.png

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. Visual flight rules are a set of regulations, which allow a pilot to only operate an aircraft in weather conditions generally clear enough to allow the pilot to see where the aircraft is going.
  2. An NDB is a radio transmitter used as an aid to navigation. The signal does not include inherent directional information.
  3. 4,500 ft above mean sea level is about 3,450 ft above ground level overhead Quirindi aerodrome.
  4. The CTAF is the frequency on which pilots operating at a non-controlled aerodrome should make positional radio broadcasts.
  5. Area VHF (very high frequency) is the appropriate flight information area frequency for a location.
  6. The clock code is used to denote the direction of an aircraft or surface feature relative to the current heading of the observer’s aircraft, expressed in terms of a position of an analogue clock face. Twelve o’clock is ahead while an aircraft observed abeam to the left would be said to be at 9 o’clock.

 

Occurrence summary

Investigation number AO-2015-060
Occurrence date 04/06/2015
Location Quirindi Airport
State New South Wales
Report release date 04/11/2015
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Separation issue
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Pacific Aerospace Corporation
Model CT/4B
Registration VH-YCU
Serial number 079
Sector Piston
Operation type Flying Training
Departure point Tamworth, NSW
Destination Tamworth, NSW
Damage Nil

Aircraft details

Manufacturer Diamond Aircraft Industries
Model DA 40
Registration VH-UNV
Serial number 40.1077
Sector Piston
Operation type Flying Training
Departure point Bankstown, NSW
Destination Bankstown, NSW
Damage Nil

Technical assistance to the TAIC - Collision with terrain involving Robinson R44, ZK-IPY, 12 km south-west of Queenstown Airport, New Zealand, on 19 February 2015

Summary

On 19 February 2015, a Robinson R44 helicopter, registration ZK-IPY, collided with terrain 12 km south-west of Queenstown Airport, New Zealand.

The New Zealand Transport Accident Investigation Commission (TAIC) conducted an investigation into the circumstances of the accident. As part of its investigation, TAIC requested technical assistance from the ATSB. To protect any information supplied by TAIC to the ATSB, and the ATSB's investigative work to assist TAIC, the ATSB initiated an investigation under the Transport Safety Investigation Act 2003.

The ATSB has finalised its work in support of the TAIC investigation and TAIC is responsible for the release of the final investigation report. Any enquiries in respect of the TAIC investigation or release of the investigation report should, in the first instance, be directed to the TAIC at: www.taic.org.nz.

Transport Accident Investigation Commission
Level 16
80 The Terrace
PO Box 10323
Wellington, 6143 New Zealand

 

_________________

The information contained in this web update is released in accordance with section 25  of the Transport Safety Investigation Act 2003.


Occurrence summary

Investigation number AE-2015-059
Occurrence date 19/02/2015
Location 12 km south-west of Queenstown Airport, New Zealand
State International
Report release date 29/08/2016
Report status Final
Investigation level Defined
Investigation type External Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Robinson Helicopter Co
Model R44
Registration ZK-IPY
Sector Helicopter
Damage Destroyed

Signals Passed at Danger by Train 1240, at Marshall (Geelong) Victoria, on 29 May 2015

Final report

Safety summary

What happened

On 29 May 2015, an empty VLocity type passenger train was being transferred from Waurn Ponds to Geelong, passing through Marshall and South Geelong stations enroute and without stops. The empty-cars train was following a Melbourne-bound service.

When the empty-cars approached Marshall, the Distant signal for this location was displaying Caution. This indicated that at least one of the Home signals in advance was at Stop. The train’s speed was reduced in response to this indication, but was subsequently increased to above 100 km/h as the train continued towards Marshall Railway Station.

Nearing Marshall station platform, the driver observed the next Home signal at Stop and applied the train’s brakes. However, the train could not be stopped before it passed this signal and the next, which were both at Stop.

Marshalltown Road level crossing intersects with the railway about 140 m beyond Marshall Station and the empty cars entered the crossing before the warning devices activated.

There was no collision at the crossing, no injuries, and no damage to any infrastructure as a consequence of this incident.

What the ATSB found

The ATSB found that the driver of the empty-cars did not respond appropriately to the two-position signal indications through the Marshall location, including the Caution indication on the Distant signal. The speed of the train was too high as it approached Marshall station and as a result the train could not be stopped in response to observing the next signal at Stop.

The driver had recently qualified to drive passenger services and this was his first shift driving without supervision. It was found that the training had not adequately prepared the driver for the sequence of two-position signals at this location. The predominant signalling on the Melbourne-Geelong corridor is three-position.

The ATSB also found that the rule that described the required driver response to a Distant signal at Caution in a two-position signalling system did not fully reflect the design principles for this type of signalling configuration.

Since the re-establishment of Marshall station, rail passenger traffic through Marshall had increased tenfold, and there was scope to enhance the signalling configuration.

What's been done as a result

Immediate actions by V/Line included imposing temporary speed restrictions for this location and retraining the driver in two-position signalling. V/Line also developed a simulator session to improve driver training in two-position signalling.

V/Line advised that funding has been secured for the development of a business case and feasibility study for a track and signalling upgrade of the South Geelong – Waurn Ponds section.

ATSB has recommended that V/Line amends the rule for the required driver response to a Distant signal at Caution.

Safety message

Operating rules and Driver training should align with the underlying principles of a network’s signalling infrastructure.

Sources and submissions

Sources of information

The sources of information during the investigation:

  • V/Line Pty Ltd
  • the train driver.

References

  • Loukopoulos, L.D., Dismukes, R.K. & Barshi, I. (2009). The Multitasking Myth. Handling Complexity in Real-World Operations. Ashgate: Farnham.
  • Reason, J. (1990). Human Error. Ashgate: Aldershot.

Findings

The following findings are made with respect to the Signal Passed at Danger (SPAD) events by train 1240 at Marshall, near Geelong, Victoria on 29 May 2015. These findings should not be read as apportioning blame or liability to any particular organisation or individual.

Safety issues, or system problems, are highlighted in bold to emphasise their importance. A safety issue is an event or condition that increases safety risk and (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.

Contributing factors

  • The driver of train 1240 did not respond appropriately to the Caution indication on Distant signal MSL22 and subsequent two-position Home signals through the Marshall location.
  • The speed of train 1240 approaching Marshall station was too high for the driver to respond in sufficient time to the Stop indications displayed by signals MSL10 and MSL8.
  • The training and assessment of the driver did not ensure that he had an adequate understanding of the two-position signalling through Marshall. [Safety Issue]

Other factors that increased risk

  • The rule describing the required driver response to a Distant signal at Caution in a two-position signalling system did not fully reflect the signalling system design principles. [Safety Issue]
  • The presence of a section of two-position signalling on a corridor that was predominantly three-position had the potential to increase human error. There was a high reliance on driver route knowledge to manage this risk.
  • Since the re-establishment of Marshall station, rail passenger traffic had increased markedly, raising the risk profile of the location. There was scope to enhance the signalling configuration to better control these risks.

The occurrence

At about 1900 on 29 May 2015, the 1744 passenger service from Melbourne arrived at Waurn Ponds. Waurn Ponds is a suburb of Geelong, a regional city about 65 km southwest of Melbourne, Victoria. The section between Geelong and Waurn Ponds station is about 12 rail km and passes through South Geelong and Marshall Stations (Figure 1).

Figure 1: The route between Geelong and Waurn Ponds stations

Figure 1: The route between Geelong and Waurn Ponds stations

Source: PASS Assets (Public Transport Victoria) adapted by Chief Investigator, Transport Safety (Vic)

The car-set and its driver was scheduled to return empty-cars to Geelong where the train would form a service to Melbourne. To allow a Melbourne-bound service from Warrnambool to pass through the section, the empty train was shunted into the siding at Waurn Ponds.

After the passage of the Melbourne-bound train (Train 8250), Train 1240 (the empty-cars) was signalled onto the mainline towards Marshall. It increased speed and travelled at between 80 and 90 km/h as it passed Waurn Ponds station. About a kilometre past Waurn Ponds, the train encountered Distant signal MSL22. This signal, about 3.6 km before Marshall Station, was the first of five signals that controlled Geelong-bound traffic on the mainline through Marshall (Figure 2).

Figure 2: The signals controlling Geelong-bound rail traffic through Marshall

Figure 2: The signals controlling Geelong-bound rail traffic through Marshall

Source: Chief Investigator, Transport Safety (Vic)

Distant signal MSL22 was at Caution when the train passed, and the signals ahead were at Stop (Figure 3). In response to the Caution indication of MSL22, the driver reduced the speed of the train from 83 km/h to 67 km/h.

Figure 3: Signal status when Train 1240 passed Distant Signal MSL22. MSL22 was at Caution (yellow), and other signals ahead were at Stop (Red). The red highlight on the line adjacent to MSL22 is indicating that Train 1240 is detected in the section.

Figure 3: Signal status when Train 1240 passed Distant Signal MSL22. MSL22 was at Caution (yellow), and other signals ahead were at Stop (Red). The red highlight on the line adjacent to MSL22 is indicating that Train 1240 is detected in the section.

Source: Geelong Regional Signalling Centre, extract and annotation of VDU recording by Chief Investigator, Transport Safety (Vic)

The next signal, Home signal MSL24, was located 2,276 m past the Distant signal. As the train travelled towards it, the signal indication changed from Stop to Proceed. Signalling through this section was two-position, meaning that Stop was indicated by a red light, and Proceed by a green light. Home signals in a two-position signalling system do not provide information on the required train speed, nor the condition of the next signal.

When the train was about 900 m from MSL24 and following the driver’s observation of its Green (Proceed) aspect, the speed of the train was increased. The train’s speed was about 90 km/h passing signal MSL24. As the train continued towards Home signal MSL26 that was 1,280 m away and at Proceed, its speed further increased. The train’s speed peaked at 105 km/h shortly after passing signal MSL26.

Soon after passing signal MSL26, the driver observed Home signal MSL10 at Stop, and probably also the next Home signal, MSL8, that was also at Stop. Both were at Stop because the train ahead had not yet cleared into South Geelong.

In response to the Stop indications, the driver made a brake application that within about five seconds progressed to an emergency application. Train 1240 could not be stopped in the distance available and passed Home signal MSL10 travelling at about 80 km/h and then Home signal MSL8 at about 60 km/h. In each instance, the signal was passed at Stop without authority resulting in a Signal Passed at Danger (SPAD) event.

The train then entered the Marshalltown Road level crossing travelling at about 50 km/h. The warning devices (lights and bells) began with the train on the crossing and the boom barriers lowered about 10 seconds later. There were no road vehicles nor pedestrians attempting to cross as the train entered the unprotected crossing. However, shortly prior, a route bus and light truck had traversed the crossing, 30 and 15 seconds prior respectively.

The train came to a stand with its leading cab about 80 m passed the crossing. There were no injuries resulting from the incident. The incident occurred at about 1932.

After reporting the incident, the driver was authorised to shunt the empty cars back into the crossing loop at Marshall. He was then stood aside from driving duties. A breath test was conducted with a zero alcohol result. Testing for the presence of drugs was not conducted.

Safety issues and actions

The safety issues identified during this investigation are listed in the Findings and Safety issues and actions sections of this report. The Australian Transport Safety Bureau (ATSB) expects that all safety issues identified by the investigation should be addressed by the relevant organisation(s). In addressing those issues, the ATSB prefers to encourage relevant organisation(s) to proactively initiate safety action, rather than to issue formal safety recommendations or safety advisory notices.

Depending on the level of risk of the safety issue, the extent of corrective action taken by the relevant organisation, or the desirability of directing a broad safety message to the [aviation, marine, rail - as applicable] industry, the ATSB may issue safety recommendations or safety advisory notices as part of the final report.

Driver training

Safety issue: RO-2015-009-SI-01

The training and assessment of the driver did not ensure that he had an adequate understanding of the two-position signalling through Marshall.

Network rule governing Distant signals

Safety issue: RO-2015-009-SI-02

The rule describing the required driver response to a Distant signal at Caution in a two-position signalling system did not fully reflect the signalling system design principles.

Context

Marshall and surrounds

Development in southern Geelong

Marshall Railway Station had been closed in 1958. It was re-established in 2004 to serve the expanding southern suburbs of Geelong, and the demand for commuter services to Melbourne.

The re-development of Marshall was a State funded and managed project. During this period, lease arrangements and management of the regional network was transferred (in 2004) from Freight Australia Limited to Pacific National. Track management of the network was subsequently transferred to V/Line in 2007.

Marshall Station was re-established with a single platform serviced by the bi-directional mainline. The development included the introduction of a loop to cater for the crossing of trains and terminating locomotive hauled passenger trains from Melbourne. The loop allowed the locomotive to be ‘runaround’ the consist for the return trip to Melbourne. The signalling was designed to allow this locomotive movement to occur without the fouling or activation of the Marshalltown Road level crossing. There was nothing unusual about this configuration for these operations.

With the introduction of VLocity type DMU trains into the Geelong corridor, the use of locomotive hauled trains terminating at Marshall diminished significantly.

Waurn Ponds Railway Station was established in September 2014. A holding siding to shunt trains clear of the mainline was provided about two kilometres from this station, towards Warrnambool.

Waurn Ponds became the normal terminating point for trains travelling to the southern suburbs of Geelong and as a result, terminations at Marshall became less common.

Safeworking system background

Prior to the re-establishment of Marshall Station, Train Order Working[1] was in place for the single line section between South Geelong and Winchelsea (about 40 km west of Geelong). When re-established, Marshall became an Intermediate Terminal Station for the two sections South Geelong - Marshall and Marshall - Winchelsea.

Then, in September 2005, the Train Staff and Ticket Safeworking System[2] was introduced between South Geelong and Marshall and Marshall was made an attended Train Order Station. The signalling system at Marshall was to be operated locally and manned for all trains.

In December 2005, further changes to the safeworking arrangements were made. The sections between South Geelong and Marshall were altered to operate under the Track Block Safeworking System, and the operation of the signalling at Marshall was transferred to the Geelong Regional Signalling Centre.

Track Block Safeworking System

The operating rules and procedures applicable to the Track Block Safeworking System were described in Section 32 of the 1994 Book of Rules and Operating Procedures. The object of the system was to prevent more than one train being on the same line in the section between two adjoining locations. This was achieved by the signaller not being able to place the signal controlling the entrance to the Track Block single line section to the Proceed position until the preceding train had exited the section.

The Track Block Safeworking System was in use on the Victorian broad-gauge network between:

  • Newport - Brooklyn (West line)
  • Brooklyn - Sunshine
  • Geelong – Waurn Ponds

The Geelong-Waurn Ponds section was the only passenger line where it applied.

Signalling arrangements through Marshall

Two-position coloured-light fixed signalling was in place between South Geelong – Marshall – Waurn Ponds. The signal numbers relevant to this event are shown enlarged on an extract of the signalling control display (Figure 4).

Figure 4: Extract of signalling control display South Geelong - Marshall - Waurn Ponds

Figure 4: Extract of signalling control display South Geelong - Marshall - Waurn Ponds

Source: V/Line Geelong Regional Signalling Centre, extract and annotation of VDU recording by Chief Investigator, Transport Safety (Vic)

The Marshall location had a signal sequence on the mainline in each direction of a Distant signal followed by a series Home signals. For Geelong-bound traffic, the signal sequence through Marshall was:

  • MSL22 (Distant signal)
  • MSL24 (Home signal)
  • MSL26 (Home signal) that had signals for the mainline and the loop track
  • MSL10 (Home Signal) and MSL12 (on the Loop track)
  • MSL8 (Home signal).
Signal control through Marshall

At the time of the incident, signalling control for Marshall was managed from the Geelong Regional Signalling Centre. This control function has since been relocated to Centrol[3] in Melbourne.

At Geelong, the relevant control workstation provided for remote control and monitoring of the signalling system between South Geelong[4] and Waurn Ponds. Signallers could observe the status of all the signalling in the area of control by means of a VDU Panel. The VDU panel also provided the means of operating the points and signals.

The signaller had control of all Home signals at Marshall. For Geelong-bound rail traffic, the Home signals could be operated individually or a through-route set such that signals would clear when the section ahead became available for following trains.

The signaller cannot control distant signal MSL22. The aspect of MSL22 was governed by the status of the Home signals through the location and functioned automatically. If all mainline Home signals at Marshall were clear, MSL22 would indicate Proceed (Green aspect), and if any was at Stop, MSL22 would indicate Caution (Yellow aspect).

Marshalltown Road level crossing activation

For trains approaching from Waurn Ponds when signals were at Proceed, a fixed track circuit activated the Marshalltown Road level crossing protection. This ensured that the crossing protection was activated in sufficient time prior to the arrival of the train.

When signal MSL8 was at Stop, the level crossing warning circuits were inhibited. This was to allow locomotive runaround movements without activating the crossing protection. Because of this configuration, Train 1240 did not trigger the crossing protection until it was beyond signal MSL8.

System protection for a train exceeding its authority

The two-position signalling system at Marshall did not include any additional controls to protect against a train exceeding its authority.

Waurn Ponds was commissioned about 10 years after Marshall and did include additional features to manage this risk. All Home signals at Waurn Ponds were fitted with Train Stop TPWS[5] to stop trains that passed a signal at Stop.

Signalling playback – recording of sequence of events

The status of signals and the movement of trains through the section were captured on the recording of the signaller’s display located at Geelong. The colour of the track section also provides an indication of its status with:

  • Red indicating the presence of a train in the section
  • Green indicating the track is clear and the route is set
  • Blue indicating the track is clear but no route is set.

At about 1922 after departing the siding, Train 1240 was travelling between Waurn Ponds and Marshall (Figure 5). At this time Train 8250 (the train ahead) had passed through Marshall Station and the Marshalltown Road level crossing had activated (road shown highlighted yellow). Another train was in the Waurn Ponds siding waiting to follow 1240.

Figure 5: Extract of VDU screen at 19:22:07 showing train 1240 travelling between Waurn Ponds and Marshall, approaching Distant signal MSL22 at Caution. The signals through Marshall are at Stop. The train ahead (8250) has passed through Marshall Station.

Figure 5: Extract of VDU screen at 19:22:07 showing train 1240 travelling between Waurn Ponds and Marshall, approaching Distant signal MSL22 at Caution. The signals through Marshall are at Stop. The train ahead (8250) has passed through Marshall Station.

Source: Geelong Regional Signalling Centre, extract and annotation of VDU recording by Chief Investigator, Transport Safety (Vic)

After Train 1240 passed Distant signal MSL22, MSL24 went to Proceed. The VDU screen at 19:23:03 showed MSL24 at Proceed and MSL26 still at Stop. All other Marshall signals were also at Stop.

Before Train 1240 passed MSL24, Home signal MSL26 also went to Proceed (Figure 6). At this point, the train ahead was approaching the Distant signal for South Geelong (SGL20), that was at Proceed (Green). Because this train was still occupying the section between MSL8 and SGL20, signals MSL10 and 8 were not yet cleared to Proceed.

Figure 6: Extract of VDU screen at 19:23:05 showing MSL26 now at Proceed. MSL10 and MSL8 are at Stop

Figure 6: Extract of VDU screen at 19:23:05 showing MSL26 now at Proceed. MSL10 and MSL8 are at Stop.

Source: Geelong Regional Signalling Centre, extract and annotation of VDU recording by Chief Investigator, Transport Safety (Vic)

The VDU screen at 19:24:31 shows that the preceding train (8250) had passed the Distant signal for South Geelong, SGL20, at around the time Train 1240 had passed MSL24. Train 8250 had not yet passed SGL19 and signals MSL10 and MSL8 had not yet cleared to Proceed.

The VDU screen at 19:25:26 shows that Train 1240 had passed Home signal MSL26, which had reverted to Stop. MSL10 was still at Stop and soon to be passed by Train 1240 without authority. Marshalltown Road level crossing had not yet not activated.

A few seconds later, Train 1240 had passed MSL10 at Stop (Figure 7) and was soon to pass MSL8 at Stop. Train 8250 was still progressing past SGL19. The headway between the two trains was such that Train 1240 needed to stop at Marshall to wait for Train 8250 to clear the section ahead.

Figure 7: Extract of VDU screen at 19:25:29 showing Train 1240 had now passed signal MSL10 at Stop

Figure 7: Extract of VDU screen at 19:25:29 showing Train 1240 had now passed signal MSL10 at Stop.

Source: Geelong Regional Signalling Centre, extract and annotation of VDU recording by Chief Investigator, Transport Safety (Vic)

A short time later, MSL8 had also been passed at Stop (Figure 8). The Marshalltown level crossing protection was not yet active.[6]

Figure 8: Extract of VDU screen at 19:25:34 showing that Train 1240 has now passed signal MSL8 at Stop. The Marshalltown Road level crossing warning protection has not yet activated. Train 8250 has not completely cleared SGL19.

Figure 8: Extract of VDU screen at 19:25:34 showing that Train 1240 has now passed signal MSL8 at Stop. The Marshalltown Road level crossing warning protection has not yet activated. Train 8250 has not completely cleared SGL19.

Source: Geelong Regional Signalling Centre, extract and annotation of VDU recording by Chief Investigator, Transport Safety (Vic)

Two-positioning signalling

Background

Two-position signalling was once common in Victoria but its use had declined. Two-position signals are route signals that apply to a single route. They do not provide drivers with information on the aspect of the next signal, nor specific guidance on the train speed to the next signal.

Home signals

Two-position Home signals are displayed as light signals or semaphores, although semaphore signals have become increasingly rare. Light signals come in various configurations and show either a red or green aspect (Figure 9).

Figure 9: Aspects of two-position Home signals

Signal number

Signal aspect

Signal meaning

Home signals:

MSL24

MSL26

MSL10

MSL8

STOP

Train must Stop at Signal

PROCEED

Train can Proceed to next Signal 

Source: ATSB

Home signals with two indications on the same signal post

Where multiple routes are available, signals are mounted either on a bracket post or arranged vertically on a single post. MSL26 was fitted with lights on brackets (Figure 10). A Proceed aspect (Green) is only shown for the route for which the points are locked and detected.

Figure 10: Multiple route two-position signal MSL26, with two light signals.
• The right hand signal provided an indication for the straight route and had a Green aspect (Proceed) for the passage of Train 1240.• The left hand signal provided a signal indication for the loop track and was red for Train 1240.

Figure 10: Multiple route two-position signal MSL26, with two light signals.
• The right hand signal provided an indication for the straight route and had a Green aspect (Proceed) for the passage of Train 1240.
• The left hand signal provided a signal indication for the loop track and was red for Train 1240.

Source: Chief Investigator, Transport Safety (Vic)
Distant Signals

Configuration

Distant signals are located ahead of the first home signal for a location and provide information to drivers on the indication of Home signals on the through route. Distant signals are located no less than the braking distance for the line speed ahead of the first home signal at the location.

Distant signals (Figure 14) can be displayed as light signals or semaphores, although the use of semaphore Distant signals has become increasingly rare on the V/Line network.

Distant signals display two aspects:

  • Yellow, indicating Caution and meaning that one or more of the Home signals applicable to the same line at that location may be at Stop.
  • Green, indicating Proceed and meaning that all Home signals applicable to the same line at that location are at Proceed.

Figure 11: Distant signal aspects, Yellow (indicating Caution) and Green (indicating Proceed), as they appear in V/Line training material. The semaphore configuration, shown on the left for each aspect, is used for V/Line assessments on Distant signals.

Figure 11: Distant signal aspects, Yellow (indicating Caution) and Green (indicating Proceed), as they appear in V/Line training material. The semaphore configuration, shown on the left for each aspect, is used for V/Line assessments on Distant signals.

Source: V/Line driver training courseware

Rules and Procedures pertaining to Distant signals

Section 2 part 5 of the Book of Operating Rules and Procedures 1994[7] stated in part:

  • A Distant signal at the Proceed position indicates all other signals applicable to the same line as the Distant signal are also at Proceed.
  • When the driver observes a Distant signal at Caution, the train must be slowed to a precautionary speed to allow the train to be safely stopped at the next signal if that signal displays Stop.

In the description of the driver’s response to a Caution indication, there was no reference to the possibility of subsequent Home signals through the location being at Stop.

Victorian Rail Industry Operators’ Group (VRIOG)

The Victorian Rail Industry Operators’ Group (VRIOG)[8] was a collaborative committee made up of rail operators and transport agencies. The purpose of the group was to establish standards to facilitate the interoperability of operations and infrastructure to enhance network safety.

VRIOG Standard 012.0 Victorian Signalling Principles Section 4 described signalling principles, signals, and points, interlocking, track vacancy detection, level crossings, and signalled single lines and proceed authorities.

Section 4.1.5 of this VRIOG standard described, in part:

  • Two position signals are route signals. Each signal applies to one route only. Two position signals do not provide information about what speed the train should travel; nor do they provide information about the aspect of the signal ahead.
  • Distant signals provide information regarding the state of Home signals on the through route at an interlocking:
  • If all of the signals ahead are at Proceed, the Distant signal can display a Green aspect.
  • If any one of the signals ahead is at Stop the Distant signal will display a Yellow aspect.

Three-position signalling

Three-position signalling was the predominant signalling type in the Melbourne metropolitan and RFR (Regional Fast Rail) areas and was in use between Melbourne and Geelong.

Three-position signals use a minimum of two lights to convey the signal indication that may apply to several routes in advance. The multiple light configuration differentiates a three-position signal from a two-position signal that will only display a single light.

Three position signals convey information to a train driver regarding the:

  • permitted speed of the train over the block ahead
  • aspect of the signal ahead.

Three position-signals come in a range of physical configurations and the possible aspects of a particular signal will be tailored to the needs of a location. There are seven indications[9] that can be displayed by three-position signals in Victoria, in all instances using at least two lights (Figure 12).

Figure 12: Three-position signal aspects. Three-position signals can have various physical configurations. The illustrated signals are to present the light aspects only.

Figure 12: Three-position signal aspects. Three-position signals can have various physical configurations. The illustrated signals are to present the light aspects only.

Source: Chief Investigator, Transport Safety (Vic)

The driver

Prior to joining V/Line, the driver had about five years experience operating freight trains between Echuca and Deniliquin. This territory was low traffic volume and low speed. Signalling was two-position, but without Distant signals.

The driver commenced employment with V/Line in October 2014 and was assigned to the Southern Cross driver’s depot. He had recently qualified to operate V/Line passenger trains on all lines worked by Melbourne based drivers. His medical was current with no restrictions recorded.

Prior to the incident shift, the driver had been rostered on shifts of eight hours duration working in and around Southern Cross Station on non-passenger services. His previous shift on 27 May 2015 was rostered to finish at 2000. He then travelled to Echuca to visit his family, returning to Melbourne on 29 May to be in position for the start of his shift at 1400. Roster induced fatigue is not considered to be a factor in this incident.

The shift on 29 May was the driver’s first operating passenger services without supervision.

Driver training

Scope

This driver commenced his training with V/Line in October 2014. Because of his previous operational experience, the driver was enrolled on the V/Line Conversion Driver Training Plan (Freight Train SCS-Regional Centres Conversion Training Plan). This training had a minimum duration of 21.4 weeks and comprised both classroom and in-field practical training.

He was required to complete all training modules covering train operations on the V/Line network including signalling and Safeworking. Some exemptions in subjects were provided in recognition of the driver’s freight experience, but none in subjects relevant to the circumstances of this incident.

The training module and assessments completed for two-position signals was the same as for any other new V/Line employee in training to be a driver.

Practical driving training comprised several stages as the driver progressed from guided driving (with supervisor guidance and explanation), through unguided driving (with supervision), and finally assessment of driving competency.

Training materials on two-position signals including Distant signals

The training material for two-position fixed signals described different signal types including Home signals and Distant signals, and included diagrams of both the older style semaphore signals and light-only signals. The training material addressed possible signal configurations, aspects, and indications. With respect to the application of Distant signals, the course notes were consistent with the published network rules and stated:

  • A Driver passing a Distant signal at Proceed would expect to find all other fixed signals applicable to the same line also at Proceed, but must read all signals and be prepared to act accordingly if the Home or Starting signal is at Stop.
  • A Driver having passed a Distant signal at Caution must slow the train to a precautionary speed to allow the train to be safely stopped at the next signal if this signal displays Stop.

There was no other guidance within the course material that described the design principles associated with Distant signals, and the specific scenario of a Distant signal at Caution and Home signals other than the first encountered being at Stop. Instructors may have explained these principles in class and during the practical training, but there is no supporting material within the training courseware.

Route knowledge training for Marshall

Route knowledge was taught through classroom and in-field training. The in-field component included a requirement that the driver undertake a minimum of three runs on each corridor. It was reported that this driver had four or five runs on the Waurn Ponds-Geelong sector, the last about two weeks before the incident. None of the familiarisation trips through Marshall were conducted at night.

Assessment

The driver assessment was conducted over several stages of the training program. Three written signal exams were conducted, all multiple-choice answer format. Assessment pertinent to Distant signals included:

  • Stage 2 Signal Exam – questions pertained to the two possible aspects of a Distant signal. The answer option for a driver’s response to a Distant signal at Caution was consistent with the published rule that the driver be prepared to stop at the next fixed signal.
  • Stage 10 Signals A Exam – similar to Stage 2 assessment.
  • Stage 10 Signals B Exam – limited to the identification of a Distant signal.

All photographs of Distant signals used in the written assessments were of the older style semaphore signals. There were no samples of light-only Distant signals in the assessment materials.

Practical assessment included train handling under guidance and check rides with an independent assessor. The Graduation stage included computer based route knowledge assessments and practical in-field assessments on all five regional corridors.

This driver had successfully completed all components of assessment by 25 May 2015, including the final route knowledge and practical in-field assessments on the five corridors, which included Marshall.

__________

  1. Train Order working is a Safeworking system that involves the use of a paper instrument issued by the Train Controller as the train driver’s authorisation to enter and proceed through the nominated single-line section. It is used on low volume single lines.
  2. Train Staff and Ticket system is a Token based Safeworking system on low volume single lines.
  3. The operational control centre for the V/Line network.
  4. At South Geelong, signals are operated locally.
  5. Train Protection Warning System.
  6. Crossing is shown yellow when active.
  7. Used by V/Line and Metro Trains Melbourne.
  8. This group has been disbanded and a new approach to standards is being developed by Public Transport Victoria (PTV).
  9. Three-position signalling indications corresponding to the aspects shown in Figure 12:
    1. Clear Normal speed – the train may proceed at the maximum speed allowed for the locality and that the next fixed signal is at Proceed.
    2. Normal speed warning – the driver must be ready to stop at the next fixed signal.
    3. Reduce to Medium speed – the train may proceed at the normal speed but must reduce to medium speed before the next signal.
    4. Clear medium speed – the train must not exceed 40 km/h and the next fixed signal is displaying a Proceed aspect.
    5. Medium speed warning – the driver may proceed at medium speed and must be prepared to stop at the next signal.
    6. Stop.
    7. Low speed Caution – the points are set in the correct position for the driver to proceed. It does not indicate that the line is unoccupied and the driver must be prepared to stop short of any obstruction. The speed of the train must not exceed 15 km/h.

Safety analysis

Train handling

Human response

Human performance is by its nature highly variable. Our ability to perceive, pay attention to, and to hold and manipulate information in our memory is limited by our finite cognitive capacity, and is subject to a number of influencing factors.

One way of describing human performance is by reference to the level of conscious control applied to that performance. That is, the extent to which our actions in any given situation are governed by conscious attention or by developed habit patterns; automatic processes which operate largely outside of our conscious control.

Some tasks require a high level of conscious attention, such as whenever we are learning how to perform a new task, or are problem solving in unanticipated circumstances. Other tasks, as people become familiar and then expert at them, require less and less conscious effort, and become increasingly automated, habitual responses to a known set of circumstances, such as perceiving and interpreting a signal indication.

Errors at reduced conscious control levels, sometimes called rule based and skill based performance levels, can occur when the current circumstances require the operator to do something different to usual. The error occurs when the stronger habitual response associated with these particular situational cues dominates, thus producing an inappropriate action for the current situation. This has been referred to in the human performance literature as a ‘strong but wrong’ response.

When the driver of Train 1240 approached the Marshall Distant signal (MSL22), it was displaying a Caution indication, providing warning that any of the following signals through Marshall may be at Stop. The driver slowed the train accordingly, ready to stop at the next signal, the outer home (MSL24) if necessary. However, on observing Home signal MSL24 at Proceed and then MSL26 at Proceed, the driver mistakenly believed that he had a clear run though Marshall. In fact, further Home signals at Marshall, MSL10 and MSL8, were at Stop.

Knowledge

Distant signal MSL22 displayed a Caution indication signifying that any of the signals through Marshall may have been at Stop. This required the driver to operate the train at a speed that would allow the train to be safely brought to a stop at any signal within the Marshall location.

Evidence indicated that the driver did not have a clear understanding of the meaning of Distant signal MSL22 at Caution and its application through this two-position signalling location.

Distraction

The driver reported that as the train approached signal MSL26 he was looking towards the facing points to confirm they were correctly set for the straight route. However, because the MSL26 signal was indicating Proceed for the straight, there was no need for the driver to confirm the points setting. This unnecessary focus on the points setting possibly contributed to the driver’s late observation of signal MSL10 at Stop.

Driver training

Training program for this driver

The driver was in training with V/Line from October 2014 through to 25 May 2015. The scope of this training was based on a gap analysis, with consideration of the driver’s previous experience. Reduced training scope was generally limited to locomotive train handling and mechanical inspections, and there was no reduction in requirements for training and assessment in signalling systems or route knowledge. As a result, there was no identified reduction in training that may have influenced the driver’s knowledge of two-positioning signalling and its application at Marshall.

Training materials

The training materials for two-position signalling reinforced the application of the published rule for a driver’s response to a Distant signal at Caution. The course materials did not expand on the design principles associated with Distant signals nor describe the scenario of a Distant signal at Caution and a Home signal, other than the next, being at Stop.

Assessments

Written assessments focussed on the identification of different types of two-position signals and the associated rules, including the rule when a driver encounters a Distant signal at Caution.

Written assessments also exclusively used photographs of the semaphore Distant signal that is an older configuration. Assessments should reflect the contemporary arrangements and signal configurations that a driver will encounter in the field.

In-field training and route knowledge

The driver’s in-field exposure during his training was predominantly to three-position signalling systems. Conversely, his exposure to two-position signalling on the V/Line network was limited. While the driver’s previous freight experience was with two-position signalling, this was on low speed, low traffic lines where Distant signals were not used.

The driver had successfully completed the assessments and met the minimum criteria for route knowledge on this corridor. However, he had not encountered a sequence of signal indications at Marshall like those presented to train 1240 on the night of the incident. In addition, he had no familiarisation with driving this route at night.

Rule

The 1994 Book of Rules and Operating Procedures described the required driver response to a Distant signal at Caution. The rules referred to the condition of the next signal beyond the Distant signal, but were silent on the possible condition of other Home signals through the location.

Mixture of signalling arrangements

The use of different signalling systems within the same high volume commuter corridor created a local condition that was potentially error provoking. The section between Melbourne and South Geelong incorporated three-position signalling, while South Geelong to Marshall and Waurn Ponds was two-position signalling.

Human performance is such that habitual tasks that are consistently practised in the same fashion and in the same sequence become largely automatic,[10] which for the most part has the positive effect of freeing our conscious attention to manage unexpected or novel events. This can also have the undesirable effect of limiting our capacity to recognise when we need to switch to less common operating modes, leading to errors. The likelihood of these errors increases further when there are insufficient cues (either internal or external) to trigger the switch; often referred to as a ‘strong but wrong’ response.[11]

Thus, in a corridor that predominantly operated with three-position signalling, correct interpretation of a short section of two-position signalling required a driver to override their habitual response and to respond in a different way. The safe operation with this configuration was dependent on a driver’s route knowledge, and on the driver successfully remembering that the interpretation of the two-position signals required a change to their common practice.

Changing traffic profile

When re-opened, the only passenger services through Marshall were the Melbourne-Warrnambool services. Commuter demand led to services through Marshall steadily increasing (Figure 13).

Figure 13: Passenger train services per day to or through Marshall (total)

Figure 13: Passenger train services per day to or through Marshall (total)

Source: Based on data supplied by V/Line Pty Ltd

Marshall was re-established with infrastructure that catered for the relatively small number of passenger services. However, over a ten year period, rail traffic increased significantly (16 in 2005 to 160 services per week in 2015), altering both the operating environment and the risk profile of the location.

To improve the control of traffic through this location, there was scope to upgrade to three-position signalling and potentially introduce measures to mitigate against SPAD events.

__________

  1. Loukopoulos, L.D., Dismukes, R.K. & Barshi, I. (2009). The Multitasking Myth. Handling Complexity in Real-World Operations. Ashgate: Farnham. p90.
  2. Reason, J. (1990). Human Error. Ashgate: Aldershot. p57.

Purpose of safety investigations & publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2016

image_5.png

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-2015-009
Occurrence date 29/05/2015
Location Marshall (Geelong)
State Victoria
Report release date 12/12/2016
Report status Final
Investigation level Systemic
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Rail
Rail occurrence category SPAD (signal passed at danger)
Occurrence class Incident
Highest injury level None

Train details

Train operator V/Line
Train number VL1141
Type of operation Empty Cars
Departure point Waurn Ponds, Vic
Destination Geelong, Vic
Train damage Nil

Stickshaker activation involving a Boeing 717-200, VH-NXM, Brisbane Airport, Queensland, on 27 May 2015

Final report

Report release date: 22/12/2015

What happened

On 27 May 2015, a Cobham Aviation Services Boeing 717-200 aircraft, registered VN-NXM, was being operated from Brisbane to Gladstone, Queensland. The weather in Brisbane was fine and clear, with a light wind from the south. The Captain was the pilot flying (PF) and the First Officer was the pilot monitoring (PM).[1] As part of their preparation for the flight, the crew determined the required flap setting for take-off, and set the flap/slat control handle take-off position detent accordingly (see flap and slat control description). The PM later recalled that, on this occasion, a flap setting of 5.6 degrees was required. Engine start and push-back were normal, and the crew taxied soon after 0900 Eastern Standard Time (EST) for an A3 intersection departure from runway 19 (Figure 1).

Figure 1: Excerpt from Brisbane aerodrome chart showing the location on the domestic apron where the aircraft commenced taxiing and taxiway A3 where the aircraft waited for a clearance to enter the runway

Figure 1: Excerpt from Brisbane aerodrome chart showing the location on the domestic apron where the aircraft commenced taxiing and taxiway A3 where the aircraft waited for a clearance to enter the runway

Source: Airservices Australia, with annotations added by the ATSB

Flap and slat control

The flaps and slats are controlled by a handle on the right side of the centre pedestal (Figure 2). The flap setting for take-off is determined by the crew according to the conditions. The detent position setting thumbwheel is then used to position a detent for the control handle according to that determination, when a flap setting other than 13 or 18 degrees is required. The flap take-off selection indicator window displays the position of this movable detent. Unlike the flaps, the slats are either fully extended or fully retracted – there is no intermediate setting. The position of the flaps and slats is displayed on each pilot’s primary flight display, beneath the airspeed indicator (Figure 3). The flap/slat control handle needs to be lifted to move it forward from the 0/EXT setting (flaps up/slats extended) to the UP/RET setting (flaps up/slats retracted), to retract the slats.

Figure 2: Flap and slat control

Figure 2: Flap and slat control

Source: Boeing, with annotations added by the ATSB

As they taxied to the holding point, the crew completed relevant procedures, which included a requirement to confirm that the flap and slat configuration was set for take-off. The crew then held position on taxiway A3 while they waited for a clearance from air traffic control to enter the runway.

After waiting for several minutes, the crew were instructed by air traffic control to line up on the runway, but with a caveat that they needed to be ready for an immediate departure. The crew were ready, so accepted the clearance to line up, which was soon followed by their take-off clearance. The crew later commented that the wording used by air traffic control in providing the clearance to enter the runway was somewhat unusual, but there was no confusion and they clearly understood the intent. The crew entered the runway and commenced a rolling take-off.[2] The crew recalled that the take-off roll was normal in all respects, with standard communication and checks made as the take-off roll progressed.

Soon after take-off, the stickshaker activated (see stickshaker description). The PF responded immediately by checking the control column slightly forward to reduce the aircraft pitch attitude. The PF noted that the airspeed at that moment was in the expected target range of V2[3] to V2 + 10 kt, but below minimum speed (Vmin)[4] and stickshaker activation speed (VSS)[5] (Figure 3). The PF also noted the airspeed appeared to be stable, with no indication of a speed reducing trend. The crew recalled that the stickshaker remained active for only a very brief period.

Stickshaker
The stickshaker is part of the aircraft stall protection system. Stickshaker activation is based on a number of parameters, including the angle-of-attack of the aircraft and the position of the flaps and slats. When the required conditions are established, an oscillating force shakes the control column rapidly through a small angle to alert the crew that the aircraft may be approaching an aerodynamic stall. If the aircraft continues towards an aerodynamic stall, other levels of warning and protection may be activated, including visual and aural alerts, and a stickpusher.

The airspeed range for activation of the stickshaker is displayed as a ‘red zipper’ on the lower part of the airspeed indicator (Figure 3). VSS marks the top of the red zipper. When the airspeed is below VSS the pitch limit indicator (which provides an indication of the angle-of-attack margin to the activation of the stall warning system) changes colour from cyan to red, to provide an additional alert to the crew. Additionally, the digits (and the outline box surrounding the digits) representing the current airspeed indication turn red if the airspeed falls below VSS.

Figure 3: Primary flight display and description of relevant airspeed indications

Figure 3: Primary flight display and description of relevant airspeed indications

Source: Boeing, with annotations added by the ATSB

Within moments of stickshaker activation, the PM noticed that the flap/slat control handle was set to the UP/RET position (flaps up/slats retract). Upon noticing the position of the handle, the PM immediately called ‘flaps’, and moved the flap/slat control handle to the previously determined take-off setting position.

As the aircraft continued to climb, the PF noticed that the landing gear was still down - the landing gear would normally be raised soon after having established a positive rate of climb (see description of the operator’s normal configuration management procedures). The crew then raised the landing gear and the climb continued. Later during the climb, the flaps were selected up, and soon after, as the aircraft continued to accelerate, the slats were retracted. The flight then continued to Gladstone without further incident.

Following the incident, the crew deduced that the PM must have selected the flap/slat control handle to the UP/RET position soon after take-off, rather than raising the landing gear handle. The crew’s deduction was based upon the configuration of the aircraft before, and immediately after, stickshaker activation. The crew were confident that before take-off procedures had been completed correctly, and that the flaps and slats had been correctly set. The crew also noted that had they commenced the take-off without the flaps and slats set, they would have received an aural warning alerting them accordingly – there was no such aural warning on this occasion.

Operator’s normal configuration management procedures after take-off

Normal procedures require that the landing gear be retracted soon after take-off. The PM observes that a positive rate of climb has been established and that the aircraft has accelerated to V2. Normally, when those conditions are met, the PM calls ‘positive rate’. If the PF is satisfied that the appropriate conditions are met, he/she responds by commanding ‘gear up’. The PM then raises the landing gear control handle to the UP position accordingly, and when the landing gear has retracted, calls ‘gear up’.

Later during the climb, as the aircraft accelerates through the flap retraction speed, the PF calls ‘flaps zero’. The PM checks that the speed is at or above the flap retraction speed, and that the aircraft is accelerating, then moves the flap/slat control handle to the 0/EXT position (flaps up/slats extended). When the flaps have reached the selected position, the PM calls ‘zero set’. Slat retraction follows a similar process at slat retraction speed which is a slightly higher speed than the flap retraction speed. To retract the slats, the PM sets the flap/slat control handle to the UP/RET position (flaps up/ slats retracted) and when the slats have retracted, calls ‘aircraft clean’.

Landing gear control

The landing gear control handle is located on the instrument panel, ahead of and slightly to the left of the pilot in the right seat. The handle is moved in a near vertical motion between the UP and DOWN positions to raise and lower the landing gear.

Flight data analysis

A review of the flight data downloaded following the flight showed that the flaps and slats had been set for take-off. The slats were extended and the flaps had been set to the take-off position determined by the crew. Soon after take-off, at around the time that the landing gear handle would normally be selected to the UP position, the flight data indicates that the flap/slat control handle was moved to the UP/RET position. The stickshaker activated shortly after the flap/slat control handle was moved. At that time, the airspeed was relatively steady at slightly over 160 kt.

The stickshaker was active for about 2 seconds, and stopped at about the time the PF lowered the pitch attitude of the aircraft from about 10 degrees noseup, to about 6.5 degrees noseup. The stickshaker stopped as the aircraft was climbing through about 170 ft, with the airspeed continuing to remain relatively steady at slightly over 160 kt. Although the climb shallowed momentarily immediately following stickshaker activation, a positive rate of climb was maintained throughout.

From about 7 seconds after the flap/slat control handle was selected to the UP/RET position, the handle was moved back to the position that had been set prior to take-off. During that 7 seconds, the flaps had travelled to the fully up position, and the slats had begun to retract. As the handle was reset, the slats moved back to the extended position (before having reached the fully retracted position) and the flaps moved back to the position that had been set prior to take-off. By the time the flaps and slats returned to the take-off configuration, the aircraft was accelerating through about 174 kt, and climbing through about 330 ft.

Flight data showed that after the configuration was reset, the aircraft continued to climb at a relatively steady speed of about 180 kt. As the aircraft climbed through about 700 ft, the landing gear was selected up. As the aircraft climbed through about 3,000 ft, the flaps were selected up as the aircraft accelerated, and soon after, the slats were retracted.

Crew comments

The crew made a number of comments regarding the incident, including:

  • When the stickshaker activated, the PF initially suspected a problem with the aircraft system that senses the position of the slats. Under some conditions, a faulty sensing system may result in a misleading stickshaker activation. The PF had experienced a failure of that nature previously, with similar symptoms.
  • When the stickshaker activated, the PF immediately assessed that the airspeed was appropriate (in the range V2 to V2+10) at that point, and that the pitch attitude was normal. Although there was no immediate explanation for stickshaker activation, the PF lowered the pitch attitude slightly to ensure that the speed was maintained. The PF then heard the PM call ‘flaps’, and became aware that the PM was manipulating the flap/slat control handle (this was at the point that the PM was resetting the configuration, back to the take-off configuration).
  • The PF also commented that with the benefit of hindsight, the thrust setting should have been increased at the onset of the stickshaker. Although that may have been an appropriate response, the limited duration of the stickshaker meant that there was little time to react.
  • The PM could not recall moving the flap/slat handle after take-off, and could not explain why the flap/slat control handle was selected to the UP/RET position when it was. Neither pilot could specifically recall the ‘positive rate’ and ‘gear up’ communication and command that normally takes place soon after take-off, but believe that it was probably carried out.
  • The PM indicated that, even though the flap/slat control handle needs to be lifted in order to move it forward from the 0/EXT position to the UP/RET position, the handle can be moved through the 0/EXT position in a single motion.
  • Both crew commented that, with the exception of brief remarks regarding the flow of air traffic while they waited on taxiway A3, sterile flight deck procedures[6] were being observed.
  • Neither the PF nor PM could recall any specific distractions that may have diverted the attention of the PM at a critical moment during the take-off.
  • For the PM, the day of the incident was the fourth consecutive day of duty. While the PM had slept adequately during the evenings leading up to the incident flight, they reported some tiredness associated with a recent change in personal circumstances and a longer commute to and from work.
  • For the PF, the day of the incident was the third day of a three-day roster, but the schedule was not demanding.
  • After a brief discussion immediately following the event, both pilots were conscious of the need to maintain their focus on the safe and efficient conduct of the flight ahead. They elected not to discuss the incident further during the flight until they were safely on the ground at their destination. Following the flight, they discussed the incident and submitted a report.

ATSB comment

Available evidence suggests that the PM inadvertently selected the flap/slat handle to the UP/RET position, instead of selecting the landing gear handle to the UP position. While the reasons are unclear, the most likely explanation resides in an understanding of human error types. The SKYbrary website includes information about human errors that may have relevance to this occurrence, particularly with respect slips and lapses – referred to collectively as execution errors (Human Error Types). The SKYbrary website also includes an article dealing with the relationship between human performance and level of arousal (Level of Arousal). The article illustrates that over-arousal can lead to a degradation in performance, but importantly, under-arousal can have a similar influence.

In a similar incident in 2003 (ATSB Report 200302037), the co-pilot of a Boeing 717-200 repositioned the flap/slat handle soon after take-off, instead of the landing gear handle. In response to that incident, the operator added the following caution to the procedures for flap/slat retraction after landing:

When retracting flaps/slats to UP/RET, pause at the UP/EXT position until the flaps indicate UP on the PFD prior to retracting the slats. Never move the flap/slat handle to UP/RET in one motion.

The ATSB report states that:

The purpose of the change was to separate the retraction of the flaps and slats into two distinct actions, in an attempt to prevent the retraction of the flaps and slats becoming `learned' as a single continuous action.

In another incident, the flaps of a British Aerospace 146-300 began to retract soon after take-off, just before the aircraft reached 100 ft above ground level. Flap retraction began at about the time the call to raise the landing gear would have normally been made (ATSB Investigation Report 9704041). Although there were numerous factors surrounding the incident, the report commented that ‘On balance … the likelihood rests that the co-pilot inadvertently selected the flaps up instead of the landing gear.’

More information about stall warnings in high-capacity aircraft is available in ATSB research report AR-2012-172 (Stall warnings in high-capacity aircraft: The Australian context 2008 to 2012). The report outlines the results of a review of 245 stall warnings and stall warning system events over a 5-year period from 2008 to 2013. Of those 245 events, 163 were stickshaker activations.

Safety message

This incident highlights the susceptibility of pilots to execution errors such as slips and lapses, irrespective of knowledge and experience. Pilots are encouraged to reflect on the circumstances surrounding this incident to help build their own awareness of human factors issues associated with operating complex equipment in a highly dynamic environment.

Aviation Short Investigations Bulletin - Issue 45

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2015

image_5.png

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. PF and PM are procedurally assigned roles with specifically assigned duties at specific stages of flight. The PF does most of the flying, except in defined circumstances. The PM carries out support duties, and monitors the actions of the PF and the flight path of the aircraft.
  2. A rolling take-off is a take-off that commences when the aircraft enters the runway and proceeds with the take-off without stopping in the lined-up position.
  3. V2 is often referred to as the take-off safety speed. It is the minimum speed at which a transport category aircraft complies with those handling criteria associated with climb, following an engine failure. V2 is normally obtained by factoring other critical speeds, to provide a safe margin with respect to aircraft controllability.
  4. Vmin is the minimum manoeuvring airspeed in the existing aircraft configuration. Vmin provides a specific margin above the stickshaker activation airspeed and aerodynamic stall airspeed.
  5. Vss represents the airspeed at which the stickshaker activates to alert the crew to the possibility of an approaching aerodynamic stall.
  6. Sterile flight deck procedures relate to a requirement for pilots to refrain from non-essential conversations and activities during critical phases of flight.

 

Occurrence summary

Investigation number AO-2015-056
Occurrence date 27/05/2015
Location Brisbane Airport
State Queensland
Report release date 22/12/2015
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Incorrect configuration
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 717-200
Registration VH-NXM
Serial number 55094
Aircraft operator Cobham Aviation Services
Sector Jet
Operation type Air Transport High Capacity
Damage Nil

Signals Passed at Danger by passenger train TD3050, at Upwey and Upper Ferntree Gully, Victoria, on 12 April 2015

Final report

Safety summary

What happened

On 12 April 2015, just prior to the 1542 Belgrave-to-Melbourne service arriving at Upwey station, the signal control panel located at Upper Ferntree Gully station lost functionality. As a result, the signaller, no longer had control or indication of signals and interlocking at Upwey.

To continue train operations through the area, procedural safeworking was instituted under the control of the signaller at Upper Ferntree Gully. By this time the Belgrave-to-Melbourne service was stopped at Upwey with the Departure signal at Stop. Having been advised of the signalling system failure, the driver of this service contacted the signaller at Upper Ferntree Gully for further instructions. A short time later, at about 1551, the train departed Upwey and proceeded to Upper Ferntree Gully without authorisation.

What the ATSB found

The ATSB found that the train passed both the Upwey Home Departure and the Upper Ferntree Gully Home Arrival signals at Stop without authority. The departure from Upwey was possibly influenced by the driver’s anxiety at having to operate the points machine a short distance beyond Upwey.

The ATSB also found that there was a missed opportunity to contact the train after it was detected as having departed Upwey unauthorised.

What's been done as a result

MTM has reviewed training provided to drivers in the operation of Dual Control Points Machines. MTM is also considering [1] the incorporation of SPAD alarms at this location, and [2] modifying the communications network to capture all safeworking communications at Upper Ferntree Gully.

Safety message

An extra degree of responsibility and situational awareness is demanded of staff under conditions of degraded signalling and procedural safeworking.

Findings

From the evidence available, the following findings are made with respect to the double-SPAD incident at Upwey and Upper Ferntree Gully, Victoria, on 12 April 2015. These findings should not be read as apportioning blame or liability to any particular organisation or individual.

Contributing factors

The signal control panel at Upper Ferntree Gully failed, requiring the introduction of procedural safeworking that resulted in an increased exposure to human error

The train passed the Upwey Home Departure signal at Stop without authorisation

The train passed the Upper Ferntree Gully Home Arrival signal at Stop without authorisation.

Other factors that increased risk

  • Although train TD3050 was identified as having made an unauthorised departure from Upwey, there was no follow-up action to contact the train.

Safety issues and actions

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.

Metro Trains Melbourne advised that as a result of this occurrence they:

  • Have reviewed training provided to drivers in the operation of Dual Control Points Machines
  • Will consider a system modification to capture all safeworking communications at Upper Ferntree Gully
  • Will add the incorporation of SPAD alarms into asset management plans for future upgrading of signalling at this location.

The occurrence

The 1542 service (TD3050) from Belgrave to Melbourne departed Belgrave on time. The train was a six-car X’Trapolis Electric Multiple Unit.

The Belgrave line (Figure 1) is part of the Melbourne metropolitan network managed by Metro Trains Melbourne (MTM). Between Belgrave and Ferntree Gully trains operate on a single bi-directional track, excepting at Upper Ferntree Gully and Upwey, where the line splits to pass either side of island platforms. These stations therefore provide the crossing points for trains travelling in opposing directions.

Figure 1: MTM network map (part)

MTM network map

Source: Metro Trains Melbourne – annotated by Chief Investigator, Transport Safety (Vic)

Train TD3050 arrived at platform 1 at Upwey Railway station (Figure 2) to cross the Belgrave-bound service that had arrived at about the same time and was at platform 2. Just prior to the arrival of TD3050, the signal control panel at Upper Ferntree Gully failed. As a result the signaller based at Upper Ferntree Gully (UFG) no longer had control of signals and points at Upwey and could not determine the location of trains in the vicinity of Upwey.

Figure 2: Upwey track layout with key signals and points marked

Upwey track layout with key signals and points marked

Source: Chief Investigator, Transport Safety (Vic)

The signaller at Upper Ferntree Gully reported the panel failure to Metrol, the control centre for train operations on Melbourne's suburban rail network. In response to this call, Metrol contacted the driver of train TD3050 by radio to advise of the failed signal control panel and to ascertain the train’s location. The driver confirmed his location at Upwey Platform 1, and was informed by Metrol that he would need to contact the signaller at Upper Ferntree Gully to obtain authority to depart from Upwey.

The driver of 3050 then called the signaller at Upper Ferntree Gully by mobile phone to obtain instructions. Conversations between the signaller and the driver of TD3050 were not recorded. The signaller advised the driver of the panel failure and that he did not have track detection. The signaller also advised the driver that he (the driver) would need to operate the points in front of him (№ 41 points).

Unable to see the status of № 41 points from the Upwey platform, the driver boarded his train and ran forward towards the points. By this action, he passed the Home Departure signal at Upwey at Stop. This was the first Signal Passed at Danger (SPAD[1]) event of this incident. Passing this Home signal at Stop, led to activation of the trip lever and a resulting enforced brake application which brought the train to a stand (see p5).

After the trip mechanism was reset by the driver, the train continued on slowly towards № 41 points. Approaching № 41 points the driver observed they were correctly set for his passage and continued on. As a result, he did not stop and lock the points in the hand position. The driver then continued on towards Upper Ferntree Gully.

Train 3050 next encountered Automatic signal[2] № 38 that was displaying a Stop indication. Particular rules apply to Automatic signals (see p4) that permit them to be passed at Stop without authority from a signaller or train controller. After passing the signal at stop and resetting from the resulting enforced brake application, the train continued on towards Upper Ferntree Gully.

About six minutes into the train’s passage between Upwey and Upper Ferntree Gully, the signaller noticed (on CCTV) that train 3050 was no longer visible at the Upwey platform. The signaller called Metrol to advise of this, and was informed by the train controller that they would contact the driver of the other train at Upwey (TD3639) for confirmation. There were no further calls made to clarify the position of TD3050.

Train 3050 subsequently arrived at Home Arrival signal № 36 at Upper Ferntree Gully (Figure 3). Observing that the points appeared correctly set, the driver proceeded past this Home signal that was also at Stop, again experiencing a mandatory stop initiated by the mechanical trip system. This was the second SPAD event of this incident.

Figure 3: Upper Ferntree Gully track layout with key signals and points marked

Upper Ferntree Gully track layout with key signals and points marked

Source: Chief Investigator, Transport Safety (Vic)

The train then recommenced its passage and passed through №s 35 and 25 points before arriving at Upper Ferntree Gully platform 1. The signaller became aware of the train as it arrived and instructed the driver not to move his train. The passage of train 3050 from Upwey to Upper Ferntree Gully had taken about 10 minutes. There was no damage to track infrastructure or the train and there were no injuries.

As a consequence of the signal panel failure, Metrol and the Station Master at Upper Ferntree Gully had agreed that Belgrave-bound trains would terminate at Upper Ferntree Gully. At the time that train TD3050 was arriving into Upper Ferntree Gully, a Belgrave-bound service was also approaching the adjacent platform.

__________

  1. An industry term referring to the act of a train passing a signal that is displaying a Stop indication without authorisation.
  2. An ‘Automatic’ signal is controlled by the movement of trains alone and is not directly controlled by a signaller/controller.

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • Metro Trains Melbourne.

References

  • MTM Weekly Operational Notice № 13/2015
  • National Standard for Health Assessment of Rail Safety Workers
  • The Book of Rules and Operating Procedures (1994) – PTC.

Submissions

Under Part 4, Division 2 (Investigation Reports), Section 26 of the Transport Safety Investigation Act 2003 (the Act), the Australian Transport Safety Bureau (ATSB) may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. Section 26 (1) (a) of the Act 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 driver of the train, the Station Master at Upper Ferntree Gully, Metro Trains Melbourne, the Office of the National Rail Safety Regulator and Public Transport Victoria.

Submissions were received from Metro Trains Melbourne, the Office of The National Rail Safety Regulator, and Public Transport Victoria. The submissions were reviewed and where considered appropriate, the text of the report was amended accordingly.

Context

The train driver

The driver was qualified for the operation of this train on this route and was medically fit for duty. He was based at the Carrum depot and had qualified to drive suburban trains in February 2007. His most recent performance audit had been undertaken in January 2015. This incident was the driver’s first SPAD infringement.

Following the incident, testing of the driver returned a zero blood alcohol result and nil presence of drugs.

Track infrastructure

Upwey to Upper Ferntree Gully

From departure at Upwey railway station to arrival at the platform at Upper Ferntree Gully was about 2.4 km on a predominantly 1:30 downgrade. Between the mainline points at the two stations (№s 41 and 35 points) the line was single-track for a distance of approximately 2.05 km. Automatic signal № 38 is located midway between the stations.

Upwey

Upwey is an unattended crossing station, about 40 km from Flinders Street Station. Home Departure Signal № 42 is at the Melbourne end of Platform 1 (Figure 4).

Figure 4: Upwey railway station looking towards Upper Ferntree Gully and signal № 42

Upwey railway station looking towards Upper Ferntree Gully and signal № 42

Source: Chief Investigator, Transport Safety (Vic)

About 160 metres from the Melbourne end of the Upwey island platform, № 41 points connects the two platform tracks to the single line extending towards Upper Ferntree Gully.

№ 41 points are controlled by a Dual Control Point Machine. They can be operated in ‘Motor’ (remote operation) or ‘Hand’ (manual operation) modes. This enables remote operation of the points by a signaller or hand operation in the case of system failure. In the case of system failure, all points are set to the Hand mode prior to being traversed to ensure the points cannot inadvertently operate while a train is passing across them. In addition, when set to ‘Hand’ mode, the Home signals protecting the points are held at Stop.

The Dual Control Point Machine has two levers – the Selector lever and the Hand Throw lever. The Selector lever is the shorter of the two. The normal position for the Selector lever is in the ‘Motor’ position (Figure 5 right-hand photo). To place the machine into ‘Hand’ mode the lever is rotated clockwise by 180 degrees (Figure 5 left-hand photo). With the Selector lever in this position, the Hand Throw lever can then be used to manually move the points to their required position. Figure 5 does not depict the actual point machine at the № 41 points at Upwey.

Figure 5: Dual Control Point Machine. The Selector lever is shown in the ‘Motor’ position (right-hand photo) and ‘Hand’ position (left-hand photo)

rid29-figure-xx-point-machine.jpg

Source: Metro Trains Melbourne

Automatic signal № 38

An intermediate Automatic signal was provided between Upwey and Upper Ferntree Gully. Automatic signal № 38 provided advance warning and indication of the status of the Home arrival signal № 36 at Upper Ferntree Gully.

An Automatic signal is not directly controlled by a signaller or train controller but by the passage of trains detected by track circuits. As part of a permissive signalling system, an Automatic signal at Stop is allowed to be passed by a train under conditions specified by a Rule.

At the time of the incident, a trial existed[3] to reinforce the process for passing Automatic signals at Stop. This trial involved train drivers who encountered an Automatic signal at Stop making use of a voice mail facility to receive an automated message conveying explicit instructions and to then provide certain identifying information. The driver of TD3050 did not follow this process.

Upper Ferntree Gully

Upper Ferntree Gully is an attended crossing station about 36 km from Flinders Street. Home Arrival Signal № 36 (Figure 6) is located about 220 metres prior to the platform.

Figure 6: Home arrival signal № 36 at Upper Ferntree Gully

Home arrival signal № 36 at Upper Ferntree Gully

Source: Metro Trains Melbourne

Trackage at Upper Ferntree Gully is more complex with several sidings either side of the mainline tracks (Figure 3). For mainline traffic, trains arriving at Upper Ferntree Gully from Upwey are typically directed to platform 1 by way of №s 35 and 25 points.

Train stops at signals

On the metropolitan network, Home and Automatic signals are fitted with Train Stops (Figure 7). This was the case at signal №s 42 (Upwey Departure), 38 (Automatic) and 36 (Upper Ferntree Gully Arrival).

Figure 7: Automatic train stop (left) and trip lever on suburban trains (right)

Automatic train stop (left) and trip lever on suburban trains (right)

Source: Chief Investigator, Transport Safety (Victoria)

The purpose of this device is to bring a train to a stand when the train passes a signal that is at Stop. When a signal is at Stop, the trip arm of the unit located beside the track is raised. This strikes the trip valve lever that is fitted on suburban trains causing an emergency brake application and the train to come to a stand. Before a train can proceed after being ‘tripped’, its trip mechanism has to be reset by the driver.

In this incident, the train brake was ‘tripped’ when passing signals №s 42, 38 and 36. This stopped the train in each case, and the driver manually reset the trip, enabling the train to recommence its journey.

Traffic control on the metropolitan network

Metrol

Metrol is the central control centre for the Melbourne suburban rail network. The centre’s train control function covers the whole suburban area, while its control of points and signalling covers a limited area within central Melbourne and one (recently modernised) outer suburban area.

Outside the centrally-controlled areas, train movements are controlled by signallers located either in dedicated signal-boxes or operating signal control panels at suburban railway stations. These signallers are under the direction of the Metrol controllers. Upper Ferntree Gully was such a location.

Local area signalling from Upper Ferntree Gully Station

Safeworking system

The safeworking system used at this location was Automatic Track & Control (ATC). In this system, authority for a train to enter a section of track is provided by signals located at each end of the section. In single-line operations, the signals at each end of a track section are arranged such that once a train is in the section, an opposing train cannot be signalled to enter.

Signal control panel

Upper Ferntree Gully, was staffed by a signaller for the control of the single-line section between Ferntree Gully and the line’s terminus at Belgrave. The station was equipped with a signal control panel (Figure 8) that provided information of signal and points status and train position.

MTM maintenance attended to the loss of panel functionality. The inspection identified that the panel fault was the result of a processing failure within the Railmaster compact telemetry unit. This is an interface component between the signal control panel and field equipment. The Railmaster unit had failed and required a hardware reboot. The equipment that had caused the signal control panel outage was reset after about an hour. However, a secondary and separate fault with a set of points resulted in a delay in re-establishing the signalling system.

Figure 8: Signal control panel, Upper Ferntree Gully

Signal control panel, Upper Ferntree Gully

Source: VicSig – Chris Jordan

The Signaller at Upper Ferntree Gully

The signaller (who was also the Station Master) was medically fit[4] and appropriately qualified for his duty, and had been last audited at Upper Ferntree Gully (with no non-conformances) a month prior to the incident.

The station is usually staffed by two. However, on this day the rostered signaller had been sent home due to fatigue. As a result, the Station Master was also performing the role of the signaller. His duties included operating the signal control panel and dealing with passenger ticketing and enquiries. Around the time that the signal control panel failed, public inquiries were low and did not interfere with his response to the panel failure.

This was the signaller’s fifth consecutive 8-hour dayshift, following a five-day break off duty. There was no indication that fatigue affected the performance of the signaller.

Procedural safeworking and Caution Orders

Procedural safeworking on the MTM network, is instituted when there is a loss of signalling system and interlocking control. It permits the ongoing operation of the network, albeit at a reduced capacity.

The safeworking of trains was governed by the Book of Rules and Operating Procedures (1994). On the metropolitan network, implementation of these Rules was supported by procedures developed by the network manager, MTM.

Procedural safeworking requires coordination between the signaller (or train controller) and the train driver in order for signals to be safely passed and for points to be safely traversed. Home signals control arrival and departure movements at stations, and protect points and other interlocking.

The instrument of authorisation to pass Home signals displaying a Stop indication is called a Caution Order. This is an instrument used by a train controller or signaller to give a train driver authority to pass a signal at Stop in accordance with prescribed measures. The issuing of a Caution Order is a formally documented process, although its application can take various forms.

Procedures for departing Upwey

Upwey is an unattended station. Under circumstances of signalling system failure[5] at unattended stations, an ATC System Caution Order is the instrument used to permit a train to pass a Home Departure signal at Stop.

The process for issuing an ATC System Caution Order included:

  • On the direction of the train controller or signaller, the driver placing protected points in the ‘Hand’ mode and ensuring they were correctly set and secured for the train’s movement
  • The driver then contacting the signaller and confirming the points had been correctly secured
  • Once satisfied that points were secured and cognisant of other traffic, the signaller dictating the Caution Order to the driver, who would record the details of the order on a prescribed form
  • On completion of the prescribed form, the train would have authority to proceed past the signal at Stop.
Procedures for arrival at Upper Ferntree Gully

At an attended station such as Upper Ferntree Gully, the applicable instrument to use for a train to pass a Home signal at Stop is the Signaller’s Caution Order. This is a paper document that is passed from signaller to train driver. Before issuing such an authority, the responsibility for ensuring that any points are safe to traverse rests with the signaller.

Therefore at Upper Ferntree Gully station, in the case that the signaller was to issue a Caution Order, №s 35 and 25 points would be secured by the signaller, before a train was given the written authority to pass signal № 36 and proceed to Platform 1.

Voice communications

Drivers operating trains on the Belgrave line could communicate with the Upper Ferntree Gully signaller on the Digital Train Radio System (DTRS), which was recorded.

However, in this instance the driver contacted the signaller using his MTM-issued mobile phone – a mode of communication that is not recorded unless received on phones that are recorded, such as at Metrol.

The non-recording of safeworking communications leaves a significant gap in the capacity to review or resolve communications in the case of investigation or procedural auditing.

__________

  1. Trial procedure running from 5 April 2015 to 21 June 2015, per Weekly Operational Notice № 13/2015.
  2. Category 2 Medical Assessment in accordance with the National Standard for Health Assessment of Rail Safety Workers.
  3. Under failure conditions of the centralised control of points and signals, those points and signals normally subject to that control are also considered to have failed.

Safety analysis

Signal control panel

The signal control panel at Upper Ferntree Gully lost functionality as a result of a processing failure within the Railmaster compact telemetry unit.

Due to this failure, the signaller lost control over and information on the signals and points at Upwey. As a result, safeworking reverted to a back-up procedural system. This required the use of Caution Orders as the authority for trains to pass Home signals at Stop. This substitute process introduced a greater procedural burden on operational staff and an increased exposure to human error.

Departure from Upwey

The procedures for passing Home signals following signalling system failure are well established formal processes. At Upwey, the correct authority to proceed past the Home Departure signal that was at Stop was a dictated ATC System Caution Order. The train proceeded without this process being followed and therefore without authority. In addition, the train then proceeded over points № 41 without them first being secured by hand and the signaller being advised.

Having instructed the driver to check the 41 points at Upwey, the signaller’s expectation would have been that the driver would proceed on foot to the points, confirm their setting, and secure them in Hand mode. The driver would then return to his train to contact the signaller to advise accordingly and to have the ATC System Caution Order dictated by the signaller and recorded by the driver.

There are a number of factors that may have influenced the driver’s behaviour that led to these errors (unauthorised passing of signals at Stop). These include:

  • A lack of understanding of the applicable safeworking procedures
  • Distraction
  • A misunderstanding of instructions from the train controller or signaller
  • Expectation of a clear track ahead
  • Infrequent operation on this line
  • Fatigue.

Lack of understanding of safeworking procedures

Safeworking rules, including the application of Caution Orders, are a fundamental knowledge-based competency for drivers of trains. The driver’s record shows the completion of required training in safeworking procedures and also subsequent supervisory auditing. Due to the infrequency of use, the driver’s experience with using alternate safeworking in practice may have been limited.

The driver had no record of any SPAD incident during his 8-year career, and therefore no history of this type of error. There was no evidence to suggest a fundamental misunderstanding of rules and procedures. Rather, the response of the driver following the incident and realisation of his error suggests a possible lapse of awareness.

Distraction

The train driver was anxious about having to operate the set of points (№ 41) that he had been requested by the signaller to secure. The driver also reported having felt a sense of relief at seeing that the points were set for his movement. This was probably because it was some time since he had covered Dual Control Point Machines in his initial (2007) and refresher (2010) training The driver also suggested that he had never hand-operated such a machine in the field. Nonetheless, the required procedure was straightforward and assistance was available from the train controller or signaller if required.

Despite the ease of the task, it is apparent that the driver was apprehensive about operating the points. It is possible that this apprehension led to the driver forgetting the requirements to first check the points and then obtain a Caution Order before departing the train from Upwey.

Misunderstanding of communications with train controller or signaller

The driver’s communication with the Metrol train controller was straightforward and there is no indication that the controller’s instructions were misunderstood by the driver. The driver called the signaller at Upper Ferntree Gully as instructed.

The communication between the driver and the signaller was not recorded and so its precise nature is not known. Combined with the driver’s sense of anxiety at operating the points, it is possible that the signaller’s instruction that the points be checked prior to receipt of authority was construed as permission to pass the Home Departure signal. However, this would have been contrary to procedure.

The driver was required to then report the state of the points to the signaller. The possibility of a momentary lapse of awareness does not fully explain why, having observed the points, he then continued without reporting their status.

Expectation

The driver of train № 3050 was aware that the opposing Belgrave-bound train was already at Upwey Platform 2. He had been informed by Metrol that there were signalling problems at Upwey and that once the opposing train had arrived he should contact the signaller at Upper Ferntree Gully to obtain ‘authority to move past [the Home Departure signal]’. He would therefore have expected that the single line to Upper Ferntree Gully was clear and that there was no impediment to obtaining authority to proceed through the section.

Infrequent operation on this line

Carrum-based drivers mostly operate over the Frankston, Craigieburn, Hurstbridge, and Sunbury lines. To maintain familiarity, they are rostered to operate over the Belgrave line twice in each 16-week cycle. Therefore, the driver was not a regular operator on this line. This driver had also not been audited on the Belgrave line in the last three years.

While less familiarity with a route can contribute to apprehension or errors, it is unlikely that this factor contributed to the errors in this instance.

Fatigue

The driver had commenced his shift at 1009 and at the time the incident occurred had been on duty for about 5 hours and 30 minutes. Based upon the driver’s rostered work schedule, time-of-day, time-on-task, and the nature of the errors observed, it is considered unlikely that the driver’s performance was fatigue-impaired at the time of the SPAD events.

Arrival at Upper Ferntree Gully

At Upper Ferntree Gully the correct authority to proceed past the Home Arrival signal that was at Stop was a Signaller’s Caution Order. The train entered the station without this authority.

In proceeding into the station, the driver also operated the train across two sets of points without them first having been secured against the possibility of movement while being traversed.

There are no additional factors or events that may have influenced the driver’s behaviour in this second SPAD event. Being already in the section and in the belief that there were no opposing trains, the driver probably believed it was safe to proceed to the platform at Upper Ferntree Gully.

Missed opportunity to contact unauthorised train

About six minutes after train TD3050 departed Upwey, the signaller at Upper Ferntree Gully noticed on CCTV vision that the platform was vacant. The signaller conveyed this observation to the Metrol train controller. However, there was no further action-by either the signaller or the train controller-to contact the train. MTM SPAD risk management procedures specify that following a SPAD, contact must be made with the driver of a train and the train stopped.

After its detected departure from Upwey, about four minutes passed before the train arrived at Upper Ferntree Gully. There was an opportunity to stop the train during this period.

Purpose of safety investigations & publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2016

image_5.png

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-2015-008
Occurrence date 12/04/2015
Location Upwey and Upper Ferntree Gully
State Victoria
Report release date 21/04/2016
Report status Final
Investigation level Defined
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Rail
Rail occurrence category SPAD (signal passed at danger)
Occurrence class Incident
Highest injury level None

Train details

Train operator Metro Trains Melbourne
Train number 3050
Type of operation Passenger
Departure point Belgrave, Vic
Destination Flinders Street, Melbourne
Train damage Nil

Loss of separation and radar vectors below minimum vectoring altitude involving Saab 340B, VH-OLL, Boeing 737, VH-YVC, and Airbus A320, VH-VNH near Adelaide, South Australia on 18 May 2015

Discontinued

Discontinuation notice

Section 21 (2) of the Transport Safety Investigation Act 2003 (TSI Act) empowers the Australian Transport Safety Bureau (ATSB) to discontinue an investigation into a transport safety matter at any time. Section 21 (3) of the TSI Act requires the ATSB to publish a statement setting out the reasons for discontinuing an investigation.

On 18 May 2015, the ATSB commenced an investigation into a number of loss of separation occurrences and radar vectors issued to flight crew when an aircraft was below the minimum vector altitude on 18 May 2015, near Adelaide Airport, South Australia involving:

  • a SAAB Aircraft Co 340B (S340), registered VH‑OLL (OLL), conducting a low capacity regular public transport flight from Mount Gambier, South Australia
  • an Airbus A320-232 (A320), registered VH‑VNH (VNH), conducting a high capacity regular public transport flight from Melbourne, Victoria
  • a Boeing 737‑8FE (B737), registered VH‑YVC (YVC), conducting a high capacity regular public transport flight from Melbourne
  • a Boeing 737 (B737) conducting a high capacity regular public transport flight from Sydney, New South Wales.

The aircraft were under the jurisdiction of an Airservices Australia (Airservices) Check and Standardisation Supervisor (workplace assessor), conducting a final assessment on a trainee Approach East controller (trainee). During the approach sequence there were two loss of separation occurrences, then OLL was below the minimum vector altitude while on a vector on one occasion, and OLL was not confirmed above the minimum vector altitude while being vectored on another.

An Airservices investigation into the occurrences found that the Adelaide Tower controller did not have sufficient understanding of the minimum vector altitude, that the intervention by the workplace assessor was not effective and that the controllers involved in a transfer of separation responsibility did not have a shared understanding, as there was no standard phraseology. The investigation report identified the following safety issues:

  • Compromised separation training for controllers at Adelaide Tower did not incorporate scenarios where aircraft were below the minimum vector altitued at night.
  • The updated Intervention Techniques and Prompting initial qualification training was not provided to existing on-the-job training instructors or workplace assessors. Additionally, the relevent refresher training module had not been updated.
  • There was no defined explicit requirements, including the required phraseology, for coordinating the transfer of separation responsibility between controllers.

Airservices subsequently advised that each of the safety issues had been addressed and all related safety actions had been completed.

The ATSB reviewed the Airservices report, safety issues and safety actions. Based on this review, the ATSB considered it was very unlikely that further investigation would identify any systemic safety issues. Consequently, the ATSB has discontinued this investigation.

 

Occurrence summary

Investigation number AO-2015-054
Occurrence date 18/05/2015
Location near Adelaide Airport
State South Australia
Report release date 31/01/2019
Report status Discontinued
Investigation level Systemic
Investigation type Occurrence Investigation
Investigation status Discontinued
Mode of transport Aviation
Aviation occurrence category Flight below minimum altitude
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Saab Aircraft Co.
Model 340B
Registration VH-OLL
Serial number 340B-175
Aircraft operator Regional Express
Sector Turboprop
Operation type Air Transport Low Capacity
Departure point Mount Gambier, SA
Destination Adelaide, SA
Damage Nil

Collision with terrain involving Robinson R22, VH-HRW, 63 km north-north-east of Mitchell, Queensland, on 28 May 2015

Final report

What happened

On 28 May 2015, the pilot of a Robinson 22 helicopter, registered VH-HRW, was engaged in aerial mustering operations about 63 km north-north-east of Mitchell, Queensland. Late in the afternoon the helicopter’s tail rotor struck the branch of a 7 m-high dead and defoliated tree, the pilot lost control of the helicopter and it collided with terrain. The helicopter was destroyed and the pilot, the sole occupant, was fatally injured.

What the ATSB found

The ATSB found that the pilot was appropriately qualified and flying due west in a serviceable helicopter at low level. The sun was to the north-west and about 13°–15° above the horizon at that time. The helicopter’s tail rotor collided with the upper branch of an isolated tree. That collision separated a portion of the tail rotor blades, leading to the remainder of the tail rotor and the helicopter’s horizontal and vertical stabilisers and tail rotor gearbox also separating. The pilot could not control the helicopter and it collided with terrain.

Given the conditions, it is likely that sun glare and the darkened backdrop of a tree-lined dry creek bed affected the pilot’s vision and perception, and therefore ability to identify the isolated tree. Despite the pilot wearing a helmet that was fitted with sun visors, the ATSB could not determine whether the visors were lowered at the time. In any event, it is likely that the pilot did not see the tree, or misjudged its height and/or its distance from the approaching helicopter.

The ATSB did not identify any pre-existing mechanical defects and established that, at the time of the accident, the helicopter was likely serviceable. The helicopter was fitted with a three-point safety harness and bladder-type fuel tanks. These tanks decrease the risk of a post-impact, fuel-fed fire. Despite these additional safety features, and the safety benefits possible from the pilot wearing a helmet, the accident was not survivable due to impact forces. A number of unrestrained items in the cabin increased the risk of injury as a result of those forces.

Safety message

Low-level aerial mustering operations are an inherently high-risk activity. When conducting this type of operation, pilots need to consider the environmental conditions as part of their flight planning and operational risk assessment. The ATSB and the Civil Aviation Safety Authority have released a number of publications illustrating the risks associated with this type of operation that provide guidance and strategies for mitigating those risks.

Sources and submissions

Sources of information

The sources of information during the investigation included the:

  • witness reports from a number of participants in the muster that day
  • results and findings of the ATSB’s on-site investigation.

References

Aviation Research and Analysis report – B2004/0292, Robinson R22 helicopter aerial mustering usage investigation, ATSB Transport Safety Investigation report.

Civil Aviation Safety Authority (2015). Sector Risk Profile for the aerial mustering sector.

Gibb R, Gray R, and Scharff L (2010), Aviation Visual Perception, Ashgate Publishing Limited: Surrey England, pp.72-74.

Nakagawara V, Wood K, and Montgomery R (2003), Natural Sunlight and its Association to Aviation Accidents: Frequency and Prevention, Civil Aerospace Medical Institute, Federal Aviation Administration.

Submissions

Under Part 4, Division 2 (Investigation Reports), Section 26 of the Transport Safety Investigation Act 2003 (the Act), the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. Section 26 (1) (a) of the Act 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 Civil Aviation Safety Authority, the maintenance provider and a number of the witnesses.

No submissions were received from those parties.

The occurrence

On 28 May 2015, the pilot of a Robinson 22 helicopter, registered VH-HRW, was carrying out aerial mustering operations on a property about 63 km north-north-east of Mitchell, Queensland (Figure 1). One of the property owners reported that the pilot had previously conducted mustering activities at the property.

The pilot flew VH-HRW to the mustering area from his home base earlier that day. This entailed a flight of about 20 minutes. The majority of the mustering activity followed between 1032 and 1329 Eastern Standard Time[1].

One of the property owners reported that the pilot then had a long break and a meal with the property owners and a station hand. The afternoon’s activities were discussed during the meal. The plan for those activities included that, while flying back to his home base, the pilot would look for stray cattle and muster them towards a number of stationary vehicles. These vehicles were to be stationed to the west of the afternoon’s operating area.

After several minutes, the station hand unsuccessfully attempted to contact the pilot by ultra high frequency radio. The station hand then drove their vehicle in the direction that the helicopter had departed. After several more minutes, the station hand located the helicopter wreckage. An attempt was made to revive the pilot but without success.

Figure 1: Image showing the helicopter’s track (in white) during the morning’s mustering. This track was derived from data downloaded from the helicopter’s on-board Global Positioning System receiver. The location of the helicopter wreckage is shown (in blue) reference the townships of Roma and Mitchell

Figure 1: Image showing the helicopter’s track (in white) during the morning’s mustering. This track was derived from data downloaded from the helicopter’s on-board Global Positioning System receiver.

Source: Google earth, modified by the ATSB

__________

  1. Eastern Standard Time (EST) was Coordinated Universal Time (UTC) +10 hours.

Findings

From the evidence available, the following findings are made with respect to the collision with terrain involving Robinson R22 helicopter, registered VH-HRW, which occurred about 63 km north-north-east of Mitchell, Queensland on 28 May 2015. These findings should not be read as apportioning blame or liability to any particular organisation or individual.

Contributing factors

  • Given the low-level flight into the afternoon sun, it was likely that due to sun glare, the pilot did not see or misjudged the height and/or distance to the dead and defoliated tree before the tree strike.
  • As a result of the tree strike, the tail rotor, combined vertical and horizontal stabilisers and tail rotor gearbox separated from the tail boom, rendering the helicopter uncontrollable and resulting in the collision with terrain.

Other factors that increased risk

  • Unrestrained items in the helicopter’s cabin increased the risk of control interference during normal flight and injury to the pilot during the accident sequence.

Other findings

  • The helicopter was modified to include bladder-type fuel tanks, which did not puncture. This prevented fuel escaping after the impact and reduced the risk of a post-impact, fuel-fed fire.

Safety analysis

Introduction

This analysis will examine the factors in the development of an accident involving a qualified pilot, who was carrying out mustering operations in an airworthy helicopter, in good weather. These factors include:

  • the position and elevation of the sun and its impact on the pilot’s ability to see and react to an isolated, dead and defoliated tree (tree) along the pilot’s track
  • the loss of a number of helicopter components as a result of the helicopter striking that tree and the resulting effect on the pilot’s ability to control the helicopter
  • a number of survivability considerations.

Development of the accident

Examination of the wreckage and accident site found that the helicopter struck an upper branch of an isolated, 7 m-high tree about 100 m to the east of a tree-lined dry creek bed. This resulted in the tail rotor blades separating from the tail rotor assembly, followed by the vertical and horizontal stabilisers and structure, then the tail rotor gearbox. Control of the helicopter was no longer possible and the helicopter collided with terrain coming to rest on the right side.

The main wreckage was located about 50 m west of the tree. This was consistent with the helicopter being in forward flight, rather than in the hover, and indicated the helicopter’s westerly direction of travel preceding the tree strike.

The pilot’s reported departure from the road coincided at the commencement of the 1600 radio news. The time taken for the station hand to attempt to contact the pilot by ultra high frequency radio and then search for the missing helicopter, and the helicopter’s clock stopping at 1605 were consistent, suggesting that the helicopter impacted terrain sometime between about 1605 and 1615. At that time, the sun was at an elevation of about 13°–15°above the horizon and about 30° to the right of track.

Given the westerly direction of travel and the ambient conditions, it was likely that the pilot was subjected to sun glare. The ATSB considered whether the helicopter’s main rotor down-wash would have produced significant airborne dust and other particles, exacerbating the pilot’s disability glare. However, given the helicopter’s forward motion, any particles would, if agitated, have been behind the helicopter’s position along the westerly flight path.

The pilot was wearing an aviation helmet fitted with two sun visors but the ATSB could not determine if either or both of the visors were in use at the time. Even so, while visors lessen glare, they do not reduce its effect under all circumstances. Compounding the pilot’s difficulty identifying and/or avoiding the tree, it was possible that the tree line to the west along the dry creek bed acted as a darkened backdrop, decreasing the salience of the isolated tree.

The ATSB concluded it was probable that, due to the effects of sun glare, the pilot either did not see or misjudged the distance to the tree, leading to the tree strike and subsequent loss of control and collision with terrain.

Survivability

Unrestrained items in the cabin, including shotguns, a bag of ammunition and a digital single-lens reflex camera, increased the risk of flight control interference during normal flight and injury to the pilot during the accident sequence. Despite this, the ATSB could not determine if the unrestrained items contributed to the accident or the pilot’s injuries.

The helicopter was fitted with bladder-type fuel tanks that did not rupture during the accident sequence, preventing fuel leakage and therefore reducing the risk of a post-impact fire. In addition, the pilot’s seat structure was compressed, consistent with its design to absorb impact forces during an accident.

The helicopter was also fitted with three-point safety harnesses, increasing the likelihood of effective restraint in the case of an accident. Moreover, the pilot was wearing an aviation-flying helmet to reduce the risk of injury in an accident.

Despite all of the above safety features, the pilot was fatally injured. This indicated that the impact forces were such that the accident was not survivable.

Context

The pilot held:

  • a Commercial Pilot (Helicopter) Licence that was issued in 2003
  • a Single Engine Helicopter rating
  • an Aerial Mustering Helicopter approval
  • a Civil Aviation Safety Authority (CASA) Aviation Medical Certificate.

A review of the pilot’s logbook and previous aircraft maintenance releases for VH-HRW showed that the pilot had accumulated about 1,170 flight hours in R22 helicopters prior to the accident.

Fatigue

Family and friends of the pilot provided a consolidated 72-hour history of the pilot’s activities prior to the accident. These were considered to be consistent with normal rural living. No activities that would be considered overly strenuous were identified and the pilot had adequate rest periods prior to, and on the day of the accident. The mustering activity on the day was not considered excessive.

Data downloaded from the helicopter’s Global Positioning System (GPS) receiver and witness accounts were reviewed to understand the pilot’s activities that day. This review showed that the pilot flew for about 3 hours and 20 minutes over a period of 7 hours. This included a stop to refuel and the previously-discussed rest period and lunch after completing the main mustering activity that morning.

Based on the recorded GPS data and witness statements, the ATSB concluded that it was unlikely pilot fatigue contributed to the accident.

Operations

The muster was coordinated with the property owners and a station hand and entailed the pilot using the helicopter to help ground personnel move the cattle to a holding point.

Recorded data from the helicopter’s GPS receiver indicated that the pilot commenced mustering at 1032 and completed the muster at 1329. This was consistent with the recollection of one of the witnesses. The muster was conducted over an area of about 16 km2 and could be expected to include turns and complex manoeuvres at low level to encourage cattle to move in the desired direction.

The station hand reported that, after lunch and resting, they observed the helicopter land on a property road shortly after it departed on the return flight to the pilot’s home base. The landing was to the west of a tree-lined dry creek. The pilot got out of the helicopter, opened a gate, got back in the helicopter, and then departed in an easterly direction.

The station hand and the property owner recalled separately that the 1600 radio news broadcast commenced on their vehicle’s radios at about that time.

The station hand, who reported being familiar with the helicopter, reported that when the helicopter departed from the road it sounded and appeared to be operating normally. That was the last recorded sighting of the helicopter prior to the discovery of the wreckage.

Wreckage information

Examination of the helicopter wreckage and ground scars found that the tail rotor blades collided with the upper branch of an isolated, 7 m-high dead and defoliated tree (tree) that was about 100 m to the east of a tree-lined dry creek bed. The terrain sloped down towards the creek bed at about 2°–5° (Figure 2).

Figure 2: Helicopter flight path looking to the west. The estimated right-to-left flight path (indicated by a yellow dashed arrow) is derived from the impact point with the dead and defoliated tree and the position of the main helicopter wreckage

Figure 2: Helicopter flight path looking to the west. The estimated right-to-left flight path (indicated by a yellow dashed arrow) is derived from the impact point with the dead and defoliated tree and the position of the main helicopter wreckage

Source: ATSB

On contact with the tree, segments of the two tail rotor blades separated from the tail rotor. During the ensuing impact sequence, one of these blades struck the lower-vertical stabiliser, causing the combined vertical and horizontal stabilisers[2] and tail rotor gearbox to separate from the tail boom (Figure 3). The tail rotor blades, combined horizontal and vertical stabilisers and gearbox were collocated in close proximity to the tree.

Figure 3: Combined horizontal and vertical stabilisers and tail rotor blades after their separation from the helicopter. One of the two tail rotor blades has been placed against the lower-vertical stabilizer to demonstrate the impact point after the initial strike with the dead and defoliated tree

Figure 3: Combined horizontal and vertical stabilisers and tail rotor blades after their separation from the helicopter. One of the two tail rotor blades has been placed against the lower-vertical stabilizer to demonstrate the impact point after the initial strike with the dead and defoliated tree

Source: ATSB

The remainder of the helicopter continued for an additional 40–50 m west of the tree, impacted terrain and pivoted on the remainder of the tail boom in a clockwise direction. Shortly after, the fuselage and main rotor blades collided with terrain.

During the accident sequence, the main rotor blade pitch links fractured in overload, consistent with the impact forces. One of the two rotor blades penetrated the acrylic glass canopy. The instrument console was dislodged from its mounting and ejected from the cockpit (Figure 4). The helicopter’s clock stopped at 1605, not inconsistent with the helicopter colliding with terrain about 5 minutes after it departed from the property road and the time taken by the station hand to locate the wreckage of the helicopter.

The main and auxiliary fuel tanks contained a significant quantity of fuel. A sample of that fuel was tested on-site and found to be adequate for continued flight. The fuel tanks sustained significant crushing and deformation damage. In addition, the tail rotor drive train flex plate[3] coupling penetrated the full thickness of the main aluminium tank. However, the internal fuel bladder was not punctured and did not leak (Figure 5). There was no fire.

Continuity of the main rotor drive train was established with evidence that, at impact, the engine was producing significant power. This included torsional deformation of the main and tail rotor drive shafts, chord wise scratching of the main rotor blades and absence of main rotor blade coning.

The ATSB established that, based on the on-site physical evidence, it was likely the helicopter was mechanically sound prior to colliding with the tree with no preexisting mechanical defects that may have contributed to the accident.

Figure 4: Helicopter wreckage, showing the ejected instrument console, damaged main rotor blade and destroyed canopy

Figure 4: Helicopter wreckage, showing the ejected instrument console, damaged main rotor blade and destroyed canopy

Source: ATSB

Survivability

Helicopter equipment

The two seat bases in the R22 helicopter also serve as storage compartments for the helicopter. Constructed of aluminium, the seat ‘boxes’ are designed to absorb and limit the transfer of impact forces to the pilot and passenger in the event of an accident. Goods that do not impede that safety feature, and are within specific weight limits, can be placed inside the storage compartment.

The pilot’s seat base was found partially compressed, consistent with the absorption of vertical impact forces during the accident sequence. The pilot and passenger seat bases contained various stowed items that were within the manufacturer’s allowable weight limits. All items found at the accident site had been retained within the compartments.

During recent maintenance the helicopter was fitted with front-seat three-point safety harnesses. The pilot was wearing their three-point safety harness and, although fatally injured, was effectively restrained during the impact sequence.

Installation of bladder-type fuel tanks

During the recent maintenance, the helicopter was modified and fitted with bladder-type fuel tanks. These tanks reduce the risk of a post-impact, fuel-fed fire.

Figure 5: Ruptured aluminium main fuel tank. Note that the remaining fuel was retained by the internal fuel bladder

Figure 5: Ruptured aluminium main fuel tank. Note that the remaining fuel was retained by the internal fuel bladder

Source: ATSB

Personal equipment - aviation helmet

The pilot was wearing an aviation helmet built to the United States (US) military standard MILDTL-87174A that was fitted with yellow and dark grey sun visors. The visors could be raised and lowered by the pilot at two pivot points, one on each side of the helmet. The ATSB could not determine if either visor was being used at the time of the accident.

Impact damage was identified to the left and right sides of the helmet. The right side of the cockpit, above the door cut-out, had an impression consistent with the shape of the pilot’s helmet sun visor pivot point.

Loose/unrestrained items

Loose, or unrestrained items were recovered in and around the wreckage. The most significant items were a digital single-lens reflex camera, two shotguns and a bag of live ammunition. A witness reported that some pilots use shotguns during mustering operations and for feral animal control.

One of the shotguns collided with one of the main rotor blades during the impact sequence. Live cartridges were scattered throughout the wreckage and the digital single-lens reflex camera was severely disrupted.

Unrestrained or loose items are known to increase the risk of loss of flight control or injury during flight.

Medical and pathological information

Post-mortem examination and toxicology analysis of the pilot did not reveal any evidence of a physiological condition that may have contributed to the occurrence, nor any evidence of drug or alcohol use. The examining forensic pathologist reported that the pilot sustained fatal injuries that were consistent with the type of injuries encountered in a helicopter accident.

Meteorological information

According to the Bureau of Meteorology, at about 1500 the weather at Mitchell, about 63 km south-south-west of the accident site, included few[4] clouds with light south-westerly winds and a temperature of 26 °C.

Witnesses who were associated with the mustering operation reported that the flying conditions at the property were ‘very good’.

The pilot was flying in a westerly direction at the time of the accident. According to the Geoscience Australia website (see www.ga.gov.au), between 1600 and 1615 the sun was at an elevation of about 13°–15° above the horizon and at an azimuth[5] of about 301°–303°. That was, about 30° to the right of the helicopter’s westerly track.

Research

Aerial mustering

Aerial mustering is the use of aircraft to locate, direct and concentrate livestock. It involves operating in an inherently hazardous environment while the aircraft is manoeuvred close to obstacles at very low heights, usually below a height of 500 ft above the surface.

In 2015, CASA released a report titled Sector Risk Profile for the aerial mustering sector. The report showed that the Robinson R22 helicopter is the most common model of helicopter on the Australian register and that about 62 per cent of the total R22 hours flown has been in aerial mustering operations. The report also discussed the development of a CASA risk profile tool to take account of the risks associated with aerial mustering operations and the associated operating environment. The report stated that the purpose of the ‘aerial mustering risk profile’ was to:

…present a picture of the key risks and effects arising from the operations of the sector’s fleet of aircraft at a given point in time. CASA and selected industry sector participants developed the sector risk profile through a process in which risks were jointly identified, assessed and evaluated for treatment. When fully implemented these risk treatments should reduce the risk profile of the sector.

A study conducted by the ATSB in 2004 titled Light Utility Helicopter Safety in Australia found that between 1985 and 2003, of the 141 accidents involving the R22 helicopter, 102 occurred during aerial mustering. The majority of aerial mustering accidents involved collision with terrain, trees, man-made features or other obstacles.

Sun glare

Research has shown that environmental conditions can greatly hinder a pilot’s ability to perform visual tasks. One of the most serious conditions in aviation is glare. When flying in the presence of strong light, as in this case flying directly towards the west when the sun was at an elevation of 13°–15° above the horizon, light from the sun is scattered within the eye and onto the retina. This results in a loss of visual performance and is termed ‘disability glare’. The problems associated with disability glare are reported to increase with age.

Disability glare is exacerbated when objects are being viewed through media or atmospherics that scatter the light further than that occurring naturally in the eye. Such conditions include dirty windscreens, flying in haze and taking off or landing directly into the sun. Research has found that pilots experience difficulty perceiving distances and depth due to glare from bright lights. Bright light sources are also shown to lead to visual misperceptions of height and distance and a momentary flash blindness (Nakagawara et al, 2006). In addition, glare was reported to distract pilot’s ‘truthful’ perception. A study conducted on behalf of the US Federal Aviation Administration (Nakagawara et al, 2003) of the US National Transportation Safety Board aviation accident database found that during a 12-month period there were:

…130 accidents in which glare from natural sunlight was found to be a contributing factor. The majority of the events occurred during clear weather and atmospheric conditions (85%), and were associated with the approach/landing and take-off/departure phases of flight (55%).

The study concluded that:

Exposure to glare from natural sunlight has contributed to aviation accidents, primarily under optimal visual conditions. The majority of accidents occurred during flight maneuvres at low altitude in airspace congested with other aircraft or obstacles, such as trees, power lines, utility poles, and terrain.

Related occurrences

The ATSB has investigated numerous accidents where sun glare was found to be a contributing factor. A number of these accidents and investigation reports are listed below and are available from the ATSB website:

  • AO-2009-018. Midair collision involving Robinson Helicopter Company R22 Betta II, registered VHHCB, 15 km south-east of Springvale Station, Western Australia on 5 May 2009.
  • AO-2012-107. Runway excursion involving Cessna 210N, registered VH-WPD, at Urapunga Aeroplane Landing Area (ALA), Northern Territory on 23 August 2012.
  • AO-2012-146. Controlled flight into water involving Robinson R22 helicopter, registered VHHOA, 89 km north-north-west of Innamincka ALA, South Australia on 31 October 2012.
  • AO-2013-178. Hard landing involving Grob G-115C2 aircraft, registered VH-ZIV, at Merredin ALA, Western Australia on 11 October 2013.
  • AO-2014-118. Aircraft separation issue involving a Skyfox CA25N aircraft, registered 243265 and a Piper PA-28 aircraft, registered VH-WJO, near Roma Airport, Queensland on 3 July 2014.
  • AO-2014-191. Collision with terrain involving an Air Tractor AT-502 aircraft, registered VHPTF, 45 km west of Moree Airport, New South Wales on 18 December 2014.

__________

  1. The R22 has combined vertical and horizontal stabilisers fixed to the right side of the tail boom.
  2. The flex plate is a device that allows for small misalignments of the rotating clutch shaft as it transmits engine power to the rotor system drive train.
  3. Cloud cover is normally reported using expressions that denote the extent of the cover. The expression few indicates that up to a quarter of the sky was covered
  4. The clockwise horizontal component of the sun’s or moon’s position from true north, measured in degrees.

Purpose of safety investigations & publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2016

image_5.png

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 AO-2015-055
Occurrence date 28/05/2015
Location 63 km north-north-east Mitchell (near Kilmorey Falls)
State Queensland
Report release date 26/05/2016
Report status Final
Investigation level Defined
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Robinson Helicopter Co
Model R22 BETA
Registration VH-HRW
Serial number 0901
Sector Helicopter
Operation type Aerial Work
Departure point near Mitchell, Qld
Damage Destroyed

VFR into IMC involving a Beech A36, VH-ANX, overhead York (ALA), Western Australia, on 19 May 2015

Final report

What happened

On 19 May 2015, the pilot of a Beech A36 aircraft, registered VH-ANX, conducted pre-flight preparations for a private flight from Bunbury Airport to Wongan Hills aeroplane landing area (ALA), Western Australia (Figure 1). The pilot assessed that based on the weather forecast, they would be able to conduct the flight in visual meteorological conditions (VMC).[1] The pilot submitted a flight plan for the flight under the visual flight rules (VFR).[2] The pilot planned to track via Northam ALA at 3,500 ft above mean sea level (AMSL), in accordance with VFR cruise altitudes. The pilot also planned to remain clear of Perth air traffic control zone. At about 1525 Western Standard Time (WST), the aircraft departed from Bunbury, with full fuel on board.

Figure 1: The pilot’s planned route from Bunbury to Wongan Hills via Northam (red) and the approximate actual track, via York (purple)

Figure 1: The pilot’s planned route from Bunbury to Wongan Hills via Northam (red) and the approximate actual track, via York (purple)

Source: Google earth annotated by ATSB

When approaching abeam Perth, the pilot observed significant cloud in the Perth area. The pilot reported seeing cloud to the left and right, but could see a clear path ahead. They then descended to about 3,000 ft to remain clear of cloud, and continued on the planned route.

When about 10 NM south-west of York ALA, the pilot observed the cloud start to close in, and build to the west. The pilot made multiple diversions to the right of the planned track, but the cloud continued to close in. The pilot then commenced turning back, but the cloud had closed in behind the aircraft. The pilot climbed the aircraft to 3,500 ft and elected to enter the cloud and continue towards Northam.

At about 1547 WST, when about 1 NM east of York ALA and at 3,500 ft AMSL, the pilot contacted Perth air traffic control (ATC) and requested assistance. The pilot advised that the flight was operating under a VFR flight plan, had entered cloud, and was instrument rated. The controller identified the aircraft on radar, then at 3,700 ft. The controller asked whether the pilot was able to remain in instrument meteorological conditions (IMC),[3] and the pilot responded in the affirmative. The controller then advised that the lowest safe altitude in the area was 3,300 ft, and asked whether the pilot wanted to continue the flight under the instrument flight rules (IFR),[4] to which the pilot replied ‘I have no choice I am in IMC’.

The controller then allocated the aircraft a unique transponder code, asked how many people were on board and the fuel endurance remaining. The controller also asked whether the pilot wanted to divert to Jandakot Airport and be provided with the radar lowest safe altitude. However, the pilot responded by asking for advice regarding the weather to the north.

As the aircraft was outside the Perth control area, the controller then coordinated[5] with the Melbourne centre controller to hand the aircraft over. The controller also requested an update on the weather be provided to the pilot. The controller then advised the pilot that the aircraft was now indicating an altitude of 2,800 ft and the pilot responded ‘just climbing back up’.

At about 1552 WST, the pilot communicated with the Melbourne centre controller, and advised that they were now visual and would continue tracking to Northam at about 2,400 ft AMSL. The aircraft landed at Wongan Hills ALA at about 1630 WST, without further incident.

Pilot experience

The pilot had about 800 hours total flying time, attained an instrument rating about 2 years prior to the incident, and had completed 82 hours of instrument flight time. The pilot had completed an instrument flight in the simulator three weeks prior to the incident, and was therefore current (and qualified) for flight under the instrument flight rules.

The aircraft was IFR approved and equipped.

Pilot comments

The pilot was not aware it was possible to contact ATC and request change from VFR to IFR flight while airborne. They had not set up any navigation aids prior to entering IMC, and reported that they were navigating primarily by reference to the directional indicator while in cloud.

The pilot could not recall why the aircraft descended below the applicable lowest safe altitude during the flight. They thought it was possibly because they were distracted by responding to ATC’s request for the aircraft’s fuel endurance, or checking the aircraft’s position on their iPad. The pilot assessed their own workload to be moderate, and only slightly increased when the aircraft entered cloud.

Weather forecast

The area forecast (ARFOR)[6] for area 60, current at the time of the incident, for the subdivision south of a line joining Cue and Geraldton, included:

Table 1: Area forecast for area 60

Cloud coverCloud typeCloud baseCloud topsWeather
BrokenStratus1,000 ft AMSL (2,000 ft inland)2,000 ft AMSL (3,000 ft inland) 
BrokenCumulus/stratocumulus2,000 ft AMSL (3,000 ft inland)8,000 ft AMSLShowers of rain

 

The terminal aerodrome forecast (TAF) current for Perth included scattered cloud with base at 3,500 ft above ground level.

ATSB comment

During flight, pilots are able to request ATC amend their flight plan from VFR to IFR, or vice versa. When requesting a change from VFR to IFR while in flight, the aircraft should remain at a VFR level and in VMC, until the IFR clearance is received. The details required by ATC include:

  • aircraft callsign and type
  • departure and destination points
  • current location
  • number of people on board
  • fuel endurance.

Safety message

Pilots are encouraged to make conservative decisions when considering how forecast weather may affect their flight. If poor weather is encountered en route, timely and conservative decision making may be critical to a safe outcome. VFR pilots are encouraged to familiarise themselves with VMC criteria detailed in Aeronautical Information Publication (AIP) Australia. Where forecast or actual conditions are such that continued flight in VMC cannot be assured, pilots should assess all available options. Unplanned flight into conditions of limited visibility can rapidly lead to loss of orientation and loss of aircraft control.

The ATSB SafetyWatch highlights the broad safety concerns that come out of our investigation findings and from the occurrence data reported to us by industry. One of the safety concerns is flying with reduced visual cues www.atsb.gov.au/safetywatch/flying-with-reduced-visual-cues.aspx.

If the pilot and aircraft are rated and certified for instrument flight, and weather conditions may not be suitable for flight under the VFR, it may be judicious to be prepared for an IFR flight. During the flight, if the pilot is not assured that VMC conditions can be maintained, the pilot may then request changing to IFR flight. When amending from a VFR to IFR flight en route, it is important to have the necessary details ready and contact ATC for an IFR clearance prior to entering IMC. Ensuring all available navigation aids are set up correctly even for a VFR flight will reduce the pilot’s workload when changing to instrument flight.

Aviation Short Investigations Bulletin - Issue 42

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2015

image_5.png

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. Visual Meteorological Conditions is an aviation flight category in which visual flight rules (VFR) flight is permitted—that is, conditions in which pilots have sufficient visibility to fly the aircraft maintaining visual separation from terrain and other aircraft.
  2. Visual flight rules (VFR) are a set of regulations which allow a pilot to only operate an aircraft in weather conditions generally clear enough to allow the pilot to see where the aircraft is going.
  3. Instrument meteorological conditions (IMC) describes weather conditions that require pilots to fly primarily by reference to instruments, and therefore under Instrument Flight Rules (IFR), rather than by outside visual references. Typically, this means flying in cloud or limited visibility.
  4. Instrument flight rules (IFR) permit an aircraft to operate in instrument meteorological conditions (IMC), which have much lower weather minimums than visual flight rules. Procedures and training are significantly more complex as a pilot must demonstrate competency in IMC conditions, while controlling the aircraft solely by reference to instruments. IFR-capable aircraft have greater equipment and maintenance requirements.
  5. Coordination is the process of obtaining agreement on clearances, transfer of control, advice or information to be issued to aircraft, by means of information exchanged.
  6. An area forecast issued for the purposes of providing aviation weather forecasts to pilots. Australia is subdivided into a number of forecast areas.
  7. Cloud cover is normally reported using expressions that denote the extent of the cover. The expression few indicates that up to a quarter of the sky was covered, scattered indicates that cloud was covering between a quarter and a half of the sky. Broken indicates that more than half to almost all the sky was covered, while overcast means all the sky was covered.

 

Occurrence summary

Investigation number AO-2015-053
Occurrence date 19/05/2015
Location overhead York (ALA)
State Western Australia
Report release date 27/08/2015
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category VFR into IMC
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Beech Aircraft Corp
Model A36
Registration VH-ANX
Serial number E-1675
Sector Piston
Operation type Private
Departure point Bunbury, WA
Destination Wongan Hills, WA
Damage Nil