Collision with terrain - Cessna TR182, VH-DOK, Great Keppel Island, Queensland, on 18 December 2010

Summary

On 18 December 2010, a Cessna TR182 aircraft, registered VH-DOK, departed Rockhampton on a charter flight to Great Keppel Island, Queensland.

On arrival at the Island, the pilot overflew the airstrip to assess the wind conditions and noted that neither of the two windsocks were operational.

The aircraft joined the circuit on downwind for runway 12. The pilot assessed the wind conditions with reference to the surface of the water and determined that the wind was from a northerly direction, with a strength of about 3-5 kts.

During the landing, the pilot reported that the aircraft floated in ground effect for an unusually long time. The aircraft momentarily touched down and then ballooned. The aircraft subsequently landed about halfway along the runway. The pilot applied the brakes, but they did not respond.

The pilot determined that the aircraft could not be stopped by the runway end and elected to go-around. During the go-around the left-wing tip collided with trees. The aircraft spun to the left before coming to rest upright.

After the accident, the pilot estimated that the tailwind was in excess of 10 kts.

It is crucial that pilots establish a decision point along the runway at which a go-around should be commenced in the event the requirements for a safe landing cannot be met.

Occurrence summary

Investigation number AO-2010-109
Occurrence date 18/12/2010
Location Great Keppel Island, (ALA)
State Queensland
Report release date 12/09/2011
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Minor

Aircraft details

Manufacturer Cessna Aircraft Company
Model 182
Registration VH-DOK
Serial number R18200970
Sector Piston
Operation type Charter
Departure point Rockhampton, Qld
Destination Great Keppel Island, Qld
Damage Substantial

Collision with terrain - Piper Aircraft PA-30, VH-EFS, 2 km north-east of Camden Airport, New South Wales, on 23 December 2010

Summary

On 23 December 2010, a flight instructor and student pilot in a Piper Aircraft Corporation PA-30 (Twin Comanche) aircraft, registered VH-EFS, departed Camden Airport, New South Wales on an instrument training flight.

Shortly after take-off, the instructor simulated an engine failure by moving the mixture control on the right engine rearwards. In response, the student reduced the engine control/s on the left engine.

The airspeed decayed and the aircraft stalled. The aircraft rolled abruptly, with the right wing dropping to a 120° angle and the aircraft entered a spin.

The instructor regained control of the aircraft at about 10 ft above ground level (AGL), with the aircraft in a relatively level attitude. The instructor then reduced the throttles to idle and the aircraft impacted the ground. The student was not injured; however, the instructor sustained minor injuries.

As a result of this accident, the operator has implemented a number of safety actions:

  • Introduced a minimum of 1 hour simulator training into their multi-engine endorsement syllabus for conducting asymmetric operations in more extreme situations.
  • Intends to introduce an additional 1 hour of asymmetric operations in the simulator, and a minimum of 1.5 hours flight time conducting asymmetric operations under simulated instrument flight rules conditions, into their command (multi-engine) instrument rating syllabus.
  • Amended their operations manual stating that simulated engine failures conducted below 2,000 ft AGL will be by the use of the throttle only.

This accident highlights the critical importance of conducting the appropriate response actions following both an actual or simulated engine failure in a multi-engine aircraft; and the inherent risks of using the mixture control to simulate a failure at low altitude.

Occurrence summary

Investigation number AO-2010-111
Occurrence date 23/12/2010
Location 2 km NE Camden Airport
State New South Wales
Report release date 12/09/2011
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Minor

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-30
Registration VH-EFS
Serial number 30-1377
Sector Piston
Operation type Flying Training
Departure point Camden, NSW
Destination Bathurst, NSW
Damage Substantial

Collision with terrain - Pacific Aerospace FU-24-954 Fletcher, VH-FNM, Wynella Station, Queensland, on 20 December 2010

Summary

On 20 December 2010, the owner/pilot of a Pacific Aerospace Corporation FU-24-954 Fletcher aircraft, registered VH-FNM, was conducting aerial spreading of urea fertilizer at Wynella Station; a property 40 km south-south-west of Dirranbandi, Queensland. At about 1650 Eastern Standard Time, the pilot was returning to the landing strip after the completion of an application run. The aircraft impacted the terrain, and the pilot was fatally injured.

Examination of the accident site indicated that the aircraft's engine was delivering power at the time of impact. Wreckage examination did not reveal evidence of any defect or mechanical failure that would have contributed to the event. Although the post-mortem report on the pilot noted that he had significant coronary atherosclerosis, there was insufficient information available to determine whether pilot incapacitation was involved in the accident.

The investigation did not identify any organisational or systemic issues that might adversely affect the future safety of aviation operations.

Occurrence summary

Investigation number AO-2010-110
Occurrence date 20/12/2010
Location Wynella Station
State Queensland
Report release date 16/12/2011
Report status Final
Investigation level Systemic
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Pacific Aerospace Corporation
Model FU-24
Registration VH-FNM
Serial number 263
Sector Piston
Operation type Aerial Work
Departure point near Dirranbandi Qld
Destination near Dirranbandi Qld
Damage Unknown

Safety issue investigation into Queensland Coastal Pilotage

Summary

On 16 December 2010, the ATSB released the findings of its investigation of the 2009 grounding of the piloted tanker Atlantic Blue in the Torres Strait. The Australian Maritime Safety Authority (AMSA) indicated that it was concerned that these findings might point to broader systemic issues affecting the safety of coastal pilotage operations. Notably, AMSA advised that it felt the ATSB was ideally placed to investigate these issues given the ATSB’s independence and investigative powers and that it would be pleased to see the ATSB investigate this matter. The findings of previous ATSB investigations and a number of coastal pilotage reviews also indicated that there may be safety issues. Consequently, the ATSB initiated a systemic safety issue investigation into Queensland coastal pilotage.

The ATSB obtained information for the investigation through a survey of all 82 licensed coastal pilots and submissions from 15 stakeholders, including the two main pilotage providers. Further evidence was obtained by interviewing 22 pilots and meeting all three providers, AMSA and other key stakeholders. Other material taken into account by the investigation included past and present issues of Marine Orders Part 54 (MO 54), the regulatory instrument governing coastal pilotage, as well as previous reviews of the coastal pilotage regime.

The report identifies that under successive issues of MO 54, no organisation(s), including the pilotage providers, has been made clearly responsible and held accountable for managing all the safety risks associated with pilotage operations. This resulted in the effective devolution of responsibility for managing the most safety critical aspects of pilotage to the individual pilots. The report also identifies systemic issues with the potential to affect future safety relating to pilot training, fatigue management, risk event reporting, check pilotage and the utilisation of coastal vessel traffic services. Action has been taken by AMSA to address these safety issues. The ATSB has issued three recommendations to AMSA and two recommendations to each provider to take action to fully address four safety issues.

Executive Summary

Background

On 16 December 2010, the ATSB released the final report of its safety investigation into the February 2009 grounding of the piloted tanker Atlantic Blue in the Torres Strait. The report identified deficiencies in the safety management of Queensland coastal pilotage operations, similar to the safety issues identified by the ATSB in previous safety investigations. In response to the ATSB’s findings, the Australian Maritime Safety Authority (AMSA), in its capacity as the coastal pilotage safety regulator, indicated its concern that there might be systemic issues affecting the safety of coastal pilotage operations, arising in particular, from the impact of commercial competitive pressures. Furthermore, AMSA felt that, given the ATSB’s independence and investigative powers, the ATSB was ideally placed to investigate these issues and indicated that it would be pleased to see the ATSB investigate this matter. Consequently, the ATSB initiated a systemic safety issue investigation into Queensland coastal pilotage.

Queensland coastal pilotage

In 1991, Australia introduced a system of compulsory coastal pilotage to protect the sensitive Great Barrier Reef (GBR) environment which lies in Queensland’s coastal waters. The GBR and Torres Strait are both recognised as particularly sensitive sea areas (PSSA)1.To protect these PSSAs, Australia requires large ships2 to use the services of an AMSA licensed coastal pilot3 when navigating the Torres Strait, the Inner Route of the GBR north of Cairns (Inner Route), the Hydrographers Passage off Mackay, and the Whitsunday Islands area.

The coastal waters of Queensland are the only area in Australia where coastal pilotage takes place. All coastal pilotages are undertaken by a single pilot. Depending on a ship’s speed, an Inner Route transit takes between 25 and 40 hours, making it the longest single-handed pilotage in the world. Transits of the Torres Strait and the Hydrographers Passage, the two other main routes, take 8 to 10 hours and 5 to 7 hours, respectively.

In July 1993, when AMSA took over responsibility for coastal pilotage from the Queensland Government, an annual average of about 2,300 piloted ships transited the three main pilotage routes. In 2010, more than 4,700 piloted ships transited these routes. Piloted traffic in the region has, therefore, doubled in less than 20 years as the economies of Queensland and Australia have expanded. Shipping traffic in the region is forecast to increase at a greater rate with traffic in the southern part of the GBR expected to double over the 10 years to 2020.4A proportion of that increased traffic will transit the compulsory coastal pilotage areas and piloted traffic in the region will probably increase at a faster rate than seen since 1993.

Since July 1993, there have been five collisions and nine groundings (including the grounding of Atlantic Blue) during a coastal pilotage. All of those incidents were mainly the result of the inadequate management of the pilotage or navigation and not due to extraordinary circumstances beyond the control of the pilot or crew. None of the incidents resulted in serious pollution or loss of life and damage to the ships involved was limited (i.e. these incidents were not classified as ‘very serious casualties’5).

Any serious shipping incident in the GBR or Torres Strait can have potentially severe and unacceptable consequences in these environmentally sensitive areas. In 2012, a United Nations report focused the attention of the international and Australian community on risks to the GBR environment.6The report documented ‘extreme concern’ over increased developments, including ports and infrastructure, in and around the GBR. Recommendations included that Australia sustain and increase efforts and resources to conserve the GBR environment, and that new developments outside existing long-established major port areas not be permitted.

Coastal pilotage is a critical defence against a shipping incident about which other defences within the broader safety system to protect the GBR and Torres Strait are centred. Other measures, such as vessel traffic services and a comprehensive system of navigational aids, complement and assist with the coastal pilotage task. Coastal pilots oversee the passage of large cargo or passenger ships along the long and navigationally challenging shipping routes in areas which are prone to strong winds and tides. The ships are often constrained by their draught7 and the proximity of shoal waters means there is little margin for navigational error. Coastal pilots have a key role in mitigating a critical risk to Australia’s most sensitive marine environment and therefore it is essential that the service provided by this small cadre of specialist coastal navigators is as safe and effective as it can be.

ATSB investigation

The ATSB safety issue investigation into Queensland coastal pilotage included a 92 question survey of all 82 licensed coastal pilots in January 2011. The survey questions were based on confidential, de-identified, pilot-reported safety concerns supplied by AMSA, matters identified in past reviews, various aspects of safety management and other relevant issues. Collectively, the pilots’ survey responses were a principal source of evidence for the investigation.

Following the survey, 22 pilots were interviewed by the investigation team. The ATSB held meetings with all key stakeholders, including AMSA and the three private companies authorised by AMSA as ‘pilotage providers’ who assign licensed pilots to ships. The ATSB also obtained pilotage related records from AMSA and the pilotage providers. Fifteen stakeholders made submissions at the outset of the investigation.

A draft investigation report, identifying the safety issues, was prepared using the evidence collected and, in December 2011, was provided to all stakeholders for comment. Eighty-nine submissions on the draft report were received from pilots and organisational stakeholders. Additional evidence and information in the submissions was used to finalise the investigation report.

Coastal pilotage services

There are three providers of coastal pilotage services operating in direct competition with each other. The two larger pilotage providers, Australian Reef Pilots and Torres Pilots, service all of the pilotage areas and, between them, have 95 per cent of the market share. Both of these companies were formed in 1993 from the former Queensland Government regulated monopoly pilot service when economic regulation was discontinued, thus allowing competition in coastal pilotage. Hydro Pilots, the smallest provider, was established in 1996 and services only the Hydrographers Passage.

At the time of the ATSB survey, all coastal pilots were self-employed and exclusively contracted to either Australian Reef Pilots or Torres Pilots with the exception of two pilots contracted to Hydro Pilots. The three pilotage providers compete with each other for pilot bookings from ship owners or their agents. The providers assign their contractor pilots to booked ships and arrange pilot transfers using boats or helicopters.8 Hence, the actual pilotage service on any ship is provided by an individual contractor pilot.

Marine Orders Part 54

From 1993 onward, the regulatory framework for the safety of coastal pilotage operations has been contained in five successive issues of Marine Orders Part 54 (MO 54), regulations formed under the Commonwealth’s Navigation Act 1912 and administered by AMSA.

In 2001, issue 3 of MO 54 introduced the requirement for a pilotage provider to implement a safety management system (SMS) for its operations and areas of responsibility. A provider was defined as ‘a person who assigns or allocates a pilot’ to a ship’s transit, consistent with their existing role and functions (to manage pilot bookings, assign pilots and arrange pilot transfers). Consequently, provider SMSs pertained only to their operations, primarily assigning pilots to ships and pilot transfer services. The SMSs did not contain any specific content directly related to the actual pilotage task (e.g. standard operating procedures).

Also under MO 54 (issue 3), the responsibility for the safe conduct of a pilotage was specifically assigned to an individual pilot, consistent with the existing roles of pilots and providers. This reinforced the situation where each pilot had a unique piloting system including procedures and passage plans. While similar, no two pilots’ systems were the same. Since 2003, the adequacy of these different piloting systems, and the competency of pilots, has been assessed by their peers who are AMSA-licensed ‘check pilots’.

In 2006, issue 4 of MO 54 superseded issue 3 but largely retained the features described above. In December 2010, when the ATSB initiated this investigation, issue 4 of MO 54 was in force. Its provisions have largely shaped coastal pilotage operations until the time of the investigation and the survey in 2011 and hence, issue 4 directly relates to the subjects discussed in the investigation report.

On 1 July 2011, more than 6 months after the ATSB investigation started, issue 5 of MO 54 came into force. While issue 5 has a number of revised provisions relating to important areas such as SMSs and pilot boat standards, it still does not clearly assign the responsibility for the overall management of safety risks associated with pilotage to any organisation(s). Issue 5 was to be reviewed from 1 July 2012 (i.e. 12 months after its implementation).

The safety management of coastal pilotage differs from the modern, systems-based approach used in many Australian ports, where an SMS has been introduced to cover all safety aspects of pilotage operations. These SMSs have been implemented by the organisation responsible for the day-to-day management of pilotage in the port, i.e. a ‘pilot organisation’. Their objective is to reduce all of the identified safety risks associated with the port’s pilotage operations to as low as reasonably practicable and support pilots in the performance of their safety critical task. Consequently, the SMSs aim to provide risk-analysed, best-practice procedures, including standard passage plans for their port/pilotage areas, i.e. a ‘pilotage SMS’. The adequacy of these port pilotage SMSs is currently assessed through internal and external audits, in some cases by safety regulators, and reviews of the SMSs are regularly undertaken for continuous improvement.

However, in coastal pilotage, it is the individual pilots and check pilots, rather than the providers contracting them, who have responsibility for the safe management of pilotage operations. The providers mainly manage the bookings and logistics of pilotage services and there is no pilot organisation(s) identifying or managing all the safety risks associated with the actual pilotage task. The absence of a pilot organisation(s) defines the culture within the coastal pilotage sector, including working relationships, and impacts all pilotage related operations.

Standard passage plans

When this investigation was initiated, there were no standard passage plans or standard procedures for the various pilotages in the GBR and Torres Strait region. Hence, ship’s crews could not effectively prepare for a pilotage as the passage plan prepared by the crew in advance often had to be changed to reflect the individual plan of a pilot after he boarded. The same pilotage using a different pilot can also vary significantly. Each pilot employs different practices in the overall conduct of the pilotage and may provide different guidance, take different rest breaks during the long pilotages and have differing expectations of the crew.

In July 2011, AMSA posted an industry passage plan (IPP) model on its website to address the issue of non-standard passage plans. Issue 5 of MO 54 requires that all pilots must prepare detailed passage plans that use the IPP model and carry hard and electronic copies of the model plan. Ships can also request pilotage providers for the latest edition of the IPP or download an electronic copy via the internet.

Coastal pilot working arrangements

Coastal pilots are remunerated a set amount (depending on the pilotage area/route) for each discrete pilotage they perform, regardless of the time they are away from home on duty. They have no paid leave or other entitlements. Hence, the greater the number of pilotages performed by a pilot, the more the pilot will earn. Faster ships, higher paying pilotage routes and minimal periods between consecutive pilotages offer a better financial return for a pilot’s time. This remuneration framework has the potential to create a strong incentive to complete a pilotage quickly rather than as safely as possible. In the survey, half of the pilots asserted that financial disadvantage conflicts with the importance they aim to give to safety, largely because they are actively competing for work with other pilots contracted to the same provider.

A pilot’s fee for a pilotage is decided and set by the pilotage provider, with no input from the pilot. There is no set hourly or daily wage rate for coastal pilots (through regulation or otherwise). The majority of pilots have indicated they would prefer to be employees rather than contractors for the certainty and security of income and conditions. In general, the survey and submissions indicated a high level of discontent amongst pilots. At the time of the survey, five licensed pilots had effectively been dismissed by their provider by not being allocated work or offered a valid contract. In the 12 months following the survey, a further eight pilots left coastal pilotage for other employment and at least five others retired.

Pilot recruitment and training

Trainee pilots are recruited by the pilotage providers if they meet AMSA’s requirements for a trainee pilot licence. These requirements include qualifications as a ship’s master and recent seagoing experience. However, experience in the GBR or Torres Strait regions (local area experience) has not been a requirement since 1993, and most trainee pilots recruited after 2000 had little or no local area experience when they started.

Once issued with a trainee pilot licence, trainees fund most of their own training and receive reduced or no remuneration during that time. The providers see their role as merely providing a trainee pilot with the opportunity to complete the AMSA training program. The program is based on ‘self-learning’ by observing different pilots and generally requires a trainee to complete at least four transits of a pilotage area with a check pilot. At least one of the four transits must be fully assessed in accordance with the check pilot system.

In the absence of a pilotage SMS, including standard procedures and passage plans, a trainee pilot tends to develop a piloting system similar to but not necessarily the same as those he has observed. Initial training is not augmented with bridge simulator courses focused on coastal pilotage and there is no training in the use of electronic charting or equivalent systems.

Trainee pilots usually obtain a restricted licence in a couple of months (generally after completing a few more transits than the minimum of four). They can then pilot independently and earn an income. During the year or so that it usually takes them to obtain a full licence (without ship type or draught restrictions), new pilots gain more local area experience and develop their skills and individual piloting systems. For a new pilot with little or no previous local area experience, it is the transits undertaken in the first couple of years of piloting which provide the experience, knowledge and skill necessary for a local knowledge expert to operate confidently in a range of conditions and areas, particularly in confined passages.

Ongoing training consists of a mandatory course (usually 3 to 5 days) approved by AMSA for coastal pilot professional development once every 4 years. Both main pilotage providers pay the course fee for mandatory professional development courses for their contracted pilots while the pilots cover other costs, such as their travel and accommodation.

Pilot fatigue

The long coastal pilotages, particularly in the Inner Route, mean that pilot fatigue is a significant risk. A fatigue management plan has been implemented by AMSA based on mandatory rest periods before pilotage and between tours of duty, and minimum ‘leave’ periods. Pilots are expected to self-manage their fatigue during the actual pilotage where AMSA acknowledges that they need to rest, particularly during the long Inner Route pilotage.

The fatigue management plan does not prescribe the use of any method for predicting potential fatigue levels (best and worst case scenarios) nor is there measurement or assessment of actual levels of fatigue or the amount and quality of sleep that a pilot is able to have. Conditions during a pilotage, such as weather, traffic and the ship’s crew or equipment, may not allow the pilot to get the expected rest. In addition, a pilot’s travel and transfer time before boarding a ship have sometimes been included in the mandated rest periods, contrary to fatigue plan requirements.

The ATSB survey, pilot interviews and submissions indicated that pilot transfer services are a major source of discontent amongst most pilots because of long waiting times due to the scheduling of pilot boat or helicopter transfers and/or the condition of pilot boats.9 Transfers in the Torres Strait and Hydrographers Passage involve long distances and are influenced by factors such as the weather and transfer scheduling. In these areas, transfer times of 2 hours are common and, at times, can be much more. Scheduling transfers to carry more than one pilot minimises the provider’s costs but may also lead to additional waiting time for pilots. The survey suggested that travel and transfer time significantly affect the adequacy of a pilot’s rest before a pilotage.

The check pilot system

In the absence of a pilotage SMS promulgating uniform practices and procedures, AMSA’s check pilot system is relied on to assure safe pilotage standards (instead of a holistic SMS that includes a check pilot system). The AMSA system combines a pilot competency assessment, the usual function of a check pilot system, with an audit of the individual pilot’s system of pilotage against certain AMSA-defined criteria. With so many different piloting systems, including the check pilot’s own system, it is difficult for a check pilot to make objective and consistent assessments. Furthermore, AMSA’s guidance states that an assessment is only the check pilot’s opinion, not an indication of the assessed pilot’s competence or capability.

Although check pilots are effectively acting as AMSA’s delegates in the process, they are remunerated by the provider to assess contracted pilots. Assessing a pilot as ‘overall unsatisfactory’ (i.e. fail) can severely affect the failed pilot’s livelihood and disrupt the provider’s operations.

In case of an overall unsatisfactory assessment of an individual pilot, AMSA has a formal process to review the check pilot’s assessment. However, in the 550 check pilot assessments conducted until 2011, an AMSA review had never taken place because no pilot had been assessed as ‘overall unsatisfactory’. Analysis of these assessments by the ATSB showed that there can be a significant number of unsatisfactory findings with respect to different criteria without an ‘overall unsatisfactory’ rating. Furthermore, while a wealth of information has been gathered through the assessments, it has not been used by anyone to continuously improve pilotage practices or analyse the training needs of coastal pilots.

Risk event and incident reporting

Reporting of risk events, near misses and incidents is critical to understanding and mitigating the risks to the safety of navigation in the GBR and Torres Strait. The survey of pilots showed that the number of grounding or collision risk events which they claimed to have experienced was about 10 times the number of reports of such events in records held by AMSA and the providers. The main reasons given by pilots for under-reporting risk events are personal disadvantage, lack of corrective action and financial or organisational pressure; all these reasons largely related to their providers.

Another concern is the claimed incidence of collision risk events between piloted ships. The survey indicated that such high risk events occurred about once a month and usually involved the pilots of competing pilotage providers. A number of the pilots’ comments indicated that a lack of understanding each other’s intentions and/or communication was a factor in these cases due to an underlying reluctance to contact a pilot from a competing provider. This may be attributed to the fact that some pilots consider other pilots, including those contracted to their own provider, as competitors.

Great Barrier Reef and Torres Strait Vessel Traffic Service (REEFVTS)

The comments of pilots (in the survey, at interview and in submission) indicated that, in general, they were not aware of the capability and limitations of REEFVTS to monitor shipping and issue warnings to help avoid a serious incident. The service’s potential to support pilotage can be fully realised only when pilots better understand its systems and by improvements to the automated warning systems to ensure that they are optimally set up for the early detection of hazardous situations in all areas, particularly those areas in the Inner Route where pilots usually leave the bridge to rest.

Coastal pilotage in a system of safety

In recognition of the potentially severe and unacceptable environmental consequences of a serious shipping incident in the Torres Strait or GBR, Australia has a number of defences in the broader system of safety to protect the region. Coastal pilotage is the final layer in defences that include REEFVTS, enhanced ship routing and modern navigational aids, through which AMSA has enhanced the safety of navigation in the area.

However, while coastal pilotage is a critical defence, its safety management has lacked a pilot organisation responsible for managing all the risks associated with pilotage operations on a day-to-day basis. This safety issue is central to other issues and impacts all pilotage operations and related activities. The defence that a pilot provides against an incident can be much more effective when supported by a systems-based approach to managing risk through a pilot organisation’s SMS.

In the absence of organisational responsibility for the actual task of pilotage, the organisational influences of current pilotage providers affect all their business activities related to pilotage services. The contractual working arrangements of pilots and generally poor working relationships with their providers are a result of these organisational influences. A particular feature that promotes competition between pilots is their ‘per job’ (instead of time based) system of remuneration.

The sole objective of compulsory coastal pilotage is to provide assurance that the risk of a shipping accident in the GBR and Torres Strait PSSAs is reduced to as low as reasonably practicable or ALARP. This can only be effectively achieved by a pilot organisation(s) that actively and systematically manages all foreseeable safety risks in providing pilotage services with an appropriate level of guidance and oversight by the safety regulator. Further, the implementation of an effective safety management system in coastal pilotage can only be achieved by an organisation which promotes and fosters an effective organisational and industry safety culture with a business imperative to provide the safest possible coastal pilotage service.

Submissions to the draft investigation report

Eighty-nine stakeholders, including 71 pilots made submissions on the draft investigation report. Fifty-one pilots indicated support for the draft report/findings, two pilots opposed it and 18 submitted no comment without indicating whether or not they agreed with the report/findings. The submission from AMSA included safety action to address the safety issues identified in the report. The pilotage providers were opposed to the draft report and its findings and, effectively, did not propose any safety action. A number of stakeholders were positive that safety issues had been identified, a few made no significant comment and one organisation opposed some of the investigation’s findings.

The submissions served to highlight that addressing any safety issues in this fragmented pilotage sector is complicated.

ATSB investigation findings

The following summarise the safety issues identified by the ATSB:

  • Successive issues of MO 54 have not assigned the responsibility for the overall management of the safety risks associated with pilotage operations, including the task of pilotage itself, to pilotage providers or any other organisation(s). Therefore, no organisation has taken on the role of managing risk during pilotage on a day-to-day basis and developed a safety management system that addresses safety risks associated with all operations, including those during pilotage. Instead, each coastal pilot has his own piloting system and passage plans, and ship crews could not always obtain a passage plan before the pilot boarded. These multiple piloting systems increase the potential for less than optimal pilotage practices and are outside the scope of AMSA audits of provider safety management systems. The individual systems of pilots are only assessed by their peers under AMSA’s delegated check pilot system.
  • The effectiveness of the check pilot system is limited by the absence of standards against which to make objective assessments. The system is impacted by conflicts of interest as a result of complex working relationships and check pilots assessing peers on behalf of AMSA where an ‘overall unsatisfactory’ assessment (i.e. fail) could disadvantage the assessed pilot, the check pilot or the pilotage provider remunerating him. In addition, there is no formal review of assessments to help achieve continuous improvement and inform corrective action, unless a pilot is assessed as ‘overall unsatisfactory’ (which has never occurred).
  • The effectiveness of the pilot training program is limited by the absence of a pilotage safety management system, electronic charting systems training and the use of bridge simulators to augment shipboard transits for initial training. The mainly self-funded trainee pilots are also motivated to complete the training program quickly so they can pilot independently and earn to their potential. New pilots with little or no local area experience undertaking the program probably gain the experience, knowledge and skill appropriate for a local knowledge expert to operate in a range of conditions only after a couple of years of piloting.
  • The effectiveness of the fatigue management plan depends mainly on a self-managed approach and individual pilots face potentially conflicting priorities related to the impact on their earnings. The plan relies on the self-reporting of rest periods and evidence indicates that pilot travel and transfer times have sometimes been included (incorrectly) in rest periods. During long Inner Route pilotages, pilots may not be able to manage their anticipated rest adequately due to constraints imposed by weather, traffic or other circumstances. The plan’s effectiveness is further limited as it does not take into account variations in sleep patterns due to irregular working hours, the actual sleep a pilot achieves and the effect of multiple consecutive pilotages.
  • The apparent level of under-reporting of risk events, including near miss groundings and collisions, means valuable opportunities for improved risk management are being lost because many pilots believe they may be personally disadvantaged by reporting. Ad hoc, informal reports made by pilots in the past were not recorded or analysed by AMSA.
  • The potential for REEFVTS to support pilotage is under-utilised because many pilots are not fully aware of the service’s ship traffic monitoring capability and limitations, and its value as an additional ‘bridge resource’. Safety enhancements can also be achieved by focusing on improvements to the service’s automated warning systems to ensure that they are optimally set up for the early detection of hazardous situations in all areas, particularly those areas where pilots usually leave the bridge to rest.

The ATSB also found that, since the safety of pilotage operations is not the responsibility or the highest priority of pilotage providers, this is reflected in organisational influences that affect all their business activities related to pilotage services and pilots. The providers mainly operate a pilot booking and transfer service. The generally poor working relationships that pilots have with their providers are related to their contractual working arrangements and the ‘per job’ basis of remunerating pilots, which also promote competition between pilots. The areas impacted by these factors include fatigue management, the check pilot system and the incidence of risk events and their reporting.

Another key finding of the investigation is that the effectiveness of the broader system of safety protecting the GBR and Torres Strait PSSAs has been enhanced through a number of measures, including compulsory coastal pilotage, REEFVTS, ship routing and navigational aids. These are all measures attributable to AMSA’s action with the assistance of other agencies such as Maritime Safety Queensland, the state’s maritime regulator.

Safety action

Action has been taken or proposed by AMSA to address the safety issues identified. In addition to publishing the industry passage plan (IPP) model, significant action includes initiating the development of standard operating procedures for the task of conducting a pilotage. Following AMSA audits of the safety management systems of pilotage providers in January 2012, each provider has undertaken to develop such standard procedures for the pilots that they assign to ships.

In addition, a review of the provisions of MO 54, issue 5 by AMSA (from 1 July 2012) will seek to more clearly assign and articulate the responsibility of a pilotage provider for the overall management of safety risks associated with pilotage operations. In this respect, the Navigation Act 2012 (received the Royal Assent on 13 September 2012) includes a significantly revised, much broader definition for a pilotage provider that is consistent with an organisation that can be assigned responsibility for the overall safety management of pilotage under MO 54.

In 2012, AMSA initiated reviews of the check pilot system and the pilot training program which should complement improvements expected through passage plans based on the IPP model and standard pilotage procedures. Workshops that focus on pilot training have been hosted by AMSA, a pilotage training steering committee has been formed, and AMSA is considering the use of bridge simulators and the independence of check pilots.

Improvements to pilot fatigue management being considered by AMSA include going beyond straight rostering and hours on/off, and encouraging providers to develop fatigue management plans. In addition, AMSA will investigate the merits of a requirement for two pilots to conduct pilotages in the Inner Route.

To improve risk event reporting, AMSA implemented an on-line reporting system in 2012 and is considering opportunities to encourage pilot feedback and reporting through an increasing use of electronic exchange of information. The REEFVTS annual review process and invigorated stakeholder interaction will be used to enhance the service in areas identified by the ATSB investigation.

The ATSB has issued three recommendations to AMSA to fully address the central safety issue related to assigning responsibility for the overall safety management of pilotage to an organisation(s), and the issues concerning pilot training and fatigue management. Action to address the central issue is essential and will impact on the effectiveness of all other safety action taken.

The ATSB has also issued two recommendations to each of the three pilotage providers to take safety action in relation to fatigue management and risk event reporting that will support and facilitate the action taken by AMSA to address those safety issues.

Purpose of safety investigations

The objective of a safety investigation is to enhance transport safety. This is done through:

  • identifying safety issues and facilitating safety action to address those issues
  • providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.

It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.

Terminology

An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.

Publishing information 

Released in accordance with section 25 of the Transport Safety Investigation Act 2003

Published by:           Australian Transport Safety Bureau

© Commonwealth of Australia 2023

Ownership of intellectual property rights in this publication

Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.

Creative Commons licence

With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.

Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.

The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau

Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.

[1]           An area of the marine environment that needs special protection through action by the International Maritime Organization (IMO) because of its significance for recognised ecological, socio-economic or scientific attributes where such attributes may be vulnerable to damage by international shipping activities.

[2]           All ships of 70 m or more in length and all types of loaded tankers, irrespective of size.

[3]           A marine pilot’s local area knowledge and skills allow safer navigation of the area. In conducting a pilotage, the pilot effectively has control of the ship’s navigation but legally only provides relevant advice to its master who remains responsible and always in command of the ship. The pilot is not a member of the ship’s crew and is employed to provide services in a specific area.

[4]           AMSA web page www.amsa.gov.au (27 July 2011).

[5]           The IMO defines ‘very serious casualties’ as those that involve total loss of the ship, loss of life or severe pollution. ‘Serious casualties’ are those that do not qualify as ‘very serious casualties’ and involve incidents such as a collision, grounding, contact, fire or explosion, and result in rendering the ship unfit to proceed, pollution and/or breakdown necessitating towage or shore assistance.

[6]           United Nations Educational, Scientific and Cultural Organization (UNESCO), World Heritage Committee, 36th session, Mission Report - Great Barrier Reef (N154), Paris, 14 June 2012.

[7]           Draught is the measure of how deep a ship is floating in water and is the vertical distance between its keel and the waterline.

[8]           Each provider operates its own transfer service which the provider’s pilots must use.

[9]            In recent years, AMSA audits have indicated that the boats have generally met AMSA’s safety standards.

Occurrence summary

Investigation number 282-MI-2010-011
Occurrence date 16/12/2010
Location Queensland Coast
State Queensland
Report release date 24/10/2012
Report status Final
Investigation level Systemic
Investigation type Safety Issue Investigation
Investigation status Completed
Mode of transport Marine
Occurrence class Technical Analysis
Highest injury level None

Cockpit fumes and smoke - Aero Commander, VH-KAV, 333 km east of Brisbane Airport, Queensland, 14 December 2010

Summary

On 14 December 2010, the crew of an Aero Commander 500-S aircraft, registered VH-KAV, departed Norfolk Island for Brisbane, Queensland.

When about 180 NM (333 km) east of Brisbane, the crew noticed intense fumes in the cockpit followed by smoke emanating from the avionics panel. The pilot in command (PIC) shutdown the aircraft's electrical system and discharged the portable fire extinguisher. The smoke dissipated immediately after.

About 30 minutes later, the crew noticed that the hydraulic pressure had declined, and the unsafe landing gear light was illuminated. The crew reinstated the electrical system and attempted to restore the auxiliary hydraulic pump, but it did not respond.

In preparation for their arrival into Brisbane, the crew conducted an emergency landing gear extension.  The aircraft landed and vacated the runway. While taxiing to the parking area, smoke was observed emanating from the left engine. The PIC immediately shut down the aircraft and the crew egressed. It was determined that fluid from the hydraulic reservoir in the left engine was leaking onto the aircraft's brakes causing smoke.

A subsequent examination of the automatic direction finder (ADF) receiver found a burnt resistor and that a circuit board in close proximity had been damaged. A capacitor was found to have short circuited, which caused the resistor to burn.

Occurrence summary

Investigation number AO-2010-108
Occurrence date 14/12/2010
Location 333 km E of Brisbane Airport
State Queensland
Report release date 16/05/2011
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Smoke
Occurrence class Serious Incident
Highest injury level None

Aircraft details

Manufacturer Aero Commander
Model 500
Registration VH-KAV
Serial number 3164
Sector Piston
Operation type Private
Departure point Norfolk Island
Destination Brisbane, Qld
Damage Nil

Total power loss - Robinson R22, VH-FDL, 9 km north of Georgetown (ALA), Queensland, on 13 December 2010

Summary

On 13 December 2010, a Robinson Helicopter Company R22 Alpha helicopter, registered VH-FDL, departed the Georgetown aeroplane landing area (ALA), Queensland on a private, aerial photography flight over local mine sites.

When returning to Georgetown, at about 150 ft above ground level, the pilot reported that he applied engine power and then heard the engine splutter twice. This was immediately followed by a decrease in engine revolutions per minute (RPM) and the low rotor RPM warning horn sounding. The engine subsequently failed. The pilot regained control of the rotor RPM and conducted a forced landing. During the landing, the helicopter struck trees and contacted the ground heavily. The pilot sustained no injuries, while the passenger sustained serious injuries.

The engine was removed from the helicopter and examined by an independent maintenance organisation. The examination found about 7 to 10 mL of water in the carburettor. A subsequent power test was also conducted and the engine performed without fault.

The helicopter had been refuelled from drum stock on the morning of the accident flight. The drum stock was tested and no contaminants were reported.

An investigation conducted by the helicopter insurer was unable to determine if the water found in the carburettor contributed to the engine failure, or able to identify the source of water contamination.

Occurrence summary

Investigation number AO-2010-107
Occurrence date 13/12/2010
Location 9 km N Georgetown
State Queensland
Report release date 16/05/2011
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Engine failure or malfunction
Occurrence class Accident
Highest injury level Serious

Aircraft details

Manufacturer Robinson Helicopter Co
Model R22
Registration VH-FDL
Serial number 384
Sector Helicopter
Operation type Private
Departure point Unknown
Destination Georgetown, Qld
Damage Substantial

Aircraft proximity - Cessna 172, VH-CNW and Piper PA-28R-201, VH-AIZ, Ballarat Airport, Victoria, on 4 December 2010

Summary

On 4 December 2010, a Cessna Aircraft Company 172S aircraft, registered VH-CNW (CNW) and a Piper Aircraft Corp PA-28R-201 aircraft registered VH-AIZ (AIZ), were conducting concurrent training flights at Ballarat Airport, Victoria. A flight instructor and student were on board CNW and had entered the circuit with the intention of conducting a touch-and-go. AIZ was preparing to commence a flying training exercise from Ballarat Airport to the local training area with an instructor and student pilot on board.

CNW joined downwind for runway 05 due to glider activity on runway 36. While AIZ lined up on runway 36 due to the more favourable wind direction.

Following a touch-and-go landing on runway 05, CNW was between 70 and 150 ft above the ground, when the instructor saw an aircraft airborne off runway 36 passing from right to left in front of them, in close proximity. The instructor of AIZ became aware of CNW at about the same time and both instructors took control of their aircraft and carried out evasive action.

One instructor estimated they were within 15-30 m of each other horizontally, at about the same height.

While both aircraft made radio broadcasts, it could not be determined why they could hear other radio traffic in the area, but not each other.

The aircraft operator of AIZ has planned the following safety action in response to this incident:

  • Institute a training procedure for trainee pilots to positively identify the location of any aircraft making a radio broadcast on the common traffic advisory frequency (CTAF) at Ballarat Airport.
  • Conduct a workshop for all staff and trainees on situational awareness.

The aircraft operator of CNW has alerted their staff and students to be extra vigilant when operating in and around Ballarat Airport and have limited student pilots from entering the circuit at Ballarat.

Occurrence summary

Investigation number AO-2010-106
Occurrence date 04/12/2010
Location Ballarat Aerodrome
State Victoria
Report release date 16/05/2011
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Near collision
Occurrence class Serious Incident
Highest injury level None

Aircraft details

Manufacturer Cessna Aircraft Company
Model 172
Registration VH-CNW
Serial number 172S10386
Sector Piston
Operation type Flying Training
Departure point Ballarat Vic.
Destination Point Cook Vic.
Damage Nil

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-28
Registration VH-AIZ
Serial number 28R-7837104
Sector Piston
Operation type Flying Training
Damage Nil

Collision of grain train 3234 with grain train 8922, at Yass Junction, New South Wales, on 9 December 2010

Preliminary report

Preliminary report released 29 March 2011

The information contained in this Preliminary report is released in accordance with section 25 of the Transport Safety Investigation Act 2003 and is derived from the ongoing investigation of the occurrence. Readers are cautioned that new evidence will become available as the investigation progresses that will enhance the ATSB's understanding of the accident as outlined in this Preliminary report. As such, no analysis or findings are included in this report.

Abstract

At about 0153 on 9 December 2010 an Up (northbound) loaded grain train travelling from Barellan, New South Wales (NSW) to Maldon, NSW and numbered as 3234, collided at low speed with the rear of another Up (northbound) loaded grain train, numbered as 8922, on the Down2 Main line at Yass Junction, NSW. The intended operation had been for both trains to wait, one behind the other, on the Down Main line at Yass Junction to enable a third northbound goods train, 4MB2, to pass them both on the adjacent Up Main line.

On 25 May 2011, the draft ATSB investigation report into the incident was provided to directly involved parties for comment. The directly involved parties were asked to provide a submission addressing the report. All submissions will be considered before the report is finalised for public release

Final report

Abstract

At about 0153 on 9 December 2010 an Up (northbound) loaded grain train travelling from Barellan, New South Wales (NSW) to Maldon, NSW and numbered as 3234N, collided at low speed with the rear of another Up (northbound) loaded grain train, numbered as 8922N, on the Down Main line at Yass Junction, NSW. The intended operation had been for both trains to wait, one behind the other, on the Down Main line at Yass Junction to enable a third northbound goods train, 4MB2, to pass them both on the adjacent Up Main line.

Train 3234N proceeded as intended past a signal which indicated that the route was not clear and that the train should proceed at caution. Train 3234N braked as soon as train 8922N was sighted but a collision nevertheless ensued. The investigation highlighted that the definition of restricted speed applying in these sorts of cases requires considerable judgement on the part of train drivers.

Occurrence summary

Investigation number RO-2010-013
Occurrence date 09/12/2010
Location Yass Junction
State New South Wales
Report release date 30/01/2012
Report status Final
Investigation level Systemic
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Rail
Rail occurrence category Collision
Occurrence class Accident
Highest injury level None

Train details

Train number 3234
Type of operation Bulk grain
Departure point Barellan, NSW
Destination Maldon, NSW
Train damage Minor

Train details

Train number 8922
Type of operation Bulk grain
Departure point Red Bend, NSW
Destination Port Kembla, NSW
Train damage Nil

Right engine failure - Cessna 404, VH-XDA, near Mount Gordon (ALA), Queensland, on 9 December 2010

Summary

On 9 December 2010, a Cessna 404 aircraft, registered VH-XDA, was being operated on a charter passenger flight from Century Mine to Mount Isa, Queensland.

Shortly after departing, the pilot noticed that there was no output from the right alternator. The pilot turned the right alternator off and continued the flight.

While maintaining 9,000 ft, the pilot noticed that the right engine oil pressure gauge was indicating zero. At the time, the pilot believed that the gauge was faulty. A descent to 5,000 ft was commenced as a precaution.

During the descent, the right engine shut down. The pilot heard a loud bang and observed smoke emanating from the engine. The pilot actioned the emergency procedures checklist and commenced a diversion to the Mount Gordon aeroplane landing area (ALA). The aircraft landed without further incident.

A subsequent engineering examination determined that the alternator drive coupling on the right engine had failed.

As a result of this incident, the aircraft operator advised the ATSB of their intention to amend the maintenance schedule for aircraft fitted with Teledyne Continental Motors engines and gear driven alternators. By reducing the existing inspection interval of up to 500 hours, to at or before 220 hours.

Occurrence summary

Investigation number AO-2010-105
Occurrence date 09/12/2010
Location Mount Gordon (ALA)
State Queensland
Report release date 12/09/2011
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Engine failure or malfunction
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Cessna Aircraft Company
Model 404
Registration VH-XDA
Serial number 4040408
Sector Piston
Operation type Charter
Departure point Century Mine, Qld
Destination Mount Isa, Qld
Damage Nil

Breakdown of separation - Boeing B737-7Q8, VH-VBF and a Boeing B767-338, VH-OGU, near Melbourne Airport, Victoria, on 5 December 2010

Summary

On 5 December 2010, at 1422 Eastern Daylight-saving Time, a breakdown of separation occurred between a Boeing Company B737-7Q8 (737), registered VH-VBF, and a Boeing Company B767-338 (767), registered VH-OGU, on departure from Melbourne Airport, Victoria. The flight crew of the 737 had reduced their aircraft's speed in order to meet a height requirement of the Standard Instrument Departure. The following 767 aircraft climbed at a faster speed.

When the aircraft were transferred from the aerodrome controller to a departures controller, there was 3.4 NM (about 6.3 km) separation between them. The departures controller expected them to climb at a similar speed, and did not recognise the loss of separation assurance. The controller's actions to manage the compromised separation were not fully effective. At one point, radar separation had reduced to 1.9 NM (3.5 km) and vertical separation to 500 ft.

On 12 October 2011, a similar breakdown of separation occurred at Melbourne between an Airbus A320-232 and a Boeing Company 737-8BK. This incident involved different controllers to those involved in the 5 December 2010 incident.

The ATSB identified a safety issue in that the procedures for takeoffs at Melbourne Airport allowed for aircraft to depart relatively close to each other, with no documented requirements to ensure jet aircraft would maintain a set climb speed or to require flight crews to advise air traffic control if that speed could not be achieved. Although the Melbourne procedures were based on those used in Sydney, the Sydney procedures specified a minimum climb speed. The safety assessment report for the Melbourne procedures did not include a detailed comparison of the procedures used in the two locations. In response to the identified safety issue, Airservices Australia has commenced action to establish a standard speed profile for use at radar terminal area aerodromes in Australia, and to ensure that pilots of jet aircraft notify air traffic control when operating at a significantly lower speed than stipulated in that profile.

Occurrence summary

Investigation number AO-2010-104
Occurrence date 05/12/2010
Location near Melbourne Airport
State Victoria
Report release date 02/05/2012
Report status Final
Investigation level Systemic
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of separation
Occurrence class Serious Incident
Highest injury level None

Aircraft details

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

Aircraft details

Manufacturer The Boeing Company
Model 737
Registration VH-VBF
Serial number 30630
Sector Jet
Operation type Air Transport High Capacity
Departure point Melbourne, Vic.
Damage Nil