Oh Avelo

We had that issue with a checkpilot. They eventually removed him from the program.

On the line side, FOs can no bid a captain in PBS, but reserves can refuse an assignment due to the other crew member (beyond just calling in sick). Captain's can't no bid FOs (because of the order of the PBS runs), but can always tell their CP to either swap out the FO or deal with a last minute sick call.

When I was a pretty new 717 FO, the first month I had a line, I got a call from scheduling telling me they were swapping me to a different (way less desirable) trip and putting that FO on my trip. I asked why but they said that "management" had told them to do so. Turns out that the other FO had been dating two of the three FAs on his trip, without them knowing about each other, and they both refused to fly with him. So instead of recrewing 2 FAs (or 1 FO), they swapped us. Fortunately the captain was cool so it wasn't a totally bad day.

Sorry, this is where I part with ALPA. Cite the “of good morale character” and fire him. Far easier solution.



Derg is absolutely correct. It’s damn near impossible to be fired from a legacy. You’d have to do moronic level of stupid, most likely on more than one occasion.
 
AA did that, too. If enough FOs put a Captain on the Bid Avoid/No Fly list, that Captain would be transferred to another base. I'm pretty sure we had one that had involuntarily seen every crew base AA had. It may have been the same one that the FOs started stealing his landing credit without him knowing about it (the joy of archaic ACARS codes).
I don’t know how you can force a guy into another base and not violate his seniority and the cba.
 
Well me too was about sexual harassment/assaults in the workplace. Not the topic at hand.

And patriarchic bigotry isn’t a thing. You made that up. It has no meaning.

At one point, I had an honest mis-speak and said "you know, the me first movement" to my wife, and she has not let me live it down.
 
Back
Top