Qantas Flight Delays

[Happy Trails]

And the racial slur is just wrong - Joyce is just as much an Australian as you and I

Hackneyed and irrelevant certainly, but hardly a racial slur.
And I say that as, inter alia, an Irish gentleman.

 

[simong]

Few points as I was actually a passenger on QF460.

We parked on the military side of Newcastle Airport, indeed due to the lack of correct steps for a 767, the military physically supported the steps and restricted the amount of passengers on at the same time. So it's fair reporting to my mind.

I noted someone knocking C7 for sensational reporting by interviewing a passenger who thought they may die. There were passengers who did think that, so again I don't see that as inaccurate. I will say I am in no way a nervous flyer, never bothered by turbulence but this was truly terrifying for me. I think for me it was the fact we were so close to the ground at the time, I am still quite shaken by the whole thing. I also have some minor pains in my neck and shoulder. Also the fact that it happened twice, after we held for so long and then were told other planes were landing fine for the same thing to happen was not great!

I would have preferred a hotel in Newcastle and to wait till the morning but QF Link Ground agent (her uniform) seemed to have no clue on that, they appeared not have even checked the hotels when I asked, there was rooms available to my checks. They said wait and we will see but I had no confidence so I did ride the bus back to Sydney airport rather than continue to wait.

At the start of the bus ride I contacted QF Customer Service to ask them to speak with Operations (or whoever would be relevant) to ensure there would be arrangements made with the airport and taxi companies to have taxis there. This took nearly 30 mins to get them to understand the issue, eventually sort of got there and was told there would be cab charges or we could claim.

On arrival (2:45am) there was two QF staffers (that I saw) handing out stupid letters (the letter telling is what had happened on our flight like we didn't know!) I asked for a cab charge and was asked if I lived in Sydney, when I replied in the positive I was told then I was entitled to nothing, she was extremely rude about it. Now I read upstream cab charges were being offered, I thought this was very bad behaviour from QF.

A few taxis were arriving, thankfully some cabbies took it on themselves to try and organise and encourage people to share cabs, no help from QF or Sydney airport. The taxi driver told me was just going off shift but heard about it and wanted to help, that was great to hear.

I am also surprised in a way that QF didn't call to see how we were going yesterday, that would seem the smart move but ho hum.

 

[phily]

Why would channel 9 say "landed at a military airport in Newcastle"?

Yes, it does sound more sensational than simply reporting that it was Newcastle airport. And apart from being fully owned and operated by the RAAF (except for the commercial terminal), it has only one runway.

 

[Red Roo]

I am also surprised in a way that QF didn't call to see how we were going yesterday, that would seem the smart move but ho hum.

Apologies for the delay in picking this up. I hope you had a chance to relax over the last few days and are feeling better.

I've since followed up with our Customer Care team who've advised that all customers from your flight have been contacted. Should this not be your experience, please send me a private message with your details as reference.

 

[QPProletarian]

On arrival (2:45am) there was two QF staffers (that I saw) handing out stupid letters (the letter telling is what had happened on our flight like we didn't know!)

This is actually quite important for travel insurance.

 

[simong]

This is actually quite important for travel insurance.

It is indeed but that doesn't mean it needs to be written that way. A statement of facts is fine, not telling me I will be travelling on a coach to Sydney when I just arrived off that coach.

 

[Melburnian1]

Today QF23 departed 50 minutes late from SYD at 1125. It is due to arrive BKK at 1625, the same 50 minutes late. This may vary a little depending on ATC in BKK among other factors.

However, the QF computer still shows QF24 as departing at the timetabled 1715. A 50 minute turnaround for an A330 is not normal for international flights.

I have seen this many times. Why doesn't the computer adjust the times for flights that it knows must be formed by a particular arrival (QF does not normally have spare planes in BKK) and therefore inform passengers a few hours in advance? Today's delay will hopefully be minor, but this lack of an update in advance also occurs with much longer delays to inbound flights.

 

[mannej]

Are you saying a 50 minute turn around isn't possible?
Aren't they turned around in similar times domestically?

 

[Melburnian1]

mannej, at MNL for instance, the minimum achievable turnaround when QF19 is late seems to be 65 minutes. True, MNL is not BKK but one feature common to both is that on international flights, there will typically be more LD 3 containers to unload or load since there is often more freight and usually at least a bit more hold baggage than on most Australian domestic flights. mannej, perhaps PER - MEL and PER - SYD are exceptions to the baggage assumption I make because of all those ex mining workers looking to restart their lives in MEL or SYD and bringing the proverbial house with them - you would know.

There is also more catering to be loaded: we all consume more on a nine hour flight from BKK to SYD than on a 4.5 hour transcontinental Australian domestic flight. Cleaning may take a bit longer for an international flight because on the inbound QF23, passengers have had at least twice as long to be messy as they have on a PER - MEL or PER - SYD flight. Boarding procedures can also be more complex for international flights: last minute security checks at some airports is an example. All these things have the potential to add a couple of minutes here, a few minutes there to turnaround times.

On Thursday 12 December, QF23 arrived BKK 33 minutes late at 1608 with QF24 departing 19 minutes late at 1734 - an 86 minute turnaround.

On the luckiest day of December, Friday 13, QF23 arrived 16" late at 1551 with QF24 departing BKK at 1728 - 13" late - a 97 minute turnaround.

Yesterday (14 December 2013) the QF23 arrived BKK at 1600 (25" late) and departed as QF24 at 1725, only 10" late but again a fairly similar 85 minute turnaround.

These historic flights are not a perfect guide to what may occur tonight, but they suggest that it won't be a 50 minute turnaround.

Of course some of this may be due to lack of ATC clearance if the flight is not ready to depart at its appointed hour.

So let's both monitor it and observe what turnaround times QF achieves tonight at BKK. Unfortunately AFF does not allow Internet gambling otherwise we could each pop $100 on the table.

 

[Melburnian1]

mannej, today's QF23 ended up arriving BKK at 1646 (71" late) and departing at 1805 (50" late) after a 79 minute turnaround. Apologies: a couple of posts ago I implied it was an A330: it is not.

This is about 60 per cent longer than your questioning about '50 minute turnarounds.'

The website flight status for the returning flight should reflect this inability to achieve super fast turnarounds.

Based on the sample of four flights above, we'd be on fairly solid ground if we concluded that QF cannot turn around at BKK in under 75 minutes. This is slower than at MNL, but the latter is an A330 route whereas QF23 is a 744 at present. It's holiday time now for many so the flights on both routes should be well loaded (and are on SYD - MNL, but I have not checked SYD - BKK).

It would be interesting to see the minimum turnaround time for a QF A330 or B744 at SYD but the inbound flight from most destinations would have to be pretty late as the schedules allow a decent time to unload and load passengers, freight and catering and refuel the planes.

 

[docjames]

Whilst modestly irritating for the pax affected, is a 60 minute delay on an ~8hr flight really that significant we need to discuss it every time it happens?

You missed QF63 and 64 on 12/12 which arrived 43mins late and departed 68 mins late. Reasons were headwinds and thunderstorm respectively.

You also missed QF437 on 13/12 which departed 28mins late.


Neither of the last two were particularly significant to the broader community - although as an affected pax it was a minor inconvenience.

I'm sure there's plenty of others on multiple airlines......

 

[Melburnian1]

QF568 ex PER operated by VH-EBM on Christmas Day may have had a medical diversion into ADL.

It was at ADL from 0458 to 0554 this morning (Thursday 26 December) and as a consequence is due to arrive at the SYD gate at 0808, 108 minutes late. Not helpful to maintaining the schedule of its next duty on one of the two or three busiest leisure travel days of the year.

 

[elbarto]

QF568 ex PER operated by VH-EBM on Christmas Day may have had a medical diversion into ADL.

It was at ADL from 0458 to 0554 this morning (Thursday 26 December) and as a consequence is due to arrive at the SYD gate at 0808, 108 minutes late. Not helpful to maintaining the schedule of its next duty on one of the two or three busiest leisure travel days of the year.

I'm sure the person who needed medical attention would have been fine with the continuing on so QF could keep their schedule.

 

[Melburnian1]

Whilst modestly irritating for the pax affected, is a 60 minute delay on an ~8hr flight really that significant we need to discuss it every time it happens?

In that instance, the good doctor, I was referring to how the QF website failed to indicate as soon as it could have that a following flight would be delayed: in that case, the return working of a BKK to Oz flight. That is a systemic issue for the website, rather than merely incomplete information for a single, unrepeated QF flight delay.

On a different matter, today's QF29 from MEL to HKG (timetabled out at 1050) was initially shown as altered to depart at 1400, but ended up leaving MEL at 1704 for a forecast HKG arrival of 2310, five hours and 55 minutes late. The Qantas source website has yet to indicate what went wrong. Did an A330 go tech in MEL or elsewhere?

As a result of the inbound delay, QF98 (HKG to BNE) passengers tonight are expected to be delayed just under five hours departing HKG with a changed departure time of 0010 (i.e. Saturday 4 January 2014). I cannot see what aircraft it is as the flight is presumably in northwest Australia at present in a part of WA that Flightradar24.com - Live flight tracker! does not cover.

As a further consequence, QF97 ex BNE (scheduled 1025) is expected to not depart for HKG until 1200 on Saturday, so all AFFers with status can enjoy an extra drink or three in what is often described on AFF as a crowded QF lounge in the mornings.

 

[gwilli1]

• QF29 was flown on 2014-01-03 by VH-QPB (A333)

I cannot see what aircraft it is as the flight is presumably in northwest Australia at present in a part of WA that Flightradar24.com - Live flight tracker! does not cover.

 

[Melburnian1]

Many thanks, gwilli1. According to the Qantas source site, that plane operated QF36 on Thursday 2 January from SIN to MEL. It arrived 11 minutes early at 0619 on Friday 3 January (today) so perhaps it required some attention before departing very late to HKG.

As an update, QF29 arrived HKG at 2316 on Friday night but QF98 did not leave for BNE until 0047, five hours and 32 minutes late. QF suggest it will arrive BNE at 1130 and optimistically suggest an hour's turnaround, departing as QF97 at 1230 for a predicted 1835 arrival at HKG, picking up 55 minutes on that schedule.

In a further update, the predicted departure time for QF97 ex BNE proved optimistic, with the actual time being 1309, 2 hours and 44 minutes late with a suggested, again bit optimistic HKG arrival time of 1837 on www.flightradar24.com given that at 1440 AEDT with seven hours until 1840 Hong Kong time, the flight still had 6600 kilometres to go. By 1450 AEDT, the QF website had amended this predicted arrival time in HKG to a far more realistic 1925.

In turn, either QF98 to BNE or QF30 to MEL will be late away from HKG this evening so that will make a total of four international flights delayed from one late departure.e late away this evening. Once again the QF website does not show this yet.

 

[Melburnian1]

QF30 from HKG to MEL last night departed at 2049 (79 minutes late) as a result of the above chain of events, and is due to arrive MEL at 0851 this morning, 56 minutes late. In turn, this late arrival is pretty likely to delay the flight QF30 forms, QF35 to SIN, which is due out at 1020.

Hopefully then due to the long turnaround time in SIN, the delays for this plane will cease and the evening flight tonight back from SIN to MEL will be punctual.

 

[nonpop]

QF30 from HKG to MEL last night departed at 2049 (79 minutes late) as a result of the above chain of events, and is due to arrive MEL at 0851 this morning, 56 minutes late.

I found myself on that QF30. The delay was handled well. We received plenty of advance notice via email, SMS, 2 missed calls to my mobile and 1 very clear vmail with instructions where to call for more info. I also had a connecting AU domestic flight and QF confirmed in the vmail I would still be OK for my connection. Well done QF for the communication.

 

[Melburnian1]

That's good to hear nonpop, but your experience shows how a delay a few flights ago can continue and affect later travellers on other flights. QF35 to SIN, the next flight for this plane, was due to depart at 1020 but still has not, and is shown on the Melbourne Airport - Flight Information, Shopping & Parking website as departing at 1045. You may well have had connecting passengers for ADL, HBA, LST or MQL who as a result of the late running will miss a connecting flight. For the routes with lower flight frequencies, this can mean a further resultant delay of some hours, which is annoying when one is tired after an overnight flight, given the difficulty in Y class in experiencing anything that remotely resembles proper sleep unless there are two or three shadows next to you.

QF35 departed at 1055, an exact two hour turnaround after its overnight trip from HKG and shown as due at SIN at 1550, the latter being 45 minutes late. Presumably after all those flight hours in quick succession it needed a decent cabin clean!