Cory6188 From United States of America, joined Feb 2004, 2686 posts, RR: 6 Reply 1, posted (7 years 1 month 2 weeks 4 days 16 hours ago) and read 2131 times:
Where the heck is CO going to come up with additional flight numbers for this? Aren't they already nearly maxxed out up to something like 9800?
AussieItaliano From United Kingdom, joined Jan 2005, 441 posts, RR: 0 Reply 2, posted (7 years 1 month 2 weeks 4 days 13 hours ago) and read 2014 times:
Exactly! That's what I find funny about this press release. It tries to paint this as being a new thing, when it's really not even as close as these two carriers once were.
During the age of Bi-lateral Transatlantic Alliances (NW-KL, UA-LH, proposed AA-BA), CO and AZ were very close partners. I think their code sharing began in 1994, and I remember that for their joint service between EWR and FCO (CO 40 & 41, AZ 640 & 641), they painted CO's livery on one side of the DC10, and AZ's livery on the other side. They also had F/A's from both airlines working the flight.
I don't know how much closer you can get in terms of joint service. That's what got AZ to begin serving EWR in addition to JFK.
USPIT10L From United States of America, joined Mar 2006, 3266 posts, RR: 8 Reply 3, posted (7 years 1 month 2 weeks 4 days 11 hours ago) and read 1953 times:
Quoting AussieItaliano (Reply 2): During the age of Bi-lateral Transatlantic Alliances (NW-KL, UA-LH, proposed AA-BA), CO and AZ were very close partners. I think their code sharing began in 1994, and I remember that for their joint service between EWR and FCO (CO 40 & 41, AZ 640 & 641), they painted CO's livery on one side of the DC10, and AZ's livery on the other side. They also had F/A's from both airlines working the flight.
The arrangement was done by the end of 1998, mostly because of CO's alliance with NW. AZ's aborted tie-up with KL was in 2000. Great to see the two of them cooperating so closely again!
WorldTraveler From , joined Dec 1969, posts, RR: Reply 4, posted (7 years 1 month 2 weeks 4 days 10 hours ago) and read 1920 times:
the question should be why CO and AZ are not codesharing as Skyteam partners already and the answer is because there is a fair amount of protectionism in place in Skyteam. Not sure if there were limits on CO coding on AZ because of DL's stronger relationship w/ AZ but DL does not presently codeshare on much of KLM, something that NW and CO did extensively before those 3 joined Skyteam. And NW does not largely code on AF operated flights. And DL does not code on NW flights beyond NRT. Not sure what CO or NW does on KE operated flights since none of the US Skyteam members fly to S. Korea other than NW's service from NRT.
anyone else is welcome to post any non-codesharing relationships between Skyteam members.
USPIT10L From United States of America, joined Mar 2006, 3266 posts, RR: 8 Reply 5, posted (7 years 1 month 2 weeks 4 days 10 hours ago) and read 1909 times:
Quoting WorldTraveler (Reply 4): Not sure what CO or NW does on KE operated flights since none of the US Skyteam members fly to S. Korea other than NW's service from NRT.
NW and CO do not codeshare with KE, but KE is a member of both airlines' frequent flyer programs. KE's route network is included in every NW WorldTraveler magazine.
Sponsor Message: 
From United States of America, joined Jul 2005, 609 posts, 
From United Kingdom, joined Jan 2005, 441 posts, 
Printer friendly format 
