Air Atlanta: questions about scope protection
Why this briefing: Explain the concerns raised in the Air Atlanta advisory and the call for stronger scope language.
The advisory raises a specific question: were flights normally performed by Atlas crews being assigned to Air Atlanta aircraft and crews? It expressly says the reports require confirmation.
Verify the flying before drawing conclusions.
The advisory asks whether reported Air Atlanta operations expose a scope gap.
Keep in mind: The flight reports were explicitly unconfirmed when the advisory was written.
01The issueUnderstand what is being discussed
The single-page advisory by John Corcoran and Jesse Johansen describes reports of planned August flying and a reported ANC–NLU flight.
It also describes a 49% investment and Titan aircraft leasing.
The advisory's opening and closing passages make clear that the flight reports were still being checked when it was written.
02Why it mattersSee the effect on members
A specific operational example can help members test whether contractual protections match their expectations.
But the answer depends on verified details: the flight, date, aircraft, operator, arrangement, and applicable contract language.
Rumor cannot substitute for those records.
03What went wrongSeparate the criticism from what is established
The authors argue that minority ownership and dry leasing leave a gap in current scope protections.
They characterize the arrangement they describe as contract-compliant while criticizing the protection the language provides.
This is their interpretation, not a ruling supplied with the advisory.
The statement that lease rates could shift profit is a potential concern, not evidence here of actual rates or profit transfers.
04The deeper concernsExplore the questions still open
Was the reported flight confirmed?
Did the planned flying occur?
Was the arrangement temporary, extended, or changed?
Has the union explained which provisions apply?
The advisory contains no visible publication date, and an August reference alone does not establish a year or current operational status.
05Our positionWhat we propose to do
establish the facts before making operational allegations, explain the scope language that applies, and seek stronger protection where verified arrangements expose a gap.
Share subsequent confirmations and corrections so members can distinguish the original concern from what was later established.