Qantas Delays/Cancellations

[JessicaTam]

I was also on this evening's (Sunday 29/5) QF453 SYD-MEL sector. Landed around 1905 about 30 minutes behind schedule...

Where were you? I was in 4K.

Edit: just checked and found I flew this aircraft in October pre-refurb. I prefer the new look!

 

[MEL_Traveller]

Where were you? I was in 4K.

Edit: just checked and found I flew this aircraft in October pre-refurb. I prefer the new look!

Glad you enjoyed it. Some of us 'took one for the team' and endured a 2-3-2 configuration The centre seats are certainly the ones to go for on that. We were fighting for armrests on the window pairs. Eating was only possible if one person at a time used their cutlery.

 

[ChrisGibbs]

Where were you? I was in 4K

I was originally in 23B then got the magic red light when boarding and moved to 7A for a quick exit out of Door L2. The refurb'd A330's are definitely better than the legacy domestic configuration and for that matter better than the SkyBed's.

 

[Melburnian1]

On Monday 30 May, QF416, the 0830 hours MEL - SYD has been cancelled as has QF407, 0715 hours SYD down to MEL.

While QF804, an early morning MEL to CBR creditably managed to be off blocks two minutes early at 0718, arrival was 33 minutes late at 0858. Was there fog?

The 0720 BNE to mining town MOV departed an hour late at 0820 hours, arriving 61 minutes late at 1006. QF2512, the 0905 hours BNE to MKY was cancelled.

QF128, the redeye from HKG (B744 VH-OEH) should arrive in SYD at about 0850 instead of 0715 as on Sunday 29 it did not take off until 2240, compared with its timetabled departure of 2015 hours.

A pleasant morning flight, QF1583, the 0920 hours SYD down to HBA turned into an afternoon journey with departure on Monday at 1209 and suggested arrival in the southern island capital at 1356 rather than 1120.

The 0950 hours SYD to LAX, QF11, did not depart until 1101 with arrival expected same day 40 minutes late at 0710.

QF1471, the 1000 short hop SYD to CBR did not depart until 1038; arrival was at 1129, 34 minutes late. The 1130 SYD across to ADL, QF1555, departed at 1224 with arrival expected as 1358, 48 minutes behind time.

QF117 from SYD to HKG has been delayed in its departure from 1215 until 1300. Arrival is estimated as 2015 in lieu of 1940 hours this evening.

The 1245 hours SYD - CBR, QF1479, should instead depart at 1320.

 

[Melburnian1]

QF406, the 0645 hours MEL to SYD has been cancelled on Tuesday 31 May.

 

[nonscenic]

Nonscenic can you translate the image please?

The image showed the forecast wind speed and direction at FL390 (typical cruise height) at 5 degree lat long intervals. Look for the underlying outline of Pacific rim countries. Then the stronger westerly jetstreams in mid latitudes and the light easterly equatorial flow become evident. They are produced globally in sections. In practice the flight route is computer generated but the charts are still produced to portray the forecast pictorially for pilots and other interests. Being a meteorologist myself, I like to look at these charts and others when flying. Together with a window seat and a gps I find it a good way of passing time on a long flight. It also helps me anticipate the arrival time and the likelihood of turbulence while meals are being served.

 

[Quickstatus]

JFK Terminal 7 checkin computer had a server glitch causing delays on Sunday afternoon from 1600 ET including to QF12.

Checkin reverted to manual for many flights. QF12 transcontinental departed 1.3 hours late but should arrive into LAX after 2100hrs. It is anticipated that BNE arrival will be marginally late if at all (as this aircraft operates QF16).

The A380 QF94 and QF12 transpacific is anticipated to depart on time. However there should be enough time for connecting passengers from JFK to make both.

This should be the last of the "run of 3" for those superstitious. Or for this flight number 4 runs.
27/5 : 0008hrs (+1)
28/5 : 1901hrs
29/5 : 2250hrs
30/5 : 1921 hrs

 

[flychrisfly]

I was on QF1 which had a slightly delayed arrival into DXB on 1 June. We were running early even after a loop and a zigzag coming into DXB when at about 200 metres of altitude a go-around was initiated. The flight deck were surprisingly quick on the Comms to tell the pax what was going on. The plane landing in front of us had noticed some foreign debris (FOD) on the runway and called it through. So we powered up and headed out into the gulf - we were landing in a westerly direction. As we moved over the water the fligh deck gave us another update and then again 5 mins before finals and then again on finals. And after we landed and were on stand the captain came out of the flight deck and had a chat with a few of us standing around waiting to disembark. Very impressed with the comms even when there was no change in the info.

 

[Quickstatus]

Thanks Flychristy,

Can you estimate how long you were in the air before the 2nd landing?

I have always thought communications from flightdeck makes air travel much more interesting even though the passenger really are just along for the ride - just "self loading freight". It is interesting you say that the comms occurred relatively quickly because this would be a period of high workrate for the pilots, even if a TO/GA manouver is highly automated.

 

[jb747]

It is interesting you say that the comms occurred relatively quickly because this would be a period of high workrate for the pilots, even if a TO/GA manouver is highly automated.

What makes you think that it's 'highly automated'? And beyond that, what do you think that 'highly automated' would actually do?

 

[Melburnian1]

On Wednesday 1 June 2016, QF19 from SYD to MNL (the 1210) did not depart until 1309. Arrival is expected 25 minutes late at 1855 but often this proves to be an underestimate as MNL suffers from congestion at many times of the day and night. A332 VH-EBL is again operating this flight today which lately has been common. QFi must have insufficient A333s to operate all medium length flights.

QF117, the second flight of the day from SYD to HKG - the 1215 hours - was cancelled on 1 June. The QF website suggests that this evening, QF98 from HKG to BNE, QF128 and QF118 to SYD and QF30 to MEL are all operating as normal with no expected delays. This is unbalanced, assuming that there is no QF aircraft sitting in HKG today that previously failed. Am I missing something or has the QF software not updated the QF website to reflect a cancellation ex HKG this evening?

Earlier on 1 June, QF93, the 0915 hours ex MEL did not depart for LAX until 1006 but it should arrive at the gate at 0700, just 25 minutes late. AFF member and meteorologist nonscenic will doubtless have an excellent explanation for a westerly jetstream or similar pushing this flight along.

 

[Quickstatus]

What makes you think that it's 'highly automated'? And beyond that, what do you think that 'highly automated' would actually do?

A320 pilot friend told me:

By pushing the thrust levers to the TOGA detent causes several actions - activates the go around mode if the aircraft is in approach mode - autothrottles to GA thrust as computed by FMC, autopilot no longer follows approach glideslope? and autopilot flies a missed approach path?

Maybe at the very base its just a "macro" - press one button and several steps are initiated/executed.

Pilot friend calls it the 5 ups: Powerup, nose up, gear up, flaps up, speak up??

One thing I did not ask him was whether after a missed approach does the aircraft have to rejoin the landing queue from the back?

Is a "missed approach" and "go around" the same?

 

[Simo]

I was on QF 41 about a week and a bit ago and we where delayed by about an hour but the reason was because we had a tail wind and because of 6am curfew had to go slow and not break curfew. I was talking to the pilot at about 4am and they said that we where going very slow and there was about 6 or 8 flights just behind them and it will be busy with landings and will cause congestion in customs and Tarmac as well

 

[Quickstatus]

QF117, the second flight of the day from SYD to HKG - the 1215 hours - was cancelled on 1 June. The QF website suggests that this evening, QF98 from HKG to BNE, QF128 and QF118 to SYD and QF30 to MEL are all operating as normal with no expected delays. This is unbalanced, assuming that there is no QF aircraft sitting in HKG today that previously failed. Am I missing something or has the QF software not updated the QF website to reflect a cancellation ex HKG this evening?

I think VH-QPC overnighted in HKG after operating (31/5/16) QF117. It did not return as QF118 on 31/5/16. I suspect this aircraft will operate tonight's (01/6/16) QF118

The QF117/118 pair is a Sunday to Thursday operation

 

[nonscenic]

Earlier on 1 June, QF93, the 0915 hours ex MEL did not depart for LAX until 1006 but it should arrive at the gate at 0700, just 25 minutes late. AFF member and meteorologist nonscenic will doubtless have an excellent explanation for a westerly jetstream or similar pushing this flight along.

It would pay them to head as far east in the Southern Hemisphere before heading up to LAX - there's not much of a jet west of LAX to help but good westerlies over the South Pacific.

 

[flychrisfly]

Thanks Flychristy,

Can you estimate how long you were in the air before the 2nd landing?

I have always thought communications from flightdeck makes air travel much more interesting even though the passenger really are just along for the ride - just "self loading freight". It is interesting you say that the comms occurred relatively quickly because this would be a period of high workrate for the pilots, even if a TO/GA manouver is highly automated.

the original comms indicated a 15 minute delay though 15 mins until landing was re-communicated about 5 mins later after they presumably (and I think it was in the announcement) had a better idea from ATC, so 20 mins all up. For what it's worth, when we looped back to line up for finals there were none of the loops or zig zags or other holding techniques applied to us, but obviously I had no idea of other traffic on approach and if we kinda pushed into an existing queue.

I would suggest the go around procedure may not be that automated but would argue that it's a) well prepared for on each approach (happy to be corrected but my understanding is the flight crew run through the go around procedures on every approach), and b) well practised in the sim and in real life. Plus the 2nd officer may have been in the coughpit and free to help out?

I meant to add that the pilot seemed quite energised by the go around - he indicated it was a bit of fun which I took to mean something a little out of the ordinary without being dangerous.

 

[Melburnian1]

On Wednesday 1 June 2016, QF19 from SYD to MNL (the 1210) did not depart until 1309. Arrival is expected 25 minutes late at 1855 but often this proves to be an underestimate as MNL suffers from congestion at many times of the day and night.

QF19 ended up arriving MNL 51 minutes late at 1921 hours. QF20 is still publicly displaying as departing at 2005 hours (on time) which for an A332 is impossible. Typical efficient turnarounds, with no passengers failing to board at the last minute for this size aircraft or other unexpected snags, and an available departure slot, appear to be 65 to 70 minutes based on numerous observations.

 

[milehighclub]

There is a good reason airlines do not change the departure time of the outgoing flight when the delay is minimal - especially under an hour for international flights.

If you change the departure time, it means that the cut off time for check in is later. Any chance of making up the delay goes out the window because you must work on new departure times once they are published. You still want all your passengers there for the original departure time in an attempt to make up lost time, which in this case is quite possible given the short delay and the combination of the flight time home.

 

[Melburnian1]

QF20 did not take off from MNL until 2122 on Wednesday 1 June so it should arrive in SYD on Thursday 2 June at about 0718, 68 minutes late.

 

[milehighclub]

Not sure where you got that time but when I was looking at this flight it had departed at 2043 (hence the nature of my reasoning behind why you wouldn't change the departure time)