Any "Latest & Greatest" about Delta?
Inventory survival kit ..
Joined: Jul 2008
Posts: 1,069
Likes: 0
From: Seeking no jacket required rotations
Just skimmed the SOT recommendations. Lots of good stuff in there that fnw will recognize. Lots of good new stuff too.
So far my only word of caution is DO NOT LET PS Front End Deviation mutate into SATELLITE basing. PS on front end is a good deal. Satellite basing is NOT.
Otherwise it looks like a job well done, assuming we can write new pwa language without holes.
So far my only word of caution is DO NOT LET PS Front End Deviation mutate into SATELLITE basing. PS on front end is a good deal. Satellite basing is NOT.
Otherwise it looks like a job well done, assuming we can write new pwa language without holes.
I've never filed an amended return. I have no idea how it will work.Hopefully they will just create a special form for us and we won't have to go back and redo the whole tax return. Yikes!
I can't even remember what year we got that notes and claims money. 2007 maybe?
I can't even remember what year we got that notes and claims money. 2007 maybe?
The IRS could very well create a simpler form for the process, but I doubt they will do it because of the relatively few people who will be effected by the change. If you didn't put the claims money in an IRA when you got it, you may have to fill out an 8880 form along with the 1040X. Still a very simple process.
Gets Weekends Off
Joined: Jun 2009
Posts: 5,113
Likes: 0
Sec 23, Y.
I tried cut/pasting it here, but it comes out looking all weird. It does say "It is expected that a pilot will avail himself of Section 23 Y. 2. on a rare basis." so that line isn't new. It also says, "A pilot who has demonstrated a pattern of inability to report as scheduled will be subject to progressive disciplinary action."
The new policy is nice in that 2 hours aren't required between your primary and backup flight.
I tried cut/pasting it here, but it comes out looking all weird. It does say "It is expected that a pilot will avail himself of Section 23 Y. 2. on a rare basis." so that line isn't new. It also says, "A pilot who has demonstrated a pattern of inability to report as scheduled will be subject to progressive disciplinary action."
The new policy is nice in that 2 hours aren't required between your primary and backup flight.
Which disciplinary trigger would you want to be subject to, "a few times during a pilot's career", or "a pattern"?
Gets Weekends Off
Joined: Jun 2009
Posts: 5,113
Likes: 0
Inventory survival kit ..
Joined: Jul 2008
Posts: 1,069
Likes: 0
From: Seeking no jacket required rotations
Sec 23, Y.
I tried cut/pasting it here, but it comes out looking all weird. It does say "It is expected that a pilot will avail himself of Section 23 Y. 2. on a rare basis." so that line isn't new. It also says, "A pilot who has demonstrated a pattern of inability to report as scheduled will be subject to progressive disciplinary action."
The new policy is nice in that 2 hours aren't required between your primary and backup flight.
I tried cut/pasting it here, but it comes out looking all weird. It does say "It is expected that a pilot will avail himself of Section 23 Y. 2. on a rare basis." so that line isn't new. It also says, "A pilot who has demonstrated a pattern of inability to report as scheduled will be subject to progressive disciplinary action."
The new policy is nice in that 2 hours aren't required between your primary and backup flight.
Gets Weekends Off
Joined: Jun 2009
Posts: 5,113
Likes: 0
Just skimmed the SOT recommendations. Lots of good stuff in there that fnw will recognize. Lots of good new stuff too.
So far my only word of caution is DO NOT LET PS Front End Deviation mutate into SATELLITE basing. PS on front end is a good deal. Satellite basing is NOT.
Otherwise it looks like a job well done, assuming we can write new pwa language without holes.
So far my only word of caution is DO NOT LET PS Front End Deviation mutate into SATELLITE basing. PS on front end is a good deal. Satellite basing is NOT.
Otherwise it looks like a job well done, assuming we can write new pwa language without holes.
If a lousy trip is coming up, and I'm the senior-most on Reserve, and there are two of us available, the junior guy might have flown 1/2 hour more than me, and be in the next lower bucket. If 35 points was the size of all buckets, it means that, at the most, the next guy below me would be about a three-day trip away. If they have smaller buckets, it means that I might be up next if I've flown anywhere between 1/2 hr and maybe one two-day trip, less than the junior most guy. As you get closer and closer to the end of the month, if bucket sizes don't get bigger then I might have to go out on a lousy 4-day trip, over 1/2 hour differential, and hit 67 hours for the month, while the guy directly behind in RAW score sits tight at 45 hours (for example).
It's still a long, long way from a purely seniority-based Reserve system.
Still, it's step in the right direction. The return of the high and low yellows would be welcome. The problem is that there is still no meaningful penalty (to the company) or reward (to us) for overusing SC assignments.
Inventory survival kit ..
Joined: Jul 2008
Posts: 1,069
Likes: 0
From: Seeking no jacket required rotations
The Reserve language is a little weak. 5 points is too small a change to the RAW score for a SC (I equate 1 hour of flying to about 2 points change in RAW score). Letting the company float RAW "bucket" sizes is equivalent to letting them float anything, such as the Reserves Required vs. Available. It rarely works well for us.
If a lousy trip is coming up, and I'm the senior-most on Reserve, and there are two of us available, the junior guy might have flown 1/2 hour more than me, and be in the next lower bucket. If 35 points was the size of all buckets, it means that, at the most, the next guy below me would be about a three-day trip away. If they have smaller buckets, it means that I might be up next if I've flown anywhere between 1/2 hr and maybe one two-day trip, less than the junior most guy. As you get closer and closer to the end of the month, if bucket sizes don't get bigger then I might have to go out on a lousy 4-day trip, over 1/2 hour differential, and hit 67 hours for the month, while the guy directly behind in RAW score sits tight at 45 hours (for example).
It's still a long, long way from a purely seniority-based Reserve system.
Still, it's step in the right direction. The return of the high and low yellows would be welcome. The problem is that there is still no meaningful penalty (to the company) or reward (to us) for overusing SC assignments.
If a lousy trip is coming up, and I'm the senior-most on Reserve, and there are two of us available, the junior guy might have flown 1/2 hour more than me, and be in the next lower bucket. If 35 points was the size of all buckets, it means that, at the most, the next guy below me would be about a three-day trip away. If they have smaller buckets, it means that I might be up next if I've flown anywhere between 1/2 hr and maybe one two-day trip, less than the junior most guy. As you get closer and closer to the end of the month, if bucket sizes don't get bigger then I might have to go out on a lousy 4-day trip, over 1/2 hour differential, and hit 67 hours for the month, while the guy directly behind in RAW score sits tight at 45 hours (for example).
It's still a long, long way from a purely seniority-based Reserve system.
Still, it's step in the right direction. The return of the high and low yellows would be welcome. The problem is that there is still no meaningful penalty (to the company) or reward (to us) for overusing SC assignments.

The old bidding high time and low time at fNW seems like it would be a nice addition too, but not sure how to make that work in conjunction with RAW.
Gets Weekends Off
Joined: Feb 2006
Posts: 1,242
Likes: 0
Just skimmed the SOT recommendations. Lots of good stuff in there that fnw will recognize. Lots of good new stuff too.
So far my only word of caution is DO NOT LET PS Front End Deviation mutate into SATELLITE basing. PS on front end is a good deal. Satellite basing is NOT.
Otherwise it looks like a job well done, assuming we can write new pwa language without holes.
So far my only word of caution is DO NOT LET PS Front End Deviation mutate into SATELLITE basing. PS on front end is a good deal. Satellite basing is NOT.
Otherwise it looks like a job well done, assuming we can write new pwa language without holes.
Gets Weekends Off
Joined: Jun 2009
Posts: 5,113
Likes: 0
It's a shame that many plan to avoid Reserves, because it introduces a hurdle that we all need to jump before we want to upgrade. It's a penalty on our advancement.
Under the old rules, some worried about being senior enough to hold Reserve...
Thread
Thread Starter
Forum
Replies
Last Post




