summary
- Melbourne Airport’s runway resurfacing work temporarily shortened the runway, but the flight crew did not take this shortened length into account when calculating the takeoff.
- Both Malaysia Airlines and Bamboo Airways flights overran the runway during takeoff, causing damage to jets and lights.
- The crew on the Malaysia Airlines flight missed the NOTAM details about the runway shortening, while the crew on the Bamboo Airways flight did not have access to the latest ATIS audio.
The Australian Transport Safety Bureau (ATSB) has released a preliminary report into two incidents in September 2023 in which Malaysia Airlines and Bamboo Airways aircraft overran the runway during takeoff from Melbourne Airport (MEL). . The incidents occurred within days of each other and the department launched an investigation.
Both flights were able to continue to their respective destinations without any problems. The ATSB said in its report that the flight crews of both aircraft: “I couldn’t identify it.” The departure runway was reportedly shorter than usual.
Details of the incident
according to aviation herald, The Malaysia Airlines incident occurred on September 7, 2023. An Airbus A330-300 registered as 9M-MTL operated as MH128 from MEL to Kuala Lumpur International Airport (KUL). During departure on Runway 34, the aircraft rotated and passed through a runway edge shift. As a result, the jet spray disrupted people and objects outside the runway.
Photo: Melbourne Airport
During the renovation, the length of the runway at its north end was temporarily shortened by nearly 5,200 feet (1,585 meters), making it significantly shorter to accommodate wide-body aircraft operations. Almost two weeks later, Bamboo Airways’ Boeing 787-9 Dreamliner also fell victim to the runway shortening. The aircraft was registered as VN-A819 and operated as QH84 to Noi Bai International Airport (HAN), Vietnam. Similar to Flight MH128, the plane reportedly rolled over the edge of Runway 34 and jets damaged runway lighting.
Thrust reduction on shortened runways
As a result of the runway troubles, the airport authority suspended runway renovation work. According to reports, on Friday, December 1, the ATSB recalled both incidents in a preliminary report. aviation herald.
“Runway 34, which was normally 3,657 meters long.” [11,998 feet]which was temporarily shortened by 1,568 meters. [5,144 feet] From the north end due to ongoing runway resurfacing work (WIP). The flight crews of both aircraft were not aware that the runways had been shortened and used the full length of Runway 34 in their takeoff performance calculations. As a result, the reduced thrust engine settings used by both flight crews extended the takeoff roll beyond the provisional runway end lights to a 450 meter buffer before the working threshold. Jet jets from each aircraft impacted the runway out of service lights, work lights, and marker cones. Workers were active in the work area at the time of both incidents, but no one suffered physical injuries as a result. There was no damage to either aircraft, no passengers were injured, and both continued their scheduled flights. ”
How the crew did not “identify” the length of the runway
According to the report, one of the NOTAMs (Notifications to Aviation Missions) included in the Malaysia Airlines A330’s briefing package indicated that the runway length had been shortened, but the crew “I missed the details of NOTAM” Preparing for flight. The Automatic Terminal Information Service (ATIS) voice also alerted the crew to the shortened runway. The pilots recalled hearing the audio and writing down the information, but an investigation revealed that no notes had been written.
“After hearing about ATIS, neither crew member recalled being aware that the runway length had been shortened, and the take-off certificate prior to departure contained a note regarding the runway length. It wasn’t recorded.” ATSB explained.
Photo: Bamboo Airways
The captain of the Bamboo Airways flight recalled that a NOTAM specifying the updated length of the runway was reviewed and identified. Additionally, crew members were notified of the changes via ATIS broadcasts. However, due to an APU failure, the aircraft’s power was cut off midway through the flight plan, causing a delay of approximately one hour. Once power was restored, the updated ATIS voice, which changed from Oscar to Papa, indicated the length and distance of the runway, but the crew reportedly did not access the latter version.
“During the takeoff roll, the flight crew noticed that the runway end lights were much closer than normal. After takeoff was completed, the flight crew discussed the proximity of the runway end lights.” The ATSB stated in its report:
The 787-9 reportedly turned just past Taxiway E on the runway. Based on sighting reports and footage, Melbourne Airport authorities estimated that the aircraft had climbed only 16 feet from the end of the runway. There was no damage to the aircraft.
