*A award flight blocked?
 

I am trying to redeem for an ANA reward from HKG-NRT/HND on Feb 12 (I am booked on the 11th as a backup, but actually need to travel on the 12th). On the ANA website, there's availability (on the partner search) for both economy and business:

NH1906 HKG-KIX 03:10-07:25
connecting to NH144 KIX-HND 08:35-09:45

I called Continental to see if they can book me on that flight, but the amazing thing was that the rep says he cannot even pull up the NH1906 flight - on either his award system or the regular revenue system - even after I provided exact flight details for him

The flight does show up on the ANA timetables as a weekly additional flight between HKG-KIX - is there any reason why Continental is unable to even see the flight?

The rep hinted that it might be a "special" flight to reposition aircraft given it's late flight time, but why would it be listed on the ANA timetable and be bookable on ANA's website? But he didn't seem too sure either.

I don't know, just thinking out loud, but one possible answer is that the Hong Kong flight may not be operated by a star alliance partner. Doesn't ANA use a regional partner for those legs?

This is a COmmon problem with CO. CO programs their flight number ranges for valid awards and we see this sort of thing for time to time -- where a flight number is outside what CO has programmed for the range of valid awards, and CO's tables of valid flights are not properly updated.

I've experienced it a COuple times, and we've seen many posts about it.

Unfortunately, CO's culture does not allow for them to make a mistake, there is no real mechanism within the company that a customer can reach to get this COrrected.

You probably should alert CO Insider, and he'll let the correct folks know, thank you for alerting him to this, and probably blame someone other than CO (e.g., NH for not notifying them or something). ;)

CO does that sometimes.
and it is very hard for them to change or do anything.
good luck

Any documentation on this supposed range?

Nothing public. It's in their system, and it's likely the issue here.