Originally Posted by
WillCAD
As for a cancelled flight, as others have said, there's no realistic chance that the TDCs at any given checkpoint would know that...
<snip>
So if a BP is expired, i.e. the flight has already departed, then it's not technically valid any more, and if a TSO notices, it is remotely possible that you may not be given access to the sterile area until you produce a valid BP which matches your ID. From the responses above, it sounds like it's not currently a problem, but be aware that it is theoretically a problem, and be ready to deal with it if it manifests (i.e. don't panic, just go to ticketing and rebook to get a valid BP).
But we can't necessarily equate "expired" with "departed", right? What if this problem happens but the flight is actually delayed and you can still make it? The BP
is valid in this case, right?
How do you convince the TSO, who doesn't have the real-time flight status? You could try to show them the delay on your phone,
if you have a phone with working internet and
if they will look at/trust it. Going to the check-in counter might help,
if they are able to reprint a BP past original departure time and
if the new BP shows the delayed departure.
Is there any anecdotal evidence that anyone has ever had this problem? (Some might way, "You're supposed to be there on time even if your flight is delayed, so it would be the pax's fault," but consider that it could be a late incoming flight arrival with a "fortunately delayed" connection. Or, when one flight is canceled, you might be involuntarily rebooked on one that was supposed to leave earlier but is delayed, but BP shows the original time. Etc. Many ways this could happen through no fault of pax.)
A related question is exactly what info the TSO sees when you scan a
mobile BP (obviously it must include the pax name for ID checking). Does the computer even show/use the flight time (somehow embedded in the QR code) or does it just confirm the date matches and give the TSO the "green light"/beep?