AA Net SAAvers & STL -- Help!
Sep 10, 2001 | 3:46 pm
#1
Original Poster
Join Date: Nov 1999
Location: St. Louis, MO - AA PLT/2.98MM (Lifetime PLT), Delta PM, SPG Gold, AMEX Plat
Programs: TW Elite (RIP), CO OnePass
Posts: 1,923
AA Net SAAvers & STL -- Help!
I'm hoping Randy might be able exert a little of his influence to help us in St. Louis out a bit.
Effective October 1, all STL-DFW flights on AA will be codeshares on TWA flights. Effective later this year, all STL-ORD flights on AA will also be codeshares on TWA flights -- leaving no mainline AA service out of STL.
One minor problem: Virtually all AA Net SAAvers (Spotlight SAAle - Japan, Go for the Goal SAAle - Continental U.S., etc) specifically exclude non AA/Eagle flights!!
After October 1, this will require connections through ORD off of AA's 5 mainline flights from STL (resulting in a lot of horribly inefficient connections, STL-ORD-SEA for example). Later in the year, it will result in not being able to use any Net SAAver fares to/from St. Louis.
If the rules of these fares were modified to include the TWA codeshares, I wouldn't have to consider choosing between one of three bad options:
1) Flying on a Net SAAver fare with a 3+ hour connection at ORD (until all ORD flights go to TWA)
2) Paying an extra $150 more for a non-Net SAAver ticket with a simple connection.
3) Flying Southwest instead (anything but that!)
I've so far tried contacting the AA Platinum Desk, the AA.com help desk and the AA Webmaster. The more progress so far is a "we'll forward your comments to the appropriate people" -- which doesn't inspire much confidence.
Randy -- Help!
Greg
Effective October 1, all STL-DFW flights on AA will be codeshares on TWA flights. Effective later this year, all STL-ORD flights on AA will also be codeshares on TWA flights -- leaving no mainline AA service out of STL.
One minor problem: Virtually all AA Net SAAvers (Spotlight SAAle - Japan, Go for the Goal SAAle - Continental U.S., etc) specifically exclude non AA/Eagle flights!!
After October 1, this will require connections through ORD off of AA's 5 mainline flights from STL (resulting in a lot of horribly inefficient connections, STL-ORD-SEA for example). Later in the year, it will result in not being able to use any Net SAAver fares to/from St. Louis.
If the rules of these fares were modified to include the TWA codeshares, I wouldn't have to consider choosing between one of three bad options:
1) Flying on a Net SAAver fare with a 3+ hour connection at ORD (until all ORD flights go to TWA)
2) Paying an extra $150 more for a non-Net SAAver ticket with a simple connection.
3) Flying Southwest instead (anything but that!)
I've so far tried contacting the AA Platinum Desk, the AA.com help desk and the AA Webmaster. The more progress so far is a "we'll forward your comments to the appropriate people" -- which doesn't inspire much confidence.
Randy -- Help!
Greg
