The pilot had planned the flight for an early morning departure from a private airstrip. He had calculated the take-off weight, with four passengers, to be below the maximum allowable for the take-off length available. The weather was fine and clear, with a light crosswind on the gently down sloping grass strip selected for take-off. The grass had been mown short but was wet from a heavy dew.

During the take-off run the pilot became concerned that the aircraft was not accelerating normally, so he closed the throttles and applied maximum braking. However, he was unable to stop the aircraft before it overran the strip end and collided with a fence, rupturing a fuel tank and causing minor damage to the engine cowlings and landing gear doors.

No defects were found with the aircraft that may have affected its performance. It is likely that the wet grass would have increased the take-off distance required and also decreased the aircraft's braking efficiency when the take-off was rejected.

The aircraft had been operating on the mustering flight for about 45 minutes. With the helicopter at 70 feet above the ground and 50 kts indicated airspeed, the pilot reported that he had just commenced a climbing turn to approach a small mob of cattle when he heard a loud noise from the rear of the cabin. The engine oversped and the rotor speed decayed. A forced landing was conducted but the pilot was unable to retain adequate rotor speed to prevent a heavy landing.

The floatplane took-off from a coastal lake in strong gusting winds associated with passing squalls. As the aircraft approached the coast, and flew over the beach at low altitude, it descended until the left float struck the top of a wave. The aircraft nosed over into the ocean and began to sink. The pilot and passenger managed to evacuate the semi submerged aircraft without injury.

The pilot subsequently reported that, after taking off toward the south into the strong wind, he had to turn left at low altitude to avoid a small hill adjacent to the shore. The aircraft had then probably encountered windshear on the downwind side of the hill, which resulted in the unintended loss of altitude and subsequent contact with the water.

After an apparently normal touchdown, the aircraft was observed to become airborne again and began to porpoise. On the third bounce, the nose landing gear collapsed, and the propeller struck the runway before the aircraft came to rest.

The pilot subsequently reported that the approach and touchdown were normal, but he was unable to recover from the bounce with elevator control and did not apply any engine power to recover the situation. His experience on the aircraft type was limited as he had only gained his endorsement the previous day.

FACTUAL INFORMATION

NITE 01, a United States Navy F-14 aircraft, had departed from the Atsugi Naval Air Facility, Japan on an Instrument Flight Rules (IFR) plan that included an exercise within Restricted Area R116. The restricted airspace R116 was used for military exercises, the northern end of which was approximately 6NM south east of the track of the B767. The F14 pilot cancelled his IFR status during his initial climb, choosing to proceed under Visual Flight Rules (VFR) procedures.

The crew of the B767 were approaching flight level (FL) 250 while descending into Narita, Japan, when they received a Traffic Alert and Collision Avoidance System (TCAS) resolution advisory (RA) instruction to climb. During the transition from descent to climb, they saw a military aircraft passing in the opposite direction at high speed, approximately 500 ft below them.

At approximately the same time, the air traffic controller observed radar returns from a VFR aircraft departing R-116 at FL250 and passed this information to the crew of the B767. He also contacted the pilot of the F-14 to establish that pilot's intentions. The B767 was climbing through FL255 (approximately) when the military aircraft passed.

The rules for VFR flight in Japanese airspace were such that a pilot could choose to conduct a flight using a 500 ft separation standard up to FL290 without an airways clearance, provided a listening radio watch was maintained on air traffic control frequencies. These procedures allowed the pilot of the F-14 to leave R-116 under VFR and maintain his own separation, of at least 500 ft, from the B767. He stated that he had the B767 in sight and was listening on the control frequency. Therefore, he had complied with the 500 ft separation standard for VFR flight below FL290.

The aircraft passed with approximately 500 ft vertical separation and no appreciable horizontal separation.

ANALYSIS

The TCAS advice to the B767 crew was a genuine alert as the respective flight paths were within the envelope for a RA alert. In this case, the crew manoeuvred their aircraft to a comparatively safe altitude, allowing the military pilot to pass beneath their aircraft.

SAFETY ACTION

As a result of the investigation, the Japanese Civil Aviation Bureau has requested the United States Air Force (the body responsible for overall military operations in the area) to remind all pilots under their jurisdiction of the proximity of IFR air routes and of the general civil airspace structure, and also to remind their pilots of the requirement to maintain adequate separation from civil aircraft.

Additionally, the Japanese Bureau has asked for military training to be kept, as much as possible, within the specified training areas.

FACTUAL INFORMATION

The pilot in command (PIC) of an instrument flight rules (IFR) Piper Chieftain (PA-31-350), enroute from Bankstown to Coffs Harbour, was cleared via Williamtown to Kempsey at 9,000 ft. The aircraft was overhead Williamtown at 1406 EST and estimated to be at Kempsey at 1440. Williamtown approach coordinated the position report with Sydney flight service, the next air traffic services (ATS) unit responsible for the flight. The planned track of the PA-31-350 remained in Williamtown airspace until approximately 10 NM south-west of Taree. North of this position the flight would be in Class G airspace from ground to flight level (FL) 125.

A De Havilland Canada Dash 8 (DHC-8) taxied at Taree and the crew made broadcasts and reports to flight service in accordance with procedures for operations in Class G airspace. The DHC-8 was an IFR regular public transport (RPT) flight to Sydney via Craven, a position 41 NM north-north-west of Williamtown. The crew of the DHC-8 had planned to operate at FL160.

North of Williamtown, the PA-31-350 was radar vectored to the west of track due to other traffic. When the aircraft was approximately 30 NM north of Williamtown the approach controller, cancelled the radar vector and instructed the PIC to track direct to Kempsey. The aircraft was 2 NM west of track and was within the tolerance of the primary tracking navigation aid. The approach controller was not required to advise flight service that the aircraft was west of track under the circumstances and there was no further coordination with flight service.

Prior to being instructed to transfer to the flight service frequency and while the aircraft was in Williamtown airspace the PIC of the PA-313-350 established radio communications with flight service. The flight service operator requested an estimate for abeam Taree. The PIC advised flight service to standby while he calculated the estimated time. At about the same time the crew of the DHC-8 reported the departure from Taree to flight service and was instructed by the flight service operator to contact Brisbane Centre approaching FL110.

The PIC of the PA-31-350 reported to flight service that the aircraft would be abeam Taree at 1428. Neither crew were given traffic information on the other aircraft although the DHC-8 was estimated to be at Craven at 1429. The PIC of the PA-31-350 heard the departure report from the crew of the DHC-8 but was not concerned because the flight service operator did not provide traffic information about that aircraft.

The PIC of the PA-31-350 was instructed by Williamtown approach to transfer to the flight service frequency. He reported to flight service that the aircraft was maintaining 9,000 ft and this was acknowledged by the operator. Shortly after, the PIC requested the callsign of the regional airline aircraft departing Taree from flight service and advised that it had just climbed through his level, about 400 ft in front of his aircraft. The crew of the DHC-8 did not see the PA-31-350.

The flight service operator was required to pass traffic information on IFR flights in accordance with criteria from the Manual of Air Traffic Services (MATS), to the pilots and crews of all IFR flights operating in Class G airspace. The operator used procedural methods and was also required to use the criteria from MATS to establish whether the aircraft would conflict or not. There was radar coverage in the area above approximately 7,000 ft which was used by ATS for the management of aircraft above FL125, in controlled airspace, but there was no radar display or access to radar information in the flight service centre.

The workload for the flight service operator was light and he was nearing the completion of an eight-hour shift. The operator assessed that the PA-31-350 would pass about 5 NM to the south-west of Taree and this aspect coupled with the similar estimates for the next positions (Taree and Craven) for both aircraft led him to believe that they would not conflict. The operator twice re-assessed the information on the two aircraft but did think that they would be in conflict. He did not plot the tracks of the aircraft on the chart display at the console. The Williamtown to Kempsey track and the Taree to Craven track cross 12 NM to the south-west of Taree. It was estimated that the aircraft passed at a position approximately 15 NM south-west of Taree.

The actual position and separation between the aircraft could not be ascertained from radar data recordings. The cloud in the area at the time of the incident was a layer of broken cloud between 7,000 and 9,000 ft.

ANALYSIS

The flight service operator did not plot the intended tracks of the aircraft. He relied on his mental ability to assess the potential for conflict. If he had plotted the tracks he would have appreciated that the DHC-8, was going to cross the track and would probably climb though the level of the PA-31-350, and that there was a potential for conflict. He was also nearing the end of his shift period and may have become complacent due to the low level of traffic. This may explain why he did not apply the MATS criteria to assess the potential for conflict.

The flight service operator was using procedural methods to monitor traffic in his area of responsibility. Some of the airspace within his area, near Taree, was within radar coverage. However, flight service did not have a radar display. The greater use of the available radar coverage in Class G airspace would have enabled ATS to more readily assess potential traffic conflicts.

The Taree departure report for the DHC-8 was broadcast during the period when the PIC of the PA-31-350 was calculating the abeam Taree estimate. The PIC of the PA-31-350 heard the Taree departure report but did not appreciate the significance of the information. Flight service did not provide information about the DHC-8 as possible conflicting traffic and because he was concentrating on the estimate calculation, the PIC of the PA-31-350 may have been distracted from monitoring aircraft reports for potential traffic conflicts. One of the reasons for reports in Class G airspace was to provide information to pilots to assist them to maintain situational awareness with regard to potential traffic conflicts. This was additional to the traffic information that flight service was required to provide to the pilots of IFR flights. Maintenance of situational awareness by pilots was part of the defence mechanism of the airspace system.

The layer of cloud under the PA-31-350 would have hindered the PIC in sighting the climbing DHC-8. Additionally, as the layer of cloud commenced at approximately 7,000 ft the crew of the DHC-8, during their climb, would have been restricted in their ability to maintain a lookout for aircraft.

SIGNIFICANT FACTORS

1. The flight service operator did not have access to radar information and was required to use procedural ATS procedures.

2. The flight service operator did not plot the tracks of the aircraft on the chart.

3. The flight service operator did not assess the traffic in accordance with the Manual of Air Traffic Services criteria.

4. The flight service operator did not provide traffic information in accordance with the Manual of Air Traffic Services.

5. The PIC of the PA-31-350 did not have sufficient information to maintain situational awareness with regard to potential traffic conflicts.

6. The DHC-8 was operating in an area of restricted visibility prior to and climbing through the level of the PA-31-350.

SAFETY ACTION

Bureau of Air Safety Investigation safety action

Because of this and other occurrences the Bureau reviewed aspects of the increased use of available radar coverage for improved safety and forwarded Interim Recommendation 970112 to Airservices Australia on the 14 July 1997. The Interim Recommendation stated:

"The Bureau of Air Safety Investigation recommends that Airservices Australia review the provision of air traffic services to maximise the use of the currently available radar coverage particularly on routes used by regular public transport aircraft."

Airservices Australia replied on the 17 October 1997 and stated that:

"Airservices Australia is reviewing the provision of air traffic services with regard to maximising the use of radar services both within and outside controlled airspace.

As you are aware, the Airspace 2000 proposal which Airservices planned to introduce on the 26th February 1998, comprehensively addresses the extension of radar services. These radar enhanced services include:

- Radar Class E airspace from Cairns to Melbourne above 8500 feet.

- A Radar Information Service (RIS) in Class G airspace within radar coverage.

The Board of the Civil Aviation Safety Authority (CASA) has deferred making a decision on the proposal.

Regardless of the outcome of the Airspace 2000 review by CASA, Airservices intends proceeding with three initiatives to enhance radar services on the 26th of February 1998.

1. Radar Class E airspace will be introduced between 8500 feet and FL125 outside existing Class C airspace from Grafton to Canberra within radar coverage.

2. Brisbane Enroute will provide radar services within the Class C control area steps over Coffs Harbour down to 4500 feet.

3. Sydney Terminal Control Unit will provide radar services to 45nm Sydney in non-controlled airspace on a discrete frequency.

These initiatives will increase Airservices use of existing radar coverage for air traffic services. Further expansion of radar services is limited pending decisions on Airspace 2000 by CASA."

On 26 February 1998 Airservices Australia implemented radar Class E airspace services in the area between Canberra and Grafton within radar coverage.

Local safety action

The regional airline safety department was planning to use the incident in their safety journal to highlight problems that may be encountered in Class G airspace.

FACTUAL INFORMATION

History of the flight

The helicopter was ferrying oil company personnel from the Griffen Venture oil rig to Karratha aerodrome. The weather was clear and the wind light. The co-pilot, occupying the left-pilot seat, was undergoing a line check by the pilot in command who was a company managing-captain and a qualified line-check captain. Although both pilots were experienced captains on the helicopter type, the co-pilot had the greater overall helicopter time, and the pilot in command the greater time on the helicopter type. Cockpit voice recorder (CVR) evidence indicated that there was some discussion between the pilots about a particular company matter during the flight and ground-taxi.

During the arrival at Karratha the co-pilot flew the approach, landing at a point known as "Heli 26" which is on taxiway F, parallel to runway 26. The pilot in command assumed control of the helicopter for the ground-taxi as control of the wheel brakes was possible only from the right-pilot seat. The co-pilot retracted the nosewheel-lock pin to allow the nosewheel to castor during taxi. CVR evidence indicated that the pilot in command did not invoke sterile-cockpit procedures and that the checklist challenge-and-response procedures were not conducted after the helicopter had landed. Both pilots reported however, that the pilot in command had completed the after-landing checks. The pilot in command taxied the helicopter along taxiway F, completing a 90-degree right turn into taxiway A and a left turn onto the terminal tarmac area. A company-LAME eyewitness reported that the nosewheel appeared to be castoring normally.

The pilot in command reported that he applied the park brake before disembarking the passengers and that he released the park brake before taxiing the helicopter to the company lines. The challenge-and-response procedure required for the pre-taxi checklist was not conducted before taxiing from the disembarkation point.

The helicopter had to be taxied slightly left around a parked BAe146 aircraft before executing a left 90-degree turn. This turn was succeeded by a right 90-degree turn to follow the marked taxiway, past a helicopter parking area. Having turned approximately 10 degrees left then 10 degrees right to go around the BAe146, the pilot in command attempted to turn the helicopter left to follow the marked taxiway. The helicopter's nosewheel steering did not fully respond. Although the pilot in command quickly realised that the nosewheel lock-pin had re-engaged and that he was unable to follow the marked taxiway, he decided to continue taxiing his helicopter through the occupied helicopter parking area. An eyewitness reported that the nosewheel was not castoring and that it was being dragged sideways on the tarmac as the helicopter turned slightly. Tyre-scuff marks on the tarmac surface confirmed that the nosewheel was not castoring.

The co-pilot reported that when the helicopter would not turn, he checked the handle, finding it slightly proud of the full-down position. He attempted to withdraw the lock-pin by pushing down on the nosewheel castor-lock control handle, first with one hand, then with both hands. He also reported that as his attention was diverted to disengaging the nosewheel lock-pin, he did not initially realise that the helicopter was entering the helicopter parking area. The pilot in command stated that he did not attempt to bring the helicopter to a light-on-wheels condition or low-hover to unload the nosewheel to release the lock-pin, due to the proximity of parked helicopters. He also reported that he did not stop as he thought that the Super Puma would clear a nearby parked S76. The CVR recorded a comment by the co-pilot, 13 seconds after it was noticed that the pin was still engaged, which appeared to indicate that he also thought the Super Puma would clear the parked S76. A further four seconds later, the CVR recorded clipping sounds made by the main rotor contacting the S76 tail rotor blade.

Both pilots heard the clipping sound which the pilot in command thought was a blade strike, although the co-pilot was unsure. The helicopter had travelled approximately 35 metres from where the lack of nosewheel castor was first noticed, to the impact point. Tips of two blades of the main rotor clipped a tail rotor blade of the nearby S76 helicopter. The tail rotor blade sheared at the contact point. The pilot in command then continued to taxi the helicopter across the parking area to the taxiway. Once clear of the parking area, he brought the helicopter to a light-on-wheels condition to unload the nosewheel. The co-pilot was then able to retract the nosewheel lock-pin which then allowed the helicopter to ground taxi normally.

Cockpit control configuration

The parking brake and nosewheel castor-control handles are located on the right side of the centre console, just to the left of the cockpit's right seat. The park brake-control handle is forward of, and in line with, the nosewheel castor-control handle. Both handles are similar in appearance and feel. The park brake is applied by pulling up the park brake-control handle and turning it 90 degrees. The brakes are released by turning the handle 90 degrees and pushing down.

The nosewheel is locked fore/aft by a lock-pin. The lock-pin is retracted by turning the castor control-handle 90 degrees then pushing down. The pin is re-engaged by pulling up on the castor-control handle then turning the handle 90 degrees to lock it in position. The locking of the nosewheel and application of the park brake are similar actions. The unlocking of the nosewheel and release of the park brake are similar actions. Other than the position of the handles, there are no cockpit indications to indicate the status of the park brake or nosewheel castor. Other company pilots reported they have, on occasions, unintentionally applied the park brake instead of engaging the nosewheel lock-pin during ground taxi.

The nosewheel lock-pin has a design weak point. This allows the lock-pin to shear if sufficient side-loads are applied to the nosewheel. The nosewheel lock-pin can be jammed in place if the nosewheel is not centred or undergoing even slight side-loads. Centring and off-loading the nosewheel is achieved by using tail rotor inputs and by bringing the helicopter to a light-on-wheels condition or hover. With the nosewheel lock-pin engaged, it is possible to achieve approximately 30 degrees of heading change whilst ground-taxiing. Flight Data Recorder (FDR) evidence indicates that the helicopter had turned approximately 10 degrees to avoid the BAe 146. The nosewheel lock-pin did not break during this incident despite the tyre-scrub marks on the tarmac surface. These marks indicated that the nosewheel underwent significant side-loading. A post-flight engineering inspection could not fault the nosewheel system.

Company procedures

The company operations manual prescribes which checklist actions are challenge-and-response items. These include the pre-taxi and after-landing checks. The pilots reported that they were aware of these requirements. The operations manual also directs the helicopter commander (pilot in command) to other publications including Base Instructions - Individual Unit Orders (IUOs) and Operations Information Circulars (OICs).

An OIC, detailing cockpit resource management procedures, introduced the use of a cockpit "sterile environment" within ten miles of a takeoff or landing point. This OIC had not been incorporated into the operations manual at the time of the incident, although both pilots later stated that they were aware of the requirement. Sterile-cockpit procedures require that only communications and actions essential to the safe conduct of a flight are conducted at certain periods in a flight. United States Federal Aviation Administration Regulation 135 requires the practice of such procedures during certain phases of flight, including ground taxi. The failure to practise this procedure has been implicated in several fatal accidents in the United States. Such a requirement does not exist under present Australian civil aviation regulations and orders.

IUOs are held at each company base. To reduce the amount of material being read by pilots, the company introduced a procedure whereby new orders were noted on the publication's cover sheet. If they were familiar with the prior orders, the pilots would then just read the new orders annotated on the cover sheet.

As company helicopters had been observed to diverge from the taxiway and cross the parking area, Karratha base introduced an order reminding pilots, "to stay on the taxi lines in the Woodside apron area and to be particularly vigilant". This order was dated 23/01/97, however the last entry on the cover sheet was 21/01/97 and referred to another order. There is no evidence to indicate that either pilot had read the order although the co-pilot did recall being advised by the company's chief pilot of a requirement to stay on the taxiway and the pilot in command stated that he was aware of the order. Some base pilots, however, stated that they were not aware of the order until it's existence had been noted during the investigation.

Both pilots had undergone company-provided cockpit resource management training (CRM).

ANALYSIS

Although company procedures required the use of sterile-cockpit procedures within ten miles of the landing point, the pilot in command did not invoke the requirement. Whilst the company procedures also required the conduct of challenge-and-response checklist items for after-landing and pre-taxi, no challenge-and-response items were conducted once the helicopter had landed or before taxiing from the disembarkation point. It was considered possible that the pilot-in-command may have inadvertently raised the nosewheel castor-control handle instead of applying the park brake before disembarking the passengers, although there is no evidence to confirm this and the pilot stated that he did not.

Having achieved two 90 degree turns after landing, physical and eyewitness evidence confirm that the nosewheel lock-pin had re-engaged some time after the helicopter had manoeuvred onto the main tarmac area. The lack of nosewheel lock-pin damage, despite the considerable side-loads generated, indicated that the pin had not fully engaged thereby not permitting the weak point to achieve is designed purpose. With no cockpit indication of the nosewheel pin position, the pilots were unaware of any potential problem with the steering until it was time to manoeuvre the helicopter within the constrained turning area.

Although he was aware of the IUO requiring company pilots to follow the taxi lines, the pilot in command decided to continue into the occupied helicopter parking area. The co-pilot did not raise an alert, possibly because his attention was focussed on attempts to release the nosewheel lock-pin, although he implied that he thought they were clear of the nearby, parked S76. It is unclear as to why, having thought that the Super Puma's main rotor blades had clipped the S76 helicopter, the pilot in command then decided to continue and bring the Super Puma to a light-on-the-wheels condition.

Despite the in-situ organisational defences and the pilot in command's considerable experience, he made a succession of decision-making errors. Both pilots were aware of the instructions, yet neither enforced the requirements. The co-pilot did not promote the sterile-cockpit requirement when the helicopter was within 10 NM of the landing point, he did not question the lack of challenge-and-response checks during the ground taxi, or challenge the crossing of the taxiway lines when the nosewheel refused to castor. The status of the pilot in command and the type of check being conducted may have encouraged the co-pilot, despite his CRM training, to assume a passive role in the crew's decision-making process.

The pilot in command's experience and his standing within the company indicated that the decision-making errors were uncharacteristic. The only contributing factor the investigation found was the CVR evidence that indicated that the pilots appeared to be preoccupied with other company matters. The preoccupation with issues outside the conduct of flight and the co-pilot's passive role within the cockpit probably contributed to the pilot in command's decision making errors. The design and location of the nosewheel castor-control and park brake handles associated with the lack of cockpit warnings may have also contributed to the incident.

SAFETY ACTIONS

As a result of this incident, the Bureau of Air Safety Investigation is evaluating safety issues concerning the regulation of cockpit procedures and design aspects of the Super Puma helicopter cockpit. Any forthcoming recommendations will be published in the Quarterly Safety Deficiency Report.

The aircraft was involved in a cotton spraying operation. The pilot reported that on the tenth take-off the aircraft failed to accelerate to normal climb speed, only reaching a height of about 15 ft. He dumped the load but was unable to prevent the aircraft descending into the cotton crop. Although the aircraft was substantially damaged the pilot was uninjured.

The engine subsequently performed normally during a test run. The pilot reported that he remembered strong 'willy willy' activity in the area immediately after the accident. He concluded it was likely that the take-off performance of the aircraft had been adversely affected by a wind gust at liftoff.

FACTUAL INFORMATION

The crew of an instrument flight rules (IFR) Saab 340 operating a flight from Sydney to Canberra had received an airways clearance for a Shelleys 5 standard instrument departure (SID) on climb to 3,000 ft. The SID required the crew to track on a heading of 335 degrees magnetic (M) and to turn on to a heading of 210 degrees M when they reached 600 ft on climb. The Saab taxied for an intersection departure for runway (RWY) 34L from taxiway B10 and stopped at the holding point awaiting departure approval. This taxiway was on the eastern side of the runway and approximately 1450m north of the threshold.

The traffic flow was busy when the aerodrome controller west (ADCW) received departure instructions from the departure south radar controller (DEPS) for a Bell 206 (B206) helicopter. The B206 was to depart from the helicopter area to the east of RWY 34/16 to Bankstown, located approximately 10 NM west of Sydney aerodrome. The planned altitude for the B206 was 1,500 ft. The ADCW cleared the pilot in command (PIC) of the B206 to take-off. The PIC of the B206 was approved to cross RWY 34L behind a landing Boeing 747 (B747). At the same time the ADCW approved two taxiing Boeing 737s (B737) to cross RWY 34L at taxiway J which was parallel to and south of B10. After departure the ADCW instructed the PIC of the B206 to change to the DEPS frequency.

The next aircraft in the landing sequence for RWY 34L was a B737. The ADCW estimated that there was sufficient time for the Saab to depart prior to the B737 reaching the runway. The ADCW requested and was granted departure instructions for the Saab by DEPS. As the approaching B737 passed a position approximately 2 NM from the threshold of RWY 34L the ADCW cleared the crew of the Saab for immediate take-off after confirming that they were ready for an immediate departure.

As the Saab accelerated the B737 was on a close final approach. The ADCW was required to provide a landing clearance to the crew of the B737 or instruct the crew to go around if the runway was obstructed. The ADCW cleared the crew of the B737 to land. As the B737 touched down the Saab was approximately 1,700 m further along the runway and travelling at a slightly lower groundspeed than the B737. At the time the Saab became airborne the distance between the aircraft was approximately 1500 m. The B737 landed while the Saab was on the runway.

As the Saab became airborne DEPS called ADCW to coordinate a change of track and level for the previously departed B206. The ADCW approved the changes. At the suggestion of DEPS the ADCW instructed the crew of the Saab to cancel the SID and to maintain runway heading. This was done to maintain separation between the B206 and the Saab. There had been a lack of provision of separation between the aircraft.

Runway separation standards

The ADCW was required to provide the crew of the B737 with landing or go-round instructions before that aircraft reached a height of 200 ft above the landing threshold. Runway separation standards required that landing aircraft should not be permitted to cross the runway threshold until a preceding departing aircraft (less than 136,000 kg maximum take-off weight) was airborne. Controllers were required to consider the effect of aircraft carrying out a go round and the implications for separation with other aircraft.

Technical crew

The B737 co-pilot was the handling pilot for the landing. The crew could not recall if the Saab was airborne or still on the runway when they landed. The provision of a landing clearance to the crew of an aircraft entitled the PIC to continue with the landing if it was deemed safe to do so, or to conduct a go round if the situation was not considered to be safe.

Separation responsibilities between ADCW and DEPS

The ADCW was responsible for controlling arriving and departing aircraft for RWY 34L and was jointly responsible in conjunction with DEPS for separating aircraft in the airspace to the west of RWY 34L.

The ADCW and DEPS did not establish which controller was to coordinate the separation between the B206 and Saab or the type of separation to be used. Both these aspects needed to be coordinated prior to departure instruction being issued and the crew receiving a take-off clearance.

When the ADCW requested departure instructions for the Saab, DEPS assumed that the aircraft would be cleared for take-off after the B737 landed. Consequently, DEPS did not query the ADCW regarding the separation of the B206 and the Saab.

Runway usage

The ADCW believed that there was an opportunity to utilise the northern portion of RWY 34L for the departure of the Saab while the two B737s crossed the runway. This required the ADCW to confirm with the crew of the Saab that they were ready for an immediate departure, to obtain departure instructions from DEPS and to issue the take-off clearance to the crew of Saab prior to the approaching B737 requiring a landing clearance.

As the ADCW issued the take-off clearance to the crew of the Saab the B737 was approximately 2 NM from the threshold of the runway. Aerodrome controllers generally accepted 2 - 3 NM as the point at which the runway should be vacated by other traffic to ensure that an approaching B737 or similar type aircraft could be assured of a landing.

The Saab accelerated slower than the ADCW expected. The ADCW appreciated that runway separation was unlikely to be maintained between the Saab and the B737. Faced with the decision to either approve the B737 to land or to instruct the crew to conduct a go around the ADCW believed that the better option was to clear the aircraft to land. He believed that this option was the safer alternative under the circumstances.

Air traffic service performance

The ADCW felt a degree of pride in his ability to perform tower control duties. He endeavoured to provide minimum disruptions or delays to aircraft.

ANALYSIS

The ADCW's desire to not unduly delay aircraft probably caused him to attempt to facilitate the departure of the Saab at a time when there was little or no margin to compensate for delays in crew reaction to instructions or differences in individual aircraft performance.

It was unlikely that there was sufficient time for the Saab to depart as the arriving B737 had passed the position on the approach used by aerodrome controllers as a guide to assist them in managing runway usage.

The ADCW was left with limited options to resolve the situation. Subsequently, he issued a landing clearance to the crew of the B737 and allowed the crew of the Saab to continue the take-off.

His desire to provide a service to aircraft may have caused him to act hastily and consequently overlook the need to coordinate the provision of separation between the B206 and the Saab after departure, and to miscalculate the runway separation between the Saab and the B737.

DEPS and the ADCW had a shared responsibility to ensure separation was maintained between departing aircraft. However, DEPS incorrectly assumed that the ADCW would not clear the Saab for take-off before the B737 landed. DEPS should have queried the ADCW as to his plan to maintain separation between the B206 and the Saab when the ADCW requested departure instructions for the Saab. Subsequently, it was only the action of the B206 PIC requesting an amended route and level that prompted DEPS to eventually query ADCW and for the potential conflict to be resolved.

SIGNIFICANT FACTORS

1. The ADCW did not coordinate with DEPS for the maintenance of separation between the B206 and the Saab.

2. The ADCW did not ensure that separation would be maintained between the B206 and the Saab prior to issuing the crew of that aircraft with a take-off clearance.

3. DEPS did not query the ADCW with regard to the position of the B206 when the latter requested departure instruction for the Saab.

4. The ADCW did not allow for a sufficient margin between the arriving B737 and the departing Saab to compensate for differences in aircraft performance.

VH-RJE was tracking inbound on a VFR flight from Rockhampton via Charon Point (CHP), on a bearing of 143 degrees from Mackay. When the aircraft was about 35 NM from Mackay, the Brisbane Sector 7 controller provided information on the flight to the Mackay tower co-ordinator. When the co-ordinator created a flight progress strip for the aircraft the tracking details were incorrectly inserted as being via Shute Harbour, a bearing of 328 degrees from Mackay. This information was available to the aerodrome controller when the aircraft reported at 33 NM from Mackay at 4,500 ft. No other position information was provided by the pilot, nor did the controller request any. A clearance to enter controlled airspace and to track direct to Mackay at 4,500 ft was issued.

VH-TNU taxied at Mackay for Rockhampton and was cleared to track direct to Rockhampton, on the 143 radial. VH-RJE requested descent and was cleared to 3,000 ft. VH-TNU reported having left 1,700 ft on climb to FL150 and was transferred to the sector 7 frequency. VH-RJE was then asked to report crossing the coast. (The aerodrome controller expected the aircraft to cross the coast about 12 NM from Mackay on the Shute Harbour track.) The pilot reported that he was over land and approaching Hay Point (about 9 NM SE of Mackay). After the controller confirmed this position he immediately informed the sector 7 controller of the confliction with VH-TNU.

In the meantime, the sector 7 controller had observed VH-RJE on radar and was seeking confirmation of that aircraft's altitude.

By the time VH-TNU had passed 4,000 ft on climb, lateral separation between it and VH-RJE was 4 NM. Although VH-RJE had been displayed on radar to the sector 7 controller prior to this time, it had not featured in the controller's planning as it was outside controlled airspace.

For aircraft flying between Rockhampton and Mackay, laterally separated tracks had been developed. VH-TNU had planned via the western route but was given the direct track. VH-RJE had planned and tracked via the direct track.