Qantas Delays/Cancellations

On Sunday 9 July, QF12 departed JFK 69 minutes late at 1919 hours, arriving LAX at 2157, 57 late. QF12 (different aircraft) then departed at 2354 hours (84 minutes late) with Tuesday 11 July SYD arrival predicted for 0655, 35 minutes down.

Monday 10 has QF541 (1605 hours BNE down to SYD that took off at 1856, B738 VH-VYD) likely to arrive at 2006 hours, 146 minutes late.

The CBR - ADL QF737 (B738 VH-VYA) should arrive at 2012, 47 minutes tardy.

Sunday 9's QF4 departed HNL at 1242, 102 minutes later than the timetabled 1100, so Monday 10 arrival in SYD was at 1843 instead of 1730. QF3 from SYD back up to HNL has been delayed on Monday 10 from its normal 1930 hours to 2025, so HNL arrival is estimated as (same day) 1010 hours, 50 minutes behind schedule.
 
Last edited:
On Tuesday 11 July, QF1582, the early morning 0620 hours from HBA up to SYD (B717 VH-NXI) did not become airborne until 0702, so arrival should be at around 0840 hours, half an hour behind the schedule.

The delayed QF8 (A388 VH-OQB) ex DFW should arrive in SYD at around 0803, 118 minutes late while the fairly similarly tardy QF12 from LAX (VH-OQC) should be in at 0801, 101 minutes late. holrs514, our AFF member on his way to DFW today (QF7) should be on his way at the appointed time, touch wood.

QF30 from HKG to MEL (A333 VH-QPE) should arrive at 0748, 68 minutes late. VA86 was 56 late and CX135 108 late, so there may have been a systemic problem in HKG last night such as bad weather.

The PVG - SYD QF130 (A333 VH-QPC) should pull in to its designated arrival gate at 0924, 54 minutes past the allotted.

QF1543 (BNE down to CBR, B717 VH-NXJ) should arrive at 0856, 51 minutes late.
 
Last edited:
Mrs C reports Tuesday 0700 MEL-CBR flight departure was delayed till 0800 on account of fog at CBR.
 
Mrs C reports Tuesday 0700 MEL-CBR flight departure was delayed till 0800 on account of fog at CBR.

Yes, I was just looking at that with QF804, the flight to which you refer (B738 VH-VZV) shown as arriving at 0912, 72 late.

QF706 (VH-VXS, also a B738) is slightly ahead of the other flight and should be at its allocated CBR gate at about 0910, just 20 minutes late.

The 1000 hours SYD - HTI, QF1572 (B717 VH-YQV) took off at 1102 and should arrive at 1325 this afternoon, 45 late.
 
Last edited:
Following on from the fog-related CBR delays on the morning of Tuesday 11 July 2017, QF1528 (1030 hours MEL - CBR that was in the sky at 1206 hours, B717 VH-NXJ) should arrive at 1255 hours, 75 minutes behind schedule.

QF23 (A333 VH-QPC) from SYD to BKK has been running late a lot lately, having at least temporarily lost its previous record of rather good timekeeping. On Tuesday 11 it departed 82 minutes behind schedule at 1112 hours and is anticipated to reach BKK's terminal at 1805 hours, 85 minutes late.

The B744 on QF63 was 28 late away at 1118 this morning; arrival is predicted at 1730, half an hour behind.

The 1055 BNE - NRT is like all the Japan flights (QF, NH and JL) generally punctual but it departed today 25 late at 1120 hours with forecast arrival at 1955 hours to be 45 minutes tardy.

QF7 for which our prayers are with AFFer holrs514 as he sweats and hopes to make a 90 minute connection in DFW is showing as 'delayed 10 minutes' from 1230 in SYD but that time has already passed.

UPDATE: QF7 departed at 1246.
 
Last edited:
Monday 10 July's QF1 (A388 VH-OQD) departed 64 minutes late from SYD at 1654 hours, arriving DXB at 0109, 54 minutes behind schedule.

However instead of spending an hour and three quarters in DXB, it did not depart until 0602 hours on 11 July meaning likely LHR arrival at 1025 hours, 210 minutes late. As 'the 10' (to use the amusing description preferred by one of the AFF aviators) is not due to depart until 1330 this afternoon London time, in theory it should not be adversely affected. The late arrival cuts down the available period for maintenance in London, given that upon arrival in MEL the aircraft is normally on very close to minimum turnaround to form 'the 9.'

Tuesday 11's QF122 (1525 hours mid afternoon ZQN - SYD, B738 ZK-ZQD that was in the sky at 1642) is likely to arrive at 1733, 53 minutes late.
 
Last edited:
QF10 on Tuesday 11 July is currently estimated to depart nearly 3 hours late due to QF1's late arrival (was diverted to LCA). How do I find out the reason for the delay (weather? mechanical issues? Something else?)? I'm keen to find out. If the QF10 delay is QF's fault and QF10 arrives at its destination (DXB, I presume) over 3 hours late I understand that they have to pay compensation.
 
QF10 on Tuesday 11 July is currently estimated to depart nearly 3 hours late due to QF1's late arrival (was diverted to LCA). How do I find out the reason for the delay (weather? mechanical issues? Something else?)? I'm keen to find out. If the QF10 delay is QF's fault and QF10 arrives at its destination (DXB, I presume) over 3 hours late I understand that they have to pay compensation.

If it went to Larnaca, then it would almost certainly be passenger medical.
 
So would that mean no compensation if QF10 (LHR-DXB) arrives over 3 hours late?

Some months ago (though not in identical circumstances) we had a discussion on AFF about whether EU compensation would be payable; one aviator disagreed with others so in the end it was indeterminate.

This otherwise quite extensive guide does not mention 'medical diversions' as an 'extraordinary circumstance' but my assumption is that QF would suggest that it was such an occasion and hence not offer compensation:

How to claim EU flight delay compensation|(EC) 261/2004 | This is Money

This source however suggests that a medical diversion would qualify as an 'extraordinary circumstance' and hence compensation would not be payable by an airline:

https://www.flightdelays.co.uk/extraordinary-circumstances

One might try to obtain a statement in writing from QF as to the exact cause of the delay, preferably from check in, lounge or gate staff, and then lodge a claim (keeping a copy) with QF and see what occurs. You could also ask at the gate as to whether the QF staff were distributing information about claiming EU compensation.

Independently, upon your return to your destination, you could contact staff at LNC airport to seek their understanding as to what exactly caused the delay. They might even email you the reason if you came into contact with a kind individual.

One other factor you could highlight is that prior to the diversion to Lanarca, Cyprus, QF1 was already hours late as it had not departed DXB until 0602 hours this morning. See my post number 5646 above. Note however that what was at that stage an expected arrival of 1025 hours in LHR would not have by itself meant a three hour plus delay to QF10, but since it shows evidence of an inbound delay that may be the airline's fault as defined in the EC regulation, it might be a point worth making.

UPDATE: QF1 departed LNC at 1158 hours. LHR predicted arrival has become later at around 1455, meaning that QF10 will be unable to depart much before 1640 hours - three hours and 10 minutes late, but once again, that estimate is reliant on everything going well and ATC giving clearance for a prompt departure at a busy time of the afternoon to an aircraft that ought have been off blocks a significant time previously if the timetable was being adhered to.

This will mean that the Wednesday evening 12 July 2255 hours MEL - DXB - LHR will depart late. Just how much will be unknown until DXB departure in many hours' time, but at least passengers who view AFF have more than 24 hours' warning of the delay.
 
Last edited:
Monday 10 July's QF12 departed JFK 66 minutes late at 1916, arriving LAX 55 late at 2155. QF12 departed LAX at 2332 hours, 72 minutes tardy with expected Wednesday 12 July's arrival at 0705 hours, 45 late in SYD.

The B744 on QF96 departed LAX at 0009 hours on Tuesday 11, 69 minutes late so it should arrive MEL at approximately 0812 hours, 42 minutes late on Wednesday 12. In contrast, QF94 departed bang on time and is predicted to be only five minutes late into MEL at 0700 at the terminal on Wednesday 12.

The BNE-bound B744, QF16 followed with pushback commencing at 0025 hours, 65 late and consequent Wednesday 12 arrival expected at 0705 hours, 55 minutes late.
 
Last edited:
QF10 on Tuesday 11 July is currently estimated to depart nearly 3 hours late due to QF1's late arrival (was diverted to LCA). How do I find out the reason for the delay (weather? mechanical issues? Something else?)? I'm keen to find out. If the QF10 delay is QF's fault and QF10 arrives at its destination (DXB, I presume) over 3 hours late I understand that they have to pay compensation.

Ive asked in the "ask the pilot" thread if another airport is A380 capable in Eastern Europe such as Bucharest's OTP rather than having to turn south and land in Cyprus LCA.
 
If it went to Larnaca, then it would almost certainly be passenger medical.

Assuming a passenger medical, would not LCA be unusual, given the flight would be tracking over central/northern Turkey?

Wouldn't ESB be closer in proximity and/or IST?
 

Thanks slinky123. The brief report (that fails to mention how QF1 had massively extended its stay in DXB so it was late before the LNC diversion) discusses a 'negative pregnancy test' and that may be so, but those who are at that stage of pregnancy ought not be flying.

This QF1 ended up arriving at LHR on Tuesday 11 July at 1447, 472 minutes late.

Tuesday 12 July's QF10 then departed at 1649 instead of 1330 hours (199 minutes late), arriving DXB at 0218 on 13 July, 163 minutes late.

On Wednesday 12 July, QF128, the overnight from HKG down to SYD (A380 VH-OQC) is arriving at 0742, 32 minutes late. At this stage, MEL arrival is predicted for 2300 hours tonight, 125 minutes late, meaning that it is unlikely tonight's QF9 will depart much before 0040 hours on Thursday 13 July.

QF2104 on Wednesday 12 (0705 hours SYD - CFS, Q200 VH-TQG) was still only taxiing at 0750.
 
Last edited:
.... discusses a 'negative pregnancy test' and that may be so, but those who are at that stage of pregnancy ought not be flying.

Well, if you aren't pregnant, then any pregnancy limitations won't be relevant....and if doing a pregnancy test, that would imply not knowing.
 
Last edited:
Assuming a passenger medical, would not LCA be unusual, given the flight would be tracking over central/northern Turkey?

Wouldn't ESB be closer in proximity and/or IST?

Closest airport is not relevant as this was not an aircraft emergency.
 
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

QF1582 (Wednesday 11 July HBA up to SYD, B717 VH-NXJ) was airborne at 0758 despite an 0700 departure time on a frosty morning in southern Tasmania. Arrival should be at about 0939 hours, 49 minutes late.
 
if pregnancy test is negative then can't be pregnant.

Possble scenario:

Woman becomes unwell with abdominal pain
Assessed by CSM
Asked by CSM - " are you pregnant?"
Patient says "don't think so but could be"
CSM assumes a pregnancy until proven otherwise (which is appropriate given the context)
Discusses with captain who discusses with ground aeromedical
Offloads the passenger at LCA to medics
News then permeates about a pregnant passenger but pregnancy test is negative.

Likely she was never pregnant in the first place
 
Last edited:

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