erkpod
Established Member
- Joined
- Jun 8, 2013
- Posts
- 2,056
A mantra that I soon learnt here at AFF is the expression "Why go direct when you can connect", especially when it comes to building status. So instead of going (for example) SYD - PER, you might go SYD - MEL - PER.
But when doesn't that work for you - especially in terms of travel time?
I was just looking at some VA fares SYD - LAX. One suggested routing was SYD - PER - MEL - LAX. Basically, you'd go SYD - PER in the afternoon, fly back to MEL on the red eye & then fly over to LAX.
Another example I was looking at was in America going from PDX to MIA. The routing I have decided on was PDX - ATL - MIA. There was one suggestion that was in my eyes simply too long: PDX - ATL - LGA - MIA. Great for a mileage/status run maybe but at what cost when it comes to time?
But when doesn't that work for you - especially in terms of travel time?
I was just looking at some VA fares SYD - LAX. One suggested routing was SYD - PER - MEL - LAX. Basically, you'd go SYD - PER in the afternoon, fly back to MEL on the red eye & then fly over to LAX.
Another example I was looking at was in America going from PDX to MIA. The routing I have decided on was PDX - ATL - MIA. There was one suggestion that was in my eyes simply too long: PDX - ATL - LGA - MIA. Great for a mileage/status run maybe but at what cost when it comes to time?