Search results

All Y+ seats are available to staff travel. They can usually only pick a seat about 30 minutes to an hour from departure anyway, so it's unlikely they would really impact commercial pax.

You can ticket this as separate tickets one booking for through-check. In fact, you need to, as you wouldn't be able to collect and recheck baggage in time at SCL otherwise.

SYD QF SCL IB MAD and SYD QF SCL BA LHR both have perfect connections at SCL currently. It's actually quite a useful involuntary reroute option at the moment.

It is not the ticketing carrier's responsibility to notify a passenger for a disruption on another carrier. That's QR's responsibility.

QF, JL, AA, BA, FJ, AY, AS are fine. They won't cancel that quickly. QR, AT, IB, MH, CX can cancel quite quickly, as quickly as 2 hours.

If you're QPPS/TPPS and HLO... fine, I'd personally let it slide. If you're checking a bag, better to be safe than sorry as it gets messy if your bag has been through checked and you've missed your connection.

In Star Alliance you're unprotected, whether it's same PNR or not. The corporate TA is doing the right thing here. Similarly, I would refuse ticketing on a 1h10m connection at LHR T2 as well.

The current routing up the middle of India and over north of Iran means there's a payload restriction. Routing via SIN removes that restriction.

Skyscanner is not accurate for a lot of things for a start. The following are still empty on QR989/18FEB... 1A, 2B/D/G, 3E/F, 4D/G, 5E/F, 6D/G, 7E/F, 8A/D/G, 9E/F, 10D/G/K

For clarity, yes, there is a website bug where if you start in NZ, it seems to treat it as Australia as the country of origin which is obviously incorrect. However, more generally, once you return to your country of origin, you can still add segments but they must be purely domestic. So for...

Correct. If you want to be bending rules or doing anything unusual or uncommon you pretty much need a clued up TA to execute it for you now unless you want to spend a lot of time banging your head on walls with useless contact centre staff.

It won't be fixed. It was a deliberate change to the security levels between QR and QF. If you happen to use a TA who knows how to push PNRs to the QF app, then they can push it to your QF app.

Ah yes, AY does. JL don't hard enforce it in the system. It's only soft enforced by the queue comber. QF/AY are literally 'computer says no and no is no'.

QF hard enforces the boarding group. I don't think anyone else in oneworld does.

Most codeshares can be fine - if you have a good agent that knows what they're doing with them. If not, then it's better to avoid them.

They do work, but you have to make sure that it's added into the correct one of the three PNRs. I would say on average that it's beyond the capability of 99% of passengers and 99% of travel agents.

I strongly advise to not book the VA wet leases in particular. There's technical issues galore with them. There can be up to 3 PNRs that exist for a single passenger to be booked on just one VA wet lease flight. Eg. as the selling agent, I sell one pax on VA1. This creates a PNR in Amadeus...

If it's a QR blockspace codeshare operated by AY, AY has a different record locator. That's a Sabre "feature" and affects all Sabre carriers. Sabre does not deal with simultaneous changes very well hence this lockout exists.

Tomorrow is still under the old seating rules.

Book yourself as another passenger rather than yourself. That is, make a booking for "another passenger" and put your own name in. The other alternate is ask your friendly travel agent if you have a good relationship with one.