Originally Posted by GogglesPisano

We're still doing well with On Time Arrivals and Departures.

Originally Posted by GogglesPisano

There seems to have been a strategic change since COVID. We used to fly empty aircraft or fly the aircraft a day late with the same flight number to improve our completion factor. Now we don't care.

We're still doing well with On Time Arrivals and Departures.

Originally Posted by Gulfasaurus

The problem is how it's implemented in DBMS. The PWA says that you're automatically released from long call duty at 6am going into a golden day. If at 6am on your last day there's nothing on your schedule, you're released. In practice though, them pre-posting it makes you unavailable for slips. When I have 4 days of availability followed by a golden day with pre-posted rest on day 4, it will make me ineligible to YS a 4-day trip. I know this for a fact because I called scheduling out on it, and they said the pre-posted rest doesn't even make me appear on the trip coverage report for that 4-day when they run it, so it ignores my slip. I've had some luck making them remove the rest and award me the YS as it should be (the original memo on pre-posted rest said it wouldn't affect slips, even though it obviously does) but it depends on who picks up the phone and wastes 30 minutes of my day for something I'm contractually entitled to assuming nobody senior to me YS that same trip, and that 6 months ago was happening automatically. So then I try to YS a decent 3-day to protect myself from a garbage 4-day that will inevitably drop later on but that often gets ignored because sometimes there aren't enough people in my bucket to satisfy the 23.S.1.a exception to note two. In name I have a 4 day availability but only for stuff they want to assign me. If I want something I'm restricted to a 3-day assuming I can even do that. But when that garbage 4-day does indeed come, then scheduling decides to remove the rest and assign it to me. Now I'm flying trash when a perfectly decent 4-day that I had a YS for and was the most senior got assigned to someone with 5 days available.

Same with 30/7. If I want to YS a trip with a 30+hr layover, it will not accept it due to the pre-posted 30/7 rest. But they can give you one you don't want when they run out of options and remove the rest. Same for Green Slips and any other color slips that would otherwise be 117 legal but get blocked by the programming. At the more ninja level I used to snipe where I wanted my 30hrs rest to fall on long blocks of reserve days by strategically using YS and the 48hr coverage window. Now it just ends up where they want it and blocks me from perfectly legal trips. That's why this whole situation is infuriating.

Originally Posted by Bazinga

no and I’d be surprised if that ever happens. It’s a completely manual process that requires adequate manpower which we obviously don’t have.

Originally Posted by Rooster435

DTW 350 B has had a few in the last week. And at least one trip that they couldn’t cover no matter what the slip.

Originally Posted by Rooster435

DTW 350 B has had a few in the last week. And at least one trip that they couldn’t cover no matter what the slip.

Originally Posted by Hotel Kilo

I've been reading about this but thus far it really hasn't impacted my BES too much, until now. I put a trip in for a drop prior to the 20th, looked at the reserve grid, all blue. My trip was not dropped due to reserve coverage on the 20th PCS run. So I guess they pre-posted rest for RES sometime on the 18th-19th? Thus making any drop using a PD unattainable when the 20th PCS run came along. I'm not burning IVD/APD on it. Probably figure out something else.

I agree with you and the others, this pre-posted rest is BS. It prevents us from manipulating schedules when our plans change. You know, because that does happen after we submit PBS bids.

Originally Posted by tennisguru

For years, since I was hired and I'd assume well before, if you were going into a golden X day (or VAC day) the system just dropped you into rest right at 0600. No CNO (not required), no pre-posting. It just happened automatically every single time. There is no reason not to go back to that. I get the company would want to pre-post rest on LC blocks of 7+ days, or when you've got a single X day in between a block of LC days. But there is zero reason to pre-post rest when you're going into 2+ X days. The system worked just fine beforehand and there was no reason to fix it.

Originally Posted by Verdell

Golden day bidding for RES closes at 8AM the morning of the 19th. The bulk of pre-posted rest happens that day, prior to the 20th PCS run.

This has been a thing since... around October 2025. Plenty of folks (including myself) raising a fuss about it. A little surprised literally everyone isn't aware of it by now.

I think it got quashed as a "oh you poor RES pilots" thing for awhile, but it always affected REG. The effects just weren't as obvious at first.

Originally Posted by tripled

it’s because of the volume. +30 (34 req 58-65 avail) pilots in the blue at noon day prior to 20th 0700 pcs run for most days in June. 24 hours later the left column was at 54 req with 53 avail. Total BS. This is a pure computer syntax gimmick to make a computer program show favorable numbers to generate a desired outcome and has NOTHING to do to with FAR117 or actual rest that makes one ‘fit to fly’. The data will show that the company skeds choosing to assign ‘rest’ only to yank it when it suits them is putting them, and flight safety, on precarious ground.

Agree that it was a scheduling threat back in oct25 but the widespread use in June coupled with the other unilateral reinterpretation on pb days is creating even more bad blood btn flt ops and the pilot group. We are pros not a bunch of regional hustlers. Bad play Mr gumm- you might have found a clever way to force us to buy back the value of a PD (and also a PB) but we don’t forget this kind of treatment once a contract gets signed.