02.02.2015 Views

Exhibits Vol 2 - Independent Pilots Association

Exhibits Vol 2 - Independent Pilots Association

Exhibits Vol 2 - Independent Pilots Association

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Harry Edwards<br />

FedexA300Mem@alpa.org<br />

B727 MEM<br />

Captain First Officer Second Officer<br />

Average BLG CH 72+06 72+06 72+06<br />

RLG CH 69+15 69+15 69+15<br />

R-day value CH 4+37 4+37 4+37<br />

# of Regular Lines 88 (53%) 88 (55%) 88 (54%)<br />

# of Secondary Lines 25 (15%) 22 (14%) 18 (11%)<br />

# of Reserve Lines 52 (32%) 50 (31%) 56 (35%)<br />

Total Lines 165 160 162<br />

Total CH Available (no c/o) 6678 6678 6678<br />

Avg CH/Rday 8.5 8.9 7.9<br />

Carry-in CH from Feb 144 144 144<br />

Feb CH carry-in to Total CHs 2.2% 2.2% 2.2%<br />

Disputes: None<br />

PSIT Notes:<br />

July is a four week month with Independence Day falling on the first Monday of the month. The BLG target was<br />

72 CH, with the average coming in at 72+06. Due to the holiday, many of the weekend pairings start with a front<br />

end DH. The exception to this was SAV, as there were pairings from SAV that were required to be built into other<br />

lines. This is also the reason there are some pairings flown out of the SAV weekend layover. BOS and PIA were<br />

again mixed, as BOS cannot turn to itself. In the first week of the month, to make it work with a 4-day work week,<br />

a CID pairing had to be put into the mix as well. LFT, which normally operates as a weekend layover was changed<br />

to a double-DH design. Because the DH’s on both ends operated on Sunday, there was a 1-in-7 issue with building<br />

it with LFT DH’s on both ends. We’ve asked the company to return this to a weekend layover.<br />

We appreciate the feedback we’re receiving each month. Please continue to send your comments, good and bad.<br />

The Scheduling Committee PIREP is our primary means of tracking issues since the company doesn’t share reports<br />

with us. Therefore, please submit a Scheduling Committee PIREP anytime you submit a Company Pilot Ops<br />

Report and then please CC the report to us here at the PSIT via email. This is the only way we can track data on<br />

current issues with any reliability. As always, we welcome your input and feedback on any trip that you operate.<br />

In Unity,<br />

Tom Rutledge<br />

Curt Henry<br />

J D Oliver<br />

Fedex757+727MEM@ALPA.org

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!