Originally Posted by
trf0412
The connecting time at JFK was pretty tight (1:15), but the flight from LHR as 15 minutes early, giving me 1:30. I got through immigration and customs really quickly and got to the One World transfer desk about 45 minutes before scheduled departure. It was at that point LAN informed me I was not checked-in for the JFK-LIM flight and the flight had been closed and therefore I would not be accepted for boarding.
No offense, buy may I ask how come it took you 45 min to get to the LA counter (when you said you "got through immigration and customs really quickly")? AFAIK, it is in the same terminal.
Originally Posted by
trf0412
- Why did BA not check me through to my final destination (it was no issue checking my bags to LIM)? Is it true that sometimes an airline can't check you all the way through? If so, how can a 1:15 MCT even be permitted?
Admittedly the MCT was probably set with the assumption that you get your onward BP before arriving JFK. However, it is certainly true that sometimes an airline can't check you all the way through, even within the same alliance. There were probably some technical reasons. Did BA or AA tell you anything?
Originally Posted by
trf0412
- Which of the 3 airlines is responsible for this sequence of events? BA say it's AA's fault, AA say it's BA's fault, LA say it's not their fault...
- Is there any scope for requesting/demanding compensation? Is there any legislation regarding this? It wasn't a cancellation and LAN may say I wasn't checked in, so therefore it's not denied boarding. So what it is? Negligence on the part of the check-in staff? Inevitable eventuality when travelling on codeshare flights?
I would say it is none of them's fault, because the incoming AA FLT did not arrive late (if the incoming AA FLT were 1 min late, you have a good case here). AA also put you on the next available FLT. You can, of course, argue and see if you can get the hotel / food charge reimbursed from AA. I would not consider this unreasonable, although honestly I don't think you have quite a good case, either. BTW, it has nothing to do with code-share IMO. You could have the same scenario even if booked on operating carriers' codes.