Contact by the Russian flag container ship Maksim Mikhaylov

Final report

Summary

At about 2330 on 20 April 2001, a licensed pilot boarded the Russian flag container ship Maksim Mikhaylov in the port of Brisbane. The pilot exchanged the necessary pilotage information with the master. He then set up his electronic charting system (ECS) and differential global positioning system (DGPS) display on a bridge front window sill to the port side of the centre line in the wheelhouse. The vessel sailed from Fisherman Islands container berth at 0015 on 21 April.

The vessel cleared the berth without incident. The pilot noticed at this stage that, as the tugs took minimum weight on their lines, the vessel heeled 3 or 4 indicating that the ship had reduced residual stability, that is the ship appeared to be tender. Once established in the Bar Cutting, the pilot requested that the ship's speed should be increased to full sea speed for the outward passage via East Channel. At about this time, the second mate took over as officer of the watch and a new helmsman took over the steering. The master remained on the bridge, mostly on the starboard bridge wing. The night was fine and clear with excellent visibility, there was little wind and a calm sea. The tide was on the last of the ebb.

Clear of the Bar Cutting, the pilot ordered an alteration of course to 060 true. Ahead, the beacons marking East Channel could clearly be seen. The pilot alternated between the radar and his ECS display. The second mate fixed the ships position at five-minute intervals and the master remained on the starboard bridge wing. The helmsman steered a straight course and demonstrated that he understood helm orders.

At about 0114, the pilot ordered five degrees of port rudder to enter the East Channel. The ships swing started to accelerate, and the rudder was ordered to amidships. Maksim Mikhaylov contacted Beacon E5 at about 0115:30.

Other than superficial paint damage Maksim Mikhaylov sustained no damage, but the beacon suffered substantial damage. The pilot reported the incident at 0125.

The ship continued on passage, anchoring off Point Cartwright where the master and pilot provided a statement to an official of Queensland Transport and a preliminary assessment of any damage to the ship was made.

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.

  1. After the initial turn was established, the turn to port was maintained by mistaken application of port rudder as a result of either the pilot giving the wrong order, or the helmsman applying the wheel to port rather than starboard. The rate of turn was exacerbated by the ship's low level of reserve stability.
  2. The lack of proper monitoring of either the pilot or the helmsman by the master and officer of the watch contributed to the contact with beacon E5.
  3. The lack of proper monitoring of the helmsman by the pilot, whilst he was giving commands and they were being executed, contributed to the contact with beacon E5.
  4. There was a demonstrated lack of Bridge Resource Management.
    - There was a lack of communication between the master and pilot. There was also a lack of oversight of the pilot by the master during the passage.
    - There was no 'shared mental model' with defined limits which could be challenged if exceeded. The ship followed closely neither the pilot's nor the ship's planned route. The ship was on the 'wrong' side of the pilot's proposed route, and this was not challenged by the Officer of the Watch.
  5. The pilot was affected by a measurable degree of fatigue. The volume of shipping at that time put an extra demand on pilotage services, resulting in shorter than normal breaks between duty periods. The pilot was at the end of his rostered-on period.

Although not contributing factors it is also considered that:

  • The pilot gave the order to turn from the heading of about 060 to enter East Channel at the position he originally planned. The order was given neither too early nor too late.
  • Language and a proper understanding of the orders given by the pilot were not causative issues in the contact with beacon E5.

Occurrence summary

Investigation number 168
Occurrence date 21/04/2001
Location Moreton Bay
State Queensland
Report release date 19/07/2002
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 Maksim Mikhaylov
IMO number 7614379
Ship type Cellular Container
Flag Russian Federation
Departure point Fisherman Islands, Brisbane
Destination Manila, Philippines

Grounding of bulk carrier Devprayag

Final report

Summary

At 1950 on 20 April 2001, the Indian flag bulk carrier Devprayag, after completing discharge of a cargo of fertiliser at the Victorian port of Portland, anchored off the port to prepare its hatches for a cargo of grain to be loaded at Geelong.

The anchorage at Portland is exposed to the south and east and, at the time of anchoring, the wind was southerly, force 3. It increased the next morning to force 5, then to force 6 later that afternoon.

At 1600 on 21 April, the master, concerned that the vessel was yawing excessively, had ordered the engine room to be on five minutes notice. Later that evening, the anchor dragged almost half a mile to the northwest before holding once more, but no action was taken by the ship's officers or the master.

By 2000 the wind was force 6/7. At 2230, the officer of the watch observed that the anchor was dragging again and he alerted the master and the engine room. The master sent the mate forward to weigh the anchor, intending to anchor again at the original position.

While the anchor was being weighed, the ship was set northwest towards Minerva Reef, along the Portland foreshore and, at about 2320, it grounded on the reef.

No one was injured as a result of the grounding and no oil or other pollutant escaped from the ship. The ship was checked for damage and no breach of the hull was found.

The vessel was detained by the Australian Maritime Safety Authority (AMSA) because of the possibility of hull damage and pollution. Four days after the grounding, the ship was refloated with tug assistance. It was inspected by divers at Portland and was released to continue its voyage after being issued with a condition of class.

This report concludes that, among other factors contributing to the incident:

  • The master, after anchoring on a lee shore, permitted the vessel to remain at the exposed anchorage in deteriorating weather;
  • The master had not noted the warning in the Sailing Directions that the anchorage was not recommended in strong E and SE weather and;
  • Priority was given to the task of preparation of the hatches for cargo rather than to the safety of the ship.

This report recommends that:

  • Mariners note the importance of using Sailing Directions when planning passages, when entering or leaving a port or anchoring in or near a port and;
  • That they be fully aware of weather conditions as well as the fact that inclement weather can alter a relatively safe anchorage into one that is unsafe.

Occurrence summary

Investigation number 167
Occurrence date 21/04/2001
Location Portland
State Victoria
Report release date 26/11/2002
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 Devprayag
IMO number 8321072
Ship type Bulk carrier
Flag India
Departure point Portland, Victoria
Destination Geelong, Victoria

Fire and muster of the passengers aboard the Spirit of Tasmania

Final report

Summary

At 1800 on 23 February 2001, the Australian flag roll on-roll off passenger ferry Spirit of Tasmania departed Station Pier in Melbourne bound for Devonport in Tasmania. On board the ship were 967 passengers, 112 crew and 10 staff from licensed businesses. The weather was good with wind from the south-south-west at 17-21 knots and a low swell. The ship was averaging a speed of approximately 17 knots.

At 0114 the second mate on the bridge received a fire 'pre-warning' from a detector he identified as being in 'The Ship's Photographer' shop on 'E' deck. Approximately one minute later the detector initiated a fire alarm followed shortly after by the second detector located in the shop. He immediately contacted the two night security stewards and asked them to investigate the alarms. The stewards called back a short time later confirming that there was a fire, which appeared to be in the store at the rear of the photography shop. The two men could see into the shop through the locked glass front door but could not enter as they did not have the key. The second mate then called the master and started the muster signal in the crew accommodation.

The master arrived quickly on the bridge and, after assessing the situation including further confirmation that the fire was serious, initiated the muster signal throughout the passenger accommodation. The time was 0120.

By this time members of the attack and back-up emergency parties had started to arrive outside the photography shop with fire fighting equipment. The mate who was leading the attack party, nominated two integrated ratings to don breathing apparatus to enter the shop and extinguish the fire.

As smoke was spreading from the shop throughout the ship's accommodation, the mate called the bridge and requested that the fire doors throughout the ship be closed remotely. The time was 0125.

The shop door key was obtained from the shop manager and the two nominated IRs entered the photography shop, initially with hand held extinguishers. Although the smoke was very thick, they located the fire in the store area at the rear. They attempted to extinguish the fire with the hand held extinguishers but found that the fire kept re-igniting. The lead IR realised that the only option was to cool the area with a fire hose. Both men retreated from the shop. A fire hose was quickly charged, both men reentered the shop and, after five minutes, the fire was extinguished using salt water. After the shop area was thoroughly checked, the fire was declared out at 0144.

While the fire was being extinguished, the passenger muster was proceeding relatively smoothly. By 0152 all passengers had been mustered at their designated muster areas by the ship s crew. The crew dealt with a number of problems during the muster including the need to move one group away from a smoke filled muster area, one passenger with a suspected heart attack and two others who had experienced asthma attacks. All passengers were kept at their muster areas for the next hour while the smoke in the accommodation was cleared and the area of the fire monitored for any signs of re-ignition.

At 0255 it was decided that the smoke in the accommodation had cleared sufficiently for the passengers to be escorted back to their cabins. The rest of the voyage was completed without incident with Spirit of Tasmania arriving at Devonport on schedule on the morning of 24 February.

Occurrence summary

Investigation number 165
Occurrence date 23/02/2001
Location Bass Strait
Report release date 12/09/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Marine
Marine occurrence category Fire
Occurrence class Incident
Highest injury level None

Ship details

Name Spirit of Tasmania
IMO number 8502391
Ship type Ro-Ro passenger ferry
Flag Australia
Departure point Melbourne, Victoria
Destination Devonport, Tasmania

Lifeboat incident on board bulk carrier Alianthos

Final report

Summary

On 20 January 2001, the Maltese flag, panamax bulk cargo carrier Alianthos arrived at the anchorage in Corio Bay, Geelong, after an uneventful voyage from Shanghai, China. The ship was in ballast and intending to load a full cargo of grain at the Geelong grain loader.

On 23 January, the master made the decision to conduct an 'abandon ship' drill while the vessel was at anchor waiting to berth. The drill commenced at 1018 and was completed by 1140. The master was not satisfied with some aspects of the crew's performance during the drill. He ordered that all crew were to receive further instruction, and complete another 'abandon ship' drill, the following day.

The 'abandon ship' drill commenced at 1700 the following day. Both port and starboard lifeboats were prepared, lowered to the water and taken away from the ship by crews who had not been in one of the boats the previous day. The third mate was assigned as the officer in charge of the port lifeboat.

When the port lifeboat returned to the ship, there was some delay in reconnecting the falls to the boat's on-load release hooks. After some time, the third mate gave the order to raise the boat from the water. The crew then disembarked at the embarkation deck and the boat was raised and secured at the head of the davit.

At the master's request, the mate continued to instruct members of the ship's catering and engineering staff who were not conversant with some aspects of the operation of the lifeboats. Once the mate had finished instructing the crew, they prepared the empty port lifeboat for lowering to the embarkation deck.

At 1742, one of the motormen was instructed to operate the davit winch to lower the port lifeboat. The motorman, who had not operated the davit before, lifted the winch brake handle and started to lower the boat. The boat moved more quickly than usual down from the housed position, resulting in the davit cradles coming to an abrupt stop as they reached deck level.

When the davit cradles hit their stops, the boat was seen to jerk sharply. At this instant, the after fall released from its on-load release hook. The stern of the lifeboat fell, swinging on the remaining forward fall. As the weight of the whole boat came onto the forward davit cradle it buckled and the boat made hard contact with the side of the ship. The starboard side of the lifeboat was cracked and holed by the contact. The forward fall and hook continued to hold the weight of the lifeboat, which had come to rest with its stern above the port gangway. There were no crew inside the lifeboat and consequently no injuries as a result of the incident.

After assessing the damage to the lifeboat and its davit, the master instructed the crew to use the after stores crane to raise the stern of the lifeboat and secure it alongside the ship. Alianthos berthed on the morning of 26 January with the lifeboat still suspended in this fashion.

Occurrence summary

Investigation number 164
Occurrence date 24/01/2001
Location Geelong
State Victoria
Report release date 10/01/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Marine
Marine occurrence category Lifeboat
Occurrence class Incident
Highest injury level None

Ship details

Name Alianthos
IMO number 8805169
Ship type Bulk carrier
Flag Malta
Departure point Shanghai China
Destination Corio Bay, Geelong

Saab SF-340B, VH-OLN

Analysis

It was likely that the Aztec pilot became distracted while attempting to identify the engine problem and did not maintain the aircraft's track clear of the control zone. The pilot's ability to navigate was probably constrained by the fluctuating in-flight visibility, his unfamiliarity with the Aztec's systems and stress due to the situation.

The proximity of the Sydney and Bankstown control zones required pilots of aircraft operating at the latter airport to be particularly attentive to maintaining track and altitude to reduce the possibility of inadvertently entering the Sydney control. The operation of the aircraft's transponder and radar surveillance of the control zone by the Sydney controllers were active defences for the airspace system.

Summary

The pilot of a Saab Aircraft AB SF-340B (Saab), on final to runway 16R at Sydney airport, was instructed by the aerodrome controller (ADC) to turn right heading 240 degrees M due to an unidentified aircraft in the control zone. The unidentified aircraft was observed to turn north and pass the Saab with 2 NM lateral and 400 ft vertical displacement. The required separation standard was either 3 NM laterally or 1,000 ft vertically. The unknown aircraft was subsequently identified as a Piper Aircraft Corporation PA-23-250 (Aztec). The Aztec pilot had entered the Sydney control zone without a clearance, resulting in an infringement of separation standards.

The Aztec pilot had intended to conduct a visual flight rules (VFR) flight from Bankstown, located 9.5 NM west of Sydney, to Grafton. He had recently purchased the Aztec and this was the first significant trip in that aircraft. The pilot had previously flown a Beech Baron and had completed a flight check on the Aztec.

Flights under the VFR conducted below 10,000 ft required a pilot to operate in the following meteorological conditions:

  • flight visibility greater than 5,000 m;
  • clear of cloud when in a general aviation control zone; and
  • 1,500 m horizontally and 1,000 ft vertically from cloud while en route.

The Bankstown terminal area forecast, issued at 0433, covering the period from 0600 to 1900 Eastern Summer Time forecast a flight visibility of 5,000 m in smoke and a few (1 to 2 OKTAS) clouds at 3,000 ft. The forecast indicated that visibility was expected to increase to greater than 10 km by mid afternoon. The actual meteorological conditions reported at Bankstown during the morning of the occurrence were:

  • 0900: westerly wind at 9 kts with visibility of 8,000 m, no cloud below 12,500 ft and temperature of 18 degrees C;
  • 0900 report was amended at 0919: westerly wind at 9 kts with visibility of 3,000 m in smoke, no cloud below 12,500 ft with the sky obscured and temperature of 18 degrees C;
  • 0930: south-westerly wind at 6 kts with visibility of 6,000 m, no cloud below 12,500 ft and temperature of 18 degrees C;
  • 1000: wind was calm with visibility of 7,000 m no cloud below 12,500 ft and temperature of 19 degrees C; and
  • 1030: north-westerly wind of 4 kts with visibility of 7,000 m, no cloud below 12,500 ft and temperature of 20 degrees C.

The actual reported weather conditions at Sydney during the morning were:

  • 0900: southerly wind at 7 kts with visibility of 4,000 m in smoke and scattered (3 to 4 OKTAS) clouds at 1,600 ft and temperature of 18 degrees C;
  • 0920: southerly wind at 7 kts with visibility of 6,000 m in smoke with a few (1 to 2 OKTAS) clouds at 4,500 ft and temperature of 18 degrees C;
  • 0930: southerly wind at 7 kts with visibility of 6,000 m in smoke with a few (1 to 2 OKTAS) clouds at 4,500 ft and temperature of 18 degrees C; and
  • 0955: south-easterly wind at 7 kts with visibility of 7,000 m in smoke with a few (1 to 2 OKTAS) clouds at 4,500 ft and temperature of 19 degrees C.

Weather conditions at the time were visual meteorological conditions that had been affected by bushfires in the Sydney basin.

The pilot had delayed departing from Bankstown in anticipation of the weather conditions improving and subsequently departed at about 0945. Immediately after take-off, while the pilot was still monitoring the Bankstown ADC frequency, the right engine commenced to `run rough'. The pilot reduced power on that engine and attempted to identify the cause of the problem. The pilot decided to return to Bankstown as the situation could not be rectified and the aircraft was vibrating. As he manoeuvred to return, the flight visibility was such that the pilot could not see Bankstown airport. He was aware of the aircraft's proximity to the Sydney control zone and reported that he was about to call Sydney air traffic control for a clearance when he was advised by the departure south controller that the Aztec had infringed the control zone.

The Aztec pilot had selected code 1200, the nominated code for a VFR flight operating in non-controlled airspace (and not participating in a radar information service) and was operating the aircraft's transponder.

The Sydney Aerodrome and Director West controllers saw, on the air traffic control radar, that the Aztec was in the control zone, northwest of Canterbury racecourse, and likely to conflict with aircraft on final to runway 16R. The ADC instructed the pilot of the Saab to turn right to avoid the Aztec. The pilot of another aircraft was similarly instructed.

Before the pilot could return to Bankstown, the right engine on the Aztec started to operate normally. The pilot decided to continue the flight and tracked to the north to vacate the control zone and to join the VFR lane. The flight continued uneventfully to Coffs Harbour where the pilot refuelled the aircraft. Subsequently, after take-off from Coffs Harbour, at approximately 300 ft, the right engine surged and the pilot landed the aircraft on the remaining runway. The pilot taxied the aircraft to a hangar for maintenance action and on reaching the hangar the left engine stopped. Inspection by a licensed aircraft maintenance engineer (LAME) found that the cooling flaps on both engines were inoperative and had caused the engines to overheat. The LAME re-rigged the cowl flaps for maximum cooling and a subsequent engine ground run confirmed normal operation.

Occurrence summary

Investigation number 200105942
Occurrence date 27/12/2001
Location 6 km NNW Sydney, (VOR)
State New South Wales
Report release date 20/09/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of separation
Occurrence class Incident
Highest injury level None

Aircraft details

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

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-23
Registration VH-ALN
Serial number 27-3032
Sector Piston
Operation type Private
Departure point Bankstown, NSW
Destination Grafton, NSW
Damage Nil

Collision between cargo vessel Handymariner and FV Lipari

Final report

Summary

At 0300 on the morning of 18 January 2001, the Hong Kong flag geared bulk carrier Handymariner was 26 miles1 off the coast of Western Australia, enroute to Bunbury to load a cargo of alumina. The ship was on a course of 156 (T) at a speed of 14 knots. The wind was from the south-south-east at force six with a rough sea of 1.5'2 m on a low swell. The visibility was estimated at 10 miles with a partly cloudy sky.

The same morning, a 15.65 m timber rock lobster fishing vessel, Lipari, left Port Bouvard at around 0310 to check its lobster pots which were set some 36 miles in a south-westerly direction from the port. On board Lipari were the skipper and two deckhands. Shortly after leaving port, the two deckhands went below to sleep. The skipper stayed on the vessel's fly bridge for the first six miles steering a course of 235 at 15 knots and then went down to the wheelhouse and engaged the autopilot. He remained in the wheelhouse listening to some music.

At 0410 the mate on watch on Handymariner detected Lipari ahead, and to port, of his ship and commenced tracking the fishing vessel on radar. The ARPA equipped radar indicated that Lipari's range at its closest point of approach was going to be small, so the mate attempted to call the fishing vessel on VHF channel 16. Despite several radio calls he received no response as, unknown to him, Lipari's VHF radio was not working. The mate then attempted to warn the fishing boat using an aldis lamp and the ship's forward whistle, but still received no response. Lipari maintained a steady course and speed.

When Lipari had closed to within four miles, the mate disengaged the ship's auto pilot and ordered the look-out onto the helm in preparation for a course alteration. Lipari continued to close with the ship on a steady course and speed, apparently unaware of the presence of the ship and unresponsive to Handymariner's radio calls, light and sound signals. With a collision now imminent the mate ordered a course alteration to starboard.

At about this time the skipper in Lipari's wheelhouse heard the ship's whistle. He made his way to the fly bridge where he identified the ship dead ahead. He turned the fishing vessel's helm hard to port but it responded slowly as the auto pilot was still engaged in the wheelhouse.

At approximately 0435 Lipari and Handymariner collided, the fishing vessel's starboard bow making contact with the ship's hull plating on the port side adjacent to number one hold. The ship sustained no damage and there were no injuries sustained by the crew of either vessel, but Lipari had been holed on the starboard bow above the waterline.

After the collision, Lipari's skipper inspected the damage and decided that the vessel was not safe to work. He followed Handymariner for approximately five minutes before turning north to Fremantle. Lipari arrived safely at a boat repair facility in Fremantle later in the morning.

Handymariner resumed its course to Bunbury and arrived at the anchorage at 0736 without further incident.

1 Miles referred as nautical miles = 1 852 m.

Occurrence summary

Investigation number 163
Occurrence date 18/01/2001
Location Off WA Coast
State Western Australia
Report release date 12/07/2002
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 Handymariner
IMO number 7702073
Ship type Bulk carrier
Flag Hong Kong
Departure point Singapore
Destination Bunbury, WA

Ship details

Name Lipari
Ship type Lobster fishing boat, class 3B, F 350
Flag Australia
Departure point Port Bouvard
Destination 36 miles south-west of Port Bouvard

Boeing 767-338ER, VH-OGG

Analysis

The controller did not detect that he had assigned an incorrect flight level when the crew of the B767 read-back FL300. There were no subsequent checks required of the controller that could have alerted him to the error until the CLAM alarm activated.

The additional coordination and TAAATS entries associated with those aircraft that had been provided with a shorter track increased the controller's workload and may have distracted him as he was trying to assist them in their important task. It is also possible that the controller may not have detected the incorrect level assignment of FL300 because the level read back by the pilot phonologically matched the information stored in the controller's short-term memory; he may not have consciously processed the assigned flight level information in the read-back provided by the crew of the B767.

The investigation did not establish why the controller unintentionally assigned FL300 when he had intended to confirm the assignment of FL330.

Summary

A Boeing 767-338ER (B767) was maintaining flight level (FL) 370 and had been assigned FL330 to maintain separation with a Cessna Citation 500 (C500), maintaining FL310, that was crossing the track of the B767. The controller entered FL330 into The Australian Advanced Air Traffic System (TAAATS). He subsequently, and unintentionally, assigned the crew of the B767 descent to FL300. The controller received a cleared level adherence monitor alarm (CLAM) when the B767 descended through FL326. Vertical separation between the B767 and the C500 reduced to 700 ft, and horizontal separation reduced to 3.4 NM. The required separation standard was 2,000 ft or 5 NM. There was an infringement of separation standards.

The controller had initially cleared the crew of the B767 to descend from FL370 to FL330. The descent was to be commenced at the discretion of the crew. He then entered FL330 into TAAATS as the new cleared flight level (CFL). The controller reported that he had made the necessary TAAATS entries on receipt of the correct level read back from the crew of the B767. There were no subsequent TAAATS entries required in relation to FL330 being assigned to the crew of the B767.

The B767 crew reported leaving FL370 approximately five minutes after they had been assigned FL330. The controller reported that he had intended to confirm FL330 as the cleared flight level with the B767 crew at that time, but he unintentionally assigned FL300. The crew of the B767 read-back FL300 and continued descent through FL330. The controller did not detect from the read back that he had assigned an incorrect flight level. There were no subsequent opportunities for the controller to realise the error until the CLAM alarm from TAAATS.

The controller indicated that he considered his workload at the time of the occurrence to be light. He was responsible for two sectors of airspace but he did not believe that the increase in workload caused by the combination of the two sectors contributed to the error. The replay of the voice recording indicated that the controller had up to ten aircraft under his control at the time of the occurrence. Three of those aircraft had requested a shorter route. The controller accommodated the requests because some of those aircraft were involved in bush fire fighting operations. When the routes for those aircraft were amended, the associated flight data record in TAAATS also needed to be amended and the changes needed to be coordinated with adjacent sectors. The controller did not believe the extra workload generated by those tasks contributed to the occurrence.

The controller was also the team leader on the shift. He reported that there were no distracting team leader issues at the time of the occurrence. The controller did not believe he was fatigued.

Occurrence summary

Investigation number 200106230
Occurrence date 26/12/2001
Location 159 km SW Sydney, (VOR)
State New South Wales
Report release date 10/09/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of separation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 767
Registration VH-OGG
Serial number 24929
Sector Jet
Operation type Air Transport High Capacity
Departure point Melbourne, VIC
Destination Sydney, NSW
Damage Nil

Aircraft details

Manufacturer Cessna Aircraft Company
Model 500
Registration VH-ZMD
Serial number 500-0263
Sector Jet
Operation type Charter
Departure point Orbost, VIC
Destination Cessnock, NSW
Damage Nil

Cessna A185F, VH-JBM, at Strahan, Tasmania, on 29 December 2001

Safety Action

As a result of the investigation the Australian Transport Safety Bureau issues the following recommendation:

Recommendation R20020082

The Australian Transport Safety Bureau recommends that the Civil Aviation Safety Authority review the requirements of Civil Aviation Order 20.11, with respect to the wearing of life jackets, to extend the requirements to the occupants of any aircraft that is standing, taxying, taking off, landing or approaching to land, on water.

Significant Factors

  1. The floats were not pumped out before departure.
  2. The floats were prone to ingress of water while operating on water.
  3. The combination of prevailing wind and aircraft heading resulted in down pressure on the right float.



 

Analysis

The pilot's decision, while conducting the preflight inspection, to defer the pumping out of the floats increased the risk of him forgetting to complete the task before departure. Compounding the situation was the pilot's perception of time pressure that may have further increased the risk of him forgetting to pump out the floats.

The combination of high aircraft weight and the likely presence of a substantial quantity of water in the floats, meant that the floats were riding relatively low in the water. A comparatively long taxy exposed the floats to further ingress of water through the seams and through the holes in the top of the right float.

The right turn after encountering the catamaran's wake would have allowed the northerly wind to lift the left wing with the associated effect of lowering the right float further in the water. It is likely that the right float became fully submerged, increasing its drag. The momentum of the floatplane acted from a centre of gravity that was higher than the drag of the right float, causing the aircraft to nose over to the right. With the slow speed of the floatplane, the effects of the control deflections and the addition of power were insufficient to stop the aircraft from nosing over.

The carriage of life jackets and the stowage of them below each of the seats, was in accordance with CAO 20.11 parts 5.1.4 and 5.1.5. While the wearing of life jackets was not required by CAO 20.11 Part 5.1.8, the consequence was that their availability was not assured after the occupants of the floatplane had exited into the water.

Summary

There were five persons on board the Cessna 185 floatplane when the pilot taxied for a charter flight from the wharf at Strahan, Tas. The pilot steered the aircraft out of the cove into more open water to position the aircraft for take-off into the prevailing northerly wind.

The pilot reported that the aircraft had travelled approximately 1 km, and was at the start of the planned take-off run, when he assessed the water state as being marginal for the aircraft. He then began steering the floatplane back towards the wharf when a catamaran cruise boat, travelling in the opposite direction, passed on the left. Waves generated by the accelerating catamaran prompted the pilot to steer the floatplane left to cross the bow-wave head on. After negotiating the wake, the pilot resumed course to the wharf. The pilot then became concerned about the buoyancy of the right float and broadcast his concerns. He increased power and applied left aileron and aft elevator to counter the increasing list to the right but the aircraft nosed over and came to rest inverted.

The pilot and two passengers were able to evacuate quickly from the submerged cabin and were followed a short time later by another passenger. At that time, the pilot was diving to assist the remaining passenger, who eventually surfaced unaided. Three life jackets floating in the water nearby were retrieved by the pilot and were donned by passengers. The pilot and passengers were rescued a short time later by a nearby boat and another floatplane.

The pilot had been tasked to use a floatplane that was positioned in a hangar near the water. While the preflight inspection in the hangar had revealed only a small amount of water in the two float lockers, the pilot intended to pump out the other six float compartments on each float when the floatplane was tied up at the wharf. He was aware that the floats had been prone to taking on water and that pumping out the floats prior to his previous flights in the aircraft had removed substantial amounts of water. It was also standard operating procedure for the operator's pilots to pump out the float compartments as part of their daily preflight inspection. However, the floats were not pumped out, and the aircraft departed the wharf with an unknown amount of water in the floats.

While the pilot could recall being subject to time pressure after the aircraft was positioned at the wharf, he was not able to clearly remember the specific circumstances that contributed to the situation. The pilot reported that he had arrived at work at 0815 Eastern Standard Summer Time and started his duty period at 0830 for a planned 0900 departure.

The pilot stated that, soon after departure from the wharf, the aircraft `felt odd'. He then radioed a colleague located in the wharf office, who indicated that the right wing was slightly low. At the time the pilot attributed the aircraft attitude to fuel imbalance, passenger loading and the wind effect. Before entering the more open water, the pilot had momentarily turned the aircraft into wind and was satisfied with the level of the wings and water handling. While the pilot attempted to observe the performance of the right float a number of times, he found it difficult to see the float from the left side of the aircraft. During the outbound taxi, the front passenger had advised the pilot that the right float was low in the water and had water breaking over it. The pilot reported that he only became concerned about the ability of the floatplane to stay afloat after the encounter with the wake of the cruise boat. At that stage he considered that beaching the floatplane was impractical due to the unsuitability of the adjacent coastline.

The front passenger later stated that the right float was basically submerged by the time the wake from the catamaran had been negotiated. He also stated that there were two round holes of approximately 30 mm diameter on the top of the right float that allowed water to enter the float. This was likely to have been the access holes for the smaller diameter bilge tubes. The access holes are normally sealed with a removable bung. The pilot stated that one or two bilge tubes were missing from their holes in the right float. Following discussions with the pilot and other company personnel, the investigation was unable to determine the point in time when the right float bungs became separated from the floats.

The passengers stated that the operator's personnel had briefed them on life jacket use when they were checked in for the flight. The pilot had also given the passengers a pre-departure briefing that included the location of the life jackets. A life jacket was stowed under each of the seats.

Civil Aviation Order (CAO) Section 20.11, Parts 5.1.4 and 5.1.5 describe the requirements for the equipping of floatplanes with life jackets. Part 5.1.8 describes the requirements for the wearing of those life jackets and states, in part: `However, occupants need not wear life jackets when the aircraft is taking-off or landing at a aerodrome in accordance with a normal navigational procedure for departing from or arriving at that aerodrome, and occupants of aeroplanes need not wear life jackets during flight above 2000 feet above the water.' Aerodrome is defined in Aeronautical Information Publication Australia, Amendment 33, as `A defined area of land or water (including any buildings, installations and equipment) intended to be used either wholly or in part for the arrival, departure and movement of aircraft.'

Occurrence summary

Investigation number 200105932
Occurrence date 29/12/2001
Location Strahan
State Tasmania
Report release date 27/08/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer Cessna Aircraft Company
Model 185
Registration VH-JBM
Serial number 18502204
Sector Piston
Operation type Charter
Departure point Strahan, TAS
Destination St. John Falls, TAS
Damage Substantial

Boeing 747-312, ZS-SAJ

Safety Action

Local safety actions

As a result of the incidents, the operator implemented a program to replace the transient suppression devices fitted to all its B747 aircraft. The operator implemented the following safety actions to minimise the likelihood of fuel spills until all the B747 aircraft were fitted with the upgraded transient suppression device:

  1. Use of fuel tank quantities for fuelling operations that were less than the certificated maximum figures to ensure the tanks were not filled to maximum capacity;
  2. Pressurisation of the fuel manifold prior to commencing the fuelling operation in order to verify that no defects existed prior to opening any refuel valves;
  3. Manual closure of the refuel valves when a fuel tank was full;
  4. Cessation of the practice whereby circuit breakers were manually pulled to override the overfill protection system;
  5. Reducing refuelling pressure on reaching the required tank quantities;
  6. An increase from 60 minutes to 90 minutes in the period allocated for refuelling of aircraft to facilitate the manual operation of the refuelling system and to drain the surge tanks if required; and
  7. An audit during February 2002 of the refuelling operations at Perth by the operator's quality assurance and industrial safety staff.

Summary

A fuel spill of approximately 100 litres occurred during refuelling of the South African registered Boeing 747-312 aircraft on the international terminal apron at Perth airport. Eighty minutes later, the Aviation Rescue Fire Fighting Services (RFFS) observed fuel venting from the right wing of the aircraft as it commenced a take-off roll on runway 21, for a flight to Johannesburg, South Africa.

The fuel spill at the terminal was due to the refuel valve in the number 4 reserve tank failing to shut off. The tank became overfilled because of a faulty quantity indicator at the refuelling station panel. Fuel overflowed from the reserve tank into the fuel tank vent system and then spilt onto the apron from a ram air scoop located near the wingtip. The tank vent system vented the fuel tanks to atmosphere by a series of tubes from the fuel tanks, to a surge tank located in the outboard section of each wing. The surge tank vented to atmosphere through a flame arrester and the ram air scoop.

The aircraft refuelling system included an overfill protection system whereby if 75 mm of fuel overflowed into the surge tank, a float switch operated, which closed all refuel valves. The overfill protection system could be disabled by pulling the appropriate circuit breaker in the main equipment centre within the lower forward fuselage.

During the period from 7 December to 30 December 2001, the Perth RFFS attended six other fuel spills ranging from 20 to 100 litres from aircraft used by the same operator. Those spills involved five B747 aircraft (including ZS-SAJ) and were due to the failure of the refuel valves to shut off during refuelling operations.

In 1998, the United States Federal Aviation Administration (FAA) issued an airworthiness directive, AD 98-20-40, that required the replacement of fuel quantity indication system (FQIS) electrical wiring outside of the fuel tanks and surge tank on older versions of the B747 aircraft. The modification was intended to prevent arcing of the FQIS wiring or probes due to electrical transients induced by electromagnetic interference or electrical short circuit conditions.

The five aircraft involved in the fuel spills at Perth airport had been fitted with a transient suppression device that was approved as an alternate means of compliance with the airworthiness directive. The device had caused problems with the FQIS, including incorrect calibration of the refuelling system that resulted in the aircraft being loaded with an incorrect amount of fuel or the fuel tanks being overfilled.

The spillage of fuel from the tank vent system during the eight occurrences indicated that the overfill protection system circuit breaker was pulled during the refuelling operation to work around the calibration problem. The work around enabled refuelling operations to continue and prevent any delay to the departure of the aircraft. If some fuel remained in the surge tank after completion of refuelling operations, it could vent to atmosphere from the ram air scoop during the take-off roll, as was observed on 17 December 2001.

Following the fuel spills, the operator carried out rectification work on the five aircraft, including the checking and changing of fuel system components, the replacement of FQIS wiring harnesses, and the re-calibration of the system. The operator also implemented the local safety actions listed below and no further fuel spills were reported.

Occurrence summary

Investigation number 200105937
Occurrence date 17/12/2001
Location Perth, Aero.
State Western Australia
Report release date 13/08/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 747
Registration ZS-SAJ
Serial number 23027
Sector Jet
Operation type Air Transport High Capacity
Departure point Perth, WA
Destination Johannesburg, South Africa
Damage Nil

Cessna A185F, VH-SLC

Significant Factors

  1. The pilot made an inappropriate power reduction before terrain clearance was assured.
  2. Turbulence and downdrafts in the lee of the headland significantly degraded the aircraft's climb performance.



 

Analysis

The combination of near maximum take-off weight, and the reduction of engine power to 81% soon after take-off, meant that the aircraft had marginal climb performance when it encountered the turbulence and associated downdrafts. By not using the full take-off distance available the pilot placed the aircraft on a climb profile that reduced terrain clearance and increased the risk of exposure to strong downdrafts.

The pilot's judgement may have been influenced by previous flights where different wind directions and lower wind strengths combined to give more favourable take-off conditions. Additionally, the detrimental effect of an early power reduction would not have been as perceptible on training flights conducted at lower aircraft weights where the aircraft's climb performance would have been far greater. Although turbulence in the lee of the headland may have been present on previous occasions, the pilot had not encountered any significant downdraft activity. Consequently, he was unprepared for conditions of that severity.

Although the pilot turned left to avoid the elevated terrain when the aircraft descended in the turbulence, it was likely that the flight path placed the aircraft into even stronger downdraft activity. Without the immediate application of a higher power setting, the aircraft did not have sufficient performance margin to continue the climb or maintain altitude.

From the point where the pilot attempted to land the aircraft there was insufficient water distance remaining on which to land and stop the aircraft normally. The aircraft contacted the beach at a speed that was fast enough, when combined with the high centre of gravity of the aircraft type, to cause it to overturn.

Summary

The pilot of the Cessna 185 Floatplane, with five passengers on board, was making a water departure for a charter flight. The pilot positioned the floatplane for a take-off into a north easterly wind of 15 kts that was gusting to over 20 kts. The take-off path was over a sand spit, approximately 50 ft above the water level. To the north, and left of the take-off path, was a steep, rocky headland that rose to a height of approximately 300 ft above mean sea level.

The pilot reported that he had selected 20 degrees of flap and applied maximum power for take-off. The aircraft became airborne after a short run and the pilot climbed it at an indicated airspeed (IAS) of 70 kts. At about 200 ft the pilot reduced engine power to 25 inches of manifold pressure and 2,500 RPM. The pilot reported that just after he reduced power, the aircraft encountered turbulence and started to descend rapidly. He turned the aircraft left, away from the spit, with the intention of regaining altitude over the water before he attempted to cross the spit. However, the aircraft continued to descend, and the pilot decided to land straight ahead. The aircraft contacted the water and bounced, then ran aground on the beach and overturned.

The pilot reported that he exited through a window and instructed the passengers to evacuate quickly, as there was a possibility of fire. The passengers reported that they were entangled in their seat belts and had difficulty releasing the buckles. A small child was being held by a passenger and another passenger was temporarily restrained by clothing that became caught on the right control yoke.

The load chart for the flight showed that the aircraft was 31 kg below its maximum take-off weight. The pilot commenced the take-off with a take-off distance of approximately 1,100 m, which exceeded the minimum take-off distance of 1,000 m stipulated by the aircraft's flight manual. However, this take-off distance was less than the 1,300 m pilots were directed to use by the operator's Authorised Landing Area (ALA) register. The pilot reported that he had not used the full length available as previous take-offs that day, from the same point in lighter winds, had been uneventful. He considered that the increased headwind component would have improved the take-off performance and climb gradient of the aircraft.

The ALA register also stated that a north-easterly wind required a climb over the spit to avoid turbulence in the lee of the adjacent headland. Another warning in the operator's ALA survey report cautioned "Dumping will be encountered on the lee side of the headland especially in the north easterly winds".

A fact sheet on mountain wave turbulence that accompanied a recent ATSB report (Occurrence 200104092) involving mechanical turbulence stated, in part:

"Flowing air near the ground is forced up the windward side of any elevated barrier and then sinks down the leeward side. Air flowing at speeds greater than 20 kts produces seriously turbulent air and significant downdrafts on the leeward side."

That situation was referred to as "dumping" in the operator's ALA survey sheet. The pilot reported that he hadn't encountered severe "dumping" during any previous take-offs.

The fact sheet also stated, in part:

"In addition to generating turbulence that has demonstrated sufficient ferocity to significantly damage aircraft or lead to loss of aircraft control, the more prevailing danger to aircraft in the lower levels in Australia seems to be the effect on a aircraft's climb rate. General aviation aircraft rarely have performance capability sufficient to enable the pilot to overcome the effects of a severe downdraft generated by a mountain wave, or the turbulence or windshear generated by a rotor."

The Cessna 185 Pilot's Operating Handbook (POH) procedures for both normal take-off and short field take-off recommend that once clear of any obstacles, the pilot retract the wing flaps and select full throttle and 2,700 RPM. Operations manual data produced by the operator listed the climb power setting as 25 inches manifold pressure and 2,700 RPM, with a footnote that the information be used as a guide only and that the user refer to the POH and Flight Manual. The aircraft's flight manual did not provide guidance on take-off procedure or associated power settings. The climb power setting of 25 inches manifold pressure and 2,500 RPM, selected by the pilot when the aircraft reached approximately 200 ft, delivered only 81 per cent of the available power.

The pilot reported that he had been encouraged by the operator to reduce power as soon as possible after take-off as a noise reduction technique. The Chief Pilot stated that a power reduction early in the climb was demonstrated during training to reduce the noise impact and to reduce engine wear. The Chief Pilot also stated that, during training it was emphasised that power reductions should only be made when clear of obstacles and when terrain had been cleared. It was also stressed that when required, full power should be used, at the pilot's discretion.

Occurrence summary

Investigation number 200105926
Occurrence date 23/12/2001
Location Palm Beach, (ALA)
State New South Wales
Report release date 17/07/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Forced/precautionary landing
Occurrence class Accident
Highest injury level Minor

Aircraft details

Manufacturer Cessna Aircraft Company
Model 185
Registration VH-SLC
Serial number 18503231
Sector Piston
Operation type Charter
Departure point Palm Beach, NSW
Destination Rose Bay, NSW
Damage Substantial