Originally Posted by
richarddd
Not a very common name. All information is correct, other than one digit of the birthday.
One thing that seems odd to me is that the SecureFlight info comes from BA (which sold the ticket), but BA doesn't ask for KTN, which comes from AA records. Also, AA has all of the correct info, linked to the FF number if nothing else.
It's also rather odd that the operating airline can't change a birthday, although passport info can be updated online. BA can change the birthday, but AA can't see the change.
In any event, we'll arrive at the airport overly early and hope for pre-check so that we can spend lots of time at the fabulous admiral's club.
The FF account info doesn't change all of the biodata info filed with the government by the operating carrier, even when the biodata info is entered into the record at time of initial booking/ticketing.
When the FF info doesn't match the biodata info otherwise entered in the booking, then AA's systems seem to take more issue with the bookings and more frequently inhibit things that can otherwise be rather easily changed -- including being changed at the airport on the day of travel. Mismatched data and its results.
It's a good idea to show up earlier for check-in when this kind of stuff happens. Actually it's a good idea to show up earlier nowadays even when there is no data mismatch and stubbornness in the system when it comes to revising data elements which can be revised.