Melburnian1
Veteran Member
- Joined
- Jun 7, 2013
- Posts
- 25,256
The delayed QF93D (A388 VH-OQD) departed at 2012 this evening (Sat 24 October 2015) and is due at LAX at 1645, nine hours and 35 minutes late.
AFF Supporters can remove this and all advertisements
I departed LAX this morning to MIA. As we took off (0900), there was 1 QF A380 at TBIT, 1 747 at TBIT and 1 747 parked by the hangers.For the second consecutive day, QF93 has been late. This morning (Sunday 25 October) it departed MEL 64 behind at 1154, with arrival in LAX forecast at 0750 hours, 45 minutes late.
As always though, better that any faults be repaired on the ground rather than a problem detected once the plane is at XX000 metres.
Talking of QF747s, the normally punctual (like most of QF's relatively small number of international flights ex BNE) QF15 from BNE to LAX this morning was timetabled out at 1000 but at 1119 appears not to have yet departed. This will mean a LAX arrival at 0700 or later today local time and will delay the so-called 'tag' flight QF11 which with the northern hemisphere time change is scheduled as an 0820 departure to JFK.
UK returns to UTC from BST this week. US returns to standard time next weekend.With the northern hemisphere time change over the weekend, QF has slowed some of its Oz to LHR or back flights so that (in theory) should mean better timekeeping.
I did when QF shifted to DXB. 90-120 mins longer for DXB compared to SIN.I have not compared the new elapsed journey times between MEL and SYD, and LHR
cmon0005, yes it is and it's the second day in a row for this A330 flight.
Whatever the cause, QF35 did not depart from MEL until 1452 hours this afternoon - two hours and 32 minutes late. QF suggests it will be in SIN at 1950 tonight, picking up just seven minutes on the schedule. QF52 back to BNE ex the Lion City is highly likely to be delayed as it is due to depart at 2050 and is normally formed by QF35. Operating aircraft is A333 VH-QPI.
If it is an official codeshare and their luggage is booked through to the final (or next) destination, that should assist.
I have found that it can also depend on the number of connecting passengers. If your family member is the sole connecting passenger, holding a flight is probably unlikely because of the expense per minute to the (second) airline, but if there are say five or more, the chances of that increase.
It also might depend on how frequent flights of the codeshare partner are to the next destination. For instance, there are lots of flights from SIN to KUL or CGK, a good number to MNL but fewer to SGN.
There is no guarantee that luggage 'will make it' even if passengers manage to board the connecting flight.
May I ask to where the family member is travelling and on what airline? Is the scheduled time of departure 2005 or so?