Strictly Scheduled: S-92A Start-Up Incident

Strictly Scheduled: S-92A Start-Up Incident (BHA VH-ZUQ Operating for Impex at Broome, WA)

Under customer induced time pressures, a pilot under going type conversion missed a unique action that was not explicitly allocated in the operator’s procedures.  Consequently the main rotor anti-flap stops of Sikorsky S-92A VH-ZUQ, operated by BHA, were damaged during start-up at Broome, WA on 10 November 2016, prior to a flight to an offshore installation.  The Australian Transport Safety Bureau (ATSB) explain:

The flight crew consisted of a pilot flying (PF) in the right crew seat, and pilot monitoring (PM) in the left crew seat.

The PM was undergoing conversion training on the S-92A and this was their first flight on the type as a PM having previously flown only as PF.

During the start procedure, the flight crew reported feeling abnormal vibrations in the airframe. A member of the ground crew then showed the pilots an anti-flap stop that had broken off the main rotor head.

S-92A anti-flap stop and securing hardware (Credit: via ATSB)

S-92A anti-flap stop and securing hardware (Credit: via ATSB)

Further inspection revealed that two anti-flap stops had been sheared off the main rotor head during start-up. The anti-flap stop failure was a result of the collective not being lowered at the appropriate point during the start procedure.

S-92A anti-flap stop secured to the main rotor hub (Credit: via ATSB)

S-92A anti-flap stop secured to the main rotor hub (Credit: via ATSB)

For engine starts with the rotor brake off, as were normally performed by this operator, the collective must be lowered as part of the start sequence. According to the operator’s standard operating procedures, the PF starts the number 1 engine first, and brings the throttle to idle. When the rotational speed of the main rotor is over 20%, and the hydraulic pressure reaches an appropriate level, the procedures state that the collective is to be moved to the full down position. The PF then starts the number 2 engine.

The ATSB identified that times pressures from Inpex, unfamiliarity and a lack of specificity in procedures all contributed.

Time Pressures

The ATSB say:

A series of events resulted in the flight crew having more tasks to complete than originally planned, and less time in which to complete them. This resulted in time pressure on the crew.

The crew conscientiously arrived about two hours before the scheduled early afternoon take-off (base instructions required them to report at least 90 minutes in advance).

…the PM was required to make a phone call to the company’s flight operations department and the crew were then involved in a discussion regarding the PM’s further training requirements.

Additionally as a result of a customer requirement:

The flight crew were also required to ‘shadow plan’ and perform the pre-flight inspection on a second aircraft, to ensure the flight could proceed in the event that ZUQ was unable to fly. According to the operator’s daily flying roster, the base pilot-in-command (PIC) [sic i.e the managing pilot at the base] was originally rostered on to be part of the backup crew. However, client obligations on the base prevented the PIC from being available in the event of the backup crew being required. The PF and PM were not aware of this prior to arriving, so they had not given themselves additional time to prepare a second aircraft before departure. Prior to departure, the PF was tasked with pre-flight inspections of ZUQ as well as the backup aircraft, but they were delayed as maintenance activities were still being conducted on ZUQ. In addition, flight data from ZUQ’s previous flight [that morning] had not yet been downloaded and analysed, further delaying the PF. The flight crew perceived a significant amount of pressure from the operator’s client for this flight. They believed that this client, more than any other they were aware of, required flights to adhere to strict schedules.

The crew did recognise the time pressures:

As a result of feeling rushed and to ensure that they were fully prepared for the flight, they completed a second threat and error review, rechecked the flight plan together, rechecked the helicopter’s technical log and walked to the helicopter together.


The ATSB comment that:

The PM’s unfamiliarity with the unique starting procedures in the S-92A compared with other helicopters contributed to the collective not being lowered in time.

The S-92A was the only helicopter in the operator’s fleet that required the collective to be lowered as part of the start sequence. It was also the only helicopter where responsibility for controls was split between the two pilots.


ATSB say:

The operator’s procedures did not designate the task of lowering the collective to either the PM or PF. However, the operator’s parent company uses procedures that specifically assign the role to the PM. Despite not being contained in the operator’s procedures, both pilots understood that it was the role of the PM to lower the collective during engine start and this had been briefed prior to the engine start. The operator’s standard operating procedures did not require any call outs for the lowering of the collective, which probably contributed to the collective not being lowered in time.

Safety Action

The operator immediately commenced their own investigation which identified 17 recommendations, which the ATSB describe as a “proactive response”. These included:

  • A review of S-92A start procedures, addressing as a minimum:
    • Flight crew division of duties with specific regard for the collective control lever
    • Standardised calls relating to the position of the collective control lever
    • The use of the rotor brake for the start procedure (this makes it easier for a single pilot to operate all controls, as the engines can be started before control input is required)
  • Changes to the engine start procedures, the section on lowering the collective is currently written in a ’Note’, this will be changed to a ‘Caution’ to highlight its importance to flight crew
  • A review of the policy and procedures used for shadow planning be undertaken, addressing as a minimum all hazards and risks associated with shadow planning inclusive of whether flight crew undergoing training should be exposed to the requirement.

ATSB Safety Message

This incident is an example of what can occur when pressure associated with on-time departures is compounded with the absence of clear operating procedures. It is important that pilots have detailed and specific instructions on which to fall back when they feel pressure beginning to build.

Our Comments

Multi Crew Operation, involves more having multiple crew members, as it needs clear allocation of duties between PF and PM.  In this case the responsibility in relation to a relatively unique feature of this aircraft type were not specified in the operator’s procedures. Apart from the extra discussion on the PM’s training and waiting for the prime aircraft to be readied, the ATSB report shows main time pressures were due to:

  • The need to routinely ‘shadow plan’ i.e. prepare a second aircraft for the unidentified oil and gas customer (presumably to minimise schedule disruption if the prime aircraft became unserviceable)
  • The unspecified ‘customer obligation’ that meant that the base managing pilot was unavailable so the prime crew also had to do the shadow planning too at short notice
  • The perception of “significant” customer pressure for this specific flight
  • An inherent belief that this customer was particularly focused on “strict schedules”

In this case those time pressures were recognised and only resulted in damage to the aircraft on the ground.  All customers contracting air services need to recognise that they can adversely affect flight safety though their procedures and behaviours. In the case of a Wrong Deck Landing (WDL) in the North Sea in 2014, the crew were interrupted both on the previous helideck and while on approach by customer radio calls.

In another case, the CHIRP Charitable Trust, who run the UK’s Confidential Human Factors Incident Reporting Programme were: Critical of an Oil Company’s Commercial Practices.  This followed the early termination of n contract ‘for convenience’ and the introduction of a new air operator.

UPDATE 31 May 2017: The US National Transportation Safety Board (NTSB) commented on customer scheduling pressures by cruise lines after the loss of de Havilland DHC-3 Otter floatplane, N270PA in a CFIT in Alaska and the loss of 9 lives: All Aboard CFIT: Alaskan Sightseeing Fatal Flight

UPDATE 28 April 2018: An AW109SP, Overweight VIPs and Crew Stress  A heavy landing after a crew were put under considerable stress during a poorly planned VIP flight booking and a hurried overweight take off in the UAE.

UPDATE 6 August 2018: In-Flight Flying Control Failure: Indonesian Sikorsky S-76C+ PK-FUP

UPDATE 7 February 2020: S-61N Damaged During Take Off When Swashplate Seized Due to Corrosion

UPDATE 19 April 2020SAR Helicopter Loss of Control at Night: ATSB Report

UPDATE 8 May 2022: HeliOffshore 2022 Conference Review

UPDATE 14 May 2022: Review of “The impact of human factors on pilots’ safety behavior in offshore aviation – Brazil”

Aerossurance has extensive air safety, operations, airworthiness, human factors, aviation regulation and safety analysis experience.  For practical aviation advice you can trust, contact us at: