{"id":131633,"date":"2026-02-02T09:09:00","date_gmt":"2026-02-02T03:39:00","guid":{"rendered":"https:\/\/aviationa2z.com\/?p=131633"},"modified":"2026-02-02T04:27:51","modified_gmt":"2026-02-01T22:57:51","slug":"jetstar-a321-returns-to-nadi-after-engine-problem","status":"publish","type":"post","link":"https:\/\/aviationa2z.com\/index.php\/2026\/02\/02\/jetstar-a321-returns-to-nadi-after-engine-problem\/","title":{"rendered":"Jetstar A321 Returns to Nadi After Engine Problem, Flight Cancelled"},"content":{"rendered":"\n

SYDNEY-<\/strong> Jetstar Airways (JQ)<\/a> safely returned an Airbus A321neo to Nadi after the crew detected a low oil quantity indication mid-flight, leading to a precautionary diversion on January 30, 2026.<\/p>\n\n\n\n

The flight, operating from Nadi (NAN) to Sydney (SYD), landed safely after the crew managed the situation and cancelled the onward journey.<\/p>\n\n\n\n

\"Jetstar
Photo: Milchul Hope | Wikimedia Commons\nhttps:\/\/commons.wikimedia.org\/wiki\/File:Jetstar_Airways_VH-VWQ_Airbus_A321-231_Melbourne_International_Airport_(MEL_YMML)_(50791311181).jpg<\/figcaption><\/figure>\n\n\n\n

Jetstar A321 Diverts After Engine Indication<\/h2>\n\n\n\n

Jetstar flight JQ120<\/strong> departed Nadi for Sydney<\/a> and climbed to flight level 340. While cruising about 250 nautical miles southwest of Nadi, the crew initiated a descent to flight level 320.<\/p>\n\n\n\n

Around 15 minutes later, pilots requested a return to Nadi after receiving a low oil quantity indication on the left LEAP engine. The crew maintained flight level 320 before descending further to flight level 280 as part of the return plan.<\/p>\n\n\n\n

The aircraft landed safely on runway 02 at Nadi International Airport approximately two and a half hours after departure. No injuries or further operational issues were reported during landing, the Aviation Herald<\/a> reported.<\/p>\n\n\n\n

Following the safe return, the aircraft remained on the ground in Nadi for several hours for technical checks. The scheduled flight to Sydney was subsequently cancelled.<\/p>\n\n\n\n

Airlines typically conduct detailed inspections when engine system alerts occur to ensure safe continuation of operations. Such precautionary returns are standard safety procedures in commercial aviation.<\/p>\n\n\n\n

Modern aircraft systems continuously monitor engine performance, including oil quantity and pressure. When abnormal indications appear, crews follow established safety protocols that prioritize precautionary action.<\/p>\n\n\n\n

Returning to the departure airport allows maintenance teams to inspect the aircraft while ensuring passenger and crew safety. The safe landing demonstrated effective crew response and adherence to operational procedures.<\/p>\n\n\n\n

\"Jetstar
Photo: By Bidgee, CC BY-SA 3.0 au, https:\/\/commons.wikimedia.org\/w\/index.php?curid=61167408<\/figcaption><\/figure>\n\n\n\n

Similar Incident<\/h2>\n\n\n\n

Qantas Flight QF1613 departed Geraldton at approximately 9:00 AM on January 10, 2025, bound for Perth. About 45 minutes into the flight, pilots detected strong vibrations in the aircraft\u2019s left engine.<\/p>\n\n\n\n

The flight crew immediately initiated safety protocols. The aircraft descended and maintained a lower altitude while preparations were made to return to Geraldton Airport. Passengers were instructed to remain seated with seatbelts secured as the crew managed the situation.<\/p>\n\n\n\n

The aircraft landed safely at Geraldton Airport around 10:30 AM. Airport authorities activated the Emergency Plan, with rescue and firefighting services positioned as a precaution during landing. No injuries were reported among passengers or crew.<\/p>\n\n\n\n

Aircraft Details and Operational Response<\/h4>\n\n\n\n

The flight operated using a QantasLink Fokker 100 aircraft registered VH-NHP. The aircraft, over three decades old, is powered by Rolls-Royce Tay 650 engines commonly used on regional jet operations.<\/p>\n\n\n\n

City of Greater Geraldton officials confirmed that engine concerns prompted the aircraft\u2019s return. Emergency services remained on standby until the aircraft safely reached the terminal.<\/p>\n\n\n\n

Qantas later described the issue as a minor technical problem and confirmed that pilots followed standard safety procedures throughout the incident.<\/p>\n\n\n\n

Passenger Experience During the Incident<\/h4>\n\n\n\n

Passengers onboard reported a calm cabin environment despite awareness of the situation. One traveler noted that while anxiety was present, crew communication helped maintain order.<\/p>\n\n\n\n

A frequent flyer onboard also highlighted ongoing concerns regarding flight delays on regional routes, stating that service disruptions occur regularly. However, he acknowledged that cabin crew handled the situation professionally.<\/p>\n\n\n\n

Qantas rebooked affected travelers onto later flights to Perth the same day. The airline issued an apology for the inconvenience caused and thanked customers for their cooperation.<\/p>\n\n\n\n

Stay tuned with us. Further, follow us on social media for the latest updates.<\/p>\n\n\n\n

Join us on\u00a0Telegram Group\u00a0<\/a>for the Latest Aviation Updates. Subsequently, follow us on\u00a0Google News<\/a><\/p>\n\n\n\n

\n
Air France Passengers Faced 48-Hour Delay After Engine Issue<\/a><\/blockquote>