LaBradford22
Advanced
- May 15, 2003
- 206
- 0
Actually, if you read the contract, LAX has several satellite bases (SNA, ONT, LGB) that the company can use to terminate a trip sequence for an LAX-based pilot. So, in the case that you described (LAX-based pilot terminating his trip sequence in SNA), the per diem clock was not running and there was no company-paid hotel room.
The only part that doesn't make 100% sense is the deadhead segment from LAX to SAN. Although, as someone else pointed out, that may make sense if you look at the larger picture and all of the other constraints that come into play when scheduling crews. Come to think of it, LAX to SAN doesn't cost the company much in terms of deadheading (about a 1-hour segment).
One thing the company could do to make crew scheduling more efficient is to isolate parts of the fleet, perhaps in hubs. For example, the B757 and A300 have had seats put back because it makes sense to do that in high demand / low yield leisure routes (i.e. Florida and the Caribbean). Maybe the A300 and B757 could be completely isolated in MIA. If the 737-800 fleet grows enough, maybe that one could be isolated in ORD, and the MD80 fleet (~360 today, should shrink in the future) could be isolated in DFW. Then, the crew scheduling for each fleet becomes similar to the way it works at WN - lots of 1-day trips with out and back turns right back to the hub city. Of course, APA may not be too crazy about this, because it limits their pilots' base city options when they move up fleets. For example, an MD80 CA moving up to B757 CA may not like having to relocate to MIA.
The only part that doesn't make 100% sense is the deadhead segment from LAX to SAN. Although, as someone else pointed out, that may make sense if you look at the larger picture and all of the other constraints that come into play when scheduling crews. Come to think of it, LAX to SAN doesn't cost the company much in terms of deadheading (about a 1-hour segment).
One thing the company could do to make crew scheduling more efficient is to isolate parts of the fleet, perhaps in hubs. For example, the B757 and A300 have had seats put back because it makes sense to do that in high demand / low yield leisure routes (i.e. Florida and the Caribbean). Maybe the A300 and B757 could be completely isolated in MIA. If the 737-800 fleet grows enough, maybe that one could be isolated in ORD, and the MD80 fleet (~360 today, should shrink in the future) could be isolated in DFW. Then, the crew scheduling for each fleet becomes similar to the way it works at WN - lots of 1-day trips with out and back turns right back to the hub city. Of course, APA may not be too crazy about this, because it limits their pilots' base city options when they move up fleets. For example, an MD80 CA moving up to B757 CA may not like having to relocate to MIA.