Quote:
1. Are you sure that the trip you are trying to swap for is a true, uncovered trip and not a Q trip?
2. Is the trip truly the same trip length as depicted in icrew? Do NOT trust MiCrew. MiCrew often incorrectly depicts trip length for any trip that releases after midnight. Example: take an ATL-LGA-ATL turn that blocks in at 2345. Add the 30 minute post flight and the trip officially ends at 0015 the next day and will correctly be depicted in icrew as a 2-day. MiCrew however will show it as a 1 day. MiCrew will also incorrectly depict most red-eyes the same way. The only time micrew correctly depicts red-eye trip length is if the final leg departs after midnight local. For any red-eye that departs before midnight, MiCrew incorrectly displays the trip length as one day less than it is contractually.
I actually submitted an FCR about this. Corporate spin reply, so don't expect any programming correction any time soon.
Pretty sure if the days are black, there’s no way to swap trips that cover the exact same days. When you do yet available minus required, the trip you are picking up has to be MORE Negative than the one you are dropping. If the trips are on the same days, the math will be equal, therefore not allowed.Originally Posted by Herkflyr
It should always process the swap. Two things.1. Are you sure that the trip you are trying to swap for is a true, uncovered trip and not a Q trip?
2. Is the trip truly the same trip length as depicted in icrew? Do NOT trust MiCrew. MiCrew often incorrectly depicts trip length for any trip that releases after midnight. Example: take an ATL-LGA-ATL turn that blocks in at 2345. Add the 30 minute post flight and the trip officially ends at 0015 the next day and will correctly be depicted in icrew as a 2-day. MiCrew however will show it as a 1 day. MiCrew will also incorrectly depict most red-eyes the same way. The only time micrew correctly depicts red-eye trip length is if the final leg departs after midnight local. For any red-eye that departs before midnight, MiCrew incorrectly displays the trip length as one day less than it is contractually.
I actually submitted an FCR about this. Corporate spin reply, so don't expect any programming correction any time soon.