Loss of separation

Boeing 767-324, VH-BZF, 3 km west-north-west of Melbourne (VOR), on 18 March 1999

Safety Action

Local safety action

As a result of the investigation, Airservices Australia Southern District have proposed to:

  1. amend the Melbourne tower training syllabus to ensure that ab initio trainees gain a broad range of experience prior to commencing aerodrome or coordinator training;
  2. require trainees and controllers supervising training to attend a training principles briefing pending the introduction of a workplace training course in the near future;
  3. impose a maximum training session duration of 2 hours; and
  4. amend local instructions relating to traffic management procedures and the use of non-duty runways.

Australian Transport Safety Bureau (ATSB) Safety Action

The ATSB is investigating safety deficiencies relating to:

  1. ab initio aerodrome controller rating training; and
  2. the identification and publication of critical safety areas including the level of separation assurance provided by standard instrument departures.

Any safety outputs issued as a result of the investigation will be published in the Bureau's Quarterly Safety Deficiency Report.

Significant Factors

  1. The supervisor of the trainee, the aerodrome controller, had a lapse in concentration at a critical stage of the departure sequence, having been operating at the position in excess of 3 hours.
  2. The trainee was unfamiliar with terminal area operations/procedures and was unaware of the increase in complexity during runway transition.
  3. Tower training publications' critical safety section and other references did not include potential standard instrument departure or arrival areas of conflict.

Analysis

The concentration level of both the aerodrome controller and the trainee had probably lapsed due to the duration of the training session. Additionally, the aerodrome controller may have been less vigilant in his monitoring of the trainee because of the reduction in aircraft numbers and his perception of the trainee's level of competence in the aerodrome control position.

Provision of information regarding the increase in complexity of traffic management during runway transition and regarding the critical safety aspects of standard instrument departures and arrivals would have provided the trainee with some knowledge to compensate for areas where he lacked experience. On-the-job training does not necessarily expose trainees to all critical elements nor provide sufficient time for them to develop their own traffic management models. Information on such critical areas is required to ensure that safety aspects are understood and considered, particularly during on-the-job training.

A greater awareness of terminal area operations and procedures may have provided the trainee with sufficient knowledge to appreciate that the departing aircraft were not going to be separated by the departure controller. In turn, this may have alerted the trainee to the fact that he was required to provide a separation solution or alternatively coordinate one with the departure controller.

Summary

A Beech 1900 (Beech) departed from runway 27 and was tracking via a STRATHBOGIE 8 standard instrument departure, on climb to 5,000 ft. Shortly after, a Boeing 767 (B767) departed from runway 34 on a DOSEL 8 standard instrument departure, on climb to 5,000 ft. The standard instrument departure tracks intersected approximately 2 NM north of the aerodrome. The departure north radar controller (departure controller) observed that the separation between the two aircraft was not going to be maintained and queried the aerodrome controller in relation to the separation procedure being applied. The aerodrome control position was being operated by a trainee under the supervision of a rated controller. The trainee advised that he thought the departure controller was providing separation. The departure controller instructed the Beech crew to turn left onto a heading of 310 degrees and the B767 crew to turn right onto a heading of 030 degrees. The two aircraft passed at the same altitude, with 1 NM lateral separation. The minimum separation required was either 3 NM laterally or 1,000 ft vertically. There was an infringement of separation standards. The B767 was fitted with a traffic alert and collision avoidance system and the crew received a traffic advisory just prior to the issue of the avoiding instructions from the departure controller.

The trainee and the aerodrome controller had been at the console for about 3 hours and the number of aircraft being managed had reduced slightly following a busy period. The runway mode was being changed from land and hold short operation (LAHSO) using runways 34 and 27, to dedicated departure runway arrangement using those runways. In LAHSO all aircraft depart from runway 27, while in the dedicated departure mode, departures to the south and west use runway 27 and those to the north and east use runway 34. In that configuration, the intersection of aircraft departure tracks is almost eliminated. It was recognised by experienced controllers that the transition period between runway modes required an increased awareness and careful consideration of the traffic management plan to ensure that potential conflicts for departing aircraft were minimised. The trainee was aware of potential problems for each mode but had not been alerted to the potential problems that may occur during a mode transition period. On taxi, the crew of the B767 requested and were approved to use runway 34. The trainee subsequently amended the departure order of the B767 and the Beech to eliminate a requirement to apply a 2-minute wake turbulence separation standard to the Beech aircraft.

The trainee did not appreciate that the aircraft's departure tracks converged north of the aerodrome. The aerodrome controller reported that as the trainee was soon to be checked for a rating his monitoring of the trainee's control was less vigilant than normal. Local instructions stated that the aerodrome controller was responsible for the separation of departing aircraft within 5 NM of the aerodrome and that for departures from different runways, the aerodrome control and departure control positions were jointly responsible for coordinating a separation solution. The departure controller's preference was to depart the B767 before the Beech but he agreed to the trainee's request to change the departure order. Normal practice in this situation was that the aerodrome control position, having initiated the change, was responsible for the separation unless otherwise coordinated. The controllers neither coordinated a separation solution nor clearly established who was responsible for ensuring separation. Both assumed that the other was going to separate the two aircraft. The aerodrome controller was not aware of the developing situation and was only alerted to the infringement following the departure controller's query to the trainee.

The trainee had undergone tower control ab initio training, which included approximately 1 day of training on the vectoring of aircraft. The course did not provide any terminal area (TMA) control training. Controllers undergoing training for tower positions were able to undertake TMA familiarisation. But the tower training syllabus did not require trainees to develop an understanding of, or to be familiar with, TMA operations. TMA familiarisation by tower trainees was conducted on an ad-hoc basis and there was no procedure to assess a trainee's level of understanding of TMA operations.

Melbourne Tower training publications did not provide advice of a preferred duration for training sessions that would maximise the training benefit. The publications did list aspects of critical safety that needed to be covered during training for both trainees or supervising controllers. But the list did not include areas of known conflict for standard instrument departures or standard arrival routes. The publications did not include advice of the potential inherent complexity of runway mode transition.

Occurrence summary

Investigation number 199903436
Occurrence date 18/07/1999
Location 3 km WNW Melbourne, (VOR)
State Victoria
Report release date 24/03/2000
Report status Final
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 The Boeing Company
Model 767
Registration VH-BZF
Serial number VH-BZF
Sector Jet
Operation type Air Transport High Capacity
Departure point Melbourne, VIC
Destination Sydney, NSW
Damage Nil

Aircraft details

Manufacturer Beech Aircraft Corp
Model 1900
Registration VH-IMH
Serial number VH-IMH
Sector Turboprop
Operation type Air Transport Low Capacity
Departure point Melbourne, VIC
Destination Williamtown, NSW
Damage Nil

Saab SF-340B, VH-EKN

Summary

A Cessna 340 (C340) departed Sydney at 1036, on climb to flight level (FL) 120, tracking via Shellys and Yass to Deniliquin. At 1047 a Saab 340B (Saab) departed Sydney for Canberra on climb to FL120, also tracking via Shellys. Once both aircraft were established in cruise there was a rate of closure of about 100 kt between them. As the Saab passed over Shellys, the Melbourne Sector 12 controller observed on radar that the lateral separation between the two aircraft was reducing to less than the required standard of 5 NM. The controller instructed the Saab to turn left though 90 degrees and advised the crew that there was traffic in their 2-o'clock position at 2 NM. The crew reported sighting the C340. Subsequent radar analysis established that the lateral distance between the aircraft had reduced to 2 NM.

The traffic level in the sector was low, with six aircraft on frequency. The controller had been operating the radar display on the 100 NM scale to enable him to readily observe boundary traffic or approaching flights. The display was centred on Shellys at the time of the occurrence. The controller was closely monitoring the progress of three aircraft that were tracking between Wollongong and Canberra. Two aircraft were in a step climb, while the third was overtaking and outclimbing the first two. The controller believed that he was maintaining an adequate scan of the radar display and was unable to provide a reason for not appreciating the effect of the high rate of closure between the two occurrence aircraft.

The morning shift of the adjacent sector to the west of Sector 12 had transitioned to The Advanced Australian Air Traffic System (TAAATS) approximately two and one-half weeks prior to the occurrence. This had resulted in the implementation of a number of changes to Sector 12 coordination procedures. Those changes were only required during the morning shift. During the afternoon the adjacent sector reverted to the same air traffic control system as that being used by Sector 12. The controller subsequently reported that while the amended coordination procedures were understood, they required conscious thought to action them.

During the morning, and at the time of the occurrence, coordination between the sector and Nowra Air Traffic Control had been restricted by communications problems and the controller was using a "hotline" and a telephone for coordination. There was no telephone available on the Sector 12 console so the controller was required to reach across to use one from an adjacent console.

The investigation did not establish the reason why the controller was unaware of the impending conflict until there was insufficient time to resolve the situation. It is probable that a combination of low traffic levels, possible fixation on the Wollongong - Canberra traffic situation, and some distraction due to amended coordination requirements, was sufficient to reduce the controller's normal level of vigilance.

Occurrence summary

Investigation number 199902615
Occurrence date 10/05/1999
Location Shelleys, (NDB)
State New South Wales
Report release date 29/07/1999
Report status Final
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 Saab Aircraft Co.
Model 340
Registration VH-EKN
Serial number 372
Sector Turboprop
Operation type Air Transport Low Capacity
Departure point Sydney, NSW
Destination Canberra, ACT
Damage Nil

Aircraft details

Manufacturer Cessna Aircraft Company
Model 340
Registration VH-MAG
Serial number 3400166
Sector Piston
Operation type Unknown
Departure point Sydney, NSW
Destination Deniliquin, NSW
Damage Nil

Boeing 737-376, VH-TJA

Summary

A Boeing 777 (B777) was tracking via an ARBEY Six standard arrival route (STAR) at 8,000 ft for a landing on runway 34 at Melbourne. A Boeing 737 (B737) departed runway 27 for Maroochydore and was cleared to track via the DOSEL Eight standard instrument departure (SID) on climb to 7,000 ft. Because the SID and STAR tracks crossed north of Melbourne aerodrome the departure controller planned to maintain the minimum vertical separation standard of 1,000 ft between the two aircraft until they had passed, and then clear the aircraft to climb/descend once the 3 NM lateral radar separation standard had been established between them. However, prior to the B737 reaching the crossing point the controller instructed the crew to cancel the SID and to track direct to Mudgee, believing that the track adopted by the B737 would result in the aircraft passing in front of the B777 with greater than the required radar standard.

When a Boeing 767 (B767) subsequently departed from runway 27 on climb to 5,000 ft the controller thought that he only had to separate that aircraft from the B777. Consequently, he instructed the crew of the B777 to descend to 6,000 ft. The crew acknowledged and advised that they had left 8,000 ft. The controller was about to instruct the crew of the B737 to climb to a higher level when he saw that the separation between the B737 and the B777 was going to reduce to less than the required standard. The controller issued instructions to both crews in order to maintain radar separation, however, the distance between the two aircraft reduced to 2.25 NM laterally and 200 ft vertically.

Both aircraft were fitted with traffic alert and collision avoidance systems (TCAS) and each crew received traffic advisories followed by a short resolution advisory. By the time the controller had issued turn instructions the advisories had ceased. Each crew had sighted the other aircraft just prior to the conflict. The short-term conflict alert (STCA) function of The Australian Advanced Air Traffic System (TAAATS) also operated during the occurrence.

The departure and approach control positions had recently transitioned to TAAATS, and the departure controller had been operating the new equipment for about 2.5 weeks. Immediately prior to the occurrence the controller had been discussing the operation of the route adherence monitor (RAM) function of TAAATS with another controller, and was attempting to establish the degree to which an aircraft would have to be off-track before the RAM activated.

When the controller instructed the B777 crew to descend, his impression was that he had resolved the possibility for conflict between the B737 and the B777. However, the track to Mudgee for the B737 did not provide the required lateral separation with the arriving B777. The controller had initially used separation assurance techniques to establish separation between all the aircraft. However, to facilitate the departure climb for the B737 the controller issued instructions to that crew which required him to more diligently monitor the track and altitudes of aircraft under his control. He then became distracted by non-essential manipulation and discussion of the system during a critical phase of the traffic management sequence. Consequently, he did not appreciate that the lateral distance between the B737 and the B777 was insufficient to maintain separation. Had the controller maintained vertical separation between the two aircraft, or had vectored the B737 behind the B777, it is unlikely that the incident would have occurred.

The situational awareness of both crews, the operation of the TCAS, and the STCA were all active defences in the incident.

Occurrence summary

Investigation number 199902459
Occurrence date 22/05/1999
Location 15 km NNW Melbourne, Aero.
State Victoria
Report release date 27/08/1999
Report status Final
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 The Boeing Company
Model 737
Registration VH-TJA
Serial number 24295
Sector Jet
Operation type Air Transport High Capacity
Departure point Melbourne, VIC
Destination Maroochydore, QLD
Damage Nil

Aircraft details

Manufacturer The Boeing Company
Model 777
Registration 9V-UA1
Sector Jet
Operation type Air Transport High Capacity
Departure point SINGAPORE
Destination Melbourne, VIC
Damage Nil

Boeing 737-376, VH-TAG

Safety Action

As a result of this incident, Airservices Australia recommended that:

  1. Team leaders brief controllers on the necessity to provide separation assurance where that assurance is not provided on system routes.
  2. Override facilities are to be used.

A cross familiarisation program between the tower and terminal control staff was developed and an education program was devised to ensure both areas have a better understanding of standard system routes.

The Manual of Air Traffic Services (MATS) 6.2.1.2 has been amended to allow controllers to cancel a SID during hours of darkness and instruct crews to depart on runway track using the climb gradient specified in the cancelled SID.

Analysis

This scenario only occurred prior to first light, which occurred after 0600 from approximately the end of March until early September. The problem with the SIDs converging during daylight hours was normally overcome by the cancelling of the SID and the issuing of a radar departure instruction while the aircraft is on the ground prior to departing RWY 03, thus providing separation assurance.

Prior to first light, separation assurance could have been achieved by DEP applying vertical separation between aircraft departing these runways, or by exercising control over aircraft release times to ensure that a radar standard would exist between them.

The DEP controller did not ensure separation between the B737 and the preceding BAe146 by permitting the trainee to issue an instruction of "unrestricted" to the ADC.

The crew of the BAe146 provided a prompt to the controller by requesting a clearance direct to Ballidu shortly before commencing a turn off runway heading. However, the crew were advised by the DEP trainee that the request was understood and that he "will advise".

A second prompt occurred to the training officer when the crew of the B737 called on the DEP frequency reporting that they were leaving 1,800ft. It appears that this prompt alerted the training officer to the developing situation, as he then instructed the trainee to turn the BAe146.

The training officer at this point still did not intervene directly, but instead indicated to the trainee that he needed to give the crew of the BAe146 a heading in order to resolve the situation more quickly. The provision of traffic information or use of "immediate" may have been appropriate under the circumstances.

That the training officer did not intervene until after the incident had largely been resolved was indicative of inattention to the operational situation and a lack of understanding of the criticality of the situation. The training officer displayed a lack of control over the trainee at a time when the issue of precise instructions and a need to alert the crew of the situation was critical. Instructions issued to the trainee were in general terms rather than the specific terminology that the situation demanded.

The task of the ADC in this instance was to manage the runway departures in accordance with instructions from the DEP controller. The ADC and ADC trainee, both understood that the primary responsibility for separation for aircraft on the 03 and RWY 06 PEPPA3 SID, lay with the DEP controller.

The ADC advised that he continued to visually monitor both aircraft via their departure tracks, even though responsibility for separation lay with the DEP controller. He also advised that at no stage did he offer to take, or accept any, responsibility from the DEP controller for separation of the aircraft.

When asked by the DEP controller whether he could monitor, the response of "Yes, I'm monitoring" was intended to indicate that he had the aircraft in sight and that, at that time, by visual observation their tracks had begun to diverge. He was thus indicating that he was able to monitor that the aircraft tracks were not likely to come together, but was not indicating any acceptance of responsibility for separation.

The training configuration utilised by the ADC and DEP was such that the trainers were unable to directly override their trainees. Use of available override systems would have made it easier for the trainers to readily communicate with the crews.

Summary

An infringement of the 3NM radar separation standard occurred at 0606 western standard time approximately 5NM to the northeast of Perth. The aircraft involved were a British Aerospace 146 (BAe146) that departed Perth on a RWY 03 BIU2 standard instrument departure (SID) followed shortly after by a Boeing 737 (B737) that departed on a RWY 06 PEPPA3 SID.

The 03 BIU2 SID is designed to provide system separation with military airspace to the north of Perth and, as a consequence joins the 06 PEPPA3 SID at position REDIL, 8NM to the northeast of Perth. Military airspace was not active at the time of the incident.

The aircraft were under the control of the Perth Departures (DEP) controller at the time. The responsibility for the provision of separation of aircraft on these two SIDs was defined in Perth Local Instructions as the responsibility of the DEP controller.

The DEP controller was monitoring a trainee controller on DEP who was approaching the final stages of rating training. The controller did not use an "override" box that would have allowed him to override the trainee and transmit instructions to the crews.

The aerodrome controller (ADC) advised the trainee DEP controller that the B737 was next for take-off. The trainee DEP controller issued the ADC an unrestricted clearance for the B737 to depart.

The crew of the BAe146 heard the B737 being cleared for take-off and realised that the two aircraft were on conflicting departure routes. The crew asked the trainee DEP controller for a clearance direct to Ballidu in an attempt to resolve the situation. The controller advised the crew that he "would advise" when the direct clearance was available.

The B737 departed and the crew contacted DEP control and advised that they were leaving 1,800 ft. The crew of the BAe146 monitored the proximity of the B737 visually and on the Traffic Alert and Collision Avoidance System (TCAS). The TCAS equipment did not provide a traffic or resolution advice.

The DEP controller did not intervene directly and prompted the trainee to turn the BAe146 away from the B737. The trainee then issued an instruction to the crew of the Bae146 to cancel the SID and track direct to Ballidu. The DEP controller then instructed the trainee to give the crew of the BAe146 a heading in order to resolve the situation. The trainee responded by instructing the crew of the BAe146 to turn left heading 360 degrees for separation. The trainee then instructed the crew of the B737 to turn right heading 090 degrees for separation.

Traffic information was not passed to either crew, nor was the word "immediate" used in passing heading instructions. There was no relay of the urgency of the situation to either crew by phraseologies used by the trainee. At that time the training officer utilised the APP console handset to contact the ADC on the hotline. The ADC was asked by the DEP controller "can you just monitor", to which the response from the ADC was "Yes I'm monitoring". The DEP controller later reported that in his mind it was a request for the ADC to provide visual separation between the aircraft. He also reported that the response received from the ADC indicated to him that the ADC had been providing separation throughout the event by visual monitoring of the aircraft.

The ADC was monitoring a trainee controller by use of a headset. The "B", or training system handset, was not being utilised. The ADC was unable to override the trainee without actually taking over the ADC handset from the trainee.

The DEP controller was not aware of the training on the ADC position and the ADC controller was not aware of the training on the DEP position.

Recorded radar data indicated that separation reduced to 1.4NM with a vertical separation of 200ft. The aircraft were separated by 1.5NM while at the same level. Minimum required radar separation for these aircraft while not 1,000ft vertically separated was 3NM.

The procedures in use were the standard procedures applicable for the use of runways 03/06 for departing aircraft prior to first light. These procedures required the issue of departure instructions for aircraft departing at night or in IMC to be in the form of a SID. It was not permissible for a controller to cancel a SID and issue a radar departure instruction while the aircraft is on the ground prior to first light. It was only permissible in these circumstances to cancel the SID after the aircraft was airborne and had reached the Minimum Vectoring Altitude (MVA). In the case of the 03 BIU2 SID, this situation provided a very short window of opportunity between the aircraft reaching the MVA and commencing a right turn off runway heading. Reliance on controller intervention to cancel this SID and issue a maintain runway heading instruction in order to maintain separation with SID departures from RWY 06 provided no separation assurance.

Occurrence summary

Investigation number 199902419
Occurrence date 06/05/1999
Location 9 km ENE Perth, (VOR)
State Western Australia
Report release date 05/09/2001
Report status Final
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 The Boeing Company
Model 737
Registration VH-TAG
Serial number 23478
Sector Jet
Operation type Air Transport High Capacity
Departure point Perth, WA
Destination Adelaide, SA
Damage Nil

Aircraft details

Manufacturer British Aerospace
Model BAe 146
Registration VH-JJP
Serial number E2037
Sector Jet
Operation type Air Transport High Capacity
Departure point Perth, WA
Destination Broome, WA
Damage Nil

Boeing 737-377, VH-CZO

Safety Action

As a result of this occurrence, the Bureau of Air Safety Investigation is currently investigating two safety deficiencies. The first relates to the inappropriate use of MATS 6-2-3 paragraph 32 by aerodrome controllers. The second relates to the non-application of MATS 6-3-1 paragraph 2 by controllers employed in the Brisbane aerodrome control tower.

Any safety output issued as a result of these analyses will be published in the Bureau's Quarterly Safety Deficiency Report.

Significant Factors

  1. The controller did not withhold the take-off clearance for CZO when there was no reasonable assurance that separation would exist between the aircraft when CZO commenced the take-off roll.
  2. The lack of visibility of the A4S taxiway at night from the control tower required that aerodrome controllers instruct pilots to confirm when clear of the runway.

Analysis

The difficulty in accurately locating aircraft on the high-speed taxiway A4S at night from the control tower is evidenced by the controller twice assuming that OGG had departed the runway and entered the taxiway. The awareness among local controllers of this difficulty should have encouraged the use of procedures to ensure the maintenance of required standards. However, the controller only recognised that his visual assessment was incorrect when advised by the crew of OGG. It is likely that the controller subsequently assessed that as CZO had not lined up, it was not necessary to cancel the clearance, but the two aircraft should simply be monitored.

The procedures relating to take-off clearances permitted a degree of discretion by the controller. However, that discretion was conditional upon a valid determination of collision risk and the maintenance of separation standards. Consequently, MATS 6-2-3 paragraph 32 was not appropriate to the issuing of the take-off clearance, as the controller had not positively identified the relative positions of the aircraft.

Summary

The aerodrome controller cleared VH-CZO for a night-time take-off from the Brisbane runway 01, believing that VH-OGG, after landing, had vacated the runway onto the high-speed taxiway A4S. At the time, CZO was at the A7 holding point. The crew of OGG alerted the controller (and the crew of CZO) that they were on the active runway. Shortly after, the controller asked the crew to confirm that they were on taxiway A4S and was advised that they were not. Aware that CZO had not lined up on the runway, the controller did not cancel the take-off clearance, but monitored the situation until OGG vacated the runway at taxiway A4.

The high-speed taxiway A4S was 1,900 m from the runway 01 threshold, and taxiway A4 was 2,310 m from the 01 threshold. Taxiway A4 required that the crew turn the aircraft through 90 degrees to exit the runway.

Taxiway A4S was equipped with uni-directional centreline lighting, which was not visible from the control tower. This made it difficult in conditions of reduced visibility for controllers to determine that an aircraft had vacated the runway and was on the high-speed taxiway. However, in visual meteorological conditions at night, it was not normal practice for controllers to ask crews to report when their aircraft was clear of the runway.

The Manual of Air Traffic Services (MATS) 6-3-1 paragraph 2 stated:

"When take-off or landing separation is based on the position of the preceding landing or taxiing aircraft and visual determination, particularly at night or in reduced visibility, is limited by poor azimuth resolution or other factors, the pilot of that aircraft shall be instructed to report when the aircraft has:

  1. crossed and is clear of a runway intersection; or
  2. stopped short of a runway strip; or
  3. vacated the runway."

The MATS 6-2-3, paragraph 31 stated:

"Before clearing an aircraft for take-off, and immediately before take-off is commenced, the tower controller shall make a visual check from the control tower to determine as far as practicable, that the take-off path is not obstructed. If the take-off path is obstructed, take-off clearance shall be withheld or cancelled as appropriate, until the obstruction no longer exists."

The prescribed separation standard was detailed in MATS 6-3-4 paragraph 24. The standard required that a departing aircraft shall not be permitted to commence take-off until the landing aircraft has vacated and is taxiing away from the runway.

The controller cleared CZO for take-off using the provisions of MATS 6-2-3 paragraph 32. This paragraph stated:

"Take-off clearance need not be withheld until prescribed separation exists if, in the opinion of the controller, no collision risk exists and there is reasonable assurance that separation will exist when the aircraft commences take-off roll."

Occurrence summary

Investigation number 199902114
Occurrence date 23/04/1999
Location Brisbane, Aero.
State Queensland
Report release date 11/10/1999
Report status Final
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 The Boeing Company
Model 737
Registration VH-CZO
Serial number 24304
Sector Jet
Operation type Air Transport High Capacity
Departure point Brisbane, QLD
Destination Cairns, QLD
Damage Nil

Aircraft details

Manufacturer The Boeing Company
Model 767
Registration VH-OGG
Serial number 24929
Sector Jet
Operation type Air Transport High Capacity
Departure point Sydney, NSW
Destination Brisbane, QLD
Damage Nil

Boeing 737-377, VH-CZC

Safety Action

As a result of the investigation, Airservices Australia have: Designed a new runway 15 SWIFT standard instrument departure to minimise the possibility of conflict in similar circumstances. This procedure is scheduled for publication on 24 February 2000; and Initiated regular discussion sessions amongst Cairns air traffic controllers to, among other things, review techniques used with successive departures. The first of these meetings took place on 24 June 1999.

Significant Factors

  1. The runway 15 SWIFT standard instrument departure allowed the possibility of a following aircraft turning inside a preceding aircraft.
  2. The performance of the B737-400 series aircraft was superior to that of the B737-300 series aircraft.
  3. The use of minimum departure separation standards was inappropriate.
  4. The decision of the approach/departures controller to concentrate on data entry tasks during the departure sequence was not sound practice.

Analysis

Controllers at Cairns considered that the aircraft were "like types" for the purposes of departure standards and neither the aerodrome controller nor the approach/departures controller considered increasing the separation requirements specified in Local Instructions. However, Boeing 737-400 series aircraft are known to normally out-perform the Boeing 737-300 series.

Separation standards used for consecutive departures allowed controllers to increase the minimum distance at their discretion. On this occasion it was not increased and, although the runway departure standard was not breached, the decision did not allow for any unexpected manoeuvre by either aircraft. Both crews acted in accordance with the standard instrument departure and the closure was the effect of aircraft performance.

The approach/departures controller elected to input data to the air traffic computer during the departure sequence. Although these actions were necessary, they were labour intensive and diverted his attention from the air situation display. They were not urgent and the decision resulted in the controller not having his full attention on the relative positions of the aircraft when they first appeared on the display.

The design of the SWIFT 2 standard instrument departure did not guarantee separation assurance. Whenever the second aircraft reached 4,000 ft prior to the first aircraft (whatever the reason) a reduction in horizontal separation was likely.

Summary

VH-CZC, a Boeing 737-300, had taxied at Cairns for departure from runway 15 bound for Sydney.

VH-TJW, a Boeing 737-400, had taxied after CZC, also for a departure from runway 15 bound for Brisbane.

Both crews had been cleared via the runway 15 SWIFT 2 standard instrument departure. That procedure required crews to turn their aircraft at the earlier of 400 ft or the departure end of the runway and then track to 030 degrees M until climbing through 4,000 ft. At that point the aircraft should be turned right onto a track of 170 degrees M to intercept the 139 degrees radial of the Cairns VOR (VHF navigation aid). The SWIFT 2 standard instrument departure was designed to counter the limitations of high terrain surrounding Cairns aerodrome and the tracking requirements of inbound aircraft from the south and east.

At 0604:15 Eastern Standard Time, the aerodrome controller coordinated the two planned departures with the approach/departures controller using the phrase "next CZC followed by TJW". The reply was "CZC unrestricted, TJW unrestricted". That instruction authorised the aerodrome controller to allow the takeoffs in accordance with Cairns Local Instruction TOWER-20, which stated that the aerodrome controller must ensure that 3 NM separation between aircraft would exist prior to the second aircraft passing the upwind end of the runway.

At 0604:48, the crew of CZC was cleared for take-off and at 0606:43, the crew of TJW was cleared for take-off. Radar analysis showed that both aircraft commenced a left turn at approximately 400 ft at, or about, the departure end of the runway and that the required 3 NM spacing was achieved.

The approach/departures controller had approved a request for a change of level from a pilot of an aircraft that had departed Cairns approximately 7 minutes earlier. After issuing the departure clearances, the controller commenced the process of making the change in the air traffic computer; an action that required nine clicks of the mouse. In order to make this change, the controller looked away from the air situation display (which was on the main screen) and used the auxiliary screen to observe the flight plan window while using the keyboard to input the data.

While the controller was performing the information change task, the crews of the departing aircraft contacted him as required. The controller acknowledged the radio broadcasts then returned to the data input task. He did not continue to check the positional information on the air situation display. A few moments later, he glanced at the display and realised that TJW had turned earlier than CZC and was also out-climbing that aircraft. As he was about to take corrective action, the controller saw that TJW had climbed through 4,000 ft and had commenced the right turn onto a heading of 170 degrees M. The manoeuvre had placed TJW on a track inside that of CZC and led to a rapid reduction of horizontal separation to less than the required standard of 3 NM. The vertical separation standard of 1,000 ft had not been achieved at the time. Radar analysis showed that the aircraft passed 1.7 NM horizontally and approximately 400 ft vertically apart.

The controller immediately cancelled the standard instrument departure for TJW and issued the crew with a radar heading of 100 degrees M to ensure that, although separation standards would be breached, TJW would pass behind CZC. The crew of TJW reported that they had the other aircraft in sight and monitored their flight path to ensure that they remained clear of that aircraft. Both crews subsequently reported that they received a traffic alert and collision avoidance system (TCAS) advice.

CZC, the B737-300 series aircraft, had taken 1 minute and 56 seconds to reach 4,000 ft whereas TJW, the B737-400 series aircraft, took only 1 minute and 27 seconds to pass the same altitude. In addition, the initial opening speed created by the departure spacing off the runway had reduced to zero within 1 minute and 30 seconds of the departure of TJW.

Occurrence summary

Investigation number 199902003
Occurrence date 03/05/1999
Location 13 km E Cairns, Aero.
State Queensland
Report release date 09/06/2000
Report status Final
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 The Boeing Company
Model 737
Registration VH-CZC
Serial number 23655
Sector Jet
Operation type Air Transport High Capacity
Departure point Cairns, QLD
Destination Sydney, NSW
Damage Nil

Aircraft details

Manufacturer The Boeing Company
Model 737
Registration VH-TJW
Serial number 26961
Sector Jet
Operation type Air Transport High Capacity
Departure point Cairns, QLD
Destination Brisbane, QLD
Damage Nil

Cessna 310, VH-JOR

Significant Factors

  1. Coordination between the tower and terminal staff was unprofessional and led to confusion as to the status of visual approaches.
  2. Various controllers had different interpretations of the meaning of "west" in relation to aircraft approaches.
  3. A significant deterioration in the prevailing weather conditions coincided with the start of a busy arrival sequence.

Analysis

As the flow controller was planning the arrival sequence, he needed to take account of the type of approach available to each aircraft. Even though visual approaches from the south-west had been in use during the morning, tower staff had advised the terminal area controllers that they were no longer available. However, the flow and approach controllers elected to continue with the plan that had the C310 as number one in the sequence and hoped that the pilot would be able to complete a visual approach. The conversations between tower and terminal area controllers in regard to the status of aircraft approaches took place between various control positions, each in partial isolation. Consequently, there was no coordinated response between tower and terminal area staff, and some confusion arose as to the status of such approaches.

As the C310 had been the first aircraft in a busy traffic sequence, the C310 needed to be repositioned when the pilot was unable to make a visual approach. When this re-sequencing occurred, pressure was on the system to try to make up some time to allow for the re-introduction of the C310. In order to minimise the delay, the approach controller had attempted to reduce the distance between the C310 and the AC50 by use of techniques that were not appropriate for the prevailing weather conditions.

Summary

The Cessna 310 (C310) was the first aircraft in a busy arrival sequence and had been programmed by the flow controller for a visual approach to right base for runway 15. The weather had been fluctuating around marginal visual meteorological conditions for some hours and although the cloud base was generally 2,500 ft, it was lower in passing, heavier showers. The visibility was generally 8 km but reduced to 3,000 - 4,000 m in the showers.

When the pilot of the C310 reported that he was unable to establish visual contact with the ground, the approach controller had to change the arrival plan and vector the aircraft to the east of the aerodrome to facilitate further descent. This amendment to the traffic management plan was intended to assist the pilot to become clear of cloud but it necessitated extra track miles for the aircraft. Consequently, an adjustment to the arrival sequence was required and the C310 became number three in the landing order. This change also meant that the timing of sequential landings had fallen behind that which the flow controller had planned and following aircraft would need to be delayed.

The Aero Commander 500 S (AC50) was the fourth aircraft in the sequence and had been held outside controlled airspace by the approach controller until a separation standard could be guaranteed with the other aircraft.

During the course of these events, several verbal exchanges took place between various tower and terminal control area staff regarding the availability of visual approaches in the deteriorating weather conditions. It was agreed that all jet aircraft, and other aircraft arriving from the north and west, would be processed for instrument landing system (ILS) approaches. While these conversations were taking place, the weather had deteriorated such that the cloud base was 1,500 ft and the visibility was generally 3,000 - 4,000 m.

The terminology of what was "north and west" was never positively determined. The flow controller thought that the track of the C310 (via Copperlode Dam - approximately 210 degrees from Cairns) was south-west and not west. Other controllers considered anything west of 180 degrees was "west" and would not have used this track for a visual approach under the prevailing weather conditions.

When the pilot of the C310 reported that he was "visual", the approach controller authorised a visual approach and transferred the pilot to the tower control frequency. Shortly after, he issued a clearance for the AC50 to enter controlled airspace at 1,000 ft. He judged that, as their observed ground speeds were similar, he would be able to maintain the required radar standard of 3 NM while keeping the aircraft comparatively close to each other in order to minimise delays in the landing sequence.

As he was monitoring the progress of the aircraft, the approach controller noticed that the groundspeed of the C310 had reduced on final approach and that the 3 NM separation with the AC50 was unlikely to be maintained. He asked the aerodrome controller if he could use the "sight and follow" procedure, which would allow the pilot of the AC50 to establish and maintain visual separation with the C310 and, consequently, allow the distance between the aircraft to reduce to below 3 NM. However, due to the deteriorating weather and his resultant inability to sight the aircraft, the aerodrome controller declined the request.

As the AC50 closed on the C310, the approach controller realised that the 3 NM standard was not going to be maintained and asked the aerodrome controller to visually separate the two aircraft, a procedure that would again allow the aircraft to proceed with less than the required radar standard. Once again, the aerodrome controller declined the request as he could not see the aircraft in the prevailing weather conditions.

The approach controller then decided to re-sequence the AC50 and issued instructions for the pilot to turn away from the approach. As the aircraft turned, the horizontal separation reduced to 2.8 NM. An infringement of separation standards had occurred.

Occurrence summary

Investigation number 199901797
Occurrence date 24/03/1999
Location 9 km NNW Cairns, Aero
State Queensland
Report release date 29/05/2000
Report status Final
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 310
Registration VH-JOR
Serial number 4040642
Sector Piston
Operation type Charter
Departure point Kidston, QLD
Destination Cairns, QLD
Damage Nil

Aircraft details

Manufacturer Aero Commander
Model 500
Registration VH-UJB
Serial number 3152
Sector Piston
Operation type Air Transport Low Capacity
Departure point Lizard Island, QLD
Destination Cairns, QLD
Damage Nil

Boeing 747-438, VH-OJC

Safety Action

Local Safety Action

Airservices Australia Sydney District is investigating whether there is a need to roster staff for the flow position prior to 0600, to ensure that aircraft arriving at the end of the curfew are sequenced appropriately. This task is scheduled for completion by October 1999. In the interim, the evening shift centre coordinator controller will monitor the forecast weather and pending traffic numbers for the following morning, and provide staff for flow duties if warranted

Summary

The Sydney approach radar controller was operating a combined departures/approach service during the early morning shift when staffing was minimal, and had been on duty since 0245.

For noise abatement reasons, runway 34 was the preferred runway for arrivals prior to 0600, but was not utilised due to an excessive downwind component. As a result, a number of inbound aircraft were required to hold, in order to land on runway 16 after 0600. The approach controller was required to nominate to the adjacent sector controllers the minimum longitudinal spacing required between successive arriving aircraft. Local procedures recommended a 15 NM spacing. The approach controller requested and was provided with 10 NM longitudinal spacing between aircraft, including a Boeing 747 (B747) approaching from the south-west, which was sequenced to land ahead of a Boeing 767 (B767) arriving from the north. The controller was also managing a number of other arriving aircraft.

Independent visual approaches (IVAs) to runways 16L and 16R were in use. The approach controller subsequently amended the initial arrival sequence when it became apparent that the B767 would arrive earlier than the B747. This placed those aircraft as number two (runway 16L) and three (runway 16R) respectively in the arrival sequence.

The crew of the B767 were vectored to intercept the runway 16L localiser at approximately 30 NM, and instructed to report when they had that runway in sight. The B747 crew had been instructed to turn right onto a heading of 120 degrees in order to intercept the runway 16R localiser. They were subsequently cleared to make a visual approach after reporting that they had runway 16R in sight. However, as the B747 turned onto final, the aircraft drifted to the left through the centreline of the 16R approach path, triggering a resolution advisory, from its traffic alert and collision avoidance system (TCAS), for the crew to descend. The approach controller observed the close proximity of the aircraft and issued instructions to both crews to turn their respective aircraft from final using a "breakout" procedure. The B767 was sighted by the B747 crew as their aircraft passed through the final approach path. The lateral distance between the aircraft was reduced to 0.3 NM at a time when the vertical separation was 500 ft.

Normally, IVAs are conducted by a director controller using specific procedures, which included the use of a 20 NM scale on the radar display, and a map for intercept guidance. In this instance the approach controller had his display set to a scale greater than 20 NM, and did not use the IVA map. Controllers are also required to provide a radar vector not exceeding 30 degrees for intercept of the localiser. The vector issued to the B747 crew provided a 36-degree intercept of the localiser. Moreover, crews subject to IVA procedures are responsible for a number of actions detailed in the Aeronautical Information Publication (ENR 1.1 - 48, paragraph 36.3.1) including, "ensuring that the runway centreline is not crossed during intercept".

Just prior to the occurrence, two controllers arrived to commence the morning shift from 0600. One of these would have normally replaced the overnight controller; however, due to the number of arriving aircraft, these controllers were instructed to staff the director and flow control positions. A third controller arrived and was waiting to take over from the approach controller when the incident occurred. However, the approach controller's workload prevented him from handing over responsibility for the position at that time.

The approach controller limited his options by coordinating the provision of a 10 NM spacing between successive arriving aircraft. As a result, when the crew of the B747 allowed their aircraft to pass through the extended centreline there was limited margin for error, resulting in an immediate traffic confliction. The performance of the controller was probably degraded by the effects of fatigue and workload. The performance of the B747 crew was likely to have been affected by similar factors.

The provision of additional staff prior to 0600 to provide either a flow or director controller to assist the approach controller, or to relieve the approach controller earlier, would have reduced the approach controller's workload during a critical period.

Occurrence summary

Investigation number 199901401
Occurrence date 07/04/1999
Location 22 km NNW Sydney, (VOR)
State New South Wales
Report release date 26/07/1999
Report status Final
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 The Boeing Company
Model 747
Registration VH-OJC
Serial number 24406
Sector Jet
Operation type Air Transport High Capacity
Departure point SINGAPORE
Destination Sydney, NSW
Damage Nil

Aircraft details

Manufacturer The Boeing Company
Model 767
Registration VH-RML
Serial number 22980
Sector Jet
Operation type Air Transport High Capacity
Departure point Brisbane, QLD
Destination Sydney, NSW
Damage Nil

Saab SF-340B, VH-KDQ

Summary

A Saab SF-340B (Saab) was conducting a scheduled passenger service from Canberra to Sydney and had been assigned descent to 7,000 ft by the Approach South radar controller in order to maintain the minimum vertical separation standard of 1,000 ft, between the Saab and a Piper Chieftain. The Chieftain was ahead in the approach sequence and had been assigned descent to 6,000 ft. The two aircraft were separated laterally by distances greater than the minimum radar separation standard of 3 NM, but their respective tracks were converging.

The controller requested the Saab crew to expedite descent to 7,000 ft. That instruction was read back by the pilot in command, however, the readback was indistinct. The controller repeated the request "Expedite descent to 7,000 ft". The pilot in command acknowledged that transmission with the aircraft's callsign. Shortly after, the controller observed that the altitude readout for the Saab was indicating that the aircraft was descending through 7,000 ft. The controller queried the Saab crew to confirm that they were maintaining 7,000 ft, then instructed the crew to turn left onto a heading of 360 degrees due to the traffic ahead. As the crew responded to that instruction, the lateral and vertical separation between the Saab and the Chieftain reduced to 1.5 NM and 500 ft respectively.

The traffic sequence had been busy, with the controller endeavouring to change the landing sequence by placing the Saab ahead of the Chieftain. The controller was required to monitor the lateral and vertical separation between a number of aircraft as two standard arrival routes converged. As a consequence, the controller was required to establish vertical separation to ensure separation was maintained between all aircraft as they approached an area of lateral conflict.

All radio transmissions between the controller and the Saab were recorded. A review of the recorded information indicated that the altitudes assigned by the controller, and the readbacks from the Saab crew, were clear and distinct except for the response to the controller's initial request to expedite descent. The Saab crew were unable to explain why they were not alerted to the possibility of an incorrect altitude following the controller's reiteration of the request to expedite descent to 7,000 ft.

The Aeronautical Information Publication GEN 3.4-10 paragraph 4.4 details readback requirements for flight crew. For other than a route clearance, "the key elements of clearances, instructions or information must be read back ensuring sufficient detail is included to clearly indicate compliance". A level instruction must be read back. In this occurrence, the controller did not expect a readback of the altitude, because the previously assigned altitude had not changed. The indistinct response from the Saab crew caused the controller to doubt that his request had been understood, so he repeated the request. When that transmission was acknowledged by the pilot in command, the controller believed that the crew now understood his request to expedite descent to 7,000 ft.

The Saab crew believed that an altitude clearance of 6,000 ft had been issued between the time the controller assigned them 7,000 ft, and when the controller requested that they expedite descent to 7,000 ft. However, the recorded transmissions did not include any reference to 6,000 ft directed to, or received from, the Saab crew during that period.

Occurrence summary

Investigation number 199901070
Occurrence date 17/03/1999
Location 28 km WSW Sydney, (VOR)
State New South Wales
Report release date 27/04/1999
Report status Final
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 Saab Aircraft Co.
Model 340
Registration VH-KDQ
Serial number 340B-325
Sector Turboprop
Operation type Air Transport Low Capacity
Departure point Canberra,, ACT
Destination Sydney, NSW
Damage Nil

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-31
Registration VH-JVD
Serial number 31-7852041
Sector Piston
Operation type Air Transport Low Capacity
Departure point Shepparton, VIC
Destination Sydney, NSW
Damage Nil

Short Bros Pty Ltd SD360-300 , SH3728

Safety Action

Local safety action

As a result of the investigation, Airservices Australia has:

  1. Introduced a revised missed approach procedure on 17 June 1999. This procedure changed the outbound heading from 030 degrees to 015 degrees, and
  2. Introduced Cairns Local Instruction TLI99/105 which restricted the available headings for departures to 030 degrees only, when missed approaches are likely.

The combined effect of these actions was to provide a nominal 15 degree buffer between the departure and missed approach paths.

Airservices Australia management at Cairns has introduced a program of regular in-flight emergency response and abnormal situation refresher training for tower staff. The first course was completed between 19 - 23 July 1999.

Recommendation

As a result of the investigation the Australian Transport Safety Bureau (formerly Bureau of Air Safety Investigation) issued the following recommendation to Airservices Australia on 23 December 1999:

R19990227

That Airservices Australia review ongoing refresher training for all staff. In particular, to ensure that adequate discussion and simulation of unusual situations pertinent to specific locations is included in the syllabus.

Airservices Australia responded on 7 February 2000 accepting the recommendation.

The Australian Transport Safety Bureau classified the response as CLOSED - ACCEPTED

Significant Factors

  1. The geographical restraints of high terrain surrounding the Cairns aerodrome required all aircraft movements in instrument meteorological conditions to proceed into a 40 degree sector of airspace.
  2. The Cairns runway 15 missed approach and departure procedures required all aircraft to turn into the same narrow sector of airspace.
  3. The weather conditions were such that missed approaches were likely and that the aerodrome controller would not be able to provide visual separation.
  4. The departure instructions for the Cessna placed that aircraft into a direct track conflict with the runway 15 missed approach path.
  5. The aerodrome controller's decision not to increase the cut-off distance beyond 8NM resulted in a reduction of the safety buffers in the separation plan.
  6. The aerodrome controller's separation plan relied on the performance of the Cessna being sufficient to climb above the Shorts.
  7. The performance of the Cessna was not as good as that expected by the aerodrome controller.
  8. The weather conditions encountered by the Cessna were such that the pilot needed to reduce the fair weather climb performance for operational safety reasons.
  9. The coordination between the aerodrome controller and the approach controller was inadequate.
  10. The Cairns Local Instructions did not authorise the use of radar by the aerodrome controller for separation purposes.
  11. Neither the aerodrome controller nor the approach controller applied positive separation assurance techniques.
  12. Cairns tower controllers had not received adequate ongoing refresher training in emergency and/or unusual situations.

Analysis

Weather

The general conditions of low cloud and heavy rain made any visual reference unlikely for both pilots and controllers. As both crews were operating in instrument flying conditions, the chances of their making visual contact with the other aircraft were low. Therefore, the presence of a break in the cloud of sufficient size to allow such sighting was of a fortuitous nature and could not be relied on for tactical planning purposes.

Missed approach and departure procedures

These procedures were so constrained by terrain considerations that, whenever an aircraft commenced a missed approach, a conflict would occur unless the aerodrome controller could visually monitor the aircraft with any departure until a specific separation standard was achieved.

Even using the 030 degrees heading option for the departure, the missed approach procedure would have, at best, resulted in the aircraft tracking parallel to each other approximately 1 -1.5 NM apart; a situation that would still result in an infringement of separation standards if no vertical separation existed. As the terrain prevented a departure heading east of 030 degrees, the situation would have required the missed approach track to be north-west of 030 degrees to guarantee a divergence.

Air traffic control procedures

MATS 6-4-3 allowed an unrestricted departure prior to an arriving aircraft commencing final approach provided a specific lateral separation standard of a minimum of 45 degrees between the departure track and the reciprocal of the final approach track existed. If the departure heading had been between 015 and 030 degrees, this standard would have been achieved. However, because of the limitations of the missed approach track and the weather situation, the maintenance of the separation standard could not be expected and an alternative standard would need to be established.

MATS also allowed for a departure when an aircraft had commenced final approach provided a reasonable assurance existed that a landing could be accomplished or that separation standards could be applied between the aircraft in a missed approach and the aircraft desiring take-off clearance. In this case the weather precluded any guarantee of the Shorts landing and no separation assurance was in place.

It may have been possible to use the lateral separation standard of 45 degrees between tracks if the departure heading had been between 015 - 030 degrees. However, even if this option had been taken, MATS required an allowance to be made when, among other things, missed approaches were likely, and/or a faster aircraft was approaching in respect of a slower aircraft taking off. Both circumstances applied to this occurrence.

Cairns Local Instructions (TWR - 29) gave further guidance in the specific case of runway 15 when "... consideration must be given to increase the cut-off distance used between the landing aircraft; and the aircraft commencing take-off." Because the Shorts was between 9 - 7.5 NM during the time that the Cessna was processed for departure, some doubt existed as to which circumstance applied. In either case the departure was conditional on a separation standard being applied and, as the heading issued was not 45 degrees from the approach track, neither of the lateral separation standards were useable.

As the aircraft were on conflicting tracks without any vertical separation established, a radar vector may have been appropriate. The approach controller was rated to perform the task but did not have either crew on frequency. The aerodrome controller had the radio contact but was not rated to perform the task. However, as the aircraft came into close proximity, an emergency radar vector by the aerodrome controller may have increased the minimum distance between the aircraft. MATS 4-1-1 para 3.f authorises any controller to take any necessary action to ensure aircraft safety.

Separation standards

Procedural lateral separation with the final approach path was possible under the provisions of MATS but not under the terms of the departure instructions issued by the approach controller. As the tracks of both aircraft were not laterally separated (a situation that became a direct conflict when the Shorts commenced a missed approach) an alternative form of separation was required.

The aerodrome controller may use visual separation based on judgement and experience to provide initial separation until a more specific standard is achieved. However, in the prevailing weather conditions adequate visual contact with both aircraft was not possible. Therefore, this standard was not appropriate.

Radar separation of 3 NM was not appropriate as the conflict occurred within 2 NM of the aerodrome. In addition, as both aircraft were heading in the same sector of airspace, the likelihood was that the standard would not be achieved for some time. Longitudinal standards were also unlikely to be attained in the short term for similar reasons.

Vertical separation was applicable but relied on the Cessna becoming established 1,000 ft above the Shorts. As the Cessna was starting from a position below that of the Shorts, the standard was not available during the initial climb phase. A standard of 500 ft was useable initially as a form of emergency separation. However, the limitations were the same as for the 1,000 ft standard.

There was an option to amend the departure heading for the Cessna to provide initial lateral separation; the limitations of this option have been discussed above. Consequently, no separation standard existed at the time the Cessna departed and separation assurance was neither achieved nor positively sought until the conflict was unavoidable.

Aircraft performance

Although the aerodrome controller expected the Cessna to out-climb the Shorts, operational factors were such that the opposite was the case. MATS 4-1-1 paragraph 13 informed controllers of such a possibility. In addition, in the case of the Cessna, several factors in the first 4 minutes of flight indicated that operations were not as expected.

Aerodrome controller

The controller had a traffic management plan that relied on an expected aircraft performance of the Cessna and Shorts types. This expectation was based on his observations since arriving at Cairns. The plan was twofold; either the Cessna would out-climb the Shorts and vertical separation would be established, or the Cessna would reach the point at which the missed approach track would conflict with the departure track first and pass clear of that point before the Shorts entered the area of conflict. There was no consultation with the approach controller and no discussion of any alternative plan even though the weather conditions precluded visual separation as an initial standard.

As the flight of the Cessna progressed, the controller realised that the climb was not as good as expected but elected to continue with his original plan hoping that one of the alternatives would still work. Separation assurance had not been implemented.

When the crew of the Shorts reported maintaining 1,000 ft the controller established that the Cessna had left 1,500 ft, thus indicating a 500 ft emergency separation standard. However, no instruction was issued to the crew of the Shorts other than a climb to 1,500 ft. Additionally, the poor quality of the radio transmission and the mention of 1,500 (ft) by the crew should have raised sufficient doubt in the controller's mind to warrant clarification.

Although the aerodrome controller considered that the radar altitude read-out from the SD36 was erratic, other controllers expressed concern over the fact that they saw the altitudes of the aircraft indicate similar levels as they approached the point of closest proximity. When the approach controller questioned the separation status, albeit with an oblique comment, the reply was that there was "not much to do mate, ..." indicating that he had done all that was required, even though no separation standard had been achieved. However, a few seconds later he issued updated traffic information to the crew of the Shorts indicating that the other aircraft was in the same position at the same level.

The passing of traffic information when an aircraft is in cloud and heavy rain and the crew are flying the aircraft with reference to instruments, was unlikely to result in a sighting; even though it did in this case. However, passing traffic information when a near collision is imminent is sound practice.

Approach controller

The controller had been surprised when he realised that the aerodrome controller had cleared the Cessna for take-off ahead of the arriving Shorts. He realised that if a missed approach resulted, then a conflict was imminent. He assumed that the aerodrome controller had accepted separation responsibility and chose to allow him to continue with that role but made no attempt to establish what standard was being used. Even though the last known information was that the Shorts was likely to conduct a missed approach and visual separation was unlikely, no coordination was instigated to adequately determine the status of separation in his airspace.

Other controllers reported that as the situation developed, they had asked what was happening and made comments such as "do something". The reply was that the aerodrome controller was providing the separation. Eventually he could see that the radar indicated a near collision situation and questioned the aerodrome controller, but this was with very ambiguous words and when the aircraft were only 10 seconds from the point of closest proximity.

Training

The circumstances surrounding the occurrence were not often experienced at Cairns. Consequently, the combination of events were such that many controllers had never seen this scenario before and were not fully familiar with how to resolve the confliction. The procedures were such that this type of incident could have happened at any time in recent years.

Although initial training covered the procedures contained in Local Instructions, some controllers could not remember any recent "Team" discussions on unusual or emergency situations and formal abnormal situation refresher training had not been regularly undertaken.

Pilot of the Cessna

Operational decisions were taken with the safety of the flight in mind and as a result of the prevailing weather conditions; the full effect of which were not known until actually encountered.

The pilot had intended to comply with the departure instructions as he commenced take-off roll but found himself unable to continue with that plan as a result of constant turbulence and downdrafts.

Crew of the Shorts

The crew had made a standard missed approach decision and the pilot in command had intended to maintain the aircraft at 1,000 ft initially. However, the instruction to the co-pilot was made at the same time as the pilot in command was broadcasting to air traffic control. The words were heard by the aerodrome controller but not by the co-pilot. This situation led to a misunderstanding, in that the controller thought the aircraft was going to maintain 1,000 ft but the crew continued to climb to their assigned level of 1,500 ft.

Summary

Sequence of events

The Short Bros SD 3-60-300 (Shorts) was being radar vectored by air traffic control for an instrument landing system (ILS) approach to runway 15 at Cairns.

The weather conditions were fluctuating about the landing minima with low cloud and rain passing through the local area in general "stream" conditions. The automatic terminal information service was quoting a cloud base of 1,000 ft with lower patches and visibility reduced to 5,000 m in passing showers. The conditions were observed to deteriorate during periods of heavy rain showers and the air traffic control tower staff updated each crew as appropriate.

As the Shorts intercepted the final approach path at 14 NM from touchdown, the aerodrome controller informed the approach controller that the weather had deteriorated at the aerodrome and that there was a likelihood that the Shorts would carry out a missed approach. The approach controller informed the crew and transferred them to the tower frequency so that the aerodrome controller could provide timely updates of the changing weather situation.

At 0744:05 Eastern Standard Time, the pilot of a Cessna 208 (Cessna) reported ready to depart on the aerodrome control frequency and was instructed to line-up. At that time, the Shorts was approximately 9 NM from touchdown with a ground speed of 120 kts.

The aerodrome controller received a departure instruction of "Left 360 unrestricted" from the approach controller (who was also providing the departure service). The pilot of the Cessna was then given a take-off clearance in accordance with that instruction but with an additional instruction to remain on the aerodrome controller's frequency when airborne. The aircraft commenced take off roll at approximately 0745:00; when the Shorts was approximately 7.5 NM from the runway 15 threshold.

At 0745:05, the crew of the Shorts was informed that the rain was increasing at the field and that the runway lights were on stage 6; the maximum intensity.

At 0746:04, the pilot of the Cessna was asked to expedite his climb through 2,000 ft and, at 0746:30, the crew of the Shorts was cleared to land.

At 0748:29, the pilot of the C208 apologised for the slow rate of climb and commented that he was "... just doing his best". At about the same time, the crew of the Shorts commenced a missed approach and, at 0748:39, they were instructed to maintain 1,500 ft and informed that there was "... traffic abeam you now at the 9 o'clock position". That transmission by the aerodrome controller was followed, at 0748:56, by a broadcast to the pilot of the Cessna saying "... caution traffic in the missed approach".

At 0749:07, the aerodrome controller updated the traffic information to the crew of the Shorts with "... caution, the traffic is in your 12 o'clock position at half a mile". The reply was garbled and included the statement "... we are maintaining one thousand at the moment..." which was followed by words that were not completely discernible but included "... one thousand five hundred..."

At 0749:27, the pilot of the Cessna was instructed to report leaving 1,500 ft and replied that he had left that altitude. A subsequent radar analysis indicated that the aircraft was climbing through 1,550 ft at that time.

At 0749:40, the approach controller checked with the aerodrome controller to ascertain his plan for separation. The reply was that there was "... not much to do". However, at 0749:51, the aerodrome controller broadcast to the crew of the Shorts that radar indicated traffic in the same position at the same level. The reply was that the crew had sighted the Cessna and were passing that aircraft.

Radar analysis indicated that the aircraft had passed at approximately 0749:50 with a minimum horizontal distance of about 70m and a vertical displacement of between 100 - 200 ft. The required separation standard was either 3 NM horizontally or 1,000ft vertically. There had been an infringement of separation standards.

Missed approach and departure procedures

Due to the constraints of terrain surrounding the Cairns aerodrome, both the missed approach and departure procedures required tracking in a 40 degree sector to the north-east. The missed approach required an initial climb straight ahead to the Middle Marker, then a climbing left turn onto a heading of 030 degrees to intercept the 045 radial of the Cairns VOR (Very High Frequency navigation aid), with a climb to 4,000 ft or a level assigned by air traffic control.

The standard instrument departure required a left turn at the earlier of 400 ft or the departure end of the runway, onto an assigned heading between 350 - 030 degrees. The lowest altitude for radar vectoring in this sector was between 1,000ft and 3,300ft depending on the precise position of the aircraft at the time.

This combination of tracking requirements resulted in a guaranteed tracking conflict whenever a missed approach was commenced when a departing aircraft was within 3NM of the aerodrome. Furthermore, an infringement of separation standards would occur whenever a missed approach was carried out in instrument meteorological conditions without vertical separation being established.

Separation standards

Air traffic controllers were limited to a minimum altitude of 1,500 ft for terrain clearance in the case of a missed approach. To establish the vertical separation standard of 1,000 ft (or 500 ft in an emergency), a departing aircraft would have to be at or above 2,500 ft (or 2,000 ft in an emergency). When the Shorts was established in the missed approach turn, it was climbing through 700 ft while the Cessna had left 1,300 ft.

The radar standard was not achieved as the tracks crossed each other approximately 2NM north-east of the runway. As the aircraft had to track in the same narrow sector of airspace, it would have been some minutes before a radar standard could be established.

Visual separation was not an option due to the prevailing weather conditions. The aerodrome controller could not see either aircraft as they came into conflict.

Lateral separation - the Manual of Air Traffic Services section 6-4-3 stated "lateral separation is considered to exist between an arriving aircraft that subsequently commenced final approach, and a departing aircraft that has been cleared on a segregated flight path". That is, a situation where the departing aircraft will not be manoeuvring within 45 degrees of the reciprocal of the final approach path while an aircraft is on the final approach path. The assigned heading of 360 degrees for the Cessna did not comply with that standard.

Longitudinal separation standards did not apply because they required distances greater than those required for radar standards.

Aircraft performance

The Shorts, a 36 passenger aircraft, had seven persons on board and very little freight. Consequently, when the missed approach was commenced, the crew attained a rate of climb of 700 - 800 ft/min. They stated that 300 - 600 ft/min was their expected rate of climb.

The Cessna was at maximum take-off weight and, because of the heavy rain, the pilot had selected the Inertial Separation Handle to bypass mode. That operation helped to divert heavy rain droplets around the engine so that the risk of flame-out was reduced.

When airborne, the pilot of the Cessna experienced severe turbulence and downdrafts, along with buffeting from the gusty wind and heavy rain. The combination of the prevailing weather conditions and the selection of bypass mode resulted in a degraded climb performance from that normally expected. Radar analysis indicated that the Cessna had an average rate of climb of 400 ft/min from take-off to the point of closest proximity and, at times, a rate of climb near zero. The pilot stated that he expected a rate of climb between 800 - 1,200 ft/min.

Air traffic control procedures

The Manual of Air Traffic Services (MATS) section 6-4-3 specified the procedures to be applied in the case of an arriving aircraft and an aircraft taking off. It stated that "a departing aircraft may be permitted to take off during the period before an arriving aircraft will commence its final approach" but goes on to say that such take-off clearance "... is conditional upon the application of separation after take-off is commenced".

Final approach was defined as 8NM from the runway 15 threshold. The aerodrome controller may have complied with the distance requirement as the Cessna was cleared for take-off when the Shorts was approximately 8NM from the threshold.

Cairns Local Instructions (TWR - 29) reinforced the provisions of MATS in the specific instance of the conflicting missed approach and departure headings from runway 15. They stated that "... consideration must be given to increase the cut-off distance used between the landing aircraft and the aircraft commencing take-off when weather conditions are such that visual or radar separation of the overshooting aircraft and departing aircraft cannot occur". Local Instructions did not specify clearly who had the responsibility for separating the missed approach from the departing aircraft. Approach control was responsible for the airspace but the aerodrome controller had to advise the approach controller of the most appropriate heading consistent with the ability to provide separation with other airborne traffic.

Cairns controllers operated in such a way that the aerodrome controller separated an aircraft on the missed approach path with other traffic, using visual separation until an alternative standard could be achieved. As the weather conditions precluded such an option, a specific alternative was required. Tower controllers were not rated to provide radar separation and could only use the radar display "for information". However, Local Instructions specified that it was the aerodrome controller's responsibility to ensure that radar separation existed between an aircraft on short final and not yet in sight and an aircraft becoming airborne.

MATS 6-5-1 allowed a tower controller to provide an uncoordinated radar vector to initiate separation in cases such as a missed approach. However, MATS required Local Instructions to specify the details. Cairns Local Instructions did not specify any such details.

Aerodrome controller

The controller had considered extending the cut-off distance but believed that, as the Shorts had not commenced final approach, he could safely clear the Cessna for take-off. He had witnessed numerous departures by Cessna 208 type aircraft and had an expectancy that the aircraft would climb at a rate which would enable vertical separation to be easily achieved if the Shorts commenced a missed approach. He also expected the Cessna to proceed at a speed that would position that aircraft well ahead of the Shorts at the crossing point of the departure track and the missed approach path.

Although the approach controller had nominal responsibility for the airspace, the aerodrome controller had assumed separation responsibility when he retained the pilot of the Cessna on his radio frequency for departure. As the Cessna departed, the controller observed that it did not turn in accordance with the standard instrument departure instructions but continued for approximately half a mile before commencing the turn. He then noticed that the rate of climb was not as good as he had expected and, at 0746:11, asked the pilot to expedite through 2,000 ft and report leaving 2,000 ft. That instruction was to maintain his traffic management plan of achieving vertical separation with any missed approach procedure and would have provided a 500 ft emergency standard if he maintained the Shorts at 1,500 ft in the missed approach.

As the aircraft closed to within 1.5 NM, the controller gave traffic information to both crews. However, that information did not include the aircraft type, or height, or relative height. The information was only position and distance to the crew of the Shorts and included the words "... traffic abeam you now at the 9 o'clock position". That information was incorrect as the Shorts was in a left turn and the traffic was actually in the 12 o'clock position moving towards the 2 o'clock position. The pilot of the Cessna was advised "Caution, traffic on the missed approach". The controller asked the other controllers in the tower at the time for advice but they were unable, in the time available, to offer an alternative course of action.

When the crew of the Shorts made a broadcast that they were "... maintaining 1,000 (feet) at the moment..." in the middle of a transmission that was broken and partly unintelligible, the controller neither questioned the crew as to their mention of the words "... one thousand five hundred..." during that broadcast nor did he issue an altitude instruction. However, he did obtain an altitude report from the pilot of the Cessna which indicated that the aircraft had left 1,500 ft on climb. The controller's subsequent conversation with the approach controller indicated that he was satisfied with the separation standard saying "...(the Shorts) supposed to be maintaining 1,000 (ft) the other has left 1,500 (ft) ...".

The controller was of the opinion that the altitude read outs from the Shorts were varying so much that he did not know that the aircraft had not maintained 1,000 ft. Radar analysis of the readouts indicated a relatively steady increase in height over the 90 seconds from 0748:30 - 0750:00 but with two "spikes" at approximately 1,100 ft (at approximately time 0749:07) and 1,500 ft (at approximately time 0749:45).

Approach controller

The approach controller had issued the departure instruction for the Cessna believing that, as the Shorts was about 8NM from touchdown, the aerodrome controller would not depart that aircraft until after the arrival, or that the Shorts was in sight and reasonably assured of a landing. However, the terminology used by the aerodrome controller "next CYC" indicated that the Cessna would commence take off within 1 minute of the receipt of a departure instruction.

As the situation developed, the controller monitored the radio frequency of the aerodrome controller to observe the plan for separation. He had heard the requirement to remain with the tower given to the pilot of the Cessna and considered that the aerodrome controller had accepted the responsibility for separation with this action. As the radar display indicated that the aircraft were on conflicting tracks and at similar altitudes, other controllers asked what separation was being applied. The approach controller replied that the aerodrome controller was providing the separation but elected to prompt the tower with the question "you right?". This coordination occurred at 0749:40, approximately 10 seconds before the point of closest proximity, and was the first contact between the controllers since the departure instruction for the Cessna was issued.

Emergency training

The Cairns air traffic controllers had not received regular training in emergency or unusual situations. Tower controllers had last undertaken formal refresher training in October 1997. However, the aerodrome controller had been absent on recreational leave and did not attend the training. He had received formal tuition in dealing with similar circumstances during his aerodrome control training in December 1997 and January 1998.

The aerodrome controller stated that he had experienced only one missed approach due to poor weather in his 3 years at Cairns. As the incident developed, he asked for advice from his fellow tower controllers but as they were occupied with their own tasks, they were unable to give a properly considered response.

Pilot of the Cessna

The pilot was conducting a single pilot operation and had intended to comply with the requirements of the standard instrument departure by turning left at 400 ft or the departure end of the runway. However, when airborne, the initial climb did not proceed as well as expected, with severe turbulence and heavy rain buffeting the aircraft. The airspeed was not increasing as quickly as he would have liked and at the upwind end of the runway the aircraft had only reached an altitude of 200 - 250 ft. Consequently, the pilot elected to continue on runway heading until a more stable climb was achieved. The left turn was commenced at an altitude of 300 ft and an indicated airspeed of approximately 70 kts. There was no broadcast to air traffic control indicating the variation to the standard procedure.

Once the aircraft had turned onto the assigned heading of 360 degrees, the pilot made every effort to maximise the rate of climb but was limited by the aircraft performance in turbulent weather conditions. At 0748:29, he broadcast to the aerodrome controller that he was experiencing a slower than normal rate of climb.

When, at 0748:56, he was given conflicting traffic information, he attempted to sight the other aircraft but found visibility limited in cloud and heavy rain. Shortly after, the aircraft broke into a small clear patch and the pilot saw the Shorts just below and marginally to his left. He estimated that the aircraft would pass just behind his own and elected not to take any evasive action.

Crew of the Shorts

The co-pilot was the flying pilot and, as the aircraft approached the minima, the crew found themselves in cloud, heavy rain and subjected to severe turbulence culminating in their decision to commence a missed approach.

The crew's main preoccupation was to ensure the safe climb-out of their aircraft in the left turn required by the procedure and, as they were experiencing instrument meteorological conditions, their first priority was to fly the aircraft. Consequently, they did not immediately inform air traffic control of their commencing a missed approach. Before they could broadcast any details, the aerodrome controller issued an instruction for them to maintain 1,500 ft and passed traffic information. As they were still in cloud and rain, their lookout was both occasional and of limited effect.

A short time later, the controller issued an updated traffic alert indicating that the other aircraft was half a mile ahead. The response from the pilot in command was that they were maintaining 1,000 ft temporarily but still climbing to 1,500 ft as cleared by air traffic control. The pilot in command had intended to maintain 1,000 ft after the traffic information had been passed but the co-pilot did not hear the instruction as it was said during the radio broadcast to air traffic control and during a period of intense flying activity. As the pilot in command was about to reiterate the maintain 1,000 ft instruction to the co-pilot, the aircraft broke into the same clear patch as the Cessna and they saw that aircraft ahead and slightly above. The co-pilot levelled the aircraft momentarily to ensure that they would pass beneath the Cessna and then continued the climb to 1,500 ft when established clear of it.

Occurrence summary

Investigation number 199901012
Occurrence date 12/03/1999
Location 4 km N Cairns, Aero.
State Queensland
Report release date 27/03/2000
Report status Final
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 Short Bros Pty Ltd
Model SD3-60
Registration VH-SUR
Serial number VH-SUR
Sector Turboprop
Operation type Air Transport Low Capacity
Departure point Townsville, QLD
Destination Cairns, QLD
Damage Nil

Aircraft details

Manufacturer Cessna Aircraft Company
Model 208
Registration VH-CYC
Serial number VH-CYC
Sector Turboprop
Operation type Charter
Departure point Cairns, QLD
Destination Croydon, QLD
Damage Nil