eolesen said:
Depending on the airline, it's not unusual for schedules to be held back until after the IATA Slot Conference, which was just held a couple weeks ago and closed on November 17th.
http://www.iata.org/policy/slots/Documents/calendar-slot-activities.pdf
Holy Cow. several posts on the topic and ones that are dead on accurate too.
Woo hoo. There is hope!
And even beyond the slot conference, DL can and does adjust the start and end dates of its summer seasonal service. They have done it before and will do it again.
DL has indeed been very aggressive at altering schedules up until the last minute. Even though DL usually has decided what int'l routes to fly by this time, it often makes tweaks to the end/start and DOW operation as late as 3 months or more before peak season. In off-peak season, DL makes changes even closer to departure.
Most of the changes that were noted in the OP envolve continental Europe which is part of the DL-AF-KL JV and not the DL-VS JV. DL was required by AF/KL to build very clear divisions between its two TATL JVs which are very much separate. DL is not sharing revenue from the VS JV with AF-KL and vv. There is no codesharing or cooperation beyond LHR with JV because of this.
DL could well adjust capacity at LHR and likely will but it probably will not affect what routes will be flown but more likely additional capacity at LHR.
robbed,
AA/US will likely fly their current published schedules for the summer. The peak booking period for summer int'l flights starts soon after the first of the year. AA/US would have to make alot of adjustments to not lose revenue if they started messing with next summer's schedules just weeks after the merger is approved - assuming it happens early in 2014.
Also, AA/US cannot share detailed financial information including route performance until they are merged so there is no way Parker and co. can know how well AA's routes do but practically anything can make money in the summer.
Your question about automation coordenation is valid. E can speak to that because he knows that área well but AA/US can operate separately under their own code for months and then implemente a codeshare as soon as they can hook up their systems. There are now fairly industry standard processes so they can run in parallel fairly quickly.
A full merge of IT systems is a much bigger process and will be very well planned to avoid the problems HP-US and UA-CO had at cutover.