Melbourne, Australia: A Virgin Australia Boeing 737-800 operating a scheduled domestic service from Melbourne to Perth was forced to return to Melbourne Airport on June 15 after the flight crew reported an engine-related issue shortly after departure.
The aircraft, operating as Flight VA697, departed Melbourne Airport at approximately 6:05 p.m. local time for the four-hour service to Perth. According to flight tracking data, the aircraft remained airborne for about 44 to 45 minutes, conducting a series of holding patterns and circling manoeuvres before returning safely to Melbourne Tullamarine Airport.
Virgin Australia confirmed that the flight crew elected to return to Melbourne after identifying an engine issue during the climb phase of the flight. The airline did not disclose the specific nature of the malfunction.
The aircraft involved was identified as a Boeing 737-800, registration VH-VUR. Aviation Safety Network data indicates the aircraft experienced the issue while climbing out of Melbourne, prompting the crew to discontinue the flight and return to the departure airport for a precautionary landing.
Flight tracking information showed the aircraft making a wide circuit over the Melbourne area before lining up for landing. The aircraft touched down safely at Melbourne Airport at approximately 6:50 p.m.
Emergency response procedures were activated as a precaution. Firefighters, airport rescue crews and paramedics were positioned at the airport during the aircraft’s arrival. However, emergency personnel were not required to intervene following the landing.
Melbourne Airport confirmed that all passengers and crew disembarked safely from the aircraft after it returned to the terminal. No injuries were reported.
Following the landing, the affected runway underwent inspections in accordance with standard emergency response procedures before normal operations resumed.
Several social media posts circulated shortly after the incident claiming that flames were visible from one of the aircraft’s engines. However, reports citing airport and airline sources indicated there was no confirmed evidence of an engine fire following the aircraft’s return. Neither Virgin Australia nor airport authorities have reported an engine fire, and the airline has continued to describe the occurrence as an “engine issue.”
Virgin Australia Chief Operations Officer Chris Snook apologised to affected passengers for the disruption. “We apologise to guests for the disruption and thank them for their understanding,” Snook said.
Passengers were subsequently accommodated on an alternative Perth-bound service later the same evening. Reports indicate the replacement flight departed Melbourne at approximately 9:45 p.m. and arrived in Perth at around 11:42 p.m. local time.
The aircraft has been withdrawn from service pending engineering inspections, evaluation and testing to determine the cause of the reported engine malfunction before it is cleared to fly again.
.jpg){kind=link}