Descent below approach path involving a Boeing 777, VH-VPF, Melbourne Airport, Victoria, on 15 August 2013

On 15 August 2013, a Boeing 777-3ZGER (B777), registered VH-VPF and operated by Virgin Australia International Airlines (Virgin), was on a scheduled flight from Los Angeles, United States to Melbourne, Victoria with 17 crew^[1] and 272 passengers on board. The flight was cleared for an approach and landing on runway 34 at Melbourne Airport via the LIZZI SEVEN VICTOR (LIZZI 7V) standard arrival route (STAR) via the MAITE, IGPON, MONTY, EGEKA and SHEED waypoints (Figure 1). The captain was the pilot flying and the first officer (FO) was the pilot monitoring the approach.

Figure 1: Aeronautical chart for Melbourne LIZZI 7 STAR

Source: Virgin

During the STAR, the aircraft was fully configured for the final approach with the landing gear down and landing flaps set. The autopilot was engaged in both vertical and lateral navigation modes.^[2] At about 0810 Eastern Standard Time,^[3] after passing waypoint SHEED,^[4] the final waypoint in the STAR, the autopilot increased the rate of descent from about 700 ft/min to about 1,500 ft/min. This was greater than the crew were expecting and the FO alerted the captain to the high descent rate. As the captain expected it to reduce and stabilise at the anticipated rate, they decided to continue the approach and monitor the aircraft’s rate of descent.

Noting that the captain was concentrating on the information presented on the aircraft’s flight instruments, the FO turned their attention outside of the cockpit to visually monitor the approach to the runway, which they had sighted to the right of the aircraft. The FO noted that the approach appeared to be too low and alerted the captain, who agreed and attempted to reduce the rate of descent by engaging the vertical speed mode of the autopilot flight director system. The captain then disconnected the autopilot and took manual control of the aircraft. The aircraft was levelled off at about 700 ft above mean sea level (AMSL), or about 500 ft above ground level, and turned to the right to align with the runway. The FO alerted the captain to the precision approach path indicator (PAPI)^[5], which was showing four red lights, indicating that they were well below the correct glide path.

The aircraft was flown level until re-established on the correct glide path for a normal approach and landing. Figure 2 shows the aircraft’s flight path during the approach and landing.

Figure 2: Approach flight path into Melbourne Airport

 

Source: Google earth, modified by the ATSB

Preparation for the approach

Prior to descent into Melbourne, while the FO was on a rest break in the flight crew rest compartment, the captain decided that, although runway 27 was the active runway for arrivals, they would land on runway 34. The captain reported that this decision was based on the increased landing distance available with runway 34 and on more favourable crosswind conditions for the landing. A number of routes were available for the approach and landing on runway 34, including a visual approach, which the captain elected to conduct via the LIZZI 7V STAR.

In accordance with Virgin standard operating procedures, as the pilot flying, the captain selected the runway 34 waypoint (RW34)^[6] from the database in the aircraft’s flight management system (FMS) and the LIZZI 7V STAR from the available approach options for that runway. The LIZZI 7V STAR ended at the SHEED waypoint, which is not aligned with the runway 34 centreline. This meant that connecting the flight plan directly from SHEED to RW34 (representing the runway threshold) would have resulted in a final approach that did not track along the runway centre-line. To account for this and more appropriately align the final approach with the runway centre-line, the captain used a feature in the FMS that produced an additional waypoint (labelled RX34) that was offset back along an extended runway centre-line.

The target altitude for RX34 was automatically calculated by the FMS based upon the position and altitudes of the RW34 and SHEED waypoints. In accordance with the advice in the Virgin Route and Airport Information Manual,^[7] the captain entered a runway extension of 2.8 NM (about 5 km) into the FMS, which created RX34 (see the section titled Briefing paper). They also intended to amend the altitude of the RW34 waypoint to 380 ft as per the recommendation in the manual, although the altitude was inadvertently entered into RX34 rather than RW34.

The captain reported that the cruise relief FO, who had replaced the FO during their rest break and was occupying the right seat at the time, checked the information that was entered into the FMS before the flight plan was activated. The captain also reported not specifically requesting the cruise relief FO to validate the data entered into the FMS.^[8]

When the FO returned to the flight deck after their rest break, and as part of the before descent checks, they checked and validated the arrival and approach data entered into the FMS. The FO reported some confusion during those checks as a result of noticing that the FMS did not present the expected glide path angle for the final legs of the approach. The FO queried this with the captain, who informed the FO that the FMS did not present that information for a manually constructed approach. The FO accepted this explanation and continued with the before descent checks. The FO recalled reviewing the Route and Airport Information Manual during the checks and checking that the altitude value of 380 ft was correct, but did not identify that the altitude had been entered into RX34 rather than the intended RW34.

1. Comprised of four flight crew and 13 cabin crew. All four flight crew were in the cockpit during the arrival and approach to Melbourne Airport.
2. In vertical navigation (VNAV) path mode, the aircraft’s altitude is directed by the autopilot flight director system (AFDS) to follow a predetermined vertical profile entered into the flight management system (FMS). Similarly, in lateral navigation (LNAV) mode, the aircraft’s location is automatically directed by the AFDS to follow a predetermined track entered into the FMS.
3. Eastern Standard Time (EST) was Coordinated Universal Time (UTC) + 10 hours.
4. Waypoint SHEED was located overhead the threshold of runway 26 at Essendon Airport, about 8 km southeast of the Melbourne Airport runway 34 threshold.
5. A ground-based, visual approach indicating system that uses a colour discriminating system that is used by pilots to identify the correct glide path to the runway.
6. RW34 was a waypoint that represented the location of the threshold for runway 34.
7. The Route and Airport Information manual formed part of the Virgin Operations Manual and contained important information and advice for the flight crew regarding particular aspects of their operation. This included information pertaining to operations at particular airports.
8. Validation of the data would have required the cruise relief FO to directly compare the data with the source of that information, in this case the chart for the LIZZI 7V approach and the Route and Airport Information Manual.

Personnel information

The flight crew consisted of a captain, a first officer (FO) and, due to the duration of the flight, two cruise relief FOs. The captain and FO were in the operating seats during the take-off and landing.

The flight was a long-range flight that was rostered as a 17-hour duty, with a 15hour flight time. Given the duration of the flight, Virgin Australia Airlines (Virgin) provided rest periods for the operating crew during the cruise. The role of a cruise relief FO was to replace an operating crew member to allow them to rest as required in the flight crew rest compartment when established in cruise. The flight was operated according to Virgin’s fatigue risk management system, which was approved by the Civil Aviation Safety Authority. A review of the fatigue risk management system found that it met the current best practice guidance available from the International Civil Aviation Organization.

Captain

The captain held an Air Transport Pilot (Aeroplane) Licence (ATPL(A)) and was endorsed to operate B777 aircraft. They held a valid Class 1 Aviation Medical Certificate with a restriction that reading correction was to be available whilst exercising the privileges of the licence.

The captain’s aeronautical experience is outlined in Table 1.

Table 1: Captain's aeronautical experience

In addition to their operational flight duties, the captain was also an approved check and training captain. The captain reported having recently completed a visual approach via the SHEED waypoint to runway 34 in the simulator and once during line operations 4–5 months prior.

The captain had 10 days off, followed by a rostered standby day with no duty, prior to operating the outbound flight from Sydney to Los Angeles on 12 August 2013. Prior to commencing duty for the occurrence flight, the captain had about 35 hours free of duty in Los Angeles and reported obtaining about 13 hours sleep during that time. On the occurrence flight, they obtained 3 hours sleep during a rest break, which was described as ‘good quality’. There was an additional rest break taken during the flight, however no further sleep was obtained. The captain reported feeling tired as the aircraft approached Melbourne but considered this ‘normal’ for the length of the flight.

First Officer

The FO held an ATPL(A) and was endorsed to operate B777 aircraft. They held a valid Class 1 Aviation Medical Certificate with nil restrictions.

The FO’s aeronautical experience is outlined in Table 2.

Table 2: FO’s aeronautical experience

In addition to their operational flight duties, the FO was also an approved training FO, and was providing training to one of the cruise relief FOs during the flight.

The FO reported that they had flown into Melbourne on four previous occasions, but that this was their first experience of a visual approach to Melbourne Airport runway 34 via the SHEED waypoint. They had previously conducted the approach in the simulator, but reported that they had not done so for over 18 months.

Prior to operating the outbound flight to Los Angeles, the FO had 2 rostered days off and a standby day with no duty. They also had about 35 hours free of duty in Los Angeles and reported obtaining about 16 and a half hours sleep. The FO reported this as ‘good quality’ sleep and that they obtained about an hour’s sleep during the first inflight rest break and about an hour and a half during the second rest break. The FO reported feeling alert at the start of the flight and tired on arrival at Melbourne, which was considered ‘normal’ given the flight time. The FO felt that the provision of training to one of the cruise relief FOs increased the FO’s level of tiredness.

Cruise relief First Officer 1

The first of the cruise relief FOs held an ATPL(A) and was endorsed to operate B777 aircraft. They held a valid Class 1 Aviation Medical Certificate with a restriction that distance vision correction must be worn whilst exercising the privileges of the licence.

The first cruise relief FO’s aeronautical experience is outlined in Table 3.

Table 3: Cruise relief first officer 1’s aeronautical experience

 The first cruise relief FO was occupying the FO’s seat during the FO’s rest period.

Cruise relief First Officer 2

The second cruise relief FO held an ATPL(A) and was endorsed to operate B777 aircraft. They held a valid Class 1 Aviation Medical Certificate with nil restrictions. This cruise relief FO was undergoing line training during the flight.

The second cruise relief FO’s aeronautical experience is outlined in Table 4.

Table 4: Cruise relief first officer 2’s aeronautical experience

Aircraft information

Flight control

The Boeing 777 can be manually controlled by the pilots via a conventional set of flight controls, or automatically using the aircraft‘s autopilot flight director system (AFDS). The AFDS can make a number of control inputs depending on the mode selected. These modes range from holding a selected heading and/or altitude to complete control through a pre-programmed flight management system (FMS) flight path in lateral flight path (LNAV) and vertical flight path (VNAV) modes. The AFDS is controlled through the AFDS mode control panel, located on the instrument panel glare shield in front of the pilots.

Altitude, heading, vertical speed, flight path angle and/or airspeed can all be set by the flight crew through the mode control panel and either automatically controlled by the autopilot or displayed to the flight crew on the flight director on the flight displays. Alternatively, guidance information for a pre-determined flight path can provided to the AFDS through the FMS.

Flight management system

The FMS is an integrated electronic system that provides the flight crew with various functions including navigation, performance optimisation and fuel monitoring, and cockpit displays. The FMS contains functions that manage the aircraft’s lateral and vertical navigation. The FMS incorporates a navigation database that contains the necessary pre-programmed waypoints to fly routes, standard instrument departures (SID), standard arrival routes (STAR) and other standard flight procedures.

A flight plan of the lateral, vertical and speed profiles for a flight can be either uploaded into the FMS as a complete plan or manually constructed by the flight crew using the waypoints contained in the navigation database in the FMS. The FMS then uses the aircraft’s current position and supporting system data to calculate commands for flight path control, which are sent to the AFDS. Map and route data are sent by the FMS to the navigation displays for visual presentation to the flight crew.

The commands for flight path control are presented to the flight crew through the flight director, which provides command bars on the primary flight display. The flight crew can make manual inputs to the aircraft’s flight controls to attain the flight director commands, or they can be automatically accomplished by engaging the autopilot.

The flight crew’s primary interface with the FMS is via the control display units (CDUs). Three CDUs are located in the centre pedestal, one each for the captain and FO (Figure 3), and a third at the rear of the pedestal, as a backup. Each CDU contains a screen for presenting FMS information and a keypad to allow the flight crew to navigate through the various pages and enter and modify FMS data. The screen contains a number of lines of information with line selection keys that allow each line to be selected to either enter or modify the data in that line. Data is entered into the CDU via the scratchpad, using the keypad at the bottom of the screen. The scratchpad is also used to present messages to the flight crew in relation to the operation of the FMS (Figure 4).

Figure 3: Captain and FO CDUs

Source: ATSB

Figure 4: CDU detail

Source: ATSB

Meteorological information

Observations from the Melbourne Airport automatic weather station were recorded every half hour. The surface weather conditions recorded at 0800 were a temperature of 9 °C, wind direction of 350° at 8 kt, QNH^[9] 1019 hPa, with Few^[10] cloud at 3,600 ft and visibility greater than 10 km with only a negligible change observed by 0830.

As sunrise was at 0705, and given the observed weather, the approach and landing occurred during daytime visual conditions.

Aids to navigation

Melbourne Airport runway 34 had three approaches available, an RNAV GNSS^[11], a VOR^[12] and a visual approach. Only the visual approach could be conducted using the LIZZI 7V STAR, as the other two approaches required the use of a different STAR that routed the aircraft over the BOLTY waypoint. BOLTY was further to the south of Melbourne Airport, before turning onto the final approach heading.

The LIZZI 7V STAR commenced at the LIZZI waypoint north-east of Melbourne Airport, and sequenced through the waypoints MAITE, IGPON, MONTY and EGEKA before completing at SHEED (Figure 1). SHEED was located overhead Essendon Airport, to the southeast of Melbourne Airport, and had a minimum altitude requirement of 2,500 ft to prevent conflict with traffic around Essendon Airport. All of these waypoints were stored in the database in the FMS.

The flight crew were using maps and charts that were provided by Virgin. The ATSB determined that the chart for the LIZZI 7V STAR/visual approach was valid for the time of the occurrence. The chart showed that the visual segment consisted of a right turn to align with runway 34. The elevation of the runway threshold was 330 ft.

Approach aids

Visual guidance to runway 34 was provided by sequenced lead-in strobe lights to assist crews conduct a visual turn onto final and a precision approach path indicator (PAPI) system, which provided glide path guidance. The PAPI consists of four indicator lights adjacent to the runway that can be either red (indicating low on approach) or white (indicating high on approach) and provides visual vertical guidance to the flight crew to assist them on attaining the appropriate glide path angle.

Melbourne Airport runway 34 has a PAPI on the left and right sides of the runway that are set to provide a glide path angle of 3°. The flight crew reported that the PAPI was not visible until they were on the right turn to align with the runway, which is when they would normally start using it for glide path reference.

Recorded data

The ATSB obtained a copy of the data recorded on the aircraft’s quick access recorder (QAR), including of the occurrence flight. Selected parameters from that data are provided in Figure 5.

Figure 5: Selected QAR data showing the occurrence after passing SHEED

Tests and research

In November 2013, the ATSB participated in a session in Virgin’s B777 full flight simulator to observe the differences in a Melbourne Airport runway 34 visual approach via the LIZZI 7V STAR with the correct and incorrect data entered into the FMS. The following observations were made:

Approach with the correct data in the FMS

During the approach with the correct data in the FMS it was found that after passing SHEED, the rate of descent increased to 1,450 ft/min before it decreased, settling at about 850 ft/min.

Approach with incorrect data in the FMS

During an approach using the data entered by the crew in this occurrence, it was found that:

• after passing SHEED, the rate of descent increased to about 1,900 ft/min, before settling to about 1,850 ft/min^[13]
• the PAPI was not distinguishable until around 1,000 ft and about to commence the turn onto final. At that point, the PAPI was displaying 4 red lights.^[14]

Organisational and management information

Operational information

Virgin provided the following information regarding the Melbourne Airport runway 34 visual approach from the LIZZI 7V STAR in their Route and Airport Information Manual (Figure 6).

Figure 6: Presentation of information regarding the visual approach via SHEED in the operator’s Route and Information Manual

An approach and landing on Melbourne Airport runway 34 using a visual approach via SHEED was included as part of Virgin’s refresher training program. In this respect the Instructor Guide for simulator refresher training included the runway visual approach via SHEED as part of a two session refresher training package that included numerous other items of training. The training was structured such that an FO under training would be the pilot flying the visual approach.

The Instructor Guide provided the same information as that contained in the Route and Airport Information Manual, but because the formatting differed from that manual the line break at the end of the second point occurred at a different point within the text and all information about the runway extension was contained on the one line (Figure 7).

Figure 7: Presentation of information regarding the visual approach via SHEED in the operator’s Instructor Guide for refresher training

On 28 July 2013, Virgin’s Flight Training/Standards branch released a Briefing Paper regarding the visual approach via SHEED.^[15] The Briefing Paper was released when an analysis by Virgin of a number of occurrences of high rates of descent during the approach were found to result from (in part):

• Delayed descent from SHEED
• Autopilot disconnect during the turn onto final
• FMC programming resulting in an above path PAPI indication when established on final.

A number of recommendations were included in the Briefing Paper in an attempt to prevent recurrence, although none of these had been included in operational procedures at the time of the occurrence. Those recommendations included:

• Crew who are tired or fatigued should plan for and require the RNAV GNSS Approach
• Briefing for the approach should cover AP [autopilot] use, the likelihood of increased decent rates and the requirement for a delayed stabilisation (500 ft Above Aerodrome Level), including the associated calls
• The FMC should be programmed in accordance with the C1 [Route and Airport Information Manual] with a hard altitude at the 2.8nm extension that places the aircraft on a 3° approach (1,270 ft) rather than leaving the higher FMC calculated value
• With the FMC programmed, the AP in LNAV/VNAV is available for the approach through the turn to final down to 200 ft AGL. While closely monitoring for acceptable performance – AP use is recommended for the approach.
• Vertical path corrections with modes other than VNAV is not recommended – any unacceptable behaviour of LNAV/VNAV must be corrected manually with the AP disconnected of [or] a go-around commenced.

The Briefing Paper also included expanded FMC configuration information (Figure 8).

Figure 8: Expanded FMC configuration information^[16]

Related occurrences

ATSB investigation AO-2013-010^[17]

On 10 January 2013, the crew of an Embraer Regional Jet 170 was conducting a scheduled passenger service from Darwin to McArthur River Mine, Northern Territory. Shortly after passing navigational waypoint SNOOD, 125 NM (232 km) north-west of McArthur River Mine, the aircraft’s flight path started diverging from its planned track. The problem was identified by air traffic control and the crew were advised.

The ATSB found that, while updating the aircraft’s flight management system for the descent into McArthur River Mine, the crew unintentionally omitted entering an intended navigational waypoint that was located 25 NM (46 km) north-west of McArthur River Mine. This omission resulted in the aircraft’s autopilot tracking the aircraft direct to the initial approach fix instead of first tracking to the intended waypoint. The crew’s crosschecking processes were not effective in identifying the data input error.

1. Altimeter barometric pressure subscale setting to provide indication of height above mean sea level in that area.
2. Cloud cover is normally reported using expressions that denote the extent of the cover. The expression few indicates that up to a quarter of the sky was covered.
3. Area Navigation (RNAV) Global Navigation Satellite System (GNSS).
4. VHF omni-directional radio range.
5. These values were a little higher than recorded on the QAR, but were likely due to slightly different winds set in the simulator to those on the morning of the occurrence, and a slightly higher airspeed during the simulator session.
6. The brightness of the airport lights, including the PAPI, could be varied in the simulator. The captain for the simulator session noted that they were probably set a bit brighter during the session than they would have been on the morning of the occurrence.
7. The briefing Paper noted that ‘This document reviews the Melbourne RW34 Visual Approach via SHEED and recommends operating techniques. This document is not intended for provision to crew as a briefing document but will result in updates to relevant company documentation.’
8. TCH. Threshold crossing height.
9. ATSB investigation report AO-2013-010 Navigation event involving Embraer E170 VH-ANO published 22 August 2014.

Introduction

Data input errors when programming a flight management system (FMS) are not uncommon (PARC/CAST Flight Deck Automation Working Group 2013). They are usually detected by the flight crew before there is any effect on the aircraft’s flight path or performance. On rare occasions, programming errors can lead to problems with the aircraft’s flight path or performance,^[18] and on very rare occasions contribute to aircraft accidents.^[19]

Although data-entry error has the potential to become a hazard to flight safety, the risk associated with the high descent rate on the occurrence flight was minimal given the approach was in visual conditions and the crew were not experiencing any significant workload or other difficulties.

This analysis examines the various human performance factors identified during the investigation as having influenced the flight crew’s actions and ability to detect the erroneous data.

Data input error and error detection

During the entry of the visual approach into the FMS, the captain inadvertently entered the runway threshold crossing altitude of runway threshold elevation + 50 ft into runway extension waypoint RX34, instead of into the intended RW34. RW34 corresponded with the runway threshold. This resulted in the aircraft descending after SHEED to meet this erroneous waypoint altitude constraint, which was 2.8 NM or about 5 km from the runway threshold and therefore necessitated a higher than normal descent rate to achieve the RX34 altitude constraint as set.

The erroneous entry of the runway threshold crossing altitude at the RX34 waypoint was almost certainly a skill-based error known as a ‘slip’, which is an error in the execution of an action (Reason 1990). Skill-based actions are those which have become so rehearsed and automatic that the individual does not need to closely monitor each stage of the action sequence in the way that they would if the task was less familiar or unknown. Due to this reduced monitoring, the individual will generally not realise that they have carried out an incorrect action until it is either too late to change, or there has already been an unforeseen consequence.

An observational study of airline operations examining error detection and recovery noted that ‘less than half the errors committed by crew were actually detected’ (Thomas, Petrilli and Dawson 2004). A number of factors may have increased the likelihood of the crew not detecting the error on this occasion.

The captain reported that the cruise relief first officer (FO) conducted a crosscheck of the FMS data, but did not ‘validate’ the data against the approach chart or Route and Airport Information Manual. This check was intended to be a gross error check only, and the operational FO was expected to check and validate the data upon their return from a break in the flight crew rest compartment. However, the operational flight crew’s checks may have been degraded because they unintentionally and unconsciously felt that this crosscheck would have detected any error in the data. Although not intended as a formal validation of the data input by the captain, this gross error check by the cruise relief FO was an opportunity for the error to have been identified.

The operational FO had just returned from a rest break and was not expecting to conduct a visual approach. The FO initially questioned the decision to conduct a visual approach, primarily because it required a level of precision which added complexity at the end of a 15-hour flight. However, the captain explained that they had conducted this approach in the simulator and had flown one during line operations. Together with the FO’s perception of the captain’s experience and reputation, this made the FO comfortable enough to accept the captain’s decision to conduct a visual approach.

On review of the FMS, the operational FO identified that, contrary to their expectation, the glide path angle was not displayed. The FO queried this with the captain. While this issue was quickly resolved, it is possible that exploring this issue distracted the FO from the check. The FO recalled checking the Route and Airport Information Manual and that the runway threshold crossing altitude was in the FMS. Regardless, the erroneous position of that altitude was not detected. Although the ATSB was not able to precisely determine what led to the erroneous data entry not being detected, a number of factors were identified that may have influenced the non-detection.

The operator’s Route and Airport Information Manual contained guidance on conducting a visual approach to runway 34 via the SHEED waypoint. The presentation of this information as a sentence that was broken over a number of lines was such that it was possible to associate the words ‘and altitude 0380’ with the runway extension waypoint (RX34), rather than the intended runway threshold waypoint (RW34). This increased the potential for this incorrect altitude to be entered against RX34, rather than the ‘“hard” altitude’ of 1,270 ft as recommended in the Virgin briefing paper.

The possible association of the altitude of 380 ft with RX34 was not the intention of the guidance, nor the deliberate action of the flight crew on this occasion. However, the ATSB noted that if the crew had been able to directly compare the altitudes in the FMS with the associated waypoint in a more graphical presentation, such as the table presented in the Briefing Paper and the accompanying expanded flight management computer configuration information (Figure 8), the probability of detecting the error would have been increased. This would have resulted from the crew’s improved awareness of the three altitudes to check (SHEED, RX34 and RW34), and their ability to individually check each against the appropriate waypoint.

Previous data entry error occurrences have highlighted the role of expectancy in influencing flight crew error detection. On this occasion, the similarity of the waypoint names RW34 and RX34 increased the likelihood that the crew could misinterpret one waypoint for the other when entering and/or checking the data.

The high descent rate after the aircraft passed the SHEED waypoint was initially identified by the operational FO. The captain believed that this was a normal aircraft response (as confirmed by the ATSB in the operator’s simulator) and that the descent would stabilise at a lower rate. When it did not stabilise as expected, the captain’s attention became focused on monitoring the rate of descent on the aircraft’s instruments instead of including in their scan the external flight path cues necessary for conducting a visual approach. Noting the captain’s change of focus, the FO changed attention from monitoring the approach on the aircraft instruments to monitoring the external visual cues. This led to a delayed recognition of, and reaction to, the aircraft’s descent below the intended approach path. It was not until the FO alerted the captain to the approach appearing to be too low, that the result of the descent rate was identified, and action taken by the captain to regain the correct approach profile.

Crew fatigue

The International Civil Aviation Organization (ICAO 2011) defined fatigue as:

A physiological state of reduced mental or physical performance capability resulting from sleep loss or extended wakefulness, circadian phase, or workload (mental and/or physical activity) that can impair a crew member’s alertness and ability to safely operate an aircraft or perform safety related duties.

Fatigue can have a range of adverse influences on human performance. These include slowed reaction time, decreased work efficiency, reduced motivational drive and increased variability in work performance, lapses or errors of omission (Battelle Memorial Institute 1998).

While research indicates that less than 6 hours sleep in the previous 24 hours can increase risk (Thomas and Ferguson 2010), the captain had about 10 hours sleep in the 24 hours prior to departure and the operational FO had about 12 and a half hours. In addition, the flight crew reported obtaining adequate ‘good quality’ sleep during the layover in Los Angeles and feeling well rested at the commencement of the flight. However, the effect of extended wakefulness for both crew and workload due to training duties for the FO meant that both crew were probably experiencing a level of fatigue known to have a detrimental effect on performance.

A fatigue risk management system (FRMS) is designed to manage the fatigue risk associated with operations, including long-haul flights. However, it is not designed eliminate fatigue, such as that experienced by the flight crew. Rather, the FRMS sits within a broader safety management system, which seeks to mitigate the effects of fatigue on performance. In this instance, selection of an instrument approach would have been an example of a mitigation to the fatigue of the crew, rather than conducting the visual approach via SHEED.

The types of errors made by the crew, the slip and then the non-detection of the incorrect waypoint RX34 altitude constraint, are broadly consistent with the effects of fatigue. However as discussed above, there are other possible influences on the development and non-detection of the error and, as such, it is difficult to conclude that fatigue actually contributed to the error and lack of detection on this occasion.

18. For example, ATSB Research and Analysis Report, AR-2009-052, Take-off performance calculation and entry errors: A global perspective reviews a series of occurrences where incorrect take-off weights were inputted into the FMS.
19. For example, ATSB investigation AO-2009-012, Tailstrike and runway overrun involving Airbus A340-541, A6-ERG, Melbourne Airport, Victoria, 20 March 2009. This accident involved the inadvertent entry in the electronic flight bag take-off performance function of a take-off weight that was 100 t lower than the actual aircraft weight. This resulted in reduced thrust and incorrect take-off speeds, leading to an early rotation, tailstrike and runway overrun causing damage to the aircraft fuselage and airport infrastructure.

From the evidence available, the following findings are made with respect to the descent below the approach path involving the Boeing 777-3ZGER VH-VPF near Melbourne Airport, Victoria on 15 August 2013. These findings should not be read as apportioning blame or liability to any particular organisation or individual.

Safety issues, or system problems, are highlighted in bold to emphasise their importance. A safety issue is an event or condition that increases safety risk and (a) can reasonably be regarded as having the potential to adversely affect the safety of future operations, and (b) is a characteristic of an organisation or a system, rather than a characteristic of a specific individual, or characteristic of an operating environment at a specific point in time.

Contributing factors

• When programming the approach into the flight management computer, the captain inadvertently entered the runway threshold crossing altitude into the runway extension waypoint, resulting in the flight management system calculating a vertical flight path that was below the intended approach path and a consequential high descent rate after passing the SHEED waypoint.
• When checking the flight management system, the first officer did not detect that the runway threshold crossing altitude had been entered into the runway extension waypoint, missing the opportunity to prevent the unintended approach path and resulting high descent rate after passing the SHEED waypoint.
• After passing the SHEED waypoint, the captain's attention became focused on the high rate of descent instead of monitoring external flight path cues as part of the visual approach, causing the first officer to shift their attention to the external cues and leading to a delayed recognition and response to the aircraft's position below the intended approach path.

Other factors that increased risk

• The flight crew were probably experiencing a level of fatigue known to have a demonstrated effect on performance.
• The presentation of the runway 34 visual approach procedure in the operator's Route and Airport Information Manual increased the potential for the runway threshold crossing altitude to be entered into the runway extension waypoint. [Safety issue]

The safety issues identified during this investigation are listed in the Findings and Safety issues and actions sections of this report. The Australian Transport Safety Bureau (ATSB) expects that all safety issues identified by the investigation should be addressed by the relevant organisation(s). In addressing those issues, the ATSB prefers to encourage relevant organisation(s) to proactively initiate safety action, rather than to issue formal safety recommendations or safety advisory notices.

All of the directly involved parties were provided with a draft report and invited to provide submissions. As part of that process, each organisation was asked to communicate what safety actions, if any, they had carried out or were planning to carry out in relation to each safety issue relevant to their organisation.

Guidance material

The presentation of the runway 34 visual approach in the operator's Route and Airport Information Manual increased the risk of the runway threshold crossing altitude being entered into the runway extension waypoint.

Safety issue: AO-2013-130-SI-01

Sources of information

The sources of information during the investigation included:

• Virgin Australia International Airlines (Virgin)
• the primary flight crew
• the Bureau of Meteorology
• the Civil Aviation Safety Authority (CASA).

References

Battelle Memorial Institute 1998, An Overview of the scientific literature concerning fatigue, sleep, and the circadian cycle, Report prepared for the Office of the Chief Scientific and Technical Advisor for Human Factors, US Federal Aviation Administration.

International Civil Aviation Organization 2011, Fatigue risk management systems (FRMS): Implementation guide for operators, 1st edition.

Performance-based operations Aviation Rulemaking Committee/Commercial Aviation Safety Team Flight Deck Automation Working Group 2013, Operational use of flight path management systems. Available from www.faa.gov.

Reason, J 1990, Human Error, Cambridge University Press, Cambridge, United Kingdom.

Thomas, MJW & Ferguson, SA 2010, ‘Prior sleep, prior wake, and crew performance during normal flight operations’, Aviation, Space, and Environmental Medicine, vol. 81, pp. 665–670.

Thomas, MJW, Petrilli, RM & Dawson, D 2004, ‘An exploratory study of error detection processes during normal line operations’, Proceedings of the 26th conference of the European Association for Aviation Psychology, Lisbon, Portugal.

Submissions

Under Part 4, Division 2 (Investigation Reports), Section 26 of the Transport Safety Investigation Act 2003 (the Act), the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. Section 26 (1) (a) of the Act allows a person receiving a draft report to make submissions to the ATSB about the draft report.

A draft of this report was provided to the primary flight crew, Virgin, Boeing and CASA.

Submissions were received from the primary flight crew, Boeing and Virgin. The submissions were reviewed and where considered appropriate, the text of the report was amended accordingly.