JetBlue and Lufthansa want to start a code share, how does that effect CO in the *A?
 

There is a link to the Jetblue forum--> http://www.flyertalk.com/forum/jetbl...ode-share.html

Or read the USAToday story, my post concerns the question at the end, what is the reaction by the *A partners, that now includes or will include us.

ORIGINAL POST: Lufthansa and JetBlue are expected to file regulatory approval for a codeshare alliance that would let the carriers put their codes on and sell seats on each other’s flights, the Financial Times reports. The Times, which cites "people familiar with the matter," says the carriers could file their request with the U.S. Department of Transportation as early as today. The New York Times also reports on the deal, though it also cites "people with knowledge of the agreement."

The Financial Times writes that "by marketing JetBlue’s flights as its own, Lufthansa would broaden its footprint at John F Kennedy International Airport" by giving its passengers connecting options on JetBlue flights to more than 50 destinations in North America and the Caribbean. For JetBlue, the tie-up would allow JetBlue to sell passengers tickets with connections to Lufthansa's trans-Atlantic flights via New York JFK – and possibly other airports, such as Boston Logan, Orlando and Washington Dulles. The New York Times says the pact would "allow JetBlue to market flights to European destinations for the first time."

Speaking to the New York Timesearlier today, Lufthansa spokesman Boris Ogursky says the two carriers are "evaluating the possibility of a customer-oriented cooperation," though he declined to comment further.

One question yet to be answered: How will Lufthansa's Star Alliance partners United, Continental and US Airways feel about Lufthansa's request to partner with a U.S. low-cost rival?

This was pretty much known it would happen, I'd expect B6 to be a *A member next year in fact, LH owns the max legal limits on them to my knowledge.

This one is interesting. I would have thought that a big part of the draw for CO to join Star would be that they are so strong in NYC, so they would get a huge amount of traffic coming through them. In Skyteam, CO/DL both offer huge service in NYC area.

With LH code sharing with B6, I would have thought that CO would be livid.

well with BOS I dont see much for CO to crow about.

As for NY well B6 doesnt have RJs on the routes it flys, so If I was going to fly 2 Carriers and CO served my destination with an RJ or Q , hello B6

Now although it did mention Florida, well doesnt LH pretty much have that already covered with its non-stops? and if anything shouldnt UA & US be the ones complaining more then CO, after all instead of flying say FRA-PHL-FLL , a person can now go FRA-JFK-FLL LH/B6

Then maybe its LH that should be complaining as now with CO a person can fly to EWR and then to alot of the European cities which till now then needed to grab a LH flight to get to. Or why fly BUF-PHL-FRA-MXP when you can now go BUF-EWR-MXP. (yes AZ flys to MXP as does DL etc but no *A Carrier till CO comes on board flys non-stop from the US

Then CO left JFK so what should LH do leave JFK as well, more people chose JFK over EWR. Just as more people chose LHR over LGW if given a choice

In the end it will all balance out, and produce more rev for all the Carriers.

Didn't the Star Alliance anti-trust immunity include trans-Atlantic revenue sharing? If so, how could this possible pass anti-trust?

Ladies and Gentlemen, I welcome you to LufthansaBlue.

Just Kidding :D

---
that would be cool though. It might also explain JetBlue's freakishly big terminal, and the connection they built to the old T6. Anyone else thinking Star Alliance Megahub? If not that, then at least a Lufthy hub at JFK?

Incorrect. A foreign entity can control up to 49% of an airline with no more than 25% of voting shares. LH owns 19% of B6.

What does that have to do with anything?

T5 is not connected to T6 at JFK and neither have a FIS. In addition LH owns 25% of T1. Neither one is going to move.

--I did in fact mean to say "built so that they could be connected". But I guess you are right when it comes to Lufthansa's share of T1, unless they plan on a huge expansion in NY.

It actually is not all that large for the operations that jetBlue has at JFK. They have 25 gates. They operate ~250 flights a day. Putting 10/gate/day through doesn't leave a whole lot of slack for when things go wrong.
T6 is essentially useless. If that space gets used for anything I'd expect it to be razed and rebuilt from scratch. And there is no way that LH moves from T1 right now.

As for the impact on CO, minimal, IMO. There are more than enough people out there that LH is connecting through NYC to various destinations and they have significant service at both airports. There was no way that LH was ever going to move wholesale to EWR and route everything through there so this isn't all that big a deal, IMO.

CO makes a good fit in *A because of its Latin routes.

*A has a big, gaping hole in Latin America, and CO fills it quite nicely. The two Mexican carriers that could fill this hole are in Oneworld or SkyTeam. Smaller, non-alliance carriers like Taca have hubs in places that likely won't support long-haul traffic needed for connections (anyone for FRA-SAL or NRT-SAL?). And a carrier like TAM has a hub that can be significantly out-of-the-way for many connections.

So CO is a very good fit for *A.

As for the EWR hub, while bringing CO's customers to the alliance will benefit the alliance as a whole, most destinations CO offers out of EWR are presently served by the alliance.

I don't think LH is connecting much traffic in NYC at the moment. People flying LH to major markets are probably flying LH to that market (they serve most every major U.S. city). People flying LH and connecting to secondary markets are likely routing via ORD, IAD, DEN, SFO, LAX, PHL or CLT rather than NYC.

But aside from FTers looking to build in extra connections, flying LH to JFK and connecting onwards probably doesn't make a whole lot of sense at the moment.

especially if CO Elites wil be able to grab a E+ seat from get go

If they will be able to,UA flys to FRA & MUC from IAD and thats how I would fly. XYZ-IAD-FRA or MUC and then LH onward or whomever

Back to JFK most *A Carriers go into JFK, I think only SAS has a presence at EWR and not JFK . Most are only at JFK or a couple also fly into EWR. So unless every *A Carrier is gonna switch to EWR whats the big deal.

LH is terrible in Y , I had less leg room then when on CO. OK the seats themselves were padded better but that was it

Craz,

SK, SQ, LH, LO, AC, UA, US, and future member AI all fly into EWR -- nothing to sneeze at.

In any event, the B6/LH linkup is a nonissue. By design, it won't deprive CO et. al. of any premium ticket sales.

well drop UA and US as I thought we were talking about Intl carriers at least I was.

TK,OS,LX,SA,MS,CA,NH,OZ,TG (used to) go Only to JFK

LH,SQ,LO go to both JFK & EWR

TP,AC,SK go only into EWR (although AC does go into LGA)

also a number of UAs partners that arent *A members also only fly into JFK

Correct. Because there are no connection options today. Adding those options is a good thing for customers and LH customers are about to have two options - EWR on CO or JFK on B6. That's a great thing for them.

It does for the cities that they are starting with. Cities like PBI, AUS and SJU are all just fine for using JFK as a connection point rather than the existing UA/US options.