Quote:
The old method basically put you on the hook to the company. Your trip would be dropped and you would effectively be on reserve those 4 days. The process of dropping trips ahead of time made very good sense on paper. I will say that the reality doesn't equal the thought.
I didn't see that previous concession in the last TA that the union tried to shove down our throat, which should have been negotiated back.
IT was attempted.
Here's another thought, other airlines, to include airlines that are much bigger than Mesa, use the same software and publish schedules 24 hours later.
Gotta call BS on that. The two largest US airlines that use Navtech are Delta & Jet Blue. I've sent messages out to both groups, Delta I got back that their average award time is about 4 days. Waiting on Jet Blue but I know it's not 24 hours. - JUST GOT Jet Blue answer. They bid separately, Captains bid first then FO's bid. Each run does come out quicker but if you put the data together to signify running both at the same time like we do and Delta does their answer is 3-4 days also.
Same with the asinine amount of time it takes the company to process SAP requests, and schedule changes on the 28th. The contract says they have 24 hours or the union has to be notified (but there are no ramifications). Every month It happens
The first time this has happened was two months ago, so claiming every month is a large exaggeration. What was done to fix it? A change in staffing on the company level.
, and the union says ok cool. What's being done to fix it? Not a lot. Have any new schedulers been hired since we started growing?
Yes
I've heard from a CP that schedule changes are all manual because 117 rules aren't taken into account with split trips.
Pairing modifications require manual work as FLICA can not edit a Sabre pairing.
Why don't they let automatic drops and pickups happen for the non-split trips, using manual intervention for the split trips?
They do. A flat out drop or add or swap 1 pairing for another is manual. The delay comes in very request is processed in order. So if your drop X for Y comes behind someones request to split the last 2 days off pairing Z you have to wait for pairing Z request to be processed before the software can automatically do X for Y.
Also have you ever seen a FA put in a Flica request? It's all handled by the same software in the same order. I've seen FA's do multipart swaps. I'll take trip A from person B if person B gets trip C from person D. That's time consuming.Originally Posted by BeatNavy
Here's something that would speed up schedules coming out and make life better...don't hold trips for IOE! Drop assigned trips for IOE when needed like other airlines. Isn't that how Mesa used to be? The old method basically put you on the hook to the company. Your trip would be dropped and you would effectively be on reserve those 4 days. The process of dropping trips ahead of time made very good sense on paper. I will say that the reality doesn't equal the thought.
I didn't see that previous concession in the last TA that the union tried to shove down our throat, which should have been negotiated back.
IT was attempted.
Here's another thought, other airlines, to include airlines that are much bigger than Mesa, use the same software and publish schedules 24 hours later.
Gotta call BS on that. The two largest US airlines that use Navtech are Delta & Jet Blue. I've sent messages out to both groups, Delta I got back that their average award time is about 4 days. Waiting on Jet Blue but I know it's not 24 hours. - JUST GOT Jet Blue answer. They bid separately, Captains bid first then FO's bid. Each run does come out quicker but if you put the data together to signify running both at the same time like we do and Delta does their answer is 3-4 days also.
Same with the asinine amount of time it takes the company to process SAP requests, and schedule changes on the 28th. The contract says they have 24 hours or the union has to be notified (but there are no ramifications). Every month It happens
The first time this has happened was two months ago, so claiming every month is a large exaggeration. What was done to fix it? A change in staffing on the company level.
, and the union says ok cool. What's being done to fix it? Not a lot. Have any new schedulers been hired since we started growing?
Yes
I've heard from a CP that schedule changes are all manual because 117 rules aren't taken into account with split trips.
Pairing modifications require manual work as FLICA can not edit a Sabre pairing.
Why don't they let automatic drops and pickups happen for the non-split trips, using manual intervention for the split trips?
They do. A flat out drop or add or swap 1 pairing for another is manual. The delay comes in very request is processed in order. So if your drop X for Y comes behind someones request to split the last 2 days off pairing Z you have to wait for pairing Z request to be processed before the software can automatically do X for Y.
The busting of the 24 hour window has only been recent due to actually having green days and pilots being able to use them. That is not historically how Mesa has worked. Watch how quickly June processes because no ones going to have green days.