Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

NetJets, Marquis Jet, Executive Jet Management?

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
Ambiguity doesn't take as many words as specific language does. Considering how important it is to "read the fine print" before signing a contract, I submit that when one is writing their own contract s/he should be doubly careful about using precise language to get exactly what was intended. Arbitration is costly so a well written contract benefits all who use it. It sounds like a good lesson was learned from the experience of the BBWG. Additional pages are also generated when new ground is covered, as in your PTO example. I predict that some new changes will be welcomed by the pilot group.
 
Additional pages are also generated when new ground is covered, as in your PTO example. I predict that some new changes will be welcomed by the pilot group.
The problem is, nobody in this company (union or management) knows how to keep it simple. For example, PTO. Why do we need short-term and long-term banks, and all the language that goes along with that? Why do we need longevity-based PTO usage, and all the language to explain it? Why do we need complicated sell-back provisions, and all the extra language to explain it?

Rather than simply complain, here's my solution: Accrue 1 day per month, 75 days maximum banked (same as now). 8 days per year can be used as PTO. Days banked over 24 can be sold back to the company at XXX%. X # of days around Thanksgiving, Xmas, and New Years are blacked out from PTO. X number of slots per day (based on fleet size) available for bid on crewops for PTO. Remainder available for pick-up with 7 days notice, 1st come, 1st served. Sick call provisions remain the same. Simple, to the point, and doesn't take XX pages to explain.
 
The pilot group is made up of many different demographic subgroups with varying needs. The one size fits all approach is easier to write I'm sure but it doesn't allow for a wide variety of scenarios that come up in a Union this size. Personally, I've always found it frustrating to make a logical request and hear something along the lines "Well yes, that makes sense but it's not in our policy to do that". I like options so I give high marks to those at the table for trying to anticipate the needs of the pilots and their families.

You will notice that I'm sticking to a discussion of the concept of PTO. That was as far as we got at our kitchen table. My husband has been preoccupied with other IBB sections. I look forward to reading the final TA. I equate details with spelled out protections and benefits so the length won't bother me. From my posting style that comes as no surprise, right? :D In all seriousness, your careers are complex and should be treated accordingly. Additionally, the more precisely written your contract is the easier it will be to enforce.
 

Latest resources

Back
Top