Qantas Delays/Cancellations

[Melburnian1]

With the caveat that the public information can be slow to update, the QF site is showing 'on time' pushback is/was expected, so that implies a minor delay.

QF35 on Monday 25 departed MEL 24 late at 1234 hours with arrival at gate in SIN estimated as 1741, 36 behind.

On Sunday 24 November, QF63 (B744 VH-OEE) arrived JNB just three minute slate at 1638 hours, but its return overnight as QF64 has been badly delayed, as it was off blocks 190 minutes late at 2200 hours. Monday 25 SYD arrival should be 1827 hours, 172 minutes behind schedule. At this stage this B744 is forming 'the 25', the 2135 hours SYD - HND, so unless maintenance is required that takes a while, the latter should still depart on time.

QF28 on Sunday (1335 hours ex SCL) departed 26 late at 1401 for a Monday 25 estimated SYD arrival of 1825, 35 down.

 

[Fergo747]

Yesterday’s QF2 will depart tonight at 2015.

Something else will have to be cancelled but not sure what at this stage.

It would appear the 7 has been cancelled

 

[Silvia]

QF153 MEL-AKL was cancelled today, so the return leg will consequently be cancelled.
Some storms looming around Sydney area so keep an eye

 

[thepumpkin]

Does anyone know why QF7 was cancelled today NOV 25 ?

 

[jpp42]

Does anyone know why QF7 was cancelled today NOV 25 ?

It was mentioned earlier in this thread, but it looks like the inbound aircraft was forming SQ2 which was cancelled at Singapore due to a technical issue. As there are no spare A380's right now with 2 being refurbished and 1 other out of service, and the B747 or A333 cannot really do this route, there is no alternative but to cancel. (The B789 can also do this route from a range perspective, but I haven't actually heard of Qantas doing this - and it has way fewer seats plus probably not really any spare aircraft either.)

 

[thepumpkin]

Thank you for finding out the likely sequence of events.

 

[jb747]

It was mentioned earlier in this thread, but it looks like the inbound aircraft was forming SQ2 which was cancelled at Singapore due to a technical issue. As there are no spare A380's right now with 2 being refurbished and 1 other out of service, and the B747 or A333 cannot really do this route, there is no alternative but to cancel. (The B789 can also do this route from a range perspective, but I haven't actually heard of Qantas doing this - and it has way fewer seats plus probably not really any spare aircraft either.)

Inserting a different type, to a destination that they don't normally fly to, is never straightforward. You'd need a replacement crew to fly the return journey. Whilst there are 787 crews in LAX, removing one would then be likely to affect the flight out of LA. Doable, but not easily.

 

[Melburnian1]

In more for 25 November, B738 VH-VXH on QF703 (scheduled 1300 hours CNS - MEL in the sky 40 minutes later) is arriving at its allocated gate at 1756 hours, 31 minutes tardy.

QF445 (VH-VXN, the 1530 hours SYD down to MEL) was not airborne until 1709, so arrival is suggested at 1830, 85 late. VH-VXG on QF447, what should be the following 1600 hours ex SYD flight got out ahead, taking off at 1702, so its at gate time will be 1826 hours, 51 late, flicking over by four minutes (later) as I watched.

The 1545 hours northbound MEL - SYD, QF470 (B738 VH-VYH) took off at 1630. Predicted arrival is 72 late at 1822 hours, as the plane had a lengthy hold - three circuits - north of Goulburn.

QF468, the 1615 hours ex MEL isn't a huge amount better. This flight (with VH-VZR) was only about 10 - 15 late taaking off at 1640, but at gate arrival looks to be 1832 hours, 52 behind. At 1807 it had just entered its holding pattern near Marulan (not far from Goulburn: both are on the main Sydney - Melbourne rail line.)

The BNE - SYD QF541 is in the hands of VH-VZL with a 46 late, 1826 early evening at gate arrival on the cards despite taking off at 1525, only 20 minutes after scheduled pushback and hence at most, 10 minute slate at that point.

QF455 (1730 hours SYd down to MEL) was airborne at 1844 after departing at 1754, so an extermely long period for the take off roll to occur. Arrival should be 2000, 55 minutes late, or beyond.

 

[Silvia]

In further, QF1 SYD-SIN (A388 VH-OQE) was airborne at 18 33, as such arrival is predicted at 23 24, 84 min behind schedule.

QF28 SCL-SYD (B747 VH-OEJ) is diverting to MEL
QF4 HNL-SYD (A333 VH-QPG) is diverting to CBR

 

[Melburnian1]

It is quite unusual for the B744 on QF28 from SCL to SYD to divert but with teh Sydney storms, that is what is occurring on Monday 25 November. The flight is timetabled to reach SYD at 1715 but after departing SCL yesterday 26 late at 1401, it has diverted to MEL where arrival was predicted as 1817. However at 1850, B744 VH-OEJ had not long entered a hold near Mt Buller, so arrival may be about 1925 if the Captain continues on to MEL. QF's computer claims the aircraft will depart MEL at 2000 hours, which is extremely unlikely, arriving SYD at 2130, 220 minute stardy. Again, this seems fantasy - unless the B744 instead diverts to CBR.

UPDATE: As at 1905, QF28 was still in a holding pattern.

The crew must surely be overtime if one includes a realistic stay in MEL of say 50 minutes (allowing time for the famous 'splash and dash' term trademarked by AFFer Quickstatus) and the subsequent run up to SYD. Unfortunately this is highly likely to mean passengers and crew overnighting in Melbourne, but time will tell.

Hoteliers must love this.

 

[Silvia]

QF1586 HBA-SYD (B712 VH-NXE) also diverted to CBR.
QF756 ADL-SYD (B738 VH-VYF) has a suggested arrival at 19 09, 74 late.

QF545 BNE-SYD 16 05 hours was cancelled
QF458 MEL-SYD 18 00 hours also cancelled
QF580 PER-SYD 14 55 hours had a similar luck

 

[Melburnian1]

QF819 from CBR down to MEL on Monday 25 November has B738 VH-VYJ and is the 1710 hours CBR - MEL airborne at 1816, with arrival suggested at 1933, 73 late after the standard hold above Mt Buller.

 

[milehighclub]

By my math, the QF28 must depart MEL by about 2030.

 

[Melburnian1]

The diverted QF28 (SCL to MEL rather than the usual SYD) shoudl be at its gate (or apron) in MEL at about 1936. B744 VH-OEJ.

 

[Melburnian1]

By my math, the QF28 must depart MEL by about 2030.

You'd know, but by my maths (using the Australian term!), I agree, because the flight crew probably signed on at about 0235 AEDT this morning in SCL, and reaching SYD by 2200 allows IIRC sign off at 2230, which would be 20 hours - that is, the normal 18 hours plus the 'by agreement' extension of crew duty hours to 20.

Do they "pull the pin" (i.e. terminate in MEL, and spend overnight at an hotel in Greater Melbourne) if it looks like being a few minutes over 20 hours, or do they "have a go" if regulators will permit that sort of approach to the last few minutes? I assume this is up to the Captain to determine and not for management in what one of our aviators amusingly referred to as 'where they (operations centre) play a video game'.

With so many other flights disrupted, airspace along the MEL - SYD track (and on approach) would have to be busy late tonight. That slows flights down and mitigates against any improvement in timings.

 

[Silvia]

QF764 ADL-SYD (B738 VH-VZJ) is diverting back to Adelaide.
Something tells me that this summer season will be full of these type of days.

 

[Melburnian1]

You'd know, but by my maths (using the Australian term!), I agree, because the flight crew probably signed on at about 0235 AEDT this morning in SCL, and reaching SYD by 2200 allows IIRC sign off at 2230, which would be 20 hours - that is, the normal 18 hours plus the 'by agreement' extension of crew duty hours to 20.

Do they "pull the pin" (i.e. terminate in MEL, and spend overnight at an hotel in Greater Melbourne) if it looks like being a few minutes over 20 hours, or do they "have a go" if regulators will permit that sort of approach to the last few minutes? I assume this is up to the Captain to determine and not for management in what one of our aviators amusingly referred to as 'where they (operations centre) play a video game'.

With so many other flights disrupted, airspace along the MEL - SYD track (and on approach) would have to be busy late tonight. That slows flights down and mitigates against any improvement in timings.

Well, here's the answer!

QF28 is departing MEL (after overnighting) at 0930 hours on Tuesday 26 November for projected SYD arrival at 1100 hours, 1030 minutes late.

Great photo opportunity for anyone wanting to photograph a QFi passenger B744 in MEL tomorrow morning.

Meanwhile another B744, QF73 (1755 hours Monday 25 SYD - SFO) is expected to depart at 2115 hours, arriving same day at 1520 mid afternoon, 175 minutes behind schedule.

QF3, the 1920 hours SYD to HNL is also to be tardy with expectations of a 2205 hours departure late this evening and consequent same day 1105 (170 minutes late) arrival. This will badly delay QF4.

 

[Melburnian1]

As I have a daughter on QF50 SFO - MEL this evening (24 Nov local) was checking progress and I note it will be 2 - 2.5 hrs delayed.
The inbound QF49 (VH-ZNH) departed MEL 0226, compared to scheduled time of 2235.

QF49 on Sunday 24 November pushed back in MEL at 0215 hours (Monday 25), 220 minutes late with SFO arrival same day 2102 hours, 197 minutes behind schedule. The returning QF50 then pushed back at 2245, 150 late with likely Tuesday 26 arrival in MEL at 0832 hours, 107 minutes tardy.

 

[pjm99au]

QF548 SYD BNE gets the trifecta. Late arriving aircraft + lightning delays on the tarmac + one pax with luggage not wanting to fly anymore = 90 minute delay.

I’ve also achieved a new personal best. This makes my 5th consecutive flight each with a delay of over 1.5hrs

 

[Melburnian1]

QF548 SYD BNE gets the trifecta. Late arriving aircraft + lightning delays on the tarmac + one pax with luggage not wanting to fly anymore = 90 minute delay.

I’ve also achieved a new personal best. This makes my 5th consecutive flight each with a delay of over 1.5hrs

I wonder how many cases a baggage handler had to rearrange to get to the said suitcase? Strikes me as a really difficult job on aircraft where luggage (and parcels) are manually loaded and unloaded. There's no way of knowing exactly where the item is AFAIK.