IBT · Republic Airways / Mesa Airlines

Agreement Metadata

This extension and transition bundle consists of coordinated public materials: the Mesa “CBA with Extension” or extension edition, Mesa-side transition communications issued under the CWA-AFA framework, the IBT / CWA-AFA Joint Collective Bargaining Agreement (JCBA) Summary, the JCBA TA sections, and the foundational Republic Airways / International Brotherhood of Teamsters (IBT) base agreement. These materials function as integration instruments rather than as a single clean, fully restated public JCBA PDF.

The Republic Airways IBT agreement is identified as the base and controlling contract. Mesa Flight Attendants therefore experience more structural change, while Republic-side architecture remains the foundation. The amendable date for the combined framework remains October 12, 2027, with Railway Labor Act Section 6 negotiations scheduled to begin in 2027.

Source caution: Public materials should be read as a source stack: Republic base agreement plus JCBA TA / summary materials, not as a single restated clean CBA.

Contract Architecture Overview

The architectural purpose of the extension is convergence rather than redesign. Mesa’s extension edition does not establish an independent rule system; instead, it selectively incorporates Republic contract structures to stabilize the combined operation during transition and to prepare for JCBA bargaining.

From a structural perspective, Republic’s agreement remains intact and authoritative. Mesa-specific changes operate as transitional overlays, pointing Mesa Flight Attendants toward Republic norms rather than altering Republic’s underlying architecture.

Implication: The extension functions as directional alignment, not as a renegotiation of the Republic contract.

Scheduling & Assignment Framework

Scheduling changes reflected in the transition materials focus on procedural harmonization. Mesa scheduling constructs, including Schedule Adjustment Period (SAP) concepts, trade windows, and reserve-utilization transparency measures, are aligned toward Republic's scheduling ecosystem rather than replacing it with a Mesa-only framework.

The JCBA Summary identifies adoption of Mesa SAP concepts inside the Republic framework, a joint reserve utilization subcommittee, reduced trade deadlines, Mesa jet bridge trade concepts, and lineholder / short-call reserve trade language. These changes are best read as process alignment and transition controls, not as a complete rewrite of Republic's core scheduling authority.

Analytical lens: Scheduling convergence is achieved through procedural alignment and selected Mesa imports, while Republic remains the base architecture.

Reserve Transition Architecture

Reserve is the clearest example of why the transition should not be described as a simple Mesa cutover or a fully restated clean JCBA. The Republic contract supplies the base reserve architecture, while the JCBA Summary and Mesa transition materials add targeted changes that align Mesa Flight Attendants toward the Republic system.

Reserve takeaway: The transition is Republic-base alignment with selected Mesa procedural imports and reserve transparency commitments. It is not best described as a fully independent Mesa reserve system, and it is not yet supported by a single clean public integrated JCBA PDF.

Economic Structure

Economic changes described in the Mesa TA Summary are almost entirely Republic-derived. Mesa wage rates, per diem, and related economic provisions are matched to Republic’s scale, with transitional increases structured to preserve parity while the parties move toward JCBA negotiations.

Supplemental economic provisions, where present, are time-limited and explicitly transitional. They function to prevent regression or disparity during integration rather than to establish independent Mesa economic norms.

Key insight: The extension achieves economic parity by importing Republic rates rather than by introducing new Mesa-specific economic architecture.

Enforcement & Dispute Resolution Architecture

Enforcement architecture remains anchored in Republic’s grievance and System Board framework. The extension materials do not restructure Republic’s enforcement pathways; instead, they provide Mesa-specific continuity protections to ensure accrued benefits are preserved during system conversion.

Provisions addressing sick leave, vacation conversion, and PDO transition operate as protective overlays rather than as independent enforcement regimes. Disputes arising during transition are expected to be routed through the controlling Republic enforcement mechanisms.

Structural takeaway: Enforcement continuity favors Republic’s existing architecture, with Mesa provisions functioning as transitional safeguards.

Structural Strengths, Weaknesses & Comparative Flags

The principal structural strength of the extension bundle is clarity of direction. The Republic agreement is clearly identified as the base contract, and Mesa-side changes are framed as necessary adjustments to reach parity and facilitate integration. This reduces ambiguity about which rules control during transition.

The primary weakness is layered textual authority. Multiple documents must be read together to resolve specific questions, increasing cognitive load and the risk of “which instrument governs” disputes during the interim period, particularly in scheduling and crediting scenarios.

Standardized Contract Scorecard

Context Notes

This analysis evaluates the transition architecture rather than a finalized JCBA. Scores reflect how effectively the extension bundle preserves stability, parity, and enforceability during integration, not the long-term strength of the eventual joint agreement.