Busdrivr

You'll care when someone drops a Deuce in your cockpit.

Perm11FO

Direct hiring into the 767 probably was caused by the failure to coordinate aircraft deliveries with the training department so that the simulators needed for the crew flow are in place before the aircraft arrive.

In addition, sadly, we purchased some new fangled sim design that had spectacular failures as the new 76s were landing in MEM monthly. I understand that the next sims will be built by CAE or Flight Safety, companies that have long track records, rather than from a company that has no experience.

Even as this is written, it appears clear that FDX still has inadequate 76 sims to handle the needed training and evaluation at this moment. Since you cannot make a full function sim out of a refrigerator box, the timing failure to order sims to match the fleet numbers take time to recover from....

NoHaz

Also cuts down on training throughput and costs. Leave the junior FOs frozen in the 75 and put new hires in widebody FO seats where they won't look to upgrade or change seats any time soon.

Fdxlag2

Agree with the sentiment, but screwing the current 75 FOs does not save any throughput. Difference training is the exact same sims regardless of whether it is a new hire or "passed over" current FDX pilot.

NoHaz

If they choose the 67. But, full training cycle if they pick the MD, Bus, or 777

MrtyMcFly

BOI commuters:

I am a new hire and start Indoc next week and I have a few questions I am hoping you guys can help me out with. I am moving the family to Boise this fall and I have some commuting/QOL questions for those of you who fly out of and commute from BOI. I know that there are usually about 3 flights out per day that leave BOI, is there ever an issue commuting to MEM? Can you leave same day to pick up trips or sit reserve out of MEM?

It looks like there are 2 A300 and 1 757 flights leaving BOI as the norm flying schedule, how senior do legs leaving BOI go? Can I speculate that the 767 is going to take over those lines when the A300 goes away? I am not planning on taking a 767 at indoc if you SSN is high enough. Thoughts?

Any insight would be appreciated, thank you!

MrtyMcFly

I am not planning on taking a 767 at indoc if you SSN is high enough.[/QUOTE]

Correction, I AM planning on taking a 767 at indoc if my SSN is high enough.

kronan

Interestingly enough,
all 76 training was conducted in the 75 sims. Same flexes 75\76. Then some top off academics and IOE 75\76 and away you go.

Why company couldn't just place all newhires in the 75, allow the 75 FOs w/ 76 bids to hit the top off and 76 Fam, I'll never know.

Adlerdriver

I'm not a BOI commuter, but many of your questions are fairly easy to answer regardless. Hopefully a BOI person can jump in and give you some more in depth info.

Personally, I wouldn't recommend picking an aircraft based on the current equipment being used to service your home town airport. Some cities are more stable than others but many change depending on many factors. Airbus are not going away any time soon, so expecting the BOI A300 to morph to a 767 isn't a given. Currently no BOI flying in the MEM 767 Bidpack. I'd pick a 767 because you think the seniority improvement will be better on a growing fleet, you want a WB aircraft that flies domestic or maybe some other factors. If it ends up in BOI even better. The A300 BOI flights in May were daytime flights. If the 767 takes those, it'll probably be a while before you could hold day flying anyway, so the fact that you're on a fleet that services BOI might not matter for many years.

In general, this doesn't look like the easiest commute we have here at Fedex by a long shot. City schedules can change from month to month, so this is just based on a snap shot of May and June. The good news is, you can get to MEM or back to BOI on company metal 7 days a week. The only exception is there's no flight outbound to BOI on Monday (which is common for most cities) since there's no outbound freight.

I don't see the two Airbus flights you mentioned (at least to MEM), there's only one. There are Airbus or 757 departures that go to OAK (usually via SLC) which may be what you're seeing. The equipment on MEM seems to vary from month to month. In May, Airbus had the day flights and 757 at night. June looks like mostly 757s.

The biggest issue I see is the inbound flight to MEM often has two legs via CPR. That's obviously one extra time each commute to get bit by MX issues, Wx diverts, etc. With one flight each day to make it to MEM for the am or pm launch, you have no back ups. It's likely you'll be commuting to the early am flights to start with. The showtime (1 hour prior to takeoff) for the pm departure out of BOI is early (1743L) and since you're turning through CPR, it arrives in MEM on the late side (0027L). That could be an issue with the commuter protection policy if you're commuting to a flight that shows within 1.5 hours of your scheduled arrival in MEM or your duty is longer than 13:30 starting from the showtime of your BOI jumpseat. Exceeding those parameters would mean you're not protected in the event you miss a trip due to your inbound jumpseat being late.

If you're on A reserve period (0130-1330), you won't be able to use the evening jumpseat to commute in just before you go on call (especially since you need to be available by 0000L and your jumpseat flight gets in at 0027L). If you already have a trip assigned, you could. Otherwise you'll probably need to come in on the morning flight or commute offline.

So, that's a quick look. It's doable, as are most cities we service. Just not the easiest. Hopefully others have some first hand advice.

June schedules BOI-MEM:
Mon-Fri
BOI-MEM 0645L Showtime 1202L Arrive
BOI-CPR-MEM 1743L Show 0027L Arrive
Sat
BOI-MEM 0707L Show 1230L Arrive
Sun
BOI-OKC-MEM 0600L Show 1241L Arrive

June MEM-BOI:
Tues-Fri
MEM-BOI 1405L Show 1754L Arrive
MEM-BOI 0250L Show 0640L Arrive
Sat
MEM-BOI 1515L Show 1850L Arrive
MEM-CPR-BOI 0248L Show 0733L Arrive
Sun
MEM-BOI 1415L Show 1804L Arrive

MrtyMcFly

Adlerdriver, thank you for the great reply, I really appreciate it!