Qantas Delays/Cancellations

There could be some congestion in the QFi PER lounge tomorrow morning as QF6 (B789 VH-ZNB, the 1050 hours 25 June FCO-PER-SYD) has just taken off at 1153, meaning likely PER at gate arrival at 0908 tomorrow, 38 late.
Arrived in Perth at 09:05 AWST, and a creditable on ground time of 93 minutes (compared to some recent QF9/QF10 times) saw it on its way to Sydney at 10:38. Arrival in Sydney expected to be 16:15 AEST, just 10 minutes late. With the 2+ hour delay to QF10, the lounge congestion was probably eased somewhat.
 
Presumably QF35/QF36 will revert to an A332 or A333, as there is no delay posted for these flights.
Re my above comment on Saturday about today's QF35/QF36 MEL-SIN-MEL rotation, due to the B789 VH-ZNC QF9 diversion and subsequent delays - I see QF35 is today being operated by A332 VH-EBQ with an 11 minute delay in departure, but a 58 minute delay in arrival at Singapore at 18:53 local.
Qantas Flight Status optimistically shows the return QF36 as still departing at 20:15 local, 82 minutes later.
 
Sunday's QF8 DFW-SYD (B789 VH-ZNA which arrived just 10 minutes tardy with QF22 from MEL) was 27 minutes late pushing back, and is expected into Sydney at 07:00 AEST on Tuesday, 45 minutes late.
 
Possibly or the aircraft that operates QF94 (ZNJ) could operate QF35/36, with the late inbound QF10 turning around to operate QF9. The regular inbound (on time) QF10 could then operate QF93.
With the issue of QF35/QF36 sorted, ZNJ has positioned to Sydney as QF6001, to provide partial coverage there while ZNH is absent. Otherwise, you're correct on the other two counts :
ZNC will turn around to operate QF9. albeit delayed 100 minutes for a 16:45 AEST Melbourne departure. That delay holding through to the Heathrow arrival at 06:45 BST on Tuesday morning. Subject to the impact of earlier crew delays, Tuesday's QF10 should leave on time.
Today's lesser delayed QF10 into Melbourne (ZNF), will then operate QF93 MEL-LAX with a projected 85 minute delay at 21:50. Again this delay is shown as holding though to the Los Angeles arrival at 19:10 PST on Monday.
 
It looks like the overnight delayed SYD-JNB B789 (amended to depart at 2200 on Monday 26 June) may be operated by QF28 ex SCL, suggested as arriving in Sydney at 1829 hours this evening, 29 late.

'The 9' (VH-ZNC) was airborne from MEL at 1659, in line with its amended 1645 hours pushback. PER arrival should be at 1845 hours, 90 late.
 
In more on 26 June 2023, QF1 (1510 hours ex SYD) took off at 1613 so expected SIN gate arrival becomes 2214 hours, 44 late for A388 VH-OQG.
 
Today's lesser delayed QF10 into Melbourne (ZNF), will then operate QF93 MEL-LAX with a projected 85 minute delay at 21:50. Again this delay is shown as holding though to the Los Angeles arrival at 19:10 PST on Monday.

ZNF arrived MEL on Monday 26 June at 2106 hours, 146 minutes late as QF10 from PER and previously LHR. There's no way it'll depart at 2150 for LAX as 'the 93'. 2245 hours is my guess.

QF103 (2040 hours SYD-HNL, A333 VH-QPG) departed at about 2207 hours, so will be quite late arriving on the major island.

B789 VH-ZNG on the shockingly delayed Sunday 1000 hours SYD-JNB QF63 departed at around 2210 on Monday 26 as QF63D.

A388 VH-OQB on 25 June as QF12 (2340 hours LAX-SYD) took off at 0203 hours so Tuesday 27 arrival should be about 0935 hours, 110 minutes behind schedule.
 
Last edited:
On Tuesday 27 June 2023, QF35, the 1200 'high noon' MEL-SIN is delayed by 180 minutes to depart right on mid afternoon at 1500 hours.

Because QF69 was tardy yesterday, QF70, the Monday 26 scheduled 1935 hours DEL-MEL that was in the sky mid evening at 2114 hours should arrive (with A332 VH-EBR) at around 1329 hours, 59 late early this afternoon.

B789 VH-ZNM on the very late QF4 from JFK arrived this morning in AKL at 0734 hours, 154 minutes late. This was a 10 minute improvement on the '164 minutes late' predicted in my post 15,140. Every minute counts. While it mayu pop up[ on the FR24 at any minute, by 0931 hours AKL time (0731 AEST), it didn't appear to have pushed back for the final sector to Sydney Town.

VH-ZNC on 'the 9' should arrive LHR today at 0542 hours, 37 minutes late.

ZNF on last night's QF10 arrival that (as noted above) formed QF93 (2025 hours MEL-LAX) was airborne at 2319, so arrival in Movie City should be at about 1927 hours, 102 minutes late on the same day.

Following its late departure from SYD last night, A333 VH-QPG on QF103 (the redeye) arrived HNL on Monday 26 June at 1132 hours, 67 minutes late, just a few minutes ago. There's no hope of the 1200 hours 'high noon' HNL to SYD arriving anything close to on time tonight in Sydney, so situation normal for this perennial late runner.

UPDATE: By 0740 AEST, QF4 became visible on the FR24 map in AKL, almost always a good sign.
 
Last edited:
QF4 (VH-ZNM, B789) took off from AKL on 27 June at 0955 so is expected to arrive at its SYD gate at 1058 hours, 138 minutes behind schedule.

It appears to be forming QF27, the 1235 hours lunchtime long flight to SCL. This isn't showing a delay, but it's doubtful it'll get away on time as probably 100 minutes is the best one could hope for in Sydney with a B789 international turnaround. Inevitably, it often takes longer for a myriad of reasons.
 
Last edited:
A333 VH-QPC on QF23 (0950 hours 27 June SYD-BKK) was not pointing skywards until 1114 hours, so at gate arrival is predicted for 1747 hours, 67 late, ensuring that te 1810 hours redeye back down to SYD (QF24) will be tardy off its blocks.
 
QF4 (VH-ZNM, B789) took off from AKL on 27 June at 0955 so is expected to arrive at its SYD gate at 1058 hours, 138 minutes behind schedule.

It appears to be forming QF27, the 1235 hours lunchtime long flight to SCL. This isn't showing a delay, but it's doubtful it'll get away on time as probably 100 minutes is the best one could hope for in Sydney with a B789 international turnaround. Inevitably, it often takes longer for a myriad of reasons.
ZNM made up 1 minute on its QF4 Sydney arrival, and after 114 minutes, was off with QF27 to Santiago just 16 minutes late. Arrival in Santiago is expected to be 27 minute late.

Meanwhile QF64 JNB-SYD (B789 VH-ZND) arrived in Sydney at 14:00 AEST, this afternoon 35 minutes late, having left Jo'burg 56 minutes late. However this mornings QF63 (B789 VH-ZNA), while just 4 minutes late pushing back, is expected to be 61 minutes late into Jo'burg later today.
 
Read our AFF credit card guides and start earning more points now.

AFF Supporters can remove this and all advertisements

QF11 has been delayed till 1630

And worse, QF35, the 1200 'high noon' MEL-SIN A332 that was to depart at 1500 mid afternoon is now apparently further delayed to 1800 hours at the start of the 27 June 2023's Melbourne winter's (chilly) evening. If it's forming QF36 ex SIN, that will also be further delayed.

Earlier today, QF63, the 0940 hours SYD-JNB took off at 1001 hours with class leader B789 VH-ZNA. Arrival should be at 1609 hours, 34 late. With the eastbound probably able to make up time due to favourable winds, with luck it might not be late into SYD tomorrow afternoon.

A333 VH-QPG is coming into SYD tonight at 2023 hours, 103 minutes late as QF104 from HNL. 'The 25' from SYD up to HND overnight isn't showing as delayed from its 2020 hours timetabled pushback, so QF104's aircraft may not be forming QF25 tonight.

A388 VH-OQG was earlier suggested as arriving LHR today as QF1 less than half an hour late but this ended up being an 0711 hours gate arrival, 36 late.
 
Last edited:
Continuing with Tuesday 27, QF11 took off at 1718 hours so A388 VH-OQB should arrive (ex SYD) in LAX at approximately (same day) 1310 hours, 365 minutes behind schedule.
 
QF35 eventually departed after an aircraft change, catering issues, a DYKWIA meltdown in the F Lounge and a minor aircon issue just prior to the eventual 1934 gate departure and 2003 takeoff.

Approx 70pax booked to connect to the QF1 in SIN, typically a 5hr connection, now with an expected 0224 arrival into SIN for a 2330 departure of QF1 so either QF1 waits (seems unlikely) or accomodate pax overnight and travel tomorrow (pending loadings). Using SQ or other carriers (even connecting in SIN) didn’t seem to be an option, nor was putting pax into the later departing but earlier London arriving EK407 with connection in DXB.

Messy.
 
In more on Tuesday 27 June, the hugely delayed QF63D arrived JNB at 0453 hours, instead of its usual 1610 hours on Sunday 25, so an incredible 2198 minutes (i.e. more than 36 hours) late. B789 VH-ZNG then had a generous layover in JNB due to the SYD curfew limitations, so it departed today at 1035 hours as QF64D with SYD arrival estimated as 0631 hours tomorrow morning, Wednesday 28 instead of the timetabled 1325 hours on Monday 26, so 2526 minutes behind schedule.
 
QF35 eventually departed after an aircraft change, catering issues, a DYKWIA meltdown in the F Lounge and a minor aircon issue just prior to the eventual 1934 gate departure and 2003 takeoff.

Approx 70pax booked to connect to the QF1 in SIN, typically a 5hr connection, now with an expected 0224 arrival into SIN for a 2330 departure of QF1 so either QF1 waits (seems unlikely) or accomodate pax overnight and travel tomorrow (pending loadings). Using SQ or other carriers (even connecting in SIN) didn’t seem to be an option, nor was putting pax into the later departing but earlier London arriving EK407 with connection in DXB.

Messy.

Great information, so have a 'happy trip'.

Even if QFi wanted to use a rival (which we can't presume), SQ may have been full. We know its loadings ex Australia are excellent, and heaps connect in SIN to/from UK/Europe. That it's Victorian school holidays from this week (and NSW from next week: how many parents ensure their kids wag school a few days prior to have a longer break?) may not help.

'Pending loadings' is a sagacious comment.

A388 VH-OQK is on 'the 1' tonight, and should be about 14 minutes late arriving at its allocated SIN gate. I'd guess the chances of it being held are low, although 70 passengers is many: it's not just two or three. Given luggage transfers, security and the like, it might end up being held until c.0330, so then four hours or so late into LHR.

Presumably QFi has to weigh up that extra cost (and annoyance to through passengers ex Sydney, as well as the flight and cabin crew probably becoming more tired) against having to deal with an angry crowd of up to 70, some of whom might not be immediately able to be found a spare seat for, or heaven forbid have to be downgraded in some instances to a lower class of travel. Quelle horreur!

Without identifying an individual, can you please give us a bit more detail of the 'meltdown'? Important businessman/woman, or (heaven forbid) politician/public servant?
 
Great information, so have a 'happy trip'.

Without identifying an individual, can you please give us a bit more detail of the 'meltdown'? Important businessman/woman, or (heaven forbid) politician/public servant?
Not me travelling, but have had reported to me by a traveller who is calm but obviously not happy!

For the description of the meltdown behaviour, I’ll go with “couple hassling F Lounge staff” to the point of “geez they may get denied boarding” level of bad interaction, raised voices etc.
 
QF35 eventually departed after an aircraft change, catering issues, a DYKWIA meltdown in the F Lounge and a minor aircon issue just prior to the eventual 1934 gate departure and 2003 takeoff.

Approx 70pax booked to connect to the QF1 in SIN, typically a 5hr connection, now with an expected 0224 arrival into SIN for a 2330 departure of QF1 so either QF1 waits (seems unlikely) or accomodate pax overnight and travel tomorrow (pending loadings). Using SQ or other carriers (even connecting in SIN) didn’t seem to be an option, nor was putting pax into the later departing but earlier London arriving EK407 with connection in DXB.

Messy.

not ideal but JQ would have at least connected pax onto QF1 in time
 

Become an AFF member!

Join Australian Frequent Flyer (AFF) for free and unlock insider tips, exclusive deals, and global meetups with 65,000+ frequent flyers.

AFF members can also access our Frequent Flyer Training courses, and upgrade to Fast-track your way to expert traveller status and unlock even more exclusive discounts!

AFF forum abbreviations

Wondering about Y, J or any of the other abbreviations used on our forum?

Check out our guide to common AFF acronyms & abbreviations.

Staff online

  • NM
    Enthusiast
Back
Top