Is LUV looking for a RJ partner?

Subscribe
1  2  3  4  5  6 
Page 5 of 6
Go to
Quote: What about an arrangement sorta along the lines of your deal with ATA?

John Dennison, former WN CFO and ATA CEO, pulled ATA out of every city that SWA served presumably because it either didn't make money or was in conflict with SWA's Scope. That pretty much shut us down as a domestic carrier.

So, I don't think that a domestic codeshare will ever come to pass at SWA.
Reply
Quote: Has this been any topic of discussion with respect to your new contract negotiations?
The latest Union newsletter has an article from our President and it addresses the "scope and codeshare" issue.

The union can't give us any details but mentions that we have a tentative agreement in regards to scope and codeshare.

I'll be the first to admit that I was wrong when I said there is no one in the "hunt" for RJ flying .

The company has looked at an RJ code share and the article mentions that it would not be a surprise if the company entered into a code share agreement with an RJ provider.

Tentative agreement below.


EXECUTIVE SUMMARY: SECTION 1 – PURPOSE OF AGREEMENT



The Negotiating Committee and the Company recently reached a Tentative Agreement (TA) on Section 1, Purpose of Agreement. Last week, during a three day session, the Negotiating Committee briefed the SWAPA Board of Directors in great detail and answered all questions regarding the agreement on Section 1. The Board concluded that Section 1 objectives had been met and unanimously endorsed the agreement.

Section 1 language was strengthened in virtually every area. Specifically, the agreement contains significant improvements and protections for the pilot group in the event the Company wishes to expand its network through codeshare and/or marketing agreements. Several improvements to merger, acquisition and successorship language were also realized.

Tentatively Negotiated Changes to Section 1


Scope
Expanded the overall scope of the contract to capture all of the work done by pilots on the seniority list

Preserved the positive public association with the valuable SWA brand by allowing only SWAPA pilots to fly SWA aircraft


Recognition
Protected pilot job security in the event of any transfer of control – voluntary or involuntary

Received commitment from SWA to make this Collective Bargaining Agreement a condition of any sale in order to protect pilot jobs and wages as negotiated


Merger
Protected pilot jobs in the event of a merger

Protected SWAPA pilots’ seniority through a fair and equitable pilot seniority integration system in the event of a merger that includes new pilots

Removed ambiguity in current language so no successor has leverage to change terms of employment previously negotiated by SWAPA

Prohibited creation of an affiliate, new airline or subsidiary, or acquisition of a controlling interest in any carrier unless all flying is performed by SWAPA pilots (i.e. avoided creation alter-ego carrier)

Required reasonable, advance notice and details of any material agreements to SWAPA



Sub-Contracting
Prohibited SWA from sub-contracting revenue flying.

Protected against wet-leases


Purchase or Acquisition of Another Company

Required reasonable, advance notice and details of any material agreements to SWAPA

Protected pay rates, rules and working conditions from being renegotiated in the event of a purchase

If pilots are acquired through the purchase of another airline, empowered SWAPA to integrate pilots into the seniority list


Codesharing
Verified and expanded terms of SWA’s commitment to grow the airline and the Pilot Seniority List

Expanded Side Letter 32 protections to properly coordinate with remainder of new Scope proposals

Clearly defined purpose of codesharing; specifically focused on SWA growth and feeder operations

Defined codeshare transaction to always include at least one flight segment on SWA

Protected SWA brand identity in relation to codeshare relationships

Secured Regional Jet (RJ) codeshare protections


Cabotage
Incorporated cabotage language in CBA, to avoid leaving protections solely to federal regulations

Prohibited use of SWA code on flights of foreign carriers carrying local revenue passengers or cargo traffic between airports within the U.S.


Foreign Domiciles
Addressed conditions surrounding foreign domiciles in relation to bidding, relocation expenses and other working conditions

Re-Opener
Updated language to specify and limit terms for which this CBA may be reopened

Amendments to Agreement

Future amendments to the agreement will be automatically integrated into an electronic version of the Collective Bargaining Agreement

Definitions
Added definitions to clarify terms specific to Section 1 of the CBA
Reply
Crazy, so what is the talk/rumors at Southwest now that this little tidbit of info has surfaced?
Reply
OK guys, not trying to be anal, but lets try to keep the terminology somewhat accurate so we know what we are talking about....

On the union newsletter you quoted "codeshare and/or marketing agreements".... that has nothing to do with a capacity purchase agreement under which most of the regionals are operating.

Also further down it mentions "Regional Jet (RJ) codeshare protections".... are you sure they don't really mean subcontracting of flying to an RJ operation???
Reply
Quote: Saab,

When I flew at Allegheny, we were called the commuters, at least "regional" is a step up. I won't tell you what the traveling public called the Shorts 330/360 that I used to fly in.

Tailwinds,

FF
Ditto, from a NPA (long defunked commuter) Jetstream 31 survivor.
fbh
Reply
Quote: Crazy, so what is the talk/rumors at Southwest now that this little tidbit of info has surfaced?
Haven't heard much on the line.
Reply
Quote: OK guys, not trying to be anal, but lets try to keep the terminology somewhat accurate so we know what we are talking about....

On the union newsletter you quoted "codeshare and/or marketing agreements".... that has nothing to do with a capacity purchase agreement under which most of the regionals are operating.

Also further down it mentions "Regional Jet (RJ) codeshare protections".... are you sure they don't really mean subcontracting of flying to an RJ operation???
I was obviously in the wrong, so I don't have a clue.

Maybe some of my SWA bro's have an idea.
Reply
The executive summary has almost no info in it - and purposely so. We are bargaining with the company in good faith, so we won't have the final language until just prior to voting on the contract. I don't see how anybody could conclude from that short blurb that we are/aren't looking for an RJ partner. All it says is that we have secured RJ contractural protection when our previous contract had none.
Reply
Not to be too much of a conspiracy/rumor guy, but concerning the post about SWA wanting to compete with XJet's branded flying--I have noticed many many of SWA's TV ads are emphasizing "you're assured that every flight on Southwest is on a nice, big roomy 737...yada yada yada."

The marketing folks must be doing at least some targeting of customers who might be choosing to fly connection/regional flights instead of SWA...like those who offer $1 beers and meals on flights (XJet? hmmm)
Reply
Quote: The marketing folks must be doing at least some targeting of customers who might be choosing to fly connection/regional flights instead of SWA...like those who offer $1 beers and meals on flights (XJet? hmmm)
Personally I bet it has a lot more to do with the entire feed concept as a whole, with the big carriers using more and more RJ's on routes SWA serves. XJT doesn't compete with SWA on any routes that I'm aware of, to top it off they pull flights when SWA opens up routes that they are on.
Reply
1  2  3  4  5  6 
Page 5 of 6
Go to