Beech Aircraft Corp F33A , VH-SIO

Summary

The student pilot was flying the Beechcraft Bonanza on a solo navigation exercise from Jandakot to Narrogin and Merredin before returning to Jandakot via Perth. The aircraft departed at about 1300 WST and was due to land at Jandakot about 2 hours later. The pilot reported that during the approach to Jandakot, he levelled the aircraft at 1,000 ft and set power to maintain the altitude. He then completed the pre-landing checks and lowered the flaps to slow the aircraft. Soon after lowering the flaps, he noted that the engine rpm was rapidly dropping. He reported that he opened the throttle and conducted the appropriate checks but the engine did not respond. The pilot transmitted a Mayday and decided to attempt a forced landing in an open patch of ground in the Canning Vale area. He then turned off the aircraft's fuel and electrical systems.

Avoiding parked trucks and buildings, the pilot landed the aircraft in a parking area of the Caning Vale Markets. The aircraft slid 15 m before hitting an unoccupied temporary building and coming to rest. The building was destroyed, the aircraft was substantially damaged and the pilot received minor injuries.

The post-accident inspection of the aircraft revealed that there was a substantial amount of fuel in both wing tanks but no fuel could be found in lines beyond the fuel selector valve. No fault was found with the aircraft's fuel system or engine.

Evidence was consistent with the engine sustaining fuel starvation and losing power but the investigation could not determine the reason for the fuel starvation.

Occurrence summary

Investigation number 199803888
Occurrence date 19/09/1998
Location Canning Vale
State Western Australia
Report release date 04/08/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 Minor

Aircraft details

Manufacturer Beech Aircraft Corp
Model 33
Registration VH-SIO
Serial number CE-1329
Sector Piston
Operation type Flying Training
Departure point Jandakot, WA
Destination Jandakot, WA
Damage Substantial

Bell 47G-5, 25031

Summary

Witnesses reported that pilot of the Bell 47 was conducting cattle mustering operations. He departed on a short flight to check for stray cattle on the side of a hill, opposite to where the main mob was located. A short time after the helicopter disappeared from view, the sound of an impact was heard. A search revealed that the helicopter had struck a single wire earth return (SWER) power line which was suspended between a post on top of the hill and another post well left of the probable flight path. One of the landing gear skids had caught the wire, upsetting the helicopter, and causing it to enter uncontrolled flight. It was not determined whether the pilot was aware that there was a wire in the area.

This accident was not the subject of an on-site investigation.

Occurrence summary

Investigation number 199803878
Occurrence date 19/09/1998
Location 2 km W Kajabbi
State Queensland
Report release date 03/08/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Bell Helicopter Co
Model 47
Registration VH-JGO
Serial number VH-JGO
Sector Helicopter
Operation type Aerial Work
Departure point 10 NM SW Kajabbi
Destination 10 NM SW Kajabbi
Damage Destroyed

Robinson R22 Beta, VH-HMR

Summary

This occurrence was investigated in 1998, and a summary report was released. The ATSB received new and significant information about this occurrence in 2004 and initiated further investigation. As a result, the ATSB has revised the summary and reissued the report as follows:

The pilot reported that he disembarked from the helicopter, leaving the engine running and the rotors turning, to converse with a stockman. He was returning to the helicopter when he heard the helicopter's engine and main rotor RPM increasing. The pilot attempted to reach the throttle control and was at the right skid before being forced to dive away as the helicopter became airborne. The helicopter flew into the ground about 5 m from its lift off point and was destroyed. There were no injuries. The wind conditions were reported by the pilot as being light and variable.

The pilot reported that he had set the engine throttle to 75%, selected the governor off, and used the cyclic and collective friction to secure the flying controls. The collective was also fitted with a strap to help secure its position but the pilot could not recall if it was deployed. The operator reported that photos taken after the occurrence indicate that the governor was selected on and the collective strap was not deployed. The circumstances of the occurrence are consistent with inadvertent raising of the collective control.

Occurrence summary

Investigation number 199803826
Occurrence date 14/09/1998
Location Myroodah Station, (ALA)
State Western Australia
Report release date 28/06/2004
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer Robinson Helicopter Co
Model R22
Registration VH-HMR
Serial number 1022
Sector Helicopter
Operation type Aerial Work
Departure point Myroodah Station, WA
Destination Myroodah Station, WA
Damage Destroyed

Cessna A150M, A1500662

Safety Action

At the time of the investigation the Civil Aviation Safety Authority was conducting an investigation into aspects relating to the pilot's licence, training and employment.

Summary

A Cessna 150, VH-FPS, was being used to muster sheep near Dalgety Downs Station. The pilot was communicating by radio with the ground party and had called in one of the party to help with a mob of sheep. A ground party member reported that the aircraft flew past him at about 80-100 ft above the ground before commencing a sharp turn to the right. During the turn the aircraft descended into the ground and caught fire. The pilot received fatal injuries. There was no evidence that the aircraft or engine had been affected by any mechanical fault before colliding with the ground.

About two months prior to the accident, the pilot's employer had arranged for the pilot to receive mustering endorsement training, which included low flying. Subsequent to the accident, the company that conducted the training reported that they had verbally advised the employer that the mustering training could not be carried out, and that only the low-flying portion of the endorsement had been completed. The documentation provided by the training company to the operator indicated that the pilot had only been given a low flying approval. The pilot's low flying training had been conducted in FPS. A review of the aircraft documentation indicated that the hours flown during the training period had been insufficient to permit both the completion of the low flying and stock-mustering training. There was no evidence to indicate that the pilot had completed aerial stock-mustering training.

Approval to conduct aerial stock mustering requires certification that an applicant has completed both low flying and aerial stock mustering training. The approval certificate at appendix II of Civil Aviation Order (CAO) 29.10 was designed to indicate that the applicant pilot had successfully completed the required training, and qualified to conduct aerial stock mustering. The approval certificate had two sections. The first section was to record that the required low flying training had been completed. The second section was to record that mustering training had been completed and the applicant was competent to conduct mustering operations.

The low flying approval certificate issued by the training organisation may have been inappropriate because it was not derived from the CAO current at the time, and because it recorded that the pilot had only undergone low flying training. There was no reference to stock-mustering training on the certificate used. Therefore, the certificate could not have been considered a stock-mustering approval. It appears that the operator did not review the CAO under which the low flying approval was awarded. Had he done so, it would have been evident that stock-mustering endorsement training had not been certified and that the pilot was not qualified to conduct stock-mustering operations.

The investigation could not determine why the aircraft descended into the ground during the turn.

Occurrence summary

Investigation number 199803584
Occurrence date 02/09/1998
Location Dalgety Downs Station, (ALA)
State Western Australia
Report release date 10/09/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model 150
Registration VH-FPS
Serial number VH-FPS
Sector Piston
Operation type Aerial Work
Departure point Dalgety Downs Station, WA
Destination Dalgety Downs Station, WA
Damage Destroyed

British Aerospace Plc AVRO 146-RJ70A , VH-NJW

Safety Action

Local safety action

As a result of this investigation, the following safety actions were initiated by the operator:

  1. The operator advised that action would be taken to ensure a uniform standard of crew resource management across the company.
  2. The pilot in command was provided with additional training to address deficiencies in his knowledge of night visual approaches.

BASI safety action

As a result of investigations into a number of previous occurrences involving crew resource management issues, the Bureau issued interim recommendation IR950101 on 17 July 1995 to the Civil Aviation Safety Authority.

"IR950101

The Bureau of Air Safety Investigation recommends that the Civil Aviation Safety Authority (CASA) require operators involved in multi-crew air transport operations to ensure that pilots have received effective training in crew resource management (CRM) principles. To this end, the CASA should publish a timetable for the phased introduction of CRM training to ensure that:

  1. CRM principles are made an integral part of the operator's recurrent check and training program and where practicable, such training should be integrated with simulator LOFT exercises;
  2. the CASA provides operators and/or CRM course providers with an approved course syllabus based on international best practice;
  3. such training integrates cabin crew into appropriate aspects of the program; and
  4. the effectiveness of each course is assessed to the satisfaction of the CASA".

The following response was received from the Civil Aviation Safety Authority on 8 September 1995:

"I refer to your Interim Recommendation No IR950101 concerning the B747-312 accident at Sydney on 19 October 1994.

CASA fully endorses the principles of and accepts the benefits flowing from CRM and similar training as well as strongly encouraging such training for flight crew, cabin crew and other operating crew. However, CASA is not fully convinced that mandating CRM or similar training, particularly for high and low capacity RPT operations, will necessarily prevent or reduce the incidence of such accidents in the future.

Nonetheless, CASA is willing to further investigate CRM training including the position taken by leading overseas regulatory authorities in this regard, particularly in relation to high and low capacity RPT operations. To this end, CASA intends to consider the issue as part of a major project to commence in the latter part of 1995. This project is to review all aspects of RPT operations conducted under CAR 217 in relation to Training and Checking organisations and is the first major review of such operations to be carried out for some time.

CASA undertakes to advise BASI of the outcome of that review in relation to CRM and similar training".

 

The following response was received from the Civil Aviation Safety Authority on 26 February 1997, and stated in part:

"I refer to BASI Interim Recommendation IR950101 and the Civil Aviation Safety Authority responses of September 1995 and January 1996.

My purpose in writing is to provide you with a formal update on the CASA position on this recommendation. I understand that the CASA General Manager Flying Operations informally conveyed this position to Director BASI earlier this year and sought from him copies of up-to-date material on crew resource management (CRM) training acquired by BASI at a recent Orient Airlines Association seminar. The CASA position for publication is shown in the quotes below."

"After further review along the lines indicated in our response of 8 September 1995, CASA agrees that regulations should be introduced requiring operators engaged in multi-crew air transport operations to have effective crew resource management training programs.

This is one of the tasks being actioned by the Air Transport Technical Committee of CASA's Regulatory Framework Program. The crew training project team working under that committee, which includes representatives from industry, is also considering introduction of other best practice initiatives such as the Advanced Qualification Program (AQP) introduced by the FAA and the New Zealand CAA. Introduction of any new legislation on these matters is of course subject to requirements for appropriate consultation with industry. The RFP has a timetable to complete and publish a new set of Civil Aviation Safety Regulations (CASRs) and associated advisory material by the end of 1998. However, where possible new CASRs will be introduced progressively before that date."

"I would also like to take this opportunity to invite BASI to provide a human factors qualified observer/adviser to assist the project team developing the CRM/AQP regulations and advisory material."

Response classification: CLOSED - ACCEPTED

CASA has since issued a Notice of Proposed Rulemaking (NPRM9809RP) on regulations relating to passenger and crew-member safety. Whilst all aircraft operators and crew members will be affected to some degree by the NPRM, the principal thrust of the proposed changes is to "upgrade safety with respect to the carriage of fare-paying passengers in aircraft requiring the carriage of cabin crew". This implies that the NPRM is largely directed toward multi-crew operations in passenger-carrying aircraft. Section 121.YY of the NPRM refers to crew-member emergency procedures training. Each operator will be required to conduct initial and ongoing CRM training for each crew-member position required for a particular aircraft type.

On 16 September 1999 the Bureau received the following advice from CASA regarding CRM training and the date of introduction of CASR Part 121A:

"It is not anticipated that new Part 121A will be effective before 1 January 2002. However, CASA is aware of the importance of CRM training for crew members and will be issuing a policy that will require operators to conduct such training. This policy will be issued in advance of the introduction of the new regulations and is expected to be in place by 1 July 2000."

The Bureau is currently monitoring implementation of IR950101.

Significant Factors

  1. The pilot in command did not adequately convey his approach intentions to the co-pilot.
  2. The co-pilot, while concerned, did not adequately communicate his concerns to the pilot in command.

Analysis

Although the crew had briefed a night visual approach to Norfolk Island, the unicom advice regarding rain showers in the area was clearly inconsistent with the forecast they held. Investigation of the occurrence identified cockpit crew coordination deficiencies that included ineffective question-and-answer communications, and crewmembers performing tasks in isolation. The crew's performance during the approach might have been more effective had they acted in a manner consistent with recognised principles of crew resource management to ensure that all resources available to the crew were fully and effectively utilised. That the perceptions of the pilot in command and co-pilot were different was in itself an indication that there was a breakdown of communication and coordination between them.

The co-pilot believed that the pilot in command did not clearly communicate his approach intentions during the final approach phase. In effect, the co-pilot was left out of the pilot in command's decision-making loop. This generated a conflict in expectations between the pilot in command and co-pilot that was not resolved. As a result, and in view of the prevailing weather, the co-pilot became concerned for the safety of the operation.

The approach briefing was inadequate. As the crew had flown frequently together during the previous two years, they should have been very familiar with one another's usual practices. The pilot in command could have requested explicit feedback from the co-pilot to assess his understanding of the situation. The crew's familiarity with each other and their destination probably contributed to the brevity of the approach briefing.

The operator had not ensured a uniform standard of crew resource management across the company. Moreover, the safety regulator had not provided operators engaged in multi-crew air transport operations with specific guidance regarding crew resource management. Consequently, the operator was left to assess issues such as syllabus content, standard of training, qualifications of CRM assessors and frequency of assessment.

Summary

Prior to departure from Sydney, the crew received a Norfolk Island weather forecast that indicated conditions should be suitable for a night visual approach. Consequently, just before descent, the pilot in command reviewed the visual approach procedures. During the descent, the Norfolk Island unicom service advised that there were rain showers in the area. Subsequently, the crew conducted a night visual approach in weather conditions where the visibility had reduced to approximately 8,000 m in drizzle and isolated low cloud. Sufficient fuel existed for the crew to divert to Noumea if necessary.

During the latter stages of the approach, the co-pilot assessed the in-flight weather as unsuitable for a night visual approach and assumed that the pilot in command shared this view. As the approach was continued, the co-pilot attempted on a number of occasions to communicate his concern to the pilot in command. However, the pilot in command initiated no significant rectifying action and continued the approach. When the runway lighting was sighted at approximately 2NM on final the visual approach slope indicator system (VASIS) indicated a three-lights fly-up. After the aircraft was safely landed, the pilot in command and co-pilot discussed the conduct of the approach. The pilot in command was somewhat surprised at the level of the co-pilot's concern.

An amended Norfolk Island terminal area forecast (TAF) had been issued during the time of the aircraft's approach, indicating a deterioration in the weather. However, due to the time required to complete normal processing procedures involved in relaying the information to the crew, they did not receive this update.

The operator reported that some deficiencies existed in aspects of crew coordination, and the pilot in command's knowledge of night visual approach procedures. The operator indicated that those issues would be addressed. The pilot in command subsequently commenced a substantial program of training, to be followed by a check before returning to line operations.

The pilot in command and co-pilot had flown together frequently for the preceding two years, both at Norfolk Island and at a previous basing in Australia. Since commencing employment with this operator, neither the pilot in command nor the co-pilot had received crew resource management (CRM) training, despite that being an assessable item of crew line and currency checks. The operator considered the occurrence to be an isolated human performance event. The safety regulator had not promulgated specific guidance regarding crew resource management training to operators engaged in multi-crew air transport operations.

Occurrence summary

Investigation number 199803515
Occurrence date 08/07/1998
Location 9 km WNW Norfolk Island, Aero.
Report release date 01/10/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 British Aerospace
Model AVRO 146
Registration VH-NJW
Serial number E1223
Sector Jet
Operation type Air Transport High Capacity
Departure point Sydney, NSW
Destination Norfolk Island
Damage Nil

Boeing 747-338, VH-EBX

Summary

The crew of a Boeing 747 (B747), maintaining flight level (FL) 390, en route from Cairns to Nagoya, was contacted by the crew of a Boeing 767 (B767), en route from Auckland to Osaka. The B767 crew reported that they had been approved by air traffic control to climb from FL370 to FL390, and that their position was 44 NM south-east of ASEDA, which is located within the Tokyo oceanic control area. The B747 crew reported that they were 54 NM south-east of ASEDA at FL390. Subsequently, the B767 crew advised that they would limit their climb to FL385. Shortly after that exchange the sector controller instructed the crew of the B767 to descend to FL370 due to traffic.

An investigation found that the sector controller was managing five aircraft tracking north on air route A597, together with an aircraft crossing A597. The controller was concerned that the longitudinal separation between the B767 and another following aircraft at FL370 would reduce to less than the required standard, which was either 2,000 ft vertically or 15 minutes longitudinally. Consequently, the controller instructed the B767 crew to climb, but failed to appreciate that the B767 would conflict with the B747 at FL390. However, the controller subsequently recognised that an error had been made and issued alternative instructions.

Occurrence summary

Investigation number 199803491
Occurrence date 24/08/1998
Location 100 km SSE Aseda, (IFR)
State International
Report release date 04/05/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of separation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 747
Registration VH-EBX
Serial number 23688
Sector Jet
Operation type Air Transport High Capacity
Departure point Cairns, QLD
Destination Nagoya, JAPAN
Damage Nil

Aircraft details

Manufacturer The Boeing Company
Model 767
Sector Jet
Departure point Auckland, NEW ZEALAND
Destination Osaka, JAPAN
Damage Nil

Bell 206B(II), VH-FVF

Safety Action

As a result of this occurrence, the Bureau of Air Safety Investigation became aware of an apparent lack of understanding relating to pilots' awareness of their responsibilities in the event of illness or temporary disability. There appeared to be a general misconception that the doctor was responsible for grounding the pilot in such circumstances.

The Civil Aviation Safety Authority has advised BASI that:

"Pilot awareness of any aviation risk is an important element in the safety system, therefore, the Authority has decided to take immediate steps to increase the pilot and doctor awareness of the risks associated with medical fitness and aviation activities.

The September edition of CASA's Flight Safety magazine will include an article highlighting the dangers of flying while suffering from even apparently minor medical conditions. In addition the DAME Newsletter scheduled for release next week will highlight the problem and advise doctors to take a pro-active role in educating pilots when they seek treatment or medical advice."

Significant Factors

The pilot continued to fly after consulting a doctor regarding severe headaches with vision disturbances.

Analysis

The aircraft

A detailed examination of all available parts of the helicopter concluded that the engine was most likely to have been operating and driving the main and tail rotors. Consideration was given to failures that could cause an uncommanded descent or turn in flight. However, the investigation considered it unlikely that an experienced pilot would allow the helicopter to smoothly descend to collision with the ground.

No evidence was found of any pre-existing defect or malfunction to the aircraft that may have contributed to the development of the accident.

The flight path

Under the prevailing conditions, the investigation considered that the track flown by the helicopter was in keeping with the pilot's normal routine. The unusual aspect of the flight path was its inappropriately timed descent.

The helicopter was reported to be in a smooth flight path, with no jerking and no abnormal sounds such as would be produced with an engine power change or sudden control inputs. On impact with the trees, the helicopter was in a steady flight regime, laterally-level and descending at about 1,200 ft/min. This could indicate that the pilot was maintaining his grip on the cyclic control. If the cyclic control was released, it would most likely have fallen to some abnormal position in a short time. This could have caused the helicopter to adopt an unusual attitude very quickly. The conclusion, therefore, is that the pilot may have been able to maintain control in some form or other: from fully conscious, to a situation where he had managed to "freeze" on the controls and simply maintain them in position.

If the pilot was fully conscious, then the flight path may have resulted from a distraction. However, no evidence was found of anyone making a phone call to the aircraft around the time of the accident. In any case, it is unlikely that an experienced pilot flying at low altitude toward rising terrain would allow himself to become distracted for the time involved in this accident sequence (about 15 secs) and not pay any attention to the flight path.

The pilot

The pilot had visited a DAME a few weeks prior to this accident. This was as a result of headaches that had increased in severity and involved vision disturbances. The ENT specialist found a suspected sinus infection and prescribed a course of antibiotics. The investigation found no underlying personal factors, other than the headache problem, that may have played a role in this accident sequence.

There is no evidence that the pilot complied with the relevant regulations, other than his initial referral of the problem to a DAME. CAR 6.16A imposed a condition on the pilot that he not resume flying duties until being cleared to do so. It is likely that the pilot was reluctant to cease his normal duties unless strongly advised. The DAME had not yet reported the pilot's medical situation to CASA. Consequently, CASA were not in a position to take more positive control of the case.

Summary

The pilot was flying the Bell Jetranger from Archerfield to his home base at Channel 10 on Mount Coot-tha. The flight continued normally until passing the Channel 9 buildings situated on the southern end of Mt Coot-tha. Approaching that area at 1,000 ft, the pilot apparently intended to track to the western side of Mt Coot-tha for a landing at the Channel 10 pad. When passing abeam the Channel 9 tower at about 850 ft, the helicopter was seen to enter a descending right turn until it struck trees and the ground 600 ft above sea level on the western slopes of Mt Coot-tha. The helicopter collided with the trees in a laterally-level attitude, with no roll rate, a descent angle of about five degrees, and a speed estimated to be its normal cruise speed. A fire erupted immediately and consumed the helicopter. The pilot was fatally injured as a result of the impact.

Accident locality

Mount Coot-tha is the location of the television transmitting towers for the Brisbane area. Channel 9 is the southernmost tower and Channel 10 is the northernmost tower. Each television station has a helicopter landing site and associated flight paths. As a standard practice, each television station pilot was aware of the others' normal approach and departure procedures and avoided the relevant areas during flights.

The pilot involved in this accident had developed a practice of monitoring the movements of the Channel 9 and Channel 7 helicopters: he would check on their presence while flying to or from his landing site, if the intended flight path took him near the other stations. On the accident flight, this could have been achieved by flying to the west of the mountain.

After passing abeam the Channel 9 area at about treetop height, the route to Channel 10 involved crossing a ridgeline. The ridge was about the same height as the mountain and would have required the helicopter to maintain altitude or climb slightly to cross the ridge.

Weather conditions at the time were suitable for the flight. The wind was light, with an easterly to south-easterly tendency.

Personnel information

The pilot held an Airline Transport Pilot Licence (Helicopter) with a current Class 1 medical certificate, with vision correction required. He had accrued considerable aeronautical experience in both aeroplanes and helicopters. Of this, 7,566.2 hours had been gained in helicopters. His most recent competency check had been a Biennial Flight Review conducted on 12 and 13 August 1998. His most recent medical examination for the issue of a flight crew medical certificate had been conducted in June 1998.

Flight and duty time records maintained by the pilot indicated that he flew the accident helicopter regularly. In addition, he regularly flew a fixed-wing aircraft, normally at fortnightly intervals. His flight and duty time sheet recorded having specialist medical appointments on 10 and 14 August.

Little examination of the pilot's activities and eating habits in the few days prior to the accident was possible. The pilot had recently been under some personal emotional stress. However, information received from colleagues and friends indicated that the current life stress did not appear to have impaired the pilot's routine behaviour and functioning.

Aircraft information

The helicopter was a Bell 206B Jetranger, serial number 1946, manufactured in 1976. It was maintained for operations in private, air work, and charter categories involving flights under the visual flight rules by day or night. Up to the morning of the accident flight, it had accrued 4,532.8 hours time in service.

Three months before the accident, an entry in the maintenance required section of the maintenance release stated "high pitched noise / vibration through airframe at speeds 100 kt +". The clearing endorsement indicated that the helicopter was inspected thoroughly and the inspection doors on the right and left sides had been reshaped to fit more snugly. The entry contained a pilot's clearing signature for the subsequent test flight.

The high speed / high frequency vibration problem was reported to have persisted for some years prior to the accident and attempts to positively isolate the problem had been unsuccessful. Its intermittent nature made troubleshooting difficult. The noise was reported to be present in cold air conditions more consistently than in warm conditions. After considerable discussion with pilots who had experienced, or had attempted to induce the problem, the investigation concluded that the problem was most unlikely to have arisen on the accident flight. In any event, the problem was considered to be unrelated to the controllability of the helicopter.

An examination of all maintenance records did not reveal any other aspect considered likely to have contributed to the accident.

Communications

The helicopter was fitted with a mobile telephone and the pilot routinely carried a pager. Answering the phone involved manipulating a panel on the centre console area to the left of, and slightly behind, the pilot. No evidence of any calls made to the telephone or the pager was found.

Recorded voice communications and radar data for the flights to and from Archerfield were examined. The data indicated that the helicopter was flown normally during the flights.

Wreckage and impact information

The helicopter's initial impact was with the top limbs of a dead tree, followed soon after by collision with a large gum tree. The main rotor blades severed the top half of the tree and the airframe shattered the bottom half, allowing the top half to fall beside the tree stump. Loud bangs heard by witnesses were consistent with these impacts and also with the outbreak of the ensuing fire. The helicopter's speed at the time of impact was estimated to be around 110 kts, its normal cruising speed. Its descent angle of five degrees was consistent with a descent rate of about 1,200 ft/min.

Although the fire consumed most of the airframe, there were sufficient parts available for specialist examination. The investigation concluded that the engine was operating at impact, and the engine was driving the rotor systems. Rotor control systems were also intact, as far as could be examined. A trailing edge balance weight at the inboard end of a main rotor blade was not found. Specialist examination determined that the mounting point at the outboard end of the weight had been fractured for some time prior to the accident flight and that the inboard mounting point had also developed a fatigue crack. The investigation could not establish whether the balance weight finally became detached as a result of impact during the accident sequence or prior to impact. Representatives of the helicopter manufacturer considered that the absence of the balance weight would not have affected the helicopter's controllability. The investigation found no pre-existing defects likely to have contributed to the accident.

Helicopter controllability

The investigation considered a number of possible failures that could have been encountered during the flight. Witness reports were consistent with recorded radar data that indicated the flight path was smooth, with no unusual noises or abrupt movements of the helicopter. At impact, the helicopter was laterally-level and at high speed. The cyclic control movement needed by a pilot to transition from level flight to a descent angle of about five degrees (corresponding to a descent rate of 1,200 ft/min) was reported to be about 12 mm. The investigation was advised that an experienced pilot would normally be aware of this amount of cyclic control movement.

Loss of tail rotor control in the cruise was considered and assessed as not being a significant immediate problem, due to the speed of the helicopter at the onset of the accident sequence. The pilot could have turned away from the mountain towards the valley to the left, where appropriate decisions could be made without the need to avoid terrain.

Possible jamming of the hydraulic system associated with the main rotor controls was considered. If a failure caused a control deflection fully one way suddenly, an abrupt flight path deviation and change in aircraft noise would be expected. Similarly, a jammed control should also be likely to produce some abrupt movements, at least initially. Both problems should have been controllable by the pilot as the aircraft hydraulics are designed to be overpowered.

Had engine power loss or surging occurred, these should have produced some audible changes in noise from the engine and the rotors. A turn initiated by the pilot toward the lower ground, climb and slowing of the helicopter would also be expected.

A bird strike, or some other event affecting the pilot, was also considered. If the pilot had been incapacitated to the extent that he was unable to control the helicopter, then the flight path would be expected to have changed in some way. Experienced pilots interviewed during the investigation indicated that if the cyclic control is released it should remain in position for a few seconds and then start to fall in a random direction. The rate of change could increase if the control diverged from the central point. This could produce obvious changes in aircraft noise and flight path.

Medical information

Medical evidence provided to the investigation indicated that the pilot had suffered from a subarachnoid haemorrhage, for which no bleeding vessel could be found, in June 1994. His flight crew medical certificate had been cancelled as a result of that event. A Class 2 medical certificate was issued as a result of a medical examination in June 1995. His next medical examination was in July 1996 and Class 1 and 2 medical certificates without restriction were issued in August 1996. Further routine flight crew medical examinations were subsequently passed in June 1997 and June 1998.

On 28 July 1998 the pilot attended a designated aviation medical examiner (DAME), reporting that he had begun to experience severe, migrainous type headaches with blurred vision and instances of double vision. The DAME considered that there was a strong possibility that emotional stress was the cause. Since the symptoms did not match the normal indications of migraine headaches, the doctor referred the pilot to a neurologist for specialist examination. The DAME also indicated that the patient was a pilot and asked for advice concerning whether he should continue flying (the pilot was keen to continue flying). The pilot initially consulted the neurologist on 5 August and a follow-up meeting was held on 10 August. With no neurological problems evident as a result of that examination, he was then referred to an ear nose and throat (ENT) specialist who diagnosed a severe sinus infection. The specialist prescribed a course of antibiotics. That visit had taken place on 14 or 17 August. No information on the speed of onset of the headaches was available.

The neurologist involved in the 1994 event was the same person involved in the pilot's recent specialist examination, and had concluded that the pilot's current symptoms had not been related to the pilot's previous medical history.

Evidence available to the investigation indicated that the pilot had suffered a headache early in the morning of the accident flight and some Channel 10 staff reported that he did not appear to be well on arrival at work. On the other hand, other people familiar with the pilot had attended the meeting at Archerfield and reported that he seemed normal at that time.

Post-accident advice from the Civil Aviation Safety Authority aviation medicine staff indicated that, based upon information obtained from the medical practitioners, the pilot had experienced a change in his medical condition so that he no longer met the required medical standard.

The limited post-mortem information available did not assist with an assessment of the pilot's physiological state at the time of impact. There was insufficient post-mortem evidence to determine if any neurological anomalies had contributed to the accident.

Medical regulations

Considering that the pilot had experienced recent medical problems and had consulted a DAME, the relevant Civil Aviation Regulations (CARs) were examined. Anecdotal evidence indicated that the DAME could have advised the pilot as to whether or not he could continue with his flying duties. CAR 6.16A also indicated that the pilot was not permitted to fly, pending a resolution of his medical situation.

CASA normally provides each DAME with more detailed guidance on the matters considered significant to aviation. The neurological section described different forms of headaches and the considerations involved with each type. In relation to the type of headache considered likely to involve this pilot, the guidance stated, "Such migraines are characterised by long periods of remission and capricious onset, and may completely incapacitate the sufferer. All cases will be considered on an individual basis."

Occurrence summary

Investigation number 199803297
Occurrence date 18/08/1998
Location Mt Coot-tha, (ALA)
State Queensland
Report release date 05/11/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Bell Helicopter Co
Model 206
Registration VH-FVF
Serial number 1946
Sector Helicopter
Operation type Business
Departure point Archerfield, QLD
Destination Mt Coot-tha, QLD
Damage Destroyed

Cessna 208B, VH-URT

Safety Action

Following the incident, the Civil Aviation Safety Authority issued the following directions to the operator:

  1. Conduct daily water washing of the compressor and compressor turbine, after the last flight of the day when operating in a salt laden environment,
  2. Conduct engine condition trend monitoring (ECTM) in accordance with the procedures detailed in CASA Airworthiness Advisory Circular 6-29 Amdt-1, and
  3. Conduct boroscope inspections of the compressor turbine at intervals not to exceed 110 hours time in service, or alternatively conduct detailed hot end inspections at intervals not exceeding 750 hours time-in-service.

In addition to these directions, CASA issued Airworthiness Directive AD/PT6A/28 applicable to all PT6A series engines installed in single-engine aircraft. This airworthiness directive detailed the requirements listed above as well as requiring all operators to carry out a visual inspection of the compressor turbine blades for evidence of sulphidation, and to continue to carry out engine compressor turbine washing in accordance with the procedures detailed in the applicable Pratt and Whitney Canada maintenance manual.

CASA also published an article in the November 1998 issue of the CASA magazine Flight Safety Australia, which outlined the circumstances of the incident, and explained sulphidation, its causes, and preventative measures.

Summary

The pilot of the Cessna 208B reported that, after a normal departure from Badu Island, he established the aircraft in cruise at about 5,000 ft for the flight to Saibai Island. The engine had performed normally up to that time. Shortly after becoming established in the cruise, the pilot heard a muffled bang from the engine compartment. On checking the engine instruments, he saw that the gas generator RPM (Ng) had stabilised at about 52% and the turbine temperature was at about 700 degrees C. (The maximum allowable temperature was 740 degrees C.) The pilot initially thought that these symptoms may have indicated an engine fire, so he shut down the engine and feathered the propeller. However, appropriate checks indicated that there was no fire. During these observations, the pilot had turned the aircraft towards Badu Island.

The pilot then attempted two engine starts, neither of which was successful. On each occasion, Ng stabilised at 17%, fuel flow was 110 lb/h, and engine light-off occurred at 850 degrees C. Eventually, Ng stagnated at 42-43% and the propeller unfeathered, but there was no indication of engine torque.

The pilot transmitted a distress call after the first start attempt. After the second attempt, he decided to concentrate on flying the aircraft and realised that his best option was to try to land on a narrow beach on the northern side of Badu Island. He was able to achieve this without any damage to the aircraft.

The aircraft was powered by a Pratt and Whitney Canada PT6A turboprop engine. Examination of the engine revealed that a compressor turbine (CT) blade had failed at about mid-span. The liberated section of blade had struck two adjacent blades, causing them to break. Metallurgical examination of the remaining section of the failed CT blade indicated that the fracture line passed through the centre of a deep sulphidation pocket. Impact damage was observed on all the remaining CT blades. Detailed examination of these blades revealed a total of seven blades that exhibited some degree of cratering due to sulphidation. Inspection of the compressor section of the engine also revealed significant corrosion consistent with operation in a salt-laden atmosphere.

"Sulphidation" refers to the reaction of sulphur containing compounds with metallic components that have been exposed to a hot gaseous environment. Components of gas-turbine engines located in the hot gas path, such as blades and vanes, are exposed to sulphidation during normal operation. Corrosive sulphates are formed during the combustion process from sulphur in the fuel and sodium and potassium salts present in the fuel and air, in particular the air in marine environments. If the accumulations of sulphur-containing salts are not removed from the surfaces of the turbine blades and vanes, the protective oxide coating will be attacked and the underlying alloy rapidly corroded.

The PT6A engine maintenance manual required desalination water-washes to be applied to both the compressor and the turbine after the last flight each day. The operator was conducting compressor washes prior to the first flight of each day, using the compressor wash ring installed on the engine. A special wash tube assembly tool for installation into the gas generator igniter boss, to enable wash solution to be introduced directly to the first-stage turbine blades, was available from the engine manufacturer. The operator was not using this tool. As a result, effective washing of the turbine blades was not achieved, allowing salt deposits to build.

The engine was fitted with an Engine Condition Trend Monitoring (ECTM) system which recorded a number of key engine parameters such as fuel flow, inlet turbine temperature, torque, and Ng. Use of this system allowed operators to delete a fixed-time hot section inspection (HSI) requirement in favour of basing the HSI interval on the results of engine condition trend monitoring. Use of the ECTM system was acceptable to the Civil Aviation Safety Authority (CASA), provided the procedures were in accordance with CASA Airworthiness Advisory Circular 6-29 `PWC PT6A Series Engines HSI Policy' 5/98. Investigation revealed that the operator was not complying fully with all the requirements of the circular.

Occurrence summary

Investigation number 199803389
Occurrence date 21/08/1998
Location Badu Island
State Queensland
Report release date 27/08/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Forced/precautionary landing
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Cessna Aircraft Company
Model 208
Registration VH-URT
Serial number 208B0428
Sector Turboprop
Operation type Charter
Departure point Badu Island, QLD
Destination Sabai Island, QLD
Damage Nil

Grumman American Aviation Group GA-7, VH-WPX

Summary

The aircraft was outbound from Adelaide on the first sector of a daily bank run and was being operated at night under the Instrument Flight Rules. The pilot reported that the township lights of Minlaton were visible during the descent, and the runway lights were clearly visible from a distance of about 12 NM. The pilot joined the circuit on a downwind leg for runway 15 and said that the runway lights were visible on both downwind and base legs. Shortly after turning final, at a height of approximately 400 ft, the pilot initiated a missed approach after losing sight of the runway. The runway lights were visible as the aircraft passed overhead the aerodrome, as were the lights of a motor vehicle passing the southern end of the runway. The pilot elected to attempt another approach for runway 15, with the option of landing on runway 33, if the second approach was unsuccessful.

A second circuit was flown at about 800 ft, with the runway lights remaining in sight on the downwind and base legs. Shortly after turning final the aircraft entered patchy low cloud that was obscuring the runway lights for brief periods. The pilot reported that he was in the process of commencing a second missed approach when he regained visual contact. He reduced power but again lost contact. While searching for the runway lights he initiated a missed approach but felt the main wheels touch down. He immediately closed the throttles and allowed the aircraft to roll to a stop.

The aircraft had touched down in a paddock approximately 800 m before the runway threshold and had rolled normally on its landing gear for about 600 m. However, the aircraft was substantially damaged when it entered a lightly timbered area at moderate speed. The pilot sustained minor injuries.

The Area 50 forecast prepared by the Bureau of Meteorology, valid from 0130 to 1430 Central Standard Time, indicated that the aircraft would be operating to the west of a trough moving through the area. Isolated showers and drizzle, together with broken low cloud on the coast and western slopes, were forecast until 1130. Isolated fog patches were forecast until 1030.

The terminal area forecast (TAF) issued for Minlaton at 0434 for the period 0530 to 1730, predicted a light south-westerly wind and rain showers. Broken cloud cover was forecast at a height of 2,500 ft, with a few lower patches at 1,200 ft, together with a visibility greater than 10 km. The forecasting officer preparing the TAF considered the possibility of low stratus, fog or drizzle affecting aircraft operations into Minlaton. However, each was discounted on analysis of the synoptic situation and on other available information. The Minlaton TAF was reviewed at 0600 but it was considered that no amendment was required. The Bureau prepares regular aerodrome forecasts for Minlaton, without the benefit of local weather observations.

The pilot subsequently lost visual contact with the runway lights at low altitude when the aircraft entered a localised area of cloud or fog, at a height lower than forecast. The aircraft had then inadvertently contacted the ground while the pilot was initiating a missed approach.

Occurrence summary

Investigation number 199803049
Occurrence date 07/08/1998
Location Minlaton, (ALA)
State South Australia
Report release date 15/07/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Minor

Aircraft details

Manufacturer Grumman American Aviation Corp
Model GA-7
Registration VH-WPX
Serial number GA7-0104
Sector Piston
Operation type Charter
Departure point Adelaide, SA
Destination Minlaton, SA
Damage Substantial

Air Tractor AT-502, VH-SNA, near Rocky Gully, Western Australia, on 14 August 1998

Summary

The Air Tractor was being used to conduct aerial reconnaissance of a forestry area prior to spraying the trees. The north-easterly wind was gusting from about 15 kts and there was 8 OCTAS of low cloud with passing rain showers. The horizon was often obscured. The pilot reported that he encountered some turbulence during the flight.

On completion of the reconnaissance flight, the pilot decided to land towards the east-south-east. He reported that late in the landing approach, with full flap selected the aircraft unexpectedly rolled left. He was unable to correct the roll before the left landing gear struck the perimeter fence. The aircraft veered left, and its left wing struck the chemical loader that was parked near the edge of the airstrip. The aircraft then cartwheeled before coming to rest inverted. The pilot and bystanders were unhurt, but the aircraft was destroyed.

No deficiencies could be found with the aircraft that may have contributed to the accident.

Occurrence summary

Investigation number 199803258
Occurrence date 14/08/1998
Location 19 km E Rocky Gully
State Western Australia
Report release date 04/08/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer Air Tractor Inc
Model AT502
Registration VH-SNA
Sector Turboprop
Operation type Aerial Work
Departure point Rocky Gully, WA
Destination Rocky Gully, WA
Damage Destroyed