Cessna 210N, VH-LMX

Safety Action

Verification of the actual fuel quantity during pre-flight inspection would have alerted the pilot to the amended state of fuel quantity on board the accident aircraft. CASA produced an Advisory Circular in September 2001 on fuel planning as guidance for operators and pilots to help ensure correct pre-flight planning procedures and that aircraft carry sufficient fuel to safely complete each flight.

The fitment of upper body restraints to the passenger seat belt systems may have reduced the exposure to some of the serious injuries incurred in this accident. Recommendation R19980281 arising from occurrence 199802830, dated 26 July 1998, was previously made to CASA to address this perceived deficiency with regard to upper body restraints. In response to this recommendation, CASA issued a Discussion Paper `Proposed Airworthiness Directive, General Series - Upper Torso Restraints for Occupants in Small Aircraft' explaining the intention to introduce such a requirement and inviting comment by the industry. The public comment period closed 01 March 2002 and CASA is now considering these comments prior to promulgation of the AD.

The Bureau's response to that action was RESPONSE STATUS: MONITOR. The ATSB will continue to monitor the CASA action and any further correspondence will be published on the ATSB website www.atsb.gov.au.

Analysis

Fuel quantity calibration and indication

Although the aircraft fuel gauges differed between left and right tanks for a given scale marking, this was compensated for by having a calibration correction card fitted to the aircraft. It is not uncommon to have such discrepancies between multiple gauges in the same aircraft and should not have been a factor in this accident.

As a back up measure the aircraft also carried a dipstick, which was usually locally manufactured by the maintenance organisation. It could be used by the pilot to verify the actual fuel quantity on board before or between flights. The dipstick found at the crash site, although not calibrated specifically for the accident aircraft, should have given a reliable enough reading to alert the pilot to the 80L discrepancy in the fuel quantity on board; if it had been used. Passengers did not see the pilot verify the fuel quantities at Rawlinna, either visually or by using the dipstick. It could not be determined if the pilot verified the actual fuel quantity on board, visually or by dipstick prior to departing Kalgoorlie but, considering the incorrect trip log annotation of 160L in each tank, it is unlikely that he did.

The fuel that rescuers observed leaking onto the front seat occupant and which had pooled under the aircraft, probably came from the disrupted fuel lines around the fuel tank selector in the first instance and later augmented by the right door pillar supply line from the right tank that was severed during the rescue. As the residual fuel in the left tank was not able to feed to the fuel selector supply lines, the fuel remaining in the left tank only approximated to the unusable amount, as published in the POH, for that tank.

The selected position of the yellow segment of the auxiliary fuel pump switch as observed at the accident site, was consistent with emergency checklist action following an inflight engine power loss or vapour purge.

The fuel selector was found selected to the right tank. The fuel pump switch and fuel selector position observations were considered in conjunction with the pilot's trip log notes showing that the flight immediately prior to the power loss was conducted on the left tank. If the pilot had conducted the emergency checklist actions, as seems likely based on the auxiliary fuel pump switch selection, then he had selected the fuel selector to the opposite tank. The evidence was consistent with a power loss while operating from the left fuel tank and a probable attempted engine re-start after changing fuel tank selection to the right tank.

In flight engine restart

The radio call made by the pilot gave the aircraft height of about 800ft above ground level (AGL) at the time the engine lost power. This would have provided gliding time of approximately one minute in the flaps up configuration recommended by the POH; and used by the pilot. This short interval after the engine power loss may have been insufficient for the pilot to successfully complete an in-flight engine re-start drill.

Fuel tank exhaustion - fuel supply starvation

The aircraft fuel usage annotations recorded in the trip fuel log by the pilot showed that he had started his fuel calculations with 80L more fuel than was on-board. The annotations also showed that the left tank had been used for taxi and take off on both flight sectors that day. Take-offs were the periods of highest fuel demand by the engine and in accordance with the POH, should have been conducted from the fullest tank. The trip fuel log showed that, on departure from Rawlinna, the right tank contained the most fuel and, therefore, should have been used for that take off.

Whether prolonged taxi or extended use of climb power using the left tank took place could not be verified and the possibility of additional fuel usage from the left tank during these periods could not be ruled out.

The pilot's fuel usage annotations showed that he calculated the aircraft had used approximately 69L from the left tank and 70L from the right tank in total for both sectors that day, up to the last hand written entry for the fuel tank selection change at 1345. Using the operator's average fuel consumption figure for this aircraft, a further 28L needed to be used from the left tank by the time that the engine lost power; approximately 1413. If the tank selections were correctly carried out as annotated by the pilot, the total fuel burn from the left tank would have been around 97L, which should have left approximately 23L remaining in that tank. The tank was observed, at the accident site, to contain approximately half a litre of (unusable) fuel. It could not be positively determined why only unusable fuel remained in the left fuel tank.

The previous accident in 1995 demonstrated, that on at least one other occasion, this aircraft's left fuel tank contents could be exhausted after one hour and 40 minutes of operation from a `tabs level' fuel quantity. Flight time of the Kalgoorlie accident flight, while operating on fuel supplied only from the left tank, was estimated to have totalled approximately one hour and 37 minutes. It was therefore possible that the contents of the left tank may have also been exhausted on the Kalgoorlie, Rawlinna, Kalgoorlie flight in this period of time.

Operations with low-fuel quantity

The trip fuel log revealed that the pilot would have expected to have 40L more fuel remaining in each tank at the time the engine lost power. Consequently, he may not have considered a low fuel state as a possible cause for the engine power loss.

Flying in turbulence with a low fuel state can also lead to uncovering of the fuel outlets in the fuel tanks. If the pilot had correctly carried out the tank changes noted in the trip log, the left tank should have had approximately 23L of fuel remaining when the engine lost power; which equated to about an eighth of a tank. If such a quantity was present in the reported turbulent conditions, then the possibility of unporting the fuel outlets could not be ruled out.

Summary

The low fuel-state of the left tank alone, or in combination with the forecast turbulence, probably caused the engine to lose power.

In the absence of evidence of a mechanical failure leading to engine loss of power, the most likely cause of the engine loss of power was associated with fuel supply starvation or exhaustion.

The presence of a vehicle on the road appeared to have caused the pilot to initiate a sudden pull back on the flight controls that led to a loss of control and subsequent impact with the ground.

Factual Information

The pilot of a Cessna 210 Centurion was tasked to fly three passengers from Kalgoorlie WA to Rawlinna WA and return.

The aircraft departed Kalgoorlie at 0804 Western Standard Time for Rawlinna with the flight proceeding without incident. The trip fuel log showed that the pilot believed that the aircraft arrived in Rawlinna with approximately 106L remaining in the left tank and 130L remaining in the right tank. The aircraft was not refuelled at Rawlinna.

Two passengers watched the pilot prepare for the return journey from Rawlinna. They reported that the pilot appeared to do a walk around the aircraft and one passenger stated that although he saw the pilot `check things at the front, wingtips and tail', the pilot did not check the fuel tanks in the wings. At approximately 1250, the flight departed for Kalgoorlie. One of the passengers recalled that, shortly after reaching a cruise altitude of about 4,000ft, the pilot appeared to become agitated and was checking something on the floor between the seats. This concerned the passenger, but after a few minutes, the pilot settled down and the passenger assumed that whatever had been a concern, was resolved. The fuel selector is located on the floor between the two front seats.

One passenger with recollection of the remainder of the flight from Rawlinna, stated that it appeared routine up until the engine lost power while the aircraft was approaching Kalgoorlie. (Due to the serious nature of the head injuries sustained in the accident by all of the passengers, their recollections of the flight prior to the engine power loss were very fragmented.)

At approximately 1413, the pilot was heard to broadcast a distress call including the aircraft altitude of 2,000 ft above sea level and his intention to land on a road. During the landing attempt, the passenger in the right front seat observed a car appear in the landing path. The passenger reports of what occurred after the car appeared were consistent with the pilot attempting to climb the aircraft to avoid the car and subsequently losing control of the aircraft during the manoeuvre.

The driver of the car and his wife saw the aircraft pass silently overhead as it crossed the road in a southerly direction. When it impacted the ground, the car driver's wife said that it appeared to `really bury in' before it was obscured by a large cloud of dust.

The driver immediately called emergency services and then he and his wife attempted to render assistance to the occupants. The pilot was fatally injured while the passengers were seriously injured.

Wreckage information

The aircraft impacted the ground in a left wing low, nose-down attitude. Examination of the aircraft found the left and right fuel tanks intact, but the fuel system plumbing was disrupted by cabin distortion at the fuel tank selector valve under the floor. The fuel line to the firewall mounted filter strainer and engine was broken and the strainer was destroyed during the accident impact sequence. The forward door pillar had been severed on the right side of the aircraft by hydraulic cutters used during the rescue effort to free the trapped front seat passenger. The examination of the fuel tank selector revealed that the right fuel tank was selected at impact.

Fuel had poured on to the right front seat occupant during the rescue and had continued for a considerable amount of time after the accident. No fuel remained in the right tank when it was examined by the investigation team on site. The rescuers said that they had not observed fuel to leak from the left wing onto the ground at any time. The aircraft's left wing low attitude uncovered the engine fuel supply lines at the inboard end of the tank and, as a result prevented the remaining left tank contents escaping through the damaged connections to the fuel selector. Less than half a litre of clean fuel remained in the outboard section (lowest point) of the left tank compartment and was considered to approximate the unusable amount for the tank. A sample of the Avgas, which was normal green colour, was taken from the aircraft and inspected at the accident site. It was free of any water or particles in suspension and visible contaminants. The fuel uplift for the flight was from the Kalgoorlie aerodrome. This fuel supply was tested by the supplier and found to be within correct specification.

The left-wing vent line was also clear of the remaining contents and did not appear to have been capable of allowing the remaining contents to drain off through the left-wing tip vent due to the syphon effect. The fuel contractor's log showed that there were multiple deliveries from the same batch of fuel to other aircraft operating from Kalgoorlie airport coincident with the delivery to VH-LMX. The bureau found no reports of fuel related problems with any of these other aircraft.

The fuel system components were bench tested and found to be capable of normal operation within the manufacturer's parameters. The wreckage, engine and component examinations found no evidence of pre-existing mechanical defects with the aircraft or its systems, that would have prevented normal operation of the aircraft prior to the accident.

Fuel pump switch

The auxiliary fuel pump switch is a two-segment split rocker type mechanism. The right half was colour-coded yellow and the left half red. The yellow half was marked START, with the upper position as ON and was used for normal start and some minor vapour purging if required. It was usually selected OFF for normal flight. In the event of an engine driven fuel pump failure in cruise flight, the yellow switch selected to ON should have provided, through a micro-switch arrangement, sufficient fuel for normal engine operation. The red half of the switch was marked EMERG (emergency) with its upper position marked as HI. This red switch was used in the event of an engine driven fuel pump failure during take-off or high-power operation and also extreme vapour purging. When the auxiliary fuel pump switch was removed and examined the yellow segment was found in the ON position.

A fuel dipstick with graduated markings on it was found in the baggage compartment of the aircraft. It was marked C210M VH-WXC and had the following graduations: LEFT FULL, 140, 100, 60, 30 with identical graduations and the word RIGHT on the reverse side of the stick. A check of the type certificate data sheet revealed that the C210N (accident aircraft) was fitted with identical type and capacity fuel tanks to the C210M.

Emergency locator transmitter

The aircraft was fitted with an emergency locator transmitter that activated upon impact. The transmission was received and logged by the Australian search and rescue organisation (AUSSAR) for 2hrs 39 mins before local police disabled the transmitter.

Pilot information

The pilot held a valid Australian commercial pilot licence and command instrument rating. He held a valid Class 1 medical certificate and did not require vision correction while operating an aircraft. At the time of the accident the pilot had accrued a total of 1,087 hours flying experience with 317.5 hours on the Cessna 210. From interviews and postmortem results, no evidence was found that the pilot had any personal or medical problems that may have adversely impinged on his ability to conduct the flight.

Survival

The nose-down, left wing low attitude of the aircraft as it impacted the ground exposed the left front seat occupant (the pilot) to the full force of the impact.

The passengers sustained numerous serious injuries in the form of fractures to legs, upper bodies and heads as well as injuries to internal organs. The leg injuries probably occurred when the floor was forced in an upward direction during the impact sequence. The floor movement also released the anchor points for the front seats. The middle row right seat remained fixed to its mounts. The middle left seat remained fixed by its rear mounts and forward left mount but with the front right mount partially released. There were no upper body restraint systems fitted to the passenger seat row positions in the aircraft, nor were any required to be. The upper body and head injuries sustained by all occupants were probably due to upper torso flailing contact with interior structure and objects. The front seat positions were fitted with upper body restraints. The effectiveness of the front seat restraint systems was compromised by the loss of integrity of the seat to floor attachments. The rearward movement of the engine firewall during the impact sequence may also have reduced the front seat survival space between front seat occupants and control panel structures; which would have increased exposure to injury.

Weather

The weather forecast for the day was for fine conditions, but with thunderstorm activity expected in the Kalgoorlie area during the afternoon after the flight. Other pilots reported experiencing some heavy turbulence in the area during the day and the operator's Chief Pilot remarked it was, `the first really rough day of the season'. The passengers recalled that, for the portions of the flight that they could remember, there was some turbulence but remarked that it was not unusually rough.

Aircraft fuelling

The afternoon before the charter flight, the aircraft operator requested the fuel contractor to fill the aircraft tanks (capacity 160L in each of two tanks) `to the tabs', which equated to a fuel quantity of approximately 120L in each fuel tank. The fuel request form was normally faxed to the fuel depot during the afternoon, but as no request had been received by the time he was due to commence fuelling tasks, the fuel contractor obtained the request sheet by walking to the aircraft operator's office and retrieving the original. The contractor noted that the sheet had been amended by the use of white-out correction fluid and that the original request entered had been for full tanks. It could not be positively determined if the pilot had sighted this fuel quantity request sheet.

Company pre-flight briefing

Some months after the accident, a director of the company stated that he spoke to the pilot in the afternoon prior to the accident flight. This conversation covered the task briefing for the following day and included the fuel load as being `to the tabs'. If this was so, the weight and balance calculations made by the pilot for the flight, in which a `full fuel' quantity was used and showed that the aircraft was close to maximum take-off weight, did not reflect any knowledge that he had received the `fill to tabs' fuel information. The director could not confirm whether the pilot assimilated this information at the time he talked to him.

Aircraft service history

The aircraft had been maintained in accordance with the relevant Civil Aviation Regulations and Orders. The aircraft had a valid maintenance release at the time of the accident with no maintenance overdue. Because a fuel quantity system calibration was required by the Civil Aviation Safety Authority (CASA) every three years as part of an airworthiness directive (AD), a calibration had been carried out six months prior to the accident in accordance with the AD. The gauge calibration results recorded in the aircraft logbook were as follows:

Left 10/46, 20/83, 30/117, 40/167, F/169 (Gallons/Litres)
Right 10/38, 20/65, 30/100, 40/145, F/164 (Gallons/Litres)

The aircraft fuel gauges, calibrated in US Gallons, were within the required parameters but the quantities differed between the left and right tanks for a given scale marking. This was compensated for by having a calibration correction card fitted to the aircraft. The calibration recordings in the logbook did not include a value for E (empty). However, the calibration card fitted to the aircraft stated that for E indication on the gauge, the tanks were to be read as empty.

A review of the aircraft's history revealed that, when being operated by its previous owner on the east coast, it had been involved in a similar accident in 1995 when it was force landed due to engine power loss. The aircraft had also taken off with the fuel tanks filled `to the tabs', and on that occasion it was estimated that the pilot had operated the aircraft for approximately 1 hour and 40 minutes when the engine lost power. The left fuel tank was used for the entire flight and when examined at the accident site, it was found to be empty.

Flight trip log

A company trip fuel log for the flight was found at the accident site. This log was being used by the pilot to record flight times and fuel usage from each tank for the flight. It had the following annotations:

PlaceTimeLeftRight
KG0804160160

 
34130160

 
04130130
RAW0928106130
RAW1250106130

 
0591130

 
13459190

The trip fuel log noted that the fuel tanks contained 160L in each tank on departure from Kalgoorlie.

The take-off from Kalgoorlie had been conducted using fuel from the left tank. The trip fuel log indicated that the aircraft had consumed 54 litres from the left tank and 30 litres from the right tank during the flight to Rawlina. Additionally, the log indicated that the pilot elected to remain on the left tank for the taxi, pre-take-off checks, take-off and departure from Rawlinna thereby carrying out both take-offs using fuel from the left tank. The pilot recorded an initial use of 15L from the left tank on departure from Rawlinna, followed by 40L from the right. At 13:45 WST he changed the selection to the left tank. About 28 minutes later, the engine lost power.

Pilots Operating Handbook (POH)

The aircraft was fitted with a placard that provided information in the form of a checklist in the event of major fuel flow fluctuations and/or engine power surges. Additionally, the POH provided expanded procedures for inflight engine restarts and excessive fuel vapour in the fuel system. The POH also noted that if the propeller is windmilling, the engine will start automatically within a few seconds. If the propeller has stopped (possible at lower speeds), turn the ignition switch to START, advance the throttle slowly from idle, and (at higher altitudes) lean mixture from full rich.

The POH went on to indicate that with fuel quantities of less than a quarter tank, prolonged uncoordinated turns or slips should be avoided as it might uncover the fuel tank supply outlets and starve the engine of fuel.

Engine out glide distance

The MAYDAY transmission made by the pilot placed the aircraft at a height of 800 ft above ground level. This height, according to the Maximum Glide graph in the POH, equated to approximately 1.2 NM, or approximately one minute of glide time from the time at which the engine lost power to the impact point.

Occurrence summary

Investigation number 200105446
Occurrence date 14/11/2001
Location 10.7 km ESE Kalgoorlie/Boulder, Aero.
State Western Australia
Report release date 16/09/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model 210
Registration VH-LMX
Serial number 21063509
Sector Piston
Operation type Charter
Departure point Rawlinna, WA
Destination Kalgoorlie, WA
Damage Destroyed

Boeing 747SP-38, VH-EAA

Summary

A Boeing 747-SP38 aircraft was maintaining Flight Level (FL) 430 with autopilot `A' engaged, when the aircraft yawed abruptly to the right and rolled to a bank angle of approximately 20 degrees. The autopilot was disengaged and the aircraft stabilised in a straight and level attitude. The uncommanded yaw occurred again. The flight crew broadcast a PAN (radio code indicating uncertainty or alert, not yet the level of a Mayday) and received a descent authorisation to FL380.

The upper rudder position indicator showed a rudder displacement of 5-degrees right and the lower rudder indicator showed zero degrees deflection. The flight crew began activating and de-activating the upper and lower yaw damper switches attempting to isolate the problem. During those actions, the aircraft commenced to `Dutch roll' (lateral oscillations with both rolling and yawing components). The crew then successfully isolated the problem to the upper damper and turned the upper damper switch off. With the aircraft at FL380, normal operations ensued. Autopilot `B' was then engaged and the flight proceeded without further incident.

Investigation by company maintenance personnel confirmed an anomaly of the upper yaw damper computer. The unit was replaced and the system tested. Normal operations ensued.

Analysis of Flight Data Recorder information revealed that during the event the upper rudder displaced 4.7 degrees. The data also indicated that the maximum roll encountered was 13 degrees to the right.

System redundancy had operated as required to limit the effect of the upper yaw damper anomaly.

Occurrence summary

Investigation number 200105429
Occurrence date 13/11/2001
Location Abeam Moomba
Report release date 25/03/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Flight control systems
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 747
Registration VH-EAA
Serial number 22495
Sector Jet
Operation type Air Transport High Capacity
Departure point SINGAPORE
Destination Sydney, NSW
Damage Nil

Boeing Co 767-300ER, VH-BZI

Summary

The crew of a Boeing 767 (B767) had been cleared to taxi for departure from runway 01, intersection "A7", at Brisbane. They proceeded along taxiway "B" then, incorrectly, initiated a turn onto taxiways "B5" and "A", which was in conflict with rapid exit taxiway "A5S". A BAe146 vacating runway 01 via "A5S", was instructed by ATC to hold short of taxiway "A" in order to avoid the B767. The crew of the BAe146, although not expecting to have to hold short of that taxiway intersection, had reduced speed to an extent that they were able to comply with the instruction.

The operator of the B767 advised that they had tried a new system of printing aerodrome charts from a computer application compact disk. However, the print format was such that the pilot in command of the B767 was not able to correctly read the notes provided on the chart with respect to taxiway routes and directions.

Safety Action

As a result of the occurrence, the B767 operator immediately replaced the aerodrome charts in the applicable aircraft with charts printed in a larger format. In addition, a briefing note was issued to crews in order to highlight the problem and to minimise the likelihood of a recurrence.

Occurrence summary

Investigation number 200105351
Occurrence date 04/11/2001
Location Brisbane, Aero.
Report release date 04/02/2002
Report status Final
Investigation type External Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 767
Registration VH-BZI
Operation type Air Transport High Capacity
Departure point Brisbane, QLD
Destination Sydney, NSW
Damage Nil

Aircraft details

Manufacturer British Aerospace
Model BAe 146
Registration VH-YAD
Serial number E2097
Operation type Air Transport High Capacity
Departure point Canberra, ACT
Destination Brisbane, QLD
Damage Nil

Instrument system event, Boeing 747-400, 9V-SPP, 19 km south-east of Nyngan Airport, on 6 November 2001

Safety Action

Local safety action

As a result of this incident the aircraft and component manufacturers have changed the software for the EIUs and reclassified the IOP #1 fault as a hard3 fault. Further testing was being conducted at the time of this report's release.

___________

[3] A fault that would completely shut down the affected EIU.

Analysis

The on-board recorders showed that the highest cabin altitude captured was 8553 feet with a subsequent continuous decrease in cabin altitude recorded prior to the loss of the system data. The cabin altitude did not reach the required height for supplementary oxygen which was consistent with the reported lack of oxygen flow through the passenger drop masks after they had deployed.

The operation of the pressure relief valve indicated that an over-pressurisation condition had been experienced in the cabin. This was most likely due to the manual closing of the outflow valves by the flight crew while the aircraft was continuing to be pressurised by the controlling CPC. The resultant rate of change of cabin pressure may have contributed to the reported injury sustained by a passenger.

The concern at the lack of oxygen flow through the masks led to some cabin crew moving from their seated position to obtain portable oxygen, or to assist passengers during the emergency descent.

Extensive research has shown that the effect of oxygen deprivation can be insidious and, as such, cabin crew may not be the best judges of their own oxygen intake. Although the cabin altitude may not have been high enough to require supplemental oxygen, that information was not available to the cabin crew at the time. As the cabin crew were unable to accurately judge the aircraft's altitude, remaining seated until advised by the flight crew that a safe altitude had been reached, in accordance with procedures, may have been a safer practice than moving through the cabin to assist passengers and accessing bottled oxygen.

Although the flight crew conducted an appropriate emergency descent, most cabin crew commented that the floor angle in the cabin during the descent seemed less steep than their emergency decompression training had led them to expect. Previous decompression events have shown that cabin floor angles less steep than expected may have led to cabin crew judgement that it was safe to move about the cabin during an emergency descent.

The reason for the loss of the IDUs could not be determined or reproduced during the subsequent testing of system components. The IOP#1 fault found on one of the EIUs, could have led to the blanking of the PIC's primary flight display, but it should not have resulted in the failure of the remaining IDUs. The subsequent IDU blanking incident in January 2003 has resulted in further investigation by the CAAS, the NTSB, the aircraft and EIU manufacturers.

Factual Information

History of the flight

On 6 November 2001, as the Boeing 747-400 aircraft was approaching flight level 360 en-route from Sydney to Singapore, the flight crew observed a CABIN ALT AUTO message and an increase in cabin altitude. The crew carried out the non-normal checklist, which included manually closing the outflow valves and turning off one of the air conditioning packs. However, the cabin altitude continued to rise and could not be controlled. The pilot in command (PIC) decided to conduct an emergency descent. The flight crew donned their oxygen masks and manually deployed the passenger oxygen masks.

As the aircraft commenced descent, one of the flight crew noticed the PIC's primary flight display screen go blank, with its data transferring to the PIC's navigation display screen. At that point a number of messages momentarily flashed onto the centre, Engine Indicating and Crew Alerting System (EICAS) screen, before all the display screens that are referred to as integrated display units (IDUs) blanked. The crew continued the emergency descent using standby instruments for reference, levelling at 10,000ft. The IDU system circuit breakers (CBs) were checked with all CBs found to be in their normal configuration. Manual selection between alternate system controllers was made but the IDUs remained blank.

After the post decompression drill announcement was made to the cabin crew, the PIC was advised that one passenger had sustained an injury in the form of bleeding from the ear. The PIC was also advised that there appeared to be no oxygen flowing through any of the passenger cabin oxygen masks, however this did not seem to have had any ill effect on the passengers. After the PIC cycled the passenger oxygen switch, a momentary surge of oxygen through the passenger masks was observed.

With Melbourne Air Traffic Control Centre providing vectoring assistance and using the standby flight instrumentation, the flight crew returned the aircraft to Sydney. Due to the loss of the display screens monitoring information, dumping of excess fuel was not possible. Information regarding the position of the landing gear or flaps was also not available. On approach to Sydney, the flight crew requested that the tower controller visually confirm that the landing gear was down and after receiving that confirmation, the crew conducted an uneventful, but overweight landing.

An inspection of the aircraft by engineers revealed that a cabin pressure relief valve had operated, indicating that the cabin had been over-pressurised at some stage during the flight. After a number of system CBs were cycled, the flight deck display screens returned to normal operation. An engine ground run and system check was then carried out, but the inflight faults could not be reproduced. The primary components of the aircraft's pressurisation and flight deck display systems were removed for further testing.

Cabin crew survey

The Australian Transport Safety Bureau carried out a survey of the cabin crew, which revealed the following:

Some cabin crew were concerned about the lack of oxygen flow through their masks during the descent and opted to use the emergency bottled oxygen. A number of cabin crew were observed removing their mask and later stated that they "could feel the presence of air" in the cabin. Some cabin crew were moving about the cabin during the descent assisting passengers. The majority of the cabin crew described the cabin floor angle as being less steep than their emergency decompression training had led them to expect. There was no evidence that any passengers or cabin crew showed signs of suffering from the effects of decompression sickness.

The operator's decompression drill detailed in the non-normal procedures of the operations manual stated that "When there is a loss of cabin pressure and the cabin altitude exceeds 14,000 feet the oxygen masks will drop. The pre- recorded announcement (where fitted) will start playing automatically".

The cabin crew were then required to immediately "Put on a drop mask as quickly as possible" and "Sit down at nearest available seat and fasten seat belt". The procedure then stated that after the aircraft had levelled off, the cabin crew were to "transfer from drop mask to portable oxygen bottle and mask" and to "assist the passengers".

The procedures also contained supplementary information regarding the symptoms and "effects of decompression sickness". The manual stated that at 10,000 feet cabin altitude, the cabin crew and passengers could experience headaches and fatigue. At 14,000 feet the effect may cause sleepiness, headaches, dizziness, impaired vision, personality changes and cyanosis-bluing of fingernails.

Subsequent occurrences involving this aircraft

On 11 November 2001, the flight crew reported that during climb there were large erratic oscillations of both outflow valves, causing large changes in the cabin altitude. The flight crew reported discomfort to their ears and observed significant rates of change in cabin altitude. The system returned to normal operation when the cabin pressure controller (CPC) was manually selected to position B.

On 16 November 2001, during taxi to the terminal, the flight crew observed the advisory message OUTFLOW VALVE L indicating a failure of the left outflow valve. After a ground test of the CPC was carried out, the message disappeared. During the next flight the message again appeared and again was cleared on completion of a ground test of the CPC.

Subsequent fleet occurrence

On 24 January 2003, all six IDUs blanked on another of the operator's Boeing 747-400 aircraft during a flight from Singapore to Sydney, while at FL350. After discussion with the operator's maintenance control personnel, the flight crew were advised to cycle selected CBs. On reset of the CBs, all the IDUs returned to normal operation and the flight continued on to Sydney. The Civil Aviation Administration of Singapore (CAAS) in conjunction with the United States National Transportation Safety Board (NTSB) are investigating the occurrence.

Component testing

The IDUs and EIUs1 removed after the 6 November flight were subjected to examination and testing by their manufacturers, under the supervision of the NTSB. One of the EIUs was found to have an internal IOP #1 card 'soft'2 fault. This fault should not have led to the IDU failure during the incident flight. No faults were found with the IDUs.

Testing of the pressurisation system components following the initial occurrence did not reveal any faults. After the subsequent flights on 11 and 16 November, further testing was conducted, which revealed that the CPC that had been fitted after the 6 November flight had a faulty pressure sensor that was giving erratic signals. One of the system's relays also displayed evidence of failure. The remaining pressurisation components were considered to be serviceable.

Oxygen system

The aircraft was fitted with two separate oxygen systems; one dedicated flight crew system and one dedicated passenger system. The crew system provided a continuous supply of oxygen to each of the flight deck regulators. Removal of the oxygen mask from the stowage box initiated the flow of oxygen. The passenger system had both manual and automatic deployment. Automatic deployment activated when the cabin altitude reached the "equivalent of 13,250 to 14,250 feet", with manual deployment available at any cabin altitude. This was a free-flow oxygen system with oxygen flow being controlled through flow control units (FCU) located downstream of the oxygen cylinders. During the first few seconds of operation, a surge of oxygen was released to open the panels above the passenger seats, allowing the masks to fall within easy reach of the passengers. The quantity of oxygen supplied was then controlled by altitude compensation mechanisms in the FCUs. The higher the cabin altitude, the greater the flow. Chapter 35-21-00 of the operator's aircraft maintenance manual stated: "Passengers are not required to receive [supplemental] oxygen below 10,000 feet, except for medical reasons".

On-board recorders

Data retrieved from the aircraft's on-board recorders revealed the following:

6:47:22 The first officer's IDUs switched from right to left EIU control, at the same time the pressurisation/air-conditioning system data stopped recording correctly.
6:47:44 The CABIN ALT AUTO message was observed.
6:48:09 The right and left EIU's were recorded as inactive.
6:52:58 Highest cabin altitude was recorded at 8553 feet.
6:54:10 Cabin altitude recorded at 6033 feet.
6:54:15 Numerous systems stopped recording data correctly and the Centre EIU became inactive.

(Note: Times refer to Coordinated Universal Time)

[1] The electronic interface units that transfer data from the electronic flight instrument (EFIS) and engine indicating and crew alerting (EICAS) systems to the IDUs.

[2] A fault that is internally logged but does not result in a complete EIU shut down.

Occurrence summary

Investigation number 200105338
Occurrence date 06/11/2001
Location 19 km SE Nyngan Airport
State New South Wales
Report release date 24/09/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Serious Incident
Highest injury level Minor

Aircraft details

Manufacturer The Boeing Company
Model 747
Registration 9V-SPP
Serial number 28029
Sector Jet
Operation type Air Transport High Capacity
Departure point Sydney, NSW
Destination Changi, SINGAPORE
Damage Nil

Schweizer Aircraft 269CB, VH-AHV, on 2 November 2001

Analysis

The displaced circlip from the upper end on the accelerator pump plunger, discovered during the technical disassembly of the carburettor, would have resulted in insufficient fuel being available to the engine during rapid high power requirements.

The engine logbook documentation did not reveal any maintenance performed to the carburettor since it's last repair and reinstallation. It was unlikely that the circlip had become displaced during the repairs of the carburettor, as bench testing would have revealed the problem.

If the maintenance action of the reversing of the linkage plate had been carried out without removing the top plate of the carburettor, it would have been difficult to verify the continued connectivity of the accelerator linkage and the proper functioning of the accelerator pump mechanism within the carburettor.

The investigation could not conclusively establish the reason for the disconnection of the accelerator pump plunger mechanism.

Summary

The pilot of the Schweitzer 269CB helicopter reported that during cruise on a repositioning ferry flight, the helicopter's engine misfired and then stopped completely so he completed a power off autorotation to a nearby dam wall. The pilot, the sole occupant, received no injuries and the helicopter was not damaged.

Troubleshooting by maintenance personnel isolated the problem to the engine's carburettor. The carburettor was replaced and the engine test run. No other anomalies were noted and the helicopter was flown back to the maintenance base.

A technical disassembly of the Precision Airmotive carburettor, model HA-6, part number 10-6030, serial number 75060303 was initiated. The examination included fuel flow level checks. During the checks, the throttle linkage was exercised through its full range from idle to full power. Throttle operation was smooth and unhindered. Several rapid accelerations were then carried out to observe the operation of the accelerator pump. No fuel was observed to flow from the accelerator pump discharge tube, positioned in the carburettor venturi, during these tests. Further examination revealed that the accelerator pump plunger mechanism was disconnected at the upper circlip attachment point on the plunger.

In addition, the accelerator pump/economiser linkages were found to have severe wear on the cam lobe face corresponding to the full throttle position and on the linkage plate that the camshaft lobe acted upon. The linkage plate also had severe wear on the cam lobe-mating surface and on the opposite non-cam lobe contact surface. That indicated that the plate had been reversed at some point during its operational life.

Carburettor background

At the time of the occurrence, the carburettor had accumulated 1,668.2 hours time in service (TIS). The carburettor had been removed from the engine at 1,154.7 hours TIS for a discrepancy reported as suspected low engine power. The repair documentation noted an air-metering pin adjustment defect. Following readjustment, the carburettor was bench tested and returned to service.

At 794.4 hours TIS, the carburettor had been removed from the engine, for a discrepancy reported as leaking fuel when in the full lean/cut-off position. The repair documentation noted that a new float needle and seat were fitted. The carburettor was bench tested and returned to service.

Occurrence summary

Investigation number 200105273
Occurrence date 02/11/2001
Location 9 km N Mareeba Aero.
State Queensland
Report release date 04/02/2002
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 Schweizer Aircraft Corp
Model 269
Registration VH-AHV
Serial number 0063
Sector Helicopter
Operation type Aerial Work
Departure point Mareeba, QLD
Destination Mareeba, QLD
Damage Nil

Beech Aircraft Corp 200, VH-SWP

Safety Action

ATSB safety action

An Australian Transport Safety Bureau investigation into a Beechcraft King Air 200 depressurisation incident, BO/199902928, issued three recommendations on the subject of cabin alert aural warning systems. The final report contained an additional recommendation on the same subject. Recommendation R20000288 stated:

"The ATSB therefore recommends that CASA mandate the fitment of aural warnings to operate in conjunction with the cabin altitude alert warning systems on all Beechcraft Super King Air and other applicable aircraft".

The Civil Aviation Safety Authority's response dated 2 February 2001 stated:

"The Civil Aviation Safety Authority accepts this recommendation and will move to prepare a regulatory amendment to make it mandatory for pressurised aircraft to have aural cabin altitude alert warning systems. This amendment will follow the normal regulatory development process which, in the first instance, will lead to the circulation of a Discussion Paper. It is anticipated that the paper will be released this month".

On the 2 February 2001, the Civil Aviation Safety Authority (CASA) also issued a Draft Discussion Paper, DP 0102CS, to the Australian aviation industry. The discussion paper was titled Proposal for Aural Warning to Operate With Cabin Altitude Alert Warning Systems. The discussion paper indicated that it was CASA's preferred option to mandate requirements to modify the aircraft concerned to install an audible warning to complement the existing cabin altitude alert warning system. Responses to that paper were to be provided to CASA by the 12 March 2001.

In April 2002 CASA issued a Notice of Proposed Rule Making (NPRM) on the fitment of aural warnings to pressurised jet and turboprop aircraft.

Investigation report BO/199902928 and the resultant recommendations are available on the Australian Transport Safety Bureau's Website, www.atsb.gov.au or from the Bureau on request.

Local safety action

The operator conducted its own investigation into the issues surrounding this incident. As a result of that investigation a number of changes have been made to the company's operational procedures. Those include a reassessment of company pilot training and check-to-line requirements. Greater emphasis is now being placed on adherence to checklists and occupational health and safety issues relating to operations in hot and humid environments.

The operator actively commenced correspondence with the Civil Aviation Safety Authority to enable the re-installation of the aural warning device kits. On the 15 January 2002, the Civil Aviation Safety Authority responded to the request. The response indicated that the operator could manufacture the system under the operator's "current certificate of approval, as manufacture in the course of aircraft maintenance". The CASA letter stated:

"Following a review of matters associated with the original warning kits and their installation, it is considered there are a number of matters you need to address to accomplish these modifications, they are:

"1.The draft NPRM 0116CS "Proposal for Aural Warning to Operate with Cabin Altitude Warning Systems" should be considered as much as possible, to avoid having to make future design changes to the system.

"2. A design advice on the modification should be submitted to CASA by the CAR35 Authorised Person to save possible rework. It would be expected that there would be a FAR 23.1309 hazard analysis carried out on the system as part of the design justification.

"3. The design needs to incorporate a backup sensor for cabin pressure in addition to the basic sensor fitted. Any failure in the backup system should not disable the warning from the prime system and vice versa. (ie FAR 23.1309 analysis)

"4. The design will call up parts and components by specification for installation in the modification."

On the 20 February 2002, the operator advised the ATSB that it had commissioned a CAR 35 engineer to draft a proposal for the design and approval of audible warning devices using the Civil Aviation Safety Authority's guidelines. Once that has been accomplished and a CAR 35 Engineering Order has been raised, the devices will be manufactured by a sub-contractor and installed in the operator's fleet of King Air aircraft.

Significant Factors

  1. The pilot did not complete the Pre Take Off and After Take Off cabin pressurisation checks.
  2. The pilot became pre-occupied with programming the GPS after receiving a track change instruction.
  3. The aircraft was allowed to climb above 10,000 ft in an unpressurised state.
  4. The effectiveness of the aircraft's cockpit warning system was reduced by the operator's practice of allowing postponement of the After Take Off check.

Analysis

Some vital checklist actions from the PRE TAKE OFF checklist and the AFTER TAKE OFF checklist were not completed by the pilot. Oppressively hot and humid conditions on the ground would have been very uncomfortable and likely to encourage the pilot to hasten his departure. Any haste during departure would have increased the risk of omitting a checklist item.

The non-standard clearance instruction, received soon after take-off, required re-programming of the GPS. That action captured his attention during the climb, and distracted the pilot from performing parts of the AFTER TAKE OFF checklist and the Transition Altitude Procedure.

The pilot had expected the routine illumination of the green auto feather advisory annunciators during the take-off and for part of the climb. Consequently, he did not identify that additional green annunciators, in the form of the bleed air off indications, were illuminated.

The pilot only noticed that the cabin altitude warning lights were illuminated after the flight nurse had alerted him to the automatic deployment of the passenger oxygen masks. Because of the separate pressure switches involved, it is possible that this deployment occurred slightly before the cabin altitude pressure warning. Alternatively, or in addition, the sun's relative position to the aircraft may have partially occluded the master warning light, making it difficult for the pilot to detect. The inclusion of an aural warning to operate in conjunction with the visual cabin altitude warning annunciator would have provided the pilot with an additional warning during a period of high workload. Desirably, the aural warning would be triggered by a different pressure switch than the visual warning.

The operator's instruction that permitted completion of the AFTER TAKE OFF check "as workload permits", allowed for postponement of a critical check on cabin pressurisation until well above 10,000 ft. Postponement of the AFTER TAKE OFF check also maintained the Auto Feather in an active state, and kept the green annunciator lights illuminated.

The pilot chose not to put on the oxygen mask, as required by the operator's Emergency Procedures, when alerted to the lack of pressurisation. That action resulted in a risk of the pilot suffering from hypoxia had the aircraft continued to climb in an unpressurised state.

Summary

The Beechcraft Super King Air 200 aircraft had arrived at Timber Creek NT to conduct an aeromedical flight to Tindal NT. The aircraft had the pilot, a flight nurse and one patient on board.

While on the ground at Timber Creek, the environment had been oppressively hot. Both the pilot and flight nurse reported feeling extremely uncomfortable and had both been perspiring profusely. The aircraft's air conditioning system was not operating properly and had offered little respite from the conditions, either on the ground or in the air. Due to the type of injuries that the patient had suffered, the flight nurse had requested that the pilot maintain "sea level" cabin pressure for the return flight. The flight nurse had also fitted an oxygen mask to the patient. The pilot recalled setting the pressurisation controls to suit the request from the flight nurse.

On the inbound flight, the pilot had been advised by Air Traffic Control to expect a non-standard clearance for the return flight due to RAAF aircraft activity in the area.

Following take-off, at about 2,000 ft, the air traffic controller instructed the pilot to intercept the 173 radial at 120 NM from Tindal, and then to track along that radial to Tindal. That had been necessary to avoid the now active Military restricted area R248(B). The pilot reported that he had then become occupied with re-programming the aircraft's Global Positioning System (GPS). During the climb to the cleared level, Flight Level 130, the pilot reported that he believed that he had actioned all the required checklist items.

As the aircraft climbed through FL125, the flight nurse noticed that the passenger oxygen masks had deployed and conveyed that fact to the pilot. The pilot was unaware of the deployment and had immediately turned around to assess the situation. When he turned his attention back to the instrument panel, the pilot noticed that the cabin ALT WARN caption positioned on the glare-shield mounted Master Warning panel was illuminated. Both Master Warning captions were also flashing. The pilot then contacted Air Traffic Control and received a clearance for an immediate descent to 10,000 ft.

The flight nurse donned the nearest available passenger oxygen mask and re-checked the flow of supplemental oxygen to the oxygen mask worn by the patient. The pilot did not don an oxygen mask during the incident.

Once established at 10,000 ft, the pilot discovered that both the left and right bleed air OFF green advisory annunciators were illuminated, and that both bleed air switches were in the ENVIR OFF position. In that position, no bleed air was available for aircraft pressurisation. The pilot had then selected both bleed air switches to OPEN, and restored normal pressurisation.

The flight was then continued to Tindal at the lower altitude.

The pilot was appropriately licensed for the flight and had approximately 3,600 hours total flying experience, of which 90 hours were on King Air 200 aircraft, with about 50 hours as pilot in command.

The Operator's Pre-Take Off Procedures required the bleed air to be selected to ON (OPEN). When the three-position bleed air switches were selected to EVIR OFF or INST & ENVIR OFF, a green advisory light L or R BLEED AIR OFF annunciator was illuminated. The pilot reported that he could not remember having selected the switches to OPEN prior to take-off.

The pilot indicated that he had not noticed the green L or R BLEED AIR OFF annunciators during the climb. He reported that that was partly due to him being accustomed to seeing the green L and R AUTOFEATHER advisory captions illuminated on the lower centre instrument console during the take-off. The pilot was also unsure if the ALT WARN and Master Warning caption had been illuminated prior to him being aware of the passenger oxygen mask deployment.

The operator's After Take Off Procedure included a requirement to turn the Auto Feather "OFF not below 1500ft". The pilot reported that the task was often left until after the transition altitude, when the cockpit routine was "less busy". That meant that the green L or R AUTOFEATHER advisory captions would remain illuminated until the checklist was completed, sometimes up to FL 150. The operator's After Take Off Procedure included a note, which indicated that the checklist only needed to be completed when workload permitted.

The After Take Off Procedures also required the pressurisation to be checked. That task involved the pilot checking that the bleed air valve switches were OPEN (up) position. The pressurisation gauges were also to be checked to ensure that the aircraft was pressurising normally. The Transition Altitude Procedures stated that "pressurisation checks should be made at least every 10,000 ft during climb and again when stabilised in the cruise".

The operator's Phase One Emergency Procedures, for a loss of pressurisation with the cabin altitude above 10,000 ft, directed the pilot to don the crew oxygen mask. The pilot reported that he had not performed that task as he had quickly descended the aircraft to 10,000 ft.

The aircraft's air conditioning system had a history of operating problems, with six instances of maintenance recorded since January 2001. The flight nurse said that the air conditioning system had been malfunctioning for some time prior to the incident, and that the aircraft had been to Darwin several times for repair. The crew also indicated that on the flight from Tindal to Timber Creek the interior of the aircraft had been hotter than normal and that it had not operated at all on the incident flight.

The maintenance record entry following the flight indicated that the air conditioning system high-pressure switch had tripped. Maintenance troubleshooting found that the system gas pressure was incorrect, and the pressure had been subsequently adjusted.

The aircraft's cabin altitude warning system and the passenger emergency oxygen mask system were both designed to operate at a cabin pressure altitude of 12,500 ft. The two systems were separate and operated in response to electrical signals received from individual pressure switches. The cabin altitude warning system illuminated both the glare-shield mounted flashing red Master Warning annunciators and the red ALT WARN annunciators on the warning annunciator panel. The passenger emergency oxygen mask deployment system activated a green PASS OXY ON annunciator on the aircraft's Caution/Advisory panel.

The operator had installed an aural warning device that operated in conjunction with the cabin altitude warning annunciator, into this aircraft on the 30 November 2000. That device had been installed under a CAR 35 engineering approval. On the 23 February 2001, following an instruction from the Civil Aviation Safety Authority that the device had to be removed because it had not been manufactured in accordance with current legislation, the unit was removed from the aircraft.

The sun's azimuth was 282 degrees true, which meant that the sun's light came from behind and to the left of the aircraft. The sunlight glare from the West may have occluded the red master warning and the altitude alert on the pilot's side and centre of the instrument panel glareshield.

A text by Thomas Turner, titled "Checklists & Compliance", written on the use of checklists in aircraft operations, pointed out the problem with operating equipment such as global positioning system units in "altitude critical areas". Such areas were defined as within 1,000 ft of the ground or within 1,000 ft of levelling off from a climb or descent. The textbook went on to say "Concentrate on what it takes to establish the new level flight attitude, trim the aircraft for level flight, and check to make sure critical items are complete before turning to less crucial tasks".

A Civil Aviation Safety Authority booklet "The Global Positioning System" stated that:

"GPS may relieve the mental task of computing the aircraft's position and speed in relation to maps of the terrain, but it may increase the workload of programming and accessing the desired information from the machine and interpreting it.

"Piloting an aircraft requires continuous monitoring and reacting to events both inside and outside the cockpit.

"The amount of information we can deal with at any one time is limited....

"Don't allow the operation of the GPS to interfere with your primary task of flying the aircraft".

Occurrence summary

Investigation number 200105188
Occurrence date 24/10/2001
Location 22 km SSE Timber Creek Aero.
State Northern Territory
Report release date 17/05/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Incorrect configuration
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Beech Aircraft Corp
Model 200
Registration VH-SWP
Serial number BB-529
Sector Turboprop
Operation type Aerial Work
Departure point Timber Creek, NT
Destination Tindall, NT
Damage Nil

de Havilland Canada DHC-8-315, VH-TQY

Summary

During initial climb, the right propeller of the DHC-8-315 (Dash 8) aircraft auto-feathered. The flight crew retarded the right engine power lever, declared a PAN (radio code indicating uncertainty or alert) condition, and completed an uneventful single engine return to Sydney airport.

The aircraft was fitted with two Pratt and Whitney Canada PW123E engines. The flight data recorder (FDR) indicated that the right engine over-torqued to 120 percent for 7 seconds after the propeller feathered. The FDR also indicated that the left engine over-torqued to 117 percent for 20 seconds. The engine manufacturer's transient over-torque limits were not exceeded.

Maintenance personnel found that a loose connection of the right engine torque signal conditioning unit (TSCU) connector pins resulted in an intermittent electrical connection. The TSCU was replaced as a precaution, and the connector was cleaned and reseated. Following a flight test, the aircraft was returned to service.

Propeller auto-feathering

The propeller auto-feather system, when selected, was designed to automatically feather the propeller during take-off if the engine torque decreased below about 22 percent rated torque. Interlock features in the auto-feather logic and control circuits provided arming control and prevented auto-feather of the operating propeller, once the auto-feather sequence for one of the propellers was initiated. The system provided for relaying a 'power uptrim' (engine power increase) signal to the operating engine.

Previous occurrences

The ATSB investigation into two previous occurrences (199905044 and 200002853) determined that in the earlier occurrence the electronic engine controller electrical connector was contaminated with water, while a faulty TSCU was found in the other.

The two previous Australian occurrences were also documented on the Australian Civil Aviation Safety Authority's database. A search of the engine manufacturer's database and the Service Difficulty Databases for Transport Canada and the United States of America Federal Aviation Administration, revealed twenty-three similar occurrences in the period from 19 June 1993 to 27 October 2001.

Of the twenty-six worldwide events reported, four were confirmed in-flight engine shutdowns (IFSD). Nineteen were attributed to electrical problems (harness and/or connector or torque signal conditioning unit). Fourteen events occurred during initial climb out and ten during the take-off roll.

Aircraft and engine manufacturer background information

The aircraft manufacturer advised that their data indicated that propeller auto-feathering as described in this incident was a result of loss of torque signal to the TSCU, most likely due to "connector intermittencies". Improvements to the system included design changes to strengthen the torque signal, and flight crew procedural changes. The aircraft manufacturer considered that the present decrease in reported occurrences reflected the success of these changes.

The engine manufacturer reported that the occurrences were associated with an intermittent loss of torque signal. They recommended, when an operator experienced one or more occurrences, that the operator conduct a fleet-wide electrical harness inspection, clean the connectors and enhance connector tightening procedures.

Service bulletins and operator letters

On 25 May 1993, the engine manufacturer issued Service Bulletin (SB) 21269 addressing the application of shrink tubing to the TSCU wiring harness to provide protection from moisture ingress and loosening of the connectors.

On 19 December 1995, the engine manufacturer issued SB 21456 addressing spurious `uptrims' and activation of the auto-feather control system when the system was in the armed condition. Those problems were attributed to the torque sensor air gap not being optimised. The procedures were described for decreasing the torque sensor air gap by replacing a spacer in the unit. The modification improved signal strength and reduced sensitivity to electrical 'noise'.

On 31 January 1996, the engine manufacturer issued SB 21463 addressing fretting of the TSCU electrical connector socket pins. The modification involved replacing the existing wiring harness with one that included a more secure connector assembly with sockets less susceptible to fretting.

On 11 December 1997, the engine manufacturer issued Operator Message Number (OMN) 464 informing operators of two recent IFSD auto-feather events and advised them that those events may have been the result of incorrect tightening torque on the TSCU connectors. They recommended that the connectors be inspected for security, and if found loose, should be disconnected and inspected for contamination and moisture.

On 28 February 2000, the engine manufacturer issued OMN 602 informing operators of recent IFSD auto-feather events and reiterated procedures currently published in the Aircraft Flight Manual. The letter strongly recommended that the operator's review, with their flight crews, the correct procedures to follow with respect to any engine or propeller malfunction on take-off. The letter also noted that previous events had indicated that flight crews often retard the power levers of both engines, thereby cancelling the `power uptrim' signal to the operating engine.

Compliance with these bulletins and messages was not mandatory, however the maintenance organisation implemented the requirements of SBs 21269, 21456 and 21463.

Occurrence summary

Investigation number 200105173
Occurrence date 27/10/2001
Location Sydney, Aero.
State New South Wales
Report release date 19/12/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Propeller/rotor malfunction
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer De Havilland Canada/De Havilland Aircraft of Canada
Model DHC-8
Registration VH-TQY
Serial number 552
Sector Turboprop
Operation type Air Transport High Capacity
Departure point Sydney, NSW
Destination Canberra, ACT
Damage Nil

Boeing 717-200, VH-IMD

Safety Action

Local safety action

As a result of the investigation, the following safety actions were carried out:

The operator issued a memo to its engineering staff highlighting the need for:

  1. extra vigilance when inspecting the rear fuselage area; and
  2. all hydraulic fluid leaks to be treated as potential total hydraulic failure and to be reported to maintenance watch.

The engine buildup unit contractor issued Service Bulletin, Rohr SB R715.29-001 on 9 November 2001, that provided instructions to install a pulsation attenuator to each engine driven hydraulic pump.

The airframe manufacturer issued an All Operators Letter (AOL) 717-048 on the 18 January 2002, recommending that operators install the hydraulic pump outlet attenuator (via Rohr Service Bulletin R715.29-001) to minimize hydraulic system vibrations.

Summary

Prior to descent into Coolangatta, the crew of the Boeing 717 aircraft noticed a low right hydraulic quantity warning. After following the abnormal checklist and turning off the right hydraulic system, the pilot in command decided that, due to the rudder reverting to manual mode and the loss of operation of two ground spoilers, he would divert the aircraft to Brisbane where a longer runway was available. After advising Brisbane Air Traffic Control of the hydraulic failure, and that a faster than normal landing would be carried out, the airport's emergency services were placed on standby.

With the right hydraulic system turned to the OFF position, the aircraft's landing gear had to be manually lowered using the emergency gear extension lever. That operation did not close the main landing gear doors after the landing gear was extended. In accordance with the abnormal check list an attempt to close the doors was conducted by the crew after receiving the green down and locked indication for the landing gear. However, following the selection of the right hydraulic system to ON, a rapid drop in hydraulic fluid quantity was noticed so the OFF position was immediately re-selected before the doors had closed.

As the aircraft touched down, the main landing gear doors contacted the runway surface. Although the doors were fitted with non-sparking polyurethane rest bumpers, the runway centerline lights were contacted creating sparks that were observed by ground personnel. The aircraft was then brought to a halt on the high speed taxiway where an engineer was requested to manually close the main landing gear doors. Following closure of the doors the aircraft taxied to the terminal. The abnormal checklist stated that the aircraft is not to be taxied but may be towed after landing gear safety pins had been fitted and main landing gear doors closed.

An inspection of the aircraft by the operator revealed that a hydraulic pipe from the right engine driven hydraulic pump had failed at its brazed fitting, resulting in the loss of hydraulic fluid from the right hydraulic system. As this was not the first time that the operator had experienced such a failure of hydraulic pipes, the aircraft manufacturer was contacted. It was determined that the pipes in the area of the rear fuselage were being subjected to vibration from the engine driven hydraulic pump, which in some cases resulted in the fracturing of the pipe fittings.

Occurrence summary

Investigation number 200105060
Occurrence date 18/10/2001
Location Brisbane, Aero.
State Queensland
Report release date 01/05/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Hydraulic
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 717
Registration VH-IMD
Serial number 55055
Sector Jet
Operation type Air Transport High Capacity
Departure point Sydney, NSW
Destination Coolangatta, QLD
Damage Minor

Fairchild SA227-AC, VH-VEH

Safety Action

The ATSB has distributed this report to all known Australian operators of Metro aircraft.

Technical Analysis Report

Fairchild Industries Inc. SA227-AC, VH-VEH

1 FACTUAL INFORMATION

1.1 Introduction

While on descent for a landing at Melbourne airport, the crew heard a loud 'bang' from the left engine and noted the aircraft yaw to the left. Observing that the left engine output torque had dropped to 15 percent and all other indications were normal, the pilot elected to leave the engine operating at low power and continued the flight to Melbourne.

Initial investigation by maintenance staff found many damaged and missing blades within the turbine assembly of the left engine. To conduct an investigation into the engine failure, the ATSB subsequently obtained the first stage turbine rotor disk and all segments from the first stage inlet guide vane assembly.

Fig. 1. Forward face of the stage-one turbine wheel - missing blade indicated.

Fig. 1. Forward face of the stage-one turbine wheel - missing blade indicated.

Analysis

The engine failure appears to have been initiated by the complete burn through of a vane in a turbine nozzle guide vane segment. That resulted in the disturbance of the airflow into the first stage of the turbine assembly and the ensuing failure of one of the first-stage turbine blades at the blade root. The reason for the nozzle guide vane segment burn through could not be fully determined. There was evidence of heat damage to many of the nozzle vanes. That damage can arise from in-service incidents such as partially blocked burner nozzles, however, there was no evidence to indicate that this occurred.

Cracking and erosion of the guide vane segments may have been detected by an in-service borescope inspection before the component failed. That inspection, however, would have required the operator to suspect that there was `fuel nozzle induced distress'. The evidence available from the operator's trend monitoring figures did not indicate any ongoing problem.

Summary

While at 8,000 ft on descent for a landing at Melbourne Airport, the crew of the Fairchild Industries Inc SA227-AC, Metro aircraft heard a loud bang from the left engine together with associated aircraft yaw. The pilot carried out the initial engine failure actions, noting that the left engine torque had dropped to 15%. The flight continued to Melbourne with the engine still operating. The pilot then carried out an uneventful approach and landing, shutting down the engine at the end of the landing roll.

An examination of the left engine, commissioned by the operator, found evidence of heat and burn damage in the turbine assembly, with one of the first-stage turbine nozzle vanes almost completely burnt away. A first-stage turbine blade had also detached from the first-stage turbine rotor assembly. That blade had then passed through the subsequent stages of the turbine section, extensively damaging the turbine components. The engine failure was fully contained.

The first-stage turbine blades and first-stage turbine nozzle assembly were forwarded to the ATSB's Technical Analysis section laboratory for further investigation. That investigation (see ATSB Technical Analysis Report, BE/200200024) found that many of the nozzle vanes had developed thermal fatigue cracking in the leading edges during operation. That cracking had led to the perforation of the internal cooling air galleries in one vane, resulting in the partial interruption to the flow of cooling air through it. The interrupted flow of air through the vane had resulted in its overheating and complete burn through. The burnt-through nozzle vane had subsequently disturbed the downstream flow of the combustion gas through the turbine and excited a once-per-revolution vibration of the first-stage turbine blades. The investigation concluded that the vibration contributed to development of fatigue cracking within the root of a single blade from the stage-one turbine, and the subsequent liberation of the cracked blade from the turbine rotor.

Maintenance issues

The engine was last overhauled on 20 January 1997 and had completed 2,327.9 engine hours and 2,473 cycles since that time. The operator's system of maintenance required that the turbine section be inspected at 3,500 hr intervals. To accomplish that inspection, the turbine section had to be removed from the engine. The forward end of the turbine was not normally examined outside of those inspection intervals.

During the 20 January 1997 overhaul, all 36 first-stage turbine blades were replaced with new items of part number 3108125-1. The 12 first-stage turbine nozzle segments were also replaced.

The 12 first-stage turbine nozzle segments were divided into two part number groups. Eight were of part number 3103820-4. Two of the ` - 4' segments were new, with the six remaining segments having been overhauled in January 1997. The remaining four nozzle segments were of part number 3103820-2 and included the failed segment. All of the ` - 2' segments had been overhauled in December 1996.

During the overhaul process the manufacturer required that the turbine nozzle segments be inspected for missing sections of vane material.

A 'Caution' note in the engine manufacturer's maintenance manual stated:

'CAUTION: MISSING MATERIAL (BURN THROUGH) AT VANE LEADING OR TRAILING
EDGE RESULTS IN IMPULSE (CYCLIC) LOADING OF BLADES.'

The engine manufacturer indicated that similar turbine blade failures had been observed in engines with clogged or streaking fuel burner nozzles.

The manufacturer further indicated that there was a `Hot Gas Path Inspection' borescope inspection procedure that could be carried out to determine the in-service wear of the first-stage turbine nozzle and first-stage turbine rotor. That inspection could be accomplished through the fuel nozzle body ports in the engine's combustion case, and was recommended if `fuel nozzle induced distress is suspected'. Fuel nozzle distress could be indicated to a pilot by an engine running hotter than normal or had reduced performance. The fuel nozzles were required to be serviced every 450 engine hours as part of the operator's system of maintenance. That maintenance had been carried out 197 hours prior to the incident.

Post-incident examination of the nozzles in the engine, carried out on behalf of the operator, did not reveal any nozzle clogging.

The operator carried out in-flight engine trend monitoring. That monitoring did not reveal any ongoing problem with the operation of the engine.

Occurrence summary

Investigation number 200104983
Occurrence date 11/10/2001
Location 46 km ENE Melbourne, Aero.
State Victoria
Report release date 19/12/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Fairchild Industries Inc
Model SA227
Registration VH-VEH
Sector Turboprop
Operation type Charter
Departure point Canberra, ACT
Destination Melbourne, VIC
Damage Nil

Boeing Co 737-376, VH-TAU

Summary

The Boeing 737 aircraft was operating a scheduled passenger service from Sydney to Alice Springs. At 1118 Central Standard Time, the flight crew advised air traffic control (ATC) that they had commenced a descent from flight level (FL) 310 to Alice Springs.

The general weather situation in the Alice Springs area was influenced by an unstable air mass with a trough developing to the west of Alice Springs. The aerodrome forecast issued to the crew prior to departure from Sydney indicated strong, gusty north-westerly winds during the day with moderate turbulence below 5000 ft expected after 1300. Storms were forecast to develop by 1130.

Distant lightning and showers had been reported to the west of Alice Springs from 0330. From that time, weather radar picture (RAPIC) imagery indicated that showers and thunderstorms were moving in a south-westerly direction at 15 to 25 kts. The RAPIC imagery available to the air traffic controllers was updated every 10 minutes. The shower/thunderstorm activity was mostly developing and decaying within 30-60 minutes, with breaks between the cells.

Showers developed in the vicinity of Alice Springs airport by 1100. An aerodrome special weather report (SPECI) was issued at 1109 due to the wind gusting to 26 kts. The visibility was 10 km or greater with one octa of cumulonimbus cloud and four octas of cumulus cloud at 9,000 ft. The report also indicated that there were showers in the area.

At 1119, the aerodrome controller advised the crew of a military aircraft inbound to the airport that `a storm or shower was passing through at the moment' with the visibility being greater than 10 km and a cloud base of 9,000 ft. That aircraft subsequently landed on runway 30 and did not report encountering turbulence during the approach.

Another SPECI was issued at 1120 due to a thunderstorm with a base of 9,000 ft and reduced visibility of 3,000 m to the north west of the airport. The 1120 RAPIC image showed a large area of rain associated with thunderstorm activity to the southeast and southwest of the airport between 2 and 13 NM. The thunderstorm activity had developed earlier over the MacDonnell Ranges to the west of the airport, and had moved in a south-easterly direction at around 15-25 kts.

At 1125, the aircraft encountered light to moderate turbulence as it passed through FL110, and the frequency of the turbulence increased as the descent continued. One minute later, another SPECI was issued, which reported that the wind was 250 degrees at 27 kts, with gusts to 37 kts. The visibility had reduced to 3,000 m to the west of the airport due to rain from thunderstorms.

The aircraft was 27 NM from the airport when the aerodrome controller advised that there were showers to the northwest and south of the airport but that it appeared `fairly clear for straight in for a final 30'. The flight crew concurred, noting that the weather was on their left. The rainfall was also observed by the crew on the aircraft weather radar that was displayed on the electronic horizontal situation indicators located on the aircraft instrument panels.

At 1128, the aerodrome controller broadcast terminal information Foxtrot, which advised that the wind was 250 degrees at 15 kts, the visibility was reduced to 6 km in passing rain showers, with heavy rain showers to the northwest. The 1130 RAPIC image showed that the thunderstorm activity had moved further to the southeast with areas of moderate rain recorded between 4 and 19 NM from the airport adjacent to and over the approach path for runway 30.

The aircraft experienced three encounters with moderate to severe turbulence between 1131 and 1132 as it descended through 4,700 ft (approximately 2,900 ft AGL). The encounters occurred at about 10 NM from the airport on the extended centreline for runway 30. At that stage the area of moderate rain was about 3 NM to the left of the aircraft with another area of moderate rain ahead on the approach path.

The flight crew conducted a missed approach at 1132. They advised the aerodrome controller that they had encountered severe turbulence and were turning right to remain clear of a thunderstorm. The aircraft sustained further encounters with moderate to severe turbulence until 1133 during the turn. Wind information recorded on the aircraft flight data recorder showed that the wind had been 325 degrees at 31 kts before the turbulence and had backed to 260 degrees at 45 kts during the encounters.

The crew subsequently advised the controller at 1134 that they had received a `very severe and nasty whack', and followed up with the comment that what they had encountered was in the `downburst type of category'. At 1136 the tower broadcast terminal information Golf and, due to the information being prepared before the missed approach, it did not contain any reference to pilot reports of severe turbulence. As there were no other aircraft in the vicinity, the terminal information was not immediately updated to include the report of severe turbulence.

The crew manoeuvred the aircraft to the north and southwest of the airport before conducting a landing on runway 12 at 1147 without further incident. After landing, the crew advised the controller that conditions on approach for runway 30 were `absolutely violent'. At 1201 the aerodrome controller broadcast terminal information Hotel, advising that thunderstorms were in the area and severe turbulence had been reported below 5,000 ft in the circuit area. That information was subsequently provided at 1203 to the crew of another aircraft inbound to Alice Springs from the north.

The procedures relating to the provision of weather information to pilots by ATC were set out in the Manual of Air Traffic Services (MATS) issued by the Department of Defence and Airservices Australia. Part 5; section 1 of MATS contained instructions regarding information to be provided to pilots by air traffic control including a hazard alert service.

The hazard alert service was required to contain information assessed by ATC as being of an unexpected and critical nature. That information would be based on the surveillance and assessment of various reports including SIGMET and AIRMET forecasts, amended forecasts, RAPIC information, observations and reports indicating weather conditions at the destination had deteriorated below the IFR or VFR alternate minima.

During the descent and approach of the aircraft, there were no SIGMETs or AIRMETs issued for the Alice Springs area, nor were the SPECIs indicating that the weather conditions had deteriorated below the IFR alternate minima. The Bureau of Meteorology (BoM) had no record of Alice Springs ATC contacting either the Darwin Regional Forecasting Centre or the Alice Springs Weather Service Office about the crew's report of severe turbulence.

Research into convective activity in dry semi-arid environments, similar to Alice Springs, has shown that storms with high bases can produce strong downdrafts (Caracena, Holle & Doswell, 2001). Studies have also shown that storms producing little or no surface rain (<0.25 cm) can produce dry microbursts. In extremely dry situations the storms may not produce lightning even though the high based cumulus clouds have a fibrous appearance and a prominent anvil (Caracena, Holle & Doswell, 2001). Researchers have also noted that radar echoes may be very misleading in determining the likelihood of dry microburst activity (Caracena, Holle & Doswell, 2001).

Analysis

The aircraft was operating in an environment that was conducive to turbulent conditions. During the encounter with the severe turbulence between 1131 and 1133, the aircraft was located about 3 NM from the edge of a convective cell with a high base. The severe turbulence encountered by the aircraft was probably associated with strong convective outflows from that cell.

The crew considered that the meteorological information issued to them prior to departure from Sydney and also by the Alice Springs aerodrome controller, was sufficient for them to determine the weather conditions likely to be encountered during the approach to runway 30. The crew's decision to continue the approach near convective activity was based on their subjective assessment of that information and the actual weather conditions.

The provision of weather information to the flight crew by the aerodrome controller was in accordance with the requirements of the MATS. There were no current SIGMETs or AIRMETs during the descent and approach of the aircraft and therefore the aerodrome controller was not required to issue a hazard alert to the crew.

The transmission from the crew at 1134 referred to downbursts but this information was not clarified by the controller to determine whether a report of windshear conditions was required in the next terminal information broadcast. Information Golf, broadcast at 1136, did not contain any reference to pilot reports of severe turbulence in the circuit area.

There was no record that the crew's reports were passed on to BoM for processing. MATS was ambiguous and did not provide clear guidance as to what action should be taken by air traffic controllers following the receipt of a pilot report concerning severe turbulence in the terminal area. Despite the ambiguity, the controller assessed the reports, and he subsequently included them in information Hotel issued at 1201. The controller also alerted the crew of the next aircraft operating in the Alice Springs terminal area about the report.

This occurrence highlights the need for air traffic controllers and flight crews to be aware of the hazards associated with convective activity. It is the second occurrence in a twelve-month period involving high capacity aircraft operating into airports affected by convective activity. The first occurrence involved a windshear encounter at Brisbane Airport in January 2001. A more detailed analysis of the hazards associated with convective activity in terminal airspace is provided in ATSB Air Safety Occurrence Report 200100213.

Safety Action

Local Safety Action

As a result of this occurrence, the air traffic services provider will be preparing a refresher training package for use by aerodrome controllers.

Reference:

Caracena, F., Holle, R.L., & Doswell, C.A., 2001, Microbursts A Handbook for Visual Identification (online). U.S. Department of Commerce, National Oceanic and Atmospheric Administration, Washington. http://www.cimms.ou.edu/~doswell/microbursts/Handbook.html
[Accessed 22 January 2002].

Occurrence summary

Investigation number 200105157
Occurrence date 22/10/2001
Location Alice Springs, Aero.
Report release date 16/08/2002
Report status Final
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Turbulence/windshear/microburst
Occurrence class Serious Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 737
Registration VH-TAU
Serial number 23486
Operation type Air Transport High Capacity
Departure point Sydney, NSW
Destination Alice Springs, NT
Damage Nil