Originally Posted by
Snookered
Appreciate the admonishment everyone, no, really! Lots of lessons learned about the pilot group in this discussion!
But can’t say that I have seen the needle move at all in spite of everyone above holding the line when it comes to not doing the company any favors with regards to SC callouts.
Admittedly small sample size here personally, but my last 3 out of 4 callouts while on SC over the past 2 months have been less than 2 hours to report … with today’s (30 minutes) being the shortest. Prior to that, most have been in excess of 2 hours. Just seemed to be trending in the wrong direction and was wondering if others are seeing the same? (Intended topic for my original post). I’m on the fringe of what’s reasonably acceptable for my commute (drive) to the airport for a SC callout anyhow, so I’m considering bidding regular for a while.
Glad you posted as it’s generated good discussion. The best argument I can give you to not do that is that it encourages bad behavior on the part of scheduling and there are some of your peers who won’t know any better. Assigning that trip they did so far out is a conscious choice on their part. They could have that flight go out on time (GS, WS or RR) but deliberately chose not to, hoping that you’d bite. By accepting it, they are emboldened to do it again. That late departure is on them not you.
To answer your other question, they 100 percent can see when you log into MiCrew and it 100 percent does not matter. Unless you mash that acknowledge button that’s not a notification; it doesn’t matter how many times you view it, you are not notified. CNO is not notification for a trip either only conversion from LC to SC or SC related rest. CNO for stand alone rest doesn’t count either, I’ve had 2 trips dropped just this year due to this. I NEVER hit acknowledge until an actual person calls and I’m dang sure it’s a clean kill.