Originally Posted by
trf0412
If that's the case, then it essentially renders the MCT meaningless if a boarding pass cannot be issued prior to arrival, as I can't imagine any MCT factoring in time to go and check-in before the flight closes.
The "normal" Int'l-Int'l MCT in JFK is 2 hours. AA and LA files something to override this and make it 1:15, so the MCT was reduced based on the assumption that BP was print before arrival to JFK. The upside is that this provides a lot more transit options for travellers (and gives the airlines more revenue). The downside, however, is that when something like your case happens, PAX are in trouble. Airlines definately needs to consider this when the MCT is filed, and you can blame them for not testing there system well enough, but the MCT is certainly not "meaningless."
Code:
T*CT-JFK/AALA/II«
STANDARD.D/D...D/I...I/D...I/I.
ONLINE 1.00 1.15 1.45 2.00
OFFLINE 1.00 1.15 1.45 2.00
** OR * ARE ALL
AA-LA II 1.15 FLT 1 - 5099 - ALL
AA-LA II 1.15 FLT 6018 - 6070 - ALL
AA-LA II 1.15 FLT 7181 - 7210 - ALL
AA-LA II 1.15 FLT 8050 - 8103 - ALL
AA-LA II 2.00
AA-** II SUP FLT 7833 - 7862 - ALL
Originally Posted by
trf0412
No, neither BA nor AA said anything about having technical issues or there being some reason they couldn't check me in. If there was, they should have noticed the tight connection and realised I wouldn't make it, so why didn't they say anything or call ahead to get LAN to check me in?
Presumably, though, if all flights were operated by a single airline, there wouldn't have been any problem checking me in for all flights on arrival at MAN? It seems the problem comes from the fact check-in was done with BA and they were unable to access LAN's system to check me in for that flight?
Is this just one of the major downfalls to booking multiple-carrier itineraries?
I think the problem arises because you are travelling on 3 different airlines. I will take it back that code-share does not matter, because now I think that might be the reason. It could be that the BA agent was entering the AA FLT number when trying to check you in the JFK-LIM FLT, and of course the system (EDIFACT) would not be able to check you in that way. The BA agent at MAN needs to put in the LA's code of that segment to check you in, and the agent might not have realised it and thought that the JFK-LIM FLT was an AA-operated FLT. AA at LHR then thought it was too much a hassle to undo the check-in for LHR-JFK segment (with the chance to lose your seat assignment) and then do the whole thing over again (likely required by the system), so suggest you to do it in JFK. Another possiblity, of course, is that LA's system was not working properly. In any case, I agree the airlines (especially AA) are morally held responsible for your case (and hence hope that AA will reimburse you), although legally I guess they aren't.