Originally Posted by
Verdell
It's wildly inconsistent and goes by the whim of the scheduler. And I've been on both sides of it.
I've been a assigned a trip because I didn't have pre-posted rest and the others ahead of me (RUO) in same bucket did. I called scheduling, they explained that the coverage report doesn't show those pilots as eligible and the trip was mine, enjoy.
I've also been assigned a trip when I was the pilot with pre-posted rest, they assigned it to someone below me (RUO) in same bucket who didn't have rest, but that pilot called scheduling and got them to remove MY rest and assign ME the trip.
I'd like to know what that pilot said that I didn't say to the scheduler that got them to drop my rest.
This inconsistency is the key, and it may be the only leverage the union can use against the company to get them to organize this debacle. The system worked just fine in the olden days (like, last year) where the system just automatically released you at 0600 going into a golden X day or VAC day. To a degree I understand them wanting to automate better the 30/168 rest, but by and large that pre-posting doesn't jack up the proper RUO nearly as much as the 0600 rest does. That part needs to be undone and reverted to the old programming which worked fine literally for years.