Planning for the Checkpoints without Scanners reference thread
#1
Original Poster
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.
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.
#2


Join Date: Dec 2009
Location: WAS
Posts: 3,048
You mean like this thread?
http://www.flyertalk.com/forum/trave...y-scanner.html
http://www.flyertalk.com/forum/trave...y-scanner.html
#3
Original Poster
Suspended
Join Date: Sep 2004
Location: USA
Programs: UA/CO(1K-PLT), AA(PLT), QR, EK, Marriott(PLT), Hilton(DMND)
Posts: 9,538
Ah, well, yes, I'm glad you are paying attention. That will be all for now
[sound of whistling wind as thread descends rapidly to the inner depths of FT]
[sound of whistling wind as thread descends rapidly to the inner depths of FT]
#4
FlyerTalk Evangelist




Join Date: Nov 2009
Location: Northeast Kansas | Colorado Native
Programs: Amex Gold/Plat, UA *G, Hyatt Globalist, IHG Plat Marriott LT Gold, NEXUS, TSA Disparager Unobtanium
Posts: 22,644
Once I have some extra time, I am hoping to revamp the NoS thread. I would really like to make it more user friendly.. Stay tuned for some updates
#5
Original Poster
Suspended
Join Date: Sep 2004
Location: USA
Programs: UA/CO(1K-PLT), AA(PLT), QR, EK, Marriott(PLT), Hilton(DMND)
Posts: 9,538
I'm sorry, I don't know how I could have missed that thread - perhaps a consequence of accessing FT from a Nokia mobile device, or the result of excessive multi-tasking, or just not paying attention.
#6
FlyerTalk Evangelist




Join Date: Nov 2009
Location: Northeast Kansas | Colorado Native
Programs: Amex Gold/Plat, UA *G, Hyatt Globalist, IHG Plat Marriott LT Gold, NEXUS, TSA Disparager Unobtanium
Posts: 22,644
#7
Join Date: May 2010
Location: SNA
Programs: AAdvantage Platinum
Posts: 529
Okay, but that doesn't mean you don't have some good ideas here. The airport list is still rather general without information on avoiding scanners at certain checkpoints. It does little to say that LAX T4 has backscatters, for example. It is a lot more helpful to add that the left most check point lane there does not. In other words, we still need a thread/ data base where we can get the details of specific terminals/ check points.
Last edited by UALpremier; Apr 7, 2011 at 1:28 am
#8
FlyerTalk Evangelist


Join Date: Mar 2002
Location: An NPR mind living in a Fox News world
Posts: 14,343
Wirelessly posted (BlackBerry8830/4.5.0.138 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/105)
The link to the site in my signature line is a great resource as well. We could make an effort to keep it current and accurate.
The link to the site in my signature line is a great resource as well. We could make an effort to keep it current and accurate.

