The following was posted in an e-newsletter I receive & it didn't really make sense to me given how many people fly codeshare, so thought I'd check w/ you. If it's true ok, learned something new (I don't normally fly codeshares-usually BMI or LH overseas). If not, I'll post your response in the next week's e-newsletter to correct it.

"If you're flying one leg of a trip as a "code share" flight -- that's where your reservation says it's one airline, say, US Airways, but it's really operated by another, say, United -- be prepared for extra screening. You'll be treated to a full-body screen and complete hand-search of your luggage. A TSAR official told me that travelers are routinely inconvenienced (and upset) by this strange policy that treats flying part of your trip on two airlines under one brand as some kind of security risk. Apparently, the airline computers read the code share part of your trip as a one-way ticket and that can flag you as a potential threat. To avoid the code share inconvenience, watch for the fine print in the reservation process that declares "Airline A Flight XYZ, operated by Airlines B."

Code-sharing alone is not the trigger. It's when the code-share is but for one leg of the trip -- which can look to the airline computer like a one-way ticket purchase. (Shouldn't be the case, but I'm told it is.) The key is whether the code share is for ONE leg of the trip."

Now that's a new one. I'll try to find out but can't promise anything after all it is the federal government where questions go in but never come out.

Thanks for checking. The e-newsletter comes out every Fri so if you do get a response, post here. If it's valid, fine. If it's not, then I'll submit a correction to the e-newsletter folk.

The NW/CO forums are full of threads about this problem--they have a lot of codeshares like this that take CO one-way and NW the other, and many people get secondary screening (SSSS) as a result.

http://www.flyertalk.com/forum/showt...ntal+codeshare

for example. Just do a search on "SSSS" and "codeshare" on flyertalk to see many other examples.

The severity of the problem tends to depend on the airline. There are fewer (but still some) such stories about UA/US codeshares. As the TSA folks here like to (correctly) point out, the airline computers do have some say over who gets SSSS, though the overarching system was architected by the government. The government will neither confirm nor deny the criteria used for selection, though it's obvious to anyone who flys much that one-way or perceived one-way tickets are a major component of it.

It's an unfortunate side-effect of knee-jerk overreactions to create the illusion of security, but that's another discussion.

The solution:

Put in the FF# for the respective airline at the time of reservation so that it is in there at ticketing.

Prior to boarding, swap out any FF#s you wish to change. Done deal, correct mileage accrual, no extra screening.

If you fly UA and US but only accumulate points to UA, simply get a US Dividend Miles number but swap it out for your Mileage Plus number once you're past security.

Spiff--my recent experience on a RTW I believe would disprove this theory. I originated a RTW in Shanghai, but had one leg from SNA-LAX-LHR on UA. I had my Mileage Plus 1K number in there but as it appears there was no return from LHR (as the return was on a separate PNR purchased a couple of months prior). I was flagged as SSSS.

Sharon,
Can't get much info on the exact criterea on what makes a selectee (eventhough everyone knows most of them).

Thanks for checking TSAMgr. It was just the above I was curious about. If it had been erroneous I would have posted a correction, but since we don't know, I won't.

Of course the downside is that some might be afraid to book code-shares worrying about SSSS (although I now have a pass ), but then again if they need to get there & it's the only way, they'll have to deal w/ the extra 2-3 min, which isn't that big a deal (she ducks knowing Spiff & others will come after her).

But then again, a bunch of my colleagues are a bit clueless; they get the ticket & wouldn't pay attention/know if it singled them out anyway (sigh). Cheers.

What I have seen and heard CAPPS II is suppose to rectify some of these problems.

(And now the Flaming of CAPPS II begins)

I know that if the airlines cancell a flight and put you on another airline the agent can put a code in the computer that will deselect you as a SSSS. Most of them don't want to take the time to do it. They want to get you transfered over as quick as they can so they don't have to hear you complain about the flight. As a screener it would save us a bunch of time not having a plane full of SSSS.

Yes, if you are rebooked and didn't have SSSS on the first BP you should demand to be de-selected.

Govt. could change CAPPS to stop harassing one-way flyers and stop harassing David Nelson, John Dear, etc. etc., and give people real, effective recourse to get off the no-fly list (instead of denials, lies, and the runaround) without implementing the Orwellian database that is CAPPS II.

There is absolutely no connection between fixing these disgraces and implementing the new disgrace that would be CAPPS II. It never has been and never will be the government's business where I flew last month, where I'm flying this week, and where I'm flying next month. My credit records, ownership or lack thereof of a phone number, and time at residence should have nothing to do with my freedom and RIGHT (not privelege) to travel (first amendment freedom of assembly and UN declaration on human rights). None of these Orwellian measures are needed for the government to stop the harassment that was the source of the original post. They could do it tomorrow morning if they really wanted to.

Happens all the time to me between NW and CO... I will typically book via NW, but CO will see their portion as a one-way and select me as a harassee (er, selectee -- SSSS).

Cheers,

SDF_Traveler

Just got back from SDF; I went to drop off (and see off) a friend off who flew in for the weekend.

Because of the severe wx outbreak in this region (both SDF & ORD), all non-stop flights to ORD were cancelled. I found a one-way SDF-ORD ticket on DL for $98 (a bargain) for same day purchase, reserved it and he purchased it at the airport on credit card. Once he was off to the checkpoint, the full treatment (but per his report, they were quite professional about it, only wanded his shoes vs sending through the x-ray, etc).

SDF was swammped (and will continue to be, today) with Selectees this morning as AA and UA have all CX'd their ORD flights (and who knows what else is cancelled). Here in Louisville, many tornado touch downs and high winds; We have wind/hail damage here and I personally witnessed 3 funnel clouds, one well defined which came close to a touchdown, to give you an idea of just how bad the wx was.

Edit: Last night there were 13 tornado touchdowns in the ORD area and both AA ORD-LHR flights cancelled. The 9:00am my friend got this morning was packed with a large waitlist. As such, ORD and other airports in this region must be facing significant #'s of selectees today because of invol re-routes. Lots of dangerous individuals, eh?

Back to SDF this morning:

Unfortunately, AA's counter wasn't open yet and the purchase of a new ticket from SDF-ORD (via CVG) was the only possible way for him to reach ORD (by commercial air) to connect onward internationally this morning. UA's counter was at least open and they were endorsing tix over to US, DL, and NW, thus more SSSS's.

Watching my friend go through the checkpoint it seemed the majority of pax were SSSS "rebooks". While efficiently operated this morning, bloody disgusting they have to put everyone through this. It was clear they were rushing through all of the dangerous selectees this morning. It would of been a nightmare if they actually went the whole 10 yards with each selectee. Kudos to the TSA for using common sense this morning.

Best,

SDF_Traveler

P.S. As they were only wanding footware and not forcing removal this morning for full x-ray, it completely contradicts the alleged shoe removal "excuse". As a TSA agent at EWR once sceamed at me "It's not metal we're looking for" (She said this in response after I refused to remove my sandal's after I said they didn't contain metal).

Some of what CAPPS II will do is update the algorithms currently used in CAPPS I so consider it as a software upgrade also.