![]() |
Originally Posted by tennisguru
(Post 3229527)
As was mentioned by someone else I think the bigger issue is the 12 hour cutoff. If I’ve got close to 12 hours to grab a bite to eat and wind down and get some decent sleep the last thing I want to do is waste 30 minutes each way on a drive. I don’t know of anyone that is going out and hitting the trails or seeing the sights in such a short window. The FAs have 15 I think which is too far the other way. I think 13 or 13.5 is a nice happy medium. It’d be nice to be able to work with the company on some city-specific carve outs, including the beach cities as others have mentioned.
Where this really comes into play is with the optimizer going full throttle I’ve seen many 4 day trips on the 717 where every layover is less than 13 hours. That’s just exhausting in and of itself plus depending on where your staying you’re losing a ton of previous layover time in transport. |
Arrival times matter just as much as the length of the layover when it comes to the shorter ones. For a 12 hour layover, my needs for a hotel/location are much different for one that is 1700-0500 versus 2100-0900.
|
One of the most egregious examples is BWI. The drive to and from Annapolis on a 12 hour layover is brutal. Especially with a zero dark thirty show.
|
| All times are GMT -8. The time now is 09:44 PM. |
Website Copyright © 2026 MH Sub I, LLC dba Internet Brands