Quote:
Originally Posted by fcoolaiddrinker
The company has to get you back to domicile. If you remove that sentence what would that accomplish? Great I’m now released on the other side of the country and I just hosed myself out of at least 5 credit. 99% of the time the next leg gets you back to domicile in that scenario. They have two legs to make that happen. Most of the time it’s a dh back that I simply deviate from. You want to force the company to get you back to domicile. DL could just add flying to your schedule through acars. I agree with your 1.5.
Real world example…
Pairing:
Day 1
MCO-ATL 20+ hour layover in ATL
Day 2
ATL-LGA
LGA-MCO Release at 12:00pm in MCO
A plane in MIA that is supposed to operate MIA-ATL-SFO is hours delayed due to mx. Scheduling attempts a reassignment of the crew that lands in ATL from MCO.
Attempted reassignment…
Day 1
MCO-ATL
ATL-SFO layover SFO
Day 2
DH SFO-MCO release at 15:15 in MCO
I don’t believe this exact scenario would be legal today as there is a domicile in ATL, however this was before the ATL domicile. The above scenario happened to me. I was never notified of the change and I went home that day. Under the language of the contract that will be going into effect with the app, this would be a legal reassignment (per ALPA) because of the “reasons beyond the control of the company.”
In the above example the reassignment was outside of the footprint of the original pairing. That should not be allowed in my opinion. I understand that my plane can break down in an outstation and that’s not what I’m talking about. A reassignment to different flying should never fall outside of the footprint of the original pairing. We have that language and then negate it with, “for reasons beyond the control of the company.”