A 737 entered a closed section of runway during its take-off from Brisbane Airport after its flight crew misinterpreted or missed dispatcher notes, a NOTAM and ATIS information detailing the shortened runway length available due to maintenance works.
On the morning of 30 November 2022, the Virgin Australia Boeing 737-800 commenced its take-off roll from Brisbane’s runway 19L for a flight to Melbourne, with 169 passengers and 8 crew on board. The flight crew comprised a training captain and a first officer undertaking ‘line flying under supervision’ as part of the first officer’s conversion onto the 737 aircraft.
The take-off thrust and speeds set by the flight crew were based on the full runway length being available. However, unrecognised by the crew, the take-off distance available for runway 19L was reduced at the upwind (01R threshold) end by 871 m due to runway works.
During the take-off roll, the aircraft briefly entered, and became airborne in, the closed section of runway. The aircraft completed the departure and continued on to Melbourne without further incident.
“The displaced threshold was detailed in dispatcher notes and in a NOTAM – notice to airmen advisory – included in pre-flight paperwork given to the crew prior to their previous flight from Melbourne to Brisbane, as well as in the paperwork for the Brisbane departure,” ATSB Director Transport Safety Stuart MacLeod explained.
“Further, the ATIS broadcast of recorded aeronautical information for Brisbane Airport at the time of the departure also alerted flight crews to the displaced threshold and reduced take-off distance at the time.
“However, during the pre-flight for the flight from Melbourne to Brisbane, the captain misinterpreted the dispatcher notes to mean there were no performance requirements for operations on runway 19L, then on reviewing the relevant NOTAMs headline, incorrectly dismissed the Brisbane NOTAM detailing the displaced runway threshold as not being relevant to their flight.”
An ATSB investigation report notes the crew’s belief that there were no performance requirements for runway 19L was reinforced by the absence of any visible runway works or other indications of restrictions during their landing on the runway after their flight from Melbourne.
“This, combined with time pressures and distractions from prioritising training needs, contributed to the flight crew then inputting the incorrect runway data during pre-flight calculations prior to the departure from Brisbane.”
This resulted in a departure with insufficient runway available due to the aircraft being overweight for that reduced runway length.
“This incident and investigation underscore the importance of flight crews considering possible variations to take-off and/or landing dimensions when determining runway performance data,” Mr Macleod said.
“This operator’s procedures did account for such changes through notification of performance requirements within their NOTAM system, however, due to a combination of distraction and misinterpretation, they were not identified.”
Since the occurrence, Virgin Australia has implemented a number of safety management, procedural and information-based changes designed to improve flight crew awareness.
“When presented with a number of NOTAMs, dismissing them based on the headline alone increases the risk of missing safety relevant information,” Mr Macleod concluded.
“As an additional defence, flight crews should ensure that the data input into performance data calculations is in conformance with other relevant information, such as the ATIS.”
Read the report: Runway excursion involving Boeing 737-8FE, VH-YFH, at Brisbane Airport, Queensland, on 30 November 2022