WN's CFO during a recent investors conference call made it known that WN
was "Very interested in doing something there (STL
)" , what this entails I don't know but a safe guess would be that they would add service to existing WN
markets that they currently do not offer "direct" service to from STL
Albany, Austin, Buffalo, Ft.Lauderdale, Hartford, Indianapolis, Jacksonville, LAX
, Manchester, Nashville, New Orleans, Islip/ Long Island, Norfolk, Oakland, Ontario, Orange County, Portland Ore, Raleigh, Reno, Sacramento, San Antonio, San Diego, San Jose, Seattle etc.
indeed has it's eyes toward expanding their presence at STL
then Airtran would probably want to steer clear of WN
, flying to existing FL
would not such as..
Atlanta, Boston, Bloomington, Akron, DFW
, Dayton, Denver, Flint, Fort Myers, Greensboro, Gulfport, Memphis, Miami, Milwaukee, Minneapolis, Moline, Newark, Laguardia, Pensacola, Philadelphia, Pittsburgh, Rochester, San Francisco, Washington National, Washington Dulles, West Palm Beach, Wichita.
Also Airtrans "possible" plans for STL
would also revolve around AA
's plans, and how much of a gap AA
However if you get WN
to add new routes from STL
to current WN
destinations that they do not serve nonstop from STL
(like what I listed previously), and if you can get Airtran and AA
to fill the gaps to places like Wichita and Laguardia then STL
will probably be better served than they previously were by a single dominant carrier.
Also carriers like CO
could upgrade RJ
flights to STL
from places like EWR
with 737s, same with DL
, NWA etc.
Also new airlines to STL
should be encouraged like Frontier (on the way), Alaska, B6