C44 Recall
06-10-2024, 03:22 AM
#291
Moderator
Joined APC: Jul 2006
Posts: 5,807
The proponents of the 23m7/batch size deal have been awfully quiet as of late. They were on SM screaming that "something" had to be done and apparently didn't care about anything other than getting rid of batch sizes. They also completely discounted anyone who opposed it as the "local who want their GS." Many of us knew this was a terrible deal from the start, we didn't need a year to see the light. I've said it from the beginning, I'd have been ok with tightening up the batch sizes if we hadn't just completely given them away, AND we actually received something of substance in return. So far what have we gotten, a report we don't have any way to verify it's accuracy? I think before anyone gets voted in as a rep, there should be a deep dive on this topic and their participation in this agreement.
06-10-2024, 08:41 AM
#292
Gets Weekends Off
Joined APC: Apr 2018
Posts: 3,238
Exactly. The PB day fiasco played out like a game of good cop, bad cop. One upper level manager “reinterpreted” PB days. Another upper level manager demonstrated a faux “good working relationship” by reinstating the contractual intent of PB days. DH is patting himself on the back for maintaining such a positive relationship. He might even accept management’s proposed settlement on a future conflict, so as not to jeopardize this “good working relationship”.
You summed it up best. Following the PWA in the first place is management’s only opportunity to maintain a good working relationship. We don’t have that today. We need reps who truly understand that.
You summed it up best. Following the PWA in the first place is management’s only opportunity to maintain a good working relationship. We don’t have that today. We need reps who truly understand that.
06-10-2024, 09:37 AM
#293
Bus driver
Joined APC: Aug 2007
Posts: 838
The sad part is the majority of guys I actually meet at work have no idea what the PR/PB day fiasco even was when I explain it to them. Only people who are engaged on here or the FB groups really know what the company tried to pull. I feel like ALPA should at least publish something explaining exactly what the company did and tried to do. Just so that these pilots are educated and know exactly what kind of management that we're working with.
06-10-2024, 11:09 AM
#294
Gets Weekends Off
Joined APC: Mar 2015
Position: stake holder ir.delta.com
Posts: 10,456
First and foremost, we were squarely in the time bucket. C44 treated 23.M.7 like a massive, uncontained fire that required getting the plane down on the nearest piece of asphalt immediately.
I would have proposed that we accelerate efforts to take full advantage of the direct API access provided by C19. By fully developing ACE (or an equivalent product), we could have drastically decreased the number of 23.M.7 incidents that were going unpaid. In doing so, we’d be driving up the company’s costs as well as their urgency to reach a deal.
In the interim, an arbitrator could have ruled that the company may use 23.M.7 at any time it desires (the “worst” case scenario for us). With fully automated enforcement, that would have given the company free rein to triple their coverage costs for any trip. Have at it.
Next, I’d have SMEs meet with the negotiating committee to appropriately value the deal. Again, no urgency on our end. The longer this goes on, the closer enforcement gets to 100%, the more it costs the company. Once the negotiating committee establishes a fair and accurate value, they can meet with company counterparts to discuss an LOA with an appropriate quid. If a fair deal is reached, it would go to the MEC for a vote, followed by MEMRAT.
I would have proposed that we accelerate efforts to take full advantage of the direct API access provided by C19. By fully developing ACE (or an equivalent product), we could have drastically decreased the number of 23.M.7 incidents that were going unpaid. In doing so, we’d be driving up the company’s costs as well as their urgency to reach a deal.
In the interim, an arbitrator could have ruled that the company may use 23.M.7 at any time it desires (the “worst” case scenario for us). With fully automated enforcement, that would have given the company free rein to triple their coverage costs for any trip. Have at it.
Next, I’d have SMEs meet with the negotiating committee to appropriately value the deal. Again, no urgency on our end. The longer this goes on, the closer enforcement gets to 100%, the more it costs the company. Once the negotiating committee establishes a fair and accurate value, they can meet with company counterparts to discuss an LOA with an appropriate quid. If a fair deal is reached, it would go to the MEC for a vote, followed by MEMRAT.
The problem was reps were getting calls to shutdown the IA side deals and blanket WS 23.M.7. slot machine. We are our worst enemy sometimes.
06-10-2024, 11:18 AM
#295
Gets Weekends Off
Joined APC: Mar 2015
Position: stake holder ir.delta.com
Posts: 10,456
Reps are recalled all the time when they do things contrary to the majority's desires. The 2 previous carriers I flew for rarely had anyone finish ALPA work on term. The bad actors were recalled and the good actors were re-elected until they did something bad. Terms are a review process while recalls and elections reflect the majority's will.
06-10-2024, 01:24 PM
#296
Gets Weekends Off
Joined APC: Jan 2016
Posts: 106
Not to address the main complaint, but the MEC chair has nothing to do with council business. There is literally no mechanism for any MEC officer involvement in any council affairs, nor would you want it that way, unless that officer was acting as an individual member and happened to be a member of that council.
06-10-2024, 03:08 PM
#297
Gets Weekends Off
Joined APC: Oct 2023
Posts: 161
The sad part is the majority of guys I actually meet at work have no idea what the PR/PB day fiasco even was when I explain it to them. Only people who are engaged on here or the FB groups really know what the company tried to pull. I feel like ALPA should at least publish something explaining exactly what the company did and tried to do. Just so that these pilots are educated and know exactly what kind of management that we're working with.
06-10-2024, 03:24 PM
#299
Gets Weekends Off
Joined APC: Mar 2015
Position: stake holder ir.delta.com
Posts: 10,456
Scheduling never calls to notify. Scheduling calls to notify during rest. Scheduling calls to notify on a day of training. Scheduling stitches together a 30 hour rest period AFTER the pilot already entered a less than 30 hour rest.
We have way too many pilots who just see a notification in Micrew and hit acknowledge, thus putting themselves on the hook for the assignment and relieving scheduling of having to actually do their job at the proper time (while a pilot is in a contactable status). I no-showed about 3 rotations last year due to improper notification. Once scheduling put the pieces together they admitted their error each time and I never heard another word about it.
We have way too many pilots who just see a notification in Micrew and hit acknowledge, thus putting themselves on the hook for the assignment and relieving scheduling of having to actually do their job at the proper time (while a pilot is in a contactable status). I no-showed about 3 rotations last year due to improper notification. Once scheduling put the pieces together they admitted their error each time and I never heard another word about it.
06-10-2024, 03:38 PM
#300
Gets Weekends Off
Joined APC: Oct 2023
Posts: 161
Thread
Thread Starter
Forum
Replies
Last Post
