I bet the increased sick calls are due to the “allergies” crowd realizing they have the ability to not work when the allergies start. And can wait until the allergies are gone. I’ve had to call in thanks to their allergies enough.

 

There’s a case to be made that the company’s pressure on pilots to verify sick occurrences actually pressures them to fly when they should not. The suspension of that inappropriate pressure now allows pilots to make the correct fly or don’t fly decision. The data needn’t implicate pilots for doing anything improper - it should show that the verification systems Delta chooses to use (that are not present elsewhere) are actually diminishing our safety. They are normalizing Pilot-pushing.

Policies matter. For years we extended far more than other carriers - and probably sacrificed safety margin by doing so.

 

I couldn’t find instructions in the SRH … how do you PD several trips at once in PCS? Every time I try, it ends up dropping one then deleting the rest.

Do you put them all under priority 1?

Or, could you point me toward a reference instruction?

Thanks in advance … oh, and I’m not a farmer, I’m a slacker.

 

Good on your for attempting to look it up, but you need to look in the icrew user guide, page 54:

"Personal DropA regular line holder will see the following template. All rotations listed in a single priority must be able to be dropped in order for that priority to be awarded. The order or arrangement of rotations (vertical or horizontal) within a priority makes no difference."

Source: https://dal.alpa.org/Portals/1/Docum...sers-Guide.pdf

 

This was on my contract wish list: add a checkbox on the PD screen to tell PCS to simply drop every single listed rotation that it can. It is ridiculous that if a pilot has say 4 rotations that they want to drop that they have to enter every conceivable combination into the priority list. I think at some point if you have what, 5 or 6 rotations, that you don't even have enough priorities to cover every possible drop contingency.

 

Thanks very much for the reference!! I was thinking of PCS as it’s own entity, not a function of icrew.

So if it can’t drop priority 1, it will still move down and try to drop priority 2, right?

And it will go through all your priorities, successful or not … meaning, it won’t award one then forget the rest? That’s what I remember running into in the past, though it very well may have been user error.

Thanks again.

 

PREAAAACCCCHHHHHH!!

I'll also add, persistent slips across months and a checkbox to turn slips on/off en masse.

 

That feature should be in MiCrew. I would also like the ability to add a specific slip for a specific OT trip by clicking on it in MiCrew.

 

I know I'm dreaming, but it'd be great to have some sort of AI-integrated slip generator. You'd generate a slip with your own specific, unique circumstances. The system would know what airport(s) you have to commute out of and will automatically check flight schedules to see if there is at least 1 scheduled flight to get you in position. Or 2 or whatever you designate, also designate if you only want DL flights or check all available airlines on the route. You'd also tell the system how much time you need to get notified and make it to the gate. Say you live right next to FLL and only need 45 minutes heads up but would need 90 minutes to make it to MIA. So you would only ever get called for trips that you could reasonably make. This would work for both in- and out-of base slips. It would automatically call you regardless of report time if the rotation started with a DH to your home. You could even build in a personal calendar integration so you could mark which events you are unwilling to miss and it would skip over you if a rotation would cause you to miss that event.

 

You asked for AI slips. Best I can do is IA calls.