FlyerTalk Forums - View Single Post - Planning for the Checkpoints without Scanners reference thread
Old Apr 6, 2011 | 10:29 pm
  #1  
PhlyingRPh
Suspended
 
Join Date: Sep 2004
Location: USA
Programs: UA/CO(1K-PLT), AA(PLT), QR, EK, Marriott(PLT), Hilton(DMND)
Posts: 9,538
Planning for the Checkpoints without Scanners reference thread

I think there have been a couple of informal attempts to document where exactly the TSA has checkpoints that are not yet scanner enabled. I'd like to start an easy to search thread that consolidates this information and was wondering if the membership might be willing to assess the following format...

Post Title: Airport Code SPACE Terminal SPACE Checkpoint location

Notes:
1) Use approved IATA airport code only
2) Terminal Name/Number should be T1, Terminal B, North Terminal, Jefferson Davis Memorial Terminal, etc
3) Ideally, checkpoint location should ideally be lifted from the airport's website or described by airline, concourse served, etc.

Body:
Date: Date you noted no scanner
Airlines served: Airlines served by this checkpoint
Alternative for: If one can get from this checkpoint to other points within the airport, describe this here.
Terminal map: (Link to official map of terminal)
Comments: Relevant info such as presence of elite line, etc.
When will scanner be installed: Members should, if possible, ascertain whether or not scanners will be implemented at the checkpoint soon. I sometimes make a comment to a TSO such as "I'm glad you don't have that ridiculous scanner in place here. I'd be worried about your health if you worked at a checkpoint with one of those things". The verbal diarrhea then waxes forth like a singing canary.

Comments on the format of the proposed thread please...

While reviewing the format, please bear in mind that the goal of this thread is that if I am traveling from say MSY on CO tonight, I should be able to do a search consisting of nothing more than "MSY CO" in order to learn whether or not that checkpoint has a scanner in place. Perhaps someone can even create an app that scrapes the information from this thread for on-the-fly reporting.
PhlyingRPh is offline