![]() |
Originally Posted by ShegotheD
(Post 3966252)
Does anyone else feel like we should have gotten something in exchange for QS... Not sure we needed to create a fix for the company violating the contract without getting something in return.
For Example.. Let's get rid of Sick Lookback for good, or sick verification, or GFB. This is just like batch sizes; we get nothing in return. |
Originally Posted by ShegotheD
(Post 3966252)
Does anyone else feel like we should have gotten something in exchange for QS... Not sure we needed to create a fix for the company violating the contract without getting something in return.
For Example.. Let's get rid of Sick Lookback for good, or sick verification, or GFB. This is just like batch sizes; we get nothing in return. That’s alot more than nothing |
Originally Posted by Puddytatt
(Post 3966254)
If sick time doesn't go towards your lookback, then you aren't required to verify it. By not having it count towards lookback, it by default also was suspending the verification requirement. GFB verification is still there under 24-32 and this MOU.
IMHO, settling the sick grievance without putting further restraints on GFB was a mistake. “General nature of the illness” needs to be removed from all verification requirements as well. |
Originally Posted by ShegotheD
(Post 3966252)
Does anyone else feel like we should have gotten something in exchange for QS... Not sure we needed to create a fix for the company violating the contract without getting something in return.
For Example.. Let's get rid of Sick Lookback for good, or sick verification, or GFB. This is just like batch sizes; we get nothing in return. |
Originally Posted by ancman
(Post 3966257)
It’s funny watching people split hairs over the lookback when the company can arbitrarily demand verification for any and every sick call under GFB.
IMHO, settling the sick grievance without putting further restraints on GFB was a mistake. “General nature of the illness” needs to be removed from all verification requirements as well. Very few GFB calls go out to non probationary pilots. Maybe that will temporarily change, but with telehealth for all, is it really that hard to get a teachers note? |
Originally Posted by ShegotheD
(Post 3966252)
For Example.. Let's get rid of Sick Lookback for good, or sick verification, or GFB.
are you new? |
Originally Posted by FangsF15
(Post 3966259)
Meh. I do find it childish, annoying, and invasive, and think it should go away, but I also don’t ever have an issue with answering a GFB call, so that’s fine with me.
Very few GFB calls go out to non probationary pilots. Maybe that will temporarily change, but with telehealth for all, is it really that hard to get a teachers note? |
Originally Posted by ancman
(Post 3966257)
It’s funny watching people split hairs over the lookback when the company can arbitrarily demand verification for any and every sick call under GFB.
IMHO, settling the sick grievance without putting further restraints on GFB was a mistake. “General nature of the illness” needs to be removed from all verification requirements as well. |
Originally Posted by Viper25
(Post 3966262)
With QHCP + Telehealth for GFB verification, at company cost, I’m not sure how much the company will love spamming GFB.
QHCP + Telehealth also lowers the company’s GFB costs. Especially if a pilot’s only convenient option for an MD-signed certificate was an ER visit previously. |
Originally Posted by ancman
(Post 3966257)
It’s funny watching people split hairs over the lookback when the company can arbitrarily demand verification for any and every sick call under GFB.
|
Originally Posted by ancman
(Post 3966265)
The company won’t even blink an eye at having to pay a bunch of $100 telehealth bills. That’s a microscopic fraction of the overall cost of a sick call.
QHCP + Telehealth also lowers the company’s GFB costs. Especially if a pilot’s only convenient option for an MD-signed certificate was an ER visit previously. |
Originally Posted by OOfff
(Post 3966268)
does your city not have an urgent care office? who goes to the emergency room for a sick note?
|
Originally Posted by FL370esq
(Post 3966266)
Me thinks arbitrarily demanding verification for any and every sick call would run counter to the GF portion of GFB. 😁
I don’t see the MOU as a “win.” I see it as closing one can of worms and opening a couple of new ones. I really wish this bandaid fix would have been saved for leverage in upcoming contract negotiations. |
Originally Posted by ancman
(Post 3966271)
Anyone who wants to maximize the company’s expense for using GFB. Which should be everyone on property.
if you want to drive up costs, though, why not just stay out longer on your sick call which now doesn’t count for lookback? |
Originally Posted by Viper25
(Post 3966205)
The coverage tool (IA) right now is an easy button. The new easy button will honor seniority, minimize dealmakers, and guarantee 23M7 pay with automation. Old ways and new ways were both easy buttons, and until they automate ARCOS moving automatically through pilots, or decide to cover trips in a meaningful timeline, they will overpay for things that used to be much cheaper. I don’t think they want to keep paying 3X forever, even if they have for the past year+.
Before you tell me about the timeline for implementation, I don’t really care because in the meantime it is status quo (IA shenanigans) PLUS no sick lookback and verification. Easy buttons the old ways vs the new way. They’re both easy buttons. The new way is better for us. |
Originally Posted by notEnuf
(Post 3966276)
This MOU conflates sick and coverage to say we got sick as a "get" for coverage issues is disingenuous. They did this to solve two separate (multiple) grievance issues. They were completely independant until this MOU combined them to show a "gain." The horse is dead but next summer I reserve the right to revive it and say I told you so when phones are blowing up and people are sick of answering the calls for trips they will never hold.
|
Originally Posted by OOfff
(Post 3966275)
i guess i don’t see “driving up costs” as a universal benefit to me, nor do i think my petty crusade is worth taking up emergency room space.
if you want to drive up costs, though, why not just stay out longer on your sick call which now doesn’t count for lookback? And yes, not calling in well until you are 100% certain that you are 100% well is essential (as with any sick call). |
Originally Posted by FangsF15
(Post 3966259)
Meh. I do find it childish, annoying, and invasive, and think it should go away, but I also don’t ever have an issue with honestly answering a GFB call, so that’s fine with me.
Very few GFB calls go out to non probationary pilots. Maybe that will temporarily change, but with telehealth for all, is it really that hard to get a teachers note? GFB has been used extensively across the entire pilot group in years past. |
Some folks weren't here for past contracts, and may not understand the special place Pilot Sick has in the heart of the company. They HATE it. With a passion. (At least in part, because we have pilots who abuse it. To what degree is beyond the point). IMO, the company over-reacts to that 'abuse', but the point is the company has an absolute burr up their backside over sick.
It was one of their major gatekeeper issues in C15. At the time, we had voluntary verification of sick (but foolishly gave that back in C19 because somehow self-reporting/documenting was too onerous on their admin folks). C15 required a MD note after 160 hours, but also had a provision where the company could always mandate an MD note. We are the only major carrier (I am aware of) who has GFB in their contract, much less an over-30-day medical records disclosure clause. C15 also tightened up the language on mandating a "bonafide relationship", where your spouse/parent/cousin could no longer write your sick note. It also had exclusion from lookback for 'major bone' or a hospital stay, but not a knee replacement. It was silly. I mean, what valid reason can one give to say that a PA or NP couldn't verify your sickness in some instances? How cynical do you have to be to say, "No, you MUST go to an MD!? C19 did slightly expand the threshold for 'lookback' from 100 hours to 120 hours. All that said, we do have a much larger annual allocation than other companies. We have all these little nuance rules and exclusions, all because the company hates sick and wants to create disincentives to using it. My point is that for the company to transition from disputing whether MiCrew 'worked' for sick reporting, to now agreeing to waive sick verification is a BIG deal. That's like Seinfeld's Soup Nazi suddenly not caring how you ordered the soup. Or, like the pilot group suddenly saying "we'll waive PB days for the next couple of months". That in and of itself tells me we had some serious leverage/proof hanging over them, and giving that up should not be dismissed as a small thing - not because of how it's good for us, but for how important it was to the company. |
Originally Posted by immolated
(Post 3966210)
I don't think management wanted this at all. I think they realized they were 2 years behind on 23m payments, still behind on sick automation, etc. and they were backed into a corner. Also schedulers are somewhat cost agnostic, especially during IROPs, which works to our advantage. If they're going to flail and shotgun broken trips during the next IROP at least it has more order and benefit to our side now. And keep in mind this was a settlement agreement they were pressed into, not a voluntary LOA. Also why it didn't go to MEMRAT.
Removing GS trigger is a huge cost. If they really run the summer schedule on only QS as you predict, I'm never going to need to pick up a single hour of single pay again. Awesome. No one will WS and open time will double in size. They will never let that happen but one can dream. You're not thinking through the second-order effects of your scenario. Sorry RES doesn't have a trigger to consider, but that still doesn't make the cost disappear. Also, if this "easy button" is so good for them, why are you now claiming they will drag their feet on implementing it? Either it's great for them and they program it quickly, or they don't like it and put it off until section 6. Pick a side? -both are true they have little ability to get icrew to do what they need it's to antiquated Over a thousand IA went out in the past two years, but according to your logic that never should have happened because they had no easy button. So what was that? Clearly they already had an easy button. We just made it cost more and removed the pre emptive side-deals that made their job easier. -by removing the anti-hassle tool but yeah this will be the new norm The IA calls will be replaced by QS calls. Yes if you're junior you now have no chance of stealing the first few by calling ahead. Sorry. Turn off your QS until the 15th and then you'll get one even at the bottom when it's your turn. That's how it should work. QOL win.- true I'll have to be more selective with my blanket slips |
Originally Posted by ancman
(Post 3966285)
I agree with most of what you wrote. But my point was that we spend a lot of time discussing / negotiating lookback and verification triggers when GFB renders most of it moot.
GFB has been used extensively across the entire pilot group in years past. Maybe they will reevaluate that equation during this period where no verification hours accumulate. Maybe even more so as we near the end of the sick year, and there is virtually no disincentive on a borderline call to not call in sick. But again, it's not that hard to get a legitimate note. |
Originally Posted by notEnuf
(Post 3966293)
I'm over it…..
|
Originally Posted by Gunfighter
(Post 3966212)
I hope the company takes advantage of this easier coverage tool and skips the GS step more often. When CS skips GS by hitting the QS easy button more than they already do with IA it expands the 23M7 financial burden going into negotiations. We have given the entry level CSers an easy button that generates millions of additional pilot value out of the PWA. Every additional QS usage over IA because of the convenience of automation gives us more leverage. If this indeed becomes more widespread than IA it's a huge win for pilots.
|
Originally Posted by notEnuf
(Post 3966293)
I'm over it but it would have been nice to have this debate and give input before the MOU... representative governance and all.
|
Originally Posted by Meme In Command
(Post 3966251)
Set qualifiers and don't just submit a blanket GS.
If you're telling the system "I'm willing to fly literally anything" what do you expect is going to happen? |
Originally Posted by FangsF15
(Post 3966289)
Some folks weren't here for past contracts, and may not understand the special place Pilot Sick has in the heart of the company. They HATE it. With a passion. (At least in part, because we have pilots who abuse it. To what degree is beyond the point). IMO, the company over-reacts to that 'abuse', but the point is the company has an absolute burr up their backside over sick.
It was one of their major gatekeeper issues in C15. At the time, we had voluntary verification of sick (but foolishly gave that back in C19 because somehow self-reporting/documenting was too onerous on their admin folks). C15 required a MD note after 160 hours, but also had a provision where the company could always mandate an MD note. We are the only major carrier (I am aware of) who has GFB in their contract, much less an over-30-day medical records disclosure clause. C15 also tightened up the language on mandating a "bonafide relationship", where your spouse/parent/cousin could no longer write your sick note. It also had exclusion from lookback for 'major bone' or a hospital stay, but not a knee replacement. It was silly. I mean, what valid reason can one give to say that a PA or NP couldn't verify your sickness in some instances? How cynical do you have to be to say, "No, you MUST go to an MD!? C19 did slightly expand the threshold for 'lookback' from 100 hours to 120 hours. All that said, we do have a much larger annual allocation than other companies. We have all these little nuance rules and exclusions, all because the company hates sick and wants to create disincentives to using it. My point is that for the company to transition from disputing whether MiCrew 'worked' for sick reporting, to now agreeing to waive sick verification is a BIG deal. That's like Seinfeld's Soup Nazi suddenly not caring how you ordered the soup. Or, like the pilot group suddenly saying "we'll waive PB days for the next couple of months". That in and of itself tells me we had some serious leverage/proof hanging over them, and giving that up should not be dismissed as a small thing - not because of how it's good for us, but for how important it was to the company. THIS is how you mentor your broccoli haired juniors |
Originally Posted by OOfff
(Post 3966277)
and when they don’t stop awarding green slips, will you also reserve the right to say you were wrong?
|
Sick leave has been a battle since I’ve been here. When I was hired, we didn’t have verification lookback. You went to 75 percent sick leave pay. Then we got the 100 hours of unverified per sick leave year and you could verify whatever you wanted to. Then we voted down something horrible and settled on the 100 hours unverified in previous 12 months with no option to verify. Turned into 120 hours last contract. My point is it is always a battle.
|
Originally Posted by FangsF15
(Post 3966289)
Some folks weren't here for past contracts, and may not understand the special place Pilot Sick has in the heart of the company. They HATE it. With a passion. (At least in part, because we have pilots who abuse it. To what degree is beyond the point). IMO, the company over-reacts to that 'abuse', but the point is the company has an absolute burr up their backside over sick.
It was one of their major gatekeeper issues in C15. At the time, we had voluntary verification of sick (but foolishly gave that back in C19 because somehow self-reporting/documenting was too onerous on their admin folks). C15 required a MD note after 160 hours, but also had a provision where the company could always mandate an MD note. We are the only major carrier (I am aware of) who has GFB in their contract, much less an over-30-day medical records disclosure clause. C15 also tightened up the language on mandating a "bonafide relationship", where your spouse/parent/cousin could no longer write your sick note. It also had exclusion from lookback for 'major bone' or a hospital stay, but not a knee replacement. It was silly. I mean, what valid reason can one give to say that a PA or NP couldn't verify your sickness in some instances? How cynical do you have to be to say, "No, you MUST go to an MD!? C19 did slightly expand the threshold for 'lookback' from 100 hours to 120 hours. All that said, we do have a much larger annual allocation than other companies. We have all these little nuance rules and exclusions, all because the company hates sick and wants to create disincentives to using it. My point is that for the company to transition from disputing whether MiCrew 'worked' for sick reporting, to now agreeing to waive sick verification is a BIG deal. That's like Seinfeld's Soup Nazi suddenly not caring how you ordered the soup. Or, like the pilot group suddenly saying "we'll waive PB days for the next couple of months". That in and of itself tells me we had some serious leverage/proof hanging over them, and giving that up should not be dismissed as a small thing - not because of how it's good for us, but for how important it was to the company. |
Honest question, is the note thing really that big of a deal? The one I've had to provide in over a decade was easy enough and only becuase of a GFB call. If that rate keeps up, having to provide 2 or 3 notes in a 3.5 decade career is a small pain to keep an amazing sick benefit. I wasn't a fan of it initially, but I really don't understand the gnashing of teeth over this. The fact that there was a question about switching to an accumulation model is concerning.
|
Originally Posted by Planetrain
(Post 3966296)
|
The funny thing is a lot of our sick burn the company does to themselves via UMR.
Tore a tendon. Saw doc that day. "you need surgery, and an MRI first just so I have right parts on hand" Took a couple weeks before UMR would approve the MRI. It showed exactly what doc thought it would. Then UMR said we had to try alternative therapy before they'd approve surgery. It's only a realistic option with a 6mm or smaller tear. I had a 14mm tear. The tear got worse, and tendon detached. UMR finally approved "emergency" surgery as I no longer had use of arm. Way more involved, expensive surgery. Same 2 week recovery. But I will likely have to do follow up surgeries because the alternative therapy had a risk and that risk (tendon detachment) came to pass. This would've been under a month and 75ish hours of sick, but turned into 2.5 months and just under 200 hours sick. Delta via UMR caused 125 hours of sick use that if they had just approved the surgery that wouldn't have been needed. This and a previous surgery were needed late in a fiscal quarter, and in both cases as soon as a new quarter hit, surgery approved. Feels like they approve things based on quarterly targets and not medical necessities. |
While we're having the historic discussion, is there a reason the sick year resets on the same month for everyone? At surface level it seems kinda dumb that it doesn't reset on an individuals anniversary.
|
Originally Posted by crewdawg
(Post 3966308)
Honest question, is the note thing really that big of a deal? The one I've had to provide in over a decade was easy enough and only becuase of a GFB call. If that rate keeps up, having to provide 2 or 3 notes in a 3.5 decade career is a small pain to keep an amazing sick benefit. I wasn't a fan of it initially, but I really don't understand the gnashing of teeth over this. The fact that there was a question about switching to an accumulation model is concerning.
|
Originally Posted by CBreezy
(Post 3966298)
Well I mean, what happened is the literal definition of representative governance.
|
Originally Posted by Meme In Command
(Post 3966313)
While we're having the historic discussion, is there a reason the sick year resets on the same month for everyone? At surface level it seems kinda dumb that it doesn't reset on an individuals anniversary.
I wouldn't be surprised if the company didn't want that because they didn't think they could handle the IT of it... |
Originally Posted by notEnuf
(Post 3966315)
So every thing is representative since we have representatives? The root of this is represent. How do they know without discussion or debate what they are representing?
Attend an LEC meeting? |
Originally Posted by notEnuf
(Post 3966307)
If you truly believe this then we should have gotten a much better deal.
|
Originally Posted by FangsF15
(Post 3966316)
That has come up in the past. Many have suggested your sick year resetting on your individual hire month, like APD does.
I wouldn't be surprised if the company didn't want that because they didn't think they could handle the IT of it... I just assumed it was so they could hold up the May sick leave spike as a reason to make our sick leave more onerous during contract negotiations. We already have vacation that resets in April and APD/Pay/everything else that resets on your hire month, so I don't see why it would be stretch for our IT to align it with APD/Pay. |
Originally Posted by FangsF15
(Post 3966322)
Okay, I'll bite. Why do YOU think the company agreed to suddenly flip their position, and suddenly agree to exclude sick verification from July to at least January (6 months) and probably more like March or April (9+ months)?
|
| All times are GMT -8. The time now is 12:06 AM. |
Website Copyright © 2026 MH Sub I, LLC dba Internet Brands