Recurrent training gnd trans expense
02-02-2019, 03:14 PM
#11
Gets Weekends Off
Joined APC: Jan 2013
Posts: 154
Try Reading the contract
Originally Posted by Adlerdriver
Nice thought but this is a huge stretch, IMO.
First, there is no location “code” restricted by the expense software when one inputs a GT expense. The only expenses that have specific location codes pre-set in a pull down menu are hotels.
First, there is no location “code” restricted by the expense software when one inputs a GT expense. The only expenses that have specific location codes pre-set in a pull down menu are hotels.
Originally Posted by Adlerdriver
You want to put the 3-letter ID for Olive Branch in? What’s stopping you? It either goes in the blank field for origin or destination.
Originally Posted by Adlerdriver
The bottom line is most of us do recurrent in our domicile. Trying to claim the airport boundary somehow defines our domicile is your loose interpretation of a rather vague portion of the CBA.
No loose interpretation here....its in the actual text of the contract. AIRPORT is expressly defined as the domicile and base. And yes, I've had this analyzed by a lawyer. My understanding is formed by a legal expert on the subject.
What radius applies to the AIRPORT? How far from the airport must we be to file an expense? 10 miles, 20 miles, 100 miles.....how about you loosely interpret that for me?
Originally Posted by Adlerdriver
There’s no way anyone is going to buy the argument that we should be able to get an Uber to the sim building for recurrent because it’s off airport and therefore not in our domicile.
02-02-2019, 03:45 PM
#12
Gets Weekends Off
Joined APC: Aug 2006
Posts: 1,820
Originally Posted by Patches
This is straight up false. In order to file the expense...you must input an airport code at the start and end of each event. MEM is the only option.
There is no airport code for Olive Branch in the system. We are all limited to a select few airfields that does not include many we are authorized to use. What part of "any two commercial locations" can't you understand?
Domicile defined in the Contract: "An airport or co-terminal airports, designated by the company, to which pilots are permanently assigned....."
No loose interpretation here....its in the actual text of the contract. AIRPORT is expressly defined as the domicile and base. And yes, I've had this analyzed by a lawyer. My understanding is formed by a legal expert on the subject.
What radius applies to the AIRPORT? How far from the airport must we be to file an expense? 10 miles, 20 miles, 100 miles.....how about you loosely interpret that for me?
That is exactly what I'm saying....because that is how the contract is written. It might not be the intent.....but that does not matter in legal settings. The words are written clearly and anyone looking strictly at the text can interpret this any other way without defining a specific radius.
There is no airport code for Olive Branch in the system. We are all limited to a select few airfields that does not include many we are authorized to use. What part of "any two commercial locations" can't you understand?
Domicile defined in the Contract: "An airport or co-terminal airports, designated by the company, to which pilots are permanently assigned....."
No loose interpretation here....its in the actual text of the contract. AIRPORT is expressly defined as the domicile and base. And yes, I've had this analyzed by a lawyer. My understanding is formed by a legal expert on the subject.
What radius applies to the AIRPORT? How far from the airport must we be to file an expense? 10 miles, 20 miles, 100 miles.....how about you loosely interpret that for me?
That is exactly what I'm saying....because that is how the contract is written. It might not be the intent.....but that does not matter in legal settings. The words are written clearly and anyone looking strictly at the text can interpret this any other way without defining a specific radius.
Edit:
The contract doesn't state "any two commercial locations." It's hard to debate the meaning of contract language if you can't get the language correct.
02-02-2019, 04:01 PM
#13
Gets Weekends Off
Joined APC: Jul 2007
Position: 767 Captain
Posts: 3,988
Originally Posted by Patches
This is straight up false. In order to file the expense...you must input an airport code at the start and end of each event. MEM is the only option.
When I incur a GT charge on my credit card from my local limo company, it shows up in my expense report. I assign it to the appropriate section of my trip. Since I live near ORD and I'm going from my house to the passenger terminal (as an example) at ORD, I type in the three letters. O - R - D in my origin. I do the same thing for the destination... O - R - D. Then I select (from the pull down menu) "Residence" for the origin specific since the limo is picking me up at my house. I select "Airport" for the destination pull down menu since I'm going to the passenger terminal to catch a deviation deadhead. I have yet to be denied or given any kind of push-back on any GT expense I've entered this way.
MEM is not "the only option". In fact, it's not even one of the options since there are none. I can type whatever three-letter code I want in both the origin field and destination field. Please explain to me what I'm missing here. You can see below, a screen shot of a GT entry from my last expense report. No problems telling the system that, 1 - My GT started and ended in the ORD vicinity and 2 - was from my residence to the airport.
So, how is it exactly that you are unable to enter the Olive Branch 3-letter ID in the same situation and are somehow forced to use MEM?
02-03-2019, 02:12 AM
#14
Gets Weekends Off
Joined APC: May 2005
Posts: 1,273
Originally Posted by Adlerdriver
Okay. Either you and I are completely missing on the communication skill set, or you're using a very different expense report system than I.
When I incur a GT charge on my credit card from my local limo company, it shows up in my expense report. I assign it to the appropriate section of my trip. Since I live near ORD and I'm going from my house to the passenger terminal (as an example) at ORD, I type in the three letters. O - R - D in my origin. I do the same thing for the destination... O - R - D. Then I select (from the pull down menu) "Residence" for the origin specific since the limo is picking me up at my house. I select "Airport" for the destination pull down menu since I'm going to the passenger terminal to catch a deviation deadhead. I have yet to be denied or given any kind of push-back on any GT expense I've entered this way.
MEM is not "the only option". In fact, it's not even one of the options since there are none. I can type whatever three-letter code I want in both the origin field and destination field. Please explain to me what I'm missing here. You can see below, a screen shot of a GT entry from my last expense report. No problems telling the system that, 1 - My GT started and ended in the ORD vicinity and 2 - was from my residence to the airport.
So, how is it exactly that you are unable to enter the Olive Branch 3-letter ID in the same situation and are somehow forced to use MEM?
When I incur a GT charge on my credit card from my local limo company, it shows up in my expense report. I assign it to the appropriate section of my trip. Since I live near ORD and I'm going from my house to the passenger terminal (as an example) at ORD, I type in the three letters. O - R - D in my origin. I do the same thing for the destination... O - R - D. Then I select (from the pull down menu) "Residence" for the origin specific since the limo is picking me up at my house. I select "Airport" for the destination pull down menu since I'm going to the passenger terminal to catch a deviation deadhead. I have yet to be denied or given any kind of push-back on any GT expense I've entered this way.
MEM is not "the only option". In fact, it's not even one of the options since there are none. I can type whatever three-letter code I want in both the origin field and destination field. Please explain to me what I'm missing here. You can see below, a screen shot of a GT entry from my last expense report. No problems telling the system that, 1 - My GT started and ended in the ORD vicinity and 2 - was from my residence to the airport.
So, how is it exactly that you are unable to enter the Olive Branch 3-letter ID in the same situation and are somehow forced to use MEM?
Edit: This is what happens of you use an unknown airport identifier.
Attachment 4198
And just for reference, AAA worked (that must be the code Fox uses for unknown airports), ZZZ did not work, but OLV (Olive Branch) was a known identifier and let me input it.
Last edited by Sluggo_63; 11-22-2020 at 02:45 PM.
02-03-2019, 02:28 AM
#15
Gets Weekends Off
Joined APC: May 2005
Posts: 1,273
Originally Posted by Patches
By the contract: Pilots are permitted to use surface transportation between "commercial locations", or between a "residence and a field airport/operations area". Field airport and operations area are not defined in the contract.
The only limitation is that you cannot expense transpo between any location and your "Base" - which is defined as the "Airport".
The huge problem here: as long as you do not involve the actual airport property....you are legal by the contract. The limitation is with the Expense Reporting software that will not let us use any identifier other than MEM. How far away from MEM must you be to file an expense?
I am legal to travel from my home to the Olive Branch airport and expense the cost....but I am limited by the software that has no code for Olive Branch. If I am in Montana, and travel to a small local airport....I just pick a code airport that is "closest" and get reimbursed all day long.
The radius of acceptable distance to define your "domicile/base" is half way to the next closest airfield in the Expense Report filing system. This is severely limiting our contractually guaranteed usage of bank funds.
The union should address this with the company to allow pilots to exercise the contract language as written. Any location outside the property lines of the actual airport are fair game - we just need a proper code when filing.
The only limitation is that you cannot expense transpo between any location and your "Base" - which is defined as the "Airport".
The huge problem here: as long as you do not involve the actual airport property....you are legal by the contract. The limitation is with the Expense Reporting software that will not let us use any identifier other than MEM. How far away from MEM must you be to file an expense?
I am legal to travel from my home to the Olive Branch airport and expense the cost....but I am limited by the software that has no code for Olive Branch. If I am in Montana, and travel to a small local airport....I just pick a code airport that is "closest" and get reimbursed all day long.
The radius of acceptable distance to define your "domicile/base" is half way to the next closest airfield in the Expense Report filing system. This is severely limiting our contractually guaranteed usage of bank funds.
The union should address this with the company to allow pilots to exercise the contract language as written. Any location outside the property lines of the actual airport are fair game - we just need a proper code when filing.
Thread
Thread Starter
Forum
Replies
Last Post
