Summary
- Runway resurfacing works at Melbourne Airport temporarily shortened the runway, but flight crews didn’t factor-in the shorter length during takeoff calculations.
- Each Malaysia Airlines and Bamboo Airways flights overran the runway during takeoff, causing jet blast and damage to lights.
- The crew of the Malaysia Airlines flight missed the NOTAM details in regards to the shortened runway, while the crew of the Bamboo Airways flight didn’t access the updated ATIS audio.
The Australian Transport Safety Bureau (ATSB) has released preliminary reports into the 2 September 2023 incidents involving Malaysia Airlines and Bamboo Airways flights overrunning the runway during takeoff from Melbourne Airport (MEL). The incidents happened inside days, prompting the bureau to open an investigation.
Each flights were capable of proceed to their respective destinations without further incident. In its report, the ATSB determined that the flight crews of each aircraft that their departure runway was shorter than normal.
Details on the incidents
In line with The Aviation Herald, the Malaysian Airlines incident occurred on September seventh, 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 past a displaced runway end. This resulted in jet blast disrupting people and objects situated beyond the runway.
Photo: Melbourne Airport
The runway, undergoing refurbishment, had been temporarily reduced in length on the northern end by nearly 5,200 feet (1,585 meters), making it significantly shorter for widebody operations. Nearly two weeks later, a Bamboo Airways Boeing 787-9 Dreamliner also became victim to the shortened runway. The aircraft, registered as VN-A819, operated as QH84 destined for Noi Bai International Airport (HAN), Vietnam. Much like MH128, the plane rotated past the tip of Runway 34 and reportedly damaged lights on the runway because of the jet blast.
Reduced thrust on a shortened runway
Because of this of the runway troubles, airport officials ceased the work to refurbish the runway. On Friday, December 1st, the ATSB recalled each incidents in its preliminary report, based on The Aviation Herald.
“Runway 34, which was normally 3,657 m long [11,998 feet], had been temporarily shortened by 1,568 m [5,144 feet] from the northern end, because of runway resurfacing works in progress (WIP). The flight crew of each aircraft didn’t discover that the shortened runway was in place and used the complete length of runway 34 for his or her take-off performance calculations. Because of this, the reduced-thrust engine settings utilized by each flight crews prolonged the take-off runs beyond the temporary runway end lights right into a 450-metre buffer before the works limit line. The jet blast from each aircraft impacted runway unserviceability lights, works lights and marker cones. Personnel were energetic within the works area on the time of each occurrences, nevertheless none were physically injured in consequence. There was no damage to either aircraft, or injuries to passengers, and each continued with their planned flights.”
How the crews didn’t “discover” the runway’s length
In line with the report, one in every of the NOTAMs (Notice to Air Missions) within the briefing package on the Malaysia Airlines A330 indicated that the runway’s length was reduced, however the crew during preparations for the flight. The automated terminal information service (ATIS) audio also alerted the crew of the shortened runway. The pilots recalled listening to the audio and writing down the data, however the investigation found that no notes were written.
the ATSB explained.
Photo: Bamboo Airways
On the Bamboo Airways flight, the captain recalled that the NOTAMs identifying the runway’s updated length were reviewed and identified. Moreover, the ATIS broadcast also notified the crew of the change. Nonetheless, an APU fault caused power to be disconnected to the aircraft halfway through flight planning, leading to a delay of around an hour. When power was restored, the newest ATIS audio, which modified from Oscar to Papa, indicated the runway’s length and distance, however the crew reportedly didn’t access the latter version.
the ATSB said in its report.
The 787-9 reportedly rotated just past taxiway E on the runway. Witness reports and photographs led Melbourne airport officials to estimate that the aircraft had only lifted to as high as 16 feet over the tip of the runway. The aircraft didn’t sustain any damage.