1st overnite

What is the gouge on the back end deviation? I have had guys tell me not to deviate until I am at the city where the DH starts. The idea, I am told, is that if they re-route or you arrive late, they have to rebuild the DH part of the trip for legal rest and if you are already deviating, they don't and you could lose out on money. Is there any other reason to do this? This doesn't seem right to me because one time we landed late at an airport with very limited airline service, and as we were leaving the plane, a ramp agent told us to call crew scheduling. We were thinking they were going to add another leg, but he called to tell us we were too late to make the scheduled DH and he rebuilt the trip. He said he saw that I was originally deviating and asked if I would still like to deviate. I deviated again and still got the extra pay for the new DH time. Was this scheduler the exception rather than the norm? Am I missing something else?

FDXLAG

The real reason not to deviate until the end of the trip is in case you are snowed in in Buffalo the company picks up the hotel tab you dont. You also remain in overage until the company can schedule you back to base.

In your example had everyone already deviated the odds are the scheduler would not have called or cared and the trip would have paid as scheduled.

Perm11FO

LAG has the right idea, but it's a pretty limited situation, unless you bid snow cities just for the fun of it.

The reality is that if the original pairing cannot be done due to any reason (even if all crew members are approved for deviations...), CRS has to rework the schedule.

Once the original pairing is reworked, your deviation request is now null and void and you have to deviate again. The concept is that you deviate from a particular pairing. When the pairing goes to Rev 1, you have to deviate from Rev 1.

In short, the minute that legality forces a rebuild of your pairing, your previous deviation request is cancelled and you are back on the revised pairing again. The scheduler in the example was nice to "remind" the crew of this. It has nothing at all to do with saving money.

LEROY

This is inaccurate for BACK-END deviations, per a grievance settlement concerning back-end deviation and trip revisions (look for the scale symbol on the electronic version of the CBA). Once you deviate on the back end, you are not entitled to pay provisions you WOULD HAVE HAD had you not deviated. The non-deviators will have a new pairing built. The deviator gets nothing, as his or her pairing has not been revised.

Magenta Line

I, too, don't deviate until after I'm at the hotel (if I'm laying over) or after I'm on the DH flight/jumpseat home. Same reason as LAG -- if anything happens, I at least have a place to put my noggin' for the night/day.

Nitefrater

This hasn't been my experience.

They rebuild the pairing all right, but for deadhead travel they consider you deviated and won't "undeviate" you if you decide you want to take the newly scheduled deadhead. For this reason I hardly ever submit a deviation request on the back end, just simply cancel the scheduled ticket in time. Granted, my bad experience with this is a number of years ago, and it's possible they're doing things differently now, but I'm not inclined to give them another chance to burn me.

FDXLAG

Spoken like a senior line holder. But in reality the non snow cities are even a higher threat for losing a days worth of flying. Ever been to Atlanta, Dallas, or even Shreveport after an ice storm.

DLax85

When you deviate it does NOT mean you are heading straight home.

You still get the bus to the hotel --- and the hotel room, if you want it (...ice/snow storm or not).

What's cancelled is your transportation back to the airport and the flight to MEM.

Also, they have to rebuild your pairing and reschedule your backend flight if you arrive late and do not get the min rest period required by CBA.

I've seen trip pay increase up to 10 credit hours when the flight needed to be reschedule the next day...and then extended again because of a 1 in 7.

The crew still headed straight home, but got paid for those extra days.

I think the real reason to NOT deviate until you arrive at the final destination is the case where you divert to another field and they end your trip right there (...i.e. they don't extend you to fly to the originally scheduled destination).

Regardless --- and bottom-line --- there are no advantages to deviating early on the back-end.

FDXLAG

Here is the link for all the Fedex guys.

https://pilot.fedex.com/contract/cba...ling_02-15.pdf

Here is how the company sees it:

"Alternately, with respect to the XXXXXXXX grievance, it is the Company’s position that since the grievant and all other members of his crew had already deviated from the backend deadhead, nothing in the agreement required the Company to rebuild the grievants’ trip when the originally scheduled deadhead was canceled."

If you skip to page 43 here is the important quote:

For all the foregoing reasons, the grievances must be denied.

Busboy

Wow!! Lots of almost truths going on here.

Assuming that you have deviated:

1) If your scheduled backend D/H is cancelled---You're SOL. FDXLAG is correct. (If a crewmember has not deviated---only his pairing will be revised)

2) Same duty time scheduled D/H? If your operating flight arrives into your outbound D/H city late and does not meet the minimum turn time 1+30---Your pairing must be rebuilt to show a legal(1+30 turn) D/H.

3) If your operating flight arrives into your outbound D/H city late and does not give you required rest prior to your scheduled D/H---The pairing must be rebuilt to show a legal rest period prior to the new scheduled D/H.

3) If your rebuilt pairing is from the same city and the same day, you will be shown as a deviator on the new scheduled D/H. And, you can not un-deviate.