Qantas Delays/Cancellations

On Thursday 8 July QF19 arrived in MNL at 1917, 47 minutes late. QF20 back overnight to SYD departed at about 2045 and is due on Saturday 9 at about 0645, 35 minutes late.

QF9 took off from MEL at about 2355, about 35 minutes late (pushback time is 2255 at this time of year).
 
On Saturday 9 July, QF401 began the day belatedly as this 0600 flight ex SYD down to MEL did not depart until 0650, with arrival at 0807, 32 minutes late. Later, QF423, the 1030, departed at 1106 with arrival suggested as half an hour behind at 1205.

QF2120 (0630 hours SYD up to WTB) departed at 0736, arriving at 0910 hours, an hour late. QF2205 (0820 SYD - ABX) departed at 0908 with arrival 32 minutes behind at 1022.

QF11, the 0950 longhaul from SYD to LAX is showing as delayed until 1045 but that time has come and gone.

The 0955 hours SYD across to AKL, QF143 did not depart until 1030 but arrival is expected only 10 minutes late at 1510 this afternoon.

The 1045 SYD - CBR, QF1473, has been cancelled.
 
Last edited:
Also on Saturday 9 July, B744-operated QF63 departed SYD 103 minutes late at 1233. JNB same day arrival is estimated as 1810, an hour late, which will somewhat delay the departure of QF64 tonight JNB time back to Olde Sydney Town.

QF2002, the 0845 hours from SYD to TMW departed on time but unusually diverted to PQQ, where it spent from 1140 to an expected 1230 with a 1315 hours arrival predicted in TMW, which would be three hours and 20 minutes late. Fog, low visibility or problems with the aircraft? From the holding pattern south of TMW one might suspect that it was one of the first two possible causes (i.e. adverse weather).

The 0950 hours longhaul SYD to LAX departed 64 late at 1054 with arrival suggested, as usual on the same day, at 0705 hours, 35 late.

The 1020 SYD - SIN, QF81 is badly delayed with an amended departure time of 1330 this afternoon for a suggested 1935 hours arrival, two hours and 50 minutes tardy.

The 1300 hours early afternoon SYD - DFW, QF7, is experiencing a minor delay to 1330 in its departure but arrival should hopefully still be on time in the currently much in the news Texas.
 
Last edited:
Friday 8 July 2016's QF2 departed LHR at 2157, 27 minutes late but arrived DXB at 0725, five minutes early. However it departed the Middle Eastern centre of commerce at 1118 on Saturday 9, 123 minutes later than its timetabled 0915 hours, so on Sunday 10 July it should arrive at 0615, 65 minutes late. Normally a late arrival such as this does not delay any of QF1/7 or 11, provided it is only one of the three that is delayed like this.

Also on Friday, the 2320 hours QF16 ex LAX departed at 2349 but is not due in BNE on Sunday 10 July until a forecast 0645, 35 minutes late.
 
Sunday 10 July sees QF1583 from SYD down to HBA forecast as delayed by 75 minutes in its departure from 0920 to 1035 hours.

QF93 from MEL is expected to depart at 1000 instead of 0915 hours for its long journey across the Pacific to LAX where arrival is still estimated as punctual.

A far longer delay is the case for longhaul QF15 from BNE to LAX that is not expected to depart until 1400, a four hour delay from the timetabled 1000 - arrival in LAX is forecast as 0930 not 0600 on Sunday 10.

Assuming that QF15 continues on its normal roster as QF11/12 between LAX - JFK - LAX, this may significantly delay the Sunday night QF12 (A388 flight from LAX to SYD) and QF16 (B744 LAX - BNE) that are both timetabled into east coast Australia on Tuesday morning 12 July. The QF website, which can sometimes be very slow to be updated, still shows QF11 departing from LAX at 0820 hours on Sunday 10 July for its transcontinental USA trip, which is impossible. 1110 is about the earliest that this could be achieved assuming an 0930 hours arrival in 'screen directors' abode'.

QF2281, the 0930 MEL - LST should instead depart at 1020.

Medium length flight QF23 from SYD to BKK is suggested as departing an hour late at 1050, with arrival predicted as 1730 not 1640.

QF171, the 1025 MEL - WLG should push back for the Windy City at 1100.

The 1105 SYD - OOL, QF1568 has been delayed until 1345.

UPDATE: QF93 did not depart until 1033 from MEL with LAX arrival suggested as half an hour behind at 0705.

QF431, the Sunday 10 July 1200 'high noon' SYD down to MEL took off at 1258 so is arriving at about 1416 hours, 41 minutes late with A332 VH-EBM.
 
Last edited:
On Tuesday July 12, Google weather predicts afternoon >30 km winds to be from the NW for the Melbourne area. Would this restrict MEL operations in the afternoon to the shorter 2200m runway 09/27 (eastwest)? (The longer 3600m runway 16/34 is north south)

Screen Shot 2016-07-10 at 3.47.43 PM.jpg
 
Last edited:
Sunday 10 July sees QF1583 from SYD down to HBA forecast as delayed by 75 minutes in its departure from 0920 to 1035 hours.

QF93 from MEL is expected to depart at 1000 instead of 0915 hours for its long journey across the Pacific to LAX where arrival is still estimated as punctual.

A far longer delay is the case for longhaul QF15 from BNE to LAX that is not expected to depart until 1400, a four hour delay from the timetabled 1000 - arrival in LAX is forecast as 0930 not 0600 on Sunday 10.

Assuming that QF15 continues on its normal roster as QF11/12 between LAX - JFK - LAX, this may significantly delay the Sunday night QF12 (A388 flight from LAX to SYD) and QF16 (B744 LAX - BNE) that are both timetabled into east coast Australia on Tuesday morning 12 July. The QF website, which can sometimes be very slow to be updated, still shows QF11 departing from LAX at 0820 hours on Sunday 10 July for its transcontinental USA trip, which is impossible. 1110 is about the earliest that this could be achieved assuming an 0930 hours arrival in 'screen directors' abode'.

QF2281, the 0930 MEL - LST should instead depart at 1020.

Medium length flight QF23 from SYD to BKK is suggested as departing an hour late at 1050, with arrival predicted as 1730 not 1640.

QF171, the 1025 MEL - WLG should push back for the Windy City at 1100.

The 1105 SYD - OOL, QF1568 has been delayed until 1345.

UPDATE: QF93 did not depart until 1033 from MEL with LAX arrival suggested as half an hour behind at 0705.

QF431, the Sunday 10 July 1200 'high noon' SYD down to MEL took off at 1258 so is arriving at about 1416 hours, 41 minutes late with A332 VH-EBM.

QF15 didn't depart until 1622. As a result, the QF11/12 LAX-JFK-LAX is canceled on Sunday.
 
QF15 didn't depart until 1622. As a result, the QF11/12 LAX-JFK-LAX is canceled on Sunday.

Some of the LAX-JFK sector passengers from BNE may have been routed via QF7
There are several AA flights LAX-JFK AA2,172,4,34, 28 that may have space to JFK
Unfortunately there are no direct AA flights LAX-LGA - these have to go usually via ORD.

Perhaps QF will put some passengers on DL,UA.
 
Some of the LAX-JFK sector passengers from BNE may have been routed via QF7
There are several AA flights LAX-JFK AA2,172,4,34, 28 that may have space to JFK
Unfortunately there are no direct AA flights LAX-LGA - these have to go usually via ORD.

Perhaps QF will put some passengers on DL,UA.

i don't think QF7 would have been an option as QF15 was scheduled to depart BNE at 1400 and was further delayed. Once further delayed, QF7 would have already left SYD.

The JFK tag was only cancelled once 15 was pushed back from 1400 to 1600.
 
QF15 didn't depart until 1622. As a result, the QF11/12 LAX-JFK-LAX is canceled on Sunday.

Do the QF B744 tech and cabin crews normally work LAX - JFK - LAX return on the one day or does each overnight in New York for one night?

If either or both types of staff overnight in New York, there will be a crew out of position. This might mean QF has to send an extra crew from BNE or SYD to work one of the flights such as QF16 in due course.

Whether these transcontinental AA flights have sufficient seats for the otherwise marooned QF passengers would be interesting. Westbound, it simply would not be possible for every QF passenger (say) booked ex JFK to show up hours earlier than is normally the case for a QF12 JFK to LAX and beyond check in: some may be connecting by air from elsewhere in USA, or even Central (or South) America; others may be connecting from a rental car/ Amtrak train or other means of transport, and have arrangements at the USA end that they cannot easily alter (weddings, funerals, business meetings are three) or are unwilling to (leisure travellers).

The QF reservations system would be very busy rebooking some of these passengers onto later flights. Conceivably some could arrive a day later in Australia (or in JFK ex LAX).
 
Last edited:
On Tuesday July 12, Google weather predicts afternoon >30 km winds to be from the NW for the Melbourne area. Would this restrict MEL operations in the afternoon to the shorter 2200m runway 09/27 (eastwest)? (The longer 3600m runway 16/34 is north south)


That's only 15 knots. Won't be an issue.
 
QF2114, the mid afternoon Sunday 10 July 2016 1440 hours from SYD to CFS was cancelled.

The 1525 hours QF2006 (SYD up to TMW) departed 72 minutes late at 1637, arriving at 1748, 73 late. QF2034 from SYD to ARM is expected to depart at 1950 rather than 1850 hours, probably due to the delays to the TWM rotation.

QF447 (1600 hours SYD down to MEL) did not depart until 1658, with arrival suggested as 1838, 63 minutes late.

QF463, the 1830 from SYD also down to MEL will instead depart at an exactly timed 1933, with arrival forecast for 2100 hours, 55 minutes late. Often this ATC attempt to allocate a non-five or 10 minute ending slot time does not seem to work: there are just too many variables, including passengers who insist on boarding late presumably in some cases so everyone else can consider how important such passengers are.
 
Last edited:
Do the QF B744 tech and cabin crews normally work LAX - JFK - LAX return on the one day or does each overnight in New York for one night?

If either or both types of staff overnight in New York, there will be a crew out of position. This might mean QF has to send an extra crew from BNE or SYD to work one of the flights such as QF16 in due course.


They overnight in NYC.
Tech and cabin crew will have different slip times. but i don't think they will be short.
Re cabin crew:
There is a B744 crew in NYC now who get an extra day in NYC and will operate Monday's transcontinental QF12.
There is also currently a crew in LAX who will not be operating the cancelled Sunday transcont QF11/12, get an extra day in LAX and will therefore operate Monday's transcont QF11.
There will be a B744 crew in LAX who operated the Saturday's transcont QF12 who will operate Sunday's QF16.
 
Some of the LAX-JFK sector passengers from BNE may have been routed via QF7
There are several AA flights LAX-JFK AA2,172,4,34, 28 that may have space to JFK
Unfortunately there are no direct AA flights LAX-LGA - these have to go usually via ORD.

Perhaps QF will put some passengers on DL,UA.
QF would transfer any LAX-JFK-LAX pax to AA. They wouldn't even consider putting them on another airline unless there were no options on AA.

AA has up to 13 non stop LAX-JFK flights each day. The first 2 or 3 (0600, 0700 and 0800 LAX departures) wouldn't work for connections from the QF flights. Add in connections via any of AAs other hubs (PHX, DFW, ORD, PHL, MIA, CLT) and there are another 30-40 odd options to get pax between LAX and JFK.
It is possible airline staff/systems rerouting pax from the canceled QF transcon wouldn't even think about LGA. In cases like these, airline staff tend to get tunnel vision and often don't consider that other nearby airports might be viable options.

2 years ago, I had a flight CAE-PHL-LGA. CAE had a large amount of flights delayed with ATC issues heading north and weather issues heading west. The delay to my flight meant I would have missed the connection and I was already approaching the gate agent about it as the airline noticed and asked for people with connections to come forward. They were blinded trying to get me to LGA via PHL even if it meant a forced overnight stay in CAE or PHL at their expense. It wasn't until I pointed out that getting put on the next flight to CLT would allow a connection to JFK with NYC arrival only 1 hour late that they remembered that New York had more then one airport.

If it was Monday, Tuesday or Wednesday, when there is a 747 from SYD/MEL to LAX, if QF would have used that aircraft for the transcon instead of waiting for QF15.
 
Do the QF B744 tech and cabin crews normally work LAX - JFK - LAX return on the one day or does each overnight in New York for one night?

Whether these transcontinental AA flights have sufficient seats for the otherwise marooned QF passengers would be interesting. Westbound, it simply would not be possible for every QF passenger (say) booked ex JFK to show up hours earlier than is normally the case for a QF12 JFK to LAX and beyond check in: some may be connecting by air from elsewhere in USA, or even Central (or South) America; others may be connecting from a rental car/ Amtrak train or other means of transport, and have arrangements at the USA end that they cannot easily alter (weddings, funerals, business meetings are three) or are unwilling to (leisure travellers).

The QF reservations system would be very busy rebooking some of these passengers onto later flights. Conceivably some could arrive a day later in Australia (or in JFK ex LAX).
It depends how the system wants to do run it. Heading east to JFK there isn't an issue. There are ~50 flights a day on AA either non stop or via another hub that will get people to JFK. Most will be delayed, some may even have to spend most of the day at LAX waiting, but all the misplaced QF transcon pax will get to JFK before the next QF flights arrive at LAX. Going back is harder. If the system tries to force everyone onto a QF flight out of the US, then there aren't as many options to get people to DFW, LAX, SFO or YVR in time to connect to QF out of North America. If the system just redirects them to AU, it could put people on AA, JL or CX to NRT or HKG, then onto QF home.
 
QF would transfer any LAX-JFK-LAX pax to AA. They wouldn't even consider putting them on another airline unless there were no options on AA.

AA has up to 13 non stop LAX-JFK flights each day. The first 2 or 3 (0600, 0700 and 0800 LAX departures) wouldn't work for connections from the QF flights. Add in connections via any of AAs other hubs (PHX, DFW, ORD, PHL, MIA, CLT) and there are another 30-40 odd options to get pax between LAX and JFK.
It is possible airline staff/systems rerouting pax from the canceled QF transcon wouldn't even think about LGA. In cases like these, airline staff tend to get tunnel vision and often don't consider that other nearby airports might be viable options.

2 years ago, I had a flight CAE-PHL-LGA. CAE had a large amount of flights delayed with ATC issues heading north and weather issues heading west. The delay to my flight meant I would have missed the connection and I was already approaching the gate agent about it as the airline noticed and asked for people with connections to come forward. They were blinded trying to get me to LGA via PHL even if it meant a forced overnight stay in CAE or PHL at their expense. It wasn't until I pointed out that getting put on the next flight to CLT would allow a connection to JFK with NYC arrival only 1 hour late that they remembered that New York had more then one airport.

If it was Monday, Tuesday or Wednesday, when there is a 747 from SYD/MEL to LAX, if QF would have used that aircraft for the transcon instead of waiting for QF15.

Thanks Himeno,
I have now noted AA's other hubs in my smartphone just in case!!!. CLT in particular.

A friend who is CLPO was routed via UA and ensconced in their Global first cabin to SYD last year.
 
Last edited:
Read our AFF credit card guides and start earning more points now.

AFF Supporters can remove this and all advertisements

However on the JFK- LAX sector they may be able to route some passengers via DFW or SFO if there is capacity issues on JFK-LAX AA services.
The oneworld map shows options between LAX and NYC airports with connections via 24 cities including SAN, SFO, PDX, SEA, MSP, AUS, IND, BOS, MCO, RDU and ATL.
 

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