Oct 27 Schedule Extension - Welcome Back Super Short Haul
#16
Join Date: Sep 2015
Posts: 366
DAY maybe also in risk of closure, but I wonder if WN eventually gets into CVG. I think RIC, DSM and GRR maybe weak currrently, but not weak enough that WN can't sustain it. They are also not as nearby to other WN stations.
Last edited by beyondhere; Oct 27, 2015 at 3:01 pm
#17
Join Date: Oct 2005
Location: ORD, MDW or MKE
Programs: American and Southwest. Hilton and Marriott hotels primarily.
Posts: 6,459
I doubt that WN had many business travelers MDW-DSM. The times were atrocious. I finally stopped even checking DSM and just fly to Omaha.
#18
Join Date: Sep 2015
Posts: 366
If WN is truly comfortable running short-hauls without them capturing any O&D (e.g. GSP-ATL's likely fate), a RIC-BWI should be important for consideration.
The Richmond area is growing and it's between the Raleigh and DC markets - which will benefit it long term. RIC is over 100 miles from both RDU and DCA/IAD/BWI, so it's location won't adversely impact it either from competing for service, unlike CAK's relation to CLE.
By WN offering a RIC-BWI, WN could sell a lot of Northeast connections to BOS, PVD, MHT, PWM, BDL, along with upstate NY, Ohio and Michigan, and transcons from BWI. Probably it wouldn't be much a backtrack really in any direction, much like AA offering RDU-CLT. I think it'd complement the RIC-ATL service.
A PHL-BWI might also open PHL for more connections, but WN might prefer running more mid to long hauls from PHL, and using MDW for connections.
The Richmond area is growing and it's between the Raleigh and DC markets - which will benefit it long term. RIC is over 100 miles from both RDU and DCA/IAD/BWI, so it's location won't adversely impact it either from competing for service, unlike CAK's relation to CLE.
By WN offering a RIC-BWI, WN could sell a lot of Northeast connections to BOS, PVD, MHT, PWM, BDL, along with upstate NY, Ohio and Michigan, and transcons from BWI. Probably it wouldn't be much a backtrack really in any direction, much like AA offering RDU-CLT. I think it'd complement the RIC-ATL service.
A PHL-BWI might also open PHL for more connections, but WN might prefer running more mid to long hauls from PHL, and using MDW for connections.
#19
Join Date: Aug 2010
Programs: MR LT Titanium, SPG LT Plat & Plat 100, SWA A+ & CP
Posts: 1,093
I'd like to see a BWI <-> RIC as it would make RIC accessible from most stations. However, ORF is reasonably close to RIC so I do not think I see that happening.
It's interesting that they're opening up short-hauls again. I would not mind reopening all those MHT, BOS, and PVD flights to Philly again. I miss those. They were always packed but I think most pax were through pax.
It's interesting that they're opening up short-hauls again. I would not mind reopening all those MHT, BOS, and PVD flights to Philly again. I miss those. They were always packed but I think most pax were through pax.
#20
Join Date: Sep 2015
Posts: 366
It will be interesting to see how Southwest deals with Richmond. So far, it's been underwhelming but not totally bleak. Richmond is a growing region with an industry focus. It's desirable that it has Amtrak, and driveable distance between DC and Raleigh's RTP area. I think the region will continue to grow.
The Virginia Beach-Norfolk-Newport News market is larger by Census figures, but RIC has more air service than ORF in both passengers and departures. It also maintains service to BOS while ORF doesn't, which gives me some inclination that Richmond might be stronger for business travel.
There are likely not a whole lot of many markets in the Eastern US where Southwest can realistically grow, with the exception of international routes out of it's hubs.
Probably Southwest's best bet is longer flights out of PHL to large markets or low frequency markets from AA out of PHL. I'm hoping WN will restore HOU-PHL. I'm not sure if the HOU-EWR cancellation works in that favor or not.
Last edited by beyondhere; Oct 28, 2015 at 9:23 am
#21
FlyerTalk Evangelist
Join Date: Jan 2014
Location: San Diego, CA
Programs: GE, Marriott Platinum
Posts: 15,507
GRR-MDW apparently only takes 16 minutes, not including taxi, taking off and landing. Can the 737 handle flying many short flights like that? I remembering hearing that Hawaiian Airlines had to go with 717s for inter-island flights because of that kind of concern.
#22
Join Date: Jan 2010
Location: Houston (HOU/IAH)
Programs: WN, UA, DL, AA, Chase UR, Amex MR
Posts: 2,267
GRR-MDW apparently only takes 16 minutes, not including taxi, taking off and landing. Can the 737 handle flying many short flights like that? I remembering hearing that Hawaiian Airlines had to go with 717s for inter-island flights because of that kind of concern.
#23
Join Date: May 2006
Location: TUS/PDX
Programs: WN CP/A-List, AS MVPG75K
Posts: 5,798
The reason HA went with the 717 as opposed to the 737NGs had to do with short ground time and the amount of time the engines have to cool at cruise. Many of the Hawaiian airports have short(ish) runways that require higher takeoff thrust and higher cruise power, since the flights cruise in the low 20s or even teens.
AQ ran them on some intra-island flights to build hours and landings for new NG pilots and they had issues with delays even with increased ground time.
#24
Join Date: Jan 2010
Location: SFO
Posts: 1,753
I am so happy about MDW-FNT. I live in San Francisco and my family is in Michigan/Flint. The only reasonably priced flights from the west coast were of course to DTW, and by reasonably priced I mean only about $500 r/t (or $650 n/s on Delta). Seriously SFO/OAK -DTW is one of the most expensive routs I fly regularly. So anyways, it's now technaly possible to fly to FNT and GRR from the west coast, with the previous routes to BWI or ATL the flights were way to long, or you could not connect.
If the price is right, the drive from GRR to just about anywhere in Michigan is fast and easy. Even for me, if it's faster getting a rental car and getting on the road the extra 20 minute drive to Flint would be worth it.
GRR also is close to Lansing which is losing its flights on Sun Country to BWI as well. I think DL picked it back up though.
As for FNT, it's actually closer to Oakland County and Auburn Hills than DTW. You could drive some business traffic there. You just have to market it the right way.
Edit**************
So I checked all 3 stations for the middle of April, nothing less than $600. Ouch. But at least I have 3 expensive stations to choose from. To compare. AA will get me to DTW for around $400, and DL for job st over $500.
If the price is right, the drive from GRR to just about anywhere in Michigan is fast and easy. Even for me, if it's faster getting a rental car and getting on the road the extra 20 minute drive to Flint would be worth it.
GRR also is close to Lansing which is losing its flights on Sun Country to BWI as well. I think DL picked it back up though.
As for FNT, it's actually closer to Oakland County and Auburn Hills than DTW. You could drive some business traffic there. You just have to market it the right way.
Edit**************
So I checked all 3 stations for the middle of April, nothing less than $600. Ouch. But at least I have 3 expensive stations to choose from. To compare. AA will get me to DTW for around $400, and DL for job st over $500.
Last edited by returnoftheyeti; Oct 28, 2015 at 9:03 pm
#25
Join Date: Apr 2004
Location: DCA/IAD
Programs: AA Gold, Amex Plat
Posts: 4,007
If WN is truly comfortable running short-hauls without them capturing any O&D (e.g. GSP-ATL's likely fate), a RIC-BWI should be important for consideration.
The Richmond area is growing and it's between the Raleigh and DC markets - which will benefit it long term. RIC is over 100 miles from both RDU and DCA/IAD/BWI, so it's location won't adversely impact it either from competing for service, unlike CAK's relation to CLE.
By WN offering a RIC-BWI, WN could sell a lot of Northeast connections to BOS, PVD, MHT, PWM, BDL, along with upstate NY, Ohio and Michigan, and transcons from BWI. Probably it wouldn't be much a backtrack really in any direction, much like AA offering RDU-CLT. I think it'd complement the RIC-ATL service.
The Richmond area is growing and it's between the Raleigh and DC markets - which will benefit it long term. RIC is over 100 miles from both RDU and DCA/IAD/BWI, so it's location won't adversely impact it either from competing for service, unlike CAK's relation to CLE.
By WN offering a RIC-BWI, WN could sell a lot of Northeast connections to BOS, PVD, MHT, PWM, BDL, along with upstate NY, Ohio and Michigan, and transcons from BWI. Probably it wouldn't be much a backtrack really in any direction, much like AA offering RDU-CLT. I think it'd complement the RIC-ATL service.
I like the Southwest product and do fly them occasionally, but 3 flights a day, to ATL only, doesn't hold a candle to the domestic connectivity we get on AA/UA/DL. DL has 8-10 daily flights, all MD80 or 757, from RIC-ATL, and from what I know anecdotally they've won the business of many frequent RIC-based flyers who were loyal to AirTran 5 years ago. Southwest hasn't done much to grow their brand here, let alone their number of flights, so it's no wonder they're cutting the RIC-MCO nonstop.
RIC-BWI wouldn't add any value because it'd be 99% connecting traffic. UA thru IAD/EWR and AA thru PHL already provide frequent one-stop service to second-tier cities in New England, upstate NY, etc.
What we really need in this market is more nonstops to cities Richmonders actually want to fly to, especially points west. STL or DEN would be logical for Southwest. There are strong rumors in the Richmond business community that we will be getting a nonstop from RIC-DEN in 2016, but I'm not holding my breath for Southwest to start it. United is the more likely candidate, based on the chatter I've heard.
Despite the frustration many of us in RIC have felt with Southwest, I would imagine ORF might be first to go. One advantage RIC and many of the smaller ex-AirTran stations have is that they are allowed to use contracted ramp and ops agents. ORF is down to 5 flights a day or so, and since it opened before 2009, the ironclad union contracts force Southwest to use their own, much higher paid, employees there. Plus, the Hampton Roads region has had more economic struggles than the Richmond region in the last few years because of decreases in government defense spending.
#27
Join Date: Jun 2005
Posts: 538
next round of station closings
It seems pretty clear that southwest is giving it a final try at some Airtran stations before deciding whether or not to close shop. Grand Rapids, Flint, Des Moines, Witchita, Akron/Canton are on the brink of closure. And even though Greenville Spartanburg was a WN station, it is also on the brink. It appears SW is testing whether rejiggering the link and connection opportunities to these stations can make them viable. But would look for most of these stations to close in 2016.
#28
Join Date: Sep 2015
Posts: 366
I had a look at both RIC-MCO and ORF-MCO. According to Q1 2015, RIC-MCO is a larger market. WN was dominating both markets in market-share as well, but WN was getting lower fares on RIC-MCO relative to ORF-MCO.
My guess is that because B6 was on RIC-MCO nonstop as well, it triggered more competition, and probably the legacy carriers were discounting one-stops even more. And/Or, there is some higher yielding potentially business traffic that Southwest gets on ORF-MCO. B6 runs a daily nonstop on RIC-MCO but on a smaller aircraft.
Southwest will be cutting RIC-MCO and other inherited AirTran MCO routes, but it will be soon on EWR-MCO.
On EWR-MCO, I doubt Southwest will buy TV air time on the NYC stations like it does in cities like Baltimore, and as Southwest doesn't participate on third party sites, it's nonstop might not be visible to the EWR catchment area for those not accustomed to check southwest.com. It will be interesting to see if this will prove successful or not, when those close to EWR might stick with UA and B6, and others further south like the park and walk to gate experience of airports like TTN and ACY.
RIC-BWI wouldn't add any value because it'd be 99% connecting traffic. UA thru IAD/EWR and AA thru PHL already provide frequent one-stop service to second-tier cities in New England, upstate NY, etc.
What we really need in this market is more nonstops to cities Richmonders actually want to fly to, especially points west. STL or DEN would be logical for Southwest. There are strong rumors in the Richmond business community that we will be getting a nonstop from RIC-DEN in 2016, but I'm not holding my breath for Southwest to start it. United is the more likely candidate, based on the chatter I've heard.
Despite the frustration many of us in RIC have felt with Southwest, I would imagine ORF might be first to go. One advantage RIC and many of the smaller ex-AirTran stations have is that they are allowed to use contracted ramp and ops agents. ORF is down to 5 flights a day or so, and since it opened before 2009, the ironclad union contracts force Southwest to use their own, much higher paid, employees there. Plus, the Hampton Roads region has had more economic struggles than the Richmond region in the last few years because of decreases in government defense spending.
Southwest might be tolerant with some routes being 99% connecting traffic, or atleast with the resumption of IND-MDW. I can bet for sure that IND will not be cut, unlike GSP and FNT, etc.
I agree that RIC-STL and RIC-DEN could be good choices. I just think a smaller step towards more service would be RIC-BWI maybe at 3x daily first. It would use less aircraft utilization and could be a good way to provide access to markets in all directions.
It's too bad that GSP-BWI is slated to being cut. I remember just last year, Southwest was doing it half-heartedly with a 1x daily evening schedule which was terrible to attract any business traffic. Southwest might be trying to stay on CLT-BWI but sabotaged GSP-BWI in the process to lure it's customers to try to use CLT-BWI. CLT-BWI has a limited 2x daily schedule.
In some ways, I think restoring BWI-EWR might not be a bad idea if some of the South markets get a 1-stop access to NYC region via BWI, and NYC region customers get South markets and Carribean flights via connection, but it's too late I guess as this short-haul resumption seems to be a change of strategy from a strategy where it was originally cut outright.
My guess is that because B6 was on RIC-MCO nonstop as well, it triggered more competition, and probably the legacy carriers were discounting one-stops even more. And/Or, there is some higher yielding potentially business traffic that Southwest gets on ORF-MCO. B6 runs a daily nonstop on RIC-MCO but on a smaller aircraft.
Southwest will be cutting RIC-MCO and other inherited AirTran MCO routes, but it will be soon on EWR-MCO.
On EWR-MCO, I doubt Southwest will buy TV air time on the NYC stations like it does in cities like Baltimore, and as Southwest doesn't participate on third party sites, it's nonstop might not be visible to the EWR catchment area for those not accustomed to check southwest.com. It will be interesting to see if this will prove successful or not, when those close to EWR might stick with UA and B6, and others further south like the park and walk to gate experience of airports like TTN and ACY.
RIC-BWI wouldn't add any value because it'd be 99% connecting traffic. UA thru IAD/EWR and AA thru PHL already provide frequent one-stop service to second-tier cities in New England, upstate NY, etc.
What we really need in this market is more nonstops to cities Richmonders actually want to fly to, especially points west. STL or DEN would be logical for Southwest. There are strong rumors in the Richmond business community that we will be getting a nonstop from RIC-DEN in 2016, but I'm not holding my breath for Southwest to start it. United is the more likely candidate, based on the chatter I've heard.
Despite the frustration many of us in RIC have felt with Southwest, I would imagine ORF might be first to go. One advantage RIC and many of the smaller ex-AirTran stations have is that they are allowed to use contracted ramp and ops agents. ORF is down to 5 flights a day or so, and since it opened before 2009, the ironclad union contracts force Southwest to use their own, much higher paid, employees there. Plus, the Hampton Roads region has had more economic struggles than the Richmond region in the last few years because of decreases in government defense spending.
I agree that RIC-STL and RIC-DEN could be good choices. I just think a smaller step towards more service would be RIC-BWI maybe at 3x daily first. It would use less aircraft utilization and could be a good way to provide access to markets in all directions.
It's too bad that GSP-BWI is slated to being cut. I remember just last year, Southwest was doing it half-heartedly with a 1x daily evening schedule which was terrible to attract any business traffic. Southwest might be trying to stay on CLT-BWI but sabotaged GSP-BWI in the process to lure it's customers to try to use CLT-BWI. CLT-BWI has a limited 2x daily schedule.
In some ways, I think restoring BWI-EWR might not be a bad idea if some of the South markets get a 1-stop access to NYC region via BWI, and NYC region customers get South markets and Carribean flights via connection, but it's too late I guess as this short-haul resumption seems to be a change of strategy from a strategy where it was originally cut outright.
#29
FlyerTalk Evangelist
Join Date: Nov 2005
Location: Phoenix, AZ
Programs: AA Gold AAdvantage Elite, Rapids Reward
Posts: 38,318
It seems pretty clear that southwest is giving it a final try at some Airtran stations before deciding whether or not to close shop. Grand Rapids, Flint, Des Moines, Witchita, Akron/Canton are on the brink of closure. And even though Greenville Spartanburg was a WN station, it is also on the brink. It appears SW is testing whether rejiggering the link and connection opportunities to these stations can make them viable. But would look for most of these stations to close in 2016.
#30
Join Date: Sep 2015
Posts: 366
B6 is adding a second daily RIC-MCO flight, likely to replace some capacity lost from WN's deletion of RIC-MCO. B6 is running E190s on both flights, however, which might be the right aircraft capturing some business travel and leisure travel.
Maybe Central VA is cut-off territory where maybe some people are more likely to drive down to Disney/Universal, than from points north of Washington region, where it will take closer to 2 full days of car drive to get down to MCO. North of Baltimore/DC, there maybe greater volume to fly down.
RDU-MCO seems like more an outlier however to that theory, as Southwest maintains 3x daily on it on larger aircraft, and DL has 3x daily as well. I don't think either WN or DL run as many connections if at all on RDU-MCO, like ATL-MCO gets.
Maybe Central VA is cut-off territory where maybe some people are more likely to drive down to Disney/Universal, than from points north of Washington region, where it will take closer to 2 full days of car drive to get down to MCO. North of Baltimore/DC, there maybe greater volume to fly down.
RDU-MCO seems like more an outlier however to that theory, as Southwest maintains 3x daily on it on larger aircraft, and DL has 3x daily as well. I don't think either WN or DL run as many connections if at all on RDU-MCO, like ATL-MCO gets.