Risks when using a non-published route
Dec 21, 2019 | 9:15 pm
#1
Original Poster
Join Date: Jul 2009
Posts: 155
Risks when using a non-published route
Traveling PLS-MCI in July. Southwest publishes routes on Saturdays and Sundays with at least a 2:10 layover. I will travel on Thursday. If I book PLS-FLL and separately book FLL-HOU-MCI with a layover longer than 2:10 in FLL, am I at risk for anything besides a missed connection that would be my fault, or bags not checked all the way through? Anything else I'm not considering?
Dec 21, 2019 | 9:59 pm
#2
Join Date: May 2002
Programs: WN F9 HA UA AA IHG HH MR
Posts: 3,305
Traveling PLS-MCI in July. Southwest publishes routes on Saturdays and Sundays with at least a 2:10 layover. I will travel on Thursday. If I book PLS-FLL and separately book FLL-HOU-MCI with a layover longer than 2:10 in FLL, am I at risk for anything besides a missed connection that would be my fault, or bags not checked all the way through? Anything else I'm not considering?
You can book this using Multi-City on one PNR, looks like 2+45 at FLL. That would protect your onward connections.
Dec 22, 2019 | 7:43 am
#4
Original Poster
Join Date: Jul 2009
Posts: 155
Dec 22, 2019 | 2:36 pm
#5
FlyerTalk Evangelist
Join Date: Jul 2011
Location: RNO
Programs: AA/DL/UA
Posts: 11,630
Try calling them. Worst case scenario is they give you the same answer "sorry, can't be done".
Dec 22, 2019 | 3:28 pm
#6
Original Poster
Join Date: Jul 2009
Posts: 155
Welcome to Southwest IT where they calculate schedules and fares for most city pairs, plop it in a database and just leave it there, instead of scheduling and pricing on the fly.
Try calling them. Worst case scenario is they give you the same answer "sorry, can't be done".
Try calling them. Worst case scenario is they give you the same answer "sorry, can't be done".
Dec 23, 2019 | 5:50 am
#9
Original Poster
Join Date: Jul 2009
Posts: 155
Dec 23, 2019 | 8:10 am
#10
Join Date: May 2002
Programs: WN F9 HA UA AA IHG HH MR
Posts: 3,305
Looks like it's back to two bookings. 
As joshua362 noted, it probably is the international leg that is gumming things up. I also wouldn't be surprised if it is a holdover from the merger that the first segment was a legacy FL flight, while the next segment was legacy WN, and Amadeus still can't process that.
The silver lining is that you are another flight credit closer to A List.
As joshua362 noted, it probably is the international leg that is gumming things up. I also wouldn't be surprised if it is a holdover from the merger that the first segment was a legacy FL flight, while the next segment was legacy WN, and Amadeus still can't process that. The silver lining is that you are another flight credit closer to A List.
Dec 23, 2019 | 10:28 am
#11
FlyerTalk Evangelist
Join Date: Nov 2000
Location: Nashville -Past DL Plat, FO, WN-CP, various hotel programs
Programs: DL-MM, AA, SW w/companion,HiltonDiamond, Hyatt PLat, IHF Plat, Miles and Points Seeker
Posts: 11,405
Yep - you get another segment.
No matter if a through flight or two separate flights, when you return to the states you will have to collect your bags for customs. So, no big deal there at all.
No matter if a through flight or two separate flights, when you return to the states you will have to collect your bags for customs. So, no big deal there at all.
Dec 23, 2019 | 5:15 pm
#12
Join Date: Sep 2009
Location: DEN
Posts: 260
Likely not the case as PLS was never served by FL, it was started by WN in 2018 (a year after the Amadeus transition).
