Cessna 441, VH-VEM

Summary

Shortly after take-off from Gawler SA, the crew of the Cessna 441 Conquest heard a loud air noise. The pilot in command recognised this as the emergency pressurisation system operating. The pressurisation selector switch was checked and found to be in the BOTH position. Selection was made between LEFT and RIGHT, however the air noise continued and there was no activation of the emergency pressurisation warning light. At this point the crew elected not to proceed to Essendon but to divert to Adelaide, where engineering staff were available.

Subsequently, a passenger noticed that the air by his feet was getting hot and advised the crew. Light grey smoke was noticed by the co-pilot in the mid cabin area. The crew conducted the emergency checklist for smoke removal and donned their oxygen masks as a precaution. The storm window was opened to assist with removal of smoke from the aircraft as it was stinging the co-pilot's eyes.

The pilot declared a PAN, and, at this point, the aircraft was 2 km abeam Parafield. The crew elected to divert to Parafield, the nearest airfield where emergency services were available. An uneventful landing was carried out and no injuries were reported.

An engineering examination of the aircraft found that the activation of the emergency pressurisation system was initiated by a faulty emergency pressurisation valve. It was also found that, in the process of fitting new side wall trim carpet to the aircraft, the edge of the carpet had not been trimmed around the rear conditioned air duct. This duct supplies air for the emergency pressurisation system and the faulty emergency pressurisation valve allowed hot air to flow unmetered into the cabin. The carpet covering the duct had been exposed to excessive heat, which led to the fumes and smoke in the cabin.

The faulty emergency pressurisation valve was replaced, the carpet trimmed, and the aircraft was returned to service.

Occurrence summary

Investigation number 200205216
Occurrence date 06/11/2002
Location Parafield, Aero.
State South Australia
Report release date 26/08/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Air/pressurisation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Cessna Aircraft Company
Model 441
Registration VH-VEM
Serial number 4410174
Sector Turboprop
Operation type Charter
Departure point Gawler, SA
Destination Essendon, VIC
Damage Nil

Boeing 737-476, VH-TJG

Safety Action

As a result of this occurrence, the following safety actions were initiated:

The operator of Canberra International Airport requested Airservices Australia to include a caution note in Canberra aerodrome information contained in the ERSA, as follows:

`During strong westerly winds down stream of buildings, severe turbulence may be experienced in the touch down area while landing Runway 35.'

The operator also requested Airservices Australia to issue a Notice to Airmen (NOTAM) to reflect that cautionary advice until the ERSA was amended, and to give consideration to making:

`…necessary caution announcements on the ATIS during similar strong wind conditions.'

Airservices Australia issued a local instruction to air traffic controllers at Canberra Tower. The instruction contained information that when the crosswind component (including gusts) from the west equals or exceeds 12 kts and runway 35 or 17 is nominated, the following shall be included on the ATIS:

`Expect turbulence over runway south of runway intersection.'

The instruction included information that controllers were to make a directed broadcast to aircraft operating on runway 35, or departing runway 17, when this crosswind condition exists and runway 35 or 17 were not nominated on the ATIS.

Airservices reported that it did not consider the issue of a NOTAM providing cautionary advice of turbulence was warranted, as directed broadcasts would provide pilots with information of the meteorological phenomenon.

Airservices Australia also reported that it would conduct a survey of the turbulence phenomenon until 1 July 2003 to determine the extent of the condition, including:

a. occasions when the westerly crosswind component, including gusts, equals or exceeds 12 kts,

b. pilot reports of turbulence / shear at touch down or take-off, including aircraft type,

c. pilot comments, and

d. pilot reports of turbulence when the crosswind is less than 12 kts.

Analysis

At the time of the occurrence, the wind direction and speed at Canberra aerodrome was 280 degrees T at 18 kts, with gusts exceeding 20 kts at times. The wind direction was therefore 80 degrees removed from the runway direction, providing a left crosswind of about 18 knots.

It is probable that the prevailing wind conditions at the time of the occurrence resulted in turbulent downwind wake eddies from the hangar located adjacent to, and to the west of, the touchdown zone of runway 35.

The downwind convergence of those turbulent wake eddies was probably in the vicinity of the touchdown zone of runway 35, and was likely to have been the source of the turbulence encountered during the landing flare.

Summary

At 1718 ESuT On 5 November 2002, VH-TJG, a Boeing 737-476 aircraft, encountered turbulence 1718 ESuT during the landing flare on runway 35 at Canberra International Airport. The aircraft was operating a scheduled fare-paying passenger service from Melbourne, Victoria to Canberra, ACT. The pilot in command was the handling pilot for the flight.

At 1700, the wind direction and speed at Canberra was 280 degrees T at 18 kts, gusting to 23 kts. At 1730, it was 280 degrees T at 18 kts, gusting to 26 kts. Runway 35 was aligned on magnetic heading 348 degrees, which was equivalent to 360 degrees T.

The automatic terminal information service (ATIS) at Canberra airport provided information on the prevailing weather conditions. At the time of the occurrence, information "Sierra" was current. It included information that runway 35 was in use, and that the wind direction and speed was 270 degrees M, with a minimum speed of 15 kts and maximum speed of 25 kts.

The aircraft was equipped with a solid-state digital flight data recorder (SSFDR). The flight data plots revealed that the pilot in command applied left control wheel to achieve a left wing low attitude of about 3 degrees as the aircraft descended through a radio altitude of about 60 ft. At about 6 ft radio altitude, the aircraft suddenly rolled left to a left wing low attitude of about 6 degrees, and the pilot in command rapidly applied right control wheel input to arrest the roll to the left. The aircraft landed about one second later in a slightly right wing low attitude.

The landing was completed without further incident, and there were no reported injuries to any of the 34 occupants of the aircraft.

The pilot in command subsequently reported that the turbulence encountered during the landing flare appeared to have resulted from a hangar located adjacent to, and to the west of, the touchdown zone of runway 35.

Construction of the hangar was completed in April 2002. The airside (eastern) face of the hangar was located 283.5 metres from the centreline of runway 35, and the roof height on the airside face of the hangar was 21.7 metres.

Turbulent wake eddies may be generated downwind of obstacles by wind flowing over and around them. The turbulent effects will depend on the size and location of an obstacle or group of obstacles, such as a cluster of buildings, as well as the direction and speed of the wind. If obstacles are located close to runways, turbulent wake eddies from those obstacles may have the potential to affect safety of flight if they result in aircraft experiencing difficulties during takeoff or landing.

The International Civil Aviation Organization (ICAO) has published standards and recommended practices that relate to aircraft, personnel, airways and auxiliary services. Those standards and recommended practices are contained in various Annexes to the Convention on International Civil Aviation, which was signed at Chicago on 7 December 1944 (the Chicago Convention). Australia is a contracting State to the convention. It is obliged under Article 37 of the convention to conform to standards and to endeavour to conform to recommended practices unless a difference has been filed with ICAO.

Annex 11 contained the standards and recommended practices that relate to the provision of air traffic services to the aviation sector. Paragraph 4.3.7 of Annex 11 detailed the information to be included in ATIS messages, and paragraph 4.3.7 k) required that messages contain:

`…other essential operational information.'

Paragraph 4.3.7 s) required ATIS messages to contain:

`…any available information on significant meteorological phenomena in the approach, take-off and climb-out areas including wind shear, and information on recent weather of operational significance.'

ATIS "Sierra" contained no information regarding the likelihood of turbulence in the touchdown zone of runway 35 at the time of the occurrence.

Canberra International Airport is a licensed aerodrome, and particulars about the aerodrome are required to be published in the Aeronautical Information Publication (AIP) Enroute Supplement Australia (ERSA).

The Civil Aviation Safety Authority (CASA) publishes Civil Aviation Advisory Publications (CAAPs) which provide guidance on the preferred method for complying with the Civil Aviation Regulations. CAAP 89O-1 (2), issued in November 2000, related to publishing aerodrome information and reporting changes to that information. That information included any event that affected the safety of aircraft using the aerodrome.

At the time of the occurrence, both the ERSA and the location briefing material for Canberra aerodrome contained no information to caution pilots of the likelihood of turbulence from the hangar located adjacent to, and to the west of, the touchdown zone of runway 35.

There have been two similar events of building-induced turbulence in the UK. One resulted in a B747 leaving the runway at London Heathrow airport, and was described in the UK Air Accident Investigation Branch (AAIB) Bulletin No. 5/2002. The other involved an A300 that sustained a podstrike at London Gatwick airport, and was described in AAIB Bulletin No. 6/2002.

The National Transportation Safety Board (NTSB) of the USA has had no reported occurrences of building-induced turbulence, nor has the NTSB identified that condition as a safety concern.

There are presently no building codes or standards in Australia that address the phenomena of building-induced turbulence with respect to proposed buildings to be located on or adjacent to aerodromes.

Occurrence summary

Investigation number 200205179
Occurrence date 05/11/2002
Location Canberra, Aero.
State Australian Capital Territory
Report release date 13/03/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Turbulence/windshear/microburst
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 737
Registration VH-TJG
Serial number 24432
Sector Jet
Operation type Air Transport High Capacity
Departure point Melbourne, VIC
Destination Canberra, ACT
Damage Nil

British Aerospace Plc BAe 146-300, VH-NJL

Safety Action

Issues associated with improving cabin air quality are the subject of ongoing efforts by the aircraft manufacturer, engine manufacturer, aircraft operators and some aviation regulatory authorities including the Australian Civil Aviation Safety Authority.

The Civil Aviation Safety Authority issued an airworthiness directive on 28 November 2002 (AD/BAe 146/102) requiring operators of BAe 146 type aircraft to action requirements of a manufacturer's Inspection Service Bulletin (ISB) 21-156. This related to the recurrent inspection of air conditioning ducts for traces of possible contamination and inspection of the ducts following a cabin air quality event.

The aircraft operator has also commenced replacing the noise-attenuating material that lines the air conditioning ducts across their entire BAe 146 fleet. This action exceeded the manufacturer's requirements outlined in its ISB 21-156.

The engine manufacturer is developing a redesigned bearing seal to improve the component's reliability and consequently reduce the frequency of incidents where cabin air is contaminated by engine lubricating oil.

Analysis

The investigation considered that the intermittent deterioration in cabin air quality was consistent with other similar occurrences during which the cabin air was contaminated by engine or APU lubricating oil. Due to the intermittent nature of contamination the source of the fumes was difficult to positively identify.

It was not possible to identify the substance(s) that had apparently contaminated the crew's drinking water while it had been left standing in the cups. However, the investigation could not discount the possibility that the drinking water had been contaminated by water-soluble compounds from cabin air contaminated by engine lubricating oil.

Summary

The co-pilot of the BAe146-300 reported that he noticed both cockpit side windows were open as he entered the flight deck to commence his pre-flight preparations and almost immediately detected the presence of fumes. He stated that these fumes had a distinctive odour that he recognised as being consistent with the contamination of the cabin air supply by lubricating oil from the aircraft's engines. This typically occurs when a faulty bearing seal allows lubricating oil to escape and contaminates one of the sources of cabin air for the aircraft.

The auxiliary power unit (APU) was operating and air conditioning Pack 1 and 2 were supplying air to the flight deck and passenger cabin. As Pack 1 supplies most of the air to the flight deck and because fumes were not apparent in the passenger cabin, the co-pilot immediately suspected that the contamination was associated with Pack 1. He de-selected Pack 1 and noticed an immediate improvement to the quality of the air.

The co-pilot briefed the pilot in command of these observations when he arrived on the flight deck. The crew used engine bleed air to provide cabin air conditioning as the aircraft taxied for take-off and Pack 1 remained de-selected. This was on the basis of the tailwind conditions encountered while taxiing, to reduce the possibility of ingesting fumes from the APU's exhaust into the aircraft cabin and the co-pilot's observations of air quality from Pack 1. The take-off was performed with all air conditioning packs selected off and number 4 engine supplying bleed air for pressurisation control of the aircraft cabin.

The co-pilot was the handling pilot for the sector from Perth to Karratha. After take-off, the crew selected engine bleed air sources from all engines and Pack 1 and 2 were used to provide air conditioning to the passenger cabin and flight deck. No fumes were evident in either the passenger cabin or the flight deck and the flight proceeded normally.

About 10 minutes prior to the top of descent, the co-pilot recalled starting to experience symptoms of a headache. He was able to continue his duties as handling pilot and completed the descent to the Karratha circuit area. The aircraft was on final approach to land, when strong oil-type fumes were again detected on the flight deck. As the aircraft cabin had already stabilised at sea-level atmospheric pressure and the source of fumes appeared to be either the air conditioning packs or one of the engine bleed air supplies, all air conditioning packs and all sources of engine bleed air were selected off. The intensity of the fumes quickly dissipated and the co-pilot completed the landing. Fumes were not detected in the passenger cabin by any of the flight attendants. The co-pilot reported that supplemental oxygen was not used on this occasion due to the critical phase of flight (short final approach to land) and the prompt action taken to isolate the source of fumes.

During the taxi to the passenger terminal, the co-pilot became aware that he was experiencing symptoms of an unusually strong headache, nausea and irritated eyes, nose and throat. His symptoms quickly improved as he conducted the external turnaround duties and he felt capable of performing his duties on the return sector as pilot not flying.

The pilot in command was satisfied that the source of fumes experienced on short final was associated with contamination of the cabin air supply by engine lubricating oil. The return flight was conducted without using APU air and with Pack 1 de-selected to minimise the possible recurrence of fume contamination. The flight was completed without incident.

Subsequent to the incident, the co-pilot recalled that during the outbound sector his bottled drinking water, which had been poured and left standing in his cup, had acquired a rank swampy, slightly metallic taste. The pilot in command was also reported to have made a similar comment about the taste of his drinking water. The cups were resting in the flight deck cup holders adjacent to the air outlet vents. This was noticed prior to the co-pilot reporting symptoms of a headache and fresh cups of water from the bottle tasted normal with no apparent sign of contamination. The ATSB were not able to test the water for contaminants as it had been discarded following the flight.

Following entry of the fume report in the aircraft's defect log, company engineering personnel applied the requirements of Airworthiness Directive AD BAe 146/86, issued 30 March 2001 that required inspection of various components associated with the aircraft's cabin air supply. This inspection revealed no apparent defects or source of contamination to the cabin air.

The operator received subsequent Operating Crew Reports associated with poor cabin air quality on 23 and 26 October 2002. The aircraft commenced a period of heavy maintenance on 28 October 2002. During this maintenance the APU was removed from the aircraft, cleaned, inspected (with nil defects found) and refitted. Air conditioning Pack 1 was also cleaned. The operator received subsequent reports of flight deck odours with respect to this aircraft on 5 and 8 December 2002 and the requirements of the Airworthiness Directive were again applied. On this occasion the inspections revealed slight leakage of engine lubricating oil from a bearing seal on the number 4 engine.

Occurrence summary

Investigation number 200204912
Occurrence date 20/10/2002
Location 6 km E Karratha, Aero.
State Western Australia
Report release date 20/08/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fumes
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer British Aerospace
Model BAe 146
Registration VH-NJL
Serial number E3213
Sector Jet
Operation type Air Transport High Capacity
Departure point Perth, WA
Destination Karratha, WA
Damage Nil

de Havilland Canada DHC-2 MK 1, VH-BVA

Safety Action

Local Safety Action

Civil Aviation Safety Authority

On 1 December 2002, the Civil Aviation Safety Authority revised the chief pilot's instrument of approval, specifying a condition that required the employment of a full-time senior float pilot.

On 20 August 2003, CASA provided the following information with respect to guidelines for aeroplane landing areas: 'As there are several levels of jurisdiction over waterways, CASA has raised with State Governments, through the Commonwealth/States/Territories Aviation Working Group, the question of whether there should be a joint review of the existing arrangements.'

Operator

In a letter to the Australian Transport Safety Bureau dated 11 June 2003, the operator advised that it had amended the company operations manual to reflect the appointment of a senior float pilot and revised the floatplane operations section of the operations manual. The operations manual stipulated that the senior float pilot was responsible to the chief pilot for the overall conduct of company floatplane operations.

The operator advised that it had appointed a new chief pilot.

An experienced floatplane pilot provided a report to the operator regarding company floatplane operations. Recommendations from that report included:

  1. additional theoretical and practical training and checking for company floatplane pilots;
  2. development of a company-specific pilot training guide; and,
  3. review and amendment as required of the company floatplane authorised landing area guide.

The floatplane pilot who wrote the report for the company has been retained to implement the changes recommended.

The company also advised that it intended to upgrade the facilities at its floatplane base to allow pilots improved access to weather, flight planning and operational reference information.

The company advised that it planned to implement a fatigue management system for pilots, including modifying the daily work schedule to allow adequate rest periods.

Factual Information

History of the flight

The pilot of the de Havilland Beaver floatplane registered VH-BVA was conducting a charter positioning flight from Hamilton Island Marina to Chance Bay, Whitsunday Island. He had landed at Chance Bay seven times in the previous two days. Weather conditions in the area were good. At 1700 Eastern Standard Time the Hamilton Island automatic weather station recorded a 7 - 10 knot wind from the northwest. Witnesses in Chance Bay said that the surface wind in the bay was 2 - 5 knots. The water surface in Chance Bay was smooth, but not glassy.

The pilot said that he commenced a straight-in approach to Chance Bay but elected to go around due to the increased number of vessels moored in the bay since the previous flight. He flew a left circuit at 500 feet and assessed that the area for landing was adequate. He said that on final approach, the flight path was higher than he would have preferred. His intention was to touchdown before passing abeam the vessels. He recalled that the floatplane speed shortly before touchdown was about 80 knots, rather than the target speed of 70 knots. He said that his response at this time was consistent with flying a landplane in that he reduced the back pressure on the control column and allowed the floatplane to contact the water at a lower nose attitude, and at a higher speed, than was ideal. Upon touchdown, the floatplane yawed sharply left 50 - 60 degrees and headed directly towards the anchored ketch 'Seark', about 300 m away. The pilot said that the water rudders (at the rear of each float) were retracted, so all the yaw control he had available was via the conventional aerodynamic rudder. As the aircraft yawed, it felt as though the rudder was stuck at full left deflection, but he thought that this was due to hydrodynamic drag. When the floatplane was an estimated 100 m from the 'Seark', it swung right so that it was heading slightly to the east side of the 'Seark'. However, the outer portion of the floatplane's left wing subsequently collided with the rear mast of the 'Seark'.

A video recording of the event showed that the floatplane touched down with a lower nose attitude than was ideal. It also showed that the left float touched the water first. The sharp left yaw followed immediately. The aircraft became airborne momentarily, shortly after initial touchdown.

The left wing of the floatplane and the rear mast of the ketch were substantially damaged. There were no injuries to the pilot or the three occupants of the ketch.

Landing area

Witnesses estimated that landing floatplanes (including this accident floatplane prior to touchdown), were passing about 50 m abeam the anchored yachts.

Civil Aviation Advisory Publication (CAAP) 92-1(1) 'Guidelines for aeroplane landing areas' stated that "a minimum width water channel of 60 m ... is recommended" for single-engine and centreline thrust floatplanes not exceeding 2,000 kg maximum take-off weight (MTOW). There were no diagrams or other guidance material provided for floatplanes greater than 2,000 kg MTOW or for multi-engine floatplanes. The MTOW for the accident floatplane was 2,313 kg. The Transport Operations (Marine Safety) Regulations (Queensland) 1995 s95 (1)(a)(ii) required that vessels operating at speeds greater than 6 knots must not approach within 30 m of a moored vessel.

Float alignment

Another company floatplane pilot reported that the aircraft required greater than normal right rudder input to maintain a constant heading during flight. During an inspection after the accident, maintenance personnel established that the floats were aligned slightly left of the aircraft's longitudinal axis. The aircraft manufacturer commented that the reported flying characteristics were consistent with the float alignment. The aircraft had been flown 23.8 hours since the last maintenance inspection, including about 10 hours by the accident pilot. No record had been made in the aircraft maintenance release regarding the 'in-flight' or 'on-water' handling characteristics.

Floatplane stability on the water

The ideal landing attitude for a floatplane is nose high, so that the rear portion of the float contacts the water first. If a floatplane lands at too high a speed (lower nose attitude than ideal), the point of contact of the floats with the water (that is, the centre of rotation of the floatplane) is at a position on the floats that is forward of the aircraft's centre of gravity and the aircraft's directional stability is reduced. If the loss of directional stability is not too severe, the pilot may be able to regain control if nose-up elevator is applied very rapidly to move the centre of rotation aft, behind the centre of gravity.

Pilot information

The pilot was the chief pilot of the company. Of his 11,256 hrs total flight time, 34 hrs were in floatplane operations, and included 79 water landings.

The pilot commenced floatplane endorsement training in October 2001. The endorsement was issued on 12 February 2002, after four sessions of training in Cessna 206 floatplanes involving 4.1 hrs and 16 water landings. Between 15 March and 25 July 2002, the pilot conducted four sessions in command under supervision in de Havilland Beaver floatplanes, involving 7.3 hrs and 23 water landings. On 25 July 2002 the company floatplane training pilot authorised the pilot to conduct solo commercial operations to specific destinations but noted that he was to be closely monitored in marginal conditions until he was more experienced.

The accident flight was the last flight of the day for the pilot. He had completed five flights with a total of 3 hrs flight time and 10 hrs duty time before the accident. The day before the accident the pilot had completed 10.2 hrs duty, including 4.8 hrs flight time during eight flights. The day prior to that was a rostered day off. He reported that neither fatigue nor any other personal issues had impaired his ability to safely operate an aircraft on the day of the accident.

The pilot's work/rest history for the 14 days prior to the accident was examined using a computerised fatigue algorithm developed by the Centre for Sleep Research, University of South Australia. The results indicated that the pilot was not experiencing significant levels of fatigue in the week leading up to, and on the day of, the accident.

Organisational information

At the time of the accident, the company employed an experienced floatplane pilot who conducted all the accident pilot's floatplane endorsement and in command under supervision training. The authority, duties and responsibilities of this floatplane pilot were not established or formalised in either the Civil Aviation Safety Authority (CASA) issued instruments of approval for key company personnel, or in the company operations manual.

The company operations manual stated that pilots with less than 250 water landings were subject to the direct supervision of the chief pilot who was to take into account the wind strength, wind direction, turbulence, tide and sea state at the origin and destination of the flight before approving a flight. There was no provision in the operations manual for when the chief pilot did not have the minimum 250 water landings experience. (Other companies required up to 300 water landings in command under supervision and 50 hours total floatplane flight time before solo commercial flight operations were permitted.)

For VFR charter in single-engine aircraft, CASA required that a pilot hold a commercial licence and the applicable aircraft special design feature endorsement, for example float alighting gear. CASA did not specify additional minimum experience requirements on the aircraft type or the special design feature.

Chief pilot appointment

Civil Aviation Order 82.0 required that a chief pilot hold licences, endorsements and ratings that permit command of all company operations. CASA had approved the pilot's appointment as chief pilot for the operator on 19 April 2002. At that time, he had obtained a float alighting gear endorsement but had not been authorised by the company to conduct solo commercial floatplane operations.

Analysis

The video recording supported the pilot's description of the event. Together they indicated that the landing technique employed by the pilot was likely to have established the centre of rotation forward of the centre of gravity with respect to the left float when it contacted the water. Under such conditions, the floatplane would have been directionally unstable and a sharp left yaw was likely. The pilot may have applied up elevator after touchdown but did not regain sufficient directional control to prevent the aircraft from colliding with the yacht.

The evidence indicated that company floatplane pilots were selecting a landing direction that provided about 50 m lateral separation from moored vessels. This separation is greater than the minimum required under marine regulations but was insufficient to prevent a collision on this occasion. The minimum separation required under marine regulations was clearly inadequate to provide a safe margin, particularly given the benign environmental conditions that existed at the time of the accident. Aviation regulations and supporting advisory material do not provide any guidance for de Havilland Beaver aircraft operators and pilots regarding appropriate lateral separation from moored vessels or other obstacles during take-off and landing operations.

The technique employed by the pilot to achieve the intended touchdown was not appropriate for floatplane operations. Its use indicated shortcomings in the floatplane endorsement training received by the pilot and reflected the pilot's low level of experience in floatplane operations. The number of water landings under supervision completed by the pilot was considerably less than that required by other floatplane operators.

It was inappropriate for the chief pilot, given his limited floatplane experience, to be responsible for company floatplane operations, with no formalised support from appropriately experienced floatplane pilots.

Analysis of the pilot's flight and duty time records suggested that fatigue did not play a role in the development of the accident.

The contribution of the misaligned floats to the development of the accident could not be determined. The lack of any maintenance release record concerning the handling characteristics of the aircraft suggests that pilots who flew the aircraft may not have considered that any aspect of the aircraft's handling characteristics warranted rectification.

Summary

The pilot of the de Havilland Beaver floatplane registered VH-BVA was conducting a charter positioning flight from Hamilton Island Marina to Chance Bay, Whitsunday Island. He had landed at Chance Bay seven times in the previous two days. Weather conditions in the area were good. At 1700 Eastern Standard Time the Hamilton Island automatic weather station recorded a 7 - 10 knot wind from the northwest. Witnesses in Chance Bay said that the surface wind in the bay was 2 - 5 knots. The water surface in Chance Bay was smooth, but not glassy.

The pilot said that he commenced a straight-in approach to Chance Bay but elected to go around due to the increased number of vessels moored in the bay since the previous flight. He flew a left circuit at 500 feet and assessed that the area for landing was adequate. He said that on final approach, the flight path was higher than he would have preferred. His intention was to touchdown before passing abeam the vessels. He recalled that the floatplane speed shortly before touchdown was about 80 knots, rather than the target speed of 70 knots. He said that his response at this time was consistent with flying a landplane in that he reduced the back pressure on the control column and allowed the floatplane to contact the water at a lower nose attitude, and at a higher speed, than was ideal. Upon touchdown, the floatplane yawed sharply left 50 - 60 degrees and headed directly towards the anchored ketch 'Seark', about 300 m away. The pilot said that the water rudders (at the rear of each float) were retracted, so all the yaw control he had available was via the conventional aerodynamic rudder. As the aircraft yawed, it felt as though the rudder was stuck at full left deflection, but he thought that this was due to hydrodynamic drag. When the floatplane was an estimated 100 m from the 'Seark', it swung right so that it was heading slightly to the east side of the 'Seark'. However, the outer portion of the floatplane's left wing subsequently collided with the rear mast of the 'Seark'.

A video recording of the event showed that the floatplane touched down with a lower nose attitude than was ideal. It also showed that the left float touched the water first. The sharp left yaw followed immediately. The aircraft became airborne momentarily, shortly after initial touchdown.

The left wing of the floatplane and the rear mast of the ketch were substantially damaged. There were no injuries to the pilot or the three occupants of the ketch.

Occurrence summary

Investigation number 200204857
Occurrence date 19/10/2002
Location Chance Bay, Whitsunday Island
State Queensland
Report release date 21/08/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer De Havilland Canada/De Havilland Aircraft of Canada
Model DHC-2
Registration VH-BVA
Serial number 245
Sector Piston
Operation type Charter
Departure point Hamilton Island, QLD
Destination Chance Bay, Whitsunday Island, QLD
Damage Substantial

Boeing 727-277, VH-TXH

Technical Analysis Report

Technical Analysis Report: Examination of the Main Landing Gear Wheel Bearings

During a routine departure from Melbourne aerodrome, the inner left main landing gear wheel separated from a B727 aircraft (registration VH-TXH) and was later recovered near the aerodrome perimeter fence. Preliminary examination showed that the outer axle bearing had failed, allowing the wheel hub to move axially outward over the retaining nut and off the stub axle (figure 1).

Safety Action

Local safety action

Following discussions with the ATSB, the operator amended the company maintenance control manual (MCM) introducing into the "Component and Material Control" section, a Shelf Life reference applicable to the storage of wheel assemblies. This shelf life has been set at a maximum of twelve months. These amendments will be incorporated at the next revision (revision 14) of the MCM.

As the operator's maintenance control monitoring of wheel change requirements generally resulted in wheel storage periods, in house, of no more than three months prior to their use in the fleet, the operator feels that the nine-month additional shelf life buffer is adequate.

In addition, the Australian overhaul facility for the operator's wheels also introduced a twelve-month shelf life limit for its stored assemblies, after which all bearings are disassembled, inspected for corrosion and re-greased.

The amendment to both the operator's MCM and its overhaul facility procedures will minimise the possibility of wheels being returned to service with bearing integrity compromised by corrosion or grease lubrication qualities degraded through prolonged storage periods.

Significant Factors

  1. The condition of the wheel bearings and the lubricating grease was degraded during the extended storage.
  2. There was no required re-inspection maintenance procedure for lubrication quality or bearing corrosion prior to fitment of the wheel to the aircraft.
  3. The number 2 wheel outer bearing failed, resulting in the inability of the wheel retention nut to retain the wheel on the axle.

Factual Information

While on approach to land at Perth, the crew of the Boeing 727 notified air traffic control (ATC) that they required runway 21 instead of 24. This was in consideration of the wet runway conditions and as a possible precaution should they experience antiskid problems. They also advised ATC to expect a normal approach.

After parking the aircraft, the crew reported the loss of the inner left main wheel and requested rescue fire-fighting services to attend while the aircraft was secured (see Figure 1.). An inspection of the Perth runway did not find any debris.

aair200204836_001.jpg

Figure 1. Left main landing gear missing number 2 wheel.

A search conducted at Melbourne airport, the point of departure, resulted in the recovery of debris from runway 34. The wheel had impacted the perimeter fence past the runway 34 overrun area and was recovered from that location.

Inspection of the landing gear revealed that the outer bearing had failed, which allowed the wheel assembly to migrate over the locked retaining nut and depart from the axle. Landing gear damage was confined to the sacrificial alloy axle sleeve (see Figure 2).

After completion of the Boeing Conditional Inspection following bearing failure, the alloy sleeve and main wheel were replaced. As a precaution, the operator also replaced the remaining three wheels of the main landing gears. As the nose landing gear wheels were from a different overhaul facility, it was not considered necessary to replace them prior to the aircraft returning to service. The line engineers who removed the main wheels verified that bearing dust seals were present on all the remaining wheel bearings.

aair200204836_002.jpg

Figure 2. Left main landing gear axle damage.

The inner bearing cone of the lost wheel was recovered from the aircraft landing gear and, along with the wheel bearings from the remaining three wheels, was sent to the ATSB for further technical analysis. The separated main wheel and bearing cone debris recovered in Melbourne were also forwarded to the ATSB.

Main wheel assemblies

The operator had recently acquired the aircraft on lease after it had been in long term storage in the USA. During the process of transfer to the Australian register, the American owner sourced a serviceable set of main wheel assemblies to standardise the aircraft with the rest of the Australian operator's fleet. The wheels carried release to service documentation after overhaul from an approved American maintenance facility.

The incident wheel (number 2) had been overhauled in accordance with approved data and released for service with the correct documentation on 14 November 2000. The wheel was subsequently fitted to the Boeing 727 on 31 August 2002. The wheel was in storage for all the intervening period between release to service and fitment to the aircraft. The remaining wheel (number 1) on the left landing gear had been overhauled in accordance with approved data and released for service with the proper documentation on 7 December 2001. The wheel was subsequently fitted to the aircraft on 31 August 2002.

Wheel numbers 3 and 4 on the right landing gear were overhauled in accordance with approved data and released for service with the proper documentation on 17 and 22 August 2001 respectively. The wheels were subsequently fitted to the aircraft on 29 August 2002. Although still a lengthy storage period, wheel numbers 1, 3 and 4 had been in storage for a significantly shorter period than wheel number 2.

The quality assurance inspector for the overhaul facility stated that, although not mandated, the company recommended to customers to re-inspect stored wheels every twelve months. He also stated that, after overhaul, all wheels were returned to their owners, and the company did not hold any wheels in long-term storage. As part of the shipment preparation, the overhaul company routinely packed the wheel bearings in grease and sealed them in plastic bags before they were placed in the wheel assemblies. The plastic bags were to be removed before the wheel re-entered service. With no wheel assemblies stored at the overhaul facility, the company had no requirement for a repetitive storage inspection procedure to be in place. This meant that the wheels fitted to the aircraft had been returned after overhaul to their owner (the aircraft owner) and were placed in storage at a site other than the overhaul facility. The aircraft owner had then supplied the wheels to the Australian operator for fitment to the Boeing 727.

At the time of the incident, the aircraft operator's maintenance control manual did not include a section relating to wheel storage and tracking procedures, which specifically mandated a storage life expiry interval and re-inspection procedure for wheels. The maintenance personnel who fitted the wheels to the aircraft stated that the wheels were received from the USA with the bearings in place. There were no reports of the bearings being received in plastic bags as described by the overhaul facility. There was also no paperwork supplied to the Australian operator to suggest that the wheels had been fitted to another aircraft after overhaul.

ATSB laboratory component examination

While damage to the failed bearing prevented the determination of specific factors that contributed to the failure of the particular unit, the evidence found during the investigation suggests that the development of corrosion damage over the contact surfaces of the wheel bearings was a major factor contributing to the failure. This was evident in the bearings examined from the remaining wheels. The corrosion led to insipient contact fatigue spalling, which is well understood can lead to catastrophic bearing failure consistent with the circumstances of this occurrence. The bearing lubricating grease was found to be congealed, hardened and in a dry state. A foreign material identified as brake dust was also found in the grease. The inclusion of this foreign material may also have contributed to the failure.

Summary

While on approach to land at Perth, the crew of the Boeing 727 notified air traffic control (ATC) that they required runway 21 instead of 24. This was in consideration of the wet runway conditions and as a possible precaution should they experience antiskid problems. They also advised ATC to expect a normal approach.

After parking the aircraft, the crew reported the loss of the inner left main wheel and requested rescue fire-fighting services to attend while the aircraft was secured. An inspection of the Perth runway did not find any debris.

Occurrence summary

Investigation number 200204836
Occurrence date 18/10/2002
Location Melbourne, Aero.
State Victoria
Report release date 23/06/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 727
Registration VH-TXH
Serial number 20549
Sector Jet
Operation type Air Transport High Capacity
Departure point Melbourne, VIC
Destination Perth, WA
Damage Minor

Cessna 182B, VH-PDK

Significant Factors

  1. The weather conditions at the time of the accident were favourable to the development of lee waves and strong downslope winds in the vicinity of the airstrip.
  2. The aircraft banked steeply out of wind, while at low airspeed and a low height.
  3. The aircraft stalled at an altitude from which recovery by the pilot was not considered possible and control of the aircraft was lost.



 

Analysis

Witnesses observed the C182 at low altitude on approach to Turalla. Their reports that the wings were rocking from side to side were consistent with the turbulence that may have been produced in the lee of the escarpment by the strong wind. Down draughts and rotor turbulence could have resulted from the vigorous airflow at right angles to the escarpment, immediately to the west of the airstrip, and existed for a considerable distance downwind of the escarpment.

An approach to land in those conditions should not have placed any exceptional demand on the pilot's skill. The strip was aligned nearly into wind and the pilot was familiar with both the airstrip and the aircraft. The pilot had probably flown from the airstrip in similar conditions previously and should have been aware of the potential for turbulence and down draughts. The landing distance available was more than adequate for the aircraft type.

In turbulent conditions a pilot can elect to use less than maximum flap, or even no flap for the approach and landing. In a strong headwind, this would not significantly increase the aircraft's landing distance. Using less than full flap on the C182 can improve aircraft handling in turbulence. However, using less flap at lower airspeeds and higher angles of bank, significantly increases the aircraft stall speed.

Although the reason the approach was discontinued was unable to be determined, it was possible that the approach became unstable in the turbulence with airspeed fluctuations. The pilot appeared to have turned right to initiate a low-level circuit. Familiarity with the airstrip and anticipating turbulence in the lee of the escarpment may have been the reason that the pilot initiated a right turn rather than climbing straight ahead, which could have placed the aircraft into an area of increased turbulence. The direction of turn was consistent also with the pilot turning away from the glare of the setting sun. The pilot's memory of his siblings' accident may have influenced the decision-making process to make a rapid escape from the area of turbulence.

Witnesses reported that the aircraft's angle of bank was between 60 and 80 degrees when the approach was discontinued. There was no apparent reason for a steep turn to be made. There was no necessity for the pilot to rapidly make another approach and landing. There were adequate margins for both daylight and fuel.

The altitude at which the aircraft was seen to be operating would probably not have been sufficient to allow recovery from a stall, even with a pilot proficient in the technique. It was also possible that at the extreme angles of bank, a sudden loss of lift resulting from windshear or turbulence, or a rapid retraction of the manually operated flaps, could have placed the aircraft in a stalled condition from which recovery would have been unlikely at such a low height.

Factual Information

History of the flight

The pilot of the Cessna 182B Skylane (C182), with one passenger on board, departed Leongatha aerodrome in Victoria at about 1530 Eastern Standard Time (EST). The pilot planned the private flight in accordance with the visual flight rules to track coastal to Moruya and then via the Araluen Valley to 'Turalla', a private property located approximately 3 km northwest of Bungendore, NSW. The aircraft carried sufficient fuel for the flight.

Witnesses reported that, at about 1755, the aircraft overflew a property belonging to a relative of the pilot 3 km to the southeast of Bungendore, at about 500 ft AGL. That relative had been nominated as the responsible person to hold and cancel the nominated SARTIME of 1820. The aircraft was then observed to track west towards the Kings Highway, at a low level, and make a right turn to join a wide left base for the grass airstrip located at 'Turalla'. The airstrip was aligned approximately 305 degrees M. The aircraft was observed to turn left onto final approach at about 50-80 ft AGL. Witnesses reported that all turns were made using about 45 degrees angle of bank. Witnesses also observed the aircraft to be buffeted by gusting winds.

The weather at the time was reported by witnesses to be clear conditions with some upper level cloud. Winds were strong and blustery, from the west and northwest. A Bureau of Meteorology assessment of the weather indicated gusty north-westerly winds backing to the west after the passage of a front, which had occurred earlier in the day. The general wind structure lent itself to at least moderate turbulence and the strong possibility of lee waves and strong downslope winds.

While on short final, the aircraft was observed to make a steep climb towards a downwind position, turning to the right using 60-80 degrees angle of bank. It was then observed to lose altitude rapidly. It turned through about 295 degrees before impacting the ground approximately 300 m east-north-east of the airstrip threshold. The aircraft struck the ground at a 60-80 degree nose down, left wing low, attitude on a heading of about 240 degrees M. The aircraft was destroyed by impact forces and post-impact fire.

Injuries to persons

The passenger was fatally injured. Autopsy and toxicological tests conducted on the passenger revealed a low level of carbon monoxide in the blood. Medical opinion indicated that death occurred prior to the commencement of the post-impact fire. The pilot was seriously injured and survived the accident for 68 days before succumbing to the effects of his injuries.

Annex 13 to the Convention on International Civil Aviation, Aircraft Accident and Incident Investigation, defined a fatal injury as an injury that resulted in death within 30 days of the date of an accident.

Wreckage and impact information

A post-impact fire consumed the cockpit area. The extent of the fire damage precluded a productive examination of the cockpit, controls and instruments. Many of the alloyed components had been reduced to a molten state. Examination of the wreckage indicated that at the time of impact the aircraft was not configured for landing. The wing flaps were set to the retracted position. The engine was removed from the accident site for technical examination. The examination determined that the engine was capable of normal operation prior to impact and that it was producing power at the time of impact. Nothing was found during the investigation to suggest that mechanical failure of any part of the aircraft could have contributed to the accident.

Personnel Information

The pilot held a current private pilot's licence, was endorsed on the aircraft type and familiar with the landing area. A review of the pilot's personal flying logbook indicated that he had accumulated in excess of 340 hours total time, most of which were accrued on the occurrence aircraft. Four days prior to the accident, the pilot had satisfactorily completed a biennial flight review. The pilot held a valid Class 2 Aviation Medical Certificate. The pilot had just completed a short hiking holiday and there was no evidence to indicate any physical or psychological conditions that may have adversely affected his ability to pilot the aircraft.

Landing area

The landing area at Turalla was inspected after the accident. With the exception of a centrally located windsock, there were no aerodrome markings to detail the exact location and dimensions of the airstrip. There was evidence of recent aircraft use on the grass strip. The landing distance available was approximately 800 m, orientated approximately 305 degrees M. There was no evidence to indicate that livestock had been grazing on the paddock that contained the airstrip in the past month. A north-south ridgeline was located approximately 1 km to the west of the airstrip. At the time of the accident, the sun was setting in the west and was visible above the horizon.

Previous occurrence at the airstrip

One of the pilot's brothers and a sister were fatally injured in a separate aircraft accident (Bureau of Air Safety Investigation Report No. BO/199603734) in the vicinity of the same airstrip in 1996, when similar wind conditions were experienced. On that occasion, the Cessna U206F (C206) aircraft was climbing on departure from Turalla when the pilot turned left onto downwind. The C206 stalled at a height from which it was not possible to recover.

Summary

The pilot of the Cessna 182B Skylane (C182), with one passenger on board, departed Leongatha aerodrome in Victoria at about 1530 Eastern Standard Time (EST). The pilot planned the private flight in accordance with the visual flight rules to track coastal to Moruya and then via the Araluen Valley to 'Turalla', a private property located approximately 3 km northwest of Bungendore, NSW. The aircraft carried sufficient fuel for the flight.

Witnesses reported that, at about 1755, the aircraft overflew a property belonging to a relative of the pilot 3 km to the southeast of Bungendore, at about 500 ft AGL. That relative had been nominated as the responsible person to hold and cancel the nominated SARTIME of 1820. The aircraft was then observed to track west towards the Kings Highway, at a low level, and make a right turn to join a wide left base for the grass airstrip located at 'Turalla'. The airstrip was aligned approximately 305 degrees M. The aircraft was observed to turn left onto final approach at about 50-80 ft AGL. Witnesses reported that all turns were made using about 45 degrees angle of bank. Witnesses also observed the aircraft to be buffeted by gusting winds.

The weather at the time was reported by witnesses to be clear conditions with some upper level cloud. Winds were strong and blustery, from the west and northwest. A Bureau of Meteorology assessment of the weather indicated gusty north-westerly winds backing to the west after the passage of a front, which had occurred earlier in the day. The general wind structure lent itself to at least moderate turbulence and the strong possibility of lee waves and strong downslope winds.

While on short final, the aircraft was observed to make a steep climb towards a downwind position, turning to the right using 60-80 degrees angle of bank. It was then observed to lose altitude rapidly. It turned through about 295 degrees before impacting the ground approximately 300 m east-north-east of the airstrip threshold. The aircraft struck the ground at a 60-80 degree nose down, left wing low, attitude on a heading of about 240 degrees M. The aircraft was destroyed by impact forces and post-impact fire.

Occurrence summary

Investigation number 200204663
Occurrence date 13/10/2002
Location 2 km W Bungendore
State New South Wales
Report release date 18/07/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model 182
Registration VH-PDK
Serial number 51673
Sector Piston
Operation type Private
Departure point Leongatha, VIC
Destination Turalla, NSW
Damage Destroyed

Near collision Aero Commander 690-A, VH-AAG, Bankstown Airport, on 25 September 2002

Summary

The pilot of a Turbo Commander reported, that when on short final approach to runway 29 centre (29C) at Bankstown Airport, he saw another aircraft, above and slightly to the left of his aircraft, in close proximity. The pilot of the Turbo Commander conducted a go around. The other aircraft was subsequently found to be a Cessna 152 (C152) flown by a pilot conducting circuit training as part of commercial pilot licence training.

The occurrence happened about 1 minute after evening civil twilight of 1819 Eastern Standard Time. The Aeronautical Information Publication defines that period between evening civil twilight and morning civil twilight as `night'. The Bankstown automatic terminal information broadcast at the time advised that runway 29C was available for all operations on radio frequency 132.8 MHz, the wind direction was 270 degrees M at a speed of 15 kts, with a maximum crosswind of 10 kts and the barometric pressure was 1013 hectopascals.

Due to the onset of twilight, the aerodrome controller (ADC) was transitioning from multiple runway to single runway operation. Runway 29C is the preferred runway for night operations. Traffic disposition at the time was three single-engine aircraft conducting circuit training, two arriving aircraft and one aircraft ready for departure.

The ADC instructed the pilot of the Turbo Commander to join left downwind for runway 29C at 1,500 ft, as the second aircraft in the arrival sequence. The first aircraft in that sequence was an Aero Commander 500, also tracking to join left downwind at 1,500 ft. Both aircraft were operated by the same company. The pilot of the Turbo Commander requested, and was approved by the ADC, to maintain 2,000 ft until sighting `the other company traffic'. The pilot of the Turbo Commander reported to the ADC on a wide downwind at 2,000 ft. The ADC instructed the pilot of the Turbo Commander to descend to 1,000 ft and to follow the company Aero Commander. General Aviation Aerodrome Procedures (GAAP) require a pilot who is instructed to follow a particular aircraft, to sight the other aircraft and to regulate aircraft speed to achieve longitudinal spacing. Those procedures also require a pilot to report to the ADC if they are unable to see, or lose sight of, the aircraft. The pilot of the Turbo Commander requested an update of the position of the Aero Commander ahead and the ADC advised that it is `in your 10 o'clock'. The pilot acknowledged that advice and continued the approach.

Pilots of both instrument flight rule (IFR) and visual flight rule (VFR) category flights operating in a GAAP control zone (CTR) are required to operate in accordance with the VFR. Also, Civil Aviation Regulation (CAR) 163A stated, `When weather conditions permit, the flight crew of an aircraft must, regardless of whether an operation is conducted under the IFR or the VFR, maintain vigilance so as to see and avoid other aircraft.'

Within a GAAP CTR, controllers use sequencing instructions and/or provide traffic information to pilots to assist them to manoeuvre to avoid other traffic. Other than the application of runway separation standards between aircraft during take-off or landing, an ADC does not use standards to segregate airborne aircraft.

Pilots of aircraft operating in a GAAP CTR are not required to use the aircraft's secondary surveillance radar transponder. The pilot of the Turbo Commander and the pilot of the Aero Commander were operating their respective transponders. The pilot of the C152 was not operating that aircraft's transponder. The ADC had access to a tower situational awareness display (TSAD), to assist in maintaining situational awareness. The TSAD used radar information from the Australian Advanced Air Traffic System and provided a track history, callsign (or mode A) and altitude if the SSR transponder was operating, and aircraft ground speed. The TSAD was limited in scale and definition and the display monitor was located to the rear of the tower console.

Recorded radar data indicated that the Aero Commander and the Turbo Commander entered the control zone with groundspeeds of 170 kts and 260 kts respectively. The maximum ground speed of the C152 was 110 kts for a short period when mid-downwind. The downwind leg for the Turbo Commander was laterally displaced about twice the distance from the runway centreline, compared with the other aircraft in the circuit, due to the need to descend and also to maintain spacing with the aircraft ahead. The pilot of the Turbo Commander reduced the aircraft's groundspeed while tracking via downwind and base.

The pilot of the C152 reported downwind and was instructed by the ADC to sight and follow the Turbo Commander on a `late wide downwind'. The pilot saw that aircraft and also noted another aircraft on final approach to the runway. Subsequently, the pilot of the C152 lost sight of the Turbo Commander and on late base requested an update of the position of that aircraft from the ADC. As the ADC was responding, the pilot of the C152 saw the Turbo Commander to his right at an altitude slightly below that of the C152. At that stage the pilot of the Turbo Commander commenced the go around and advised the ADC. Recorded radar data showed that just prior to the go around, the Turbo Commander was 200 m west of the C152 and on a converging track. The groundspeed of the Turbo Commander when on final approach was 100 kts; the groundspeed of the C152 on late base was 70 kts.

While the TSAD was available to assist the ADC, it is unlikely to have been of much benefit as that controller needed to visually monitor all aircraft in the circuit. The occurrence reinforces the need for vigilance by both pilots and controllers during GAAP. The pilot of the C152 was required to maintain separation with and to follow the Turbo Commander but was probably constrained by his limited flying experience. The ADC, having established an arrival sequence, was required to monitor the situation to ensure that it happened as planned. A combination of darkness, the transition to single runway operations and the significantly higher groundspeed of the Turbo Commander, compared with the other aircraft in the circuit at the time, were additional factors that increased the complexity of the situation.

Occurrence summary

Investigation number 200204471
Occurrence date 25/09/2002
Location Bankstown, Airport
State New South Wales
Report release date 15/10/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Near collision
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Aero Commander
Model 690
Registration VH-AAG
Serial number 11101
Sector Turboprop
Operation type Air Transport Low Capacity
Departure point Canberra, ACT
Destination Bankstown, NSW
Damage Nil

Aircraft details

Manufacturer Cessna Aircraft Company
Model 152
Registration VH-MAQ
Serial number 15281602
Sector Piston
Operation type Flying Training
Departure point Bankstown, NSW
Destination Bankstown, NSW
Damage Nil

Boeing 717-200, VH-VQC

Safety Action

Local safety action

Engine/EEC manufacturer

On 25 October 2002, the engine manufacturer issued worldwide communication WW/20032/1/25-10-002 informing operators and airframe and engine technical representatives of the in-flight shutdown event and the fault codes witnessed.

On 27 November 2002, the engine manufacturer issued worldwide communication WW/20032/2/27 Nov. 02 updating the operators and airframe and engine technical representatives of the in-flight shutdown event investigation. That communique informed of the testing of the Fuel Metering Unit and EEC.

On 20 December 2002, the engine manufacturer issued Notice to Operators (NTO) number 54 advising operators of the in-flight shutdown events and of engine restart procedures in the event of an engine shutdown without abnormal engine indications. That communique also advised of harness installation procedures, review of the fault codes and recommended interrogation of the multi-function control display unit (MCDU) at intervals of 50 flight hours.

The engine manufacturer further advised that they will be incorporating a software upgrade of the EEC to version 7.0, which will include an improvement to remove the possibility for certain intermittent failures to trigger a 'health lane' degradation without triggering the corresponding maintenance message.

The Operator

Following the return to service of the aircraft after the 4 October 2002 event, the operator implemented a MCDU interrogation procedure on the incident aircraft for a period of three days. The MCDU stored fault codes were reviewed at the end of each day of flying. The procedure was similar to that subsequently recommended by the engine manufacturer in NTO 54 issued on 20 December 2002. The maintenance history of the right engine was also reviewed as far back as its installation on the aircraft, which occurred on 3 August 2002.

Following the 24 November 2002 event, the operator carried out similar actions as completed after the 4 October 2002 event. The maintenance history of the aircraft was reviewed as far back as the last A check in September 2002. The MCDU review procedure was expanded to cover all aircraft in the fleet. The operator initiated review procedure was superseded on 27 November 2002 by an interim health check procedure developed by the engine manufacturer. This procedure required MCDU fault codes to be reviewed after every 25 to 30 sectors.

Australian Civil Aviation Safety Authority

On 29 November 2002, the Australian Civil Aviation Safety Authority (CASA) issued a directive to the operator to review all fault codes at the end of each day's flying for the occurrence aircraft until further notice.

On 6 December 2002, CASA relaxed the MCDU review requirement for VH-VQC to every port with engineering support available.

On 16 January 2003, CASA issued a request to the operator requiring reviews additional to NTO 54. That action included a review of fault codes at the end of each day's flying for all operator aircraft, with the incident aircraft logged fault codes being reviewed after each sector where engineering support was available. They further expanded the review of fault codes after each sector where engineering support was available to include all operator B717 aircraft.

CASA has subsequently advised the ATSB that the operator has commenced the following program to ensure continued airworthiness of the fleet:

- The MCDU is to be interrogated for EEC faults after each flight into a manned port. Recurring faults identified in NTO 54 should result in replacement of the EEC.

- Fault codes and corrective actions are to be reported to CASA.

- EECs are to be modified per RRD SB-BR700-73-900316.

- One modified EEC is to be installed, in turn, on each aircraft in the fleet.

- Once a modified EEC has been installed, its reliability is to be monitored by continuing the MCDU interrogation after each flight to a manned port for two weeks. Once the reliability is established, MCDU interrogation can be extended to service check intervals.

- Modification of both the EECs, and confirmation of their reliability through MCDU interrogation described above constitutes the corrective actions after which the MCDU interrogations can revert to service check intervals.

- All EECs returned to the manufacturer are to be upgraded and the entire fleet is scheduled to be modified not later than the first quarter of 2004.

RECOMMENDATIONS

Recommendation 20030032

As a result of this investigation, the Australian Transport Safety Bureau recommends that the German Airworthiness Authority, Luftfahrt-Bundesamt issue an airworthiness directive to mandate compliance with Rolls-Royce Deutschland Ltd and Co KG Service Bulletin SB-BR700-73-900316.

Recommendation 20030037

As a result of this investigation, the Australian Transport Safety Bureau recommends that the United States Federal Aviation Administration liaise with the German Airworthiness Authority, Luftfahrt-Bundesamt to develop and issue an airworthiness directive to mandate compliance with Rolls-Royce Deutschland Ltd and Co KG Service Bulletin SB-BR700-73-900316.

Significant Factors

  1. The right engine EEC sustained a failure of both channels of an independent two-channel system, resulting in an in-flight engine shutdown with no prior indications to the flight crew.



 

Analysis

During climb following take-off, the right engine electronic engine controller (EEC) removed electrical power from the engine fuel-control metering valve, which was spring loaded into the closed position. Following loss of the electrical signal, the valve closed resulting in fuel starvation and engine shutdown. The loss of electrical signal to the engine fuel-control metering valve was the result of a dual channel failure of the EEC. The dual channel failure was believed to be the result of:

the failure of channel A because of checksum anomalies of the electrically erasable/programmable read-only memory and

the failure of channel B as a result of electrical intermittences, caused by the loss of signal path resulting from solder joint fractures of the resistors of the analog interface module circuit board.

Examination of other fleet EECs has confirmed the fracturing anomaly of the solder joints of the resistors of the analog interface module circuit board. The effect of the solder joint fracturing on the function of the EEC appears to be loss of signal path on the circuit board and eventual 'health lane' degradation of the unit leading to a shutdown of that channel.

Fracturing of one or more resistor solder joints on both channels of the EEC simultaneously could lead to the loss of system redundancy in the EEC and a subsequent in-flight shutdown of the engine. The possibility of a successful engine restart could be difficult to predict. The crack propagation rate of the resistor solder joint fracture, and the amount required for signal loss is as yet unknown. Therefore, probability calculations for reliability rates of the units may be inaccurate. Compliance to Service Bulletins SB-BR700-73-101401 (SB-BR715/73-009), SB-BR700-73-101404 (SB-BR715/73-010) and SB-BR700-73-900316 was not mandatory.

Factual Information

Flight recorder data

Data reviewed following the flight confirmed that approximately 3 minutes after full power application for takeoff, the fuel flow to the right engine dropped to zero, resulting in the subsequent in-flight shutdown of the engine.

Component history

Documentation provided by the operator annotated that the EEC part number 114E6112G119, serial number LHBR0141, had accumulated 426.7 hours time since new, 393 cycles since new, and had been installed on 2 August 2002. The unit had been modified to software version 6.1 (the most recent version).

Electronic engine controller

The EEC was a two-channel (A and B) electronic unit with system redundancy. It controlled, among other items, engine start sequencing, power requirements, operating temperature, turbine speeds, fuel flow, engine monitoring, and automatic relight. It contained fault detection, storage, and readout capabilities, all stored on an electrically erasable/programmable read-only memory (EEPROM) located on a computer board assembly. The EEPROM provided a history for troubleshooting purposes of any fault event within the EEC or associated control systems by logging a fault code of the event. Those fault codes were then stored until intentionally cleared during maintenance action. The distinct two channels in the unit ensured that should one channel fail, the other would assume control and monitoring of the engine. The transfer of control and monitoring of the engine to one EEC would not necessarily signify that other items controlled by the non-controlling channel would not function. The EEC also provided an electrical signal for opening the engine fuel-control metering valve (normally closed) upon engine starting, which was spring loaded to the closed position.

Component testing

The EEC and FMU units were shipped to the respective component manufacturer's facilities for testing under the supervision of the United States of America (USA) National Transportation Safety Board. Representatives from the aircraft, EEC and engine manufacturers were also present for the testing. Testing of the FMU revealed no anomalies.

EEC serial number LHBR0141 testing

During environmental stress screening of the EEC (a high-speed scan of the faults over a temperature cycle alternating from -55 to +74 degrees C), failures of the Channel A EEPROM were recorded when the internal temperature of the EEC was at -2 degrees C or colder. Test procedures used to test new units for acceptance, also revealed faults of the Channel A EEPROM at temperatures below -55 degrees C. However, initial testing of the EEC could not duplicate the dual channel failure (A and B) that would have been required to sustain the reported in-flight shutdown.

The Channel A EEPROM was sent to the manufacturer for detailed examination. Examination indicated that a phenomenon called a 'single bit flip' had occurred within the used memory section area of the input/output microprocessor of the unit. The input/output microprocessor memory was configured with positively charged hexadecimal binary 1s occupying unused memory sections. The 'single bit flip' phenomena was a result of unused sections of the microprocessor memory becoming negatively charged binary zeros, resulting in checksum failures and 'health lane' degradation of the EEC. Checksum failures are the result of discrepancies of the internal self-check program, which sums the values of all memory blocks.

Follow up vibratory testing of the EEC confirmed a failure of Channel B. Further examination indicated fracturing of solder joints at five resistors on the analog interface module circuit board of Channel B.

Other Australian fleet occurrences

On 24 November 2002, while on the downwind leg for landing at Hobart, another crew of the same aircraft reported that the left engine 'spooled down'. The crew reported that they did not see any caution advisories prior to the power decrease. The crew then completed a single engine landing. Following the event, the operator's maintenance personnel conducted troubleshooting of the left engine and noted one fault code related to the EEC (not listed in maintenance documentation) logged on the MCDU memory. The engine was inspected and ground run, both at idle and at a high power setting. The engine started and operated normally. The EEC and FMU were replaced after conferring with the engine manufacturer. Further engine ground runs were completed and the aircraft was deemed to be serviceable.

Documentation provided by the operator recorded that the EEC part number 114E6112G119, serial number LHBR0148, had accumulated 4,686.4 hours and 4,311 cycles since new. The unit had been modified to software version 6.1.

The engine manufacturer advised that a visual inspection of the unit revealed fracturing of the soldier joints of six resistors of Channel A and four resistors of the Channel B analog interface module circuit boards.

Other overseas occurrence

On 30 November 2002, a USA operator's Boeing 717-200 was on climb at FL 280 when it sustained an in-flight shutdown of the right engine. Following the event, EEC part number 114E6112G119, serial number LHBR0093, which had accumulated approximately 6,700 hours time since new was examined. That examination revealed fracturing of the solder joints at five resistors of Channel A and ten resistors of the Channel B analog interface module circuit board.

Solder joint fracturing

The engine manufacturer reported that the anomaly of fracturing or cracking of the resistor solder joints was believed to have resulted from thermal cycle induced stress due to differential thermal expansion between the printed circuit board and the resistor. They further reported that identical resistor packages were utilised on the installation of both channels within the EEC and that the solder joint fracturing anomaly could affect a total of seven resistors per channel of each EEC. Five of these resistors were assessed as being capable of contributing to the top-level failure events analysed in the unit system safety assessment.

Service bulletin history

On 20 December 2002, the engine manufacturer issued Service Bulletin SB-BR700-73-101401. That bulletin referenced compliance with the EEC manufacturer's Service Bulletin SB-BR715/73-009 also released 20 December 2002, which gave instructions for the repair of several specific resistors on the analog interface module circuit board. That repair would attach the resistors to the board and connect them to the original solder pad by 'flying leads'. This would then eliminate any mechanical stress on the resistors. Compliance time of that bulletin was at the next shop visit of the EEC for repair, or as arranged by the EEC manufacturer and was not mandatory.

On 17 January 2003, the engine manufacturer issued Service Bulletin SB-BR700-73-101404. That bulletin referenced compliance with the EEC manufacturer's Service Bulletin SB-BR715/73-010 also released on 17 January 2003, which gave instructions for a software modification of the processor communication's modules (A3, A4) with new input/output software to change the fill pattern of the unused areas of the EEPROM memory from hexadecimal binary 1s to binary 0s, thereby reducing the possibility of checksum failures. Compliance time of that bulletin was at the next shop visit of the EEC for repair, or as arranged by the EEC manufacturer.

On 20 February 2003, the engine manufacturer issued Service Bulletin SB-BR700-73-900316 advising the fleet operators of a numbers of inspections and modifications to improve the reliability rates of the EEC. The bulletin listed a total of ten service bulletins issued by either the engine or EEC manufacturer, which the engine manufacturer recommended be incorporated at the earliest opportunity without affecting flight schedule. Incorporation of these modifications required a return of the component to the engine manufacturer.

None of those service bulletins were mandated through the issuing of an airworthiness directive from either the USA Federal Aviation Administration or the German Airworthiness Authority.

Summary

The crew of the Boeing 717-200 aircraft reported that during the climb from Launceston airport, while passing 7,000 ft above sea level, the right engine sustained an uncommanded in-flight shutdown. The R ENG RPM LO alert was observed followed by the RH SYS FAIL advisory. The crew reported that they did not see any caution advisories prior to the shutdown. The ENGINE FAIL/SHUTDOWN INFLIGHT checklist was actioned and the crew completed a single engine landing.

Following the event, the operator's maintenance personnel interrogated the multi-function control display unit (MCDU) and carried out a right engine electronic engine controller (EEC) fault review check. A return to service check, a dry motoring run and an engine idle run were carried out with no faults found. A further EEC fault review was carried out and several fault codes were noted in the memory. These related to electronic faults listed for a FADEC SYSTEM FAULT [full-authority digital engine control] and EEC BOX FAULT [electronic engine controller]. After conferring with the engine manufacturer, the EEC and the fuel-metering unit (FMU) were removed for further testing. After replacement of those units, an EEC return to service and an FMU leak check were carried out. At the request of the engine manufacturer, engine ground runs were carried out and the aircraft was deemed to be serviceable.

Occurrence summary

Investigation number 200204444
Occurrence date 04/10/2002
Location 11 km N Launceston, (VOR)
State Tasmania
Report release date 30/06/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Serious Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 717
Registration VH-VQC
Sector Jet
Operation type Air Transport High Capacity
Departure point Launceston, TAS
Destination Sydney, NSW
Damage Nil

Piper PA-32-300, VH-MAR

Summary

At about 1708 Eastern Standard Time (EST) on 26 September 2002, the pilot of a Piper PA-32-300 (Cherokee Six) aircraft, registered VH-MAR, reported taxiing for departure from runway 14 at Hamilton Island, Queensland. The charter flight was to Lindeman Island, a distance of about 15 km to the southeast. On board the aircraft were the pilot and five passengers.

Witnesses to the east of runway 14 at Hamilton Island reported that, shortly after the aircraft became airborne, the engine began coughing and misfiring, before cutting out and then starting again. Shortly after, the aircraft commenced a right turn, and the engine was heard spluttering and misfiring. Witnesses reported that, when part way around the turn, the engine again cut out, and the aircraft descended and impacted the ground.

The aircraft came to rest upright, aligned in an east-north-easterly direction, approximately 300 m to the west of the runway centreline and approximately 100 m south of the departure end of the runway. A severe post-impact fire consumed the majority of the aircrafts fuselage. The six occupants of the aircraft were fatally injured.

The pilot was qualified, appropriately endorsed and authorised for the operation. The pilots condition and demeanour on the day of the occurrence were reported to be normal.

There was no evidence that fuel contamination, amount of fuel carried, structural failure or meteorological conditions were factors in the occurrence.

The engine installed in the aircraft was different from that specified in the aircraft Type Certificate Data Sheet. Notwithstanding, the Civil Aviation Safety Authority (CASA) and the engine manufacturer reported that the installed engine should have been capable of producing the power output expected from the engine certified for installation in the Cherokee Six. Furthermore, the engine had been in service in the aircraft for 126.2 flight hours with no reported power abnormalities, suggesting that, provided there were no defects, the engine should have been capable of producing the required power throughout its operating range.

The extensive damage caused by the impact forces and post-impact fire prevented functional testing of a significant number of aircraft and engine components. On the available evidence, there was nothing found to suggest what may have degraded the engine performance to the extent reported by the witnesses to the occurrence.

Post-mortem toxicological examination of the pilots blood revealed a blood alcohol concentration (BAC) of 0.081%, the presence of an inactive metabolite of cannabis, and an analgesic preparation consistent with a therapeutic dosage. The possibility that the pilots BAC reading resulted at least in part from post-mortem alcohol production could not be discounted.

There was insufficient evidence to definitively link the pilots prior intake of alcohol and/or cannabis with the occurrence. However, the adverse effects on pilot performance of post-alcohol impairment, recent cannabis use and fatigue could not be discounted as contributory factors to the occurrence. In particular, the possibility that the pilot experienced some degree of spatial disorientation during the turn as a combined result of the manoeuvre, associated head movements and alcohol-induced balance dysfunction could not be discounted.

The following factors were considered to have significantly contributed to the occurrence.

  1. Based on witness reports, the aircrafts engine commenced to operate abnormally shortly after lift off from the runway.
  2. The pilot initiated a steepening right turn at low level.
  3. The aircraft stalled at a height from which the pilot was unable to effect recovery.

The operator has initiated a number of safety actions in order to mitigate some of the issues identified in the report. Those actions include the areas of: company pilot training, fatigue management, documentation, and aircraft operations.

The ATSB has issued four recommendations concurrent with the release of this report. The first three recommendations address the potential use of alcohol and drugs by safety-sensitive personnel in the Australian aviation industry, and options to manage the safety risk to the travelling public of that potential use. The fourth recommendation addresses the CASA Air Operator Certificate Safety Trend Indicator surveillance methodology. In addition, two Safety Advisory Notices have been issued to CASA relating to pilot manipulation of the Cherokee Six fuel selector and development by operators of pilot induction training programs.

Occurrence summary

Investigation number 200204328
Occurrence date 26/09/2002
Location Hamilton Island, Aero.
State Queensland
Report release date 18/03/2004
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-32
Registration VH-MAR
Serial number 32-40920
Sector Piston
Operation type Charter
Departure point Hamilton Island, QLD
Destination Lindeman Island, QLD
Damage Destroyed

Boeing 747-4H6, VH-OED, 2 km west-south-west of Los Angeles Airport, on 24 August 2002

Summary

The following text has been reproduced from NTSB Report OPS02SA003 into this incident:

History of Flight

At 0703:50 [UTC], the flight crew of ROK17 contacted the LAX local controller (LC1) and advised they were on a visual approach to runway 6R. Radar data indicated the airplane's radar track was approximately 7 miles west of the airport on a southerly heading. The LC1 controller issued the flight crew a landing clearance for runway 6R and advised that opposite direction traffic was departing the south complex turning southbound at the shoreline. The flight crew acknowledged the transmission.

At 0704:14, the LC1 controller issued the flight crew of QAF108 a take off clearance for runway 25R and advised of opposite direction traffic landing the north complex. The flight crew acknowledged the transmission.

At this point the LC1 controller began assisting the flight crew of Aero Mexico 460, the previous arrival to runway 6R that required assistance exiting the runway. According to the FAA, the LC1 controller walked to the north side of the tower cab (opposite side from the LC1 position) to view the situation. The controller returned to the LC1 position and noticed ROK17 was south of course heading northeast bound and at 0704:55, transmitted to the flight crew, "confirm turning back to six right." The flight crew responded, "affirmative." Radar data indicated the airplane's radar track began a left turn.

The LC1 controller then assisted the flight crew of Aero Mexico 460, who needed additional instructions to exit runway 6R. According to the FAA, the LC1 controller walked to the north side of the tower cab again to view the situation. The controller returned to the LC1 position and noticed ROK17 appeared to be aligned for runway 7L and at 0705:31, instructed the flight crew to "turn immediately north you are lined up for runway seven there's a seven forty seven opposite direction." The flight crew acknowledged the instructions. Radar data indicated the target separation was 4.05 miles and 1,300 feet.

The LC1 controller then instructed the flight crew of QAF108 to turn left heading 210 degrees and advised, "the Boeing seven five seven is moving out of your way." The flight crew of QAF108 responded, "that was close." Radar data indicated the closest proximity between the 2 targets was 1.17 miles and 600 feet.

The LC1 controller reissued the landing clearance to the flight crew of ROK17 and advised QAF108 to change to departure control frequency.

Approximately 2 minutes later the flight crew of ROK17 apologized to the LC1 controller on the frequency and stated that they had made a mistake and were not aligned properly for runway 6R.

ATC Environment

a. Airport Information

The Los Angeles International Airport is located in the northwest suburbs of Los Angeles, California adjacent to the Pacific coastline. The terrain is largely flat to coastal with large expanses of urban areas.

The airport has dual parallel runways. Runways 6L/24R and 6R/24L are referred to as the north complex and runways 7L/25R and 7R/25L comprise the south complex.Runway 6R is 10,285 feet long and 150 feet wide with a displaced threshold of 331 feet. The runway is equipped with high intensity runway lights, runway centerline lighting and medium-intensity approach lighting system with runway alignment indicator lights. According to the FAA, at the time of the incident the appropriate lighting systems for runway 6R were on and operating normally.

b. Tower and ATC Operations

The Los Angeles Air Traffic Control Tower is a Level 12 ATC facility, and is classified as a tower with radar. The tower is centrally located on the airport between the north and south complexes. The tower operation can accommodate 2 local control positions, Local 1 (LC1) and Local 2 (LC2). The LC1 workstation is located on the south side of the tower cab and is typically responsible for arrival and departure operations at the south complex. The LC2 workstation is located on the north side of the tower cab and typically responsible for the arrival and departure operations at the north complex.

At the time of the incident the local control positions were combined at LC1. In this type of configuration the LC1 controller was responsible for operations at both the north and south complexes. LAX was conducting over ocean operations, which consisted of airplanes arriving runway 6R (north complex) and departing runway 25R (south complex). According to the facility's Standard Operating Procedures Manual, LAXT 7110.1B, the operation is used primarily during 0000 and 0630 (Pacific Time) to mitigate noise. During these hours the facility's runway selection program requires the use of the inboard runways (6R and 25R) to the maximum extent possible.

c. Meteorological Information

The LAX surface weather observation at 2350 PDT indicated wind conditions from 240 degrees at 6 knots, visibility 6 statute miles, sky condition clear, temperature 17 degrees Celsius, dew point 16 degrees Celsius, altimeter 29.98 (inches of mercury).

d. Applicable ATC Procedures

I. Visual separation is a means employed by ATC to separate aircraft within airport traffic areas. Tower controllers base separation on observed or known traffic and airport conditions. Visual separation procedures are outlined in FAA Order 7110.65, "Air Traffic Control", paragraph 7-2-1 and states in part:

e. TERMINAL

Visual separation may be applied between aircraft under the control of the same facility within the terminal area up to but not including FL 180, provided:

1. Communication is maintained with at least one of the aircraft involved or the capability to communicate immediately as prescribed in 3-9-3, Departure Control Instructions, subparagraph a2 is available, and:

2. The aircraft are visually observed by the tower and visual separation is maintained between the aircraft by the tower. The tower shall not provide visual separation between aircraft when wake turbulence separation is required or when the lead aircraft is a B757.

II. FAA Order 7110.65, paragraph 2-1-6, Safety Alert states in part:

Issue a safety alert to an aircraft if you are aware the aircraft is in a position/altitude, which in your judgment places it in unsafe proximity to terrain, obstructions, or other aircraft.

Occurrence summary

Investigation number 200204016
Occurrence date 24/08/2002
Location 2 km WSW Los Angeles, Airport
State International
Report release date 06/03/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of separation
Occurrence class Serious Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 747
Registration VH-OED
Serial number 25126
Sector Jet
Operation type Air Transport High Capacity
Departure point Los Angeles, USA
Destination Sydney, NSW
Damage Nil

Aircraft details

Manufacturer The Boeing Company
Model 757
Sector Jet
Departure point Unknown
Destination Los Angeles, USA
Damage Nil