A possible solution?
#11
Submitting a "call me for everything" slip and then getting mad when you get called for everything is peak pilot. Most of our problems get solved with using parameters.
That being said, I'd be all for eliminating the need to submit new slips every month. More pilots would put time and effort into submitting slips with parameters if:
1. They didn't have to every month
2. They were easier to "turn off/on"
That being said, I'd be all for eliminating the need to submit new slips every month. More pilots would put time and effort into submitting slips with parameters if:
1. They didn't have to every month
2. They were easier to "turn off/on"
Using a negotiated provision and then some rando interweb memer calling you out for COMPLYING WITH THE PWA AND RE-GRIEVED SETTLEMENT.
#12
If you didn't want to get called in the middle of the night, you had the tools at your disposal long before batch sizes went away.
#13
#15
Thread Starter
Roll’n Thunder
Joined: Oct 2009
Posts: 5,179
Likes: 594
From: Pilot
#16
Gets Weekends Off
Joined: Jul 2008
Posts: 5,590
Likes: 346
For WS maybe but hard no for GS. Getting woken up at 3 am while being 15th in line (and probably again at 4am when you are 14th in line etc etc) would get old really fast. Keeping AA for GS only and perhaps shortening the window a bit would solve 99 percent of the problem.
In exchange for no other concessions and a massive quid in section 6 of course.
In exchange for no other concessions and a massive quid in section 6 of course.
Also we have not always had auto accept. We always had auto acknowledge.
#17
Edit: Just saw you add your second point, the only time I can remember not having auto accept was the old way of calling one pilot at a time. It was not auto acknowledge for GS because there’s no getting out of auto acknowledge; in the old days if you took no action the trip was removed with no penalty. You’re right that that’s how it was for WS.
I’m 100 percent fine going back to that way for what it’s worth.
#18
Line Holder
Joined: Feb 2023
Posts: 201
Likes: 113
The only ways to actually speed up trip coverage through the IBGS step without increasing nuisance phone calls are to either reduce the acknowledgement window timeframe from 12 minutes to something far shorter, or to move the OOBWS step to after IBGS. And I don’t support either without substantial concessions from the company.
This might well be an unpopular view, but I don’t think trip coverage is a disaster for us, especially with quick slips incoming. Quick slips will ensure seniority is respected, and the company will pay 3x for the inconvenience of being called in a big batch if you want them. Trips will be covered within 12 minutes, rather than current IA calls where wait times are unknown and a total crapshoot.
I think we should stop trying to figure out how to solve the company’s problem and let the negotiating committee decide how they want to approach it in section 6. We will all get to vote on whatever is agreed to.
#20
While we are throwing out ideas for the NC to put a $$ on, here is a one call and done approach. Accept/Acknowledge together, just like the "good ol days".
Batch size of 1, sequentially called in seniority order every X minutes until someone accepts/acknowledges. Set X according to time until report. Close in, calls go out every minute. Further out calls fire off every 2,3,4 minutes. Worst case is 11 pilots interrupted for a trip they can't hold because #1 took 12 minutes to accept/acknowledge. Further out only 3-5 pilots interrupted without a chance at the trip. No blasting 10-100 at a time. Calls can be further restricted during base night time.
The programming is complex. It would take an intern an entire day with OpenAI Codex to complete the ARCOS project and then a team of Amish IT craftsmen another month to hammer and chisel it into DBMS.
Batch size of 1, sequentially called in seniority order every X minutes until someone accepts/acknowledges. Set X according to time until report. Close in, calls go out every minute. Further out calls fire off every 2,3,4 minutes. Worst case is 11 pilots interrupted for a trip they can't hold because #1 took 12 minutes to accept/acknowledge. Further out only 3-5 pilots interrupted without a chance at the trip. No blasting 10-100 at a time. Calls can be further restricted during base night time.
The programming is complex. It would take an intern an entire day with OpenAI Codex to complete the ARCOS project and then a team of Amish IT craftsmen another month to hammer and chisel it into DBMS.
Thread
Thread Starter
Forum
Replies
Last Post




