agreed, I understand the code-share rules, but it doesn't allow us to build some of the crazy itineraries as seen on other carriers.

I just came across something interesting tonight. I was trying to build an itinerary from NYC to VPS (Ft. Walton Beach, FL) on NW... the lowest fare basis is K on NW

Here's the routing:
FROM-TO NYC-NW-CLE/DTT-NW-HOU/MEM-NW-VPS*

When I enter a basic EWR/VPS via MEM it says both segments say K9.

But for the same dates, when I try for EWR/DTW/MEM/VPS the MEM/VPS segment is K0.

I am taking this to mean that the load is light on the EWR/MEM side of things and they are looking to offer attractive fares to get me into MEM, but that the MEM/VPS segment is doing well.

I haven't tried it yet, but I will try EWR/DTW and then DTW/VPS and force the booking engine to put MEM in on its own... MEM is the only route that NW serves from VPS anyway.

Not exactly *amazing*, but this is the first time I that have actually seen how this operates, as opposed to just wondering how it worked...

EDIT: well, here's something really interesting... I went back to check out the idea listed above and the fare basis changed... it is no longer a K fare, now it is V.

[This message has been edited by EWR-COflyer (edited 02-10-2002).]