Qantas Delays/Cancellations

[Melburnian1]

In further on 15 August, QF449 (A332 VH-EBL, the 1630 hours from SYD down to MEL that was in the sky at 1725) is predicted to be at its nominated arrival gate at 1851 hours, 46 minutes late.

The 1620 hours ADL - MEL (QF692, B738 VH-VZV) pointed skywards at 1713, so the suggested 1847 hours arrival will be 37 late.

 

[xen0n33]

August 15's QF435 SYD-MEL (VH-EBD), scheduled for 13:00 departure, didn't end up leaving until 14:20 (arrival in MEL was 15:51 - headwinds prevented making up any time).

Taxied out almost to the runway but stopped as it was announced that a fault had occurred and they were working to clear it. Shortly after it was announced that we'd be returning to the gate (another short delay on the way back waiting for a spare gate) and an engineer called for. Eventually it was explained as being an issue where the tyre pressure was being incorrectly reported as being too low and they'd need 15-20 minutes to work around that.

 

[Melburnian1]

Wednesday 16 August has QF80, the redeye NRT down to MEL (A333 VH-QPB) arriving at 0829, 34 minutes late.

Transcon QF565 (A332 VH-EBD, 0600 hours from SYD that took off only five minutes or so tardy at 0620) is battling the winds and unlikely to arrive PER before 0949, 44 minutes late.

 

[Melburnian1]

Continuing with Wednesday 16 August, QF127 from SYD to HKG has been delayed by an expected hour in its departure to 1100, meaning arrival at least 35 late at 1755 late this afternoon local time. QF29 from MEL is also delayed with its departure the same at 1100, 40 late being the estimate. This is also a HKG-bound flight.

QF52 arrived BNE at 0825, 130 minutes late due to the late arrival of the ex-MEL flight yesterday. It is not departing until a scheduled 1200 'high noon' on QF51 back to SIN so there should not be any directly related late running from its tardy arrival.

The 0915 hours MEL - LAX longhaul, QF93, departed 54 late at 1009 hours.

QF2207 (1025 hours mid morning SYD - ABX that took off at 1105, Q300 VH-SBB) is predicted to arrive in the Border City at 1236, 41 minutes late.

 

[r0dn3y]

Continuing with Tuesday 15 August, QF2053 (1230 hours MEL across Bass Strait to DPO) that departed five minutes early at 1225 had a missed approach at the latter at about 1334. Timetabled 'at gate' arrival is 1335.

Q400 VH-LQD initially looked as if it could be diverting to nearby BWT, but by 1344 appeared to be again heading for DPO. Is there fog at DPO? It is rainy, the wind does not looks overly strong, humidity is at 98 per cent and the barometer is low.

QF2053 had a second missed approach at DPO at 1403 hours, but by 1420 was diverting back to MEL. The QF website at 1425 was incorrectly showing it as having landed at DPO at 1403 hours. Interestingly (although a takeoff not a landing) ZL3562 managed to point skywards from nearby BWT at 1407 for its MEL-bound flight.

I was on this flight. Actually had 2 missed approaches due to low cloud at Devonport and returned to Melbourne, arriving around 1500. Passengers were re-booked onto QF2057 which left 1545 ..

 

[Melburnian1]

I was on this flight. Actually had 2 missed approaches due to low cloud at Devonport and returned to Melbourne, arriving around 1500. Passengers were re-booked onto QF2057 which left 1545 ..

r0dn3y. thank you. I had recorded the second missed approach and the diversion to MEL as well, a few posts back.

How many passengers were on your original QF2053? QF2057 can't have been too well booked if everyone was able to be conveyed by the latter. Was QF2057 close to, or, full?

Did you receive extra refreshments due to the delay?

Was there any explanation as to why QF2053 did not, for instance, endeavour to land at LST as an alternate? As far as I could see yesterday LST was open, but admittedly I did not observe a Q300, Q400 or similar landing there around 1400 hours.

 

[r0dn3y]

r0dn3y. thank you. I had recorded the second missed approach and the diversion to MEL as well, a few posts back.

How many passengers were on your original QF2053? QF2057 can't have been too well booked if everyone was able to be conveyed by the latter. Was QF2057 close to, or, full?

Did you receive extra refreshments due to the delay?

Was there any explanation as to why QF2053 did not, for instance, endeavour to land at LST as an alternate? As far as I could see yesterday LST was open, but admittedly I did not observe a Q300, Q400 or similar landing there around 1400 hours.

No worries. Sorry I missed part of your post. I've have now edited my post to show your full QF2053 info.. I've been a reader for a while but this is my first time contributing anything...

At an estimate, QF2053 was <50% full. QF2057 only had a couple of seats free from what I could tell.

After the first missed approach the Captain advised the missed approach was due to low cloud. He said we did an ILS approach but when we reached his minimum altitude they couldn't see the runway due to the low cloud, so had to perform a missed approach. He said was in contact with the company and they will advise what the plan was soon. A short time later he came back on the PA to advise they would try another approach again in around 10-15 minutes and hopefully the low cloud has improved. He then went on to say if they failed a second time again we would be diverting to either Launceston or going back to Melbourne, but he wasn't sure which one at this time. After the 2nd missed approach he confirmed we were going back to Melbourne. He didn't give a reason (Melbourne vs Launceston) however I suspect it was a combination of the light load, the minimal time before the next Devonport departure and also perhaps no delays to that plane / crews next scheduled onward flight (Mildura I think)?

The cabin crew did offer drinks and a snack on the flight back to Melbourne, but no hot drinks due to turbulence.

Personally, returning to Melbourne and catching another flight straight away wasn't much worse than diverting to Launceston, and catching a bus back to Devonport. First time (hopefully the last) doing 3 trips across Bass Straight in one day though!

 

[Melburnian1]

Continuing with Wednesday 16 August, QF127 from SYD to HKG has been delayed by an expected hour in its departure to 1100, meaning arrival at least 35 late at 1755 late this afternoon local time....

QF127 departed at 1126; HKG arrival today is predicted at 1822 hours, 62 late.

The 1630 hours MEL - SYD QF 450 took off at 1708 hours with B738 VH-XZP. Arrival is forecast as 35 minutes tardy at 1830 hours. In the opposite direction, QF469 with VH-VZO, the 1615 hours should arrive at around 1824, 34 minutes behind the eight ball, so very similar to its northbound counterpart.

The 1555 hours BNE down to MEL (QF627, B738 VH-VZE) was extremely prompt in becoming airborne at 1604 but is encountering some air traffic congestion on approach (althou8gh it has not been in a holding pattern, but may have been subject to ATC-imposed 'speed restrictions' as arrival is likely at 1850, half an hour behind schedule.

VH-VZT on QF569 from SYD across to PER, the 1635 hours took off about 15 minutes late at 1659 but presumably due to unfavourable winds arrival is predicted at 2044 hours, 64 minutes late.

QF571, the next odd number in the series, is another SYD - PER (the 1735 hours that took off even more expeditiously at 1746 with VH-EBB.) Arrival should be at 2118 hours, 38 late.

 

[Melburnian1]

Thursday 17 August 2017 sees QF1545, the 0815 hours peak time SYD - CBR not expected to depart until 0945 hours; arrival becomes as an estimate 1050 instead of 0915.

QF565 (0600 hours SYD - PER) was airborne only five minutes late at 0618 but its A332, VH-EBE is contending with unfavourable winds so arrival is suggested as 0949 hours, 44 minutes late. QF575, the 0810 hours with VH-EBS was airborne from SYD at 0828 (the same 18 minute taxi as for 565) but PER arrival is estimated at 1203 hours, 48 late.

QF93 from MEL to LAX, the 0915 hours, is predicted to commence pushing back at 1030 with a 45 minute late same day arrival at 0720 hours the estimate. This is due to A388 VH-OQH on the inbound QF94 being likely to arrive at 0818 hours, 83 minutes late. QF94 this morning has a fairly unusual flight path through Gippsland near Maffra and over Mt Baw Baw.

 

[Melburnian1]

One missed from last night, QF9 (2255 hours Wednesday 16 August MEL - DXB - LHR) departed at 0017 on 17 August. QF estimates that the DXB stop will be from 0835 to 1000 (against timetabled departure at 0905) with LHR arrival suggested as 1510, an hour behind. Often however time can be picked up between DXB and LHR on a gate-to-gate basis. 85 minutes in DXB is fast (considering everyone has to deplane and those continuing on reboard, plus the crew change and numerous other tasks), but it sometimes is as quick as this. The long allowed turnaround in LHR between QF9 and QF2 means that the latter should not depart late if QF9 is just an hour or three late, unless there is some necessary, time consuming maintenance.

 

[jb747]

QF94 this morning has a fairly unusual flight path through Gippsland near Maffra and over Mt Baw Baw.

Flying in over Gippsland isn't all that unusual, but flying over NZ is. The track would have been chosen to reduce the effect of the strong winds further north.

 

[Melburnian1]

Flying in over Gippsland isn't all that unusual...

I don't necessarily observe it every day (so must have missed other via Gippsland days) but the most common routing in Oz for QF94 seems to be close to Sydney then down on the standard Sydney - Melbourne track.

 

[jb747]

I don't necessarily observe it every day (so must have missed other via Gippsland days) but the most common routing in Oz for QF94 seems to be close to Sydney then down on the standard Sydney - Melbourne track.

There are three common tracks. Most used is via Sydney, but via Brisbane, or via Mallacoota appear pretty regularly. All depends on the upper level winds.

 

[docjames]

Flying in over Gippsland isn't all that unusual, but flying over NZ is. The track would have been chosen to reduce the effect of the strong winds further north.

Interesting - from https://flightaware.com/live/flight/QFA94/history/20170816/0510Z/KLAX/YMML

[FONT=&quot]Distance[/FONT]​

[FONT=&quot]Actual: 13,733 km (Planned: 12,771 km/Direct: 12,773 km)


The day prior was the "usual" track "via sydney"....[/FONT]

 

[Melburnian1]

Continuing with Thursday 17 August, QF834 from MEL up to CBR, the 1655 hours did not take off until 1742. Arrival for B738 VH-XZA is predicted 37 late at 1837.

Transcontinental QF571 (1735 hours SYD across to PER that was airborne more or less on time at 1749 with A332 VH-EBD) is suggested as arriving at 2118 hours this mid evening, 38 minutes behind schedule thanks to the winds.

Wednesday 16's QF12 departed JFK at 1854, 44 minutes late, arriving LAX 54 late at 2154 hours. With its change from a B744 to an A388, QF12 then pushed back at 2335 hours, 65 minutes tardy. Friday 18 arrival is estimated at 0705 hours, 45 minutes late.

 

[Melburnian1]

Friday 18 August sees QF98, the redeye HKG - BNE (VH-QPJ) suggested as arriving at 0801 hours, 76 minutes behind schedule as on Thursday night it did not become airborne until 2110 compared with timetabled departure of 2000 hours.

QF94 (A388 VH-OQA) was showing last night as less than half an hour late but this morning (Friday 18) is arriving at 0731 hours, 36 late. This may marginally delay QF93, the 0915 hours MEL - LAX.

The winds must again be very unfavourable as QF565 (A332 VH-EBM, the 0600 hours SYD - PER that took off at 0627 only about 12 minutes tardy) is not estimated to arrive until 1000 hours, 55 minutes late. One weather site said that wind variability in Western Australia was typically higher at this time of year, but that is a complex discussion best left to meteorologists.

QF80 from NRT to MEL has a generally good timekeeping record (as do most flights ex or to Japan) but this morning it was held over Tocumwal NSW for a while, so arrival is predicted at 0826, 31 minutes tardy. If this aircraft forms the returning QF79, the 0935 hours, it may be marginally delayed in its departure.

The AKl - BNE Jetconnect-operated QF124 (the 0620 hours scheduled that was airborne 61 minutes later) is arriving with B738 ZK-ZQA at 0915, an hour behind schedule.

 

[docjames]

Interesting - from https://flightaware.com/live/flight/QFA94/history/20170816/0510Z/KLAX/YMML

[FONT=&amp]Distance[/FONT]​

[FONT=&amp]Actual: 13,733 km (Planned: 12,771 km/Direct: 12,773 km)


The day prior was the "usual" track "via sydney"....[/FONT]

And the next day much more northerly - overflying South Stradbroke Island

https://flightaware.com/live/flight/QFA94/history/20170817/0510Z/KLAX/YMML

Actual: 15,072 km (Planned: 12,771 km/Direct: 12,773 km)

Again note planned vs actual (so presumably significant winds made the extra distance a better option)



And then the following day is "via AKL" route

https://flightaware.com/live/flight/QFA94/history/20170818/0510Z/KLAX/YMML

 

[Melburnian1]

Media reports are highlighting the strong winds at SYD but so far, on 18 August as at mid morning there are not huge numbers of significant delays. However the commentary discusses how these winds are to peak between 1000 and 1400 hours.

QF507 (B738 VH-VZS) did not take off until 0851 in BNE, 81 minutes after its timetabled 0730 hours departure. Arrival is showing as 1026, also 81 late. As at 1016 the aircraft is about to turn east to land on the east-west runway.

 

[moa999]

QF7 ended up in PHX instead of DFW due to medical.

Pics from Phoenix Airport
https://twitter.com/PHXSkyHarbor/status/898330807227473920

Has now spent 2hrs on the ground.
QF8 not yet showing a delay, but surely will be

 

[jb747]

QF7 ended up in PHX instead of DFW due to medical.

Has now spent 2hrs on the ground.
QF8 not yet showing a delay, but surely will be

It's an alternate for Dallas, and sometimes for LA too.