Hotel Kilo

Great, thanks, this was a missing piece for me. So how are most of you running ARCOS to avoid the VRU calls at all hours?

Bucking Bar

Has not been my experience. A proffer accepted is no longer a proffer.

My understanding is that Y waives the proffer when >12 hours and N excludes the pilot from being given the proffer <12 hours.

One caveat that confuses many pilots is that this conversation only deals with trip covered with ARCOS. PCS certainly waives the proffer aspect on WS awards.

Bucking Bar

Looking forward to NuGuy's input on this. I use the Do Not Call line to blank out the hours my wife sleeps during the school year (say 23:00 to 07:00). I go into great granularity on the overnights, hours, credit, etc for trips that I desire. The variable that I cannot control for is if the company uses ARCOS to cover the rotation. Often ARCOS screws up on acknowledgement where I get skipped because the acknowledgment was not logged or scheduling immediate calls to confirm the acknowledgment and find out "when will you be at the airport."

NuGuy

A better way to look at it is this. ARCOS has two steps:

Step 1) "Hey Mr./Ms. Pilot. Here are some trip(s). Are you interested, and if so, which one's do you prefer?". The answer can be none, thus, the whole thing is a proffer.
If you select auto-accept, you are saying "I will look at any rotation that you proffer, but you don't need to call me for this step. Don't call me unless I'm the person the trip would go to for sure".

Step 2) "Hey Mr./Ms. Pilot, you are the successful bidder for a/the rotation from step one, the trip is yours. Do you really want it?". Again, the answer can be no for this step as well, so it's also a proffer.
If you select auto-acknowledge, you are saying "I will accept whatever rotation materializes for this step, so you don't have to call". The system will call you anyway if inside 12 hours.

If you select auto-accept, but not auto-acknowledge, the system won't call you unless you're the successful bidder. You then get 12 minutes to decide if you want to do it or not.

Both steps are proffers. That's the big takeaway.

Bucking Bar

Thank you. Well stated.

NuGuy

Everything in ARCOS is logged and accessible by the Scheduling Committee, including phone contact. They can even listen to the phone message that is left if your phone picks up.

hockeypilot44

What happens if you check no to autoaccept, but yes to auto ackowledge?

Redbird611

I'm considering putting in a blanket green slip with do not call hours during the evening when I really don't want to be teased, say 2300-0600 for example. I would then have a second green slip at lower priority with auto-accept "Yes" and auto-acknowledge "No", likely with some trip parameter restrictions. I'm thinking that should allow me to look at proffers during the daytime but limit being bothered needlessly at night.

All 5 Stages

My rep says that the MEC voted 9-8 to approve the grievance settlement.

A5S

dragon

There is a joint letter out from the some of the LECs detailing more of this hideous agreement.

As you have read in Contract Awareness Bulletin 23-03, the MEC chair settled an MEC grievance regarding the improper use of PWA Section 23.M.7 (herein, 23.M.7). In return for the Company’s promise not to invoke 23.M.7 outside of eight hours to trip report (unless approved by the Scheduling Committee chair), and another promise to properly pay the pilot harmed by any use of 23.M.7, the MEC chair conceded to the elimination of ARCOS batches and associated batch size penalties. We find this to be an ill-advised, rushed, and strategically flawed concessionary settlement that will be detrimental to line pilots.

Recall that on April 30 and May 1 of 2022, the Company abandoned long-standing scheduling practices by egregiously violating the intent of 23.M.7. Historically, it had been used only for individual flights or rotations subject to cancellation because Delta Scheduling could not find a pilot in time—not simply as a shortcut to ease their trip-coverage workload. However, on April 30 and May 1, the Company invoked 23.M.7 for next-day trip coverage, abrogating seniority and violating the contractual rights of pilots with valid green slips and white slips in place.

At the time, ALPA rightly responded by sending the Company a “cease and desist” letter and distributing MEC Brief 22-07, Flight Ops Staffing Plan: Abrogate Seniority. Additionally, ALPA published MEC Brief 22-08, History and Past Practice 23.M.7, a document signed by eight former Scheduling Committee chairs and a former Negotiating Committee chair discussing 23.M.7 established practice. That document also made it clear that the Company had admitted to their “mistake” and had promised to refrain from abusing 23.M.7 in the future.

To no one’s surprise, management reneged on that promise. In fact, management has willfully and systematically violated our new contract before the ink has even dried in multiple ways. For example:

The Company has failed to consistently provide bid packages to ALPA for review five days prior to bids opening, as required (23.B)
The Company is refusing to provide positive space following reroute, as negotiated (23.L.15)
The Company is systematically not paying the proper pilot when abrogating the trip-coverage ladder (23.M.7)

Management handles trivialities like lanyard and hat rules as if they are solemnly enshrined laws, while simultaneously treating our legally binding contractual protections as mere suggestions to be followed only when convenient for them. While management’s lack of integrity is nothing new, it is only getting worse as they become ever more brazen in their blatant disregard for our PWA. With the summer operational pressures building, we expect that management will continue to violate their own Rules of the Road whenever it suits them, as they have so often done in the past. With that in mind, let’s address the 23.M.7 grievance settlement.

The MEC chair is authorized per the Delta MEC policy manual to settle grievances on behalf of the MEC. However, when the stakes are high (such as with group grievances that affect all pilots), the MEC is almost always consulted for direction prior to ALPA entering into a grievance settlement agreement. That practice is consistent with bottom-up governance and ensures that no important and necessary provisions are overlooked.

In this case, the topic was only briefly touched upon at the March MEC meeting, and the MEC expressed a willingness to consider a settlement, provided it adequately limited the Company’s use of 23.M.7 and had no concessions. Instead, and without further MEC input, the MEC chair produced a final settlement that diverged from the MEC’s original vision to an alarming degree. This kind of top-down governance has caused significant problems for Delta pilots in the past, and we are concerned that abandoning bottom-up governance is once again harming Delta pilots by taking their elected union representatives out of the decision-making process until it is too late to viably change course.

We’d like to emphasize that 23.M.7 was never intended to be used indiscriminately. Following repeated Company abuses of this PWA clause (contrary to their promises to stop the behavior), the MEC filed a grievance to limit its use to unusual circumstances, as originally intended. Subsequently, the MEC chair entered into settlement talks and agreed to the following grievance settlement:

Immediate elimination of ARCOS batch sizes
Unlimited use of 23.M.7 inside of eight hours to report
Management promises not to invoke 23.M.7 beyond eight hours to trip report unless receiving prior written approval from the Delta MEC Scheduling chair
Management promises to produce a manually generated list showing every instance of 23.M.7 use, and list the bypassed pilot who was paid
Management promises to automate the 23.M.7 report and payment process by June 2024

Make no mistake, the Company has been contractually compelled to identify and pay the bypassed 23.M.7 pilot this entire time but has repeatedly failed to comply. Consequently, the MEC chair’s settlement has resulted in Delta pilots essentially renegotiating for a right we already had! In so doing, the MEC chair has immediately put the Company into compliance, rewarding them for failing to do what they had been obligated to do all along.

In theory, this agreement places new restrictions on the Company’s use of 23.M.7 as a scheduling tool and provides ALPA with new visibility on the process to ensure that affected pilots are properly paid. However, we see several problems with this theoretical solution, which is why we argued against it in session, and remain opposed.

In broad terms, the MEC granted an immediate and sizable concession to the Company (eliminating batch sizes), in exchange for nothing more than a few promises. Batch sizes will effectively be set at Company discretion; “at Company discretion” never works out well for us. Based upon management’s historic and well-documented inability to keep its deals, we have no confidence that they will uphold their end of the bargain. Furthermore, this settlement does nothing to address the Company’s practice of running concurrent steps of coverage (GS & IA), which is also contrary to our PWA. More specifically, our concerns are:

The complete and immediate elimination of batch sizes during ARCOS callouts is a major win for management, and a major concession for Delta pilots; this was not a win/win outcome. It is extremely disappointing that the MEC conceded batch sizes after spending considerable negotiating capital to secure batch size restrictions and contractual remediation in both LOA 20-04 and C2019. With this restriction gone, the Company will be able to shotgun ARCOS calls to every eligible pilot with a qualifying white slip or green slip request—every single time the Company deploys ARCOS. “Auto Accept” and “Auto Acknowledge” features may reduce the number of ARCOS calls a pilot receives. However, these options have their own limitations and risks, and will require significantly more time for pilots to properly input their parameters, compared to blanket slip requests. In short, we have conceded substantial flexibility to management, to the detriment of our own QOL and convenience.

With ARCOS batch sizes for all intents and purposes eliminated, so too is the 2:00 batch size exceedance penalty. If management delays implementation of automated 23.M.7 coverage reports, or disregards them completely, then there is no recourse for us aside from filing another time-consuming grievance (opening pilots to the risk of another concessionary MEC chair–directed settlement like this one). In short, based on hard-earned experience, we know the Company cannot always be trusted to keep its deals.

Neither guardrails, a pulldown provision, nor remediation (penalties for noncompliance) were negotiated in this settlement. Of particular concern, this settlement does nothing to define “schedule integrity;” therefore, management can continue to apply it without restraint.

This settlement codifies unlimited use of 23.M.7 within eight hours of report, and therefore pilots are effectively precluded from grieving any use of 23.M.7 within eight hours of report in the future. If management holds every open trip until eight hours to report, they could cover every trip using 23.M.7, and we would have no recourse. This is significant, because the MEC chair conducted zero analysis of pertinent data concerning 23.M.7 abuse prior to reaching this agreement. If (hypothetically) 90% of current 23.M.7 abuse occurs within eight hours, then the value of this settlement to the pilot group is minimal. Without this basic data, we are flying blind. The MEC chair approved this settlement without taking the time and effort to perform the research necessary to evaluate the impact it will have on Delta pilots now and in the future despite being in the “time” bucket. Would the new trip coverage timeline that started on June 2 have provided a solution to the problem? We’ll never know. There was no need to skip the most basic level of due diligence to rush this settlement.


While there was room to negotiate increased batch sizes in this settlement, eliminating them altogether was a poor strategic decision with lasting, if not permanent, consequences. There is always risk involved when filing grievances; we have found that arbitration is not as clear-cut as we would like. There were certainly legitimate differences of opinion about our chances of prevailing in the 23.M.7 grievance, and our ability to improve the terms of this settlement. (The best opportunity to improve it, of course, would have been prior to the MEC chair agreeing to it and backing the MEC into a corner.)

For us, the most disappointing aspect of this settlement is that it did not need to happen this way, and it highlights a major flaw in our internal processes. While the policy manual gives the MEC chair latitude to negotiate settlements, it also opens the door to risks, such as the Company inducing artificial time pressure to get a deal done, and the potential for the MEC chair to act outside the MEC’s guidance. There can be no doubt that pilots are better served when the MEC is fully involved from the beginning of the process, rather than getting a settlement dropped in our laps as a “take it or leave it” proposition only after settlement negotiations are complete.

PWA revisions of this magnitude are typically the result of a letter of agreement negotiation, and then subject to membership ratification. However, in this case, the MEC chair settled the grievance outside of the parameters agreed to by the MEC, took a closed session MEC vote to move forward with the settlement without seeking improvements, and refused to send it to the pilots for approval. This lack of transparency and accountability is an unwelcome and ominous throwback to the “bad ol’ days” of top-down DALPA governance. In any case, PWA Section 23.Z.1 has been functionally eliminated.

Fundamentally, this settlement gives a green light to management to continue running the airline at redline, to violate the PWA at will—and be rewarded for doing so—while further eroding pilot quality of life. As ugly as this summer is shaping up to be, our concern is that this settlement will only exacerbate the problem. The settlement does nothing to improve our QOL; however, it does help solve management’s self-induced problems heading into the busy summer season and beyond.

In summary, we believe that this rushed, ill-advised grievance settlement will be detrimental to the pilot group. Work rules, once given away, are extremely difficult to reacquire. Had the MEC chair sought MEC direction prior to agreeing to settlement terms, as has happened in the past, the decision-making authority would have stayed with the MEC, where it belongs. This agreement sets the stage for management to further employ abusive scheduling practices just as summer flying heats up. We ask you to stay safe and be vigilant. If you see the Company violating scheduling rules, call and ask them to fix the problem. If it’s not fixed, that call will stop the 120-day grievance clock—and report it via the ACE app. Continually evaluate your fitness for duty.

As always, please reach out to us with any questions or feedback.

In unity,