Hiller UH-12E, VH-MJV

Summary

The Hiller UH-12E helicopter was tracking from Quirindi to Tamworth. The pilot attempted to call Tamworth Tower on both tower frequencies but received no reply. As the helicopter approached the control zone boundary at 15 NM from Tamworth, the pilot called the tower again but received no reply. He then landed the helicopter and called the tower using his mobile telephone, but received only a recorded message.

Suspecting either a problem with his radio or that the tower was not active, the pilot decided to enter the control zone without a clearance, transmitting his position and intentions on the tower radio frequency. He flew the helicopter into the circuit area and crossed runway 12R between one CT4 aircraft that had landed and a second CT4 on final approach. Upon sighting the helicopter, the aerodrome controller broadcast a traffic alert to the five aircraft operating in the circuit.

The pilot landed the helicopter at the base of the tower and shut down. He walked to the tower and called the controller on intercom. He reported that his radio was unserviceable and requested clearance to re-position the helicopter to the general aviation parking area for repair of the radio. The controller refused clearance and asked the pilot to have the radio repaired before flying the helicopter again. The pilot reported that at the time, he informed the controller that he was unfamiliar with Tamworth Aerodrome, but the controller terminated the discussion. The pilot then walked to the general aviation area, crossing two grass runways without authority.

The controller later stated that the time between his initial sighting of the helicopter and its landing at the base of the tower was insufficient to enable him to give a light signal to the helicopter. There was also insufficient time to instruct the CT4 on final approach to go around.

Examination of the helicopter radio revealed that the frequency selector gears had slipped out of mesh and out of position.

The pilot reported that this was his first flight into the Tamworth control zone, and that he had not briefed himself adequately before departing Quirindi. Aeronautical Information Publication ENR 1.1 section 9.2 (dated 10 August 2000) detailed the requirements for VFR flights entering Classes C or D airspace. Paragraph 9.2.1 stated:

"Before reaching the boundary of classes C or D airspace, the pilot must establish two-way communications with ATC on the frequency notified on the chart, in ERSA, or AIP supplement or NOTAM, and obtain a clearance."

Enroute Supplement Australia EMERG 2 detailed the procedure for flights OCTA under VFR experiencing communications failure, and stated:

Stay in VMC

Broadcast intentions (assume transmitter is operating and prefix calls with "Transmitting blind") Remain VFR and land at the nearest suitable non-MBZ aerodrome. Report arrival to ATS if on SARTIME or reporting schedules. Search and Rescue telephone number 1800 815 207.

Occurrence summary

Investigation number 200005967
Occurrence date 12/12/2000
Location Tamworth, Aero.
State New South Wales
Report release date 20/07/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Hiller Aviation
Model UH-12
Registration VH-MJV
Serial number 5124
Sector Helicopter
Operation type Aerial Work
Departure point Quirindi, NSW
Destination Tamworth, NSW
Damage Nil

Boeing 737-476, VH-TJP

Analysis

A combination of wind effect and aircraft mishandling was the most likely reason for the rapid rotation that led to the tail strike. As the aircraft was subject to 10 kts of crosswind and 3 kts of tailwind during the take-off, it was considered possible that this knowledge may have induced the pilot in command to incorrectly anticipate aircraft response to control input. Furthermore, the change in wind effect just before rotation, although not a significant amount (approximately 6 kts), may still have had an effect on the control feel and/or resulted in a marginal reduction in lift at that crucial phase of the take-off.

As the aircraft was fully pressurised and climbing through flight level 320 when ATC informed the crew of the pavement damage, the crew were clearly unaware of the tail strike before receiving this information. Following lift-off, the almost immediate distraction of the MWS and the need to consult the QRH may have, at the very least, diverted the crew's thought processes at a busy time. The rapid but normal climb that followed and the delay in receiving ATC confirmation of the tail strike possibly guided the pilot in command toward his decision to continue the flight rather than return to Melbourne.

Communicating with ATC is just one of the many tasks that are required of the crew during the period immediately after take-off. It can be a demanding phase of flight and controllers are aware of minimising transmissions to the crew during this phase. However, a more timely report to the crew from ATC may have enhanced the flight crew's situational awareness. This would have allowed them the benefit of additional information on which to decide a course of action.

This incident highlighted the fact that the aircraft operator's/manufacturer's Non-Normal Checklist may not be able to deal specifically with every conceivable variation in a non-normal situation that may arise during the course of a flight. Pilots are therefore required to use their judgement in order to ensure the safety of the aircraft.

Summary

The crew of an aircraft awaiting take-off clearance reported that a departing Boeing 737-400 struck its tailskid during rotation. That information was passed to the Tower Controller, however there was a delay of almost 12 minutes in relaying the advice to the flight crew while the runway was inspected to confirm that a tail strike had actually occurred.

The crew of the 737-400 reported that they had felt a thump during the rotation but believed it was the sound of an oleo leg bottoming. Shortly after the tailskid contacted the runway surface, the aircraft's Master Warning System (MWS) drew the crew's attention to faults in the hydraulic and flight control systems. The initial part of the climb was therefore taken up with the Quick Reference Handbook (QRH) Non-Normal Checklists concerned with the hydraulics problem, in addition to normal departure procedures.

Shortly after takeoff, the Cabin Services Manager informed the pilot in command that the rear cabin crew had heard a bump during during the takeoff. However, the pilot in command believed this was related to the hydraulic problem. The Cabin Services Manager later passed on additional information describing the sound as a "metallic scraping noise". At that time the aircraft was climbing through flight level 320 and was fully pressurised. The possibility of a tail strike was further indicated to the flight crew when they were informed by air traffic control (ATC) that there had been some pavement damage to the runway from which they had departed. The QRH procedure for a tail strike on takeoff was to ensure that the aircraft was not pressurised in case of possible structural damage. However, the procedure was reliant upon the flight crew being immediately aware that a tail strike had occurred. It did not give guidance on a course of action when the tail strike was not recognised until after the aircraft was pressurised. As it was then only 25 minutes before the aircraft would be commencing descent (at which time the depressurisation process would commence) and the pressurisation system was operating normally, the PIC elected to continue the flight to Adelaide.

Maintenance personnel inspected the aircraft on arrival and confirmed a tail strike. No damage was sustained by the tailskid except removal of paint. The hydraulic systems were also checked but no fault could be found. During the subsequent departure from Adelaide there was a recurrence of the hydraulic fault. Indications of Hydraulic System "A" low pressure and "Flight Control" low pressure were a repetition of the faults experienced on departure from Melbourne. It was subsequently determined that a hydraulic reservoir T-piece was clogged where it metered the "A" system and was the cause of the pressure fluctuations. Analysis of the Flight Data Recorder (FDR) data determined that the MWS activated in response to low pressure in hydraulic system "A" while the landing gear was in its retraction cycle and was not connected to the tail strike event.

Boeing data (Airliner, Jul-Sep 1994) suggested that the most common factors in takeoff tail strike events are excessive rotation rate and early rotation. Information from the operator's Flight Crew Training Manual indicated that takeoff and initial climb performance depend on rotating at the correct airspeed and proper rate, to the rotation target attitude. Rotation should be smooth and at an average pitch rate of 3 degrees per second. A body attitude of 9 to 10 degrees would be achieved in approximately 2.5 to 3 seconds with all engines operating, with liftoff occurring at a pitch attitude of 9.1 degrees. When the rotation rate exceeded 3 degrees per second, the minimum tail clearance decreases, and may result in contact with the ground. The minimum tailskid clearance on a normal "flaps 5" takeoff should be approximately 58 cm and occurs after liftoff. This is a consequence of the aircraft geometry and the dynamic forces that are acting after rotation has been initiated.

Analysis of FDR data for the incident indicated that rotation commenced at the correct indicated airspeed of 144 kts. The recorded data also showed that the aircraft had been subject to a rapid rotation during the liftoff period. From nose wheel off the ground to the main wheels leaving the ground, the average rotation rate was 4.3 degrees per second.

The incident occurred on the first sector of the day, the pilot in command was the handling pilot and was very experienced on the Boeing 737-400. The takeoff was conducted from runway 27 with a surface wind of 150-180 degrees at 5-12 kts. The aircraft was therefore subject to approximately 10 kts of crosswind and up to 3 kts of tailwind during the takeoff roll. Analysis of FDR data confirmed that during the 7 seconds prior to rotation the wind effect on the aircraft changed from 3 kts of headwind to 3 kts of tailwind.

Occurrence summary

Investigation number 200005684
Occurrence date 29/11/2000
Location Melbourne, Aero.
State Victoria
Report release date 20/12/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Ground strike
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 737
Registration VH-TJP
Serial number 24441
Sector Jet
Operation type Air Transport High Capacity
Departure point Melbourne, VIC
Destination Adelaide, SA
Damage Nil

Beech Aircraft Corp 200C, VH-KFN

Safety Action

As a result of this occurrence, the Australian Transport Safety Bureau issues the following recommendations:

R20010085

The Australian Transport Safety Bureau recommends that the Civil Aviation Safety Authority review the potential side effects on humans of a mix or cocktail of HFC-134a refrigerant, in its gaseous form, and the associated air conditioning system lubricant. If that review finds the use of such materials is significantly adverse to human health, the use of HFC-134a refrigerant and its associated lubricant as an air conditioning refrigerant in aircraft should also be reviewed.

R20010124

The Australian Transport Safety Bureau recommends that the Civil Aviation Safety Authority advise the aviation industry of the potential side effects on humans of the mix or cocktail of HFC-134a refrigerant, in its gaseous form, and the associated lubricant.

R20010086

The Australian Transport Safety Bureau recommends that the Federal Aviation Administration of the United States review the potential side effects on humans of a mix or cocktail of HFC-134a refrigerant, in its gaseous form, and the associated air conditioning system lubricant. If that review finds the use of such materials is significantly adverse to human health, the use of HFC-134a refrigerant and its associated lubricant as an air conditioning refrigerant in aircraft should also be reviewed.

R20010087

The Australian Transport Safety Bureau recommends that Raytheon Aircraft Company review the potential side effects on humans of a mix or cocktail of HFC-134a refrigerant, in its gaseous form, and the associated air conditioning system lubricant. If that review finds the use of such materials is significantly adverse to human health, the use of HFC-134a refrigerant and its associated lubricant as an air conditioning refrigerant in aircraft should also be reviewed.

Analysis

It was probable that, from the description of the odour detected by the crew, the refrigerant and oil that was found leaking from the forward air conditioning evaporator were the source of fumes inhaled by the crew. The smell of the melting plastic tie and heated insulation material was not directly relevant to the safety problem. Leakage of refrigerant may allow the ingress of moisture into the air conditioning system leading to formation of other hazardous contaminants. Consequently, the fumes inhaled by the crew may have been a mix of refrigerant HFC-134a, oil lubricant and any other contaminants present in the air conditioning system. The symptoms exhibited by the crew were consistent with those described in the MSDS for both the refrigerant and the oil.

The aircraft was cruising at FL250. Under normal conditions, the Beech 200 pressurisation system is designed to provide a cabin pressure altitude of approximately 3,900 ft at an aeroplane operating altitude of 20,000 ft; 9,900 ft at 31,000 ft and 11,700 ft at 35,000 ft. The occurrence flight was operating at an altitude of 25,000 ft, and the aircraft's pressurisation system would have been expected to maintain the cabin altitude at approximately 6,800 ft.

The aircraft's cabin altitude was maintained by restricting the outflow of air from the cabin which would lower the rate at which total cabin air is changed and consequently may have allowed an accumulation of fumes. Additionally, because the cabin pressure was less than sea level, any air conditioning system gas released into the cabin would expose the crew to higher concentrations of contaminant cocktail, particularly in the relatively small cabin volume of a little over 11 cubic metres. Despite the studies conducted by several agencies including the USEPA and the US Navy, it appeared that no research has been performed into the use of HFC-134a or the cocktail of refrigerant and additives in the aviation industry. Extrapolation of the results of the US Navy study appeared to confirm that the release of HFC-134a into an even more confined area such as in an aircraft cabin is likely to be more hazardous.

PAFT noted that the release of the entire refrigerant charge from a domestic refrigerator (6 ounces) into a space the size of the typical kitchen would not pose a risk. This is a space considerably larger than the 11 cubic metres of the aircraft cabin involved in this occurrence. The initial refrigerant loss during the occurrence was an estimated at 1.1 pounds or approximately .5 kg. This represented about 17% of the total refrigerant capacity of the system. If the oil content, in solution with the refrigerant, lost a similar percentage of its total, then the system could have lost about 22 ounces (.625 kg) of its total system content of refrigerant and oil into the cabin. The location of the pipe fracture on the high-pressure side of the system probably resulted in a sudden and total loss of the system contents into the cabin in a very short time. However, the precise rate at which the air conditioning system discharged into the confines of the relatively small aircraft cabin could not be determined. The PAFT recommendation to keep vents open when operating air conditioning systems in automotive vehicles was not an option available to the pilot until the aircraft was depressurised.

The stresses that resulted in the pipe fracture may have been introduced some time prior to the incident during maintenance on the fittings. Access to the fittings is difficult and proper support with tools of both halves of the fitting during the torque fastening procedure was reported as not always possible. This may have been a factor in the fracture of the pipe.

Factual Information

The Beech Super King Air aircraft was maintaining flight level (FL)250 on an aerial ambulance flight, when members of the medical crew advised the pilot that they noticed an unusual burning odour in the cabin, similar to that of a bakery. When the smell became stronger, the pilot elected to return the aircraft to the maintenance facility at Jandakot.

A short time later, in addition to the cooking odour, an odour similar to hot plastic and rubber was smelt by the crew. The medical crew elected to don therapeutic oxygen masks and advised the pilot that the smell had become more intense and that they had now gone onto oxygen. The flight nurse observed that the doctor's complexion had changed to ashen gray and he was leaning against the cabin bulkhead with his eyes closed. The nurse then assisted the doctor to don his oxygen mask. The nurse said that the doctor was in a confused mental state. The nurse only recognised the seriousness of the situation "when the doctor's speech became slurred and was running his words together in their sentences". The nurse stated that his own symptoms manifested very quickly and he "felt quite euphoric and light headed". The nurse also estimated that by the time he donned his own oxygen mask, he was rapidly approaching unconsciousness. The pilot donned his oxygen mask and, when he feared he may be sick in his mask, initiated an emergency descent to 10,000 ft. During the descent he depressurised the cabin in an attempt to clear the fumes.

The crew reported that the fumes in the cabin had caused them to experience nausea and confusion soon after they detected the smell. They remained on oxygen for the rest of the flight.

The pilot reported that while inbound he had asked Air Traffic Services (ATS) to repeat instructions on several occasions and this prompted ATS to ask him to confirm that operations were normal. He did not recognise any of the landmarks that he usually used to identify his correct track while on approach to Jandakot. He stated that on that occasion his vision was affected to the extent that he had great difficulty focussing outside the cockpit. The pilot said that following the emergency descent to 10,000 ft, he engaged the autopilot and changed the GPS to the coordinates for Jandakot. The aircraft autopilot then flew the GPS guided track to abeam Jandakot from where the pilot took control and conducted the landing. He could not recall anything about the approach and landing, and later had to ask the flight nurse if he had used any flap, because the flaps were in the retracted position after landing and he did not remember retracting them. After landing, the crew's symptoms did not significantly improve and they were taken to hospital for medical assessment.

Several months after the occurrence, some members of the crew reported to the ATSB that they were still suffering various residual effects including headaches, elevated blood pressure, reduced concentration levels and anxiety. They attributed the symptoms to their exposure to the fumes encountered on the occurrence flight.

A maintenance investigation following the occurrence discovered several air conditioning system defects. A bleed air pressure-reducing valve in the under-floor cabin area was found to be leaking hot bleed air onto an adjacent air conditioning duct. There was also evidence that the insulation was heat affected and had discoloured from the bleed air leak. A "spirap" type loom bundling plastic tie was also found in the vicinity, which had been melted. Samples of those heat-affected items were taken by the ATSB and forwarded to a laboratory for testing, to identify if heat application produced any emissions. The results of that testing and subsequent instrumented flight test showed that the bleed air leak did not reach a sufficiently high enough temperature to be considered a source of hazardous fumes in this incident.

In addition to the faulty reducing valve, two air conditioning refrigerant leaks were detected in the forward air conditioning evaporator refrigerant pipes. Airconditioning compressor lubricating oil was also observed on the evaporator and dripping from a fractured flared fitting onto the surrounding structure. The fitting was located on a pipe that delivered high pressure liquid refrigerant to the expansion valve and evaporator. When the system refrigerant was replenished during the maintenance investigation, it was noted that a considerable quantity of refrigerant was required to refill the system. The initial refrigerant loss was estimated as at least 1.1 pounds or approximately 0.5 kg. As the lubricating oil level could not be determined with any accuracy, maintenance personnel then decided to totally evacuate the system and replenish refrigerant and oil levels from empty. The nature of the leak, troubleshooting and repairs precluded an accurate measurement of the total oil and refrigerant quantities that had escaped and the initial estimate would have been the minimum system loss incurred from the leak. The pipes and fittings to the evaporator were located in a confined space to which proper access for some maintenance activities was very difficult.

The vapour cycle type air conditioning system in the aircraft used a new environment-friendly refrigerant HFC-134a instead of the ozone depleting refrigerant type R12 that had been in service for many years. The design of the vapour cycle systems was such that a significant amount of the oil lubricant for the air conditioning compressor was in solution with the refrigerant. The polyol ester-based lubricating oil had a particular odour when heated, which was similar to the smell detected by the crew.

The Material Safety Data Sheet (MSDS) for HFC-134a stated, "overexposure can cause central nervous system depression with dizziness, confusion, incoordination, drowsiness or unconsciousness. Irregular heartbeat with a strange sensation in the chest, `heart thumping', apprehension, light-headedness, feeling of fainting, dizziness, weakness, sometimes progressing to loss of consciousness and death. Suffocation if air is displaced by the refrigerant vapours".

The MSDS for the polyol ester-based lubricating oil that was used in conjunction with the refrigerant charge stated that inhalation may cause nasal respiratory irritation and dizziness. The operator's engineering manager also stated that the lubricating oil was known to produce valeric acid when heated which was known to cause dizziness and nausea. He stated that prolonged exposure could lead to unconsciousness. The MSDS sheet supported that. In addition to the refrigerant charge of 104 ounces or almost three kg of HFC-134a, the air conditioning system was also charged with 34 ounces or almost one kg of polyol ester oil, of which approximately 26 ounces or almost 75% was held in solution with the refrigerant gas/liquid.

In addition to the refrigerant and oil chemicals, the airframe manufacturer had a maintenance warning that when moisture entered the air conditioning system, it could cause the formation of hydrofluoric acid or hydrochloric acids. The MSDS data for those compounds gave warnings of eye irritations and burns when exposed to the mist or vapours.

The Programme for Alternative Flurocarbon Toxicity (PAFT) found in 1987 that the HFC-134a refrigerant exhibited a very low risk and was considered to be "practically non-toxic". The PAFT tests stated that at very high concentration levels (over 50%), exposure could sensitise the heart to adrenaline and that it could cause irregular heartbeat, even death.

A 1998 University of New South Wales (UNSW) study on the use of HFC-134a in the confined space of motor vehicles concluded that the refrigerant posed a considerable risk to vehicle occupants. It cited two scientific reports in the United States and four scientific papers in peer reviewed journals describing adverse effects expected from human inhalation as all being "scientifically consistent". The study recommended that fresh air vents be kept open at all times when using the air conditioning system and to introduce a pungent odour producing element into the systems to aid in the early detection of refrigerant leaks.

The United Sates Environmental Protection Agency (USEPA) and the US Navy Bureau of Medicine commissioned research to determine safe levels of exposure to HFC-134a. The studies concluded with statements of significantly different safe exposure values. The US Navy-determined levels of acceptable exposure were significantly lower than the values assessed by the USEPA. The US Navy research into the exposure of humans to HFC-134a was conducted in a confined area to simulate the confines of a submarine.

Although there was research data available on HFC-134a and polyol ester-based lubricants, at the time of preparing this report, the ATSB could not find any data on the effects of exposure to HFC-134a at air pressures less than sea level. Similarly, the ATSB could not find data on exposure to a mix or "cocktail" of the two agents HFC-134a and polyol ester lubricants at air pressures at sea level or less than sea level.

Occurrence summary

Investigation number 200005948
Occurrence date 02/12/2000
Location 102 km W Southern Cross
Report release date 21/12/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fumes
Occurrence class Serious Incident
Highest injury level Minor

Aircraft details

Manufacturer Beech Aircraft Corp
Model 200
Registration VH-KFN
Serial number BL-31
Sector Turboprop
Operation type Aerial Work
Departure point Jandakot, WA
Destination Kalgoorlie, WA
Damage Nil

Piper PA-31-350, VH-FIA

Summary

Approaching Adelaide on descent, the pilot of the Piper PA31 observed that the main cabin door had opened in flight. A direct track to Adelaide was requested and the aircraft landed uneventfully a short time later.

An inspection by the pilot found that the door handle was still in the locked position and all locking pins were extended. The pilot reported that the door was properly closed and locked prior to departure.

A maintenance inspection was unable to fault the door locking mechanisms and a series of functional tests of the door concluded that the door could not be opened without first moving the handle to the OPEN position.

The aircraft was returned to service. The pilot then flew a total of six sectors over two days without further incident, however at the completion of the seventh sector, the pilot noticed that the locking handle had moved approximately halfway between the fully closed/locked position and fully open/unlocked.

Maintenance personnel again inspected the aircraft, but no fault could be found. During that inspection, it was noted that when closing the stair door from the outside, the forward support cable could become wedged in between the door and the jam. This would not be immediately apparent to the pilot if closing the door from the outside and could prevent the door locks from correctly securing the door. The aircraft was returned to service without further incident.

Occurrence summary

Investigation number 200005640
Occurrence date 28/11/2000
Location 41 km SW Adelaide, Aero.
State South Australia
Report release date 02/04/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-31
Registration VH-FIA
Serial number 31-7752032
Sector Piston
Operation type Air Transport Low Capacity
Departure point Kingscote, SA
Destination Adelaide, SA
Damage Nil

Amateur Built RV-6A, ZK-VBC

Safety Action

Independent of the ATSB investigation, an assessment of both accidents was undertaken (B A Llewellyn, November 2001). That report suggested, among other things, that the fuselage upper longeron in the area of the cockpits of RV-3 and RV-6 aircraft be strengthened. The writer of the independent report sent copies to the Australian Civil Aviation Safety Authority, as the airworthiness certification authority for Australia and to the aircraft designer.

Factual Information

The owner/builder of the the Vans RV-6A aircraft was conducting a flight from Townsville to Toowoomba. The aircraft departed Townsville at 0846 local time. The pilot subsequently contacted Oakey Approach at 1324, and the aircraft was identified on radar at 3500 feet. The pilot was instructed to maintain that altitude. When the aircraft was about 26 nautical miles from Toowoomba, the pilot transmitted a mayday distress message stating that the aircraft's engine had failed. A short time later he reported that a propeller blade had failed. No further transmissions were heard from the aircraft. About 30 minutes later, a searching helicopter located the wreckage in a flat clear area amongst hilly, tree covered terrain.

The area apparently chosen by the pilot for an emergency landing was about 300 m long and relatively flat. There were trees under the likely approach path of the aircraft and rising ground at the far end. The surrounding hills were above the level of the landing area.

Examination at the accident site revealed that the aircraft struck the ground while banked about 90 degrees left, and descending at an angle of about 34 degrees. A 200 mm section of one propeller blade tip had broken off and could not be located at the accident site. Witness marks indicated that the propeller was rotating under power when the blades contacted the ground. Aside from the broken tip, the propeller blades were in good condition. No other faults were found that might have prevented the aircraft from operating normally.

During the impact sequence, the section of the fuselage forward of the pilot's seat was deflected upward relative to the rear fuselage. The cockpit sides had buckled outwards. That resulted in the pilot striking the instrument panel, even though his shoulder harness remained fastened.

Aircraft information

The pilot purchased the aircraft in 1996 and he first flew it in 1998. At the time of the accident, the aircraft had accumulated 383 hours time in service.

The pilot fitted a new engine and propeller to the aircraft during construction. The engine was modified to improve and balance the airflow through the valves of each cylinder to enhance engine performance. In an apparent further attempt to improve engine performance, the pilot replaced one magneto with an electronic ignition system that was capable of varying the ignition timing in response to changes in engine RPM and manifold pressure. That variation contrasted with the fixed timing ignition provided by the other "standard" magneto fitted to the engine.

The aircraft's wing was a constant chord, low aspect ratio wing. A characteristic of low aspect ratio wings is high induced drag at low speed. Unless the pilot controls the speed carefully, the effect on aircraft performance can be a rapid speed loss and a high rate of descent. If such a situation arose during an approach to land, the only means of regaining speed and arresting the rate of descent would be to increase engine power. If little or no engine power was available, the outcome could range from a heavy landing to a loss of control of the aircraft.

Examination of the failed propeller blade

A fatigue crack had initiated near the leading edge of the blade 216 mm from the blade tip. Crack growth had occurred as a result of alternating thrust loads, and had propagated along the thrust face (rear surface) of the blade. The characteristics of the crack indicated that it had grown under constant amplitude loading. There was no evidence of flight by flight striations. The propeller material was of the correct type and no damage or other reason for the crack to initiate was found.

All propellers are subject to alternating thrust loads during normal operation. Propellers are designed so that those loads will not exceed the design value, thus preventing the development of fatigue cracks during operation. The firing of each cylinder in a reciprocating engine produces torsional vibrations. That means that the crankshaft momentarily speeds up at each firing stroke, and then slows down again prior to the next firing stroke. The vibration leads to alternating thrust loads in the propeller.

Examination of the engine connecting rod big-end bearings revealed distress on the bearing surfaces. That distress was indicative of firing loads exceeding the designed capacity of the bearing lubrication. For optimum operation of spark ignition engines, the peak pressure developed by the combustion of the fuel air mixture should occur approximately 15 degrees after the crank has located past top centre.

Ignition timing was a critical factor, influencing engine power, fuel economy, and the operating condition of the engine. Timing depended on the rate of propagation of the flame front through the fuel-air mixture. Increased or advanced ignition timing resulted in increased combustion chamber pressures. Magneto timing was fixed and was optimised for the operating range of the engine. If the response of the electronic ignition system to reductions in manifold pressure created by part throttle opening was to advance the timing of ignition, that could increase cylinder head pressures and increase the magnitude of torsional vibration.

Pilot information

The pilot, aged 64, held a New Zealand Private Pilot Licence and a current Class 2 Medical Certificate. The medical certificate was subject to three restrictions; the pilot was required to wear spectacles, he was granted an exemption regarding his hearing standard, and he was subject to a restriction regarding a drug he was taking for tinnitus (a ringing or similar sensation in the ears, due to disease of the auditory nerve).

The post-mortem examination of the pilot revealed that he had previously suffered at least one myocardial infarction and had coronary artery disease. Specialist examination of the pilot's electrocardiogram traces over a number of years did not reveal any pre-existing signs of a heart problem. Specialist medical opinion was that the possibility of the pilot suffering a heart attack induced by high stress levels after the propeller failed could not be excluded.

According to the pilot's logbook, he had a total flying experience of 1,179.6 hours at the time of the accident, of which 1,109.9 hours were in command. He had 383.2 hours on the accident aircraft, all of which were in command. On the day before the accident, the pilot had flown the aircraft from Auckland, New Zealand to Townsville, Queensland. That flight took 13 hours.

Analysis

The evidence indicated that the flight proceeded normally until the propeller failed. The pilot correctly diagnosed the nature of the problem and appeared to have been attempting an emergency landing when the accident occurred. It is possible that, with little effective power being available from the engine, the aircraft entered a low speed/high rate of descent situation during the final landing approach. Any yaw existing at the time could have been sufficient to cause the aircraft to roll left or right. The impact dynamics were consistent with such a sequence.

It is possible that vibration caused by the out-of-balance propeller limited the pilot's ability to accurately interpret the aircraft instruments, including the airspeed indicator. Such a situation might have affected his control of the airspeed during the final approach to the landing area and may have contributed to the loss of control.

The distortion to the cockpit sides was very similar to the damage sustained in a fatal accident involving an RV-3 aircraft on 12 March 2000 (ATSB Occurrence Brief 200000885). Both aircraft were originally designed under US Federal Aviation Regulation Part 121-191 (experimental - amateur). As such, they were not required to meet any design standard.

The degree to which the pilot's medical conditions may have affected the final outcome could not be established.

The investigation was unable to determine the factors leading to the accident, other than the failure of the propeller blade.

Summary

The owner/builder of the Vans RV-6A aircraft was conducting a flight from Townsville to Toowoomba. The aircraft departed Townsville at 0846 local time. The pilot subsequently contacted Oakey Approach at 1324, and the aircraft was identified on radar at 3500 feet. The pilot was instructed to maintain that altitude. When the aircraft was about 26 nautical miles from Toowoomba, the pilot transmitted a mayday distress message stating that the aircraft's engine had failed. A short time later he reported that a propeller blade had failed. No further transmissions were heard from the aircraft. About 30 minutes later, a searching helicopter located the wreckage in a flat clear area amongst hilly, tree covered terrain.

Occurrence summary

Investigation number 200005572
Occurrence date 24/11/2000
Location 53 km NE Oakey, Aero.
State Queensland
Report release date 24/06/2002
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 Amateur Built Aircraft
Model Vans RV-6
Registration ZK-VBC
Serial number 24625
Sector Piston
Operation type Private
Departure point Townsville, QLD
Destination Toowoomba, QLD
Damage Destroyed

British Aerospace Plc BAe 146-300, VH-EWR

Summary

The BAe146 and the SAAB 340B were on converging tracks. The air traffic controller responsible for their separation received an electronically generated Short Term Conflict Alert (STCA) on his display. The STCA was a warning to the controller that the predicted radar paths of the two aircraft may lead to a loss of separation standards. The required separation standard was 5 NM laterally or 1,000 ft vertically. By the time the controller took positive control and instructed the crew of the BAe146 to turn left for avoiding action, lateral separation had reduced to below the required standard. The crew of the SAAB received a Traffic Alert from their aircraft's traffic alert and collision avoidance system (TCAS).

Analysis of the radar data indicated that lateral separation between the two aircraft reduced to 2.4 NM and vertical separation to 500 ft. The controller did not use any separation assurance technique in his traffic management plan. He stated that he was used to working in a much busier air traffic environment: circumstances that would demand closer vigilance. At the time of the conflict, the controller was distracted from his primary task of providing a radar control service during a discussion with a TAAATS Flight Data Corrections (TFDC) officer over a minor administrative issue.

Occurrence summary

Investigation number 200005295
Occurrence date 11/11/2000
Location West Maitland, (VOR)
State New South Wales
Report release date 25/07/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of separation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer British Aerospace
Model BAe 146
Registration VH-EWR
Serial number E3195
Sector Jet
Operation type Air Transport High Capacity
Departure point Sydney NSW
Destination Brisbane, QLD
Damage Nil

Aircraft details

Manufacturer Saab Aircraft Co.
Model 340
Registration VH-OLN
Serial number 207
Sector Turboprop
Operation type Air Transport Low Capacity
Departure point Coffs Harbour, NSW
Destination Sydney, NSW
Damage Nil

Cessna 404, VH-SKW

Summary

A Cessna 404 Titan aircraft was being operated on a scheduled passenger service from Cairns to Aurukun.

At 1116 EST, the crew reported to Brisbane Air Traffic Control that they were holding overhead Aurukun with an unsafe landing gear indication. At about 1212 EST, the crew advised ATC that they intended to land at Aurukun. The aircraft's nose landing gear collapsed soon after contacting the runway during the landing roll. The aircraft sustained significant impact damage to both propellers and the nose landing gear, and abrasion damage to the forward underside of the fuselage. There were no injuries.

The pilot later reported that the flight had proceeded normally until about 200 feet above ground level during approach to land when he noticed the red landing-gear unlocked light illuminate. All three green landing-gear down lights were also illuminated. The crew conducted a missed approach and then held overhead the runway while assessing the problem, and to reduce the fuel load. They found that the landing-gear circuit breaker had tripped. The crew reset the circuit breaker, but it tripped again immediately. They then attempted to extend the landing-gear using the emergency system but were unsuccessful.

The landing gear system was examined by company engineering personnel, who informed the ATSB that they found that electrical arcing had occurred across multiple terminals in the cannon plug connector located at the bulkhead of the nose-wheel well. Several of the terminals had fused together, causing the erroneous landing gear position indications. The most likely reason for the arcing was the ingress of moisture. The emergency extension system operated normally when tested by maintenance personnel who advised that the crew had probably not operated the emergency extension system correctly.

The ATSB did not conduct an on-site investigation of this accident. All information relating to the accident was obtained from the flight crew and company engineering personnel.

Occurrence summary

Investigation number 200005212
Occurrence date 08/11/2000
Location Aurukun, (ALA)
State Queensland
Report release date 22/05/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Wheels up landing
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer Cessna Aircraft Company
Model 404
Registration VH-SKW
Serial number 4040042
Sector Piston
Operation type Air Transport Low Capacity
Departure point Cairns, QLD
Destination Aurukun, QLD
Damage Substantial

Boeing 747-400, VH-ANA

Summary

The pilot in command of the Boeing 747 reported that while cruising at flight level 380 the aircraft encountered clear air turbulence. Although the weather forecast indicated active thunderstorms within 110 NM of the track being flown, turbulence was not forecast nor was there any indication, either visually or via the radar, that turbulence was imminent. The seat belt sign was not illuminated at the time, nor was it required to be illuminated.

Cabin crew reported that a passenger sustained a suspected broken ankle while exiting a lavatory. Another passenger, who was waiting to enter a lavatory, sustained a suspected sprained ankle. There were no other reports of injuries.

Occurrence summary

Investigation number 200005031
Occurrence date 27/10/2000
Location 796 km S Guam, Aero.
State International
Report release date 28/05/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Accident
Highest injury level Serious

Aircraft details

Manufacturer The Boeing Company
Model 747
Registration VH-ANA
Serial number 24062
Sector Jet
Operation type Air Transport High Capacity
Departure point Sydney, NSW
Destination Osaka, JAPAN
Damage Nil

Beech Aircraft Corp A36, VH-EUB

Summary

The pilot of the Beechcraft Bonanza was conducting a Global Positioning System (GPS) instrument approach into Lilydale from waypoint "charlie" which was located 15 NM north of Lilydale. As the pilot approached waypoint "India", a position 5 NM south of "charlie", the controller advised the pilot that he was two and a half miles east of "charlie". When the pilot advised that he was just passing waypoint "india", the controller responded that he was not and that he was, in fact, two and a half miles east of "charlie".

The pilot decided not to follow the controller's information and conducted a missed approach. Just as the pilot commenced the missed approach procedure, he became visual and was able to visually establish that his position was accurate and, as he expected, on the GPS approach track. The pilot continued the approach visually.

The pilot later reported that he had checked all of the available information and had verified that he was tracking via the correct GPS track. When the controller advised him that he was 2.5 NM east of "charlie" the GPS indications were within 0.13 NM of waypoint "india". The pilot reported that he checked the GPS function with an accompanying pilot and found no error.

The investigation revealed that the controller had never seen this approach being flown in instrument meteorological conditions before. In an attempt to educate himself about the Lilydale GPS approach, the controller used the bearing and range line to graphically display the last two positions of the approach on the air situation display. The controller misread the approach plate and displayed incorrect waypoints on the air situation display. The controller used this incorrect display to provide positional information to the pilot.

Following this occurrence, Airservices Australia developed an electronic selectable map, based on verified data, available on the air situation display to display all of the waypoints associated with the Lilydale, Moorabbin and Avalon GPS approaches.

Occurrence summary

Investigation number 200004914
Occurrence date 26/10/2000
Location Lilydale, (ALA)
State Victoria
Report release date 03/08/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category ANSP info/procedural error
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Beech Aircraft Corp
Model 36
Registration VH-EUB
Serial number E-251
Sector Piston
Operation type Business
Departure point Shepparton, VIC
Destination Lilydale, VIC
Damage Nil

Airbus A340-300, B-2380

Summary

The Airbus A340-300 was on a flight from Shanghai (Pudong International Airport) to Sydney (Kingsford-Smith) Airport. The co-pilot was the handling pilot. During the flight, the crew observed there was low fluid quantity in the Green hydraulic system and they witched off the Green system engine-driven and electric pumps. As the Airbus was manoeuvred for the approach to runway 16R at Sydney, the crew extended the landing gear by gravity extension. The crew reported that the landing was normal, and that engines number 2 and 3 thrust reverses were deployed after touchdown. Directional control was maintained with rudder, however, as the aircraft was decelerated through approximately 30 kts, directional control was suddenly lost. He applied full manual braking, but the aircraft was yawed rapidly to the right, and came to rest on a heading of approximately 280T, which was about 120 degrees off runway heading. The main landing gear wheels remained on the sealed surface of the runway, however, the nose wheels were on the grasses area adjacent to the runway, approximately 16 m beyond the runway edge. None of the passengers or crew was injured.

The investigation revealed that a crack in the number one engine EDP case led to the loss of the Green system hydraulic fluid. However, this was not a factor contributing to the final loss of directional control of the aircraft. The flight data revealed that the engine number one thrust lever was inadvertently advanced after the pilot in command took control of the aircraft. The rapid manner in which it was advanced, suggests there may have been some confusion between the pilot in command and the co-pilot at the time of the takeover of control. In the process of taking control, it is likely that the pilot in command placed his right hand on the thrust levers before the co-pilot could completely relinquish his control of them, and that the subsequent advancement of thrust lever number one was a result of this confusion. As the aircraft began to veer rapidly tot eh right, the crew's attention was substantially diverted by the unexpected and sudden loss of control of the aircraft. with their attention so diverted, none of the crew would have been initially aware of the engine number one thrust lever position, and that the engine was delivering substantial asymmetric thrust that contributed to the loss of control.

Occurrence summary

Investigation number 200005030
Occurrence date 01/11/2000
Location Sydney, Aero.
State New South Wales
Report release date 07/11/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Runway excursion
Occurrence class Serious Incident
Highest injury level None

Aircraft details

Manufacturer Airbus
Model A340
Registration B-2380
Serial number CES561
Sector Jet
Operation type Air Transport High Capacity
Departure point Pudong Shanghai
Destination Sydney, NSW
Damage Minor