Qantas Delays/Cancellations

[moa999]

I thought the IATA code for Dubai World/Al Maktoum was DWC not AWC.

One of the HFC members also ended up there on 3Dec. A good 50km away from DXB

 

[Melburnian1]

I thought the IATA code for Dubai World/Al Maktoum was DWC not AWC.

One of the HFC members also ended up there on 3Dec. A good 50km away from DXB

moa999, thanks - corrected. How this QF flight was able to land at DWC but not DXB is a good reminder as to how weather is localised. We might think that two locations 40 or 50 kilometres away from each other might have very similar weather - not necessarily so.

 

[jb747]

How this QF flight was able to land at DWC but not DXB is a good reminder as to how weather is localised. We might think that two locations 40 or 50 kilometres away from each other might have very similar weather - not necessarily so.

Actually it isn't an example of that at all.

SA	27/12/2016 23:00->	[SIZE=-1]METAR OMDW 272300Z 12003KT 0100 R30/0225N FG VV001 18/18 Q1017 TEMPO 0500=[/SIZE]
SA	28/12/2016 00:00->	[SIZE=-1]METAR OMDW 280000Z 13004KT 0100 R30/0325 FG VV001 17/17 Q1017 TEMPO 0500=[/SIZE]
SA	28/12/2016 01:00->	[SIZE=-1]METAR OMDW 280100Z 13004KT 0100 R30/0250N FG VV001 17/17 Q1017 TEMPO 0500=[/SIZE]
SA	28/12/2016 02:00->	[SIZE=-1]METAR OMDW 280200Z 11003KT 0100 R30/0325N FG VV001 17/17 Q1017 NOSIG=[/SIZE]
SA	28/12/2016 03:00->	[SIZE=-1]METAR OMDW 280300Z 18005KT 0100 R30/0325N FG VV001 16/16 Q1017 NOSIG=[/SIZE]
SA	28/12/2016 04:00->	[SIZE=-1]METAR OMDW 280400Z 18004KT 0200 R30/0225N FG VV001 16/16 Q1018 NOSIG=[/SIZE]
SA	28/12/2016 05:00->	[SIZE=-1]METAR OMDW 280500Z VRB01KT 0100 R30/0175N FG VV001 17/17 Q1019 BECMG 3000 BR=[/SIZE]
SP	28/12/2016 05:41->	SPECI OMDW 280541Z VRB02KT 0100 R30/0175N FG VV001 18/18 Q1019 BECMG 3000 BR=
SA	28/12/2016 06:00->	[SIZE=-1]METAR OMDW 280600Z VRB02KT 0200 R30/0200N FG VV001 18/18 Q1019 BECMG 3000 BR=[/SIZE]
SP	28/12/2016 06:12->	SPECI OMDW 280612Z 20003KT 180V240 0800 R30/0500D FG VV001 18/18 Q1019 BECMG 3000 BR=
SA	28/12/2016 07:00->	[SIZE=-1]METAR OMDW 280700Z 24003KT 190V280 0600 R30/0450D FG VV002 19/19 Q1019 BECMG 3000 BR=[/SIZE]
SA	28/12/2016 08:00->	[SIZE=-1]METAR OMDW 280800Z 31003KT 260V360 1500 0900E R30/1300U BCFG BKN002 19/19 Q1018 BECMG 3000 BR=[/SIZE]
SA	28/12/2016 09:00->	[SIZE=-1]METAR OMDW 280900Z 30003KT 260V340 3500 BR FEW010 20/20 Q1018 BECMG 8000 NSW=[/SIZE]

 

[Melburnian1]

The Wednesday 28 December QF11 arrived in JFK at 1641, 11 minutes late but the return working, QF12, did not depart until 1843, 43 minutes late. LAX arrival should be at 2155, an hour behind schedule, with Quickstatus' explanation above being a useful guide.

The 2230 hours LAX - SYD is showing as on time but this will not be possible if passengers connect from the B744 on the transcontinental QF12.

The Thursday 29 December 2016 QF422 (A333 VH-QPI) was airborne at 1058; it should arrive at about 1206 hours, 41 minutes delayed. This is one way to travel in the A333 business class on a very short domestic sector: this aircraft was on time arriving on QF30 ex HKG this morning, but could not manage to depart on time on this unconnected domestic sector.

A333 VH-QPA on the 0945 hours SYD - BKK 29 December QF23 was in the aky at 1142. Arrival should be at roughly 1635, an hour late. If that holds, it should be possible for QF24, the 1800 hours overnight from BKK to SYD to depart on time if all goes well during the turnaround.

 

[Melburnian1]

QF881, the 1140 OOL - MEL that took off at 1154 - on time - may have had a missed approach to MEL at about 1500 hours due to the storm currently sweeping through mid afternoon on Thursday 29 December 2016. ADL has had significant rain in the last two or three days: it's Melbourne's turn. B738 VH-XZE is the aircraft.

With the heavy rain and flash flooding in parts of Melbourne, it looks like MEL may have been closed for a while.

In an hour and 19 minutes between 1459 and 1618 hours, MEL (airport) had 42.6 millimetres of rain: tropical conditions like Jakarta or Manila!

QF437, the 1330 hours from SYD down to MEL (B738 VH-VYA) took off late at 1405 but is arriving at about 1618, 73 minutes late after being held in the usual location above Mt Buller, Victoria.

The 1400 hours SYD - ME:L, QF439 is hot on its heels with arrival expected at roughly 1621, 46 minutes tardy. B738 VH-VXM is the aircraft.

QF473, a 1415 hours SYD - MEL is also operating today: B738 VH-VZR was in the sky at 1437, not very late, but will not arrive until around 1637 which would be 47 minutes behind the scheduled 1550 hours arrival.

 

[Melburnian1]

Also delayed by the mid afternoon Thursday 29 December storm in MEL was QF442, the 1500 hours MEL - SYD (A332 VH-EBA) that became airborne at 1629. It is predicted to arrive at 1745 hours, 80 minutes behind schedule.

 

[Melburnian1]

Thanks to the second consecutive day of fog affecting DXB, QF9 (this time the Wednesday 28 December 2325 hours ex MEL) has been again diverted, but this time not to DWC but to AAN.

QF9 departed MEL last night at 2349, arriving on Thursday 29 December at AAN at 0729, 59 minutes after it was meant to be on blocks at DXB. It then departed this 'other' Middle Eastern airport at 0945, and is estimated to arrive in DXB at 1050 hours. QF has yet to provide an estimated departure time from DXB for the shorter leg onwards to LHR.

Meanwhile the Wednesday 28 December QF2 unexceptionally departed LHR 19 minutes late at 2104 hours and was able to land at DXB for an at gate arrival at 0921, 96 minutes late. It is estimated to depart the Middle East's major airport at 1105 (90 minutes behind time) for a Friday 30 December SYD suggested arrival at 0730, an hour late. One might expect DXB to be extremely busy due to handling many tens of delayed flights so it will be interesting to observe if this estimate for departing DXB reflects what occurs.

One reason why QF9 could not depart AAN a little earlier to more or less match the post-fog arrival time of 0921 of QF2 might be the congested airspace and runways, so an approximate 1050 hours arrival in DXB for QF9 might be the earliest that air traffic controllers could allocate.

Due to the earlier mid afternoon MEL storms (see above) QF443 (A332 VH-EBB, the 1500 hours SYD - MEL that took off at 1526) should arrive at about 1743, 68 minutes tardy.

The folowing QF445, the 1530 hours ex SYD, B738 VH-VZV) should arrive about 51 minutes late at 1756 while as at 1735 hours, the next southbound, QF447 (A332 VH-EBP) remained in a holding pattern above Mt Buller (Vic.) with an estimated arrival in MEL of 1824, 49 minutes late after taking off at 1635 as the 1600 hours SYD - MEL.

QF693, the 1645 hours latish afternoon from MEL across to ADL is estimated to depart at around 1830.

 

[jb747]

One reason why QF9 could not depart AAN a little earlier to more or less match the post-fog arrival time of 0921 of QF2 might be the congested airspace and runways, so an approximate 1050 hours arrival in DXB for QF9 might be the earliest that air traffic controllers could allocate.

Why would matching up the timing with an aircraft going in the other direction have any relevance?

 

[Melburnian1]

Why would matching up the timing with an aircraft going in the other direction have any relevance?

Because as I explained above, QF9 spent a significant amount of time at the alternate airport, well beyond when the fog must have sufficiently cleared at DXB - otherwise QF2 could not have landed at DXB at 0921 hours.

It was merely an illustration as to how delays 'compound' when there is fog (or sandstorms) and there is a build up of 'traffic' into and out of these major airports.

I didn't assert that the two flights were connected. I just used one an an example of an aircraft that was able to reach DXB well ahead of the second, previously diverted one that must have been held at the alternate airport until ATC in DXB could accommodate it.

 

[jb747]

You haven't really explained anything. The data is out there, you aren't seeing it.

What time did the QF 9 arrive at the holding fix. How long did it remain in the pattern? What time did it land?

When did QF 2 arrive at the fix. How long did it remain in the pattern. What time did it land?

I gave you the reference for past weather reports a few comments ago. What was the weather when QF 2 landed? When did the fog clear?

 

[Melburnian1]

Continuing with Thursday 29 December, QF452, the 1700 hours MEL - SYD took off at 1811 (B738 VH-VZT) with arrival predicted as 52 minutes late at 1917 this evening.

Delays into MEL may be reducing as QF453 southbound from SYD to MEL is expected to arrive at 1905 hours, half an hour late with B738 VH-VYE after this timetabled 1700 hours ex SYD was in the sky a few minutes late at 1726. Unless it is further delayed, it is not as bad as the mid afternoon flights down to MEL.

There has been much flash flooding in Melbourne suburbs but as noted above Tullamarine airport had one of the heavier deluges. So we've had ASP and AYQ this week, and the Adelaide suburbs also copping lots of rain.

QF690, the 1455 hours mid afternoon ADL - MEL was airborne at a much delayed 1827 hours. Arrival is predicted for 1959 hours this evening instead of 1640 this afternoon - at 1930, the aircraft was being held above Rupanyup, Victoria. B738 VH-VZL has the task.

 

[Melburnian1]

Actually it isn't an example of that at all...

Kind of you to post this: I've noted the subsequent comment from you that 'the data is out there - you aren't seeing it.'

One other AFF member (not Quickstatus) contacted me by private message to say 'he'd have no idea how to interpret it.'

A 'sticky' (that in some cases on AFF turns into what the moderators call a 'Wiki') might be useful for many AFF users.

You deal with these weather reports every time you fly or do a SIM exercise, so it's natural that you're an expert at quickly interpreting them. AFF members who are also aviators presumably need to be able to quickly read and interpret them.

For the rest of us, who in many cases are writing from a passenger perspective and not that of an airline staff member's, a 'sticky' could be of assistance. You have explained the weather reports at times (maybe a year ago?) but as with many blogs and sites like this it can be difficult to search back to find such contributions unless one knows what search terms to use.

 

[Melburnian1]

Into the mid evening of Thursday 29 December, the MEL storm (not a rugby team!) related delays continue, but are highly variable.

QF484, the 1915 hours MEL - SYD took off at 2036. B738 VH-VYF should arrive about 73 minutes late at 2153 this evening.

In contrast, QF490, the 2000 hours departure took off at 2045 (B738 VH-XZN) and is only about 22 minutes late.

Southbound, QF459 (B738 VH-VZU) is operating the 1800 hours SYD - MEL that was in the sky at 1935, its scheduled time of MEL arrival. Instead, it should arrive at 2121 hours.

At 2122 AEDT, QF635, the 1800 hours BNE - MEL that took off about 20 minutes late at 1838 this evening remained in a holding position above Tocumwal NSW. It is estimated to arrive at 2202, 42 minutes late.

 

[Melburnian1]

QF1 is mostly punctual on its SYD - DXB longer sector but on Thursday 29 December 2016, this 1645 hours scheduled departure was airborne at a rather late 2000 hours. A388 VH-OQB should arrive at its DXB gate at 0224 hours on Friday 30, 104 minutes late.

The Wednesday 28 December QF9 ex MEL that was diverted in the Middle East departed DXB at 1302 hours, later than advised by QF on Thursday 29 December. LHR arrival is predicted to be 1630, three hours and 50 minutes (or 230 minutes) tardy.

'The QF2' (to use the lovely description of an esteemed contributor) that arrived ex LHR in DXB at 0921 hours this morning instead of its scheduled 0745 hours then departed at 1330, again far later than QF had suggested earlier today. SYD arrival should be at 0940 hours, 190 minutes late on Friday 30 December 2016. This is quite unusual for QF2.

QF16 should arrive in BNE on Friday 30 at 0755, 50 minutes late, having departed from LAX 64 minutes behind schedule.

 

[Flyerqf]

'The QF2' (to use the lovely description of an esteemed contributor) that arrived ex LHR in DXB at 0921 hours this morning instead of its scheduled 0745 hours then departed at 1330, again far later than QF had suggested earlier today. SYD arrival should be at 0940 hours, 190 minutes late on Friday 30 December 2016. This is quite unusual for QF2.

This flight never departed. Technical issue with OQF. There is NO spare in the 380 or 747 schedule tomorrow so this may cause a downgrade of an A380 (Eg Hong Kong) to an A330. Otherwise delays will be start to appear on other services as a result of the out of position A380.

 

[Melburnian1]

This flight never departed. Technical issue with OQF. There is NO spare in the 380 or 747 schedule tomorrow so this may cause a downgrade of an A380 (Eg Hong Kong) to an A330. Otherwise delays will be start to appear on other services as a result of the out of position A380.

Thank you Flyerqf.

I was relying on the QF website for that flight, which had if I am not mistaken listed it as having departed at the time I discussed above.

Unfortunately because it is Christmas holidays, flights should be full or close to it, so changing QF127 on Friday 30 December (and the return QF128) to an A333 or even A332 may see passengers (to use that shocking USA term) 'bumped' (involuntarily.)

While they've seen it all (well mostly) before, this is when one has to feel for the staff of the operations department as they feverishly work to ensure that at least some passengers can get to where they are booked on the same day. Imagine the communications necessary to different flight and cabin crews, changes to catering arrangements, freight and even fuelling requirements, plus how these alterations affect staff rosters when there are limits on how many hours some can work each month. This one change must run into the tens of man hours to make, even if tasks like reservations will be largely or totally computer based.

 

[Flyerqf]

Thank you Flyerqf.

I was relying on the QF website for that flight, which had if I am not mistaken listed it as having departed at the time I discussed above.

Unfortunately because it is Christmas holidays, flights should be full or close to it, so changing QF127 on Friday 30 December (and the return QF128) to an A333 or even A332 may see passengers (to use that shocking USA term) 'bumped' (involuntarily.)

While they've seen it all (well mostly) before, this is when one has to feel for the staff of the operations department as they feverishly work to ensure that at least some passengers can get to where they are booked on the same day. Imagine the communications necessary to different flight and cabin crews, changes to catering arrangements, freight and even fuelling requirements, plus how these alterations affect staff rosters when there are limits on how many hours some can work each month. This one change must run into the tens of man hours to make, even if tasks like reservations will be largely or totally computer based.

QF127/128 has just been updated in the schedule to a 333 (instead of 388) and 117/118 had changed from 333 to 332.

 

[Melburnian1]

The Thursday 29 December QF9 departed from MEL 64 minutes late at 0029 hours on Friday 30. DXB arrival is estimated at 0715, 45 minutes late. A388 VH-OQD is the aircraft.

 

[Melburnian1]

QF127/128 has just been updated in the schedule to a 333 (instead of 388) and 117/118 had changed from 333 to 332.

This is a net loss of 187 seats for each of QF127 and QF128; because I don't know which configuration A332 will run QF117 and QF118, that change cannot be easily calculated. Flyerqf, you may have access to ExpertFlyer or similar to work that out.

 

[Flyerqf]

This is a net loss of 187 seats for each of QF127 and QF128; because I don't know which configuration A332 will run QF117 and QF118, that change cannot be easily calculated. Flyerqf, you may have access to ExpertFlyer or similar to work that out.

36J/199Y for 117/118