Delays and reporting
#41
Gets Weekends Off
Joined APC: Mar 2018
Posts: 1,016
Yikes. It's 2019. The company owns the airplanes and the airline. You're an employee. You operate within the authority given to you by the company. If they want the airplane to depart, barring any safety concerns you might have, you comply. Captains are not God anymore.
#42
Gets Weekends Off
Joined APC: May 2012
Position: CAP A320
Posts: 300
Happened to me (us) recently...
Had I NOT acknowledged the CCS msg, my unSoft Start day would have still started at 815, but they would not have gotten the extra 4 hours that they ended up with.
I would have had to extended.. which I would have done (I get to the airport with my uniform on, I'm spring loaded to lean forward and get the job done).
This Soft Start saved the company about $1600 among the 3 of us~
Food for though
Always
Motch
FS, FP & FtC
Had I NOT acknowledged the CCS msg, my unSoft Start day would have still started at 815, but they would not have gotten the extra 4 hours that they ended up with.
I would have had to extended.. which I would have done (I get to the airport with my uniform on, I'm spring loaded to lean forward and get the job done).
This Soft Start saved the company about $1600 among the 3 of us~
Food for though
Always
Motch
FS, FP & FtC
Here's the DYK for your perusal.
#43
Gets Weekends Off
Joined APC: Mar 2017
Posts: 705
I think you missed the memo that went into detail from ALPA and company about the Captains trying to make the call on keeping the door open for pax. It's not in your control and stated in the memo. Though a pilot is trying to do the right thing, we do not have all the available information for connections downrange and where that plane is needed, etc... It's not about zone overruling the CAP, it's when NOC tells zone, it must go. You cannot say no. Or you can, but you'll be getting a call from FODM that tells you, you must go. You don't have a leg to stand on, since what info do you have to support your "eye in the sky" decision? Right, not enough! So let's stop with the Captain Authority issue. Doesn't apply here when a decision from the top comes.
#45
Gets Weekends Off
Joined APC: May 2012
Position: CAP A320
Posts: 300
It's amazing how many pilots don't read MEC/LEC reports or memos, ALPA DYK's, Fleet Newsletters, under the Safety section of Content locker (FSAP news, FOQA notes, Safetyliner), Pilot Bulletins, etc.... Same guys that post the same silly questions or post scenarios that have been addressed.I get it when people might be confused with our UPA legalese, and post for clarification. Problem is guys like you want everyone else to produce the document because they were too lazy to read it themselves the first time and even lazier, asking everyone else to get it for them. ON top of that, you'll argue until your face turns blue, on procedures or actions, that are wrong because you were misinformed or lazy.
#46
Gets Weekends Off
Joined APC: Mar 2017
Posts: 705
It's amazing how many pilots don't read MEC/LEC reports or memos, ALPA DYK's, Fleet Newsletters, under the Safety section of Content locker (FSAP news, FOQA notes, Safetyliner), Pilot Bulletins, etc.... Same guys that post the same silly questions or post scenarios that have been addressed.I get it when people might be confused with our UPA legalese, and post for clarification. Problem is guys like you want everyone else to produce the document because they were too lazy to read it themselves the first time and even lazier, asking everyone else to get it for them. ON top of that, you'll argue until your face turns blue, on procedures or actions, that are wrong because you were misinformed or lazy.
#47
Gets Weekends Off
Joined APC: Mar 2018
Posts: 1,016
Of course alpa didn’t sign any letter to the effect this knucklehead implies. I guarantee that my contractual/FOM knowledge (and yours too, Floyd) dwarfs this guys. Not sure what his agenda is, but what he’s trying to infer(that some SOC scmuck has final say as to the brake release/pushback) is completely off the mark. Sometimes reading this forum is fun. But honestly, since anybody can post here, you never know when you’re dealing with a management boot lick, scab, or just some company employee who simply doesn’t know any better. Dollars to donuts fanaticalflyer is one of the three.
#48
Banned
Joined APC: Mar 2013
Posts: 384
At 0300 the company determines that due to a known delay they want to delay a pilot’s 0700 report time until 1100 for a Basic unaugmented FDP. Note that without a soft start, his FDP would begin at 0700 and yield a Table B limit of 14 hours, which would require the FDP end by 2100.
At 0300 the company successfully reaches the pilot and advises him of their intent to “soft start” the FDP. The original 0700 report time for that FDP is now treated as the RAP start time, with a new 1100 report time. To calculate the correct RAP+FDP limit for that day, you must follow these steps.
At 0300 the company successfully reaches the pilot and advises him of their intent to “soft start” the FDP. The original 0700 report time for that FDP is now treated as the RAP start time, with a new 1100 report time. To calculate the correct RAP+FDP limit for that day, you must follow these steps.
Can someone explain to me why the RAP starts at 0700 from the soft start vs 0300 when the company contacted and was acknowledged by the pilot? Doesn't the company calling you interrupt the rest period?
#49
Gets Weekends Off
Joined APC: Sep 2013
Posts: 919
At 0300 you are still on rest. The company can attempt to contact you during your rest and, if they are successful, they can notify you of the change in your upcoming duty and it doesn't interrupt your current rest period!
YOU ARE UNDER NO OBLIGATION TO ANSWER YOUR PHONE WHEN YOU ARE ON REST!!!!!
Because you are under no obligation to the company at this time, the FAA views this as an allowable situation. I may not agree with the logic of all that is allowed to happen afterward, but basically the FAA looks at it as the same situation as being put on a Short Call, where you are now not going to have to report to the airport at the beginning of your "duty period" but you are still anticipating an actual Flight Duty period, so you get the same rest treatment as a Short Call reserve that had an availability period that started at your original report time.
This example is what we are calling a "soft reset."
Keep in mind that if the delay is substantial and they contact you with greater than 10 hours notice before your updated report time, you can be "hard reset." This means that you are given a new rest period that now ends at your new updated report time and all your duty calculation will be based on that. This situation is more common in the international theater, when the inbound airplane is substantially delayed out of the US.
In either case, you can avoid any issues because:
YOU ARE UNDER NO OBLIGATION TO ANSWER YOUR PHONE WHEN YOU ARE ON REST!!!!!
If you delay in returning the phone call from the crew desk until after you have started your duty period (0701 or later) , then the original limits of that duty period apply. So, they can work within those limits or put you back on rest for 10 hours and try again.
#50
Gets Weekends Off
Joined APC: Mar 2006
Position: 737 fo
Posts: 908
It's amazing how many pilots don't read MEC/LEC reports or memos, ALPA DYK's, Fleet Newsletters, under the Safety section of Content locker (FSAP news, FOQA notes, Safetyliner), Pilot Bulletins, etc.... Same guys that post the same silly questions or post scenarios that have been addressed.I get it when people might be confused with our UPA legalese, and post for clarification. Problem is guys like you want everyone else to produce the document because they were too lazy to read it themselves the first time and even lazier, asking everyone else to get it for them. ON top of that, you'll argue until your face turns blue, on procedures or actions, that are wrong because you were misinformed or lazy.
Thread
Thread Starter
Forum
Replies
Last Post