Originally Posted by
ARedLetterDay
Goobers. I faxed them my d*@% ID several months ago that included the suffix to my name and asked them to add it to my account and they refused, even going so far as to tell me to NEVER use the suffix in ANY AA reservation.
Sometimes it's a wonder any of these admin departments are able to run at all.
I had a similar experience due to TSA previously insisting not to use any suffix in the PNR.
However, thanks to the "SECURE FLIGHT FINAL PHASE" Oct 20, 2010 document linked above, it seems TSA is now saying that for DOMESTIC, the suffix is NOT required, but for INTL it IS absolutely required. (see AA linked doc, above) Based, on that information, I phoned in AAdvantage Cust Svc and they initially refused, but after referencing the above "SECURE FLIGHT FINAL PHASE" document, they quickly changed their tune and added my suffix by using a "#" between my last name and my suffix, so for now I finally have my full name matching exactly my passport details.
Now, we will have to wait until they fix the issue on AA.com as currently there is no field for the suffix and as a result, OLCI fails for INTL check-in, but still works for DOMESTIC check-in.
I am very surprised that AA.com appears unprepared to handle the INTL suffix requirement, which prevents those of us with a suffix to not be able to do INTL OLCI. Is anyone also experiencing this?