Go Back  Airline Pilot Central Forums > Airline Pilot Forums > Major > Delta
Prepare yourselves… 2023 AEs >

Prepare yourselves… 2023 AEs

Search

Notices

Prepare yourselves… 2023 AEs

Thread Tools
 
Search this Thread
 
Old 10-23-2023, 04:05 AM
  #5561  
Rerouted On Weekends
 
Jaww's Avatar
 
Joined APC: Oct 2015
Position: 717A
Posts: 2,937
Default

Not to mention that the company didn’t implement VB within the prescribed time period and ALPA was fully within its rights to cancel the agreement because of that. Don’t leave that part out. If it was so important to delta you think they would have acted on it in the required time period.
Jaww is offline  
Old 10-23-2023, 04:46 AM
  #5562  
Gets Weekends Off
 
Joined APC: Jan 2020
Posts: 379
Default

Originally Posted by TED74
Not a ridiculous fallacy, despite your hyperbole. The company wanted VBs in order to reduce credit. Credit in most cases increases the quality of rotations. It’s what front- and back-end deadheads have. It’s what easy green slips have. It’s what easy reserve assignments have. Outside of contractual provisions the company may or may not follow, credit is the last buffer that keeps the optimizer from completely destroying quality of life for those of us who don’t favor hard time trips.

TDYs and VBs would have pulled credit out of the system - from all bases, and it would have given the optimizer more options to sodomize. For anyone living in or near MCO flying the 7ER, it probably would have been a pretty good gig. For everyone else, it probably would have made things just a little worse. In the end, more pilots preferred not to risk the experiment and the MEC executed the will of the majority. The company had a year to try VBs and TDYs and never did. We pulled it down just like the company could have pulled it down.

Nothing ridiculous, nothing crazy. The big bad ATL boogeymen didn’t go rogue. If the company wants a Florida pilot base, they can open one at any time.
Sure, it would’ve been great for MCO until Mgmt decided to pull it out of MCO and put it somewhere else. IIRC the language wasn’t strong enough to make sure it stayed in MCO.
igotgummed is offline  
Old 10-23-2023, 04:55 AM
  #5563  
Gets Weekends Off
 
brakechatter's Avatar
 
Joined APC: Aug 2009
Posts: 406
Default

Originally Posted by TED74
Not a ridiculous fallacy, despite your hyperbole. The company wanted VBs in order to reduce credit. Credit in most cases increases the quality of rotations. It’s what front- and back-end deadheads have. It’s what easy green slips have. It’s what easy reserve assignments have. Outside of contractual provisions the company may or may not follow, credit is the last buffer that keeps the optimizer from completely destroying quality of life for those of us who don’t favor hard time trips.

TDYs and VBs would have pulled credit out of the system - from all bases, and it would have given the optimizer more options to sodomize. For anyone living in or near MCO flying the 7ER, it probably would have been a pretty good gig. For everyone else, it probably would have made things just a little worse. In the end, more pilots preferred not to risk the experiment and the MEC executed the will of the majority. The company had a year to try VBs and TDYs and never did. We pulled it down just like the company could have pulled it down.

Nothing ridiculous, nothing crazy. The big bad ATL boogeymen didn’t go rogue. If the company wants a Florida pilot base, they can open one at any time.
Better synopsis. The flying could have been pulled from any one or all bases and was entirely at the discretion of the Company, hence part of the angst the MEC had -- the unknown. The violation of seniority -- having to be on the piece of equipment in order to bid the base -- was additional heartache, although seemingly less of a factor. My personal opinion was the greatest contributor to the pulldown was the lack of progress from the Company over the AM JV negotiations along with a few other areas of leftover frustration from some of the concessions of C2015 that the Company was exploiting (eg Company setting the value of SILs). There were a few reps, including C44 as I recall who wanted to let the process play out for a bit and gather the data of the Company's implementation plans, while seemingly not supporting the ongoing use of VB as directed. They were in the minority. There was also discussion of letting TDYs continue while pulling down VB, but that too did not carry the majority and the whole LOA was pulled -- in an optimal timeframe.

Not to mention that the company didn’t implement VB within the prescribed time period and ALPA was fully within its rights to cancel the agreement because of that. Don’t leave that part out. If it was so important to delta you think they would have acted on it in the required time period.
This is not correct. There was no required timeline that the Company had to meet, although their lack of implementation in a more timely manner was more fodder for the pulldown -- again, based mostly on other factors IMO. Either side could pull down part or all of the agreement with the required notice, I think it was 45 days but that penguin might have fallen off of the iceberg.
brakechatter is offline  
Old 10-23-2023, 04:59 AM
  #5564  
Gets Weekends Off
 
Joined APC: Sep 2015
Position: UNA
Posts: 4,657
Default

Originally Posted by brakechatter
Better synopsis. The flying could have been pulled from any one or all bases and was entirely at the discretion of the Company, hence part of the angst the MEC had -- the unknown. The violation of seniority -- having to be on the piece of equipment in order to bid the base -- was additional heartache, although seemingly less of a factor. My personal opinion was the greatest contributor to the pulldown was the lack of progress from the Company over the AM JV negotiations along with a few other areas of leftover frustration from some of the concessions of C2015 that the Company was exploiting (eg Company setting the value of SILs). There were a few reps, including C44 as I recall who wanted to let the process play out for a bit and gather the data of the Company's implementation plans, while seemingly not supporting the ongoing use of VB as directed. They were in the minority. There was also discussion of letting TDYs continue while pulling down VB, but that too did not carry the majority and the whole LOA was pulled -- in an optimal timeframe.



This is not correct. There was no required timeline that the Company had to meet, although their lack of implementation in a more timely manner was more fodder for the pulldown -- again, based mostly on other factors IMO. Either side could pull down part or all of the agreement with the required notice, I think it was 45 days but that penguin might have fallen off of the iceberg.
I was under the impression flying had to be pulled from the base the pilot bid from. EG if MCO7ER had been 50% ATL pilots, 35% NYC pilots and 15% DTW pilots, that’s the breakdown of flying that MCO would have had to had.

but kinda moot anyway as no base owns flying.
Gone Flying is offline  
Old 10-23-2023, 05:14 AM
  #5565  
Moderator
 
Joined APC: Dec 2007
Position: DAL 330
Posts: 7,000
Default

Originally Posted by Gone Flying
I was under the impression flying had to be pulled from the base the pilot bid from. EG if MCO7ER had been 50% ATL pilots, 35% NYC pilots and 15% DTW pilots, that’s the breakdown of flying that MCO would have had to had.

but kinda moot anyway as no base owns flying.

That is the way I remember it also. IMHO it was a missed opportunity - All DALPA had to do was insist the unilateral pull down capability was permanent. If the company would not agree to that then - No Deal. If the company did agree to that it would have allowed DALPA to continually decide if it was beneficial to the Pilots or not.

The potential disruption to the flying distribution was never understood by a lot of Pilots and was exploited by those who did not want this. The reduction in "credit time" via DHs was real, but we will never know the extent and how it might have affected the Pilot group as a whole.

In any case I believe the Union pulled it down as part of a bigger strategic move and that's fine, but it would have been nice to have tried it if we kept the unilateral pull down capability.

Scoop
Scoop is offline  
Old 10-23-2023, 06:06 AM
  #5566  
Gets Weekends Off
 
Joined APC: Oct 2014
Posts: 905
Default

Originally Posted by brakechatter
This is not correct. There was no required timeline that the Company had to meet, although their lack of implementation in a more timely manner was more fodder for the pulldown -- again, based mostly on other factors IMO. Either side could pull down part or all of the agreement with the required notice, I think it was 45 days but that penguin might have fallen off of the iceberg.
MOU 16-03 was signed with the contract and effective on 12/1/16. Paragraph 4.A. stated it was effective for 1 year unless extended. No action was taken to extend, and the company didn’t announce a virtual base until June 2018. So while alpa just exercised their pulldown language, had that not been there they could have shut it down because the MOU was expired.
bugman61 is offline  
Old 10-23-2023, 06:19 AM
  #5567  
Rerouted On Weekends
 
Jaww's Avatar
 
Joined APC: Oct 2015
Position: 717A
Posts: 2,937
Default

Originally Posted by bugman61
MOU 16-03 was signed with the contract and effective on 12/1/16. Paragraph 4.A. stated it was effective for 1 year unless extended. No action was taken to extend, and the company didn’t announce a virtual base until June 2018. So while alpa just exercised their pulldown language, had that not been there they could have shut it down because the MOU was expired.
Thanks bug. It’s amazing how quickly people forget.
Jaww is offline  
Old 10-23-2023, 06:42 AM
  #5568  
Gets Weekends Off
 
Joined APC: Jul 2022
Posts: 947
Default

Originally Posted by Scoop
That is the way I remember it also. IMHO it was a missed opportunity - All DALPA had to do was insist the unilateral pull down capability was permanent. If the company would not agree to that then - No Deal. If the company did agree to that it would have allowed DALPA to continually decide if it was beneficial to the Pilots or not.
Exactly. Our pull down language gave us plenty of control. We could have asked for permanent pull down language, more control over monthly VB parameters, and an additional quid as well. Instead, ALPA simply pulled the whole thing prematurely out of irrational fear.

Originally Posted by TED74
The company wanted VBs in order to reduce credit.
What happened very soon after the VB/TDY MOU was pulled? The largest reduction in credit this pilot group has ever seen. The company didn’t need VBs to do it.
ancman is offline  
Old 10-23-2023, 07:00 AM
  #5569  
Gets Weekends Off
 
brakechatter's Avatar
 
Joined APC: Aug 2009
Posts: 406
Default

Originally Posted by Jaww
Thanks bug. It’s amazing how quickly people forget.
Didn't forget anything. The team that negotiated it did. Stand by my post, except to clarify that the company could not just unilaterally pull time from any base, while at the same time being in complete control of the outcome of where the time came from, if any. Somewhat akin to the AE process.
Neither was the point of the post -- in that the pulldown was not some mentality to protect the PTC mafia.
brakechatter is offline  
Old 10-23-2023, 07:34 AM
  #5570  
Gets Weekends Off
 
Joined APC: Sep 2014
Posts: 4,999
Default

Originally Posted by ancman

What happened very soon after the VB/TDY MOU was pulled? The largest reduction in credit this pilot group has ever seen. The company didn’t need VBs to do it.
Of course they didn’t need VBs to reduce credit. Had we given them VBs, it would have been even worse.

Any other straw men?
TED74 is offline  
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
ColoradoAviator
Delta
3697
10-28-2022 04:00 AM
Trip7
Delta
3969
11-02-2021 08:57 AM
jsfBoat
Career Questions
2
05-12-2011 06:25 PM
Joachim
Regional
7
10-23-2007 05:06 PM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



Your Privacy Choices