Originally Posted by
sailingfun
The problem is there is past practice and agreements between the union and the company along with decisions in system board actions that more or less define what reasonably available is. If you live 3 hours from Atlanta and delay a few flights because 3 hours is your interpretation of reasonably available you are not going to like the result. If on the other hand you live 2 hours from the airport and get caught in traffic causing you to need 3 hours that day you will be fine. That’s the intent of how it is written. Shortly after the Western merger the company took action against pilots sitting short call in San Diego. We finally agreed that was not acceptable and also agreed that it must be ground transportation. Like many things in the contract we try to leave wiggle room. When you get guys abusing that the company looks for changes no one likes. Sick leave verification is a example.
Yes, this. Again, it is intentionally ambiguous to allow for reasonable variance, but not abuse. I was on the 767-400 when the 747 was about to close, and there were 4 pilots who were 'fired' for sitting SC from as far away as California, one of whom had no record of commuting for SC in
two years (No Non-Rev record, KCM, or other travel record was found). The company said "two can play this game", and put every single reserve pilot on SC the maximum number of times the entire summer of 2017. We had 6 departures a day from JFK, and they had 11 FO's on SC once - enough to replace every FO but one. I have no sympathy, nor wish ALPA to burn any good will on fellow pilots who abuse the system like those 4 did. Screw them, because they absolutely screwed the rest of their 'fellow' pilots. 3 of them reportedly got their jobs back. SMH.
Originally Posted by
FL370esq
First off, thank you for the typo correction. 2...3....meh. Same stuff, right? And I think we are in agreement (except for the exception thing which I am actually not confusing with the other part). A drive in the NYC and/or LAX area (or ATL for that matter) may certainly take 3 or 4 hours depending on time of day and/or accidents/construction (roving pot hole repair)/weather which begs the question, what is the no-traffic time to report in that case? You posted "you will not want to have to explain why it took you much longer than about that [3 hours]." Three hours isn't written anywhere either so what would you need to be explaining?
As for the exception (and only the exception, Mrs. Riley), I will ask again - why did ALPA and the Company agree to a report no sooner than 2 hours rather than one hour or 3 hours? Short call starts at the beginning of the short call window, period. The language in the exception says "[t]he pilot must be able to report for a rotation with a report as early as two hours after the start of the short call period." I love that language because I can, in good conscience, stand in the CPO office and say I made it within 2 hours despite scheduling wanting me there in 40 minutes. If it is good enough for the beginning of the window, it is good enough anywhere else in the window...because promptly report isn't written anywhere.
Carrying it further, what if I am NYC-based but live in BOS or DC and decide not to commute in (and therefore not become "unavailable" under the exception)? Is promptly reporting now less than 2 hours for me because I am not "unavailable" or is it more so I can just tell the scheduler that I am leaving now and will be there in 4 hours because "promptly report" has no time with it and 4 hours is a prompt report from my home?
Good stuff to discuss...
Yes, you
are conflating two different things. I think we all agree that reporting within 2 hours meets any callout expectation, and that in some special circumstances 3 will still be reasonable. That's all fine and good. And I fully agree that "about 2 hours" is generally agreed with the company. But...
Where you are wrong is the paragraph you cite is not addressing what "promptly available" means. It is only to do with being "unavailable for contact" while you are
already commuting in, that's it. Frankly, I think
this conflation is why so many people erroneously get the idea that "SC is 2 hours". It is
not. Go reread the entire 23.S.7.b exception and also 23.S.7.c. It is
literally an exception! While they are in the same orbit as one another, you can't conflate the two. SC is not 2 hours, period. dot. In other words 2:01 is not over any defined 'line'.
Again, SC is
intentionally not defined.
Having said all that, reference my comments above - if you are abusing this 'non definition', you are screwing your fellow pilots. And It pizzes me off when the rest of us have to wear diapers because the rules don't apply to you. Sitting SC in Chattanooga is clearly a no-go. Sitting SC in base housing (PTC), or in Kew Gardens but not leaving your house for 2 hours is also a no-go. You might get away with it for a time, but eventually it will catch up with you, and the rest of us. This is why we have stupid contract provisions like 100-hour sick verification - because abusers screwed the rest of us.
Also, part of the reason this is important is the aforementioned GS callout must be given the same callout time as SC, which is 'promptly available' - NOT 2 hours. So, if you are LAX based, and they decide to reroute someone else instead of giving you the GS (as a Reg pilot), and you could have been there within 2.5 or even 3 hours, they owe you single pay. Do not let anyone tell you the cutoff is 2 hours for that. It is not.