Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Our contract limits day/night transitions. You can transition between day and night flying only once per block of flights, you must have at least 16 hours off between the day and night flights and the transition must be at either the first, or last, layover in the block.
These provisions were put in many years ago to prevent having a schedule which constantly swapped back and forth between day and night flying while allowing a block (week) of flying to either start or end with a day trip. This would typically be a Sunday afternoon start, 16+ hour layover, then night flying for the rest of the week or a week of night flying ending with a 16+ hr layover and Sunday morning flight into ILN.
The transcon consists of three duty periods. The first and third of which are day flight, the second is night flying. That's two day/night transitions which weren't allowed. The company initially broke the trip up with different crews, on different trips, doing segments of the transcon but not making the whole cycle.
The agreement was made to allow the double day/night/day transition for the transcon in exchange for a couple of concessions from the company. The minimum rest was INCREASED (not decreased as had been alleged) from 16 hours to 24 hours at both SFO and JFK. That 24 hour rest can not be reduced. Additionally, the requirement for catering on the SFO-LAX-JFK night was added. Those company concessions provided the same, if not better, protection to the crews than the original rule which was intended to address a completely different issue.
There was no membership vote on this issue.
I have a question. Why did none of your Airbuses make it on Friday? I heard they were CAT2... We had at least one runway CAT2 most of the night.
Ooooh...I'll take this one. :nuts:
hvydriver may be pontificating a conspiracy theory:
"RVR dropped below 1200 anytime there was an Astar a/c in range."
http://messages.finance.yahoo.com/B...cks_A/threadview?bn=25762&tid=12384&mid=12617
Ooooh...I'll take this one. :nuts:
hvydriver may be pontificating a conspiracy theory:
"RVR dropped below 1200 anytime there was an Astar a/c in range."
http://messages.finance.yahoo.com/B...cks_A/threadview?bn=25762&tid=12384&mid=12617
That's interesting LJ. We ran the trip precisely the same way you describe above. Except we didn't give on the double/day/night transition. And we already had catering, of course.
Our contract limits day/night transitions. You can transition between day and night flying only once per block of flights, you must have at least 16 hours off between the day and night flights and the transition must be at either the first, or last, layover in the block.
These provisions were put in many years ago to prevent having a schedule which constantly swapped back and forth between day and night flying while allowing a block (week) of flying to either start or end with a day trip. This would typically be a Sunday afternoon start, 16+ hour layover, then night flying for the rest of the week or a week of night flying ending with a 16+ hr layover and Sunday morning flight into ILN.
The transcon consists of three duty periods. The first and third of which are day flight, the second is night flying. That's two day/night transitions which weren't allowed. The company initially broke the trip up with different crews, on different trips, doing segments of the transcon but not making the whole cycle.
The agreement was made to allow the double day/night/day transition for the transcon in exchange for a couple of concessions from the company. The minimum rest was INCREASED (not decreased as had been alleged) from 16 hours to 24 hours at both SFO and JFK. That 24 hour rest can not be reduced. Additionally, the requirement for catering on the SFO-LAX-JFK night was added. Those company concessions provided the same, if not better, protection to the crews than the original rule which was intended to address a completely different issue.
There was no membership vote on this issue.