Airline Pilot Central Forums

Airline Pilot Central Forums (https://www.airlinepilotforums.com/)
-   Delta (https://www.airlinepilotforums.com/delta/)
-   -   DALPA C19 Survey (https://www.airlinepilotforums.com/delta/116439-dalpa-c19-survey.html)

Hillbilly 09-05-2018 02:27 AM


Originally Posted by Denny Crane (Post 2668445)
The 12 month look back is used to determine whether you need to verify in the current bid month. Example: I went over 100 hours March 2018. I am required to verify for any sick call with a QHCP. Every month since then, on the the first day of the bid period, I have to type in my DBMS password to acknowledge I must verify by QHCP if I call in sick.



This month 24hrs will drop off and I will be under 100 hrs and go off QHCP. If, in October I call in sick for a 25 hour trip 3-7 October (taking me back over 100 hrs) then call in well for a week then sick out over an 8 day 50 hour trip later in Oct., I will have to verify that 50 hour trip to get paid for it.



Your current month is still part of the 100 hours.



Denny



So when you start October and the 24 hours have dropped off the look back and as a result you no longer have a pop up to acknowledge with your DBMS password for the October bid period and your verification status for the October bid period is shown as NONE, if you call in sick for the first trip in your example your verification status for the October bid period is going to change in the middle of the bid period to QHCP and require you to verify the subsequent sick call in the October bid period ? The amount used in the 12 previous completed bid periods haven’t changed have they?

I may be completely wrong here, but I’m having a difficult time reconciling the examples provided here with the language itself and NN 17-13. I also recall a conversation during TA2 with one of the negotiators that left me with the impression that a verification status only changes bid period to bid period because the lookback that triggers it uses only completed bid periods. That’s why the second sick call in your example wouldn’t have a different verification requirement from the first one. That first sick call in October that takes your up to the minute iCrew display over 100 hours is not a part of a completed bid period. It’s gonna get you for November unless you have more dropping off the lookback than are coming into it, but your verification status for the current bid period should be the same all bid period long.

crewdawg 09-05-2018 04:14 AM


Originally Posted by 80ktsClamp (Post 2668421)
How about let's fix that part of the contract? There will always be the weaker willed.

Unless you're talking a option to click a button or use the VRU to call in sick, then I agree. Otherwise, I think it keeps us from having to waste negotiating capital when we have much bigger issues to fix. I guess I just don't see it as such a big deal compared to many other issues, I would put this WAY down on the list of something I'd like too see "fixed." After improvements in Scope/JV, retirement, medical, reroute, rigs, reserve, DH, Pay banding, vacation, training, DH, recovery flying, rotation construction, paid parking, holiday pay, night pay, distance learning pay.

Han Solo 09-05-2018 04:39 AM


Originally Posted by crewdawg (Post 2668519)
Unless you're talking a option to click a button or use the VRU to call in sick, then I agree. Otherwise, I think it keeps us from having to waste negotiating capital when we have much bigger issues to fix. I guess I just don't see it as such a big deal compared to many other issues, I would put this WAY down on the list of something I'd like too see "fixed." After improvements in Scope/JV, retirement, medical, reroute, rigs, reserve, DH, Pay banding, vacation, training, DH, recovery flying, rotation construction, paid parking, holiday pay, night pay, distance learning pay.

1-button icrew click should just happen, no negotiations. arcos is significantly more costly to implement and it just happened, well so should 1 button sick/well. hopefully it would be implemented just slightly better.

hockeypilot44 09-05-2018 04:44 AM


Originally Posted by Denny Crane (Post 2668445)
The 12 month look back is used to determine whether you need to verify in the current bid month. Example: I went over 100 hours March 2018. I am required to verify for any sick call with a QHCP. Every month since then, on the the first day of the bid period, I have to type in my DBMS password to acknowledge I must verify by QHCP if I call in sick.

This month 24hrs will drop off and I will be under 100 hrs and go off QHCP. If, in October I call in sick for a 25 hour trip 3-7 October (taking me back over 100 hrs) then call in well for a week then sick out over an 8 day 50 hour trip later in Oct., I will have to verify that 50 hour trip to get paid for it.

Your current month is still part of the 100 hours.

Denny

This is wrong. Only looks at previous 12 months. Current month won’t count until next month when a month drops off.

sailingfun 09-05-2018 04:45 AM


Originally Posted by Han Solo (Post 2668533)
1-button icrew click should just happen, no negotiations. arcos is significantly more costly to implement and it just happened, well so should 1 button sick/well. hopefully it would be implemented just slightly better.

The point of ARCOS is to save the company money and improve operational integrity. I suspect the company views a one click sick option as having the opposite effect.

TED74 09-05-2018 04:52 AM


Originally Posted by Han Solo (Post 2668533)
1-button icrew click should just happen, no negotiations. arcos is significantly more costly to implement and it just happened, well so should 1 button sick/well. hopefully it would be implemented just slightly better.

Just in case anyone doesn't know how calling in sick works presently, it's like this:

Pilot, in a normal voice:
"Hello, I'm calling in sick"

Scheduler, in a normal voice:
"What's your employee number?"

Pilot:
"123456"

Scheduler:
"Call us back when you're well"

Pilot:
"Thanks, goodbye"

I'd much rather have programmers work on 1-button GS On/Off toggle, myself.

I honestly can't see the company doing anything to benefit only the pilots without getting credit for it in negotiations. I've also heard that in anticipation of icrew's sunset, there will be no non-essential programming changes made to its functionality.

sailingfun 09-05-2018 05:03 AM


Originally Posted by TED74 (Post 2668549)
Just in case anyone doesn't know how calling in sick works presently, it's like this:

Pilot, in a normal voice:
"Hello, I'm calling in sick"

Scheduler, in a normal voice:
"What's your employee number?"

Pilot:
"123456"

Scheduler:
"Call us back when you're well"

Pilot:
"Thanks, goodbye"

I'd much rather have programmers work on 1-button GS On/Off toggle, myself.

I honestly can't see the company doing anything to benefit only the pilots without getting credit for it in negotiations. I've also heard that in anticipation of icrew's sunset, there will be no non-essential programming changes made to its functionality.

1. MICREW
2. Self book DH deviations
3. Online jumpseat listing
4. Airport sign in
5. Ipads
6. original DH deviation policy
7. Automatic listing to first class upgrade
8. ULC for MD11
A few items done without any Quid.

TED74 09-05-2018 05:31 AM


Originally Posted by sailingfun (Post 2668553)
1. MICREW
2. Self book DH deviations
3. Online jumpseat listing
4. Airport sign in
5. Ipads
6. original DH deviation policy
7. Automatic listing to first class upgrade
8. ULC for MD11
A few items done without any Quid.

So you're telling me there's a chance!

I don't know the history of several of those, but it would seem that many benefit management or otherwise offload a workload or volume of complaints non-pilots would have had to process.

Making it easier to call in sick seems to run counter to everything the company prioritizes. I'd be shocked if they moved on this with no quid.

Han Solo 09-05-2018 05:38 AM


Originally Posted by TED74 (Post 2668549)
Just in case anyone doesn't know how calling in sick works presently, it's like this:

Pilot, in a normal voice:
"Hello, I'm calling in sick"

Scheduler, in a normal voice:
"What's your employee number?"

Pilot:
"123456"

Scheduler:
"Call us back when you're well"

Pilot:
"Thanks, goodbye"

I'd much rather have programmers work on 1-button GS On/Off toggle, myself.

I honestly can't see the company doing anything to benefit only the pilots without getting credit for it in negotiations. I've also heard that in anticipation of icrew's sunset, there will be no non-essential programming changes made to its functionality.

Except that's not how it works. You forgot the part where you can be on hold for 5 minutes under normal circumstances to 3+ hours during an IROP. I've also been transferred to speak to the duty pilot to explain why I can't fly my rotation. This from a pilot who has never used more than 40 hours in a year. The company pressures pilots to fly sick, it needs to end.

sailingfun 09-05-2018 05:45 AM


Originally Posted by TED74 (Post 2668572)
So you're telling me there's a chance!

I don't know the history of several of those, but it would seem that many benefit management or otherwise offload a workload or volume of complaints non-pilots would have had to process.

Making it easier to call in sick seems to run counter to everything the company prioritizes. I'd be shocked if they moved on this with no quid.

No, I don’t feel there is a chance. The company will feel this will cause a increase in sick calls.


All times are GMT -8. The time now is 04:09 PM.


Website Copyright © 2026 MH Sub I, LLC dba Internet Brands