Originally Posted by
bgriff
I don't think AR is necessarily as bad as it's made out to be for shorthaul travel -- it's in longhaul that it looks worst compared to other airlines. But that said, there is some risk of disruption due to strikes or who knows what -- hard to say how much risk, though usually strikes are announced with a bit of forewarning.
That said, how much time are you thinking is exactly the right amount? It's a tricky call because too early and the United check-in counter at EZE won't be open, but given the risk of delays on the incoming flight (not necessarily AR-specific delays, just the risk you'd have making a plan like this anywhere in the world) I'd ideally want about 4 hours, no less and maybe a bit more.
Thanks for the quick reply, BGriff - I agree that any flight can be delayed for reasons unrelated to the airline itself, and that's a chance we all take in flying.
Regarding the connection, the AR flight would arrive at EZE at 5:35 pm, the United flight to IAH leaves at 9:20 pm, so almost four hours. We'll need to claim our luggage, find our way to the United check-in counter (we have priority status), then get through security and to the gate. If we take the LAN flight we'd arrive at AEP at 10:20 am, leaving almost ten hours to get between the airports and check in, etc. If we end up flying on LAN, we'd probably arrange a private car and driver to pick us up at AEP, take us somewhere for a day trip and lunch, then drop us at EZE. Would welcome any suggestions for lunch/trips, given that we will have already spent six days in BA at the beginning of the trip at a conference that will include a lot of sight-seeing excursions.
Thanks again!