Rolladen-Schneider Flugzeugbau GmbH LS6-B, VH-HDT

Safety Action

Local Safety Action

As a result of this accident the GFA is considering a review of start point procedures, and a review of visibility from, and of, gliders.

The GFA will also review the use of advanced avionics in gliders in an endeavour to determine if programming and interrogating of those systems is distracting the pilots from their primary task of visual collision avoidance.

Summary

The two gliders were taking part in the Australian National Gliding Championships at Narromine NSW. One, a German registered Rolladen Schneider LS8A glider, registered D-1003 was flown by a British national, while the other, an Australian registered Rolladen Schneider LS6B glider, VH-HDT, was flown by a Japanese national. Both pilots complied with the Gliding Federation of Australia (GFA) requirements for foreign nationals operating in Australia.

Although some gliders in the competition had self-launch capability, both gliders involved in the accident were launched by aero-tow. The 52 gliders competing on the day were launched in approximately 45 minutes. Launching commenced at mid-day with D-1003 being launched at 1225. After release at 2,000 ft AGL the pilot manoeuvred to take up a position near start point "Charlie" from where he would start the day's task. Shortly before the accident D-1003 was observed to be steadily banking to the right in a thermal at approximately 6,000 ft AMSL, in the company of at least six other gliders.

VH-HDT was launched at 1230 and at approximately 1315 was observed to be approaching from the south-west, flying fast, and manoeuvring to join those gliders circling near start point "Charlie". HDT was seen to bank to the right to conform to the established circling direction within the thermal. Concurrent with banking to the right HDT pulled up sharply, directly below D-1003. Immediately prior to the collision, HDT's angle of bank was observed to rapidly reduce. The cabin section of HDT was observed to collide with the lower centre and forward fuselage of D-1003. The structural integrity of the forward fuselage of HDT was destroyed and the forward fuselage was observed hanging approximately 20 degrees below the normal fuselage line. The glider descended vertically, rotating to the right, before impacting the ground and coming to rest inverted. The pilot did not survive the collision.

The post mortem examination did not disclose any abnormalities that may have contributed to the accident.

The pilot of D-1003 advised that he had not sighted HDT approaching the thermal. He felt and heard a huge impact concurrent with D-1003 pitching violently nose down. The pilot immediately released the canopy and seat harness before parachuting clear. D-1003 descended in a flat spin to impact inverted 200 metres from HDT. The pilot landed a further 200 metres away, sustaining back injuries during the landing.

The wreckage of both gliders was examined and no pre-impact fault was found in either glider. The examination confirmed that HDT had impacted the lower fuselage of D-1003. There was some evidence of intermeshing of the wings during the collision sequence, however the structural integrity of the wings was probably not greatly compromised by the collision.

The on-board data recorders were recovered and examined. Because of impact damage to security switches within the units, all recorded data had been lost.

Both pilots involved in the accident had been assigned to start the task at start point "Charlie". Start point Charlie was approximately 15 km north of the town of Narromine and had been allocated to 13 of the competing gliders on the day of the accident. A start point is a GPS position based on a geographical feature that the pilot must transit in order to register a start for the day's task. After passing though the start point the pilot reports the start time and allocated point to the competition organisers by radio. An on-board recorder that is interrogated for verification by the competition organisers also records the start time and position.

The organisers had nominated four start areas for the day. The four start areas were dispersed at locations up to 20 km from the airfield. Within each start area were five geographical start points. Each pilot was issued with a randomly selected list of four valid start points, one from each area. The pilot could use any one, but only one, of these four start points. This created a double dispersion: a scatter of start areas, and a scatter of start points within those areas. The use of multiple start areas and start points was introduced to eliminate the overcrowding of airspace that occurred when just one start point was used.

Approximately 20 minutes after the last glider is launched the organisers declare the points open which signals to the pilot's that they can, in their own time, commence the day's task. The start points were not open at the time of the accident. The system of multiple start points has been deemed successful in reducing the incidence of congestion within the start area and on the competition task.

The pilot of HDT was wearing sunglasses and was looking through four facets when observing features and events outside of the canopy. At the time of the accident the sun was essentially overhead, the sky was clear and visibility was unlimited. There would not have been an impediment to the vision of the pilot of HDT as he approached the thermal from the south-west. Neither the pilot's visual acuity nor the weather were considered to be factors in the accident.

The pull up when entering a thermal is a manoeuvre used by glider pilots to convert forward speed to height. There are certain etiquette's surrounding the approach to an occupied thermal and these form part of the training undertaken by all glider pilots. The pilot of HDT was highly experienced; he was a gliding instructor in Australia and Japan, and he had taken part in many national and international gliding competitions. Accordingly, he would have been aware of the factors to be considered when joining the thermal. It is not known why the pilot of HDT did not observe the position and flight path of D-1003 while approaching the thermal. D-1003 was essentially on a consistent flight path within the thermal and should have been visible to the pilot of HDT.

HDT was equipped with reasonably sophisticated navigation and communications systems. It may be that the pilot was attending to this equipment while approaching the thermal and did not notice D-1003 until after initiating the pull up. The rapid change to the angle of bank observed just before impact was probably the initiation of an unsuccessful avoidance manoeuvre by the pilot of HDT.

Occurrence summary

Investigation number 199805348
Occurrence date 25/11/1998
Location 13 km N Narromine, Aero.
State New South Wales
Report release date 20/02/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Airborne collision
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Rolladen-Schneider Flugzeugbau GmbH
Model LS6
Registration VH-HDT
Operation type Gliding
Departure point Narromine, NSW
Destination Narromine, NSW
Damage Destroyed

Aircraft details

Manufacturer Rolladen-Schneider Flugzeugbau GmbH
Model LS8
Registration D-1003
Operation type Gliding
Departure point Narromine, NSW
Destination Narromine, NSW
Damage Destroyed

British Aerospace Plc BAe 146-200A , VH-JJX

Safety Action

Local safety action

Airservices Australia advised that a request to change the warning message has been submitted by the Northern District. (This is one of many TAAATS software modification requests that have been submitted.) However, the modification is unlikely to be actioned in the short term due to the need to action higher priority tasks.

Bureau of Air Safety Investigation safety action

BASI will monitor Airservices' actions and, in particular, any system modifications made to prevent further similar occurrences.

Summary

The aircraft was enroute from Alice Springs to Cairns and was displayed to the Daintree sector controller in the Brisbane air traffic control centre, as a green jurisdiction track and label. Without notice, the display changed to an uncoupled black track without label data, resulting in the sector controller losing situational awareness. Investigation revealed that the Cairns tower coordinator controller had cancelled the aircraft's flight data record (FDR) in the Australian advanced air traffic control system (TAAATS).

The coordinator had assumed that an aircraft on the ground at Cairns was the aircraft displayed as airborne and consequently felt it was unnecessary to check further prior to deleting the record. Local instructions precluded the cancellation of flight data records not under the coordinator's jurisdiction without prior consultation/coordination with other air traffic control units. The possibility of this occurring had been recognised by management and the instructions were issued in an endeavour to prevent inadvertent deletion of a flight data record.

TAAATS displays a warning message requesting confirmation of the requested action when a controller deletes an FDR for an aircraft. This message does not warn controllers that they do not have jurisdiction of the aircraft. Airservices Australia have proposed that the warning message for non-jurisdiction FDRs should be amended to alert controllers to the fact that coordination is required prior to deleting the FDR.

SAFETY ACTION

Local safety action

A request to change the warning message has been submitted by Airservices Australia Northern District (This is one of many TAAATS software modification requests that have been submitted). The modification is unlikely to be actioned in the short term due to the need to action higher priority tasks. Bureau of Air Safety Investigation safety action BASI will monitor Airservices' actions and, in particular, any system modifications which are made to prevent further similar occurrences.

Occurrence summary

Investigation number 199805341
Occurrence date 14/11/1998
Location 80 km SW Cairns Aero.
State Queensland
Report release date 29/07/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category ANSP info/procedural error
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer British Aerospace
Model BAe 146
Registration VH-JJX
Serial number E2127
Sector Jet
Operation type Air Transport High Capacity
Departure point Alice Springs, NT
Destination Cairns, QLD
Damage Nil

Fokker B.V. F28 MK 4000, VH-EWD

Summary

Perth ATS assigned the aircraft an altitude of FL330 on descent from FL370. However, the radar mode C display of the aircraft showed the aircraft descending through FL330 to a final level of FL323. When the air traffic controller queried the crew, the pilot verified FL330. The mode C readout then showed the aircraft climbing and then maintaining FL330. When the aircraft descended below FL330, a Fokker F28 was at FL310, and positioned 4 NM away.

Occurrence summary

Investigation number 199805323
Occurrence date 20/11/1998
Location 228 km N Perth, Aero.
State Western Australia
Report release date 20/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 Fokker B.V.
Model F28
Registration VH-EWD
Serial number 11208
Sector Jet
Operation type Air Transport High Capacity
Departure point Karratha, WA
Destination Perth, WA
Damage Nil

Aircraft details

Manufacturer Saab Aircraft Co.
Model A340
Registration 9V-SJB
Serial number 32-40062
Sector Turboprop
Operation type Air Transport High Capacity
Departure point Singapore
Destination Perth, WA
Damage Nil

British Aerospace Plc 3107, VH-TQJ

Safety Action

As a result of this incident and other occurrences, the Bureau of Air Safety Investigation undertook a systemic investigation of the Class G airspace demonstration. That investigation was part of the Bureau's normal systems safety investigation role. The Bureau of Air Safety Investigation released interim recommendation IR980253 on 9 December 1998, which recommended that the Civil Aviation Safety Authority (CASA) terminate the demonstration. The demonstration was terminated on 13 December 1998 by CASA. This investigation supported the decision to terminate the demonstration.

Significant Factors

  1. The crew of the Jetstream did not hear the King Air crew's inbound broadcast on the mandatory broadcast zone frequency.
  2. The crew of the King Air did not hear the Jetstream crew's taxi broadcast on the mandatory broadcast zone frequency; nor did they hear the transmissions made on the Brisbane control frequency by the air traffic controller that provided essential traffic information regarding the Jetstream, and instructed them to maintain 6,000 ft.
  3. The air traffic controller had insufficient time to establish communications with both crews and provide them with sufficient information to enable them to take action to prevent a near collision.
  4. The crews had not been alerted to the presence of each other's aircraft.
  5. The procedures used in the Demonstration Class G Airspace Trial, which encompassed the Williamtown MBZ and MTA, did not fully consider the impact of radio congestion.

Analysis

The incident occurred because the crew of the King Air had not been alerted to the possibility of conflicting traffic and continued their descent for Williamtown in the Class G demonstration airspace. The crew had been alerted about another aircraft, a Beech 1900, which was to the north of Williamtown. The air traffic controller believed that the crew of the King Air had been alerted regarding the Jetstream. The controller assumed that he had heard a read back of the level requirement, when in all probability, the controller heard the "two in together" transmission. He also assumed that the King Air would stop descending and maintain 6,000ft. These assumptions were unfounded.

Analysis of the incident highlights problems involving radio communications, attentional focus, workload, and Class G Airspace training and procedures.

Radio communications

The crew of the King Air did not hear the taxi transmission broadcast by the Jetstream crew on the mandatory broadcast zone frequency; nor did they hear the transmissions made on the Brisbane control frequency by the air traffic controller that provided essential traffic information regarding the Jetstream and instructed them to maintain 6,000 ft.

When the crew of the Jetstream made their first "all stations" broadcasts on the national advisory frequency and the mandatory broadcast zone frequency, the King Air was in Class C airspace and its crew were communicating with air traffic control. The crew of the King Air had no reason to be on the national advisory frequency or the mandatory broadcast zone frequency and could not hear the Jetstream's transmissions.

The crew of the Jetstream reported that they were not aware that communication between themselves and the air traffic control agency could be established while on the ground at Williamtown. The establishment of such communication may have alerted the controller to the potential conflict between the two aircraft much earlier than was the case.

Attentional focus

Throughout the sequence of events for this particular occurrence, when monitoring more than one frequency, the crews had to decide upon which frequency to maintain their primary focus in the face of competing cognitive demands.

The crew of the King Air selected and monitored the mandatory broadcast zone frequency at approximately 31 NM south-west of Williamtown, when the aircraft was passing approximately FL 150. This was entirely reasonable, and accorded with the requirements of AIP. (Annex B to AIP Supplement H48/98, paragraph 5.1, and AIP Supplement H66/98 required crews to monitor the mandatory broadcast zone frequency when below the 8,500 ft upper limit of the mandatory transponder area, except when receiving a radar information service.) However, the focus of the crew's attention would have been centred on the transmissions made on the Brisbane Control frequency.

When the crew of the King Air were cleared by Brisbane to leave the control area on descent, their attention would have been focussed on receiving their clearance and providing an accurate readback to air traffic control. Their focus would not have been on monitoring the mandatory broadcast zone frequency. Accordingly, the crew of the King Air did not hear the Jetstream's departure report, which was being broadcast on the mandatory broadcast zone frequency at that time. Moreover, the Brisbane controller's transmission on the control frequency of 126.9 MHz was the only transmission that linked the King Air with the Williamtown mandatory broadcast zone.

The crew of the Jetstream were broadcasting their departure report on the mandatory broadcast zone frequency using their VHF 1 radio. Their attention would have been focussed on their transmission and on handling the aircraft. They had the Brisbane Control frequency of 126.9 MHz selected on their VHF 2 radio, but their focus would have been on their transmission on the mandatory broadcast zone frequency on VHF 1. The crew of the Jetstream did not hear the transmission that "linked" the King Air with the Williamtown mandatory broadcast zone. Such a link may have assisted the crew of the Jetstream to develop a better mental model of the air traffic situation.

Although the crew of the Jetstream were monitoring the Brisbane Control frequency of 126.9 MHz for over 4 minutes prior to their departure from Williamtown, insufficient information was broadcast on that frequency for the crew to develop an accurate picture of the air traffic situation. Notwithstanding the monitoring of the control frequency, the crew's attentional focus during their taxi and departure would have been on any transmissions made on the mandatory broadcast zone frequency.

When the King Air crew confirmed that they were still on the control frequency, the controller gave them traffic information on a Beech 1900. The King Air was passing 8,700 ft on descent when this traffic information was received and focus of their attention was shifting towards the establishment of mutual separation with other aircraft in the mandatory broadcast zone.

The crew of the Jetstream reported their position to Brisbane Centre passing 4,000 ft on climb. During the period of the Jetstream's transmission, the crew of the King Air was making an "all stations" broadcast on the Williamtown MBZ frequency. The crew of the Jetstream did not hear this broadcast because their attention was focussed upon making their report, and reading back the clearance. The crew of the King Air did not hear the Jetstream's transmission because they were concentrating on arranging mutual separation in the mandatory broadcast zone with the Beech 1900.

Weather

The meteorological area forecast for Williamtown and the trend type forecast were not favourable and indicated that an instrument approach would be necessary for aircraft inbound to Williamtown. The actual weather was consistent with the forecast.

Class G airspace

Contributing to the incident was the confusion on the part of aircrew concerning the requirements of the Demonstration Class G Airspace trial. Also contributing, was the fact that the design of the Class G procedures encompassing the Williamtown mandatory broadcast zone and mandatory transponder area did not fully consider the impact of radio congestion.

During the Class G airspace trial, there was some confusion within the aviation community regarding the termination of radar services. The Civil Aviation Safety Authority reviewed the first fortnight of the trial and as a result clarified some of the procedures in "Aiming Higher", vol. 1 no. 8, October-November 1998. In the section "Termination of radar services by Air Traffic Control (ATC)", the article explained that when an aircraft receiving a radar control service leaves controlled airspace and the radar service continued as a radar information service, ATC would advise "Control service terminated". Further, ATC would advise "Radar service terminated" when a radar information service was terminated.

The air traffic controller's transmissions reflected this aircrew confusion. Indeed, his workload was increased because of deficiencies in the education program provided to the aviation community prior to the introduction of the Demonstration Class G airspace. Also, although the crew of the King Air complied with all of the provisions of the AIP, they did not fully understand the procedures to be used when operating in the Demonstration Class G airspace.

The design of the procedures used in the Demonstration Class G airspace did not fully consider the impact of radio congestion. Even though the controller attempted to separate the two aircraft, he was not required to do so in Class G airspace.

Summary

The crew of British Aerospace Jetstream 31, VH-TQJ, had flight-planned from Williamtown to Sydney via Mt McQuoid at flight level (FL) 120. The crew of Beechcraft Super King Air B200, VH-KCH, had flight-planned from East Sale, to Williamtown via Mt McQuoid at FL 250. Both aircraft were equipped with dual very high frequency (VHF) radios and Mode C transponders, which were operating at the time. A transponder is a radio device which, when triggered by a secondary surveillance radar signal, transmits a response that provides, when selected to mode C, altitude and positional data on a radar display for air traffic controller reference.

The routes flown by the two aircraft were within the Class G demonstration airspace detailed in the Aeronautical Information Publication (AIP) Supplement H66/98 of 5 November 1998. The route segment from Williamtown to Mt McQuoid included airspace inside the mandatory broadcast zone for the Williamtown control zone up to and including 5,000 ft. It also included the mandatory transponder area from 5,000 ft to 8,500 ft for a radius of 30 NM centred on Williamtown, and Class C airspace above 8,500 ft to the south-west. The crew of the King Air were descending on air traffic services route Whisky 170 (W170) on track from Mt McQuoid to Williamtown. W170 was a low-level two-way route. The crew of the Jetstream tracked to intercept W170 to Mt McQuoid after departing from Williamtown and were on climb.

Williamtown was listed in paragraph 4.3 of AIP Supplement H66/98, which required aircraft not receiving a radar information service to "monitor and, when required, use the frequency specified", which was 118.3 Megahertz (MHz), the Williamtown mandatory broadcast zone frequency when inside the Williamtown mandatory transponder area. The crews of both aircraft attempted to monitor and use the mandatory broadcast zone frequency while they were inside the mandatory transponder area.

The meteorological area forecast for Williamtown issued at 1800 Eastern Summer Time (ESuT) was for 3 octas of stratus at 1,000 ft, 6 octas of cumulus at 1,800 ft and 6 octas of stratocumulus at 2,500 ft. The trend type forecast included moderate turbulence below 5,000 ft from 1800 to 1900 ESuT, and from 1900 to 2100 ESuT the visibility was expected to reduce to 4,000 m in drizzle with broken cloud at 1,000 ft. The reported weather was a varied cloud base from 1,200 ft to 1,600 ft, with the tops 4,000 ft to 5,000 ft. A higher level cumulo-nimbus cloud cell was reported to the west of Williamtown.

While taxiing at Williamtown, the crew of the Jetstream made "all stations" broadcasts on the national advisory frequency and the mandatory broadcast zone frequency. The crew of the King Air did not hear these transmissions because they had not selected or transferred to those frequencies at that time, nor were they required to. The King Air was established in Class C airspace and the crew was communicating with the air traffic controller located in the Brisbane Area Control Centre.

The crew of the King Air selected and monitored the mandatory broadcast zone frequency at approximately 31 NM south-west of Williamtown, when the aircraft was passing approximately FL 150. AIP Supplement H66/98 required crews to monitor the mandatory broadcast zone frequency when below 8,500 ft, the upper limit of the mandatory transponder area, except when receiving a radar information service.

At 18:45.41, the crew of the King Air was cleared by Brisbane Centre to leave control area on descent, was given the area QNH, and informed that control services would terminate passing 8,500 ft. They were also advised that Williamtown was operating on mandatory broadcast zone procedures. The crew acknowledged this transmission. During this period, the crew of the Jetstream broadcast their departure on the mandatory broadcast zone frequency on their VHF 1 radio. On their VHF 2 radio, they had the Brisbane Control frequency of 126.9 MHz, selected, which they had been monitoring, together with the MBZ frequency, for four minutes prior to departure. The crew of the King Air reported that they did not hear the Jetstream's departure broadcast.

At 18:46.41, the controller asked if the crew of the King Air was still on the control frequency, and then provided the crew with traffic information regarding a Beech 1900 inbound to Williamtown from the north that was descending through 6,000 ft. The crew of the King Air acknowledged the traffic information. The King Air was passing 8,700 ft on descent when the traffic information was passed.

At 18:47.01, the controller attempted to provide the crew of the King Air with additional information about unidentified traffic (the Jetstream), 3 NM south-west of Williamtown. The transmission was over-transmitted by another aircraft and was unreadable. The crew of the King Air heard only the last few words of the transmission, and did not consider it relevant to their flight. The King Air was passing 8,500ft, which meant that it was leaving Class C controlled airspace and entering the Williamtown mandatory transponder area in the Class G demonstration airspace. During the high workload at that period of the flight, the crew was preparing for an instrument arrival into Williamtown due to the weather conditions. The controller did not follow up this "unacknowledged" transmission, because the crew of the Jetstream reported on the control frequency, its reported position identifying it as the previously unidentified traffic.

The mandatory broadcast zone at Williamtown was established in Class G (uncontrolled airspace). While within the mandatory broadcast zone, pilots were required to maintain a continuous listening watch on the mandatory broadcast zone frequency. They could arrange mutual separation within the mandatory broadcast zone. The frequency was not normally monitored by air traffic services. Pilots of IFR aircraft were required to report "Changing to Williamtown mandatory broadcast zone 118.3 MHz" when they were inbound to the Williamtown mandatory broadcast zone area.

At 18:47.24, the crew of the Jetstream reported their position to Brisbane Centre and that they were passing 4,000 ft on climb. The controller instructed the crew to squawk (transponder) ident, to squawk code 1201, and to maintain 5,000 ft due to inbound traffic. The squawk code and altitude restriction were read back correctly by the Jetstream crew, although the crew then inadvertently selected the wrong code of 1207. During the period of the Jetstream's transmission, the crew of the King Air was making an "all stations" broadcast on the Williamtown mandatory broadcast zone frequency. The Jetstream crew reported that they did not hear the broadcast.

At 18:47.56, the controller again attempted to provide traffic information about the Jetstream to the crew of the King Air, together with an instruction to maintain 6,000 ft. That transmission was over-transmitted by another aircraft and was not heard by the King Air crew. The over-transmission was confirmed by the crew of the Jetstream, who transmitted "two in together". The controller reported that he was "95% sure" that the King Air crew had read back "maintain 6,000 ft", which was not supported by analysis of recorded audio data. The transmission "two in together" was recorded. At the time of the controller's transmission, the Beech 1900 crew initiated communication with the King Air crew on the mandatory broadcast zone frequency and between them they subsequently arranged mutual separation.

Occurrence summary

Investigation number 199805078
Occurrence date 16/11/1998
Location 11 km SW Williamtown, Aero.
State New South Wales
Report release date 13/12/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Separation issue
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer British Aerospace
Model 3100
Registration VH-TQJ
Serial number 703
Sector Turboprop
Operation type Air Transport Low Capacity
Departure point Williamtown, NSW
Destination Sydney, NSW
Damage Nil

Aircraft details

Manufacturer Beech Aircraft Corp
Model 200
Registration VH-KCH
Serial number BB-1125
Sector Turboprop
Operation type Military
Departure point East Sale, VIC
Destination Williamtown, NSW
Damage Nil

Embraer EMB-120 ER, VH-FNQ

Summary

As the pilot of the Brasilia was applying take-off power, a nickel leading edge erosion strip separated from one of the left propeller blades. The strip then bounced off the tarmac under the aircraft and struck the right propeller blades. The engines were shut down and all passengers disembarked safely.

The propeller blades had completed a total of 17,161 hours in service. The last repair work including the fitment of the nickel sheath protective strips took place approximately 2,100 hours prior to the incident.

The erosion strip was recovered and was forwarded for specialist metallurgical examination. This examination confirmed that the erosion strip had separated due to loss of adhesion at the adhesive to sheath interface.

The propeller blade and the failed portions of the nickel sheath were returned to the manufacturer for detailed examination including investigation of the procedures used to perform the nickel sheath replacement. It was found that the sheath had been bonded using an approved adhesive AF111. Inspection of the nickel sheath showed that the surface had been prepared correctly prior to the adhesive being applied. Examination of the blade and nickel sheath showed the cause of the separation to be cracking of the sheath-to-blade bond joint. Spectrum analysis of the adhesive showed the presence of silicone.

The investigation determined that this contamination was introduced during the bonding process. Review of the process showed that an adhesive tape containing silicone had been used, and this is considered to be the most likely cause of the introduction of silicone.

The propeller manufacturer has reviewed its procedures associated with this process. Improvements have been identified and are being incorporated into the manufacturer's Component Maintenance Manuals.

Occurrence summary

Investigation number 199805073
Occurrence date 13/11/1998
Location Bundaberg, Aero.
State Queensland
Report release date 06/09/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Propeller/rotor malfunction
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Embraer-Empresa Brasileira De Aeronautica
Model EMB-120
Registration VH-FNQ
Serial number 120-054
Sector Turboprop
Operation type Air Transport Low Capacity
Departure point Bundaberg, QLD
Destination Brisbane, QLD
Damage Minor

Saab SF-340A, VH-LPI

Summary

On 11 November 1998, VH-LPI, a Saab 340A turbo-propeller aircraft was enroute between Albury, NSW and Melbourne, Victoria on a scheduled public transport service. The aircraft was operating in instrument meteorological conditions and had accumulated a deposit of ice on the wings and windscreen wipers. The crew interpreted this ice deposit as being less than that required for them to activate the de-ice systems on the wing leading edges, in accordance with the aircraft flight manual procedures. As the aircraft approached Melbourne the crew were instructed to enter a holding pattern at Eildon Weir. The crew acknowledged this instruction and reduced power in order to slow the aircraft to the holding pattern airspeed. The crew subsequently allowed the airspeed to fall below the target speed of 154 knots, and despite remedial action, did not regain the target speed.

Shortly after the aircraft entered the holding pattern it suffered an aerodynamic stall and rolled approximately 126 degrees to the left and pitched nose down to approximately 35 degrees. The crew regained control after approximately 10 seconds. The aircraft lost 2,300 ft of altitude. The crew was not provided with a stall warning prior to the stall.

The investigation found that despite being certified to all required certification standards at the time, the Saab 340 aircraft can suffer from an aerodynamic stall whilst operating in icing conditions without the required warnings being provided to flight crew. This problem had been highlighted when the aircraft was introduced to operations in Canada and as a result a modified stall warning system was mandated for aircraft operated in Canada. This modification was not fitted to other Saab 340 aircraft worldwide.

The investigation also found a number of other occurrences involving Saab 340 aircraft where little or no stall warning had been provided to the crew while operating in icing conditions. Deficiencies were found in the operator's manuals, procedures and training.

During the course of the investigation, a number of recommendations were made in 1998 and 1999 concerning flight in icing conditions and modifications to the Saab 340 stall warning system. The completion of the investigation and finalisation of the report were the result of extensive consultation with the aircraft manufacturer and certification authorities.

Occurrence summary

Investigation number 199805068
Occurrence date 11/11/1998
Location Eildon Weir
State Victoria
Report release date 15/05/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Incident
Highest injury level Minor

Aircraft details

Manufacturer Saab Aircraft Co.
Model 340
Registration VH-LPI
Serial number 340A-151
Sector Turboprop
Operation type Air Transport Low Capacity
Departure point Albury, NSW
Destination Melbourne, VIC
Damage Nil

Beech Aircraft Corp C90-B80, VH-FDZ

Summary

The pilot of the Beechcraft King Air reported that just prior to touchdown, the elevator control forces changed abruptly, causing an uncommanded pitch down. The nosewheel struck the surface of the airstrip and the aircraft bounced twice. During the subsequent landing roll, the nose landing gear collapsed and the propellers struck the ground.

An investigation by the operator found that an elevator servo in the autopilot system was malfunctioning. The unit would not disengage when the autopilot was turned off. The mode in which the servo operated on the test bench was consistent with the control forces experienced by the pilot during the landing. Because of the aircraft's proximity to the ground, the pilot had been unable to counter the unexpected forces in time to prevent the nosewheel from striking the ground prematurely.

A manufacturer's product improvement service bulletin, issued soon after the aircraft was manufactured, had not been implemented on this servo unit. The modification was to improve the mechanical integrity of the engage clutch assembly and eliminate the possibility of the clutch not disengaging due to mechanical interference between various parts of the clutch assembly and the servo casting.

The operator forwarded its investigation report to BASI and the Civil Aviation Safety Authority and recommended that the Service Bulletin be upgraded to ensure that all servos of the type still in service were modified.

The Civil Aviation Safety Authority informed BASI that it believes that the occurrence was an isolated incident involving this model servo unit and accordingly, airworthiness directive action is not considered to be warranted at this time.

Occurrence summary

Investigation number 199804978
Occurrence date 10/11/1998
Location Coen Township, (ALA)
State Queensland
Report release date 29/07/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Hard landing
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer Beech Aircraft Corp
Model 90
Registration VH-FDZ
Serial number LJ-1021
Sector Turboprop
Operation type Aerial Work
Departure point Cairns, QLD
Destination Coen Township, QLD
Damage Substantial

de Havilland Canada DHC-8-102, VH-TQF

Analysis

The complexity of the traffic sequence for the ADC was increased by the amount of traffic in the area, and by the fact that the pilot of the turbojet aircraft conducted a go-around. However, had the ADC instructed the Cheetah pilot to report prior to turning base or final for runway 30, he would have had some options to better manage the traffic sequence. The ADC could have also utilised one of the other controllers to assist in the sequencing of the traffic, by monitoring the flight of the Cheetah.

Once the ADC recognised that the use of the intersecting runways was not possible, the use of the appropriate and complete RTF for the situation would have assisted in minimising the possibility for conflict. Under the circumstances, the use of the RTF for emergency conditions may have been appropriate. In his haste to ensure that the Dash 8 received the instruction to hold, the ADC compounded the situation by not allowing the crew time to acknowledge the take-off clearance prior to issuing the hold instruction. Had the ADC transmitted after the crew had completed their acknowledgment, it is probable that they would have clearly received, and been able to safely respond to, the hold instruction.

The use of land-and-hold-short procedures for the particular runways in use was not an option for the ADC.

Summary

The aerodrome circuit was active with a number of aircraft conducting circuit training, or inbound for landing. Both runways 35 and 30 were in use. Runway 30 intersected runway 35 approximately 750 m from its threshold. The tower was staffed with three controllers operating the aerodrome control (ADC), coordination and surface movement control positions.

The ADC had instructed the crew of a De Havilland Dash 8 (Dash 8) to line up for a departure from runway 35. The pilot of an American Aircraft Corporation Cheetah (Cheetah) had been instructed to continue approach for runway 30. The ADC cleared the Dash 8 crew for take-off and then looked towards the final approach path for runway 30 to monitor the approach of the Cheetah. As the ADC completed the transmission to the Dash 8 crew, he saw that the Cheetah was on short final and immediately transmitted an instruction to the Dash 8 crew to hold their position. This instruction was over-transmitted by the acknowledgment of the take-off clearance by the pilot in command of the Dash 8. The ADC commenced to issue a land-and-hold-short instruction to the pilot of the Cheetah; however, seeing that the Dash 8 was starting its take-off roll, he ceased the transmission and issued a further instruction to the Dash 8 crew to hold position. This instruction was over-transmitted by the Cheetah pilot reporting that he was initiating a go-around. The Dash 8 became airborne prior to the intersection of the runways, however, the crew held their aircraft at approximately 50 ft above ground level while the Cheetah passed approximately 100 ft above and slightly behind the Dash 8.

The automatic voice recording of the radio transmissions from the ADC during this period indicated that there were few or no intervals between any of his transmissions. The pilot of another aircraft that was operating in the circuit heard the hold-short instruction. The crew of the Dash 8 reported that they did not hear either of the hold-short instructions.

The ADC had formulated a traffic plan but this changed when a turbojet aircraft he thought was going to conduct a full-stop landing on runway 35, conducted a touch-and-go. The ADC had instructed the crew of the Dash 8 to line up on runway 35 after the approach of the turbojet aircraft, and had amended the approach of the Cheetah to runway 30 to facilitate the departure of the Dash 8. The ADC did not instruct the pilot of the Cheetah to report at a position that would have enabled him to adjust the traffic sequence if required. There was also a delay between the time the ADC approved the Dash 8 crew to line up, and the eventual issue of the departure instructions and a clearance. This delay was due to radio transmissions from the pilot of the turbojet aircraft, as well as the coordination of inbound traffic with the approach controller. During this period, the Cheetah pilot had continued his approach to runway 30. The ADC did not check the position of the Cheetah in relation to the intersection of the runways prior to issuing the take-off clearance to the Dash 8 crew. That was done as he was completing the transmission of the take-off clearance to the crew. As a final action to resolve the conflict between the aircraft, the ADC proposed to issue a land-and-hold-short instruction to the pilot of the Cheetah; however, the landing distance available (590 m) to the pilot did not meet the distance required (900 m) for land-and-hold-short operations.

The Manual of Air Traffic Services details the radiotelephony phraseology (RTF) to be used by controllers to cancel take-off clearances or to stop a take-off in emergency conditions. The ADC used only part of the required RTF for the cancellation of the take-off clearance. He did not use the RTF for an emergency situation.

Occurrence summary

Investigation number 199804856
Occurrence date 07/11/1998
Location Canberra, Aero.
State Australian Capital Territory
Report release date 23/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 De Havilland Canada/De Havilland Aircraft of Canada
Model DHC-8
Registration VH-TQF
Serial number 067
Sector Turboprop
Operation type Air Transport Low Capacity
Departure point Canberra, ACT
Destination Sydney, NSW
Damage Nil

Aircraft details

Manufacturer American Aircraft Corp
Model AA-5
Registration VH-TXA
Serial number AA5A-0241
Sector Piston
Operation type Private
Departure point Unknown
Destination Canberra, ACT
Damage Nil

Boeing 747, ZS-SAN

Safety Action

As a result of this and a similar occurrence, the Bureau of Air Safety Investigation is currently investigating a perceived safety deficiency. The deficiency relates to the notification of approved long range navigation systems to ATS.

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

Summary

A Boeing 747 (B747) was en route between Sydney and Perth, tracking via air route Q158. The crew contacted Perth air traffic control at waypoint BIDDY, and were issued with a standard terminal arrival route (STAR) to Perth. The controller and the crew entered into a discussion regarding Perth STARs. The crew were asked if the aircraft was Area Navigation (RNAV) equipped and replied that the aircraft was not so equipped. Aircraft that are not RNAV equipped are not permitted to track on air route Q158 from Sydney to Perth.

The investigation subsequently revealed that the aircraft was RNAV equipped and therefore, permitted to use Q158. There was no infringement of separation standards.

Occurrence summary

Investigation number 199804738
Occurrence date 26/10/1998
Location Biddy
State Western Australia
Report release date 19/07/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Miscellaneous - Other
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 747
Registration ZS-SAN
Sector Jet
Operation type Air Transport High Capacity
Departure point Sydney, NSW
Destination Perth, WA
Damage Nil

Boeing 767-238, VH-EAL

Summary

A Piper Seminole was being flown from Essendon airport, which is located 5 NM south-east of Melbourne airport, to Bendigo. The extended centrelines of the respective northerly runways, which were being used for arrivals and departures, are approximately 3 NM apart. The wind at the time was northerly at 25 kts.

The pilot of the Seminole was instructed to maintain runway heading of 350 degrees and climb to 6,000 ft. After take-off the aircraft was identified on radar by the Melbourne departures north (DEPN) controller.

Six minutes later the crew of a Boeing 767 (B767) was cleared to take-off from runway 34 at Melbourne, for Sydney, and to maintain runway heading on climb to 5,000 ft. After take-off the aircraft was identified on radar by the DEPN controller who cleared the crew to climb to flight level (FL) 200.

Traffic was light, with four departing and one arriving aircraft being managed by the DEPN controller. The controller was aware of the need to maintain either vertical or lateral separation between aircraft departing from Melbourne and the Seminole, and was also conscious that the present heading of the Seminole was not in the direction of Bendigo. He had previously radar vectored a departing Boeing 737 ahead of the Seminole, and planned to do the same with the B767, however, he observed that the B767 did not appear to be climbing as fast as he had expected. Consequently, the controller would have to take both the B767 and the Seminole further to the north before achieving sufficient vertical or lateral separation to enable him to allow the aircraft to resume their respective planned routes. The minimum required separation was either 3 NM lateral or 1,000 ft vertical.

When the B767 was approximately 7 NM to the south-west of the Seminole the controller believed he could vector the B767 to pass behind it, thus minimising any delay to both aircraft. The controller did not issue instructions to ensure vertical separation prior to turning the B767.

The B767 was vectored right, onto a heading of 040 degrees. Shortly after, the Seminole was vectored left onto a heading of 270 degrees. The DEPN controller then instructed the B767 crew to continue the right turn onto 060 degrees as the aircraft was passing approximately 4,500 ft, and instructed the pilot of the Seminole to turn right onto 290 degrees. The B767 crew was requested to expedite the turn onto 090 degrees. Shortly after, the crew reported receiving a traffic alert and collision avoidance system (TCAS) resolution advisory, indicating the crew should maintain the current altitude of approximately 5,400 ft due to a conflicting aircraft. The crew complied, and advised the DEPN controller accordingly. The controller advised the crew that they had passed another aircraft that was to their left. Separation was reduced to 1.5 NM lateral and 600 ft vertical. The B767 crew did not sight the other aircraft.

The B767 crew subsequently reported that the wind at 5,000 ft was westerly at 50 kts. This would have had the effect of increasing the groundspeed of the B767 as it turned towards the east. Consequently, the rate of closure between the B767 and the Seminole would have been greater than anticipated by the controller, and it was probably at that stage he became aware that the aircraft might pass with less than the required separation. However, his subsequent instructions were unable to rectify the situation. Had the controller continued to employ separation assurance techniques, the occurrence would probably not have eventuated.

Occurrence summary

Investigation number 199804849
Occurrence date 25/10/1998
Location 19 km NE Melbourne, (VOR)
State Victoria
Report release date 20/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 767
Registration VH-EAL
Serial number 23306
Sector Jet
Operation type Air Transport High Capacity
Departure point Melbourne, VIC
Destination Sydney, NSW
Damage Nil

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-44
Registration VH-ZWI
Serial number 44-7995219
Sector Piston
Operation type Unknown
Departure point Essendon, VIC
Destination Bendigo, VIC
Damage Nil