Grounding of the Greek registered ship Doric Chariot

Final report

Summary

On 26 July 2002 Doric Chariot sailed from Hay Point, Queensland on a voyage to India via the Great Barrier Reef inner passage and Singapore. A pilot was engaged for the Reef passage.

The voyage initially proceeded normally and, on 29 July, as the ship approached Eel Reef light, the pilot requested a slight course alteration to allow more sea room for passing a south-bound ship. After passing this ship the pilot requested another course adjustment to bring the ship back toward the planned track. He then spoke with the OOW (Officer of the Watch) about the time he should next be called and sat on the daybed at the side of the wheelhouse to take a rest before the ship arrived at the next reporting position near Piper Reef.

The ship continued under the direction of the OOW until the pilot was next called. When the pilot stood up and looked at the ship's position with reference to the two beacons ahead at Piper and Inset Reefs, he immediately realised that the ship was to the west of the two-way route and approaching the southern end of Piper Reef. He ordered, 'hard-a-starboard' and, shortly afterwards 'full astern' but it was too late. The ship started to swing to starboard but, within about one and a half minutes, at about 0335, the ship ran aground to the south of Piper Reef light.

The ship was successfully refloated on 6 August 2002. No injuries or pollution resulted from the grounding.

The report concludes that the pilot:

  1. sat down intending to rest but fell asleep, in an inappropriate area of the pilotage passage;
  2. instructed that he should next be called in a position too close to the approaching dangers for any successful corrective action to be taken should it be required;
  3. was likely to have been experiencing a significant level of fatigue, based on the FAID program measurement, that affected his performance. This was predominantly as a result of his personal fatigue strategies before and during the passage and;
  4. did not provide the OOW with sufficient clear, unambiguous, instructions regarding the course between Eel Reef and Piper Reef and made assumptions as to the OOW's actions that were not justified.

The report also concludes that the OOW:

  1. did not maintain an effective visual watch and allowed Doric Chariot to stray from the intended course;
  2. did not adjust the ship's course to follow the route drawn on the chart;
  3. did not fix the ship's positions at intervals that were consistent with safe navigation and;
  4. did not fully understand the pilot's intentions.

Additionally,

  1. The bridge resource management exercised by the pilot and the OOW was ineffective.

The report makes three recommendations involving clearer understanding between pilots and officers; a fatigue management policy by pilots; and a paper to the IMO.

Occurrence summary

Investigation number 182
Occurrence date 29/07/2002
Location Piper Reef (North QLD)
State Queensland
Report release date 25/09/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Marine
Marine occurrence category Grounding
Occurrence class Incident
Highest injury level None

Ship details

Name Doric Chariot
IMO number 9075670
Ship type Bulk Carrier
Flag Greece
Departure point Hay Point, Qld
Destination India

Fatality aboard Western Muse

Final report

Summary

At 0712 on 18 June 2002, the Panama flag bulk carrier Western Muse berthed at Port Kembla, NSW, to load a cargo of steel slabs and coils for Pohang in South Korea. The vessel had been chartered for the voyage by BHP Transport and Logistics.

The cargo was to be loaded using the ship's cranes. The master was advised to ensure that the cranes and wires were in good condition as they would be inspected by the stevedores before being used. Before the vessel's arrival at Port Kembla, after checking the cargo gear, both the master and mate were satisfied that the cranes and wires were in good condition.

The stevedore's inspection of the cargo gear started soon after the vessel had berthed, but unsuitable weather conditions led to only one crane being checked that day. The next morning the other cranes were inspected and, as a result, the mate was told to change the cargo wire of no. 2 crane.

During the remainder of that day, the crew carried out the task of changing the wire. Much of the work was carried out from the platform on top of the crane, requiring the use of safety belts.

By about 1745 the wire had been changed. The bosun, who was on the platform on top of the crane, gave the order for the operation of the crane to be checked. He then released the clip on the rope lanyard attached to his safety belt from railing on the platform. At the same time, the deck cadet, who had been operating the crane, raised the cargo hook, then the jib.

The lanyard on the bosun's safety belt was drawn into the sheaves for the jib, dragging the bosun in between the sheaves and the luffing wire. He screamed out and one of two seamen with him immediately shouted to the cadet, by handheld radio, to stop the crane.

By the time the bosun was freed, he was haemorrhaging severely from wounds to his leg and pelvis. The master asked for ambulance assistance and, by about 1830, paramedics and a police rescue squad were in attendance on the ship. Soon afterwards, one of the paramedics advised the master that the bosun was dead.

The police forensic squad arrived to carry out their work and, at about 2230, the bosun's body was removed from the top of the crane and taken to the mortuary. The interim post-mortem report stated that the cause of death of the bosun was massive traumatic injuries resulting in amputation of the left leg and the side of the pelvis.

The ATSB investigation concludes that, among other factors contributing to the incident:

  • The task of changing the wire was physically and mentally demanding, possibly causing the bosun's concentration to lapse at the end of the day;
  • It is probable that the bosun was concentrating on the cargo wire and that he was not watching the luffing wire after he released the lanyard on his safety belt. In addition, poor light would have made it difficult to see any detail on the platform.

This report recommends that:

  • In accordance with the objectives of the ISM Code, companies, in addition to documenting preventive maintenance procedures, also develop, document and implement associated safety procedures;
  • Procedures and precautions for personnel working aloft include warnings that loose clothing or personal safety equipment might become entangled in moving machinery.

Conclusions

These conclusions identify the different factors contributing to the incident and should not be read as apportioning blame or liability to any particular individual or organisation.

Based on the evidence available, the incident occurred due to a combination of the following factors:

  1. After the bosun released the rope lanyard on his safety belt, the lanyard became entangled in the luffing wire or was drawn into the sheaves for that wire, dragging him in between the sheaves and the wire.
  2. The task of changing the cargo wire, in addition to being arduous and lengthy, was physically and mentally demanding, possibly causing the bosun's concentration to lapse at the end of the day.
  3. The conditions of lighting under which the crew were operating at the top of the crane would have made it difficult to see any detail on the platform.
  4. It is likely that the bosun was concentrating on the movement of the cargo wire and that he omitted to watch for movement of the luffing wire.
  5. Though the mate had signed a permit to work that morning, the conditions for the permit were not re-assessed once darkness had fallen.
  6. While the company and the ship had the necessary ISM accreditation, the safety manual contained no precautions or procedures for the crew when working in close proximity to moving machinery on cranes.

In addition, although not a contributing factor, the Inspector concludes that the condition of the wire that was renewed did not meet the requirements of Marine Orders Part 32. The wire was not fit for use and, hence, did require replacing.

Occurrence summary

Investigation number 179
Occurrence date 19/06/2002
Location Port Kembla
State New South Wales
Report release date 01/05/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Marine
Marine occurrence category Fatality
Occurrence class Serious Incident
Highest injury level Fatal

Ship details

Name Western Muse
IMO number 9234214
Ship type Bulk carrier
Flag Panama
Departure point Port Kembla, NSW
Destination Pohang, South Korea

SA Fortius contact with the number two coal loader at Pt Kembla

Final report

Summary

At 1148 on 15 April 2002, the Bahamas flag bulk carrier SA Fortius arrived off the New South Wales port of Port Kembla. The ship's deadweight was 88 674 tonnes at a mean draught of 10.655m and it was trimmed almost 3 metres by the stern.

At 1300 the pilot embarked, and the ship proceeded inwards to the number two coal loader, in the inner basin. The intention was for SA Fortius to enter the outer harbour, pass through the 'Cut' and turn to starboard through some 230 to berth, on a southerly heading, at the coal loader in the eastern basin. The wind speed was about ten knots from the south-southeast.

Approaching the breakwater, four tugs were made fast, one on a tow line through the forward centre Panama lead, two tugs alongside on the starboard side (one forward, the other aft) and a tug aft, on a line led through a stern Panama lead, on the port side.

The passage to the inner harbour apparently proceeded without incident. Once in the inner harbour the pilot initiated the turn to starboard utilising the ship's engine, rudder and the two forward tugs. The tug made fast through the forward Panama lead towed the bow to starboard, while the forward tug on the starboard side was used to slow the ship by coming astern.

After the ship had turned through some 90 it became apparent to the pilot that SA Fortius was experiencing a significant drift angle1. The master of the stern tug became concerned as SA Fortius's stern was closing on the multi-purpose berth and the dolphin at the southern end of the grain berth. He anticipated that the next order from the pilot would be for his tug to take the stern to port and he positioned the tug forward of the beam, between the ship and the dolphin.

The ship maintained headway, contacting the third fender from the southern end of number two coal berth on a heading of about 078 (T).

At, or immediately after, the time of contact the pilot ordered the two stern tugs to take the ship's stern to starboard. The stern tug however, had become temporarily trapped between the grain berth dolphin and the ship and sustained damage to its fenders forward and aft. At this time the tug positioned on the starboard side aft parted its tow line. The ship maintained a reduced rate of turn and cleared both the grain berth dolphin and number two coal berth, which had sustained damage in the initial contact.

SA Fortius was directed to berth at number one coal berth, where it completed mooring at 1523.

This report concludes that:

  1. SA Fortius developed a large drift angle, which resulted in the ship being too far to the north in the turning basin.
  2. The drift angle was not detected by the pilot.
  3. The engine was put to 'slow ahead' at about 1356, when the intended engine order was 'slow astern'.
  4. The pilot did not take sufficient notice of the tachometer and rudder angle indicator.
  5. The bridge team work was negligible, resulting in a breakdown of effective and safe communications between the pilot and the ship's staff on the bridge.
  6. The master did not take sufficient steps to ensure that he was aware of the intended manoeuvre in the inner basin.
  7. There was a lack of specific direction to the tugs by the pilot. He did not follow the 'Standard Orders to Tugs' issued by the Port Kembla Port Corporation in December 1999.

The report recommends that:

  • Pilots use the procedures as laid out in 'Standard Orders to Tugs' issued by the Port Kembla Port Corporation in December 1999, when directing tug manoeuvres.
  • Port authorities, where not otherwise equipped, should consider the introduction of an electronic aid, with track prediction capability, to assist pilots with the berthing of ships.
  • All ports should consider publishing their general port entry and berthing manoeuvre plans on the Internet. This would provide port users with direct access to port information (or indirect access through ship's agents), permitting masters and officers to plan passages as recommended in the International Chamber of Shipping's 'Bridge Procedures Guide'.
  • Periodic meetings between pilots and tug masters be reintroduced at an operational level.
  • When piloting ships, pilots should consider means by which they can verify all orders given by them.

1 With the bridge aft, drift angle is the angle between the ship's heading and the direction in which the ship's bridge is travelling. Rowe, R.W. (1996) The Shiphandler's Guide, Nautical Institute.

Occurrence summary

Investigation number 178
Occurrence date 15/04/2002
Location Port Kembla
State New South Wales
Report release date 18/03/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Marine
Marine occurrence category Contact
Occurrence class Incident
Highest injury level None

Ship details

Name SA Fortius
IMO number 9221217
Ship type Bulk carrier
Flag Bahamas
Departure point Newcastle, NSW
Destination Port Kembla, NSW

Grounding of the Panama registered bulk carrier La Pampa

Final report

Summary

At about 0624 on 27 March 2002, the Panama flag bulk carrier La Pampa sailed from the Clinton Coal Terminal at Gladstone for Fos in France. A pilot was on board and three tugs assisted the ship off the berth. The vessel was loaded with 160 927 tonnes of coal and had a deepest draught of 17.825 m.

Both main steering pumps were tested satisfactorily before departure and were running when the vessel sailed. At about 0650, just before the tugs were released, a steering alarm sounded. The rudder was stopped at hard to port, but the problem quickly seemed to resolve itself. Then, at about 0710, by which time the tugs had been released and had returned to their berth, the steering alarm sounded again.

The steering continued to operate as the chief engineer went to the steering flat to investigate. There he found that both main hydraulic inlet and outlet lines on number one steering pump were leaking large quantities of oil under pressure. This pump was stopped and then restarted but at about 0712 the steering failed. The pilot asked for tug assistance, while the chief engineer tried, unsuccessfully, to operate the emergency steering system.

At 0714, before the tugs could assist the ship, La Pampa grounded on the northern side of the channel. At 0722 the vessel was refloated with the assistance of the tugs and was anchored at an emergency inner anchorage. Tank soundings established that number one double bottom ballast tank was taking in water and the ballast and stripping pumps were started to control the ingress of water. During this time the chief engineer was checking the steering gear and discovered pieces of piston seal from one of the hydraulic rams lodged in a control valve.

Later in the day the decision was made to shift the ship to the outer anchorage. At 1820, with number two steering pump operating, the anchor was weighed. La Pampa proceeded outward with three tugs in attendance but, at 1904, the steering failed once again. The vessel then had to be assisted by the tugs to the outer anchorage where it was anchored at 2345. Repairs to the hull and steering gear were then undertaken.

The Australian Maritime Safety Authority (AMSA) detained the vessel until 14 April when repairs to the steering gear were complete and they were satisfied that the vessel was seaworthy.

The report concludes that:

  • the grounding was caused by a major failure of the steering gear.
  • the steering gear failure was due to the disintegration of the piston seals in the starboard steering rams.
  • the failure of the seals on the suction and discharge ports on number one steering pump was the result of an over pressurisation caused by debris from the failed piston seals being passed into the hydraulic system.
  • the failure of the piston seals in the starboard steering rams meant that the steering system could not be operated using either the emergency pump or number two steering pump without isolating these rams.
  • The master did not direct anybody to inspect the steering gear when the initial, transitory, malfunction occurred at 0650

The report recommends that:

  • Port authorities consider the risks associated with the passage of deep draught vessels within their ports and have appropriate contingency plans in place to deal with foreseeable emergencies.

Occurrence summary

Investigation number 176
Occurrence date 27/03/2002
Location Gladstone
State Queensland
Report release date 30/06/2004
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Marine
Marine occurrence category Grounding
Occurrence class Incident
Highest injury level None

Ship details

Name La Pampa
IMO number 9000649
Ship type Bulk carrier
Flag Panama
Departure point Clinton Terminal, Gladstone
Destination Fos, France

Collision involving Forum Samoa II and Seabreeze II

Final report

The collision

At 0401 on 11 April 2002, the fishing vessel Seabreeze II collided, bow on, with the starboard side of the general cargo ship Forum Samoa II. There were no injuries to any person on either vessel, but the collision resulted in damage to the bow of the fishing vessel, which returned to port for repairs.

Neither vessel was keeping an adequate lookout before the collision and this report, as do many previous reports of collisions, emphasises the need for all vessels to maintain a proper lookout at all times.

Occurrence summary

Investigation number 177
Occurrence date 11/04/2002
Location Cape Morton
State Queensland
Report release date 22/12/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Marine
Marine occurrence category Collision
Occurrence class Incident
Highest injury level None

Ship details

Name Seabreeze II
IMO number N/A
Ship type Fishing vessel
Flag Australia
Departure point Mooloolaba, Queensland
Destination North-north-east of Cape Moreton

Ship details

Name Forum Samoa II
Ship type Cargo ship
Departure point Fisherman Islands in Brisbane
Destination Sydney

Serious injury to a crew member on board CSL Pacific

Final report

Summary

At 1800 on Sunday 17 February 2002, the bulk carrier CSL Pacific sailed from Melbourne after discharging a cargo of furnace slag. The ship was bound for Adelaide to load a cargo of powdered cement.

At 0750 on Monday morning, the chief engineer, deck mechanic and deck fitters met to discuss their major work for the day which was to repair some of the buckets on number one bucket elevator.

Prior to starting work, the deck mechanic went to number one control room and checked that the circuit breaker for the main electric motor on the bucket elevator was open. He did not place a danger tag on the circuit breaker.

The same morning, the boatswain and seamen had started to prepare cargo holds one and two to receive the powdered cement cargo in Adelaide. The seamen were sweeping the residue of the slag cargo from the bottom of the holds into the bucket elevators. This work was being performed under the supervision of the mate who was periodically running number two bucket elevator for short periods to provide the men with empty buckets to fill.

At about 1100, the boatswain, working in the bottom of number two hold, requested that the mate rotate number two bucket elevator. At this time a deck fitter was working inside the top of number one bucket elevator. He was lying with his torso inside the bucket with one foot resting on one of the drive chains as he was welding.

The mate went to number two control room and ran the bucket elevator for a couple of seconds. He then went to number one control room to check on the cleaning in number one hold. While there he decided to run the bucket elevator to provide an empty bucket for the man working there and went to the circuit breaker for the drive motor. Finding no danger tag, he closed the breaker and then ran the motor for 2-3 seconds. Although he had been told about it earlier, he had forgotten about the work being performed at the top of number one bucket elevator.

The fitter welding inside the bucket elevator sustained serious injuries when the bucket elevator moved. His right hip had been dislocated, his pelvis and a vertebrae had been fractured, two ribs were broken, and he had some ligament damage in the groin area.

Help was quickly at hand and the injured fitter was lifted out of the bucket elevator and taken on a stretcher to the ship's hospital where he was examined by the second mate. It was evident that the fitter's injuries were serious. The master organised a telephone consultation with a surgeon from the Royal Adelaide Hospital who advised him to land the fitter as soon as possible. After speaking to the ship's manager and the Adelaide agent the decision was made to divert the ship to Portland, Victoria.

CSL Pacific arrived off Portland at 1740. At 1800 the injured fitter was transferred to a pilot launch and then to Portland base hospital. The deck fitter spent the next six weeks in Portland base hospital recovering from his injuries before being repatriated on 2 April 2002.

Occurrence summary

Investigation number 175
Occurrence date 18/02/2002
Location Off Portland
State Victoria
Report release date 17/02/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Marine
Marine occurrence category Injury
Occurrence class Incident
Highest injury level Serious

Ship details

Name CSL Pacific
IMO number 7420716
Ship type Bulk carrier
Flag Bahamas
Departure point Melbourne, Vic
Destination Portland, Vic

Lancair IV-T, VH-CIV, 6 km north-east of Drysdale, Victoria, on 20 December 2002

Safety Action

Local safety action

The Sports Aircraft Association of Australia (SAAA) announced in July 2003 that it is scoping the development and implementation of a four-stage flight safety assistance program for members. The program adopts some of the existing programs run by the association and will develop into a broader program incorporating aspects not currently covered.

The intention is to encourage members to sign onto the total program while still giving them the choice under the experimental rules.

During July /August 2003, the Association's technical coordinator travelled overseas to meet with United States of America Experimental Aircraft Association officials to discuss that organisation's flight advisor program.

An outline of the SAAA intended program was introduced to SAAA members in October 2003.

The Association will also include a note and link to this report on its website www.saaa.com.

Analysis

Planned activities on the 9 December 2002 flight had indicated that the aircraft became laterally unstable as the aircraft approached the stall speed. Recorded flight data indicated that the aircraft also entered a stall during the flight on 9 December, even though this was not planned. It is possible that this stall was an unplanned activity. There was no evidence that any of the aircraft's performance and handling characteristics encountered in this unplanned stall, such as stalling airspeed, were considered when preparing for the flight when the accident occurred, when stalls were part of the test program.

Lateral instability, as the aircraft speed approached the stall speed, had been experienced and noted in a previous flight. The test flight program did not include a lateral stability test for the flight and the recorded aircraft data did not indicate that a lateral stability test had been undertaken on the flight. It is possible that the notes referred to a tendency for the aircraft to drop a wing as it approached the stall, or stalled, as similarly experienced during the accident flight.

During the flight when the accident occurred, the aircraft departed controlled flight from a deliberately induced stall during a test flight. The aircraft then descended rapidly, at an airspeed that was not consistent with a stalled or spinning configuration.

The aircraft instruments displayed a stall speed that was significantly below the actual stall speed in that configuration. It is possible that the stall occurred before the flight crew expected it.

The aircraft was based on an established aircraft design, but had significant design changes from the original. Those design changes were likely to have changed the performance and handling characteristics of the aircraft and the cumulative effect of those changes would have been hard to predict.

The test flight program had been developed in accordance with some of the approved advisory material. The advisory material gave detailed guidance on what was to be done, and how it should be done. It did not give detailed guidance on defining what should be expected during the test program, and what to do if something unexpected occurred during the program. As an example, a particular aircraft design is normally expected to stall at a particular airspeed for a given configuration and flight condition. The particular handling characteristics as the aircraft approaches and passes through a stall should also be predictable and expected. When these characteristics are examined during a test flight, they would be expected to fall within a defined range. The guidance material did not detail what to do if any of the performance or handling characteristics were outside the expected ranges.

There was no evidence of a significant risk management process, other than preflight briefings conducted by the pilot of the first two flights, throughout the design, construction, or test flight program development for the aircraft. Such a program could have assisted in identifying hazards and their attendant risks, and for managing them appropriately from initial construction though to certification. While there was no requirement for an owner/builder to have a risk management process, such a process would have been prudent considering the significant changes made to the aircraft.

The test program did not incorporate flight instrument calibration and therefore the accuracy of the flight instruments was unknown. It would not have been possible to confidently establish the exact speeds at which the aircraft's handling and performance were assessed.

The test flight program only required one person on board the aircraft for test flights. The investigation was not able to identify an operational reason for the owner/builder to be on board the aircraft.

Factual Information

History of the flight

The Lancair, registered VH-CIV, was a homebuilt aircraft operating under an experimental certificate of airworthiness. The owner had recently built the aircraft and had commenced a test flight program. The aircraft departed with a test pilot occupying the pilot seat, and the owner/builder occupying the right seat. Witnesses reported seeing the aircraft flying in the Drysdale area before descending steeply. It subsequently impacted the ground and the two occupants were fatally injured.

The pilot departed from Point Cook and flew along the coast, southwest of Point Cook aerodrome, at altitudes between 3,000 ft and 4,000 ft. After crossing Port Phillip Bay to the Bellarine Peninsula the pilot climbed the aircraft to between 5,000 ft and 6,000 ft. Recorded flight data indicated that the aircraft was slowed, and stalled at an altitude of 5,200 ft. The pilot recovered from the stall, but the aircraft entered another stall during the recovery at 4,950 ft. The pilot recovered the aircraft from that stall, and then repositioned it and entered a third stall at an altitude of 6,200 ft. The aircraft rolled at the initiation of the stall, and continued to roll as it then descended rapidly, accelerating to approximately 150 kts at an angle of approximately 40 degrees from the horizontal, with low engine power. The engine power increased shortly before the aircraft impacted the ground.

The aircraft impacted the ground upright, with the wings level, at a pitch angle of 40 degrees nose down. The landing gear was retracted at the time of impact, and the flaps were either completely or nearly retracted. There was no indication of any mechanical failure prior to impact. The accident was not survivable.

Flight crew

The pilot was an experienced ex-military pilot with 6,500 hours total aeronautical experience, including experience over many years in aircraft with a wide range of performances.

The owner/builder had a Commercial Pilot (Aeroplane) Licence issued 16 October 2001. He had 352 hours total aeronautical experience in a range of general aviation aircraft with a level of complexity and performance up to four-seat single-engine aircraft, with a constant speed propeller and retractable landing gear.

Aircraft

The aircraft was originally being constructed to comply with the requirements of Civil Aviation Safety Authority (CASA) Civil Aviation Order (CAO) 101.28. During construction, the experimental designation concept was developed and the aircraft construction was subsequently changed and completed in accordance with the experimental designation under Advisory Circular (AC) 21.4(2) issued September 2000. The certification requirements in the experimental category were less prescriptive than those in CAO 101.28 as experimental aircraft are not type-certificated. 'Experimental' is not a category but rather a designation. It is also important to note that an experimental certificate does not attest to an aircraft being fully airworthy (Civil Aviation Safety Authority Advisory Circular 21.1(1) - Aircraft Airworthiness Certification Categories and Designations Explained - Revised December 2000).

The aircraft was based on a Lancair IV-T kit plane that was originally designed to use a high-performance piston engine. The owner/builder decided to replace the engine with a turbo-propeller engine and sought assistance from a number of people to redesign the aircraft to accommodate the new engine.

Documentation indicated that during construction, numerous changes had been made to the original design, including the engine type and the design of the aircraft from the firewall forward. The propeller had been modified by removing 20 cm of the propeller tips. No evidence was found to indicate that any form of risk assessment had been undertaken to consider the safety implication of these aircraft design changes. A risk assessment was not required for aircraft constructed under the experimental designation.

Aircraft equipment

The aircraft was equipped with an integrated electronic flight information system (EFIS) comprised of a number of data acquisition units and three liquid crystal multi-function display (MFD) units, that could be configured to present operational information in different ways. The instrumentation system received data from a variety of sources, and integrated that data to present operational information to the pilot. Each MFD also contained a memory unit that recorded information that was sent to it. This information was used by the ATSB to determine the flight profile prior to the accident.

The MFDs could be selected by the pilot to display primary flight information, navigation information, or engine system information. The primary flight information consisted of an electronically generated artificial horizon display upon which a number of other information displays were overlayed. Indicated airspeed (IAS) was also displayed on the left side of this display. The IAS was presented as a vertical tape display of airspeed with a range of approximately 100 kts, in increments of 10 kts. The actual airspeed was also displayed numerically on the left side of the artificial horizon display, adjacent to the IAS speed tape display. The airspeed tape display contained a number of coloured regions to indicate various speed ranges and included the stall speed of the aircraft. The stall speed was dynamically generated and changed with varying flight loads on the aircraft. The displayed stall speed was known as the G-corrected stall speed. The EFIS derived the G-corrected stall speed from the aircraft's static 1G stall speed. The 1G stall speed had to be manually entered into the EFIS. The aircraft instrumentation system had been programmed with a 1G indicated stall speed of 69 kts with flaps and landing gear retracted.

The aircraft was also equipped with a video camera mounted on the ceiling just behind the two front seats, which was aimed at the instrument panel. This camera operated for some of the test flights, and some of the recordings were recovered from the camera after the accident.

The original aircraft design (with a piston engine) had a declared indicated stall speed of 84 mph, or 73 kts with flaps and landing gear retracted. The Comparative Aircraft Flight Efficiency (CAFE) foundation test flight of this version of the aircraft type recorded a stall speed of 78 kts with flaps and landing gear retracted. That test flight was conducted with a calibrated pitot/static boom, so the indicated airspeed would have been accurate in that instance. A theoretical aerodynamic calculation for the accident aircraft indicated a stall speed of 82 kts. Recorded information indicated that the aircraft stalled at 82 kts at the commencement of the accident sequence.

A flight path marker symbol, in the centre of the primary flight display, indicated the current pitch attitude of the aircraft. At an airspeed of 20 kts above the G-corrected stall speed, an amber pitch limit indicator symbol appeared above the flight path marker. The pitch limit indicator symbol moved down toward the flight path marker symbol as the airspeed decreased towards the stall speed. At 5 kts above the stall speed, the pitch limit indicator symbol turned red. At the point of stall, the pitch limit indicator symbol overlayed the flight path marker symbol. Coincident with the pitch limit indicator symbol changing to red, an aural annunciator would repeat a voice warning of 'stall' and a red stall flag symbol would display in the bottom left corner of the primary flight display.

The aircraft was also equipped with an angle of attack sensing device that used pressure information from two ports on the upper and lower sides of the left wingtip to derive the angle of attack. This instrument could have indicated when the aircraft was approaching a stall. The investigation did not determine if it had been calibrated before the accident flight.

During a test flight on 9 December 2002, the test pilot had decelerated the aircraft until it was approaching the stall as a part of the test flight program. Written records from that flight noted:

'A/c [aircraft] becomes laterally unstable below 80 Kts.'

Recorded flight data indicated that the aircraft stalled three times during this flight, from speeds of 72, 75 and 76 kts. The test pilot had also noted:

'Close to stall at 75 Kts with 10 [degrees] flap
Close to stall at 72 Kts with full flap'.

Video recordings from the flight indicated that the aircraft had stalled, and rolled 45 degrees to the left, and then 45 degrees to the right of horizontal during the recovery from the stall. Stalls were not a part of the test flight program for the flight.

Test program

A friend of the owner/builder developed a program for the flight testing of the aircraft. That program followed the guidelines in the Federal Aviation Administration (FAA) Advisory Circular 90-89A - Amateur-built Aircraft and Ultralight Test flighting Handbook. The CASA Advisory Circular 21.4(2) - Amateur Built Experimental Aircraft - Certification, advised that CASA:

'...most strongly urges [Amateur-built experimental aircraft builders] to make detailed reference to [this document], prior to their flight programs commencing, and [to] follow the guidance provided.' (section 14.4).

The test flight program was detailed, and was clearly developed in accordance with the recommendations of Advisory Circular 90-89A. Neither the advisory material, nor the test flight program considered action to be taken if aircraft handling or performance produced unexpected results.

CASA Advisory Circular 21.4(2) stated:

'14.5 Those undertaking test flight programs may also derive benefit in consulting the following additional references, as applicable to the class of aircraft involved:

'(a) CAA publication dated January 91, Flight Test Guide for Certification of CAO 101.28 Category Aeroplanes...'

This document recommended calibration of aircraft flight instruments, so that the limits of the flight envelope could be accurately determined. The test flight program for the accident aircraft did not include the in-flight calibration of aircraft flight instruments, including the airspeed indicator. Comparison of the recorded airspeed from the satellite navigation system, fitted to the aircraft as apart of the EFIS, with the recorded airspeed from the pitot/static system showed no inaccuracy in airspeed indication.

There was no evidence that any significant risk assessment was undertaken during construction of the aircraft and in the development of the test flight program. Such a risk assessment could have examined the planned activities and considered any potential hazards for their likely impact on the aircraft's safety during test flights.

The friend who developed the test program stated that he conducted the first two flights of the aircraft, but subsequently did not participate any further in the test program. Prior to those initial flights, he conducted an operational pre-flight briefing with the owner. These briefings included hazards and potential actions. The investigation did not determine whether the test pilot for the accident flight conducted similar operational pre-flight briefings for subsequent flights.

There was no evidence that any significant re-evaluation of risk was done during the subsequent conduct of the test flight program. Such a risk assessment process could have examined the results of test flights for hazards that became apparent from analysis of observations and data from each flight. This could have allowed for a considered assessment of any risk mitigators for their likely impact on the aircraft's safety during subsequent test flights, as the aircraft flight envelope was expanded. For example, if unexpected handling characteristics had been encountered during a stall sequence, then previously identified mitigation procedures, such as moving the centre of gravity forward, could have been considered.

Aircraft design

An aircraft operated as an experimental aircraft does not have to comply with any specific design. Builders may comply exactly with a design, or may deviate from that design as much as they wish, or may build an aircraft independent of any previously developed design.

If an aircraft is built mainly in accordance with an established design, but with some design differences, then it may perform differently from an aircraft built exactly in accordance with that established design. If design differences are incorporated one at a time, then it is possible to measure the effect of any single design difference. If many design differences are incorporated at one time, the effect of a single design difference on the behaviour of the aircraft may be impossible to predict due to the compounding effect of other incorporated design differences. The accident aircraft had been constructed with many differences compared with the original Lancair IV-T design.

Required persons on board during test flights

A CASA delegate had issued a special certificate of airworthiness authorising flight in accordance with the test flight program. The approval included operating limitations for the test flight program, such as geographical limitations, minimum weather conditions for flight and the maximum number of persons to be on board the aircraft.

Test flights are hazardous compared with normal flight. Accordingly, there is normally a requirement for only operational persons to be on board an aircraft during a test flight. The special certificate of airworthiness under which the accident flight was made stated 'Only personnel essential for the conduct of the testing may fly on board the aircraft. The carriage of passengers is prohibited.'

This aircraft type was normally flown as a single crew operation, and the cockpit of this aircraft was configured for single crew operation. There was no evidence that the test flighting required two persons on board.

Occurrence summary

Investigation number 200206005
Occurrence date 20/12/2002
Location 6 km NE Drysdale
State Victoria
Report release date 04/11/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Neico Aviation Inc
Model Lancair IV-T
Registration VH-CIV
Sector Piston
Operation type Private
Departure point Point Cook, VIC
Destination Point Cook, VIC
Damage Destroyed

Cessna 210K, VH-RTH

Summary

The commercial pilot had hired a privately owned Cessna 210 for a flight to Killiecrankie on Flinders Island with two family members and two friends. After arriving overhead, the aircraft was positioned on downwind for a downhill landing on strip 27 at Killiecrankie. The pilot commented that there appeared to be no wind, which he determined from the windsock and the conditions prevailing on the ground, from the water in the bay and the stillness of the trees. A pilot on the ground, who is the owner of and responsible for the airfield maintenance and who witnessed the accident, reported that the wind was easterly at about 15 knots at tree top height, although probably less on the ground. The witness said that the sock was damaged, but it was still possible to determine the wind direction from environmental cues.

A passenger on the aircraft reported that he did not detect any indications of strong wind on the surface of the water or significant movement of the trees or foliage as the aircraft approached the threshold of the strip.

The pilot reported that on late downwind he configured the aircraft for landing with the first stage of flap and landing gear extended and turned the aircraft onto the final approach at approximately 800 ft above ground level. Although this was higher than normal for a turn onto final, he considered it to be okay. Full flap was lowered and the power reduced for landing.

As the aircraft neared touchdown well down the strip, the pilot considered it to be a late landing but still with sufficient length remaining for braking. The aircraft touched down and bounced twice into the air before the pilot applied power for the go-around. The witness reported that the aircraft initially touched down about two thirds of the way along the 1,400 metre strip before bouncing and then going around.

The pilot reported that although he applied full power, the aircraft did not accelerate to take off speed and did not gain sufficient height to clear the trees beyond the end of the strip. The passenger reported that as the aircraft approached the end of the strip during the go-around, it appeared to dip slightly as if affected by a gust of wind. The aircraft impacted the trees in a nose-up, wings-level attitude at full power, before the pilot reduced the power to idle. The fuselage remained upright during the impact sequence.

While the evacuation was taking place the aircraft began to burn and as the last passenger was exiting, the aircraft was almost totally engulfed in flames. All passengers evacuated through the main doors. The post-impact fire destroyed the aircraft. The pilot reported that prior to the flight he had thoroughly briefed the passengers on the emergency exits and the evacuation procedure.

The pilot later commented that he felt that the following factors contributed to the accident:

  1. Although he had landed at Killiecrankie before and was aware of the downhill slope to the west, it was about 12 months prior to the accident.
  2. The damaged windsock did not display the wind strength as accurately as an undamaged windsock would have.
  3. He unwittingly initiated a tailwind go-around with insufficient strip remaining.

Occurrence summary

Investigation number 200205901
Occurrence date 17/12/2002
Location Killiecrankie (ALA)
State Tasmania
Report release date 20/05/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 Serious

Aircraft details

Manufacturer Cessna Aircraft Company
Model 210
Registration VH-RTH
Serial number 21059327
Sector Piston
Operation type Private
Departure point Latrobe Valley, VIC
Destination Killiecrankie, TAS
Damage Destroyed

Boeing 747-438, VH-OJU

Safety Action

The engine manufacturer issued Service Bulletin SB72-E181 on 6 August 2003 to provide a long-term solution to the uneven blade root friction problem. That SB introduced a revised dry film lubricant (DFL) to be used as an alternate blade root lubrication coating. Incorporation of the SB is indicated by a change in blade part number.

The manufacturer has also revised the manufacturing process for the HPC blades, changing the blade root machining process from broaching to milling.

A new design HPC blade drum has been developed to prevent blade loading slot cracking. Service Bulletin SB72-E106 was issued on 7 March 2003 to include the application of the improved DFL to the first stage HPC blade root dovetails of those blade drums at manufacture.

As an interim measure, the manufacturer has revised the inspection limits for blade root damage and scores, and has instigated blade root DFL removal and replacement at each module overhaul. An ultrasonic, non-destructive-inspection procedure, that can detect blade root cracking without removing the engine from the aircraft, has also been developed.

The manufacturer reported that an update to these solutions would be supplied to all operators.

Technical Analysis

Technical Analysis Report: Examination of an RB211-524G-T Turbofan Engine Compressor Failure

Boeing 747-438, VH-OJU

EXECUTIVE SUMMARY

An Australian registered Boeing 747-438 aircraft operating a regular passenger transport flight sustained the failure of an engine shortly after take-off from Los Angeles, USA. The engine was subsequently shut-down and the aircraft returned for an uneventful landing.

The failed engine was a Rolls Royce RB211-524G2-T model. Preliminary inspection by the operators maintenance personnel found evidence of extensive internal mechanical damage within the high-pressure compressor section of the engine and as a result, returned the engine to Australia for inspection and overhaul.

The Australian Transport Safety Bureau examined the engine following its disassembly into primary modules. The engine had failed as a result of the liberation of a single blade from the first-stage high-pressure compressor section. That failure subsequently precipitated a titanium metal fire within the compressor, extensively damaging the following stages and rendering the engine inoperative.

The engine manufacturer has attributed three previous failures of RB211 high-pressure compressors to the loss of blades from the first-stage rotor. The blade losses were all associated with fatigue cracking of the dovetail root connection. The manufacturer identified uneven centrifugal loads on the blade roots as a significant factor in the development of blade cracking; possibly exacerbated by patchy root friction and minor mechanical imperfections in the critical blade root transition region.

Evidence from the current investigation indicated the nature of the failure to be very similar to the previously reported events.

Summary

Following take-off from Los Angeles International Airport (LAX), the crew of the B747-438 aircraft noticed a severe airframe jolt while conducting a climbing left turn. The cockpit instruments indicated that the number 1 engine exhaust gas temperature was rising through 900 degrees C. Passengers also reported flames emanating from the number 1 engine tailpipe.

The crew shut down the number 1 engine and returned the aircraft to LAX for a one- engine inoperative landing.

An initial investigation carried out by the operator's maintenance personnel revealed that there had been an apparent failure within the engine's high-pressure compressor (HPC) assembly. The engine was removed from the aircraft and transported back to the operator's engine maintenance facility in Australia, where a more detailed examination was carried out. An Australian Transport Safety Bureau (ATSB) metallurgist was present for that examination.

The engine was a Rolls Royce RB211-524G2-T-19/15 turbofan engine. The designation `T', in the engine model number, indicated that the engine had been manufactured with a core engine from the larger Rolls Royce `Trent' engine series. The inclusion of the `Trent' core had enabled the engine to be more fuel-efficient and operate at a lower exhaust gas temperature.

The `Trent' core engine was split into numbered modules. The three modules of interest to the investigation were: Module 33, the intermediate case module; Module 41, the high-pressure system module; and Module 51, the intermediate and low-pressure turbine assembly module.

The engine had a nominal overhaul life of 30,000 hours or 4,000 cycles. At the time of the failure the engine was well within its overhaul life, having been in operation for a total of 13,922 hours and 1,395 cycles. It had not undergone any major maintenance.

The ATSB Technical Analysis report on the engine failure, (see Appendix A), indicated that the engine failure had resulted from the liberation of a single blade from the first-stage HPC rotor in Module 41. The blade release had resulted in extensive damage to the engine. The friction from the liberated blade impacting the surrounding blades on the HPC rotor resulted in a titanium fire within the compressor assembly.

A close inspection of the remains of the liberated blade root stub showed evidence of fatigue cracking and loss of the forward trailing edge corner of the blade dovetail root block. None of the other blades within the first-stage HPC assembly showed any visible evidence of cracking when inspected with the unaided eye. Minor collateral damage was also evident to components in Module 51 and Module 33 resulting from the blade failure.

The manufacturer was aware of three similar failures of the HPC blades in the RB211-524G/H-T series of turbofan engines. In those failures, cracking in the blade root area was believed to have resulted from uneven friction on the blade root bedding surfaces due to a breakdown in blade root lubricant. The manufacturer further indicated that damage in the blade root area that led to local stress concentrations, such as scores and sharp edges, might also have contributed to those blade failures.

The evidence from the ATSB investigation indicated that the failure mode in this incident was the same as the three other known failures in RB211-524G/H-T turbofan engines.

Occurrence summary

Investigation number 200205895
Occurrence date 15/12/2002
Location Los Angeles, Aero.
State International
Report release date 16/01/2004
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 747
Registration VH-OJU
Serial number 25566
Sector Jet
Operation type Air Transport High Capacity
Departure point LAX airport, Los Angeles USA
Destination JFK airport, New York USA
Damage Minor

British Aerospace Plc BAe 146-100A, VH-NJX

Safety Action

Civil Aviation Safety Authority (CASA)

  • On 23 January 2003, CASA airworthiness directive AD/BAe 146/102 became effective, requiring all operators of BAe 146 aircraft to action the requirements of BAE Systems (Operations) Limited, Inspection Service Bulletin (ISB) 21-156. That ISB relates to inspections of air-conditioning ducts. It has been found that the sound attenuating material used in the air-conditioning ducts can absorb oil and become a source of persistent air contamination.
  • On 10 July 2003, CASA airworthiness directive AD/BAe 146/105 became effective, requiring all operators of BAe 146 aircraft to carry out a modification in accordance with BAE Systems Service Bulletin SB. 49-036-36019E. That modification provides an improved seal at the aircraft - APU interface, reducing the likelihood of contamination of cabin air due to ingestion of oil from the APU bay.

Operator

The operator of the aircraft involved in this incident previously incorporated various modifications to the cabin air system, APU and engines and introduced improved maintenance practices in an effort to minimise the occurrence of cabin fumes events.

More recently, the operator has undertaken to go beyond the requirements listed in CASA AD/BAe 146/102, by fully replacing the sound attenuating ducts of their entire BAe 146 fleet. On 30 April 2003 the operator advised that during the period since August 2002, when the first duct replacement was completed, there has been a reduction in safety reports received. It has not stopped air quality events occurring but has removed the occurrence of lingering odours.

The operator has also:

  • commenced trials of a new bearing seal that has realised positive results during recent bench testing by the engine manufacturer
  • refined a flowchart for use by engineering personnel that ensures that every regulatory aspect is completed during the maintenance investigation and certification process
  • developed a stand-alone Cabin Air Quality Safety Report, as an adjunct to the Safety Occurrence/Incident Report currently in use. This allows the operator to focus on the specifics of air quality and what symptoms crews are experiencing
  • employed a coordinator to be the company's single point of contact for liaison with external agencies such as CASA and the ATSB, regarding all air quality matters.

Analysis

It is likely that the copilot's initial attempt to clear the fumes on 2 December was unsuccessful because the problem involved more than just an air conditioning pack. An oil mist forming in the APU bay as a result of the faulty generator drive seal could have resulted in the contamination of the air supply to both air conditioning packs. The maintenance engineers believed that they had identified the source of the fumes and had taken appropriate action. It is considered likely that their assessment was correct and that the report of fumes during the following flight was due to residual contamination of the air conditioning packs.

When checking for fumes during the ground test of the air conditioning packs, the engineers used bleed air from engines 1 and 4 and consequently missed an opportunity to identify engines 2 or 3 as the possible source of the contamination. The difficulty in positively identifying the origin of the contamination was highlighted by the smell reported by the operating crew on 6 December. It could not be discounted that the cabin fumes were a result of the intermittent leak of oil in the number 3 engine, that was identified ten days after the original incident, instead of, or as well as, the APU.

Summary

The British Aerospace 146-100A (BAe 146) was being prepared for a regular public transport service from Perth to Newman, WA. As the copilot boarded the aircraft to conduct pre-flight checks he detected strong fumes in the cabin and the flight deck. He noted that the auxiliary power unit (APU) was supplying bleed air to one of the aircraft's two air conditioning packs that in turn supplied conditioned air to the flight deck and cabin. In an attempt to clear the fumes, he directed the bleed air supply to the alternate pack.

Bleed air from the APU was generally used when air conditioning was required during ground operations or during the take-off and landing phases. During flight, the air conditioning packs receive bleed air from the engines.

As the copilot continued the pre-flight checks, he noticed the cabin fumes becoming stronger and so shut down the air conditioning pack and opened the flight deck windows.

Maintenance engineers were requested to investigate the source of the fumes and subsequently discovered an oil leak in the APU generator drive adaptor pad. Rectification work, including the replacement of a carbon seal, was carried out 11 days later, on 13 December. To enable the aircraft to continue in service on the day of the incident, the APU was isolated from the air conditioning system in accordance with the terms of the aircraft's Minimum Equipment List (MEL) that permitted operation of the aircraft in non-standard configurations. The operator reported that the maintenance engineers then addressed the defect in accordance with the Civil Aviation Safety Authority (CASA) airworthiness directive AD/BAe146/86, effective 3 April 2001, and the British Aerospace Systems Inspection Service Bulletin (ISB) 21-150. That ISB called for certain actions to be performed whenever a cabin air quality problem was identified, which was suspected of being associated with oil contamination of the air supply from the air conditioning packs. No oil contamination was found. The engineers then operated both packs using bleed air from engines 1 and 4 until they were satisfied that there were no fumes and the aircraft was then released for service.

The copilot had been exposed to the fumes for approximately 30 minutes. The two cabin crew, who boarded the aircraft shortly after the copilot, were exposed to the fumes for approximately 20 minutes. All three were eventually affected by the fumes, became unwell, and were removed from flight duty. In accordance with company standard practice they underwent medical examinations. The pilot in command was exposed to the fumes for less than 5 minutes and was not affected. Impaired performance due to the inhalation of contaminated air is considered a potential threat to flight safety. For that reason, company procedures emphasise the importance of flight crew donning oxygen masks if poor air quality is suspected during flight.

The pilot in command and a replacement crew subsequently departed in the same aircraft for the flight to Newman. The cabin crew reported a slight smell of fumes toward the rear of the aircraft during the first sector. On the return sector, both cabin crew reported feeling unwell, with symptoms consistent with fumes inhalation.

Follow-up inspections of the air conditioning system, engines and APU were carried out in accordance with the CASA airworthiness directive and no contamination was evident. On 6 December, the operating crew indicated that a smell was apparent and it appeared to be consistent with the operation of the APU. As the APU was still isolated, engineers doubted that it could be contaminating the air conditioning system. All four engines and the regenerative ducts were again checked, with no contamination evident. Follow up inspections were scheduled in accordance with the ISB.

A further cabin air quality event occurred on 12 December, when the flight deck crew detected fumes shortly after departure. The flight crew proceeded to identify the source of the fumes using a contamination source location schedule. That schedule involved selecting different combinations of engine air and air conditioning packs. The fumes were traced to the number 3 engine, which was isolated, and the flight continued as planned. Subsequent inspection revealed oil wetness in the number 3 engine high-pressure compressor; the result of a worn number 1 bearing seal. Trend monitoring had not indicated abnormal oil consumption for that engine. The engine was replaced and airworthiness directive AD/BAe146/86 was complied with. No further contamination was evident and fumes were not reported during subsequent flights.

Evidence from previous incidents of air system contamination on this aircraft type had indicated that fume events were often intermittent in nature and were associated with engine or APU oil contamination of the air conditioning system. The air supplied to the air conditioning packs was protected from contamination by oil seals in the engines and APU. A defect in one of those seals could result in oil entering the cabin air conditioning system, with the first sign of the defect being an awareness of fumes by passengers or crew members.

The investigation of cabin fumes incidents on BAe 146 aircraft has typically been characterised by a difficulty in precisely locating the original source of the oil leak that led to the creation of the fumes. That has been especially so if there was more than one engine/APU leak combination. The failure of oil seals has been a common factor in the majority of those incidents.

Occurrence summary

Investigation number 200205865
Occurrence date 02/12/2002
Location Perth, Aero.
State Western Australia
Report release date 21/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 Minor

Aircraft details

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