There are two kinds of EFBs - those with DIGs and those without:


https://www.youtube.com/watch?v=s2w9X_tHU7k

 

Are you sure you didn't have a percentage bid lying around...

 

[QUOTE=Gunfighter;2713597]
There is no way this can be true. You have zero obligation of any kind on an X day.

This discussion is about what happens during the first minute coming off your last X day. But while you are on it there is no debate about this. Zero obligation while on an X day. Full stop.


Ha! Hardly. I hope I'm wrong about this because that would mean whenever they forget to mark R and annotate a specific 30 hour period, then you'd only have 24, and would still be owed another 30. That's fine with me!

But speaking of the company's perspective, why on earth would they not simply hack out a free memo that says "unless you hear otherwise from CS, you will automatically be released at 6PM going into an X day"? Or at least an "if on long call" version of that?

What possible gain would they get from putting themselves in a position to miss an obvious 30 hour break trying to get 6 more hours of an unusable 12 hour callout going into an X day and then creating a legality issue for rest for the next period?

 

You absolutely do NOT have an obligation to check your schedule or answer your phone on an X day.

From the Scheduling reference handbook (page 96).

 

Correct. The only thing that happens on an X day is the company has a chance to shorten your notification window on your first day from 12 to 10 hours if they get an assignment on your schedule by 9 hours prior to the end.


You are wrong. And you say here exactly why it’s wrong without realizing it. For a 30/168 break you have to have a specific rest period that is at least 30 hours, designated when you start the rest period. You can’t extend it from 24 to 34 and have it count. When you go into a single X day it’s only 24 hours when it starts. Your schedule has you going back on call the next day at midnight. Adding 10 hours if they give you an assignment doesn’t meet the requirements of the regs.

From the ALPA 117 guide:

And if you still don’t believe it, call scheduling and ask a supervisor if a single X day plus a 10 hour window on your first on call day counts as a 30/168 break.

I agree. It would make sense to have an automatic release 6 hours prior to a single X day. There already is early release prior to hard non flying days. My guess is that they want to keep the flexibility to roll your days if needed. My experience has been that they are very good at making sure they turn any 24 hour breaks on my schedule into 30 rest periods.

 

You are correct in that you don't have an obligation to check your schedule on an X day but be ready for that call at 0001 if you don't.


Not entirely true. Say you have 1 golden day in between to groups of 4 days on call. If you are not used on the last on call day prior to the golden day you are automatically released at 1200 so you will have 36 hours in rest. This is NOT true of a regular X day. CS will not necessarily put an R on your schedule but you will have a 36 hour rest period that satisfies the requirement. How do I know this? Personal experience and a call to CS.

See above.

If it's a regular X day they should call and put you into 30hr rest prior to the X day. If they don't then it's on them.

Denny

 

My head is swimming here, and I am normally a reserve pilot.
Maybe this question will help someone, or perhaps it will just show my ignorance.
Why would scheduling assign rest that begins on day prior to an X day (say starting at 2000) and the reserve rest display shows that rest terminating at 0219 on the X day?
Seeing that could lead one to believe that the X day itself was not rest.

And would a single screen display of rest periods—including X or * day rests—help unmuddy the waters?

 

I’ve had them put some seemingly random rest periods after trips that ended on my last reserve day and extend into an X or golden day. Like your example they ended at 0041 or 0102. No idea why.

X days are already known to be rest so they don’t have to put anything specific in iCrew regarding rest for it to count as a prospective rest period.

A single screen would help. Along with a ton of other things that could be improved in iCrew.

 

For those of you who do not believe in the X day schedule check, I guess technically a pilot could wait till 0001 of the on call day to check the schedule, thus not checking the schedule on the X day.

...but the PWA clearly puts the responsibility on the pilot for checking and acknowledging an assignment for the first on call day. How else do you you interpret section 23.S.3.d.2.b) and the associated note?

23.S.3.
d. will be notified of his assignment to open time under Section 23 N. or O. by one of the following two methods:
1) telephone contact from Crew Scheduling.
2) electronic placement of a rotation or conversion to short call that is placed on his schedule prior to:
a) his release from a rotation, or
b) nine hours before the end of his last non-fly day (other than a vacation day) before an on-call day.
Note: A pilot is responsible for ascertaining whether he has been assigned a rotation or converted to short call under Section 23 S. 3. d. 2) b). Crew Scheduling is not required to make telephone contact for such an assignment or conversion.

or 2

3.S.2.a.5) Note Two: Note two: A pilot is responsible for ascertaining whether he has been so assigned a rotation. Crew Scheduling is not required to make telephone contact for such an assignment.

 

If you live close to your base, you can check your schedule after breakfast on your first on call day. An hour to shower/dress/pack and 30 minutes to drive to the airport means a schedule check at 0830 can have you signing in at the worst-case 1000 start. Minimum schedule checks aren't necessarily adequate for a commuter, but they work fine in base.