olly

VTO's were finalized 1700 LBT 27 jun. Checked my calender, and Block display. sched looked great- one long trip w carryover into aug. Looked at it several times over the past several days to export the calendar, set up jumpseats etc

loged on vips today, and noticed that as of today 01jul, 3 days after the vto's are "finalized" they have added several R days starting on tues 03jul.

My trip had carryover- and it would appear that the reason for the addition is to get the blg value for the jul bid period.

However, they did it after the finalization, and added the R days, today the 1st . If I had gone off the fdx vips grid until showtime of my line as "finalized" on the 27th, I never would have known about the addition.

Plan to call contract enforcement monday, but anyone know how this could be legal- adding events to a vto- After the finalization time?

HazCan

Just flew with a guy who had his VTO changed up after they were finalized. No explanation. He also has a call into enforcement and is supposed to hear something tomorrow. Sounds like BS.

Time Off

Let us know how this plays out. That is totally UNSAT.

Malkovich

I predict a British voice on the phone saying "They can do that"

A300_Driver

It's all part of the new "Just Bend Over and Take It Culture"!

olly

Dt contacted labor relations, company had IT records of the r days being added to my line prior to vto finalization deadline. I have no proof, screenshots, or printouts other than a few txt msg s complimenting my vto. Taking my word that I checked not only my calendar
But, next activity, future activities & block display every day, DT suspects that there may be some interoperability IT issue between VIPS, and the system futures uses, and is opening an investigation. It is a potential issue for both the company & Alpa if the company believes they've made an assignment, and the pilot has no knowledge of said assig ghent. In my case, I could have noted my vto s next activity and not log into Vips again until showtime. A no show for the phantom assignment would be the pilots fault, and the company may have a reliability issue, bad for both. But if there is an IT problem, the burden of proof will be on the pilot, as this situation had revealed that the company "has"proof that they made a legal assignment.

Nitefrater

Surprise! Surprise! Surprise! Did you expect anything different? The company will ALWAYS have IT records to support it's position. After all, it owns the computers and the programmers.

Screenshots don't cost a lot of computer storage space, and it's a good idea to take them often and save them in your "Pearl Harbor" file. Trip revisions, crew notifications, anything that seems strange, FCIFs that will later become vaporware, whatever you're looking at when you decide to call crew scheds... you get the idea.

jzuniga

Good call NF... I'm going to start doing that and file it in the CYA files at home;-)

Z

Time Off

Thanks for the follow-up. I would like to hear the result of DT's investigation. This is a problem that could affect everyone.

appDude

And for FxCal users, remember the iOS screen shot capture technique: momentarily press the Home/Menu button and the Sleep/Wake(On/Off) button at the same time. Great way to keep a record of all company communications.