Originally Posted by
daniellam
I don't know how many time I have said this in other threads relating to this topic, but this is how it happens:
- The data your provide for SecureFlight is used BEHIND THE SCENES where the airline's computer system transmits to the the TSA before you even check-in. The TSA matches this information against their no-fly lists and sends either an "OK to fly", or "Not OK to Fly" message back to the airline.
- If the airline receives an "OK to fly" message from the TSA, then you will be able to receive your boarding pass (even if the name on the boarding pass does not show your middle name etc.).
- If the airline receives a "Not OK to Fly" message from the TSA, then you won't be receiving your boarding pass to begin with!! (As the airline would not be able to issue you a boarding pass). If this happens to you, then you will have to apply for a "redress number" that you can use in the future when you fly.
I'm quite aware of this and I know what "SecureFlight" is.
However, if the "Secure Flight" data is never validated, what is the point in collecting it and passing it onto the TSA? How exactly does this improve security?
I might as well use ROCKS for my middle name, and perhaps a typo here and a typo when it comes to my birthdate, or accidentally hit the wrong gender
because the data isn't validated anywhere in the check-in process.
There is no validation procedure for US domestic travel, other than the off chance that an airline CSR might check your ID against the SSR DOCS field.