Fairchild SA226-TC, VH-EEQ

Safety Action

As a result of this investigation the following interim recommendations were issued.

IR19990112

The Bureau of Air Safety Investigation recommends that the engine manufacturer, AlliedSignal, audit the process employed to manufacture TPE 331 turbine wheel knife-edged seals should be audited to determine those factors that may lead to excessive variations in slot corner radii.

IR19990113

The Bureau of Air Safety Investigation recommends that the engine manufacturer, AlliedSignal, determine the sensitivity of turbine wheel seals to the initiation of fatigue cracks from slot corners, as a function of slot corner radii.

IR19990114

The Bureau of Air Safety Investigation recommends that the engine manufacturer, AlliedSignal, consider, during engine design and the formulation of continuing airworthiness instructions, the possibility that turbine wheel seal fatigue failure may result in hazardous modes of engine failure.

IR19990115

The Bureau of Air Safety Investigation recommends that the Civil Aviation Safety Authority Australia conduct an audit of that part of the aviation safety system that establishes the operational history of life-limited components, to establish why the operational history of second-stage turbine wheel, p/n 868272-1, s/n P03214C, could not be determined with certainty.

IR19990116

The US Federal Aviation Administration should note the safety deficiency identified in this document and take appropriate action as considered necessary.

Analysis

The uncontained failure of the second-stage turbine wheel was caused by the progressive reduction of the wheel cross-section, during operation, near the transition from the hub to web. No material anomalies or regions of pre-existing crack growth were associated with the separation of wheel segments.

Analysis of the recovered turbine components revealed that the reduction in wheel cross-section was caused by the effects of sliding contact with sections of the fractured second-stage wheel knife-edged seal. The web was reduced from original approximately 13 mm to approximately 8.5 mm.

Examination of the remnants of the second-stage seal indicated that the fracture of the seal had occurred as a result of fatigue crack growth from the radii at the corners of the slots formed in the forward edge of the seal.

A significant variation in the radii of the slot corners was noted when a comparison was made between the fractured seal and the seal from another second-stage wheel assembly. The one intact slot corner of the fractured second-stage wheel seal was sharper and did not display the smoothly rounded characteristic of the corners of other seals. A decrease in radius would create an increase in stress concentration and increase the likelihood of fatigue crack initiation.

Summary

The right engine of a Fairchild Metro II aircraft, VH-EEQ, failed at the top of descent to Launceston. The aircraft subsequently completed an uneventful single-engine landing. On-site inspection revealed that the engine failure was caused by the disintegration of the second-stage turbine wheel and that segments of the wheel had penetrated the engine nacelle. One fragment penetrated the fuselage and was found lodged in the cabin lining.

The AlliedSignal TPE331-3U-304G engine, serial number P03214C, was reported to have completed 6,017.4 hours and 6,273 cycles since new.

The second-stage wheel was identified as part number 868272-1, serial number 1-01345-1313. The recorded history of the second stage wheel indicated that the wheel had been in service for a total of 2,972.84 hours and 2,878 cycles at the time of failure on 5 March 1999. The wheel was installed new in engine s/n P90105 on 11 Jan. 1982. It was removed from engine s/n P90105 on 25 Sept. 1992 with a recorded service life of 564.74 hours and 508 cycles. The wheel was installed in engine s/n P03214C on 30 Aug. 1994 with a recorded history of 564.74 hours and 508 cycles in service. There remain, however, uncertainties in the recorded service history of the part.

Occurrence summary

Investigation number 199901064
Occurrence date 05/03/1999
Location 54 km NNW Launceston, (VOR)
State Tasmania
Report release date 03/09/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Fairchild Industries Inc
Model SA226
Registration VH-EEQ
Serial number TC-251
Sector Turboprop
Operation type Charter
Departure point Melbourne, VIC
Destination Launceston, TAS
Damage Minor

Bell 47J-2A, VH-THH

Summary

A Bell 47J helicopter was being ferried by two pilots from Lyndock SA to Kings Creek Station NT over a period of 3 days. Refuelling stops were planned for Port Augusta, Roxby Downs, Coober Pedy, Cadney Park if required, and Kulgera. Additional equipment was also carried, including a ground refuelling hose and pump unit, aircraft manuals, hand tools, additional engine oil, water, and seven 20 L jerry cans of fuel.

The flight was uneventful to Cooper Pedy where a flight plan was lodged nominating Cadney Park and Kulgera as landing points. The helicopter subsequently departed at about 0730. When it failed to arrive at Cadney Park or Kulgera, a search was initiated. The burnt-out wreckage of the helicopter was located 2 days later in flat, open, sparsely timbered country, about 1 NM south-west of Temptation Bore and approximately 152 NM from Coober Pedy, close to the direct track to Kulgera. The accident was not survivable.

At the time of the accident the weather was fine and clear, with a light breeze from the south-east, and a temperature in the vicinity of 30 degrees Celsius.

Examination of the wreckage did not reveal any pre-existing defects which may have contributed to the accident. An intense post-impact fire fuelled by the fuel from the jerry cans had consumed the cockpit and forward section of the tail boom. The engine displayed severe impact and external fire damage, but all internal components were intact, well lubricated, and capable of normal operation. The fire had destroyed the fixed emergency locator transmitter mounted on a bracket at the forward section of the tail boom. The remains of a hand-held emergency locator beacon were found in the debris of the burnt cockpit. The damage sustained by the main and tail rotor assemblies was consistent with the transmission system not being powered at the time of impact. The rotational velocity of the main and tail rotor assemblies was very low at impact and it was likely that the main rotor RPM was too low for a controlled descent. Damage sustained by the engine cooling fan indicated it was not rotating at impact. Some of the flight control systems had been consumed by the fire, but the remainder were correctly connected and functioned normally. The pilot's collective lever and cyclic control stick had separated during the impact. Both displayed bending overload failures but no fire damage was evident.

One main fuel tank had collided with a main rotor blade during the impact sequence. That tank was ruptured and deformed from collision with the blade, and contained a minute quantity of fuel, but displayed no evidence of fire damage. The other main fuel tank was ruptured and heavily sooted externally, but contained no fuel, and there was no evidence of fire internally. The remainder of the fuel system was too extensively damaged to determine if a fuel leak had existed during flight. Of the seven jerry cans, most were ruptured and heavily sooted externally. Fire and explosives experts' analyses determined that the main tanks contained only a small quantity of unusable fuel at impact. The intensity of the fire indicated that there was a substantial quantity of fuel in the jerry cans. Earth displaced from the impact craters made by the forward cockpit section and tailskid was consistent with the helicopter being in a nose-down attitude, with some forward velocity at impact.

Maintenance records for the helicopter indicated that it had been correctly maintained in accordance with an approved system of maintenance. The maintenance release was current, and there were no outstanding maintenance requirements.

Both pilots were appropriately licensed for the flight. The pilot flying at the time of the accident had about 350 hours of rotary wing flight time, but had limited experience on the Bell 47J type. The pilot in the rear seat had over 7,000 hours rotary wing flight time, but his logbook indicated that he had not operated the Bell 47 type since before September 1997.

The estimated weight and balance of the helicopter on departure from Coober Pedy indicated that the centre of gravity was within approved limits and its weight was within the authorised maximum take-off weight.

The investigation determined that the main fuel tanks of the helicopter and the seven additional 20 L jerry cans were full when it departed Lyndock. The fuel management between Lyndock and the final refuelling at Coober Pedy could not be determined. After refuelling at Coober Pedy on the evening before the accident flight, the helicopter was hover taxied to another area for overnight parking. The main tanks were therefore less than full at departure from Coober Pedy the next morning. The range of the helicopter with full main tanks was insufficient to reach Kulgera and it would have had to land en route to be refuelled from the jerry cans in order to reach its destination.

It was reported that the pilot in the rear seat had flown the route several times and was known to refuel at locations of high visibility. He had refuelled at Aston Hill, about 15 NM north-north-west of Cadney Park on previous occasions but there was no evidence to suggest that the helicopter had landed between Coober Pedy and the accident site on this occasion.

Calculations using the known fuel quantities purchased at the previous enroute refuelling stops, indicated that the range of the helicopter with full main tanks should have been sufficient to reach Temptation Bore. The pilot may have been planning to land and refuel at Temptation Bore, which would have been visible in the near distance when the engine stopped from fuel exhaustion. The reason the engine stopped from fuel exhaustion and why the helicopter then collided heavily with the ground in a nose low attitude, with the rotor system rotating well below the speed required for a controlled descent, could not be determined.

Occurrence summary

Investigation number 199901057
Occurrence date 07/03/1999
Location 282 km NNW Coober Pedy, Aero.
State Northern Territory
Report release date 17/03/2000
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel exhaustion
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Bell Helicopter Co
Model 47
Registration VH-THH
Serial number 3711
Sector Helicopter
Operation type Aerial Work
Departure point Coober Pedy , SA
Destination Kulgera, NT
Damage Destroyed

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

Bell 206L-3, VH-NDW

Safety Action

Action by the helicopter operator

Within a few weeks of the accident, the helicopter operator informed the Bureau that it had taken the following actions:

"1. Amended Section A.7 of the company operations manual to include the following:

A7.2 DETERMINATION OF METEOROLOGICAL MINIMA

  • If weather deteriorates to below published VFR, pilots are to have an alternate route or landing route.
  • In Controlled Airspace or Control Zones, pilots are to request special VFR from ATC
  • Outside Controlled Airspace, pilots may operate to Special VFR Minima.
  • If enroute weather conditions deteriorate to cloud base of 500 feet agl or less, and or visibility of 800 metres or less, the pilot should proceed via the alternate route or to the alternate landing area.
  • Advise ATC and base of intentions.
  1. Engaged a consultant to facilitate the establishment of a comprehensive safety management system within the company."

Discussion with the operator on 9 March 2000 indicated that as a result of legal advice, implementation of the safety management system had been suspended until the accident report and Coronial processes had been completed.

SAFETY ACTION

As a result of this occurrence, the Australian Transport Safety Bureau (formerly BASI) made the following recommendation.

R20000003

The Australian Transport Safety Bureau (formerly BASI) recommends that the Aviation Rescue and Fire Fighting (ARFF) unit and Cairns Port Authority examine the adequacy of the current launch facilities for the ARFF rescue boat against the benefits which might accrue from a launch ramp on or adjacent to the airport.

Significant Factors

  1. The Cairns area was under the influence of south-easterly stream weather, which included periods of low cloud and very heavy rainfall.
  2. The pilot continued the flight on the direct track from Green Island to The Pier in conditions of deteriorating visibility.
  3. The pilot experienced sudden white-out conditions that deprived him of all external visual reference.

Analysis

The circumstances of the accident indicated that the pilot continued the flight into adverse weather conditions to the point where flight using external visual reference was no longer possible. Because the helicopter was not certified for instrument flight, and the pilot's instrument flying experience was minimal, continuation of the flight in the deteriorating conditions, including turning the helicopter onto a reciprocal track without visual cues, involved risk. The pilot's only viable option at that point was to attempt a water landing. In the event, there was insufficient outside visual reference for him to achieve a skids level, zero speed landing.

The pilot indicated that initially there was a gradual, rather than sudden, decrease in visibility. However, the deterioration from low visibility to white-out conditions occurred very rapidly.

There was no indication that a return to Green Island or tracking via another route formed part of the pilot's strategy for the flight. A number of factors could have contributed to this:

  1. The pilot's operating culture was conditioned from having "got through" adverse weather on previous occasions.
  2. Having decided to track via the shipping channel because of turbulence considerations on the coastal route, the pilot effectively "locked out" the coastal route as an alternate course of action.
  3. The weather information passed by the tower controller probably placed an expectation in the pilot's mind that he could negotiate the weather successfully.
  4. The pilot may have experienced subtle pressure as result of the "have a good look before turning back" culture.

The recorded radar data indicated that the pilot maintained steady control of altitude and speed through most of the flight. The only significant deviation occurred when the controller noted and advised the pilot of the altitude change from 100 ft to 200 ft and back again. This information does not indicate that the malfunctioning ASI had a significant affect on the pilot's control of the helicopter, or the eventual outcome of the flight.

The elapsed time between activation of the airport emergency plan and the ARFF rescue boat's arrival at the crash scene was 22 minutes. The journey from the airport to the Marlin Marina boat ramp took 17 minutes. While there was no consequence for this accident, the absence of a boat ramp into the Barron River at the airport added significantly to the rescue boat launching time.

Summary

The helicopter company's operations, based at Cairns Airport, Queensland, included passenger charter flights between The Pier, at Cairns Harbour (4 km SE Cairns Airport) and Green Island (22 km NE Cairns Airport).

At about 1035 eastern standard time the pilot departed The Pier for Green Island in a Bell 206 helicopter with six passengers on board. Because of the likelihood of mechanical turbulence in the lee of the high terrain south of Trinity Inlet, he initially tracked via the Cairns Harbour shipping channel. When he reached the end of the shipping channel, he was unable to see the island because of rain so he descended from his cruise altitude of 500 ft to about 300 ft and was then able to see the island about 9 km ahead. The helicopter arrived at Green Island at about 1045.

At 1130, the pilot departed Green Island for The Pier with six passengers on board. There was light drizzle falling at the time but he assessed that conditions in the area were suitable for flight utilising external visual reference. The pilot again elected to track via the shipping channel. Clearance to enter the Cairns Control Zone was not immediately available because of other traffic, so the pilot conducted a number of orbits in the helicopter until he was issued with a clearance at about 1139 to track to The Pier via the shipping channel, not above 500 ft. The controllers advised the pilot that, within 7-9 km from The Pier, the cloud base was 800-1,000 ft, with some showers, and visibility less than 10 km.

As the pilot continued tracking along the shipping channel, using the channel beacons as track markers, he noticed that the weather conditions ahead were deteriorating. A short time later, he descended the helicopter to about 150 ft to keep the water surface in sight, and reduced speed. At about 1143, the controller cautioned the pilot that a parasail was operating in the Cairns Harbour area. A short time later, the pilot received a request for his arrival time from the company's office at The Pier. He responded that he expected to arrive in 5 minutes.

The pilot later reported that by that time the weather conditions had deteriorated further, he was flying at 50 ft or less above the water in light to moderate rain and could no longer see any channel beacons. He selected the windscreen demister on as condensation had begun to form on the inside surface. He also armed the inflatable floats that were fitted to the skid-type landing gear.

At about 1146, the pilot asked the controller for directions to The Pier. The tower controller advised that The Pier was on a bearing of 205 degrees M, at a range of 1.5 NM (3 km). At about that time, in-flight visibility rapidly deteriorated to an extent where external visual cues were not available. The pilot, noticing that the altimeter was indicating 100 feet, placed the helicopter in a gentle descent in an attempt to keep the surface of the water in sight. The helicopter contacted the water a short time later and rolled inverted. The pilot and five passengers quickly escaped from the fuselage to the surface of the water. One passenger was trapped in the cabin for a number of minutes and did not survive the accident.

The helicopter was certified for flight under the Visual Flight Rules and was equipped with a satellite navigation system receiver. Inflatable floats were attached to the skid type landing gear. These could be inflated by the pilot in the event of a water landing. The helicopter was not fitted with a radio altimeter.

The Cairns area was under the influence of south-easterly stream weather. The Bureau of Meteorology issued an amended aerodrome forecast for Cairns at 0808 for the 24-hour period from 1000. The forecast was for an easterly wind at 15 kt, visibility of 9,000 m, and light rain. Some cloud patches were expected with a base of 800 ft, a broken layer at 1,800 ft, and overcast at 10,000 ft. Periods of up to 1 hour of heavy rain, scattered cloud at 800 ft, and broken cloud at 1,500 ft were expected over the forecast period.

Controllers on duty in the tower indicated that the weather conditions had been fluctuating significantly and rapidly throughout the morning. There were periods when conditions met the criteria for VFR flight. This contrasted with intervals of low cloud and very heavy rain, amongst the worst conditions they had seen at Cairns. Radar images and rainfall rates suggested that visibility in the area of the accident could have been reduced to a few hundred metres or less. Personnel who were at The Pier at the time of the accident described the rainfall as torrential, with visibility as low as one car length.

A weather radar system operated by the Bureau of Meteorology was located at Saddle Mountain, approximately 11 km north-west of Cairns Airport. The weather radar data recorded at 1150 showed an area of moderate rainfall centred over Cairns Harbour, adjacent to Cairns City. It extended about 5.4 km north-south and about 3.6 km east-west.

The weather information the controller passed to the pilot was based on his visual assessment of the weather in Cairns Harbour as he saw it from the control tower. When the controller issued the caution to the pilot regarding the parasail, the radar indicated altitude of the helicopter was 100 ft.

The Bureau of Meteorology advised that conditions of minimum visibility at Cairns Airport occurred during the period between about 1155 and 1210. The recorded rainfall of 5.8 mm between 1150 and 1210 at Cairns Airport was similar to that which would be encountered in thunderstorms. Although there was an automatic weather station at Green Island it was not equipped to measure rainfall.

Examination of recorded Air Traffic Services radar data provided information on the track, altitude, and groundspeed of the helicopter for a portion of the flight. The data indicated that the helicopter was initially tracking via the Cairns Harbour shipping channel at about 100 kts and an altitude of 200 ft above mean sea level. At about 7 km from The Pier, the speed gradually decreased to 55-60 kts and then to below 40 kts. The last recorded speed was 31 kts. The recorded altitude during the final 2 minutes of the recording was 100 ft, apart from one value of 200 ft. The last recorded position of the helicopter was 2.4 km north-east of The Pier at about 1148.

Examination of the wreckage confirmed that the helicopter struck the water in a slight left skid-low, nose-low attitude, and at low forward and vertical speeds. All seats and safety harnesses retained their integrity. There was evidence of flexing of the roof frame on the right forward side of the cabin, immediately behind the pilot's seat resulting from induced stresses following main rotor blade contact with the water.

The postmortem examination report stated that the non-surviving passenger had received a minor head injury that may have had sufficient effect to prevent her from releasing her safety harness. The examination established that the passenger died as a result of drowning. The flexing of the cabin roof occurred above the seating position of the passenger who was trapped in the helicopter. It is possible that the roof flexed sufficiently to cause the head injury to that passenger.

Company ground staff who worked at Green Island conducted a safety briefing (in Japanese) for the passengers. Those staff had completed proficiency testing in emergency procedures applicable to Bell 206 helicopters. The operation of the life jackets, seat belts, and emergency exit procedures was demonstrated. The information was summarised on safety information cards (in English and Japanese) in the helicopter. Each passenger wore a life jacket contained in a belt-mounted bag.

The pilot said that, after the cabin filled with water, he was able to easily egress from the helicopter. When he surfaced, he saw 2 or 3 passengers on the opposite (left) side of the upturned fuselage. He dived and attempted to open the passenger door on the right side of the helicopter but was unable to do so. When he next surfaced, there were 5 passengers on the surface. He made a number of further attempts to open the right side door but could not. Two passengers had made a few dives from the opposite side of the helicopter and they brought the injured passenger to the surface.

The pilot reported that, during an earlier positioning flight to The Pier, the airspeed indicator (ASI) was not functioning normally in that it did not indicate above 40 kts. He thought that the fault was probably due to water in the pitot-static system and expected it to clear during the flight to Green Island. However, the fault remained. After landing at Green Island, the pilot sucked then blew into the pitot head in an attempt to remove any blockage that might be in the system. Because there were no maintenance facilities on the island, there was no means of assessing the serviceability of the instrument before the subsequent flight. The ASI did not function during the accident flight. The pilot said that he relied on the ground speed display on the GPS for speed information during the flight. He did not consider that this had any meaningful affect on his cockpit workload during the flight.

The opinion of other experienced helicopter pilots spoken to during the investigation was that the absence of an ASI would have increased the pilot's workload, particularly in view of the weather conditions. The erroneous indication on the ASI and the need to refer to the GPS display would have disrupted the pilot's normal instrument scan pattern. Further, the GPS displayed ground speed, not "airspeed", so the speed information the pilot was receiving was not appropriate to some flight regimes. Civil Aviation Order Part 20, Section 18 specifies that, for VFR charter operations, a helicopter must be equipped with a serviceable ASI prior to take-off.

The company advised that periods of poor weather usually generated higher demand for helicopter flights because rough seas and/or rain discouraged some tourists from returning to Cairns by boat. The pilot indicated that the company expected the pilots to "give it a go" in the case of bad weather. The company indicated that pilots were expected to "have a good look before turning back" during operations away from the departure area, but that there was no pressure placed on pilots to complete flights in unsuitable weather conditions.

The pilot was programmed to conduct a number of other flights later in the day. However, he stated that the schedule had no bearing on his decision to depart Green Island. The pilot reported that the usual routes from Green Island to Cairns were via the shipping channel, or coastal via False Cape. Wind from the south or south-east at about 15 knots or greater caused mechanical turbulence in the lee of the high terrain on the southern side of Trinity Inlet. Under such conditions he usually avoided the False Cape/coastal route because of passenger comfort considerations. The accident flight was one such instance.

The pilot said that when he departed Green Island, the weather conditions easily met the VFR criteria. His technique in conditions of deteriorating visibility was to descend, maintain a visual reference outside the cockpit and to reduce speed. He applied this technique on the accident flight. Although visibility was poor, he continued, in part because of his experience in operating in similar conditions, but also because the advice from the controller indicated that the weather would improve as he neared Cairns. However, the pilot emphasised that he had turned back on a number of previous occasions because of unsuitable weather conditions.

The pilot stated that, even though he held a night VFR rating it was not current. In addition, he disliked instrument flight and had undertaken minimal instrument flying since achieving the rating in 1992. In any event, the helicopter was not certified for IFR flight. Against this background, he did not consider turning at low level to fly back towards better conditions as a safe option.

The pilot reported that the visibility conditions during the return flight from Green Island were the worst that he had experienced. The sea surface became flat and featureless and blended completely with the precipitation. By that time, it was too late to turn around. He reflected that he might have been better placed by tracking coastal because vegetation and other land features would have provided a higher level of visual contrast against the rain/cloud and may have enabled him to safely continue the flight. Alternatively, he would have been able to land the helicopter and await passage of the weather.

The aerodrome controller activated the Cairns Airport Emergency Plan at 1147 after the helicopter disappeared from radar and the pilot did not respond to radio calls. The police, ambulance, Queensland Emergency Service (QES) helicopter, and Cairns Aviation Rescue and Fire Fighting (ARFF) unit responded. The ARFF response involved dispatching a vehicle towing a trailer mounted rescue boat to Marlin Marina boat ramp, near The Pier. The vehicle arrived at the boat ramp at 1204 and the boat reached the crash scene at 1209. By that time, a tourist vessel and a seaplane were in attendance and the QES helicopter was overhead. All persons involved in the accident were placed aboard the tourist vessel and taken to the Marlin Marina boat ramp. The ARFF later commented that had a launching facility been available at the Barron River adjacent to the airport, they would have arrived on the scene much quicker.

Occurrence summary

Investigation number 199901009
Occurrence date 12/03/1999
Location 5 km SE Cairns, (VOR)
State Queensland
Report release date 31/03/2000
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category VFR into IMC
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Bell Helicopter Co
Model 206
Registration VH-NDW
Serial number 51290
Sector Helicopter
Operation type Charter
Departure point Green Island, QLD
Destination Cairns, QLD
Damage Substantial

Airbus A320-211, VH-HYT

Safety Action

Local safety action

As a result of this investigation the operator advised that the following actions were taken:

  1. All maintenance personnel were made aware of approved company maintenance procedures relating to APU's.
  2. Company personnel were instructed on the proper reporting procedures to ensure prevention of any further breakdown in the reporting chain.

As a result of this investigation the operator advised the following:

  1. The role and responsibility of personnel posted at reduced or single-engineer bases are to be clarified and reviewed.
  2. Arrangements for the ongoing supervision of personnel posted at reduced or single-engineer bases are to be reviewed.
  3. The occurrence is to be reviewed with respect to the company's standard crew resource management policy.
  4. The role and responsibility of ground personnel are to be reviewed and clarified with respect to non-normal and emergency situations.

Analysis

It is likely that during the time the engineer was away from the APU, with the oil dolly still connected, the faulty spool valve in the oil delivery line permitted the oil to continue to flow into the APU, resulting in an overfilled condition with excess oil draining into the tailpipe. The APU then surged and automatically shut down. The surge was probably caused by some of the excess oil within the APU escaping through the bearings and entering into the combustion chamber, where it was ignited. This would have resulted in a rapid increase in the exhaust gas temperature. Flame from the combustion would then have "torched" through the turbine stage into the tailpipe, where it ignited the overflow oil that had drained into the tailpipe.

The pilot in command was initially provided inadequate information regarding the APU problem. He was aware that the APU had shut down, and was informed that there was an APU fire. However, this was not confirmed by an ECAM message due to the location of the fire in the tailpipe. This series of events was an unusual situation and did not fit with the pilot in command's expectations of an APU fire. Had he been properly informed of the circumstances of the fire, it is unlikely that he would have considered it necessary to inspect the APU. Consequently, he would have been able to more rapidly respond to ensure the safety of the passengers and crew.

The operator was unable to immediately follow its post-occurrence investigation procedures due to delayed and incomplete reporting of the circumstances of the occurrence.

 

Summary

On 19 February 1999, while on the tarmac at Townsville with the auxiliary power unit (APU) operating, the crew of A320 Airbus VH-HYT observed an advisory message for "oil quantity below 1/4" on the electronic centralised aircraft monitoring (ECAM) cockpit display. The limitations section of the operator's A320 Operating Manual stated that the minimum before start APU oil quantity was 1/4. However, it also noted that with the ECAM low oil level message displayed, the APU should be considered unserviceable until an engineering inspection was conducted. This included a check of the APU oil level and inspection of the APU compartment and air intake for oil contamination.

The pilot in command notified the operator's Townsville maintenance engineer of the ECAM APU oil quantity message. The operator's procedure in response to a low APU oil quantity ECAM advisory message required that the APU be inspected for gross oil leaks and that the aircraft maintenance log APU oil servicing records be reviewed to determine oil consumption. However, because the APU bay was a controlled fire zone, the operator's maintenance procedures specified that the APU access door not be opened while the unit was operating.

The engineer opened the APU bay access door and inspected the operating APU for oil leaks. He then returned to the cockpit, where he consulted the aircraft maintenance log to review the APU oil servicing records. Noting that oil had not recently been added to the APU, the engineer advised the pilot in command that he would replenish the APU oil.

Passengers were already on board for the flight to Brisbane. Because of the prevailing hot and humid conditions, the engineer decided that, for reasons of passenger comfort, he would leave the APU running while he replenished the oil. This decision to add oil to the APU while it remained operating was in violation of the operator's standard policy and procedures, which stated that replenishment of APU oil may only be carried out while the unit is not operating.

The engineer connected the oil supply line from a mobile oil dolly to the operating APU. The oil dolly was equipped with a pressurised supply tank, with delivery of oil from the tank being controlled by a hand-operated spool valve in the oil delivery line. The engineer had determined that 1 L of oil should be added to the APU, and he calculated that it would take 15 seconds to deliver that quantity from the oil dolly into the APU. After the oil had been added, the engineer returned to the cockpit to observe whether the ECAM advisory message had extinguished, leaving the APU access hatch open and the oil delivery line still connected to the operating APU. The ECAM advisory remained illuminated, so the engineer returned to the APU bay. As he was climbing onto the workstand, a fire broke out in the APU tailpipe and the APU shut down.

The surface movement controller in the control tower observed fire and smoke coming from the tail of HYT. He sounded the crash alarm and radioed HYT on the surface movement control frequency, but there was no response. Three fire trucks responded immediately and parked in a fanned position around the aircraft's tail, with one truck being parked under the APU exhaust. Two firemen climbed onto the top of that truck to better observe the source of the fire and to determine the appropriate fire-fighting measures to be employed.

The crew had been conducting pre-flight checks when they noticed the APU shutdown. At the same time, they heard the sirens from the fire trucks, and a customer service officer entered the cockpit and notified the crew that the APU was on fire. However, the engineer also entered the cockpit and stated that the fire was under control, but he did not inform the pilot in command that the fire was located in the APU tailpipe and not in the APU bay.

HYT was equipped with a fire and overheat detection system located in the APU compartment. The system was designed to provide for automatic APU shutdown and agent discharge in the event of fire or overheat in the APU compartment while the aircraft was on the ground. A fire warning light was fitted to the overhead panel in the cockpit to alert the crew in the event of an APU fire. However, because the fire was located in the APU tailpipe, it did not activate the APU fire detection system and consequently there was no fire warning. After being advised that an APU fire had occurred, the pilot in command elected to leave the aircraft to obtain further information about the nature of the problem and its effect on the safety of the aircraft. Before leaving the cockpit, he made a public address to the passengers to advise that the aircraft had experienced a problem with its air-conditioning system, and that this would delay the aircraft's departure.

The pilot in command then left HYT through the left forward cabin door (L1) but did not brief the cabin manager, who was stationed at L1, about the nature of the problem. The cabin manager was therefore unable to plan for the possible evacuation of passengers from the aircraft. The pilot in command proceeded to the rear of HYT, where one of the fire crew informed him that the fire was still burning. The fire crew were unaware that passengers were already on board and when the pilot in command asked if they wanted the passengers off the aircraft, the fire controller instructed the pilot in command to disembark the passengers immediately. However, no instruction was given regarding doors that were not to be used for the disembarkation.

The pilot in command then ran back and instructed the cabin manager stationed at door L1 to disembark the passengers. Up until that point, the only information that the cabin manager had been given about the fire was from the customer service officer when the officer had entered the aircraft to advise the pilots of the problem. None of the other flight attendants were aware of the situation until the order to disembark the passengers was given. All passengers and crew were then disembarked through both the front and rear entry doors on the left side of HYT.

The airport fire crew discharged three 5 kg carbon dioxide bottles into the APU exhaust and the fire was extinguished. When the fire controller determined that HYT was safe, he released it to the crew. The engineer conducted a damage inspection of the aircraft and it was dispatched with the APU inoperative.

On arrival at Brisbane, the pilot in command lodged a general flight report stating that HYT had sustained an APU tailpipe fire at Townsville. The report noted that there was no fire warning or ECAM display associated with the APU tailpipe fire. The same day, the engineer reported to the operator's Melbourne maintenance base that HYT had sustained an APU tailpipe fire. Neither of these reports mentioned that the APU oil had been replenished while the unit was operating.

On 4 March 1999, the engineer lodged an accident/injury report of the event with the operator, noting that an APU tailpipe fire had occurred. On 5 March 1999, BASI received an air safety incident report from the company concerning the occurrence and on 8 March 1999, BASI also received an air safety occurrence report from RAAF Townsville.

On 10 March 1999, the operator interviewed the engineer. During the interview, it was established for the first time that the APU oil had been replenished while the unit was operating. The engineer advised the operator that on 21 February 1999, he and another engineer had inspected the spool valve of the oil dolly. The inspection was conducted to determine if oil continued to flow from the delivery hose with the spool valve in the closed position. The inspection revealed that the spool valve was faulty and that it had probably been faulty at the time of the occurrence.

Occurrence summary

Investigation number 199900990
Occurrence date 19/02/1999
Location Townsville, Aero.
State Queensland
Report release date 10/04/2000
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fire
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Airbus
Model A320
Registration VH-HYT
Sector Jet
Operation type Air Transport High Capacity
Damage Minor

Piper PA-25-235, VH-EVZ

Safety Action

Investigations into five fatal collisions between gliders and aero towing aircraft from 1986 cited the presence of unalerted traffic in a see-and-avoid environment as a contributing factor. The investigation into another two fatal mid-air collisions involving gliders cited the lack of alerted traffic information as a contributing factor. In nearly all of these occurrences the aircraft involved were radio-equipped and the pilots of the gliders either did not broadcast their intentions or did not respond to the other pilots' transmissions. Following the accident investigation of Occurrence 199700049 the Bureau issued recommendation R19970092 to the Gliding Federation of Australia on 8 August 1997 that related in part to traffic alerting procedures and high visibility marking of gliders. The response received from the GFA dated 8 September 1997 stated in part,

"The GFA recognizes that the rate of mid-air collisions involving gliders is unacceptably high in the circuit areas of aerodromes and will implement measures to improve discipline in flying the pattern and making better use of the radio".

The Bureau classified the response as CLOSED - PARTIALLY ACCEPTED.

Information in the 1991 research report "Limitations of the See-and-Avoid Principle" published by the Bureau of Air Safety Investigation and other research into the difficulties associated with visual acquisition of aircraft in an airborne environment, suggested that reliance on the see-and-avoid principle to provide reliable safe separation from other aircraft was inadequate without additional traffic alerting information. Repeated emphasis to pilots to be more vigilant and maintain an effective lookout has not reduced the incidence of mid air collisions in gliding activity. Implementing additional defences into a system that recognises and takes into consideration these limitations, such as more effective use of radio for traffic information, conspicuity and traffic segregation can improve the level of safety.

With the conclusion of the investigation into this occurrence the following recommendations are made:

R20000095

The Australian Transport Safety Bureau recommends that the Gliding Federation of Australia in conjunction with its member clubs incorporate the use of radio for effective traffic alerting into standard operating practices as a matter of priority.

R20000096

The Australian Transport Safety Bureau recommends that Civil Aviation Safety Authority review the assessment process for the issue of a radiotelephone operator certificate of proficiency or equivalent, as specified by Civil Aviation Regulations subregulation 83A(2) and subregulation 83E(1)(a) and establish competency standards for those applicants for whom English is a second language, especially in respect of a candidate's ability to effectively communicate and comprehend traffic information.

R20000097

The Australian Transport Safety Bureau recommends that the Gliding Federation of Australia adopt measures to make all aircraft engaged in gliding activities more conspicuous.

R20000098

The Australian Transport Safety Bureau recommends that the Gliding Federation of Australia consider developing procedures that permit segregation of aero towing and gliding activity

Significant Factors

Aero towing operations from Waikerie were conducted through areas where gliding activity resulted in traffic conflicts that relied solely on visual acquisition for separation.

Inadequate use of the CTAF by pilots for traffic alerting.

The collision warning broadcast by the pilot of the Twin Astir was not effective.

Traffic lookout by the pilot of the Astir CS was not effective.

Analysis

Aero towing operations from runway 26 resulted in a flight path through an area where there was at times a concentration of aircraft. On this occasion, the presence of at least two gliders either thermalling or about to join the circuit pattern for a landing, created an area of potential conflict with the towing combination. Although each aircraft was radio-equipped, the required traffic broadcasts did not provide their pilots with an awareness of each other's presence. Effective use of radio communication could have alerted them to a possible conflict. Instead of relying solely on visual acquisition of the other aircraft for collision avoidance, each pilot would have had an awareness of the proximity of the other aircraft and used that information to mutually resolve the conflict and aid visual separation.

The towing combination should have been readily visible to the pilot of the Astir CS at a distance far enough to allow adequate time for him to take avoiding action. However, the Astir CS was not seen to deviate from its flight path until just before colliding with the towline, suggesting that its pilot had not seen the towing combination until too late to avoid a collision. On more than one occasion during his training the pilot of the Astir CS had been advised of the need to keep a continuous lookout by his instructor. Despite his training the pilot of the Astir CS did not see the towing combination.

The pilot of the Pawnee was responsible for traffic lookout and avoidance during the towing phase of the flight. It was possible that she had seen the other glider in the area but not the Astir CS. It had approached the towing combination from behind and would not have been in the Pawnee pilot's normal traffic scan. The unaddressed warning broadcast by the pilot of the Twin Astir may have conveyed a sense of danger to the pilot of the Pawnee. However, in the few seconds available to her it was unlikely that she would have been able to understand the significance of the warning and take appropriate avoiding action.

The pilot of the Twin Astir found himself in a situation for which there was no emergency procedure. His expectation that the pilot of the Astir CS would give way to the towing combination was not unrealistic. Confronted with an unexpected and rapidly developing dangerous situation, and without time to formulate any course of action, he reacted instinctively and broadcast an unaddressed warning. There was no obvious response from either pilot to this warning. The Twin Astir pilot, in releasing the towline when a collision between the Astir CS and the towline was unavoidable, saved his glider from also coming into collision with the other aircraft.

Summary

Sequence of events

A Grob Twin Astir two-seat glider, was being towed aloft by a Piper Pawnee aircraft for a passenger flight from Waikerie SA. The pilot was seated in the rear of the tandem cockpit. Several other gliders were airborne in the area, including a single-seat Grob Astir CS that had been launched from Waikerie just over an hour earlier for a local flight.

The pilot of the Twin Astir reported that the flight had been normal following the take-off from runway 26. The tow combination had turned left shortly after becoming airborne and continued climbing in a wide arc. Three km south of the airfield, as the towing combination was climbing through approximately 1,500 ft on a northwesterly heading, he saw a single-seat Astir CS glider near his right wingtip. He estimated that it was 8 to 10 metres away, on a converging course with the towing combination, and travelling at a slightly faster speed. He expected the pilot of the Astir CS to turn right, away from the towing combination. When this did not occur he broadcast a warning "Break right, break right" on the common traffic advisory frequency (CTAF) in an attempt to warn the other pilot. However, when he saw the Astir CS commence a gentle turn left, and a collision seemed imminent, he released the towline. He estimated the time from when he first saw the Astir CS until towline release was 4 to 5 seconds.

The passenger in the front seat of the Twin Astir recalled seeing another glider out to the left and above the towing combination shortly before the collision occurred. It was flying in the opposite direction but not close enough to cause him concern about a risk of collision. His attention was then drawn to the glider off the right wingtip when he heard the pilot broadcast the radio warning.

The Astir CS struck the towline approximately midway between the Pawnee and the Twin Astir, catapulting it into collision with the Pawnee. The collision dislodged the tail of the glider and damaged the left wing of the Pawnee. Witnesses at the airfield, who heard the sound of the collision, saw the Astir CS descend almost vertically. They described the Pawnee's descent as a spin or spiral, completing at least one and a half rotations to the left before it disappeared from view. The pilot of the Twin Astir took avoiding action and returned safely to Waikerie. The wreckage of the Pawnee and the Astir CS were found in a field about 3 km south of the airfield. Neither occupant of the two aircraft survived the collision and subsequent ground impact. The investigation did not find any pre-existing defect with either aircraft that could have contributed to the collision.

Witnesses reported the weather was clear apart from isolated patches of rain to the north of the aerodrome. Visibility outside the rain areas was unlimited. Sun glare was reported not to have been a problem at that time of the day because of the high sun angle. Turbulence was light in weak thermal convection.

Pilot experience and background

The pilot of the Astir CS was a Japanese national who had arrived in Waikerie a week earlier to further his gliding experience and qualifications. He had received his initial training to solo standard in Japan. In the week before the accident he had received further training at Waikerie during which he had made 14 instructional and familiarisation flights. His instructor reported that he had found it necessary to emphasise the need for the pilot to keep a continuous traffic lookout during those flights. The pilot of the Astir CS was issued with a Gliding Federation of Australia (GFA) validation and allowed to make solo flights. He had, as part of his training, undertaken a briefing and oral test required for the use of glider radio equipment on the CTAF. His examiner for the test was also a Japanese national employed as a gliding instructor by the gliding organisation. The instructor reported that the accident pilot's understanding of the English language would probably not have been sufficient to understand the significance of the unaddressed "Break right, break right" warning broadcast by the pilot of the Twin Astir. The pilot of the Astir CS was reported to have been well rested prior to the day's flying operations. Earlier that day he had completed a short flight in the same aircraft, returning due to the lack of thermal currents. A damaged pair of sunglasses was found in the wreckage of the Astir CS but it could not be determined if they were being worn at the time of the collision.

The pilot of the Pawnee held a Commercial pilot licence and valid Class 1 medical certificate. She had obtained her basic glider-towing permit on 27 November 1998 and had conducted aero towing at Waikerie since, accumulating some 117 hours in aero towing operations. As a prerequisite for aero towing, prospective tug pilots were required to have undertaken gliding training to solo standard. She had completed this training, which included spin recovery techniques. The instructor who carried out that spin training reported she was competent and had displayed sound recovery techniques. She had previously qualified and been certified for solo aerobatic manoeuvres, including spin recoveries, in powered aircraft. On the day of the accident she had completed 8 towing flights before the accident flight.

The pilot of the Twin Astir was appropriately qualified for passenger-carrying flights in gliders. Additionally, he held a Private Pilot's Licence and a valid Class 2 Medical Certificate. He was also qualified to conduct aero towing and had flown an aero tow launch earlier that day.

The investigation did not find any pre-existing medical condition that could have impaired the performance of the three pilots involved in the occurrence.

Radio requirements

The gliding organisation relied extensively on the patronage of overseas pilots. Many of those pilots were from non-English speaking backgrounds. Their English language skills were assessed as part of the requirement for the issue of a Radiotelephone Operators Authorisation. This was a requirement for the use of glider radios on the CTAF. Issue of an authorisation was dependent on a satisfactory oral examination on radio use and knowledge of procedures. This exam was conducted by a GFA Level 1 instructor who held either a radio licence or authorisation.

The CTAF area at Waikerie operated on a frequency of 126.7 MHz and extended from the surface to 3,000 ft above the aerodrome, and to a radius of 5 NM. Within the CTAF area pilots had to use the designated frequency, however outside the CTAF boundary glider pilots could use one of three allocated gliding frequencies. The GFA Manual of Standard Procedures (MOSP) required pilots of radio-equipped gliders to broadcast their intentions before entering the CTAF area or when about to take-off. It also stated that "Radio-equipped gliders must also respond to calls when appropriate when operating within a CTAF area". Other radio calls could be made at the pilot's discretion. The gliding organisation had a local rule that required an additional broadcast to be made on downwind.

Each of the aircraft involved in this occurrence was equipped with a serviceable VHF radio, however impact damage to the radio in the Astir CS made it impossible to determine the frequency selected at the time of the accident. The pilot of the Twin Astir reported that the pilot of the Pawnee had broadcast she was taxiing for aero towing operations from runway 26 before the launch. He did not recall hearing any response from other traffic.

Procedures

The local topography around Waikerie produced favourable soaring conditions to the south of the field. This characteristic was known to both tow pilots and glider pilots and was often exploited by them for gaining altitude. However, this area encroached on the designated left traffic pattern from runway 26 and at times resulted in aero towing aircraft and gliders sharing the same airspace. There was no segregation of gliding and aero towing activity. Aeronautical Information Publication procedures permitted gliders to use thermal lift on the "live" side of the circuit. This was provided that glider pilots monitored the CTAF and maintained adequate separation from other traffic in the circuit area. The local gliding operator discouraged the practice below 1,000 ft above ground level. The GFA Rules of the Air required pilots of gliders to maintain separation from other gliders and from towing combinations by at least 200 feet horizontally and vertically.

Vision

Although the see-and-avoid technique was the primary means of collision avoidance for aircraft operating under visual flight rules (VFR) there were limitations to its effectiveness, even for relatively slow aircraft such as gliders and light aircraft. The slim frontal profile of gliders made them more difficult to see than most powered aircraft. In 1991 the then Bureau of Air Safety Investigation published a research report "Limitations of the See-and-Avoid Principle" which documented the physiological and psychological limitations associated with seeing other aircraft. The report recommended that pilots should be aware of those limitations and not rely entirely upon vision to avoid collisions. In recommending the use of alerted see-and-avoid the report concluded that visual acquisition for collision avoidance should be the last defence in achieving separation.

Chapter 4 of the GFA publication Basic Gliding Knowledge (Fourth Edition) titled "The Development of Effective Lookout" described in detail the visual detection of other aircraft and the limitations of human vision in the airborne environment. It also stressed the need for pilots to ensure there was no other traffic in the airspace before manoeuvring and to avoid allowing one's attention to dwell in the cockpit. It did not mention the use of radio to assist in the detection of other traffic. The pilot of the Astir CS should have been familiar with scanning techniques and traffic lookout taught during his initial training. His subsequent training at Waikerie emphasised the need to continuously maintain a lookout. The Astir CS was fitted with a single-piece canopy that provided the pilot with an unobstructed forward and upward view. Visibility from the cockpit of the Astir CS was better than that from other aircraft whose canopies incorporated a windshield bow.

Survival

The pilot of the Astir CS had been wearing an emergency "slim-pack" type parachute. The gliding organisation required pilots of all single-seat gliders to wear a parachute and to be briefed on the emergency escape procedure. The investigation was unable to determine if the pilot was capable of performing the escape functions to parachute to safety following the collision with the Pawnee. The pilot of the Pawnee was unable to regain control of the damaged aircraft following the collision. Information obtained during the investigation suggested that damage to the Pawnee wing structure would probably have made the aircraft uncontrollable. The pilot of the Pawnee was not equipped with a parachute nor was she required to wear one.

Occurrence summary

Investigation number 199900844
Occurrence date 02/03/1999
Location 3 km S Waikerie, Aero.
State South Australia
Report release date 27/09/2000
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 Piper Aircraft Corp
Model PA-25
Registration VH-EVZ
Serial number 25-2342
Sector Piston
Operation type Private
Departure point Waikerie, SA
Destination Waikerie, SA
Damage Destroyed

Aircraft details

Manufacturer Grob - Burkhart Flugzeugbau
Model G102
Registration VH-GDL
Serial number 1296
Operation type Gliding
Departure point Waikerie, SA
Destination Waikerie, SA
Damage Destroyed

Pitts Aviation Enterprises S-2A, VH-PTD

Safety Action

Following this occurrence and a previous mid-air collision between a Piper Archer and a Piper Tomahawk at Hoxton Park on 6 June 1998, the Bureau issued the following interim recommendations on 8 June 1999:

IR19990077

The Bureau of Air Safety Investigation recommends that the Civil Aviation Safety Authority increase the number of mandatory radio broadcasts at non-controlled aerodromes to include a set of critical location broadcasts for those locations where the risk of collision is increased.

IR19990078

The Bureau of Air Safety Investigation recommends that the Civil Aviation Safety Authority extend the proposed radio requirements as outlined in the Notice of Proposed Rule Making (NPRM9702RP) to include both licensed aerodromes and any unlicensed aerodrome into which fare-paying passenger services operate.

IR19990079

The Bureau of Air Safety Investigation recommends that the Civil Aviation Safety Authority amend current procedures/airspace for aircraft operating into and departing from Hoxton Park in order to reduce the potential for further aircraft collisions".

IR19990077

On 13 September 1999, the Civil Aviation Safety Authority responded to IR 19990077 as follows:

"CASA agrees that additional mandatory broadcasts at non-controlled aerodromes should facilitate alerted see-and-avoid between aircraft operating in the vicinity of an aerodrome. CASA will therefore take action to mandate the following additional broadcasts at MBZ and CTAF aerodromes:

upon entering the runway for takeoff; and

upon joining the circuit."

ATSB classified the CASA response as CLOSED-ACCEPTED.

On 19 November 1999, the Bureau responded to the Civil Aviation Safety Authority as follows:

"CASA's commitment to increase the number of mandatory broadcasts at CTAF and MBZ areodromes is supported. The Bureau will monitor the implementation of this recommendation. As such, could you please advise the Bureau of the proposed date that this safety initiative is likely to be implemented ?"

CASA amended the Aeronautical Information Publication (AIP) Australia. The amendments effective on 2 December 1999, in section AIP ENR 1.1, included new paragraphs 60.1 and 60.3.

Para 60.1 read as follows:

When approaching an aerodrome and before crossing the MBZ or CTAF area boundary, all aircraft must broadcast the following details on the MBZ frequency and, similarly, all radio-equipped aircraft must broadcast on the CTAF:

  1. callsign and aircraft type;
  2. position (reported as distance with either the radial, bearing, or quadrant from the aerodrome);
  3. level; and
  4. intentions

Para 60.3 read as follows

All aircraft operating into an aerodrome within an MBZ, and all radio-equipped aircraft operating into an aerodrome within a CTAF area, must broadcast on the MBZ frequency or CTAF when joining the circuit.

IR19990078

On 14 July 1999, Airservices Australia responded as follows:

"Airservices does not wish to comment on this recommendation except to agree with the remarks referring to the potential for frequency congestion at non-controlled aerodromes should this recommendation become mandatory."

On 13 September 1999, the Civil Aviation Safety Authority responded as follows:

"Since fare-paying passengers may travel at any time to any destination with a suitable landing area, CASA considers that compliance with such a requirement by non-radio equipped aircraft would be at best difficult, and would not impose it without a clearly identified safety issue and justification.

"At the same time, the intended CASA action detailed in the response to IR19990077 will go a long way towards satisfying the intent of this interim recommendation."

ATSB classified the CASA response as CLOSED-PARTIALLY ACCEPTED.

On 19 November 1999, the Bureau responded to the Civil Aviation Safety Authority as follows:

"The Bureau agrees that the implementation of IR19990077 will go a long way toward meeting the intent of IR19990078. In addition, your reference to the difficulty of complying with such a requirement by non-radio equipped aircraft in those cases where passenger-carrying services do not operate in accordance with fixed schedules, is also supported.

"However, a number of operators do conduct scheduled flights into unlicensed aerodromes. In such cases, additional protection for the passengers who commute on those services may be provided by other means. Additional information would assist the pilots of both radio and non-radio equipped aircraft to make decisions about their intended activities that would reduce the risk of collision with passenger-carrying flights."

IR19990079

On 14 July 1999, Airservices Australia responded as follows:

"Airservices agrees that the preferred situation would see aircraft operating in the vicinity of Hoxton Park equipped with two radios and with the suggestion that more appropriate position reports in the circuit area would assist in situational awareness.

"We are also aware of anecdotal evidence that pilots interpret the requirements for radio calls in the MBZ differently which itself can cause confusion and loss of situational awareness."

On 13 September 1999, the Civil Aviation Safety Authority responded as follows:

"Special procedures to facilitate the safety of operations are already in place at Hoxton Park. Given the constraints imposed by the geographical proximity of other aerodromes to Hoxton Park, and also in the light of the volume and nature of aircraft operations at these locations, CASA would welcome more detailed information from BASI as to how it considers current procedures and airspace arrangements could be amended to reduce the potential for further aircraft collisions."

ATSB classified the CASA response as OPEN.

On 19 November 1999, the Bureau responded to the Civil Aviation Safety Authority as follows:

"The implementation of IR19990077 would, again, go some way in addressing the concerns raised on IR19990079. The Bureau understands the present airspace constraints imposed on Hoxton Park; however, Hoxton Park's unique problems should be taken into consideration in any future proposals for airspace changes in that area. In relation to the procedural aspects, the Bureau believes that there may be solutions that would reduce the risk of aircraft collisions in the Hoxton Park area. The following suggestions are offered, without prejudice, for your consideration:

"1. Pilots departing the Bankstown CTR boundary whose aircraft are not equipped with dual radios, should switch immediately onto the Hoxton Park frequency rather than delaying that action until 3 NM from the CTR boundary, as currently advised in the ERSA; "2. A defined airspace corridor with designated altitudes for those flights operating directly between Bankstown and Hoxton Park;

"3. Approach points for arrivals of flights from locations other than Bankstown, be designated for Hoxton Park; and

"4. Circuit entry procedures as currently outlined in the ERSA, be more comprehensively defined.

"Therefore, the Bureau requests that IR19990079 be reconsidered and that CASA provide advice on the outcome of any further consideration at your earliest convenience."

Conspicuity trials

Approximately two months after the accident, the then Bureau of Air Safety Investigation conducted a series of trials on the conspicuity to a pilot on final approach of a light-coloured light aircraft on the "piano keys" of runway 34 at Hoxton Park. The trial was conducted in very similar weather conditions, and during the same time of day, as the accident.

A brief description of the trials and their results were published in Issue 23 of "Asia-Pacific Air Safety", September 1999. In short, the Bureau found that under some conditions of light and contrast, combined with an expectancy that a runway would be clear, a pilot of an aircraft on final approach may fail to perceive an aircraft on the piano keys at the threshold of the runway.

Significant Factors

  1. The CTAF radio broadcast procedures did not provide the pilots with adequate opportunity for "alerted-see-and-avoid".
  2. Probably neither pilot saw the other aircraft.
  3. The technique of briefly lowering the nose on final approach did not allow the Pitts pilot to be certain that the runway was clear before he committed the aircraft to a landing.

Analysis

Why neither pilot saw, nor was aware of, the other aircraft could be primarily due to communications and visual acquisition limitations.

Without radio information, pilots only become aware of traffic by "unalerted see-and-avoid", i.e. by visually scanning all airspace surrounding their aircraft with no prior expectation of seeing another aircraft.

If the pilots of two approaching aircraft have communicated by radio, each pilot has some idea of where to look for the other's aircraft and is expecting its arrival. This "alerted see-and-avoid" process greatly increases the probability of each pilot sighting the other aircraft in time to arrange separation.

A pilot operating at an uncontrolled aerodrome in an "alerted see-and-avoid" environment such as a Mandatory Broadcast Zone (MBZ) or CTAF, would expect other pilots to broadcast their position and intentions. Consequently, pilots' efforts to scan the sky for traffic might be less rigorous than they would be in the "unalerted see-and-avoid" environment. If an aircraft is operating on an unalerted basis in an alerted environment, other pilots can incorrectly conclude that the absence of radio calls means that there is no conflicting traffic. It is therefore less likely that traffic approaching on an unalerted basis will be seen in an alerted see-and-avoid environment than in an unalerted see-and-avoid environment.

Communications

The investigation concluded that the requirement for only two CTAF broadcasts was probably inadequate, even though the pilots were free to make additional radio calls when appropriate. The Pitts pilot reported that he made a broadcast when he was 5 NM from Hoxton Park and again upon entering the crosswind leg for a left circuit for runway 34. The reason the other three pilots did not hear the radio calls from the Pitts pilot could not be determined. He did not broadcast his position on the base leg or on final approach which, in any case, he was not required to do. As a result, the Sundowner pilot had little opportunity to take advantage of alerted-see-and-avoid procedures at a time when he would have been preparing to take off. If the Sundowner pilot had not transmitted his intention to enter the runway and take off, the Pitts pilot similarly had little opportunity to use alerted see-and-avoid.

The Pitts pilot did not hear the Sundowner pilot's taxi call as the Pitts was probably more than 5 NM from Hoxton Park when the call was made. If so, the Pitts would not have been on the Hoxton Park CTAF at that time. Consequently, the Pitts pilot would have had to sight the Sundowner to become aware of its presence.

Vision

The Sundowner pilot's spectacles may have limited his ability to see the Pitts by reducing the contrast between the yellow painted Pitts and the environment. In addition, the relatively small profile of the Pitts could also have made visual acquisition more difficult.

Trees obscuring traffic on left base for runway 34 prevented the Sundowner pilot from effectively scanning that part of the circuit while in the runup bay. However, while on the taxiway between the runup bay and the runway threshold, he should have had an unobstructed view of the final approach path.

The same trees may have obscured the Pitts pilot's view of the aircraft in the runup bay. However, when the aircraft was on the taxiway between the runup bay and the runway, there were no visual obstructions affecting the view from final approach.

After the Pitts had lined up on final approach, the nose-high pitch attitude of the aircraft at approach speed would have denied the pilot, seated in the rear cockpit, a continuous view of the runway threshold. In addition, briefly lowering the nose to obtain an unobstructed view of the threshold would have given the Pitts pilot limited opportunity to see the Sundowner entering the runway or beginning its take-off. He did not see the Sundowner before committing his aircraft to a landing.

Factual Information

Sequence of events

The pilot of a Beechcraft Sundowner was preparing to depart Hoxton Park Aerodrome for his first solo navigation training exercise. The pilot of a Pitts Special S-2A had flown his aircraft from Bankstown to the training area and then to Hoxton Park to conduct practice circuits before returning to Bankstown.

The Pitts pilot reported broadcasting details of his entry to the Hoxton Park common traffic advisory frequency (CTAF) area when he was 5 NM from Hoxton Park, and when he entered the circuit area on the crosswind leg for runway 34. He also reported that, in order to maintain separation from a preceding aircraft in the circuit, he had reduced speed and followed that aircraft.

Meanwhile, the Sundowner pilot had completed his pre-departure checks in the runup bay. He then taxied his aircraft onto runway 34 and commenced the take-off run. At that time, the Pitts was on final approach. The Pitts pilot reported that during the final approach he had repeatedly lowered the nose of the aircraft for short periods in order to provide a view of the flight path to the runway threshold before committing himself to a landing. The last time he had performed the manoeuvre was about 400 m from the threshold.

As the Sundowner was accelerating along the runway, the Pitts landed on top of it about 80 m from the threshold. Both aircraft became entangled and travelled approximately 100 m along the runway before slewing to the right then turning sharply left and coming to rest on the runway. The propeller of the Pitts deeply penetrated the Sundowner cabin and killed the pilot.

Another pilot operating in the circuit heard the Sundowner pilot make a pre-taxiing radio broadcast on the CTAF. The investigation could not establish if the Sundowner pilot made any further broadcasts before the collision. The Pitts pilot later stated that he did not remember hearing any radio transmissions from other aircraft. Further, he reported that he had no idea that he had collided with another aircraft until he vacated the cockpit.

Shortly before the accident, three other aircraft were operating in the circuit area. Their crews later reported hearing each other's radio traffic on the CTAF, but not hearing any radio transmissions from the Pitts.

Wreckage examination

The Sundowner came to rest on a southerly heading, sustaining deep propeller slashes to the left forward side of the cabin. The fin was severed. The Pitts's right main wheel had penetrated the Sundowner's left rear cabin. The very high frequency (VHF) transceiver was tuned to 127.0 MHz, the CTAF, and later testing showed that the radio was serviceable.

The wreckage examination indicated that the Sundowner was serviceable before impact.

The Pitts came to rest on a heading slightly east of south. Both right wings were detached and displaced 90 degrees rearward. The VHF transceiver was tuned to 127.0 MHz and later testing showed that the radio was serviceable. Test running of the engine showed that it should have performed normally before the impact.

The wreckage examination indicated that the Pitts was serviceable before impact.

Pilot information

The Sundowner pilot was 70 years old and held a student pilot licence (aeroplanes) and a valid Class 2 medical certificate with a requirement to wear vision correction. At the time of the accident he was wearing multi-focal prescription spectacles, that corrected his vision to 6/6. He had a total of 106 hours flying experience, including 22 hours on type. He had completed a short dual check flight earlier in the day, and had been cleared to carry out the solo navigation exercise.

Autopsy and toxicological tests did not reveal any pre-existing medical conditions, alcohol or other drugs that might have prevented the pilot from safely operating the aircraft.

The pilot's yellow-brown tinted lens spectacle lenses were designed to change colour in accordance with variations in temperature and ultra-violet light exposure. (As temperature reduced and/or the level of ultra-violet light increased, the lens darkened.) This tint reduced light to the eye and changed the colour of the environment. When viewed through the lens, the contrast between the yellow painted Pitts and the blue sky would have been reduced.

The Pitts pilot was 72 years old and held a private pilot licence (aeroplanes) and a valid Class 2 medical certificate with a requirement to wear vision correction. At the time of the accident he was wearing vision-correcting prescription sunglasses. He had been a pilot for about 38 years, and had about 2,700 hours flying experience, including 491 hours on type.

Weather

The weather at the time of the accident was fine, with visibility of 40 km and scattered cumulus clouds with a base of 4,500 ft above mean sea level. Wind conditions were light and favoured landings on runway 34.

Aerodrome information

Hoxton Park was designated as a CTAF aerodrome. The radio frequency for aircraft-to-aircraft communication was 127.0 MHz. The only mandatory radio broadcasts required in accordance with CTAF procedures were to be made when beginning to taxi and when inbound to the aerodrome. Pilots operating within CTAFs would normally be expected, upon hearing one of those broadcasts, to respond with information on their position and intentions and to arrange mutual separation.

According to the Aeronautical Information Publication, "Enroute Supplement Australia" (ERSA), runway 34 was the preferred runway for use in still wind conditions. Aircraft using runway 34 normally conducted left circuits, resulting in traffic on the downwind leg passing behind aircraft in the runup bay for runway 34. A copes of trees about 10 m in height was located immediately to the south-west of the runup bay. The trees obscured the view that pilots in the runup bay would have had of aircraft on the left base leg or of aircraft turning onto final approach for a landing on runway 34. However, from the holding point on the taxiway between the runup bay and the runway 34 threshold, and from most of the taxiway, the view of traffic on final approach was unobstructed.

The Hoxton Park CTAF was changed from 118.1 MHz to 127.0 MHz with effect from 3 December 1998. Notice to Airmen (NOTAM) C9/98 (10 November 1998) publicised the change, but it was not published in ERSA until the 25 March 1999 issue.

Occurrence summary

Investigation number 199900970
Occurrence date 10/03/1999
Location Hoxton Park, Aero.
State New South Wales
Report release date 21/06/2000
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Pitts Aviation Enterprises
Model S-2
Registration VH-PTD
Serial number 2022
Sector Piston
Operation type Private
Departure point Bankstown, NSW
Destination Bankstown, NSW
Damage Substantial

Aircraft details

Manufacturer Beech Aircraft Corp
Model 23
Registration VH-AYZ
Serial number M-1580
Sector Piston
Operation type Flying Training
Departure point Hoxton Park, NSW
Destination Goulburn, NSW
Damage Substantial

Airbus A320-211, VH-HYI

Summary

The Airbus A320 (A320) departed Sydney for Coolangatta carrying sufficient fuel for the planned flight. In addition to the flight fuel, there was provision for a 10 per cent variable reserve, 60 minutes fixed reserve, 30 minutes holding fuel, plus 200 kg for contingencies. The Coolangatta terminal area forecast (TAF) indicated intermittent (INTER) periods of visibility reducing to 3,000 m in heavy showers. The term INTER is used to indicate a change in prevailing conditions expected to occur frequently for periods of less than 30 minutes duration, the conditions fluctuating almost constantly, between the times specified in the forecast. The Brisbane TAF was similar, with no indication of thunderstorms at either location.

Near Williamtown, en route to Coolangatta, the crew received an "Airport Warning" for Brisbane. An Airport Warning is issued by the Bureau of Meteorology (BoM) to advise airport users of approaching severe weather conditions; it is not a forecast intended for flight-planning purposes by flight crews. The warning indicated that a line of thunderstorms was approaching from the west towards Brisbane, and the crew noted that the Brisbane weather was expected to deteriorate coincident with their arrival at Coolangatta. However, the TAF was not updated until an hour after the BoM became aware of approaching thunderstorms, and the amended TAF was never passed to the crew.

The crew calculated that should a missed approach become necessary at Coolangatta a diversion to Tamworth could be carried out. Tamworth is listed as an "adequate airport for twin engine operations" in the operator's A320 operating manual This listing is relevant to extended range twin-engine operations. Notes appended to the listing indicate that the list is a guide, and that the suitability of the airport should be checked prior to its use. The fuel required to divert was based on a fixed reserve of 30 minutes.

The crew contacted Coolangatta Approach then Coolangatta Tower prior to commencing a descent, and were advised that the weather conditions would be suitable for an approach and landing, but that thunderstorms were approaching from the west. A decision was then made by the pilot in command to continue to Coolangatta, but divert to Tamworth if necessary. Constant updates on the weather at Coolangatta were passed to the crew during the descent, and aircraft radar returns indicated a clear approach path with storms cells still to the west of Coolangatta. Advice was received by the crew that Brisbane weather was deteriorating rapidly at this time, with rain and lightning close to the airport.

A runway 32 VOR/DME approach was commenced to Coolangatta and the crew became visual at approximately 1,500 ft. The approach proceeded normally, with the full length of the runway being visible in light to moderate rain. The co-pilot was the handling pilot, and the pilot in command considered the weather conditions exceeded company requirements for a co-pilot approach and landing. However, at about 800 ft, the co-pilot unexpectedly commenced a missed approach, commenting that he did not like the conditions. Due to the rapidly deteriorating weather the pilot in command decided there was no option but to carry out the diversion to Tamworth.

The crew was subsequently advised by company central operations to divert to Williamtown rather than Tamworth as the company did not have a standing pavement concession for the use of Tamworth, and the airport was not included in the company's air operator certificate. As the aircraft would not arrive at Williamtown with the required fuel reserves intact, the crew declared a fuel emergency to air traffic control. The aircraft arrived at Williamtown with fuel equivalent to a fixed reserve of 27 minutes.

Occurrence summary

Investigation number 199900851
Occurrence date 03/03/1999
Location Coolangatta, Aero.
State Queensland
Report release date 10/09/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel - Other
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Airbus
Model A320
Registration VH-HYI
Serial number 140
Sector Jet
Operation type Air Transport High Capacity
Departure point Sydney, NSW
Destination Coolangatta, QLD
Damage Nil

Robinson R22 Beta, VH-NLT

Safety Action

As a result of this occurrence, the Bureau of Air Safety Investigation is investigating perceived safety deficiencies involving helicopter performance, pilot licensing and experience requirements.

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

Significant Factors

  1. The pilot was inexperienced.
  2. The density altitude and relative humidity were high.
  3. The wind conditions were gusty.
  4. There was no documented data or guidance available to the pilot to assist him in assessing the expected performance of the helicopter during the take-off.
  5. The pilot did not adequately plan the take-off to account for the weather conditions and helicopter landing site characteristics.
  6. The pilot used an inappropriate take-off technique.
  7. The helicopter was probably at or close to maximum all up weight and had inadequate performance to complete the take-off in nil wind.
  8. The weather conditions had changed since the first take-off and did not assist the helicopter during the second take-off.

Analysis

The helicopter weighed close to its maximum permissible all up weight. The pilot reported that the power required to hover the helicopter in ground effect was about 23 inches manifold air pressure, which was close to the placarded limit. The flight manual data also indicated that the helicopter had insufficient power to hover out of ground effect in nil wind. The reported high power being used to achieve an in-ground effect hover associated with the high-density altitude conditions and the available flight manual performance data, indicated that the helicopter's engine was unlikely to have been capable of providing appreciably more power than that already being used.

The reported site information indicated that the helicopter would have needed to achieve a climb profile of at least three degrees. However, the available performance data indicated that there was unlikely to have been sufficient power available to depart from the in-ground effect hover and achieve the required climb profile in nil wind. The helicopter's performance would have been adversely affected by the high relative humidity, which had the effect of further increasing the already high-density altitude. Had the pilot consulted the flight manual or conducted a power check prior to landing on the pad, he may have realised that there was unlikely to have been sufficient power available to attempt the departure, or at least he could have planned the departure with a rejected take-off in mind.

Neither the helicopter's flight manual, nor operator's operations manual provided climb performance data or guidance on expected power requirements for the helicopter to depart the hover and transition into forward climbing flight. Although the Civil Aviation Orders specify minimum performance requirements for aeroplanes, there are no similar requirements for helicopters. With no regulatory requirement for climb performance information to be provided by either the helicopter's manufacturer or the operator, the pilot had no documented guidance on the helicopter's expected performance in forward climbing flight. While it would have been prudent for the pilot to conduct a power check before commencing operations into or out of the helicopter landing site, there was no guidance provided by either the operator or helicopter manufacturer on required power margins. Therefore, a power check may have been of relevance to a pilot with experience in R22 limited power operations. However, the accident pilot's experience was not extensive, with a total flying time of about 173 hours. While he had accumulated 36 flying hours during the month prior to the accident he had only flown about 50 hours during the previous 16 months. It appears incongruous that, in accordance with the regulations and orders, the pilot had sufficient experience to transport passengers but insufficient flying experience to undertake mustering operations. While there was no documentary evidence detailing the pilot's initial training, there appeared to be some gaps in his knowledge with regard to operating the R22 helicopter close to its limits. The limited amount of flying he conducted in the 15 months between completing his course and joining the helicopter's operator may have also been a factor. He appeared to have been ill prepared to operate the helicopter in the high-density altitude conditions of Northern Australia.

Although the task of carrying passengers from the station was not authorised by the helicopter's operator, the pilot reported that he was advised that the on-site experienced pilot was "in charge". The helicopter's operator was unaware of the requirement to conduct passenger flights, and in using the term "in charge" in relation to the on-site pilot, probably contributed to the pilot's belief that the on-site pilot was a nominated person who could authorise all flights. If the operator had been aware of the passenger flights, then more appropriate supervision of the pilot may have been provided. There appeared to have been a misunderstanding between the operator and the on-site pilot as regards to the use of the helicopter.

The pilot reported that he had not experienced any problems during the first take-off from the site. He reported the wind as being gusty, averaging 15 kts and that there were thunderstorms in the area. With evidence indicating that there was probably little power available to depart the hover and achieve the required departure angle in nil wind, it was likely that the helicopter's performance was assisted during the previous take-off by the wind conditions existing at the time. This may have lulled the pilot into a belief that the helicopter had sufficient power to attempt further take-offs.

During the accident take-off, the helicopter's main rotor RPM decreased. No evidence of a mechanical fault was subsequently found. The pilot reported that the wind was gusty and the humidity was high and increasing as storms built-up in the area. It was possible that the relative humidity had increased sufficiently to decrease the main and tail rotor performance or decrease the amount of power available from the engine. Alternatively, or in combination with the high relative humidity, the wind may have changed direction or lost strength during the accident take-off. In either case, the pilot would have had to increase the collective pitch to maintain the departure profile. This may have resulted in the power required to drive the helicopter's rotor system exceeding the power available from the engine. As a result, the main rotor RPM drooped which reduced the lift being produced by the main rotor and the helicopter descended to the ground. Because the pilot had conducted the departure without considering the possible requirement to reject the take-off, the area into which the helicopter descended was unsuitable for landing.

CONCLUSIONS

Findings

While the pilot was conducting the take-off from Fossil Downs Station, the environmental conditions may have changed such that the power required to maintain the helicopter's departure profile exceeded the power available from the engine. As a result, the main rotor RPM decayed and the helicopter descended onto the ground. The pilot had not adequately assessed the power needed to conduct the takeoff and had used an inappropriate takeoff technique for the environmental conditions and helicopter weight. There was a misunderstanding between the operator and the customer as to the use of the helicopter. The pilot inadvertently believed he was authorised in accordance with the company operations manual to conduct the passenger flights. The helicopter's operator was unaware that the passenger flights were being conducted.

Summary

The Robinson R22 helicopter was sent to Fossil Downs Station by the operator to conduct a small mustering assignment. As the operator's pilot was relatively inexperienced and not qualified to conduct mustering operations, the helicopter was fitted with dual controls so that an experienced and qualified pilot who was on-site could conduct the flying while the operator's pilot occupied the other seat. However, after the aircraft arrived at the station, the on-site pilot requested that the operator's pilot transport two passengers from the station to Fitzroy Crossing. Although the operator's pilot had insufficient hours to conduct mustering, he held a commercial pilot's licence and was qualified to carry passengers.

The pilot transported the first passenger from the helicopter landing site without incident. However, during the second departure, at about 15 ft and just as the helicopter was achieving translational lift, it sank back towards the ground. When the pilot increased the collective pitch in an attempt to regain the required departure profile, the low rotor RPM warning horn sounded and the rate of descent increased. The pilot reported that he checked that the throttle was fully open but the main rotor RPM continued to decay. The helicopter landed heavily and the main rotor blades clipped a tree. The pilot reported that as soon as it landed, he shut the engine down. The helicopter was extensively damaged but neither occupant was injured. The pilot reported that he flew the second flight's take-off into wind along a similar path to that flown during the previous passenger flight.

The maintenance organisation that repaired the helicopter reported that no mechanical fault was found that would have contributed to the accident. The accident was not subject to an on-site investigation by the Bureau of Air Safety Investigation.

Weather conditions

The pilot reported that the ambient temperature was about 37 degrees Celsius. He also reported that the humidity was high and increasing as storms were developing in the area. The wind was averaging about 15 kts from the south-east and gusting. The density altitude at the site, without factoring the relative humidity, was calculated to be about 3,000 ft.

The helicopter landing site

The pilot reported that he was using a southerly departure from the site to align with the general wind direction. The pilot reported that in the southerly direction, the helicopter landing site had an available length of about 50 to 60 m from the departure point with about 3 m high bushes at the departure end. There was also a small fence running east to west about 40 m from the departure point.

Helicopter performance

The helicopter weighed close to its maximum all up weight of 622 kgs. The helicopter's flight manual indicated that the calculated maximum weight to hover out of ground effect in nil wind, was about 605 kgs. The pilot did not consult the helicopter's flight manual for likely power requirements and power availability; nor did he conduct a power check prior to arriving at the helicopter landing site in order to ascertain the actual power available. While the Robinson R22 Flight Manual provided hover performance data, it did not contain performance data related to the expected climb performance of the helicopter during take-off, or in forward flight. The operator's operations manual did not provide guidance regarding power margins. There was no requirement under the existing regulations for information or guidance related to required power margins for departure or climb performance to be provided by either the helicopter's manufacturer or operator.

The pilot reported that the power setting required to hover the helicopter in ground effect was about 23 inches manifold air pressure, which was approximately the placarded limit manifold air pressure of 23.5 inches. The pilot could not recall the power indication during the accident take-off.

Ambient wind conditions can have significant and differing effects on a tail rotor equipped helicopter's performance. Engine power is delivered to a transmission system, which drives the main and tail rotors The power required to drive the transmission system is determined primarily by the amount of drag being produced by the rotors and the power available is determined by the power output of the engine(s). The difference between the power available and power required is known as the power margin. If the power required to drive transmission exceeds the amount of power available from the engine, then the main and tail rotor speed will decay, or droop. When the speed of the main rotor droops significantly, the main rotor loses lift and the helicopter descends. Wind blowing over a main rotor provides translational lift that can significantly reduce the power required to drive the helicopter's transmission system. Wind may also assist a helicopter to maintain heading, which also reduces the load demand on the transmission and therefore reduces the power required to drive the transmission. Conversely, a wind from an adverse direction may increase the load demand on the transmission and, in turn, the power required from the engine. Therefore, the wind may cause a net effect which, depending on its strength and direction, will reduce or increase the power required for a tail rotor equipped helicopter to maintain flight.

The density of air is affected by a number of factors including its moisture content. Relative humidity is the ratio of the amount of moisture in the air to the amount it is capable of absorbing at a given temperature. The greatest decrease in air density (increase in density altitude) due to moisture content will be at a high temperature. In general, as the density altitude increases, helicopter rotor and piston engine performance decrease. The performance data provided in the R22 helicopter's flight manual is only valid for nil-wind conditions and does not account for the adverse effects of high relative humidity.

Although the Civil Aviation Orders (CAOs) specify minimum performance requirements for single and multi-engine aeroplanes, there are no minimum performance criteria specified for helicopters.

Pilot Experience

The pilot had about 173 hours flying experience, of which about 83 hours were in command. All his flying experience had been gained on the Robinson R22 helicopter. Prior to joining the operator, he had flown about 14 hours during the 15 months since gaining his commercial (helicopter) pilot's licence in September 1997. He had been employed by the operator for less than one month and had accumulated just over 36 flying hours in that time. His initial training was conducted at several helicopter training schools in Queensland, and he reported that during the training, he had not experienced the helicopter being close to limits of power or practiced rejected departures and had not previously experienced main rotor RPM droop. He also reported that at the time of the accident, he was unaware of how to recover from a low rotor RPM condition. There were no available records related to his initial flying training, however, the pilot reported that he considered the training to be adequate. The operator conducted a proficiency check on the pilot about three weeks prior to the accident. The pilot's performance during the check was rated as satisfactory. About a month after the accident, the pilot attended a Robinson Safety Course where he flew with an experienced R22 helicopter instructor. The instructor reported that the pilot demonstrated an inappropriate take-off technique and that he required remedial instruction.

The Civil Aviation Orders impose a minimum requirement of 100 hrs as pilot-in-command before a pilot may conduct mustering operations. The Civil Aviation Regulations specify that a pilot may obtain a commercial (helicopter) pilot's licence, under certain circumstances, after a minimum total of 105 flying hours of which at least 35 hours are as pilot-in-command.

The company's operations manual required pilots to obtain authorisation from the Chief Pilot or a person nominated by the Chief Pilot before conducting any flights. The pilot reported that the Chief Pilot told him that the on-site pilot was "in charge". When he was requested to conduct the passenger flights, the pilot believed that the on-site pilot had the appropriate authority.

Occurrence summary

Investigation number 199900833
Occurrence date 03/02/1999
Location 9 km ENE Fossil Downs Station (ALA)
State Western Australia
Report release date 24/09/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Forced/precautionary landing
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer Robinson Helicopter Co
Model R22
Registration VH-NLT
Serial number 2542
Sector Helicopter
Operation type Charter
Departure point Fossil Downs Station, WA
Destination Fitzroy Crossing, WA
Damage Substantial

Hughes Helicopters 369HS, VH-SHD

Summary

The Hughes 369HS helicopter was on a ferry flight from Western Australia to New South Wales. After landing at Ceduna to refuel, the pilot was advised by the local fuel agent that the Jet A1 fuel bowser was non-operable. The pilot reported that the operator's maintenance organisation advised him that the helicopter could be flown using avgas as an alternative fuel. The pilot reported that after the refuel, he completed a pre-flight inspection, started the helicopter and ran it for a short time before taking off. After take-off, he conducted a circuit to ensure that the engine was performing correctly. All the indications appeared normal so the pilot decided to depart the airfield. During the climb, at about 500 ft, the pilot turned off the fuel start pump switch. He reported that almost immediately after he turned the pump off, the engine failed. The pilot reported that he placed the helicopter into an auto-rotative descent, turned on the start pump and transmitted a Mayday that was acknowledged by flight service. The pilot also reported that although he noticed the engine-out warning system and the re-ignition systems operating during the descent, the engine did not relight. The helicopter's emergency locator beacon automatically operated following the firm auto-rotative landing. After landing, the pilot turned off the helicopter's fuel and electrical systems and vacated the cockpit. The helicopter was extensively damaged during the landing, but the pilot was not injured. The Bureau of Air Safety Investigation did not conduct an on-site investigation.

The version of the flight manual that was current when the accident occurred included a caution that stated, "When using alternate fuel mixtures or emergency fuels, the start pump should remain on until the engine is shutdown". Avgas has a higher vapour pressure than kerosene type fuel and is therefore susceptible to vapour lock in the vacuum type fuel system used in this helicopter. The pilot reported that the maintenance organisation did not advise him of the fuel pump requirement and that the caution did not appear in the flight manual available in the aircraft at the time. The helicopter's manufacturer reported that the amendment that included the caution relating to the use of the pump was issued in 1998. The operator was unable to provide a reason for the failure to incorporate the amendment relating to the use of alternative fuels in the helicopter's flight manual.

The investigation also found that the fuel filter element's outer fine mesh screen was substantially blocked with corrosion by-products from the stainless steel mesh filter element. Some of the screen pleats at the bottom of the filter element had cracked as a result of a corrosion-cracking mechanism. Analysis indicated that the corrosion of the fuel filter element was possibly caused by sulphur-bearing compounds found in Jet A1 fuel. It would be normally expected that such extensive blockage of the fuel filter would trigger the fuel filter caution light. However, the crack found in the filter element pleat may have been large enough to permit fuel to pass through and not create sufficient pressure differential within the fuel filter housing to trigger the caution light.

Following the refuel with avgas, the engine apparently lost power when the pilot turned off the fuel start pump. It is possible that when the fuel start pump was turned off, a vapour lock formed in the helicopter's fuel system, interrupting the fuel flow to the engine and causing the engine to flame out. The effect of the corroded and blocked fuel filter in contributing to the engine power loss was not determined.

Occurrence summary

Investigation number 199900820
Occurrence date 27/02/1999
Location 9 km E Ceduna, Aero
State South Australia
Report release date 19/10/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Forced/precautionary landing
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer Hughes Helicopters
Model 369
Registration VH-SHD
Serial number 240564S
Sector Helicopter
Operation type Aerial Work
Departure point Ceduna, SA
Destination Port Augusta, SA
Damage Substantial