First of all, once the f/a's are integrated then their TA is null and void and they can all fly with east or west pilots. Can someone explain what opening up a pilot satellite has to do with f/a's? Does your company have a policy of only flying pilots and f/a's from common bases?
Oh geez! More outside chatter. Sure, the FAs TA is null and void with a new contract. But don't count on their new contract allowing flying with West crews until the pilot contract is in place. Your question in your first paragraph shows your totally out of our loop. They could move the 330s to PHX they want, but the INTL trips, at least now, don't start in PHX. I doubt there will be a market for that for years to come out of PHX to anywhere in Europe. Most of our 330s don't have PHX-Europe range anyway. The rest of your what ifs don't make enough sense to comment on. Jetz, stick with reality and the current status quo. From the FAs I fly with, they are miles away from an agreement, maybe further away than we are. The company knows Separate Ops for FAs make more sense than for pilots. They're in no hurry.
I've heard of some airlines keeping pilots and f/as together for an entire pairing. But I've never heard of this co-domicile thing, and don't think any other company does this. At UA we have pilot domiciles where there are no f/a domiciles, and f/a domiciles where no pilot domicile exists. JFK pilots fly with west coast f/a's all the time. Heck sometimes we have f/a's from 3 or 4 different domiciles on different pairings on each flight.
Who cares what other airlines do. Stick to UA posting where you may have some credibility.
So what would prevent the company from moving 330's (those not specifically covered in the TA) to PHX and 320's to CLT to keep minimum fleet numbers, or having west crews in a PHL satellite fly to Europe to destinations announced after the TA was signed, with east f/a's on "non-TA 330's?"
All kinds of contract and TA language.