Qantas Delays/Cancellations

Anyone know why QF2905 Antartica charter from Adelaide would drop off the flight trackers ?
 
Last edited:
While showing earlier as expected to be on time, QF79, the Sunday 24 November 0920 hours MEL - NRT has beaen delayed to a projected 1100 hours pushback, suggesting arrival at 1905 tonight, 85 late. Either QF80 - 1920 hours scheduled evening redeye ex NRT to MEL - or QF62, the 1930 hours to BNE will be tardy as a result.
The flight is cancelled so assuming QF80 won’t run. It started as an aircraft computer issue which extended the delay but they couldn’t fix it
 
The flight is cancelled so assuming QF80 won’t run. It started as an aircraft computer issue which extended the delay but they couldn’t fix it

Great information (though 'grating' for passengers.)

Indeed, QF80 is displaying as 'cancelled.' However on occasion 'the 79' forms 'the 62' NRT to BNE, and 'the 61' 'the 80.' There doesn't seem to be a particular pattern to this.

Due to the late QF3 ex SYD and consequent delay to the Saturday 23 QF4 ex HNL that is due into SYD on Sunday 24, the latter date's QF3 is again to be delayed, in this case by an hour tonight to 2020 hours in pushback.
 
Last edited:
EXCLUSIVE OFFER - Offer expires: 20 Jan 2025

- Earn up to 200,000 bonus Velocity Points*
- Enjoy unlimited complimentary access to Priority Pass lounges worldwide
- Earn up to 3 Citi reward Points per dollar uncapped

*Terms And Conditions Apply

AFF Supporters can remove this and all advertisements

Saturday 23 November's QF2 departed LHR on time, arriving SIN on Sunday 24 at 1803, 18 late. However instead of departing at or close to 1915 hours, QF2 then is staying in SIN until an estimated 0230 hours (0530 AEDT) on Monday 25 November. It should arrive in SYD at 1305 this afternoon, 415 minutes late, but may be later. A388 VH-OQF should be the aircraft. Departure must have at one stage been expected to be 0000 (midnight) in SIN as Google Flights is displaying that. At this stage, the aircraft is forming QF1, the 1700 hours afternoon SYD back to SIN and on to LHR so let's hope it isn't delayed two more hours in SIN as that would start to raise the prospect of 'the 1' being delayed. Usually an A380 takes at least 95 - 100 minutes to turn around, assuming everything goes well including all passengers fronting when they're meant to.

Should the crew have signed on at 1815 or so last night (Sunday 24), they'd be very tired by now. However as one of our aviators has mentioned, maximum flight crew duty limit is 18 IIRC with 'by agreement' extension to 20 hours, giving leeway even with this very significant delay.
 
Last edited:
QF2 had to return to the gate. I imagine given the length of the delay it was due to technical reasons.

Thanks milehighclub. Flight Aware's site suggests it departed the gate (C23) at 1940 hours (2240 AEDT) on Sunday 24. An extremely long night for crew and passengers, because if departure is expected in say two, then four hours after the scheduled pushback (but the delay becomes unexpectedly longer), they can't be booked into an hotel.

FA"s site is under the misapprehension that there is '2643 kilometres to go' (i.e. remaining) in QF2's flight stage. When there are extensive delays, various monitoring sites can become confused and show incorrect data.
 
Yesterday’s QF2 will depart tonight at 2015.

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

QFi is back to only nine of its 12 A388s being available for passenger trips. It has an 'out' on Tuesday, as that's the start of the two days when only nine are required at present. This changes some time in December when QF127/QF128 become an A388 (though for a shorter period than originally intended due to the drop in HKG bookings) but as milehighclub kindly informed us previously, the two A388s in Dresden (DRS) and Abu Dhabi (AUH) are supposed to return to the fold on 7 and 10 December. I assume this means 'available for revenue flights' not just their initial journeys from those airfields.
 
Last edited:
But today is Monday. Something has to be delayed or cancelled. Looking at what's happening. OQE went from the QF7 to the QF1 today and OQF is now on the QF7 as its next flight. Considering that aircraft is Singapore, I'm guessing the QF7 will have a 24 hour delay.
 
But today is Monday. Something has to be delayed or cancelled. Looking at what's happening. OQE went from the QF7 to the QF1 today and OQF is now on the QF7 as its next flight. Considering that aircraft is Singapore, I'm guessing the QF7 will have a 24 hour delay.

I wasn't disputing that something needs to be cancelled today, as that's self evident: all I was doing was 'looking forward' to tomorrow when the situation IIRC differs. (Of course, if 'the 7' or 'the 1' is cancelled today, that'll still work through meaning 'the 8' or 'the 2' doesn't then operate, but different matter.)

Based on passenger numbers (which won't be the only consideration), it's less work to cancel QF7/QF8 than QF1/QF2 because the former has c.100 empty seats on its return to Australia due to sector length, and the latter, setting down and picking up passengers in SIN both ways will presumably have many more individual passenger bookings than 'the 7/8.'
 
QF 79 to Narita is delayed due to "a delay of the incoming aircraft". It was due to depart at 0920, and the board is showing 1100, which might be a tad optimistic.
 
QF 79 to Narita is delayed due to "a delay of the incoming aircraft". It was due to depart at 0920, and the board is showing 1100, which might be a tad optimistic.

It was, as it pushed back at 1110 hours. Mooted NRT arrival is 1915 hours, 95 late.

milehighclub was on the money. QF7, the 1440 hours SYD - DFW is cancelled on Monday 25 November due to A388 VH-OQF failing in SIN on the way as QF2a. QF8 on Monday will also not operate.

If an AFFer happens to be booked on either, advice as to alternative travel arrangements, which hotel(s) used and how well the transfers were handled and qulaof included meals would be great.

QF428, the 1130 hours MEL - SYD is another to get the gong.
 
Last edited:
QF35 will be late pushing back. I am not sure how late but as we are still at the gate and we were due to depart at 1210 ...

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.
 
QF2 had to return to the gate. I imagine given the length of the delay it was due to technical reasons.
Looks like the QF2 won't be departing.
Yesterday’s QF2 will depart tonight at 2015.

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

Whilst any return to the gate is most likely technical, both passenger and crew issues can also force a return. In the case of passengers, and most crew, you'll be able to get going again as soon as they and their luggage are offloaded.

Given that the company needs the aircraft back in Oz, waiting exactly 24 hours before scheduling the next flight is a little curious. It's possibly a part that they know the arrival time for, but that's also one of the CASA stand down times.
 
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.
 

Become an AFF member!

Join Australian Frequent Flyer (AFF) for free and unlock insider tips, exclusive deals, and global meetups with 65,000+ frequent flyers.

AFF members can also access our Frequent Flyer Training courses, and upgrade to Fast-track your way to expert traveller status and unlock even more exclusive discounts!

AFF forum abbreviations

Wondering about Y, J or any of the other abbreviations used on our forum?

Check out our guide to common AFF acronyms & abbreviations.
Back
Top