Originally Posted by Mr. July
It's useful to know where the direct flights stop (so you know how far out of the way you're traveling - e.g. PDX-PHX-BWI - when choosing between flights, determine how long/short the individual flight segments will be (BWI-ORF-LAS vs. BWI-MCI-OAK), or factor for potential weather delays if you have a choice of cities (say PHX vs MDW)),
Exactly why i wish this data was there. Seriously the unbridled defense brigade on this forum is such a
The WN pilot tells me what altitude he's flying, what mountain he's passing, what city is on the right side, and I just want to tell him "I'm eating peanuts...not all at once...cuz it's such a big bag".
Point is, what's useless for some is useful for others, and it's just a recommendation, geez.
The only change I could see is a notation on the confirmation screen/printout page telling you where your direct flight stops - especially since that's the city you're most likely to see listed or hear called when you arrive at the airport and/or gate for your flight.
Exactly. And there are easily half-dozen other circumstances.
It should be easily available *before* you hit the purchase button however. What if you have a warrant for your arrest in AZ but not in Nevada?