Since when the NVA on the itinerary has a year printed? On all my itineraries I have on hand none of them has a year in the NVA field...

The only NVA field I saw with year on it is the fare conditions, but that's always qualified with another clause limiting the validity from the first segment day, but of course the earlier one prevail

Sorry I'm a bit lost.... So CX offered to honor the impossible 2019 booking? or allow you to move it to an earlier day? From an earlier post seems they only willing to refund the immaterial fare difference to you, if any at all as it's an ex-TPE D fare ticket

Previously CX reservation also tried to do something impossible for me: Hold an N fare seat on a flight with no such fare offered. They can do so but upon ticket issuance the system showed an error and they simply can't move forward with the issuance... So while I still have some doubt on what the MPC agent said that's not completely impossible....

If you have a number of ex-TPE tickets to shuffle around I'd recommend you to move one to secure the high season seat first... And then I'd recommend you to ask for some AM for redeeming an one-way ticket instead of getting refund... As least you can close your itinerary gap by redeeming one one-way ticket during non-peak season

Depends on display setting, but usually it doesn't. If you look at the e-ticket data in the GDS, sometimes you may see nothing, sometimes you may see one digit ("8" for 2018), sometimes you see two digits ("18"). In any case, it is implied. You can easily get the year by cross-reference with the date of the first flight.

That's a whole different thing. A class, or a Reservation Booking Designator (RBD), is available, does that mean that there's a fare associated with your itinerary. It may be that the N class, if combined with some other segments, can be priced. It may be that the N fare was taken away. There are various reasons, but this was not an IT problem and at most was an agent who didn't check the fares filed before making the booking for you.

I believe the #1 question was how could CX change the booking when the change would clearly beyond the ticket expiration.

CX IT strike again?

Hong Kong Customs, like other customs agencies in the wolrd, is in charge of most customs responsibilities in Hong Kong, as well as some weird responsibilities. Funny enough, consumer protection is one of the responsibilities of Hong Kong Customs.

Case-in-point: HX managers have been arrested by Hong Kong Customs before because of some problematic bookings.

If what you have said is true, then that means a ticket can last almost 2 years?

This is what I am not sure.

As I said, it can happen. I've seen it happen. The flight is beyond NVA, but it got revalidated. This is especially common with IRROPs, but it can happen under normal scenario, too. I've even had a manually priced ticket (because it involves many AA domestic add-ons) issued by TPECX that had a mismatch between my itinerary and the NVA / NVB range. My return journey, at the time of original issuance, was already beyond NVA, because TPECX applied an incorrect fare basis. Even a travel agent may sometimes be able to validate a coupon to a flight outside of NVA / NVB range. Of course, in this case, the travel agent will receive a debit memo afterwards.



I will admit I don't know very well how the system works in HKSAR, but after reading https://www.customs.gov.hk/tc/consum...ion/index.html and ???? - ????? - ??????? - ??????????????????????????????<br>???????????????? ???? (English version available by clicking "English"), I hardly think this is something HK Customs would handle.

The ticket's validity is still 1 year, but the first day of validity does not need to start on the date of issuance. You can buy a ticket that has 1-year validity now but have the first segment in Sep. 2019. You can either leave the return journey OPEN or book a placeholder flight and make date change afterwards (assuming a flexible ticket or airline specifically allows this because of technical difficulties to book beyond 11 or 12 months). You can then use the return journey in Sep. 2020. That's what many people do with their RTW tickets.

Actually it didn't show the year but my assistant was told verbally by an agent that it was 2019.

No - they are saying I have to refund. They won't even guarantee me getting on the flight on the new date of booking (1 Feb 2019) even though I have a confirmed ticket.

That's a great idea!

The latest agent said that it was combination of "something the system shouldn't have allowed" and an agent not reading the ticket rules in detail enough