Does the OP have a rather common first name and last name? If so, then the SecureFlight info may matter more. Lots of people with very uncommon names fly just fine even when the InSecureFlight info is incorrect.
And for international trips, the key info is from the passport; and that passport info need not be a perfect match with InSecureFlight entries for a passenger to fly -- weird as that kind of outcome sort of is, welcome to DHS/TSA in action.
That said, when this kind of stuff hits, it's usually because the person has a higher chance of being hit with hara
SSSSment than the average passenger. But most times like this, hara
SSSSment is not the outcome on the boarding pass when this happens.
Originally Posted by
MSPeconomist
IIRC there's a rule about not being able to change any of the Secure Flight information within 72 hours of departure. Hence you cannot change the birthdate yourself. I don't know whether phone agents can override this or whether it requires document verification at the airport. It's a rule that applies if you're trying to add a Know Traveler Number, but I've never heard of a birthdate being wrong somehow.
It's a good practice to check this online about five days before any international itinerary, especially if you're dealing with a flakey computer system or one that's had some major "updates" or "enhancements" recently.
The operating airline can update the InSecureFlight info and KTN at the airport. I've had AA/US, DL and UA enter my KTN into the record even after I've been checked-in -- sometimes even after I've flown part or most of the way on a ticketed PNR for a one-way trip.
Incorrect birthdates on ticketed PNRs for international flights can be updated by the operating airline when the check-in attempt is at the airport and the passport is in need of being validated in person prior to check-in.
I've had the birthdate and even sex info and KTN revised at airports more times than I care to count. If the reps say it can't be done even after check-in, then the passenger can ask to get unchecked in and tell the reps to attempt the update of the info again. That seems to work and has often enough resulted in getting PreCheck LLL.