121.563
Thus far, we have had several crews get full FAA violations in 2009 for "pocketing" an MEL. Don't let it happen to you. I'm not trying to monger fear, and we all know how to play the game, but we still need to be VERY, VERY careful when doing so. Don't let on-time performance or a commute ruin your career.
The only flexibility I'd have in this issue is perhaps if it is extremely minor (broken plate clip, broken map light, reading light out in PSU, etc) is to wait until you get back to the hub, but if I saw anyone that looked like a fed on board if it was up to me (and it isn't) I'd write it up at the outstation.
Don't pocket write ups. Also, don't write up 10 cockpit lights being burnt out at 8am. Call maintenance.
Contact negotiations plus the screwing we're getting on benefits means I'm writing up broken map lights now. And none of this "Write it up when we get back to the hub." If I notice broken on the first flight of the day in an outstation, it's getting written up then. They'll just defer it, but hey. It might take us just long enough to get the deferral done that we're out late by a minute or 2. No D0 bonus for Phil & Co for that flight.
Don't pocket write ups. Also, don't write up 10 cockpit lights being burnt out at 8am. Call maintenance.
Do not compromise safety just because youre afraid of what management may do. If something happens, it's your ticket.
So this brings up the famous interview question: Last flight on Christmas Eve and your nav light (or something similar) goes out at the outstation with no MX. What do you do? If you write it up, the flight will cancel, on Xmas Eve, with your pax stuck for the night.
So this brings up the famous interview question: Last flight on Christmas Eve and your nav light (or something similar) goes out at the outstation with no MX. What do you do? If you write it up, the flight will cancel, on Xmas Eve, with your pax stuck for the night.